[Desktop-packages] [Bug 2051478] Re: Typing passphrase pretty quickly using Yubikey fails to unlock a LUKS partition
I've confirmed the merge fixed the issue. https://launchpad.net/ubuntu/+source/plymouth/24.004.60-1ubuntu1 ** Changed in: plymouth (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2051478 Title: Typing passphrase pretty quickly using Yubikey fails to unlock a LUKS partition Status in Plymouth: Fix Released Status in cryptsetup package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Fix Released Bug description: It looks like there are some behavioral changes between 22.02.122 and 23.360.11. I didn't have any issue until recently but after upgrading to 23.360.11 on Ubuntu, the same unlocking method of LUKS partition stopped working. How to reproduce: 1. format Yubikey with a static password ``` $ ykman otp static --generate 2 ``` (it will emit 38 characters and the ENTER event within a moment when a button is long pressed) 2. add the new key to LUKS ``` $ sudo cryptsetup luksAddKey /dev/nvme0n1p3 ``` 3. reboot and use the Yubikey to input the passphrase Actual: it fails to unlock When typing the same passphrase by-hand it works. Furthermore, when not using Plymouth, both by-hand typing and Yubikey work. WORKAROUND: 1. boot into the recovery mode 2. unlock the volume in the console 3. remove "splash" from /etc/default/grub and run `update-grub` 3. reboot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: cryptsetup 2:2.6.1-6ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 15:41:03 2024 InstallationDate: Installed on 2024-01-08 (21 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crypttab: dm_crypt-0 UUID=cfd8c295-9988-4934-a91a-460a9d16d80f none luks To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2051478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051478] Re: unlock passphrase doesn't work in plymouth but works in recovery mode
By downgrading plymouth from 23.360.11-0ubuntu2 to 22.02.122-4ubuntu2 by hand, the passphrase worked so it's a plymouth issue rather than cryptsetup, it seems. https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/libplymouth5_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-label_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-theme-spinner_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-theme-ubuntu-text_22.02.122-4ubuntu2_amd64.deb ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Changed in: cryptsetup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2051478 Title: unlock passphrase doesn't work in plymouth but works in recovery mode Status in cryptsetup package in Ubuntu: Invalid Status in plymouth package in Ubuntu: New Bug description: The system suddenly stopped accepting the existing passphrase on boot. However, the passphrase is definitely correct since the same one can be used in the recovery mode and it unlocks the volume appropriately. I'm not sure which recent update brought this behavior. Last successful graphical boot: 2024-01-28 00:43:09 +0900 Fwiw, the existing passphrase was long enough and contains some special characters such as "!". The confusing part is shorter passphrase but with "!" seems to work. WORKAROUND: 1. boot into the recovery mode 2. unlock the volume in the console 3. add a new key with `cryptsetup luksAddKey /dev/nvme0n1p3` or remove "splash" from /etc/default/grub and run `update-grub` 3. reboot ProblemType: BugDistroRelease: Ubuntu 24.04 Package: cryptsetup 2:2.6.1-6ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 15:41:03 2024 InstallationDate: Installed on 2024-01-08 (21 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crypttab: dm_crypt-0 UUID=cfd8c295-9988-4934-a91a-460a9d16d80f none luks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2051478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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
[Desktop-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 Desktop 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 daemon.notice
[Desktop-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]
[Desktop-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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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 BSS APId 255
[Desktop-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
[Desktop-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 Desktop 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 Compilers:
[Desktop-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 Desktop 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: 27.8 C mobo:
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
** Changed in: deja-dup Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: Invalid Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Eoan: Fix Released Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
FWIW, "python-gi" is probably from:
debian/rules
override_dh_auto_configure:
dh_auto_configure -- \
--libexecdir=/usr/lib \
-Dgvfs_pkgs=gvfs-backends,python-gi,gir1.2-glib-2.0 \
-Dboto_pkgs=python-boto \
-Dcloudfiles_pkgs=python-cloudfiles \
-Dswiftclient_pkgs=python-swiftclient
and it seems the definition of gvfs_pkgs is:
meson_options.txt
option('gvfs_pkgs', type: 'string', value: '', description: 'Distro package
names to install giobackend duplicity support, separated by commas')
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1847706
Title:
Deja Dup still tells python-gi (python 2) is required while duplicity
is now python3
Status in Déjà Dup:
Triaged
Status in deja-dup package in Ubuntu:
Triaged
Status in deja-dup source package in Eoan:
Triaged
Bug description:
Please see the screenshot attached. When running a backup operation
against a remote server with SSH, Deja Dup stops by saying "python-gi"
package is required.
However, duplicity is updated with Python3 now, so it doesn't make
sense to install Python 2 based package. The prerequisite check needs
to be updated probably with python3-gi instead.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: deja-dup 40.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 11 12:34:15 2019
InstallationDate: Installed on 2019-08-28 (43 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
** Attachment added: "Screenshot from 2019-10-11 12-35-40.png" https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1847706/+attachment/5296436/+files/Screenshot%20from%202019-10-11%2012-35-40.png ** Also affects: deja-dup Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: New Status in deja-dup package in Ubuntu: New Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] [NEW] Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
Public bug reported: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup Importance: Undecided Status: New ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Summary changed: - Deja Dup tells python-gi (python 2) is still required while duplicity is now python3 + Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: New Status in deja-dup package in Ubuntu: New Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838345] Re: Support Japanese new era "令和 (Reiwa)"
Indeed, the upstream of Takao fonts as IPA fonts has a new release, so we need to release a new one too. https://ipafont.ipa.go.jp/ > 2019-04-26 > > IPAex Fonts (Ver.004.01) were released. Detail information is shown in > release notes. > > Note: SQUARE ERA NAME REIWA(U+32FF) has been added. You may need to update > the dictionary for your input-method system to enter this character by Kana > input. Please refer instruction of your system for that. > New version of IPAmjMincho with SQUARE ERA NAME REIWA will be available by > the end of May. ** Changed in: takao-fonts Importance: Undecided => Wishlist ** Changed in: takao-fonts Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1838345 Title: Support Japanese new era "令和 (Reiwa)" Status in Takao Fonts: Triaged Status in fonts-takao package in Ubuntu: Triaged Status in fonts-takao source package in Xenial: Triaged Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） [Impact] Users who run Ubuntu in Japanese. [Test cases] == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1) Type in 'heisei' 2) Verify that the input method in use gives you an option "平成", and optionally also the square era glyph. 3) Type in 'reiwa' 4) Verify that the input method in use gives you an option that includes "令和", and possibly also the square era glyph (if supported for Heisei) 5) Type in the following strings, and verify that the options are provided in the input method: * "れいわ"(reiwa) => "令和" * "れいわ"(reiwa) => "㋿" * "２０１８ねん"(2018nenn) => "平成三十年" * "２０１９ねん"(2019nenn) => "平成三十一年" * "２０１９ねん"(2019nenn) => "令和元年" * "２０２０ねん"(2020nenn) => "令和二年" [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. To manage notifications about this bug go to: https://bugs.launchpad.net/takao-fonts/+bug/1838345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1500504] Re: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all
@Mark, Although I or someone needs to report and fix it in the kernel, for the time being you can write the file as follows to make sure to add "i8042.nomux" for every kernel update. [/etc/default/grub.d/touchpad.cfg] # workaround for LP: #1500504 GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT i8042.nomux" `sudo update-grub` needs to be executed by hand for the first time. But update-grub will be triggered automatically for the next kernel update. Thanks, ** Description changed: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] - ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] - ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] - ↳ Video Bus id=7[slave keyboard (3)] - ↳ Power Buttonid=8[slave keyboard (3)] - ↳ FJ Camera id=10 [slave keyboard (3)] - ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] + ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] + ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] + ↳ Video Bus id=7[slave keyboard (3)] + ↳ Power Buttonid=8[slave keyboard (3)] + ↳ FJ Camera id=10 [slave keyboard (3)] + ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] - ProblemType: Bug - DistroRelease: Ubuntu 15.10 + WORKAROUND: + 1. write "/etc/default/grub.d/touchpad.cfg" as follows + + # workaround for LP: #1500504 + GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT i8042.nomux" + + 2. execute `sudo update-grub` and reboot + + + ProblemType: BugDistroRelease: Ubuntu 15.10 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: - + CurrentDesktop: Unity Date: Tue Sep 29 01:23:48 2015 - DistUpgraded: Fresh install - DistroCodename: wily + DistUpgraded: Fresh installDistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes - InstallationDate: Installed on 2015-09-28 (0 days ago) - InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) + InstallationDate: Installed on 2015-09-28 (0 days ago)InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: FUJITSU FMVS90TB - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 - SourcePackage: xserver-xorg-input-synaptics + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Sep 29 00:39:08 2015 xserver.configfile: default xserver.errors: - Error loading keymap
[Desktop-packages] [Bug 1500504] Re: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all
@Mark (1aunchpad-nct), For my case(FUJITSU FMVS90TB), only i8042.nomux was needed. I have no problem with suspend/resume. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1500504 Title: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ FJ Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: CurrentDesktop: Unity Date: Tue Sep 29 01:23:48 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: FUJITSU FMVS90TB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Sep 29 00:39:08 2015 xserver.configfile: default xserver.errors: Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5138 vendor SHP xserver.version: 2:1.17.2-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1500504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1500504] Re: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all
To be clear, the touchpad is not broken. It works on Windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1500504 Title: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ FJ Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: CurrentDesktop: Unity Date: Tue Sep 29 01:23:48 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: FUJITSU FMVS90TB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Sep 29 00:39:08 2015 xserver.configfile: default xserver.errors: Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5138 vendor SHP xserver.version: 2:1.17.2-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1500504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1500504] Re: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all
For the record, I tried mainline build below, but I still don't see any event from touchpad. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc3-unstable/ Linux lifebook 4.3.0-040300rc3-generic #201509271225 SMP Sun Sep 27 12:26:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1500504 Title: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ FJ Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: CurrentDesktop: Unity Date: Tue Sep 29 01:23:48 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: FUJITSU FMVS90TB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Sep 29 00:39:08 2015 xserver.configfile: default xserver.errors: Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5138 vendor SHP xserver.version: 2:1.17.2-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1500504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1500504] Re: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all
"i8042.nomux" does the trick. I've got the kernel parameter from here: https://bugzilla.kernel.org/show_bug.cgi?id=69731 Will test it more to confirm it really fixes my problem. ** Bug watch added: Linux Kernel Bug Tracker #69731 http://bugzilla.kernel.org/show_bug.cgi?id=69731 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1500504 Title: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ FJ Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: CurrentDesktop: Unity Date: Tue Sep 29 01:23:48 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: FUJITSU FMVS90TB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Sep 29 00:39:08 2015 xserver.configfile: default xserver.errors: Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5138 vendor SHP xserver.version: 2:1.17.2-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1500504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1500504] Re: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all
I can get events from event9(touchscreen) in evtest, but no event from event4(touchpad). [/proc/bus/input/devices] I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input9 U: Uniq= H: Handlers=mouse0 event4 B: PROP=1 B: EV=b B: KEY=e520 3 0 0 0 0 B: ABS=66080001103 ... I: Bus=0003 Vendor=04f3 Product=0095 Version=0110 N: Name="ELAN Touchscreen" P: Phys=usb-:00:14.0-4/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0095.0001/input/input17 U: Uniq= H: Handlers=mouse1 event9 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=32738003 [evtest to event4(touchpad)] $ sudo evtest /dev/input/event4 Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1 Input device name: "SynPS/2 Synaptics TouchPad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 273 (BTN_RIGHT) Event code 325 (BTN_TOOL_FINGER) Event code 328 (BTN_TOOL_QUINTTAP) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event code 335 (BTN_TOOL_QUADTAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 1298 Max 5692 Resolution 49 Event code 1 (ABS_Y) Value 0 Min 1150 Max 4854 Resolution 90 Event code 24 (ABS_PRESSURE) Value 0 Min0 Max 255 Event code 28 (ABS_TOOL_WIDTH) Value 0 Min0 Max 15 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max1 Event code 53 (ABS_MT_POSITION_X) Value 0 Min 1298 Max 5692 Resolution 49 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min 1150 Max 4854 Resolution 90 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event code 58 (ABS_MT_PRESSURE) Value 0 Min0 Max 255 Properties: Property type 0 (INPUT_PROP_POINTER) Testing ... (interrupt to exit) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1500504 Title: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ FJ Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: CurrentDesktop: Unity Date: Tue Sep 29 01:23:48 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: FUJITSU FMVS90TB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias:
[Desktop-packages] [Bug 1500504] [NEW] [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all
Public bug reported: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ FJ Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: CurrentDesktop: Unity Date: Tue Sep 29 01:23:48 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: FUJITSU FMVS90TB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB285 dmi.board.vendor: FUJITSU dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd12/25/2014:svnFUJITSU:pnFMVS90TB:pvr:rvnFUJITSU:rnFJNB285:rvrA3:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS90TB dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Sep 29 00:39:08 2015 xserver.configfile: default xserver.errors: Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm Error loading keymap /var/lib/xkb/server-ED9090187DB169A1C122BC910C79F5FB9768C61F.xkm xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5138 vendor SHP xserver.version: 2:1.17.2-1ubuntu7 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1500504 Title: [FUJITSU FMVS90TB] SynPS/2 Synaptics TouchPad detected, but not working at all Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: SynPS/2 Synaptics TouchPad is detected, but not working at all. I disabled touchscreen from BIOS level, but still no luck. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=9[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=6[slave keyboard (3)] ↳ Video Bus
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495851] Re: Can't seem to make USB microphone the preferred input
I had a similar frustration when I used a USB headset. I put the content below as a workaround. [~/.config/pulse/default.pa] #!/usr/bin/pulseaudio -nF .include /etc/pulse/default.pa ## Whenever a new sink or source appears, this module will switch the ## default sink/source to be the new sink/source load-module module-switch-on-connect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1495851 Title: Can't seem to make USB microphone the preferred input Status in gnome-control-center package in Ubuntu: New Bug description: My laptop has a built-in audio port that accepts a three-channel ⅛” plug for a stereo+microphone headset. Unfortunately due to the nature of the beast, there is rather a lot of cross-talk, and the electronics in the laptop are not the best. Also the DSP inside the laptop is surrounded by sources of magnetic interference such as the fans, power supply, WiFi antenna, etc. When I plug in my nice USB microphone, I always have to go into the sound settings tool and hunt over to the input tab and select it from the listing in order to get audio through it. It's lucky that I know how to do this, as some folks would simply plug it in, test it, and decide that it doesn't work! While I would argue that USB audio devices should be preferred over built-in laptop chips, I am most frustrated by the lack of ability for me to even say "From now on prefer this specific audio device for input, whenever it is present". I want to make my USB microphone Just Work without all the clicking about! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-control-center (not installed) ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 15 09:09:22 2015 InstallationDate: Installed on 2014-05-29 (473 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to vivid on 2015-05-05 (132 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1495851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1475949] Re: Port to relocated peripheral settings
I'm not sure it is caused by this change, but I've opened LP: #1489730 as one finger tap no longer enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1475949 Title: Port to relocated peripheral settings Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Most Peripheral settings were moved into gsetings-desktop-schemas for 3.16, since they are now shared with mutter which handles peripheral configuration for the wayland/libinput cases. For x11 g-s-d still handles most of these settings. The migration code in g-s-d 3.16 makes it not possible to just revert the changes to the schemas, so this cherry-pick's from upstream the bits required for u-s-d/u-c-c to use the new keys and also handling migration of the settings. Upstream removed handling of keyboard repeat settings from g-s-d, however I have kept this and just pointed u-s-d at the new keys in gsettings-desktop-schemas. The new settings aren't entirely a 1:1 mapping to the old setting, however the only user facing change, is that touchpad disable while typing setting is removed and this is always enabled now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1475949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1489730] [NEW] after upgrading, one finger tap no longer works
Public bug reported: 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) ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1489730 Title: after upgrading, one finger tap no longer works Status in unity-settings-daemon 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/unity-settings-daemon/+bug/1489730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1489730] Re: after upgrading, one finger tap no longer works
@Tim, default setting has always been off. I can activate it by synclient, but just after login it's always off. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1489730 Title: after upgrading, one finger tap no longer works Status in unity-settings-daemon 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/unity-settings-daemon/+bug/1489730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to language-selector 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-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 Desktop Packages, which is subscribed to language-selector 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1468105] Re: Use fcitx-mozc as default ja_JP input method
FWIW, tegaki and zinnia are not moving strongly, but are maintained on some level. https://github.com/tegaki/tegaki/commits/master https://github.com/taku910/zinnia/commits/master -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1468105 Title: Use fcitx-mozc as default ja_JP input method Status in language-selector package in Ubuntu: New Status in mozc package in Ubuntu: New Bug description: As discussed in bug #1439006, we would like to use fcitx-mozc as default ja_JP input method, replacing the dated anthy back-end. This would need to be conducted in the following steps: 1. Strip src:mozc's dependency, by dropping uim and possibly zinnia/tegaki support. 2. MIR for the stripped version of mozc. 3. Switch to fcitx-anthy in language-selector, and demote anthy related packages to universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1468105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1439006] Re: Install Fcitx for Japanese users
Personally I don't think gyp would cause a lot trouble and the main problem would be the dependency to framework libraries. Would it be possible to split the package into two sources or something like that so we are able build only ibus/fcitx support from a source that's OK to MIR? I don't think we want to MIR all of the frameworks. Just dropping uim support in Ubuntu by dropping d/p/uim-mozc.patch and build-depends:libuim-dev is a good option, IMO. I tried it a few months ago[1] and found it was useful to keep a diff from Debian minimal. [1] http://bazaar.launchpad.net/~nobuto/ubuntu/vivid/mozc/mir/revision/44 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1439006 Title: Install Fcitx for Japanese users Status in im-config package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Bug description: According to my proposal [1], Fcitx should be default for Japanese uses on Vivid release cycle. https://lists.ubuntu.com/archives/ubuntu-desktop/2015-March/004645.html Ref: https://bugs.launchpad.net/ubuntu/+source/language- selector/+bug/1430893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1439006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1439006] Re: Install Fcitx for Japanese users
@Aron, I'm not sure about the future including Desktop Next or convergence, however I believe it's still worthy to have Mozc as default for the time being. The engine itself is well maintained by Google team as Mozc/Google Japanese Input(It's like a Chromium/Chrome relation) in upstream, and popular on Windows, Linux and Android with no doubt. Up until now, we didn't bring Mozc to MIR because it has a wide dependencies. Now that fcitx is in main, a big remaining depedency is gyp. It would be great if Desktop team is positive to maintain it. @Ikuya, your input is more than welcome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1439006 Title: Install Fcitx for Japanese users Status in im-config package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Bug description: According to my proposal [1], Fcitx should be default for Japanese uses on Vivid release cycle. https://lists.ubuntu.com/archives/ubuntu-desktop/2015-March/004645.html Ref: https://bugs.launchpad.net/ubuntu/+source/language- selector/+bug/1430893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1439006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale
** Changed in: ubuntu-translations Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should return Mincho(serif) font in ja locale Status in Ubuntu Translations: Fix Released Status in fonts-takao package in Ubuntu: Fix Released Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232801] Re: same msgid in multiple context, network established and infiniband mode
connection established context was changed from Connected to Connection Established by the commit below. This issue no longer exists. revno: 445 committer: Mathieu Trudel-Lapierre mathieu...@ubuntu.com branch nick: network-manager-applet timestamp: Mon 2015-01-26 20:15:32 -0500 message: * New upstream release: 0.9.10.1. * Resync packaging with Debian: - debian/rules: Set DEB_HOST_MULTIARCH, use dh_install exclusions rather than removing .la and .a files separately. - debian/control: Build-depends: update NM b-deps, drop docbook-to-man, bump to dh 9, update libgtk/libglib2.0 b-deps versions and make libnm-gtk Multi-Arch-aware. - debian/*.install: update paths for multi-arch. - debian/compat: bump to compat level 9. * debian/patches dropped because they were applied upstream: - git_use_paths_in_vpn_name_files_4867951.patch, - git_revert_system_ca_cert.patch, - lp289466_always_show_tray_icon.patch, - key-certificate-extensions.patch, - lp829673_gconf_hide_applet.patch, - 0001_Move_on_with_enter_in_the_country_page_of_the_new_mobile_wizard.patch * debian/patches/lp328572-dxteam-connect-text.patch, debian/patches/lp330571_dxteam_wired_connect_text.patch, debian/patches/lp330608_dxteam_gsm_connect_text.patch: stop carrying needless string changes causing delta with upstream; any changes to the strings should happen there so we stay in sync. dropped; included upstream. * Refreshed remaining patches. ** Changed in: ubuntu-translations Status: Triaged = Invalid ** Changed in: network-manager-applet (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1232801 Title: same msgid in multiple context, network established and infiniband mode Status in Ubuntu Translations: Invalid Status in network-manager-applet package in Ubuntu: Invalid Bug description: network-manager-applet 0.9.8.0-1ubuntu3 There are translatable string Connected in multiple contexts in the source code. One context is connection established. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849418/+files/connection-established_context.png Another is Infiniband mode. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849424/+files/infiniband_context.png It's hard to cover two context in one translation. GNOME master is not affected, Connected is used only in infiniband context. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1232801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1447022] Re: CubebUtils from firefox is registered as volume 0, no sound for YouTube html5 videos
full output of `pactl list` during playing a video. ** Attachment added: pactl_list.txt https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1447022/+attachment/4381143/+files/pactl_list.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1447022 Title: CubebUtils from firefox is registered as volume 0, no sound for YouTube html5 videos Status in firefox package in Ubuntu: New Bug description: When playing YouTube html5 videos, no sound output. It turns out that CubebUtils from Firefox registers a sink to pulseaudio as volume 0 (no sound). $ pactl list snip Sink Input #25 Driver: protocol-native.c Owner Module: 10 Client: 72 Sink: 0 Sample Specification: float32le 2ch 44100Hz Channel Map: front-left,front-right Format: pcm, format.sample_format = \float32le\ format.rate = 44100 format.channels = 2 format.channel_map = \front-left,front-right\ Corked: no Mute: no Volume: front-left: 0 / 0% / -inf dB, front-right: 0 / 0% / -inf dB balance 0.00 Buffer Latency: 10 usec Sink Latency: 45223 usec Resample method: copy Properties: media.name = AudioStream application.name = CubebUtils native-protocol.peer = UNIX socket client native-protocol.version = 30 application.process.id = 6482 application.process.user = nobuto application.process.host = lifebook application.process.binary = firefox window.x11.display = :0 application.language = en_US.UTF-8 application.process.machine_id = a67563f873c74c5af38cfebd54f1e51b application.process.session_id = c2 application.icon_name = firefox module-stream-restore.id = sink-input-by-application-name:CubebUtils ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: firefox 37.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: nobuto 4198 F...m pulseaudio /dev/snd/controlC0: nobuto 4198 F pulseaudio BuildID: 20150328222441 Channel: Unavailable CurrentDesktop: Unity Date: Wed Apr 22 17:42:41 2015 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-02-28 (52 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) Locales: extensions.sqlite corrupt or missing Plugins: Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) PrefSources: prefs.js user.js [Profile]/extensions/e...@alc.co.jp/defaults/preferences/eow-prefs.js [Profile]/extensions/keysn...@mooz.github.com/defaults/preferences/keysnail-prefs.js Profiles: Profile0 (Default) - LastVersion=37.0/20150328222441 (In use) RelatedPackageVersions: google-talkplugin 5.40.2.0-1 rhythmbox-mozilla 3.1-1ubuntu3 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB24F dmi.board.vendor: FUJITSU dmi.board.version: D2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS54KR dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1447022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1447022] [NEW] CubebUtils from firefox is registered as volume 0, no sound for YouTube html5 videos
Public bug reported: When playing YouTube html5 videos, no sound output. It turns out that CubebUtils from Firefox registers a sink to pulseaudio as volume 0 (no sound). $ pactl list snip Sink Input #25 Driver: protocol-native.c Owner Module: 10 Client: 72 Sink: 0 Sample Specification: float32le 2ch 44100Hz Channel Map: front-left,front-right Format: pcm, format.sample_format = \float32le\ format.rate = 44100 format.channels = 2 format.channel_map = \front-left,front-right\ Corked: no Mute: no Volume: front-left: 0 / 0% / -inf dB, front-right: 0 / 0% / -inf dB balance 0.00 Buffer Latency: 10 usec Sink Latency: 45223 usec Resample method: copy Properties: media.name = AudioStream application.name = CubebUtils native-protocol.peer = UNIX socket client native-protocol.version = 30 application.process.id = 6482 application.process.user = nobuto application.process.host = lifebook application.process.binary = firefox window.x11.display = :0 application.language = en_US.UTF-8 application.process.machine_id = a67563f873c74c5af38cfebd54f1e51b application.process.session_id = c2 application.icon_name = firefox module-stream-restore.id = sink-input-by-application-name:CubebUtils ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: firefox 37.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: nobuto 4198 F...m pulseaudio /dev/snd/controlC0: nobuto 4198 F pulseaudio BuildID: 20150328222441 Channel: Unavailable CurrentDesktop: Unity Date: Wed Apr 22 17:42:41 2015 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-02-28 (52 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) Locales: extensions.sqlite corrupt or missing Plugins: Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) PrefSources: prefs.js user.js [Profile]/extensions/e...@alc.co.jp/defaults/preferences/eow-prefs.js [Profile]/extensions/keysn...@mooz.github.com/defaults/preferences/keysnail-prefs.js Profiles: Profile0 (Default) - LastVersion=37.0/20150328222441 (In use) RelatedPackageVersions: google-talkplugin 5.40.2.0-1 rhythmbox-mozilla 3.1-1ubuntu3 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB24F dmi.board.vendor: FUJITSU dmi.board.version: D2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS54KR dmi.sys.vendor: FUJITSU ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1447022 Title: CubebUtils from firefox is registered as volume 0, no sound for YouTube html5 videos Status in firefox package in Ubuntu: New Bug description: When playing YouTube html5 videos, no sound output. It turns out that CubebUtils from Firefox registers a sink to pulseaudio as volume 0 (no sound). $ pactl list snip Sink Input #25 Driver: protocol-native.c Owner Module: 10 Client: 72 Sink: 0 Sample Specification: float32le 2ch 44100Hz Channel Map: front-left,front-right Format: pcm, format.sample_format = \float32le\ format.rate = 44100 format.channels = 2 format.channel_map = \front-left,front-right\ Corked: no Mute: no Volume: front-left: 0 / 0% / -inf dB, front-right: 0 / 0% / -inf dB balance 0.00 Buffer Latency: 10 usec Sink
[Desktop-packages] [Bug 1447022] Re: CubebUtils from firefox is registered as volume 0, no sound for YouTube html5 videos
Please disregard. My profile remembered mute settings per site. No problem in Private Window. ** Changed in: firefox (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1447022 Title: CubebUtils from firefox is registered as volume 0, no sound for YouTube html5 videos Status in firefox package in Ubuntu: Invalid Bug description: When playing YouTube html5 videos, no sound output. It turns out that CubebUtils from Firefox registers a sink to pulseaudio as volume 0 (no sound). $ pactl list snip Sink Input #25 Driver: protocol-native.c Owner Module: 10 Client: 72 Sink: 0 Sample Specification: float32le 2ch 44100Hz Channel Map: front-left,front-right Format: pcm, format.sample_format = \float32le\ format.rate = 44100 format.channels = 2 format.channel_map = \front-left,front-right\ Corked: no Mute: no Volume: front-left: 0 / 0% / -inf dB, front-right: 0 / 0% / -inf dB balance 0.00 Buffer Latency: 10 usec Sink Latency: 45223 usec Resample method: copy Properties: media.name = AudioStream application.name = CubebUtils native-protocol.peer = UNIX socket client native-protocol.version = 30 application.process.id = 6482 application.process.user = nobuto application.process.host = lifebook application.process.binary = firefox window.x11.display = :0 application.language = en_US.UTF-8 application.process.machine_id = a67563f873c74c5af38cfebd54f1e51b application.process.session_id = c2 application.icon_name = firefox module-stream-restore.id = sink-input-by-application-name:CubebUtils ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: firefox 37.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: nobuto 4198 F...m pulseaudio /dev/snd/controlC0: nobuto 4198 F pulseaudio BuildID: 20150328222441 Channel: Unavailable CurrentDesktop: Unity Date: Wed Apr 22 17:42:41 2015 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-02-28 (52 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) Locales: extensions.sqlite corrupt or missing Plugins: Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) PrefSources: prefs.js user.js [Profile]/extensions/e...@alc.co.jp/defaults/preferences/eow-prefs.js [Profile]/extensions/keysn...@mooz.github.com/defaults/preferences/keysnail-prefs.js Profiles: Profile0 (Default) - LastVersion=37.0/20150328222441 (In use) RelatedPackageVersions: google-talkplugin 5.40.2.0-1 rhythmbox-mozilla 3.1-1ubuntu3 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB24F dmi.board.vendor: FUJITSU dmi.board.version: D2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS54KR dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1447022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to language-selector 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to language-selector 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431862] [NEW] im-config hangs if LC_CTYPE does not have quotes
Public bug reported:
If LC_CTYPE does not have any quotes, regex does not hit, then im-config
hangs at the point below.
/usr/share/im-config/xinputrc.common
92 IM_CONFIG_LC_CTYPE=$(locale | sed -nr
's/LC_CTYPE=\([a-zA-Z_]*).*\/\1/p')
93 IM_CONFIG_SCRIPT=$(grep $IM_CONFIG_LC_CTYPE $IM_CONFIG_LC_PREFS
| grep -v '^#' | awk '{print $2}')
$ cat ~/.pam_environment
LC_CTYPE=ja_JP.UTF-8
LC_PAPER=ja_JP.UTF-8
LC_MEASUREMENT=ja_JP.UTF-8
PAPERSIZE=a4
$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE=ja_JP.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=ja_JP.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=ja_JP.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
$ bash -x /usr/bin/im-config
+ . /usr/share/im-config/xinputrc.common
++ IM_CONFIG_VERSION=0.27-1ubuntu3
++ IM_CONFIG_DATA=/usr/share/im-config/data
++ IM_CONFIG_LC_PREFS=/usr/share/im-config/locale_prefs.conf
++ IM_CONFIG_XINPUTRC_USR=/home/nobuto/.xinputrc
++ IM_CONFIG_XINPUTRC_SYS=/etc/X11/xinit/xinputrc
++ IM_CONFIG_DEFAULT=/etc/default/im-config
++ . gettext.sh
+++ test 'X\t' = 'X\t'
+++ echo=echo
+++ test -z ''
+++ case $0 in
++ TEXTDOMAIN=im-config
++ export TEXTDOMAIN
++ TEXTDOMAINDIR=/usr/share/locale/
++ export TEXTDOMAINDIR
++ '[' -r /etc/default/im-config ']'
++ . /etc/default/im-config
+++ IM_CONFIG_DEFAULT_MODE=auto
++ id -u
+ '[' 1000 = 0 ']'
+ IM_CONFIG_XINPUTRC=/home/nobuto/.xinputrc
++ gettext 'user configuration'
+ IM_CONFIG_XINPUTRC_TYPE='user configuration'
++ automatic_im
++ '[' -r /usr/share/im-config/locale_prefs.conf ']'
+++ locale
+++ sed -nr 's/LC_CTYPE=\([a-zA-Z_]*).*\/\1/p'
++ IM_CONFIG_LC_CTYPE=
+++ grep /usr/share/im-config/locale_prefs.conf
+++ awk '{print $2}'
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: im-config 0.27-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 13 22:26:12 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-02-28 (12 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
PackageArchitecture: all
SourcePackage: im-config
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: im-config (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug vivid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1431862
Title:
im-config hangs if LC_CTYPE does not have quotes
Status in im-config package in Ubuntu:
New
Bug description:
If LC_CTYPE does not have any quotes, regex does not hit, then im-
config hangs at the point below.
/usr/share/im-config/xinputrc.common
92 IM_CONFIG_LC_CTYPE=$(locale | sed -nr
's/LC_CTYPE=\([a-zA-Z_]*).*\/\1/p')
93 IM_CONFIG_SCRIPT=$(grep $IM_CONFIG_LC_CTYPE
$IM_CONFIG_LC_PREFS | grep -v '^#' | awk '{print $2}')
$ cat ~/.pam_environment
LC_CTYPE=ja_JP.UTF-8
LC_PAPER=ja_JP.UTF-8
LC_MEASUREMENT=ja_JP.UTF-8
PAPERSIZE=a4
$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE=ja_JP.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=ja_JP.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=ja_JP.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
$ bash -x /usr/bin/im-config
+ . /usr/share/im-config/xinputrc.common
++ IM_CONFIG_VERSION=0.27-1ubuntu3
++ IM_CONFIG_DATA=/usr/share/im-config/data
++ IM_CONFIG_LC_PREFS=/usr/share/im-config/locale_prefs.conf
++ IM_CONFIG_XINPUTRC_USR=/home/nobuto/.xinputrc
++ IM_CONFIG_XINPUTRC_SYS=/etc/X11/xinit/xinputrc
++ IM_CONFIG_DEFAULT=/etc/default/im-config
++ . gettext.sh
+++ test 'X\t' = 'X\t'
+++ echo=echo
+++ test -z ''
+++ case $0 in
++ TEXTDOMAIN=im-config
++ export TEXTDOMAIN
++ TEXTDOMAINDIR=/usr/share/locale/
++ export TEXTDOMAINDIR
++ '[' -r /etc/default/im-config ']'
++ . /etc/default/im-config
+++ IM_CONFIG_DEFAULT_MODE=auto
++ id -u
+ '[' 1000 = 0 ']'
+ IM_CONFIG_XINPUTRC=/home/nobuto/.xinputrc
++ gettext 'user configuration'
+ IM_CONFIG_XINPUTRC_TYPE='user configuration'
++ automatic_im
++ '[' -r /usr/share/im-config/locale_prefs.conf ']'
+++ locale
+++ sed -nr 's/LC_CTYPE=\([a-zA-Z_]*).*\/\1/p'
++ IM_CONFIG_LC_CTYPE=
+++ grep /usr/share/im-config/locale_prefs.conf
+++ awk '{print $2}'
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: im-config 0.27-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 13 22:26:12 2015
EcryptfsInUse: Yes
InstallationDate:
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should hit Mincho(serif) font
The PDF document above is a template of tax declaration paper from Japanese National Tax Agency. It specifies both Ryumin(serif) and Gothic-BBB(sans-serif), but Evince uses one sans-serif font TakaoPGothic to substitute both. ** Attachment added: GothicBBB_Ryumin.png https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/4339988/+files/GothicBBB_Ryumin.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should hit Mincho(serif) font Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] [NEW] fc-match Ryumin should hit Mincho(serif) font
Public bug reported: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts- takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-takao (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should hit Mincho(serif) font Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should hit Mincho(serif) font
Example PDF document. ** Attachment added: h26syotoku.pdf https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/4339987/+files/h26syotoku.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should hit Mincho(serif) font Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale
@Rolf, As you may know, I usually remain with the LTS releases and only run the development release from time to time. As such, I hope the fix for this ticket will be backported to trusty as well. If this fix lands into vivid successfully and no regression reported in vivid, we can consider to backport it to trusty as well. However I'm under the impression that this Ryumin thing is not so critical. Furthermore, my system is mainly English-based. I hope you won't mind me adding my own experiences here. I can basically confirm your findings, except that my US-locale returns a different font. $ env LC_ALL=en_US.UTF-8 fc-match Ryumin ipamp.ttf: IPAPMincho Regular $ env LC_ALL=ja_JP.UTF-8 fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular My patch fixes this behavior, the result for Ryumin will be always the same in all locales. I tried the test PDF in different viewers and noticed there were some alignment issues in the viewer built into Firefox (please refer to my screenshot). I suspect that is another, separate issue? Yes, that's separate issue in Mozilla's pdf.js I think. The PDF I attached is rather complicated, I think it's natural rendering is broken in some viewers. One of the things I sometimes notice is that Chinese at times seems to have precedence over Japanese. For someone like me, that is unfortunate. Are you aware of a list of known issues or some website to check if one's configuration has any errors? This area of Ubuntu seems to change from release to release so it is hard to keep up (with a lot of improvement being made, at least that has been my experience). I do not know as much as you do, so at best, I will notice the effects but I would be utterly unable to dig into the causes. That's why your work is so much appreciated. You titled the ticket fc-match Ryumin should return Mincho(serif) font in ja locale. That name is so obviously Japanese that I wonder why the returned value should be locale-specific. From the superficial information I have it seems that optimizations for Japanese are sometimes only made only for Japanese locale, leaving people like me who only display and write Japanese in a non-Japanese locale out in the rain. I understand that sometimes this might have to do with political sensitivities and the power of numbers. Nowadays Ubuntu switches font substitutions by locales. For example, `fc-match serif` returns DejaVu Serif for most locales, TakaoPMincho for ja locale. You can specify per-user font locale settings(actually it's LC_CTYPE) in ~/.pam_environment or ~/.profile. https://help.ubuntu.com/community/EnvironmentVariables#Session-wide_environment_variables Can you please put LC_CTYPE=ja_JP.UTF-8 in your ~/.pam_environment, re-login and see how it works? ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should return Mincho(serif) font in ja locale Status in Ubuntu Translations: New Status in fonts-takao package in Ubuntu: Confirmed Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale
lp:ubuntu/fonts-takao seems out-of-date unfortunately. I'm attaching debdiff instead. ** Patch added: fonts-takao_vivid.debdiff https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+attachment/4340222/+files/fonts-takao_vivid.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should return Mincho(serif) font in ja locale Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale
I don't think it causes any side effects for other locale. Because all binding=strong are guarded by ja locale or ja specific font. But to be safe, adding CJK testers as subscriber to notify this change beforehand. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should return Mincho(serif) font in ja locale Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale
** Changed in: fonts-takao (Ubuntu) Assignee: (unassigned) = Nobuto Murata (nobuto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should return Mincho(serif) font in ja locale Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should return Mincho(serif) font in ja locale
I cannot see any visual change in the test file in evince, though. I will have to admit I would not be good at spotting any difference, though. What words should now display in the more brush-like Mincho font? Right. I thought Ryumin was used in the doc more often, but it wasn't. We need to prepare more proper sample doc if we try SRU ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should return Mincho(serif) font in ja locale Status in Ubuntu Translations: New Status in fonts-takao package in Ubuntu: Confirmed Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should hit Mincho(serif) font
hm, it happens only with Japanese locale. $ env LC_ALL=en_US.UTF-8 fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular $ env LC_ALL=ja_JP.UTF-8 fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should hit Mincho(serif) font Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430339] Re: fc-match Ryumin should hit Mincho(serif) font
ok, it turned out that 65-fonts-takao-pgothic.conf is too strong. We need to figure out good balance between 65-fonts-takao-pgothic.conf and 65-fonts-takao-mincho.conf to return the correct substituted font for Ryumin in ja locale. ** Summary changed: - fc-match Ryumin should hit Mincho(serif) font + fc-match Ryumin should return Mincho(serif) font in ja locale -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-takao in Ubuntu. https://bugs.launchpad.net/bugs/1430339 Title: fc-match Ryumin should return Mincho(serif) font in ja locale Status in fonts-takao package in Ubuntu: New Bug description: Ryumin and Gothic-BBB are generic font names for serif/sans-serif like Arial/Times new roman. fonts-takao-mincho has a rule[1] to offer substitute for Ryumin, however `fc-match Ryumin` does not return fonts-takao-mincho(serif), it returns fonts-takao-gothic(sans-serif) instead. Expected result: $ fc-match Ryumin fonts-japanese-mincho.ttf: TakaoPMincho Regular Actual result: $ fc-match Ryumin fonts-japanese-gothic.ttf: Takao Pゴシック Regular [1] /etc/fonts/conf.d/65-fonts-takao-mincho.conf 21 match target=pattern 22 test qual=any name=family 23 stringRyumin/string 24 /test 25 edit name=family mode=prepend 26 stringTakao P明朝/string 27 /edit 28 /match ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fonts-takao-mincho 003.02.01-9ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 22:41:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228) PackageArchitecture: all SourcePackage: fonts-takao UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-takao/+bug/1430339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425510] Re: Default IM configuration causes hangs
@Cefn, I'm curious you have installed ibus-gtk and ibus-gtk3 or not. Because you installed gtk2 app(e.g. inkscape) on Lubuntu. FWIW, Ubuntu has dependency to ibus-gtk and ibus-gtk3 by default because it's has gtk2 and gtk3 apps in the image. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1425510 Title: Default IM configuration causes hangs Status in im-config package in Ubuntu: Invalid Bug description: Certain applications have associated input hangs, where no key input events can be sent which sometimes clear after some time, and in at least one case (Inkscape), this is eliminated by running from Start-Run as follows, hence overriding the declaration of GTK_IM_MODULE in /etc/X11/Xsession.d/70im-config_launch , distributed in im-config... bash -c unset GTK_IM_MODULE inkscape A permanent fix on my machine could be to modify the 70im- config_launch file, or declare an overriding export in some later .rc file. Anyone know where I should make this declaration if not modifying package-maintained files? An alternative solution could be to install scim-gtk-immodule and run... bash -c export GTK_IM_MODULE=scim inkscape See also https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1385009 Similar behaviours are experienced with Kupfer - minutes of hang with apparently no input events being passed, followed by (sometimes) unfreezing. I'm running Lubuntu Utopic with LXDE and Compiz (minimal dependencies on GTK), so it's feasible that some component is not properly declared in a dependent package. I can't find whether there is in fact a xim module available and running anywhere on my system. How can I check? Other input issues relating to out-of-order key event delivery to Chrome-based applications are experienced on the same build, but I think this may be an independent bug, ostensibly resolved by declaring IBUS_SYNC_MODE=1 https://code.google.com/p/chromium/issues/detail?id=456766 but thought I should mention as it's kind of in the same subsystem and may be linked. I speculate that there is some missing dependency or bad configuration in the default presentation of IM capabilities, which eventually causes a DBUS timeout or similar, eventually causing a fallback without any international input, but which is functional. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: im-config 0.26-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 Date: Wed Feb 25 12:26:26 2015 InstallationDate: Installed on 2015-01-01 (54 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1425510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1385009] Re: Hangs up on text edit
Hi, can you still reproduce the hang up after installing ibus-gtk package and re-login? I'm curious it's related to bug 1377370 or not. ** Changed in: inkscape (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1385009 Title: Hangs up on text edit Status in Inkscape: A Vector Drawing Tool: New Status in inkscape package in Ubuntu: Incomplete Bug description: Inkscape window became not responding when I edited an simple text element in simple svg. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: inkscape 0.48.5-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 24 11:24:51 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2014-09-17 (36 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140916) SourcePackage: inkscape UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1385009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to eog 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to eog 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%
** Also affects: eog via https://bugzilla.gnome.org/show_bug.cgi?id=733290 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: Unknown Status in “eog” 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%
I can't reproduce the issue with High Contrast theme. Adding light- themes task here. ** Also affects: light-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: Unknown Status in “eog” package in Ubuntu: Confirmed Status in “light-themes” package in Ubuntu: New 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334918] [NEW] selecting a window in scale by mouse click unexpectedly opens the link underneath the pointer
Public bug reported: When select a window in scale mode, the link underneath the mouse pointer will be automatically opened. How to reproduce: 1. open the PDF (doc_with_url.pdf) with Evince https://launchpadlibrarian.net/178628332/doc_with_url.pdf 2. close other windows 3. press Super + W to trigger scale mode 4. select the window of Evince by mouse click 5. repeat 3. - 4. multiple times Expected result: There is only one window of evince. Actual result: Web browser will be opened and it has multiple tab of http://launchpad.net/;. This behavior is observed at least with Evince and Pidgin. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 27 10:10:48 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-19 (38 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1334918 Title: selecting a window in scale by mouse click unexpectedly opens the link underneath the pointer Status in “unity” package in Ubuntu: New Bug description: When select a window in scale mode, the link underneath the mouse pointer will be automatically opened. How to reproduce: 1. open the PDF (doc_with_url.pdf) with Evince https://launchpadlibrarian.net/178628332/doc_with_url.pdf 2. close other windows 3. press Super + W to trigger scale mode 4. select the window of Evince by mouse click 5. repeat 3. - 4. multiple times Expected result: There is only one window of evince. Actual result: Web browser will be opened and it has multiple tab of http://launchpad.net/;. This behavior is observed at least with Evince and Pidgin. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 27 10:10:48 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-19 (38 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1334918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1323478] Re: ibus input Chinese word in webapp, words were duplicated
Hi, the new package of im-config just enables ibus in QT5 apps in this case. You saw this issue only in combination of ibus and pinyin, I will mark this affects ibus-pinyin not im-config for now. ** Package changed: webbrowser-app (Ubuntu) = ibus-pinyin (Ubuntu) ** Changed in: im-config (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1323478 Title: ibus input Chinese word in webapp, words were duplicated Status in “ibus-pinyin” package in Ubuntu: New Status in “im-config” package in Ubuntu: Invalid Bug description: I just update im-config to ver. 0.24-1ubuntu4.1, so I can input Chinese word in webapp now, like Amazon webapp client (previous version not support ) But, when I input Chinese word via ibus pinyin method, words were duplicated. I always got double what I typed. For example, input '好', show '好好', input '你好', show '你好你好'. I think this is new issue for this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-pinyin/+bug/1323478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
Thank you, Scott. ** Changed in: im-config (Ubuntu Trusty) Status: Fix Committed = Fix Released ** Changed in: ubuntu-translations Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: Fix Released Status in “im-config” package in Ubuntu: Fix Released Status in “im-config” source package in Trusty: Fix Released Status in “im-config” package in Debian: Fix Released Bug description: debdiff for utopic: https://launchpadlibrarian.net/173673054/im-config_utopic_v2.debdiff SRU debdiff for trusty: https://launchpadlibrarian.net/173673094/im-config_trusty-sru_v2.debdiff [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: allSourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
Something wrong in SRU process. Bug member field of im-config in the status page below is empty. http://people.canonical.com/~ubuntu-archive/pending-sru.html Anyway the proposed package seems accepted into trusty-proposed, setting the status accordingly. ** Changed in: im-config (Ubuntu Trusty) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: Fix Released Status in “im-config” source package in Trusty: Fix Committed Status in “im-config” package in Debian: Fix Released Bug description: debdiff for utopic: https://launchpadlibrarian.net/173673054/im-config_utopic_v2.debdiff SRU debdiff for trusty: https://launchpadlibrarian.net/173673094/im-config_trusty-sru_v2.debdiff [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: allSourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1206295] Re: VPN indicator hard to see with wired network icon
*** This bug is a duplicate of bug 823633 *** https://bugs.launchpad.net/bugs/823633 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #823633, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 823633 Wired VPN network connection icon needs to be fixed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1206295 Title: VPN indicator hard to see with wired network icon Status in “network-manager-applet” package in Ubuntu: New Bug description: When using a wired network, and using a VPN it is hard to see the little lock icon. It is much more visible with the wireless icon, since most of it is towards the top, and the lock is in the bottom corner. The wired network icon however mostly overlaps the lock, and they merge into one blob and it's hard to see the lock. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1206295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
** Patch added: im-config_utopic.debdiff https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1309885/+attachment/4095027/+files/im-config_utopic.debdiff ** Description changed: + debdiff for utopic: + https://launchpadlibrarian.net/173631365/im-config_utopic.debdiff + SRU debdiff for trusty: + https://launchpadlibrarian.net/173225716/im-config_trusty-sru.debdiff + [Impact] - * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. + * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] - 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. - 2. install and launch webbrowser-app - 3. confirm that you cannot enable IM inside webbrowser-app - 4. update im-config packages to -proposed one - 5. logout from desktop session and re-login - 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. + 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. + 2. install and launch webbrowser-app + 3. confirm that you cannot enable IM inside webbrowser-app + 4. update im-config packages to -proposed one + 5. logout from desktop session and re-login + 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] - * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, + * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 - -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? - ProblemType: Bug - DistroRelease: Ubuntu 14.04 + ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) - PackageArchitecture: all - SourcePackage: im-config + PackageArchitecture: allSourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: Confirmed Status in “im-config” package in Debian: New Bug description: debdiff for utopic: https://launchpadlibrarian.net/173631365/im-config_utopic.debdiff SRU debdiff for trusty: https://launchpadlibrarian.net/173225716/im-config_trusty-sru.debdiff [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
Now that Debian released a fix for this bug, let me tweak Ubuntu patch along with Debian. ** Changed in: im-config (Ubuntu) Status: Confirmed = In Progress ** Changed in: im-config (Ubuntu) Assignee: (unassigned) = Nobuto MURATA (nobuto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: In Progress Status in “im-config” package in Debian: New Bug description: debdiff for utopic: https://launchpadlibrarian.net/173631365/im-config_utopic.debdiff SRU debdiff for trusty: https://launchpadlibrarian.net/173225716/im-config_trusty-sru.debdiff [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: allSourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
** Patch added: im-config_trusty-sru_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1309885/+attachment/4095712/+files/im-config_trusty-sru_v2.debdiff ** Description changed: debdiff for utopic: - https://launchpadlibrarian.net/173631365/im-config_utopic.debdiff + https://launchpadlibrarian.net/173673054/im-config_utopic_v2.debdiff SRU debdiff for trusty: - https://launchpadlibrarian.net/173225716/im-config_trusty-sru.debdiff + https://launchpadlibrarian.net/173673094/im-config_trusty-sru_v2.debdiff [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: allSourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: im-config (Ubuntu) Status: In Progress = Confirmed ** Changed in: im-config (Ubuntu) Assignee: Nobuto MURATA (nobuto) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: Confirmed Status in “im-config” package in Debian: New Bug description: debdiff for utopic: https://launchpadlibrarian.net/173673054/im-config_utopic_v2.debdiff SRU debdiff for trusty: https://launchpadlibrarian.net/173673094/im-config_trusty-sru_v2.debdiff [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
** Patch removed: im-config_trusty-sru.debdiff https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1309885/+attachment/4088758/+files/im-config_trusty-sru.debdiff ** Patch removed: im-config_utopic.debdiff https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1309885/+attachment/4095027/+files/im-config_utopic.debdiff ** Patch added: im-config_utopic_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1309885/+attachment/4095711/+files/im-config_utopic_v2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: Confirmed Status in “im-config” package in Debian: New Bug description: debdiff for utopic: https://launchpadlibrarian.net/173673054/im-config_utopic_v2.debdiff SRU debdiff for trusty: https://launchpadlibrarian.net/173673094/im-config_trusty-sru_v2.debdiff [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: BugDistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: allSourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
** Description changed: - Cannot enable ibus or input Japanese text inside webapp-container. + [Impact] + + * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. + webapp-container, webbrowser-app, friends-app, etc. + + [Test Case] + 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. + 2. install and launch webbrowser-app + 3. confirm that you cannot enable IM inside webbrowser-app + 4. update im-config packages to -proposed one + 5. logout from desktop session and re-login + 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. + + [Regression Potential] + + * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, + both Qt5 and Qt4 app tests are preferred to make sure there is no + regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) + before attaching the patch. + + [Other Info] + related discussion is debian bug report. + http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 + + + -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: New Status in “im-config” package in Debian: New Bug description: [Impact] * Cannot input languages which need IM(ibus, fcitx) in Qt5 apps, e.g. webapp-container, webbrowser-app, friends-app, etc. [Test Case] 1. prepare ibus or fcitx environment with CJK(Chinese, Japanese, Korean) language, for example. 2. install and launch webbrowser-app 3. confirm that you cannot enable IM inside webbrowser-app 4. update im-config packages to -proposed one 5. logout from desktop session and re-login 6. confirm that now you can enable IM and input CJK language with ibus or fcitx. [Regression Potential] * This patch sets QT_IM_MODULE which might affect Qt4 app behaviour, both Qt5 and Qt4 app tests are preferred to make sure there is no regression for both sides. I used webbrowser-app(Qt5) and skype(Qt4) before attaching the patch. [Other Info] related discussion is debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- original description -- WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] [NEW] Cannot enable ibus inside webapp-container
Public bug reported: Cannot enable ibus or input Japanese text inside webapp-container. WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: im-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable ibus inside webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: New Bug description: Cannot enable ibus or input Japanese text inside webapp-container. WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable ibus inside webapp-container
An upstream debian bug is talking about setting QT_IM_MODULE for fcitx, but the idea is the same for fixing IM in QT5. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 ** Bug watch added: Debian Bug tracker #732396 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable ibus inside webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: New Bug description: Cannot enable ibus or input Japanese text inside webapp-container. WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable ibus inside webapp-container
** Also affects: im-config (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732396 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable ibus inside webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: New Status in “im-config” package in Debian: Unknown Bug description: Cannot enable ibus or input Japanese text inside webapp-container. WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309885] Re: Cannot enable IM inside Qt5 apps including webapp-container
** Summary changed: - Cannot enable ibus inside webapp-container + Cannot enable IM inside Qt5 apps including webapp-container ** Patch added: im-config_trusty-sru.debdiff https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+attachment/4088758/+files/im-config_trusty-sru.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1309885 Title: Cannot enable IM inside Qt5 apps including webapp-container Status in Ubuntu Translations: New Status in “im-config” package in Ubuntu: New Status in “im-config” package in Debian: Unknown Bug description: Cannot enable ibus or input Japanese text inside webapp-container. WORKAROUND: launch webapp-container with QT_IM_MODULE variable like the line below. $ env QT_IM_MODULE=ibus webapp-container --app-id=Gmailmailgooglecom --webapp=XX --enable-back-forward --store-session-cookies webapp-container looks like QT5 application, im-config needs to care about QT_IM_MODULE in addition to other *_IM_MODULE variables? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: im-config 0.24-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 17:23:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1309885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
Hi all, I have made a merge proposal to fix this bug hopefully in time for 14.04 release. https://code.launchpad.net/~nobuto/ubuntu/trusty/zenity/expandable-on-list-view/+merge/214387 If you want a fix for stable releases like 13.10(saucy), please follow the Stable Release Updates process described in: https://wiki.ubuntu.com/SRU Thanks, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in One Hundred Papercuts: Triaged Status in Zenity: Fix Released Status in “zenity” package in Ubuntu: Triaged Status in “zenity” package in Debian: Confirmed Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281215] Re: List box doesn't expand veritcally
*** This bug is a duplicate of bug 1296191 *** https://bugs.launchpad.net/bugs/1296191 ** This bug is no longer a duplicate of bug 1242886 Regression: List boxes do not properly resize when given height ** This bug has been marked a duplicate of bug 1296191 Winetricks gui is unreadable due to zenity height issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1281215 Title: List box doesn't expand veritcally Status in “zenity” package in Ubuntu: Confirmed Bug description: If I run `zenity --list --height=XXX [OTHER OPTIONS]` the list box will have a fixed height. Usually, this height is less than optimal and makes the list hard to read. This bug has been reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=702535 and there's a patch: https://git.gnome.org/browse/zenity/commit/?id=80bc8ce643979fec201c4ebd5cd6405b6310357f ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: zenity 3.8.0-1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.13.2-0ubuntu4 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 17 13:48:26 2014 InstallationDate: Installed on 2014-01-14 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140113) SourcePackage: zenity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1281215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1303106] Re: zenity --list has a window of 3 lines only
*** This bug is a duplicate of bug 1296191 *** https://bugs.launchpad.net/bugs/1296191 ** This bug is no longer a duplicate of bug 1242886 Regression: List boxes do not properly resize when given height ** This bug has been marked a duplicate of bug 1296191 Winetricks gui is unreadable due to zenity height issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1303106 Title: zenity --list has a window of 3 lines only Status in “zenity” package in Ubuntu: Confirmed Bug description: On xubuntu 14.04 (but others as the same problem on others flavours), a zenity box (zenity version 3.8.0) using zenity --list option only show a usable window of 2 or 3 lines. The rest of the zenity box is a very very thick border. for example, in a terminal, type : zenity --list --text=foo --radiolist --width=500 --height=630 --column=check --column=N° --column=side false 0 Gauche false 1 right false 2 bottom true 3 top No problem in former versions of ubuntu, only in Trusty Thar. The bug is also describe on gnome bugzilla : https://bugzilla.gnome.org/show_bug.cgi?id=702535. The correction seems very simple : Adding this line at line 1024 in /usr/share/zenity/zenity.ui seems to fix [the bug] : property name=expandTrue/property. The patch work perfectly on my PC. Edit : the bug existed on 13.10 and was patched https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1192101. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: zenity 3.8.0-1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 5 18:48:19 2014 InstallationDate: Installed on 2014-03-16 (20 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140315) SourcePackage: zenity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1303106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
*** This bug is a duplicate of bug 1296191 *** https://bugs.launchpad.net/bugs/1296191 Ah, unfortunately duplicate work happened. The fix has been released for another bug report. Marking a duplicate for it. ** This bug has been marked a duplicate of bug 1296191 Winetricks gui is unreadable due to zenity height issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in One Hundred Papercuts: Triaged Status in Zenity: Fix Released Status in “zenity” package in Ubuntu: Triaged Status in “zenity” package in Debian: Confirmed Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192101] Re: Fail to expand dialog box
*** This bug is a duplicate of bug 1296191 *** https://bugs.launchpad.net/bugs/1296191 ** This bug is no longer a duplicate of bug 1242886 Regression: List boxes do not properly resize when given height ** This bug has been marked a duplicate of bug 1296191 Winetricks gui is unreadable due to zenity height issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1192101 Title: Fail to expand dialog box Status in “zenity” package in Ubuntu: Confirmed Bug description: i only get a one line displayed into a very narrow scrolling box; for example when i want to choose something with winetricks. It seems not having any dconf settings by the way to fix that. The found workaround is to : - edit /usr/share/zenity/zenity.ui - and add on the line 1024 : property name=expandTrue/property After saving that tweak, winetricks dialog box display as expected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: zenity 3.8.0-1 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Tue Jun 18 11:29:58 2013 MarkForUpload: True SourcePackage: zenity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1192101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
** Changed in: zenity (Ubuntu) Status: Confirmed = In Progress ** Changed in: zenity (Ubuntu) Assignee: (unassigned) = Nobuto MURATA (nobuto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in Zenity: Fix Released Status in “zenity” package in Ubuntu: In Progress Status in “zenity” package in Debian: Confirmed Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
** Changed in: zenity (Ubuntu) Status: In Progress = Confirmed ** Changed in: zenity (Ubuntu) Assignee: Nobuto MURATA (nobuto) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in Zenity: Fix Released Status in “zenity” package in Ubuntu: Confirmed Status in “zenity” package in Debian: Confirmed Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1291302] [NEW] password never match since IM is on in unity lockscreen
Public bug reported: With a combination of ibus-mozc and unity, password never match until making IM off manually. How to reproduce: 1. set ibus-mozc as a default IM 2. lock screen with unity (Ctrl+Alt+L) 3. input your password to unlock screen Expected result: screen unlocked. Actual result: password never match until making IM off manually. ibus-mozc: Installed: 1.13.1651.102-2 Candidate: 1.13.1651.102-2 Version table: *** 1.13.1651.102-2 0 500 http://jp.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status unity: Installed: 7.1.2+14.04.20140311-0ubuntu1 Candidate: 7.1.2+14.04.20140311-0ubuntu1 Version table: *** 7.1.2+14.04.20140311-0ubuntu1 0 500 http://jp.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 05:58:23 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (148 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1291302 Title: password never match since IM is on in unity lockscreen Status in “unity” package in Ubuntu: New Bug description: With a combination of ibus-mozc and unity, password never match until making IM off manually. How to reproduce: 1. set ibus-mozc as a default IM 2. lock screen with unity (Ctrl+Alt+L) 3. input your password to unlock screen Expected result: screen unlocked. Actual result: password never match until making IM off manually. ibus-mozc: Installed: 1.13.1651.102-2 Candidate: 1.13.1651.102-2 Version table: *** 1.13.1651.102-2 0 500 http://jp.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status unity: Installed: 7.1.2+14.04.20140311-0ubuntu1 Candidate: 7.1.2+14.04.20140311-0ubuntu1 Version table: *** 7.1.2+14.04.20140311-0ubuntu1 0 500 http://jp.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 05:58:23 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-15 (148 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131014) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1291302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
** Bug watch added: Debian Bug tracker #739248 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739248 ** Also affects: zenity (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739248 Importance: Unknown Status: Unknown ** Bug watch added: GNOME Bug Tracker #702535 https://bugzilla.gnome.org/show_bug.cgi?id=702535 ** Also affects: zenity via https://bugzilla.gnome.org/show_bug.cgi?id=702535 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in Zenity: Unknown Status in “zenity” package in Ubuntu: Confirmed Status in “zenity” package in Debian: Unknown Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
** Attachment added: trusty-with-upstream-patch.png https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1242886/+attachment/3997346/+files/trusty-with-upstream-patch.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in Zenity: Fix Released Status in “zenity” package in Ubuntu: Confirmed Status in “zenity” package in Debian: Unknown Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281215] Re: List box doesn't expand veritcally
*** This bug is a duplicate of bug 1242886 *** https://bugs.launchpad.net/bugs/1242886 ** This bug has been marked a duplicate of bug 1242886 Regression: List boxes do not properly resize when given height -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1281215 Title: List box doesn't expand veritcally Status in “zenity” package in Ubuntu: Confirmed Bug description: If I run `zenity --list --height=XXX [OTHER OPTIONS]` the list box will have a fixed height. Usually, this height is less than optimal and makes the list hard to read. This bug has been reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=702535 and there's a patch: https://git.gnome.org/browse/zenity/commit/?id=80bc8ce643979fec201c4ebd5cd6405b6310357f ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: zenity 3.8.0-1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.13.2-0ubuntu4 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 17 13:48:26 2014 InstallationDate: Installed on 2014-01-14 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140113) SourcePackage: zenity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1281215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
** Attachment added: trusty.png https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1242886/+attachment/3997345/+files/trusty.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in Zenity: Fix Released Status in “zenity” package in Ubuntu: Confirmed Status in “zenity” package in Debian: Unknown Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242886] Re: Regression: List boxes do not properly resize when given height
As attached above, upstream commit fixes the issue. https://git.gnome.org/browse/zenity/commit/?id=80bc8ce643979fec201c4ebd5cd6405b6310357f -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given height Status in Zenity: Fix Released Status in “zenity” package in Ubuntu: Confirmed Status in “zenity” package in Debian: Unknown Bug description: In Zenity 3.8.0-1 (Saucy), list boxes are showing up strangely. I noticed this when using the 'repostory' tool (https://code.launchpad.net/~davidc3/+junk/repostory), but it's a repeatable zenity bug: When Zenity contains a list box and a specified height parameter, the window appears at the right height, but the list part expands as if no height were specified, only up to about 6 lines before adding a scrollbar. The following bash demonstrates the problem: #!/bin/bash for category in Alpha Beta Gamma Delta Epsilon Zeta Eta Theta Iota Kappa Lambda Mu;do echo $category for col in Purple Green Blue Pink Grey do echo entry done done | zenity --list --title Foobar --width 800 --height 500 --checklist --column Category --column Purple --column Green --column Blue --column Pink --column Grey To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1242886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192101] Re: Fail to expand dialog box
*** This bug is a duplicate of bug 1242886 *** https://bugs.launchpad.net/bugs/1242886 ** This bug has been marked a duplicate of bug 1242886 Regression: List boxes do not properly resize when given height -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1192101 Title: Fail to expand dialog box Status in “zenity” package in Ubuntu: Confirmed Bug description: i only get a one line displayed into a very narrow scrolling box; for example when i want to choose something with winetricks. It seems not having any dconf settings by the way to fix that. The found workaround is to : - edit /usr/share/zenity/zenity.ui - and add on the line 1024 : property name=expandTrue/property After saving that tweak, winetricks dialog box display as expected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: zenity 3.8.0-1 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Tue Jun 18 11:29:58 2013 MarkForUpload: True SourcePackage: zenity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1192101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 773098] Re: floating LibreOffice window cannot be docked to the main window under Compiz/Unity running
This issue is no longer reproducible with current trusty environment: libreoffice | 1:4.1.3-0ubuntu3 | http://jp.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages compiz | 1:0.9.10+13.10.20131011-0ubuntu1 | http://jp.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity | 7.1.2+14.04.20131106.1-0ubuntu1 | http://jp.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages That means now we can dock/undock floating windows like [Style and Formatting] with mouse operation. ** Changed in: compiz (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/773098 Title: floating LibreOffice window cannot be docked to the main window under Compiz/Unity running Status in Unity: Invalid Status in “compiz” package in Ubuntu: Invalid Status in “libreoffice” package in Ubuntu: Invalid Status in “openoffice.org” package in Ubuntu: Won't Fix Status in “unity” package in Ubuntu: Invalid Bug description: Binary package hint: libreoffice Under Compiz/Unity running, floating LibreOffice window like Styles and Formatting cannot be docked to the main window with mouse operation. How to reproduce: 1. open [Format]-[Style and Formatting] 2. move Styles and Formatting window to the right edge of the main window Expected: docked to the main window https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/773098/+attachment/2095366/+files/docked.png Happened instead: keep floating https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/773098/+attachment/2095368/+files/floating.png WORKAROUND: Press [Ctrl]+[Shift]+[F10] on the floating window. compiz: 1:0.9.4+bzr20110415-0ubuntu2 unity: 3.8.10-0ubuntu2 libreoffice: 1:3.3.2-1ubuntu4 ProblemType: BugDistroRelease: Ubuntu 11.04 Package: libreoffice-common 1:3.3.2-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Fri Apr 29 08:44:51 2011LiveMediaBuild: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=ja_JP:en LANG=ja_JP.UTF-8 SHELL=/bin/bashSourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/773098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232801] [NEW] same msgid in multiple context, network established and infiniband mode
Public bug reported: network-manager-applet 0.9.8.0-1ubuntu3 There are translatable string Connected in multiple contexts in the source code. One context is connection established. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849418/+files/connection-established_context.png Another is Infiniband mode. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849424/+files/infiniband_context.png It's hard to cover two context in one translation. GNOME master is not affected, Connected is used only in infiniband context. ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1232801 Title: same msgid in multiple context, network established and infiniband mode Status in Ubuntu Translations: New Status in “network-manager-applet” package in Ubuntu: New Bug description: network-manager-applet 0.9.8.0-1ubuntu3 There are translatable string Connected in multiple contexts in the source code. One context is connection established. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849418/+files/connection-established_context.png Another is Infiniband mode. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849424/+files/infiniband_context.png It's hard to cover two context in one translation. GNOME master is not affected, Connected is used only in infiniband context. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1232801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232801] Re: same msgid in multiple context, network established and infiniband mode
** Attachment added: infiniband_context.png https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849424/+files/infiniband_context.png ** Description changed: network-manager-applet 0.9.8.0-1ubuntu3 There are translatable string Connected in multiple contexts in the source code. One context is connection established. + https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849418/+files/connection-established_context.png Another is Infiniband mode. + https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849424/+files/infiniband_context.png It's hard to cover two context in one translation. + + GNOME master is not affected, Connected is used only in infiniband + context. ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1232801 Title: same msgid in multiple context, network established and infiniband mode Status in Ubuntu Translations: New Status in “network-manager-applet” package in Ubuntu: New Bug description: network-manager-applet 0.9.8.0-1ubuntu3 There are translatable string Connected in multiple contexts in the source code. One context is connection established. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849418/+files/connection-established_context.png Another is Infiniband mode. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849424/+files/infiniband_context.png It's hard to cover two context in one translation. GNOME master is not affected, Connected is used only in infiniband context. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1232801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232801] Re: same msgid in multiple context, network established and infiniband mode
** Attachment added: connection-established_context.png https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849418/+files/connection-established_context.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1232801 Title: same msgid in multiple context, network established and infiniband mode Status in Ubuntu Translations: New Status in “network-manager-applet” package in Ubuntu: New Bug description: network-manager-applet 0.9.8.0-1ubuntu3 There are translatable string Connected in multiple contexts in the source code. One context is connection established. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849418/+files/connection-established_context.png Another is Infiniband mode. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1232801/+attachment/3849424/+files/infiniband_context.png It's hard to cover two context in one translation. GNOME master is not affected, Connected is used only in infiniband context. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1232801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1231765] Re: [network]: gnome-control-center crashed with SIGSEGV in g_hash_table_remove_all()
attaching a valgrind log. ** Attachment added: valgrind.log https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1231765/+attachment/3844036/+files/valgrind.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1231765 Title: [network]: gnome-control-center crashed with SIGSEGV in g_hash_table_remove_all() Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu 12.04 LTS gnome-control-center: 1:3.4.2-0ubuntu0.12 network-manager: 0.9.4.0-0ubuntu4.3 How to reproduce: 1. open System Settings(gnome-control-center) 2. choose and open Network settings 3. press All settings to go back to System Settings(gnome-control-center) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1231765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
