[Touch-packages] [Bug 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
This is a problem even at the desktop level. With the gnome desktop font set to the default 'Ubuntu 11' if I use an app (gImageReader in my case, see also https://github.com/manisandro/gImageReader/issues/613) to write certain decomposed characters (e.g. \u0069\u0300), they are not properly combined on the screen. This is a bad user experience. I've switched to 'DejaVu Sans 11' as a workaround, as it seems to handle everything correctly so far. However, the related DejaVu Sans Mono Book still messes this up (e.g. in gnome-terminal and gedit), but on different combined characters. So for monospace needs I've found FreeMono to cover the most ground (pkg: fonts-freefont-ttf). Try this, while switching between the default gnome-terminal font (Ubuntu Mono?) and DejaVu Sans Mono Book: $ echo -e '\u0069\u0300\u0020\u0254\u0327' ì ɔ̧ The ì renders correctly while the open o + cedilla doesn't, both here and with the terminal font set to DejaVu Sans Mono Book, but if you switch to the default font in the terminal the open o + cedilla renders correctly while the ì renders with both the dot and the grave accent on top of each other, rather than the dot disappearing like it should. I would guess that the related font definitions (Ubuntu Regular/Mono, DejaVu Sans Mono, possibly others) are simply incomplete when it comes to these less common character combinations. font-manager has been very helpful for side-by-side comparisons of sample text in multiple fonts. ** Bug watch added: github.com/manisandro/gImageReader/issues #613 https://github.com/manisandro/gImageReader/issues/613 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: Incomplete Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: Confirmed Status in fonts-tlwg package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: Confirmed Status in ttf-bitstream-vera package in Ubuntu: Won't Fix Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889010] Re: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem
I am able to fix this, temporarily, by going into pavucontrol, unmuting the microphone under Input Devices, and muting it again. I will have to check later what the exact name of the microphone device in question is. Note this applies even to headphones that do not have a built-in microphone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1889010 Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm unable to play sound through the headphone jack on this laptop. When I try to play a wav with aplay (e.g. aplay /usr/share/sounds/speech-dispatcher/test.wav) the level indicators in pavucontrol fluctuate, but no sound results. Adjusting the volume does not help. Also, when the headphones are plugged in, I cannot play sound through the internal speakers by selecting the "Speakers" port in pavucontrol Output Devices. With the headphones unplugged, the internal speakers work fine. I tested the Ubuntu 19.10 live USB and I am able to play sound through the headphones without doing anything special (plug in headphones, select "Headphones" from the popup that appears, and use aplay as above), so the hardware itself is apparently okay. The headphones do not work when booting the Ubuntu 20.04 live USB. The problem may be intermittent as I seem to recall I have been able to use the headphones since upgrading to 20.04, but I am not sure of my recollection. I also think that in some of my tests, I was able to play sound through the speakers with the headphones plugged in (by selecting Speakers in pavucontrol) but I cannot reproduce this now. Happy to provide more information, try troubleshooting ideas, etc. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 2549 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jul 26 14:20:31 2020 InstallationDate: Installed on 2019-06-03 (419 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago) dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0G7VYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5482 dmi.product.sku: 089E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found
I've encountered a similar issue for a root volume group w/ encryption. How can I try the same workaround as @veribaka starting from a busybox prompt? In busybox /etc/crypttab does not exist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887964 Title: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume group is no longer found. During boot the console shows Volume group "vg01" not found Cannot process volume group vg01 Gave up waiting for suspend/resume device ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell! Attached dist-upgrade logs and console output. Tried the "vgck --updatemetadata vg01" recommended on this bug report: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889010] Re: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem
This seemed like it might have been related to bug 1873384. However I have pulseaudio 1:13.99.1-1ubuntu3.5 in which that bug is supposedly fixed, and changing input sources does not fix the problem for me. On the other hand the speakers are now working with the headphones plugged in, when "Speakers" is selected in pavucontrol. I don't know what changed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1889010 Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I'm unable to play sound through the headphone jack on this laptop. When I try to play a wav with aplay (e.g. aplay /usr/share/sounds /speech-dispatcher/test.wav) the level indicators in pavucontrol fluctuate, but no sound results. Adjusting the volume does not help. Also, when the headphones are plugged in, I cannot play sound through the internal speakers by selecting the "Speakers" port in pavucontrol Output Devices. With the headphones unplugged, the internal speakers work fine. I tested the Ubuntu 19.10 live USB and I am able to play sound through the headphones without doing anything special (plug in headphones, select "Headphones" from the popup that appears, and use aplay as above), so the hardware itself is apparently okay. The headphones do not work when booting the Ubuntu 20.04 live USB. The problem may be intermittent as I seem to recall I have been able to use the headphones since upgrading to 20.04, but I am not sure of my recollection. I also think that in some of my tests, I was able to play sound through the speakers with the headphones plugged in (by selecting Speakers in pavucontrol) but I cannot reproduce this now. Happy to provide more information, try troubleshooting ideas, etc. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 2549 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jul 26 14:20:31 2020 InstallationDate: Installed on 2019-06-03 (419 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago) dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0G7VYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5482 dmi.product.sku: 089E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889010] [NEW] [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem
Public bug reported: I'm unable to play sound through the headphone jack on this laptop. When I try to play a wav with aplay (e.g. aplay /usr/share/sounds /speech-dispatcher/test.wav) the level indicators in pavucontrol fluctuate, but no sound results. Adjusting the volume does not help. Also, when the headphones are plugged in, I cannot play sound through the internal speakers by selecting the "Speakers" port in pavucontrol Output Devices. With the headphones unplugged, the internal speakers work fine. I tested the Ubuntu 19.10 live USB and I am able to play sound through the headphones without doing anything special (plug in headphones, select "Headphones" from the popup that appears, and use aplay as above), so the hardware itself is apparently okay. The headphones do not work when booting the Ubuntu 20.04 live USB. The problem may be intermittent as I seem to recall I have been able to use the headphones since upgrading to 20.04, but I am not sure of my recollection. I also think that in some of my tests, I was able to play sound through the speakers with the headphones plugged in (by selecting Speakers in pavucontrol) but I cannot reproduce this now. Happy to provide more information, try troubleshooting ideas, etc. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 2549 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jul 26 14:20:31 2020 InstallationDate: Installed on 2019-06-03 (419 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago) dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0G7VYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5482 dmi.product.sku: 089E dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1889010 Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I'm unable to play sound through the headphone jack on this laptop. When I try to play a wav with aplay (e.g. aplay /usr/share/sounds /speech-dispatcher/test.wav) the level indicators in pavucontrol fluctuate, but no sound results. Adjusting the volume does not help. Also, when the headphones are plugged in, I cannot play sound through the internal speakers by selecting the "Speakers" port in pavucontrol Output Devices. With the headphones unplugged, the internal speakers work fine. I tested the Ubuntu 19.10 live USB and I am able to play sound through the headphones without doing anything special (plug in headphones, select "Headphones" from the popup that appears, and use aplay as above), so the hardware itself is apparently okay. The headphones do not work when booting the Ubuntu 20.04 live USB. The problem may be intermittent as I seem to recall I have been able to use the headphones since upgrading to 20.04, but I am not sure of my recollection. I also think that in some of my tests, I was able to play sound through the speakers with the headphones plugged in (by selecting Speakers in pavucontrol) but I cannot reproduce this now. Happy to provide more information, try troubleshooting ideas, etc. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: nate 2549 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jul 26 14:20:31 2020 InstallationDate: Installe
[Touch-packages] [Bug 1379536] Re: Coarse-grained kernel keyring mediation
I have the same problems I tried all things, I can not upload anything, I can not give anything update. https://kodi.software/ & https://luckypatcher.cam/ & https://nox.tips/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1379536 Title: Coarse-grained kernel keyring mediation Status in AppArmor: In Progress Status in apparmor package in Ubuntu: Triaged Bug description: Tracking bug to support coarse-grained kernel keyring mediation. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1379536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
Can confirm that NSCD installation eliminated lag, reference comment #22. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817955] Re: Getting new "DN is out of the realm subtree" error on adding principal
I do not think so, but I may not fully understand what "subtree" implies. The realm was initially created with a command equivalent to: kdb5_ldap_util -D cn=admin,dc=example,dc=com create -subtrees dc=example,dc=com -r TEST.EXAMPLE.COM -s -H ldap://ldapserver.example.com with user entries like: dn: uid=testuser,ou=People,dc=example,dc=com I explicitly added the ou=People,dc=example,dc=com with "kdb5_ldap_util ... modify -subtrees ...", but that did not help. Setting sscope to 2 also did nothing. I can add a principal without specifying dn, but that leads to an entry like: dn: krbPrincipalName=testu...@test.example.com,cn=TEST.EXAMPLE.COM,cn=krb5,dc=example,dc=com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1817955 Title: Getting new "DN is out of the realm subtree" error on adding principal Status in krb5 package in Ubuntu: New Bug description: Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg- 2ubuntu5.4), and started getting errors when adding new principals to LDAP. Obfuscated example: kadmin.local -q "ank -x dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\" testuser" now gives: Authenticating as principal root/ad...@test.example.com with password. NOTICE: no policy specified for testu...@test.example.com; assigning "default" add_principal: DN is out of the realm subtree while creating "testu...@test.example.com". This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to CVE-2018-5729 or CVE-2018-5730. I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817955] [NEW] Getting new "DN is out of the realm subtree" error on adding principal
Public bug reported: Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg- 2ubuntu5.4), and started getting errors when adding new principals to LDAP. Obfuscated example: kadmin.local -q "ank -x dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\" testuser" now gives: Authenticating as principal root/ad...@test.example.com with password. NOTICE: no policy specified for testu...@test.example.com; assigning "default" add_principal: DN is out of the realm subtree while creating "testu...@test.example.com". This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to CVE-2018-5729 or CVE-2018-5730. I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check. ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1817955 Title: Getting new "DN is out of the realm subtree" error on adding principal Status in krb5 package in Ubuntu: New Bug description: Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg- 2ubuntu5.4), and started getting errors when adding new principals to LDAP. Obfuscated example: kadmin.local -q "ank -x dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\" testuser" now gives: Authenticating as principal root/ad...@test.example.com with password. NOTICE: no policy specified for testu...@test.example.com; assigning "default" add_principal: DN is out of the realm subtree while creating "testu...@test.example.com". This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to CVE-2018-5729 or CVE-2018-5730. I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
I don't really understand why people are focusing on the ugly symlink
workaround. It seems to me that the obvious immediate fix for the
warning is to just delete the offending line from gtk-main.css. Of
course, the deeper question is whether gnome-builder.css used to provide
some important functionality, and whether that functionality needs to be
replaced somehow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Thanks everyone! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: Fix Released Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2
This *is* 520546 :) Happened again with console-setup 1.178ubuntu2.7 and keyboard- configuration 1.178ubuntu2.7. Seems like it happens with every update to these packages... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Thanks for bearing with me. I can confirm that the fix works after installing the relevant packages. I tested it by setting a slideshow wallpaper with a change interval of one second. Before the fix, this would cause plasmashell's memory usage to skyrocket. With the fix applied, the memory usage is stable. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: Fix Committed Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Thanks! I enabled the bionic-proposed repo and saw the package update available yesterday, but had no time available to do the update and perform tests. Now I do, but I no longer see an update to qtdeclarative- opensource-src available--just qtdeclarative5-dev and qtdeclarative5-qtquick2-plugin. Was it already accepted? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: Fix Committed Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Fantastic, thanks so much! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: New Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Thanks so much Dmitry! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: New Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
** Description changed: - KDE Plasma is affected by a Qt bug that causes image slideshows to leak - memory, eventually exhausting all available memory and crashing the - system: https://bugs.kde.org/show_bug.cgi?id=368838 + [Impact] - This principally affects people who use the popular slideshow wallpaper - feature. Thankfully, there's a Qt patch to fix it the issue: - https://codereview.qt-project.org/#/c/224684/ + * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. + * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. + * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ - It's slated to go into Qt 5.11. We should strongly consider cherry- - picking it into 5.9.x to get this important fix into our users' hands as - soon as possible. + * An attempt was made to backport the fix prior to Bionic's release, + but this was overlooked or unsuccessful (see the history here). As a + result, it now needs to be done as an SRU. + + [Test Case] + + * Use KDE Plasma + * Right-click on the desktop and choose "Configure Desktop" + * Change the wallpaper type to "Slideshow" and choose a folder full of images + * Click Apply + * Wait a few days; Plasma will eventually totally freeze + + [Regression Potential] + + * Regressions are unlikely given that the specific backport patch has + been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, + and the actual code fix in Qt was released to users in Qt 5.11 months + ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: New Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: New Bug description: KDE Plasma is affected by a Qt bug that causes image slideshows to leak memory, eventually exhausting all available memory and crashing the system: https://bugs.kde.org/show_bug.cgi?id=368838 This principally affects people who use the popular slideshow wallpaper feature. Thankfully, there's a Qt patch to fix it the issue: https://codereview.qt-project.org/#/c/224684/ It's slated to go into Qt 5.11. We should strongly consider cherry- picking it into 5.9.x to get this important fix into our users' hands as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Am I missing something? There is nothing to fix in qtdeclarative- opensource-src for Cosmic since it has Qt 5.11, and Qt 5.11 simply includes the fix by default. This bug tracks cherry-picking the fix into the version of qtdeclarative-opensource-src that's in Bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: New Bug description: KDE Plasma is affected by a Qt bug that causes image slideshows to leak memory, eventually exhausting all available memory and crashing the system: https://bugs.kde.org/show_bug.cgi?id=368838 This principally affects people who use the popular slideshow wallpaper feature. Thankfully, there's a Qt patch to fix it the issue: https://codereview.qt-project.org/#/c/224684/ It's slated to go into Qt 5.11. We should strongly consider cherry- picking it into 5.9.x to get this important fix into our users' hands as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
That's for 5.11.1; what about the backport to 5.9.5 for Bionic? ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: KDE Plasma is affected by a Qt bug that causes image slideshows to leak memory, eventually exhausting all available memory and crashing the system: https://bugs.kde.org/show_bug.cgi?id=368838 This principally affects people who use the popular slideshow wallpaper feature. Thankfully, there's a Qt patch to fix it the issue: https://codereview.qt-project.org/#/c/224684/ It's slated to go into Qt 5.11. We should strongly consider cherry- picking it into 5.9.x to get this important fix into our users' hands as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2
For me this issue appears to have been introduced with the recent update to console-setup-1.178ubuntu2.6 and keyboard- configuration-1.178ubuntu2.6 on 8/17/18. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2
Can confirm on Bionic that: 1. this started happening randomly 2. `sudo kbd_mode -s` fixed it immediately -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
I think so, yes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784161] Re: Mouse inoperative in other apps while Shotwell is uploading to Flickr
Adding some detail here: Switching back to xorg reproduces the bug 100%. I can click on the launcher, it seems to be the only thing that'll receive my clicks while the bug is active, but new apps launched while the bug is active are also unable to see mouse clicks. Kernel is 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux shotwell is 0.28.2 that came preinstalled, I've done nothing to it other than import a folder of photos and authenticate with Flickr for my upload key. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1784161 Title: Mouse inoperative in other apps while Shotwell is uploading to Flickr Status in xorg package in Ubuntu: New Bug description: I'm using Shotwell to Publish (ctrl+shift+P) photos to Flickr. Some of these uploads take quite a while, so I'd like to do other things while they're running. If I alt-tab over to Firefox or Slack or whatever, my mouse works normally, but if I alt-tab back to Shotwell to peek if the upload has completed yet, and then alt-tab over to another app again, now my mouse doesn't work. Pointer moves, yes. Doesn't produce mouse-over events, doesn't click, doesn't scroll. As soon as the upload completes in Shotwell, the mouse works normally again. I popped into freenode/#ubuntu IRC and they suggested trying Wayland. This behavior does not occur in Wayland, so it was suggested that I report it here under xorg. I'm running Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784161] [NEW] Mouse inoperative in other apps while Shotwell is uploading to Flickr
Public bug reported: I'm using Shotwell to Publish (ctrl+shift+P) photos to Flickr. Some of these uploads take quite a while, so I'd like to do other things while they're running. If I alt-tab over to Firefox or Slack or whatever, my mouse works normally, but if I alt-tab back to Shotwell to peek if the upload has completed yet, and then alt-tab over to another app again, now my mouse doesn't work. Pointer moves, yes. Doesn't produce mouse-over events, doesn't click, doesn't scroll. As soon as the upload completes in Shotwell, the mouse works normally again. I popped into freenode/#ubuntu IRC and they suggested trying Wayland. This behavior does not occur in Wayland, so it was suggested that I report it here under xorg. I'm running Ubuntu 18.04 LTS. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1784161 Title: Mouse inoperative in other apps while Shotwell is uploading to Flickr Status in xorg package in Ubuntu: New Bug description: I'm using Shotwell to Publish (ctrl+shift+P) photos to Flickr. Some of these uploads take quite a while, so I'd like to do other things while they're running. If I alt-tab over to Firefox or Slack or whatever, my mouse works normally, but if I alt-tab back to Shotwell to peek if the upload has completed yet, and then alt-tab over to another app again, now my mouse doesn't work. Pointer moves, yes. Doesn't produce mouse-over events, doesn't click, doesn't scroll. As soon as the upload completes in Shotwell, the mouse works normally again. I popped into freenode/#ubuntu IRC and they suggested trying Wayland. This behavior does not occur in Wayland, so it was suggested that I report it here under xorg. I'm running Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782613] [NEW] Periodically remove very old thumbnails or cap thumbnail cache size to avoid filling up disk with thumbnails
Public bug reported: The cross-desktop thumbnail spec contains no provision for removing thumbnails, and as a result, the thumbnail cache (~/.cache/thumbnails) can grow without limit. For some users with large numbers of images, the cache can wind up taking up quite a lot of space and even causing free space issues. We should consider setting a maximum size for the cache, or removing old thumbnails not accessed in the last few years, or something like that. More information, including proposed cleanup scripts, can be found in the following upstream KDE bug report that was reported to track this issue: https://bugs.kde.org/show_bug.cgi?id=79943 ** Affects: thumbnailer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1782613 Title: Periodically remove very old thumbnails or cap thumbnail cache size to avoid filling up disk with thumbnails Status in thumbnailer package in Ubuntu: New Bug description: The cross-desktop thumbnail spec contains no provision for removing thumbnails, and as a result, the thumbnail cache (~/.cache/thumbnails) can grow without limit. For some users with large numbers of images, the cache can wind up taking up quite a lot of space and even causing free space issues. We should consider setting a maximum size for the cache, or removing old thumbnails not accessed in the last few years, or something like that. More information, including proposed cleanup scripts, can be found in the following upstream KDE bug report that was reported to track this issue: https://bugs.kde.org/show_bug.cgi?id=79943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1782613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] [NEW] Attempt to import nonexistent gnome-builder.css
Public bug reported:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when running
various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error: gtk-
main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file
or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
** Affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Attempt to import nonexistent gnome-builder.css
Status in ubuntu-themes package in Ubuntu:
New
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Yay, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Committed Bug description: KDE Plasma is affected by a Qt bug that causes image slideshows to leak memory, eventually exhausting all available memory and crashing the system: https://bugs.kde.org/show_bug.cgi?id=368838 This principally affects people who use the popular slideshow wallpaper feature. Thankfully, there's a Qt patch to fix it the issue: https://codereview.qt-project.org/#/c/224684/ It's slated to go into Qt 5.11. We should strongly consider cherry- picking it into 5.9.x to get this important fix into our users' hands as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used
Relevant upstream KDE bug reports: - https://bugs.kde.org/show_bug.cgi?id=387502 - https://bugs.kde.org/show_bug.cgi?id=377473 ** Bug watch added: KDE Bug Tracking System #387502 https://bugs.kde.org/show_bug.cgi?id=387502 ** Bug watch added: KDE Bug Tracking System #377473 https://bugs.kde.org/show_bug.cgi?id=377473 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1572244 Title: Kubuntu requires that the WiFi password be entered twice before WiFi can be used Status in network-manager package in Ubuntu: Confirmed Status in plasma-nm package in Ubuntu: Confirmed Bug description: Kubuntu 16.04 ISO number 20160417.1 Xenial Final Bug reported against network-manager Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it requires to enter the wifi password twice before I can use the wifi. Once from the network icon panel, then second time a prompt on the desktop to enter the wifi password. I do not know if this is typical behavior of Kubuntu since I usually use GTK base desktops. I guess network-manager is the right package to file this report against. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.373 CurrentDesktop: KDE Date: Tue Apr 19 16:48:02 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.77.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.77.0/24 dev wlp3s0 proto kernel scope link src 192.168.77.128 metric 600 LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52 802-11-wireless 1461084315 Tue 19 Apr 2016 04:45:15 PM UTC yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/3 Wired connection 1 4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e 802-3-ethernet 1461077415 Tue 19 Apr 2016 02:50:15 PM UTC yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52 /org/freedesktop/NetworkManager/ActiveConnection/3 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1572244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
I noticed that this problem can be fixed for me if the GPG_DEFAULT_OPTIONS variable on line 171 of ppa.py is changed. If I add these two properties to the list, then the problem goes away completely: "--keyserver-options", "http-proxy=" + os.environ['http_proxy'] Obviously, you would want to check for the existence of this variable before you just went using it, but it looks like this is the problem. The PPA library does not forward the HTTP proxy settings along to GPG, so GPG tries and fails to make a direct connection to the keyserver. Am I missing something about the way this works, or can we make a similar change and resolve these proxy issues? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1089389 Title: juju bootstrap fail behind a proxy when a gpg key must be imported Status in software-properties package in Ubuntu: Triaged Bug description: This is related to a Maas environment hosted behind a proxy. I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK ubuntu@zookeeper:/var/log$ echo $? 0 On the zookeeper node, python-software-properties is version 0.82.7.3 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Dec 12 14:40:21 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
The script worked for me too with an HP Spectre x360 13-w013dx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
I was able to test with a Live USB disk booting Kubuntu 17.10 and I'm sorry to say that there was no change: the HSP profile was still the default. However, I'd also reported this upstream to the PulseAudio folks, and it looks like they've identified the problem and are preparing a fix: https://bugs.freedesktop.org/show_bug.cgi?id=103058 ** Bug watch added: freedesktop.org Bugzilla #103058 https://bugs.freedesktop.org/show_bug.cgi?id=103058 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in pulseaudio package in Ubuntu: Incomplete Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
Thanks for the info. I'll give that a shot and report back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in pulseaudio package in Ubuntu: Incomplete Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720684] [NEW] Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
Public bug reported: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in bluez package in Ubuntu: New Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1720684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700089] Re: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
holding the following packages at their respective versions resolves the error, for now. (apt-get install these packages with "apt-get install =" and then use "apt-mark hold =") ((posted for the new guys like me, who were slightly terrified when this error popped up)) python3-click-package=0.4.45.1+16.10.20160916-0ubuntu1 gir1.2-click-0.4=0.4.45.1+16.10.20160916-0ubuntu1 libclick-0.4-0=0.4.45.1+16.10.20160916-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1700089 Title: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in click package in Ubuntu: Confirmed Bug description: Not sure what happened, just had this pop up. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 AptOrdering: click:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jun 23 14:59:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-08-21 (305 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: click Title: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-19 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1700089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
This bug has been submitted to the linux kernel bug tracker as well https://bugzilla.kernel.org/show_bug.cgi?id=195457 ** Bug watch added: Linux Kernel Bug Tracker #195457 http://bugzilla.kernel.org/195457 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
Same issue with asus zenbook 3, same audio card. In addition the built in speaker output is broken, it can only be 0% or 100%, no in between. Seemingly related. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605883] [NEW] wget uses system CA certificates even when told not to
Public bug reported: In the wget man page, the command line options --ca-certificate and --ca-directory have the sentence: "Without this option Wget looks for CA certificates at the system-specified locations, chosen at OpenSSL installation time." To me, that implies that *with* these options, the system-specified locations are *not* searched. (That would be useful if the sysadmin has installed certificates that the user doesn't trust.) However, it appears that even with these options, the system SSL directory /usr/lib/ssl/certs (symlink to /etc/ssl/certs) is still searched. Running wget --ca-certificate=/dev/null --ca-directory=/nonexistent https://www.google.com succeeds. I would expect it to fail, having no trusted CA certificate. strace reveals that it reads a certificate from /usr/lib/ssl/certs. Either the code should be fixed, or the man page should be clarified. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: wget 1.17.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Jul 23 09:12:02 2016 SourcePackage: wget UpgradeStatus: Upgraded to xenial on 2016-05-27 (57 days ago) ** Affects: wget (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1605883 Title: wget uses system CA certificates even when told not to Status in wget package in Ubuntu: New Bug description: In the wget man page, the command line options --ca-certificate and --ca-directory have the sentence: "Without this option Wget looks for CA certificates at the system-specified locations, chosen at OpenSSL installation time." To me, that implies that *with* these options, the system-specified locations are *not* searched. (That would be useful if the sysadmin has installed certificates that the user doesn't trust.) However, it appears that even with these options, the system SSL directory /usr/lib/ssl/certs (symlink to /etc/ssl/certs) is still searched. Running wget --ca-certificate=/dev/null --ca-directory=/nonexistent https://www.google.com succeeds. I would expect it to fail, having no trusted CA certificate. strace reveals that it reads a certificate from /usr/lib/ssl/certs. Either the code should be fixed, or the man page should be clarified. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: wget 1.17.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Jul 23 09:12:02 2016 SourcePackage: wget UpgradeStatus: Upgraded to xenial on 2016-05-27 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1605883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
I don't know if this will help anyone else arrive at a solution, but I observed alsamixer while switching back and forth between non-speaker phone mode and speaker phone mode in a phone call. While switching the mode I watched capture "devices" (not sure of the correct term) DEC4 and DEC6 change gain amounts as follows: non-speaker phone mode DEC4 at 68%, dB gain: 0.84 DEC6 at 80%, dB gain: 0.99 speaker phone mode DEC4 at 70%, dB gain: 0.87 DEC6 at 68%, dB gain: 0.84 I'm learning about this on the fly because I'd like a solution, so I have no idea what to do next but maybe someone else does. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in pulseaudio package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
I tried updating the modem firmware as explained at https://lists.launchpad.net/ubuntu-phone/msg08514.html, but no apparent change. I, too, previously had the more recent radio image M9615A- CEFWMAZM-2.0.1701.07 until I flashed the m9615a-cefwmazm-2.0.1700.98 image. I'd be willing to play around with alsa-mixer settings, but I don't know how to do it on the phone at this point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in pulseaudio package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)
I also have this issue on my Nexus 4: LGE Nexus 4 (mako) OTA-9.1 Ubuntu image part: 20160217.1 Ubuntu 15.04 - armhf (20160217-111536) device image part: 20160112 device build description: aosp_mako-userdebug 4.4.2 KOT49H 20160107-1211-0ubuntu4 test-keys Custom image part: 20160217.1 Is there a workaround other than holding my phone to my mouth while using speaker phone? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in pulseaudio package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480524] [NEW] package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: unknown. apport sent me here ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Sat Aug 1 01:59:01 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-06-10 (51 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: systemd Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 033MX4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/03/2013:svnDellInc.:pnInspiron3521:pvrA05:rvnDellInc.:rn033MX4:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 3521 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1480524 Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: unknown. apport sent me here ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Sat Aug 1 01:59:01 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-06-10 (51 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: systemd Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 033MX4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/03/2013:svnDellInc.:pnInspiron3521:pvrA05:rvnDellInc.:rn033MX4:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 3521 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1480524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275042] Re: Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC
I have the same issue in Ubuntu MATE Remix 14.04.1 on an iBook G4 (mid-2005, PPC). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275042 Title: Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC Status in Mesa: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with Force Version with the Synaptic package manager on new distributions. We had a problem with wrong colors in SuperTuxKart 0.8 last year. The Irrlicht guys have released a little hack for Irrlicht on Linux PPC (http://irrlicht.sourceforge.net/forum/viewtopic.php?f=7t=48577). They told me that is a driver bug, and that workaround costs performance and RAM. Unfortunately this workaround isn't suitable for Mesa 9.2 and higher. At this time we have to install Mesa 9.1.X and lower on new Linux distributions like Lubuntu 13.10, Lubuntu 14.04, Debian Sid etc. It would be nice to solve this issue because we don't need the workaround in the future. Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU Xena 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM HIS Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1275042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311403] Re: Can't type password after resume.
This happens sporadically on my 2013 Dell XPS-15 (same model Mark Shuttleworth uses... just sayin' ;) For me, the passowrd text box often just doesn't show up at all the rest of the UI is there, but not the text box. Sometimes I can click on guest session from the gear menu to get it back, but sometimes there is no gear menu, and I have to hard reset (maybe there's some other way to cancel out of the lock screen, but I don't know it). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 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 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
