[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles

[Niklas Schmelzle]

The graphic glitch just happened on my system (Ubuntu 23.10, Lenovo
ThinkPad T14 Gen 2a with AMD Ryzen™ 5 PRO 5650U with Radeon™ Graphics ×
12) again. I have `COGL_DEBUG=disable-batching` set in /etc/environment.
Furthermore all extensions are deactivated (however, not deleted).
System was also rebooted.

Interestingly, this time it did not occur to an XWayland window. I
configured chrome to run wayland directly (which decreased the frequency
of the error occuring, at least it seemed like it).

Here dmesg:

[70061.823842] amdgpu :07:00.0: amdgpu: [gfxhub0] no-retry page fault 
(src_id:0 ring:24 vmid:1 pasid:32771, for process chrome pid 5084 thread 
chrome:cs0 pid 5121)
[70061.823858] amdgpu :07:00.0: amdgpu:   in page starting at address 
0x000c5de7b000 from IH client 0x1b (UTCL2)
[70061.823865] amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00100430
[70061.823869] amdgpu :07:00.0: amdgpu:  Faulty UTCL2 client ID: IA 
(0x2)
[70061.823873] amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 0x0
[70061.823877] amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 0x0
[70061.823880] amdgpu :07:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
[70061.823883] amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 0x0
[70061.823886] amdgpu :07:00.0: amdgpu:  RW: 0x0


I might try to set the kernel parameter next. For clarification: I would add 
amdgpu.mcb=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run 
'sudo update-grub' (or update-grub2?). Afterwards I can just reboot?

BTW, just to rule other influences out: I do hibernate my system from
time to time. This should not have any influence, or?

-- 
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/2038998

Title:
  [amdgpu] Screen corruption, distorted geometry and misplaced triangles

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.2

[Touch-packages] [Bug 1954902] [NEW] lpoptions cannot change system-wide default printer

[Niklas Rother]

Public bug reported:

According to "man lpoptions":

> When  run by the root user, lpoptions gets and sets default options and
> instances for all users in the  /etc/cups/lpoptions  file.   Otherwise,
> the per-user defaults are managed in the ~/.cups/lpoptions file.

According to my experimentation, this is incorrect. When lpoptions is
run as root, the file "/root/.cups/lpoptions" is updated (aka the
personal default printer of root), not "/etc/cups/lpoptions" (aka the
system-wide default printer).

I'm unsure whether this is a documentation bug or wrong behavior. I
assume the later, because there seems to be no other option to set the
system-wide default printer.

root@mi553-022:~# lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
root@mi553-022:~# apt-cache policy cups
cups:
  Installed: 2.3.1-9ubuntu1.1
  Candidate: 2.3.1-9ubuntu1.1
  Version table:
 *** 2.3.1-9ubuntu1.1 500
500 http://ftp.luis.uni-hannover.de/ubuntu focal-updates/main amd64 
Packages
500 http://ftp.luis.uni-hannover.de/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2.3.1-9ubuntu1 500
500 http://ftp.luis.uni-hannover.de/ubuntu focal/main amd64 Packages
 2.2.7-1ubuntu2.8 500
500 http://ftp.luis.uni-hannover.de/ubuntu bionic-security/main amd64 
Packages

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1954902

Title:
  lpoptions cannot change system-wide default printer

Status in cups package in Ubuntu:
  New

Bug description:
  According to "man lpoptions":

  > When  run by the root user, lpoptions gets and sets default options and
  > instances for all users in the  /etc/cups/lpoptions  file.   Otherwise,
  > the per-user defaults are managed in the ~/.cups/lpoptions file.

  According to my experimentation, this is incorrect. When lpoptions is
  run as root, the file "/root/.cups/lpoptions" is updated (aka the
  personal default printer of root), not "/etc/cups/lpoptions" (aka the
  system-wide default printer).

  I'm unsure whether this is a documentation bug or wrong behavior. I
  assume the later, because there seems to be no other option to set the
  system-wide default printer.

  root@mi553-022:~# lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  root@mi553-022:~# apt-cache policy cups
  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://ftp.luis.uni-hannover.de/ubuntu focal-updates/main amd64 
Packages
  500 http://ftp.luis.uni-hannover.de/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://ftp.luis.uni-hannover.de/ubuntu focal/main amd64 Packages
   2.2.7-1ubuntu2.8 500
  500 http://ftp.luis.uni-hannover.de/ubuntu bionic-security/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1954902/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

[Niklas Rother]

Thanks for building the packages for focal.

I can confirm that this fixes the problem for me!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1938144

Title:
  monitor_read: unpermitted request 48 on server while attempting GSSAPI
  key exchange

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
  server) with the option "GSSAPIKeyExchange=yes", and this causes the
  connection to fail. The server has GSSAPI (Kerberos authentication)
  enabled, but is is only used for non-root users (root uses SSH keys).

  Client command:

  ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
  root@server -v -p  -o GSSAPIKeyExchange=yes

  Client log:

  OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: Reading configuration data /home/user/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: Connecting to compute-test [130.75.80.46] port .
  debug1: Connection established.
  debug1: identity file /home/rother/.ssh/id_rsa type 0
  debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_dsa type -1
  debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519 type -1
  debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_xmss type -1
  debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to server: as 'root'
  debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: Doing group exchange
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Received GSSAPI_COMPLETE
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Rekey has happened - updating saved versions
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent
  debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA 
SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent
  debug1: Will attempt key: /home/user/.ssh/id_dsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk 
  debug1: Will attempt key: /home/user/.ssh/id_xmss 
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-with-mic
  debug1: Delegating credentials
  debug1: Delegating credentials
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-keyex
  Connection closed by 1.2.3.4 port 

  Server log:

  debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: private host key #0: ssh-rsa SHA256:REDACTED
  debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:REDACTED
  debug1: private host key #2: ssh-ed25519 SHA256:REDACTED
  debug1: rexec

[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

[Niklas Rother]

Thanks for the PPA! I currently don't have an impish system at hand,
would it be possible to build it for focal as well?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1938144

Title:
  monitor_read: unpermitted request 48 on server while attempting GSSAPI
  key exchange

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
  server) with the option "GSSAPIKeyExchange=yes", and this causes the
  connection to fail. The server has GSSAPI (Kerberos authentication)
  enabled, but is is only used for non-root users (root uses SSH keys).

  Client command:

  ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
  root@server -v -p  -o GSSAPIKeyExchange=yes

  Client log:

  OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: Reading configuration data /home/user/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: Connecting to compute-test [130.75.80.46] port .
  debug1: Connection established.
  debug1: identity file /home/rother/.ssh/id_rsa type 0
  debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_dsa type -1
  debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519 type -1
  debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_xmss type -1
  debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to server: as 'root'
  debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: Doing group exchange
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Received GSSAPI_COMPLETE
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Rekey has happened - updating saved versions
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent
  debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA 
SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent
  debug1: Will attempt key: /home/user/.ssh/id_dsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk 
  debug1: Will attempt key: /home/user/.ssh/id_xmss 
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-with-mic
  debug1: Delegating credentials
  debug1: Delegating credentials
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-keyex
  Connection closed by 1.2.3.4 port 

  Server log:

  debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: private host key #0: ssh-rsa SHA256:REDACTED
  debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:REDACTED
  debug1: private host key #2: ssh-ed25519 SHA25

[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

[Niklas Rother]

Ok, I managed to reproduces this in a clean "ubuntu:latest" docker
container. Steps to reproduce are below. During testing, I noticed that
I aliased "ssh" to "ssh -K -X", and that "-K" (or equivalently "-o
GSSAPIAuthentication=yes") is crucial. This changes the problematic SSH
client command to

ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
root@ac3f9944f201 -v -p  -o GSSAPIKeyExchange=yes -o
GSSAPIAuthentication=yes -F /dev/null

Complete steps to reproduce (container ac3f9944f201 is the server, IP
1.2.3.4 is the IP of the container host; this needs to be adapted):

Server:

podman run -it -p :,:88 ubuntu

apt update
apt install openssh-server krb5-kdc krb5-admin-server
touch /etc/krb5kdc/kadm5.acl
touch /etc/krb5kdc/kadm5.dict
krb5_newrealm 
kadmin.local 

addprinc user
addprinc -randkey host/ac3f9944f201
ktadd -k /etc/krb5.keytab host/ac3f9944f201
exit

mkdir /run/sshd
/usr/sbin/sshd -d -p  -f /dev/null -o GSSAPIKeyExchange=yes -o 
GSSAPIAuthentication=yes

Client:

podman run -it ubuntu

apt update
apt install openssh-client krb5-user
kinit user
echo "1.2.3.4 ac3f9944f201" >> /etc/hosts

ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
root@ac3f9944f201 -v -p  -o GSSAPIKeyExchange=yes -o
GSSAPIAuthentication=yes -F /dev/null

Notice "monitor_read: unpermitted request 48" on the server, and
"Connection closed by 1.2.3.4 port " on the client (instead of the
expected "permission denied).

** Changed in: openssh (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1938144

Title:
  monitor_read: unpermitted request 48 on server while attempting GSSAPI
  key exchange

Status in openssh package in Ubuntu:
  New

Bug description:
  I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
  server) with the option "GSSAPIKeyExchange=yes", and this causes the
  connection to fail. The server has GSSAPI (Kerberos authentication)
  enabled, but is is only used for non-root users (root uses SSH keys).

  Client command:

  ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
  root@server -v -p  -o GSSAPIKeyExchange=yes

  Client log:

  OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: Reading configuration data /home/user/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: Connecting to compute-test [130.75.80.46] port .
  debug1: Connection established.
  debug1: identity file /home/rother/.ssh/id_rsa type 0
  debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_dsa type -1
  debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519 type -1
  debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_xmss type -1
  debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to server: as 'root'
  debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: Doing group exchange
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Received GSSAPI_COMPLETE
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Rekey has happened - updating saved versions
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/E

[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

[Niklas Rother]

Thanks Sergio for trying to reproduce this! I'm a bit puzzled, why the
bug did not trigger in your case. I'll try to reproduce this in a clean
VM as well now. One important thing might be that I tried to login as
"root", for which I did not have a Kerberos-Ticket, so a "permission
denied" would be expected, unless something like "publickey" is included
in  PreferredAuthentications.

@Miriam: The SSH-configuration should be irrelevant, because of the
options "-f /dev/null" and "-F /dev/null". The Kerberos-config could be
part of this. I'll try to reproduce this on a clean machine and post
better steps for reproducing afterwards.

Thank you all for helping with this!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1938144

Title:
  monitor_read: unpermitted request 48 on server while attempting GSSAPI
  key exchange

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
  server) with the option "GSSAPIKeyExchange=yes", and this causes the
  connection to fail. The server has GSSAPI (Kerberos authentication)
  enabled, but is is only used for non-root users (root uses SSH keys).

  Client command:

  ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
  root@server -v -p  -o GSSAPIKeyExchange=yes

  Client log:

  OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: Reading configuration data /home/user/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: Connecting to compute-test [130.75.80.46] port .
  debug1: Connection established.
  debug1: identity file /home/rother/.ssh/id_rsa type 0
  debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_dsa type -1
  debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519 type -1
  debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_xmss type -1
  debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to server: as 'root'
  debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: Doing group exchange
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Received GSSAPI_COMPLETE
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Rekey has happened - updating saved versions
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent
  debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA 
SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent
  debug1: Will attempt key: /home/user/.ssh/id_dsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk 
  debug1: Will attempt key: /home/user/.ssh/id_xmss 
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-with-mic
  debug1: Delegating credentials
  debug1: Delegating credentials
  debug1: Au

[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

[Niklas Rother]

Hello Athos,

thanks for looking into this!

This is reproducible without Ansible, that was just use-case that
brought up the issue. I've further narrowed it down to the following
setup:

Server:
/usr/sbin/sshd -d -p  -f /dev/null -o GSSAPIKeyExchange=yes -o 
GSSAPIAuthentication=yes

Client:
ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@compute-test 
-v -p  -o GSSAPIKeyExchange=yes -F /dev/null

I think this should make it independent from my local config, right?
Obviously there is also Kerberos involved, which I would call configured
pretty standard in our environment, but I can have a look at that config
as well, if this is desired.

The problem will not arise when:
- The client has no valid Kerberos-Key (unset KRB5CCNAME)
- If any of the the GSSAPI* options is missing on client or server
- If the order of "gssapi-with-mic,gssapi-keyex" is switched (!)


** Changed in: openssh (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1938144

Title:
  monitor_read: unpermitted request 48 on server while attempting GSSAPI
  key exchange

Status in openssh package in Ubuntu:
  New

Bug description:
  I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
  server) with the option "GSSAPIKeyExchange=yes", and this causes the
  connection to fail. The server has GSSAPI (Kerberos authentication)
  enabled, but is is only used for non-root users (root uses SSH keys).

  Client command:

  ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
  root@server -v -p  -o GSSAPIKeyExchange=yes

  Client log:

  OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: Reading configuration data /home/user/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: Connecting to compute-test [130.75.80.46] port .
  debug1: Connection established.
  debug1: identity file /home/rother/.ssh/id_rsa type 0
  debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_dsa type -1
  debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519 type -1
  debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_xmss type -1
  debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to server: as 'root'
  debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: Doing group exchange
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Received GSSAPI_COMPLETE
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Rekey has happened - updating saved versions
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent
  debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA 
SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent
  debug1: Will attempt key: /home/user/.ssh/id_dsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk 
  debug1: Will attempt key: /home/user/.ssh/id_xmss 
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
serv

[Touch-packages] [Bug 1938144] [NEW] monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

[Niklas Rother]

Public bug reported:

I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
server) with the option "GSSAPIKeyExchange=yes", and this causes the
connection to fail. The server has GSSAPI (Kerberos authentication)
enabled, but is is only used for non-root users (root uses SSH keys).

Client command:

ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server
-v -p  -o GSSAPIKeyExchange=yes

Client log:

OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /home/user/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to compute-test [130.75.80.46] port .
debug1: Connection established.
debug1: identity file /home/rother/.ssh/id_rsa type 0
debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
debug1: identity file /home/rother/.ssh/id_dsa type -1
debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
debug1: identity file /home/rother/.ssh/id_ecdsa type -1
debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/rother/.ssh/id_ed25519 type -1
debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/rother/.ssh/id_xmss type -1
debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
debug1: Authenticating to server: as 'root'
debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: Doing group exchange
debug1: Calling gss_init_sec_context
debug1: Delegating credentials
debug1: Received GSSAPI_COMPLETE
debug1: Calling gss_init_sec_context
debug1: Delegating credentials
debug1: Rekey has happened - updating saved versions
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent
debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA 
SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent
debug1: Will attempt key: /home/user/.ssh/id_dsa 
debug1: Will attempt key: /home/user/.ssh/id_ecdsa 
debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/user/.ssh/id_ed25519 
debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk 
debug1: Will attempt key: /home/user/.ssh/id_xmss 
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: 
server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Delegating credentials
debug1: Delegating credentials
debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-keyex
Connection closed by 1.2.3.4 port 

Server log:

debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f  31 Mar 2020
debug1: private host key #0: ssh-rsa SHA256:REDACTED
debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:REDACTED
debug1: private host key #2: ssh-ed25519 SHA256:REDACTED
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
debug1: rexec_argv[2]='-p'
debug1: rexec_argv[3]=''
debug1: Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port  on 0.0.0.0.
Server listening on 0.0.0.0 port .
debug1: Bind to port  on ::.
Server listening on :: port .
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f  31 Mar 2020
debug1: private host key #0: ssh-rsa SHA256:REDACTED
debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:REDACTED
debu

[Touch-packages] [Bug 1912673] [NEW] sounds not working on Dell XPS 17 (9700)

[Niklas]

Public bug reported:

My investigation process:

Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
worked.

I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones,
using linux-image-5.4.0-42-generic, I did not try blutooth.

I sudo apt upgrade, dist-upgrade to get kernels

linux-image-5.8.0-38-generic
linux-image-5.8.0-40-generic

Sounds did not work.
I download linux-image-unsigned-5.10.9-051009-generic.
Sounds did not work.

I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
Sounds did not work.

After googling I found this solution in the comments:
https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

"""

Download and install dkms module:

https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
dkms/+packages

Alternatively, you can install linux-oem-20.04, it will install the
5.6 kernel with the above driver. Your system may be more stable with
5.4 kernel since it is in wide use.

Manually install sof-firmware from Arch Linux:

https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
firmware-1.5.1-1-any.pkg.tar.zst.html

You will need to delete the existing "sof" and "sof-tplg" files from
the Ubuntu linux-firmware package first. Note if this package gets
updated from Canoncial and they don't update these, you will have to
delete and then reextract. Files go into the /usr/lib/firmware/intel/sof
and /usr/lib/firmware/intel/sof-tplg folders.

Manually install the ucm2 files:

http://xps17.ddns.net/sof-soundwire.zip

These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
contents of the existing sof-soundwire folder (if you have it) and
replace them with the ones from the archive.

Reboot. You should now have all your audio devices available. If speakers 
do not play, you may need to run alsamixer (non-root) from a terminal and 
unmute and set the mixer levels all the way up.
"""


This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually
opening alsa-mixer and changing soundcard to sof. The sound would
otherwise just show 'dummy'.

My sounds still do not work on 5.8 or 5.10, full name listed above. I
did not get to test this temporary fix with 5.4.

my full alsa-info:
http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

based on some google research, this seems to be a common problem:
https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/
https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/
https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
etc...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
Uname: Linux 5.6.0-1042-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  neoh   1786 F pulseaudio
 /dev/snd/pcmC1D0p:   neoh   1786 F...m pulseaudio
 /dev/snd/controlC0:  neoh   1786 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 12:08:45 2021
InstallationDate: Installed on 2021-01-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0CXCCY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal package-from-proposed

** Description changed:

  My investigation process:
  
  Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
  worked.
  
- I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones, 
+ I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones,
  using linux-image-5.4.0-42-generic, I did not try blutooth.
  
  I sudo apt upgrade, dist-upgrade to get kernels
  
- linux-image-5.8.0-38-generic 
+ linux-image-5.8.0-38-generic
  linux-image-5.8.0-40-generic
  
- Sounds did not work. 
+ Sounds did not work.
  I download linux-image-unsigned-5.10.9-051009-generic.
  Sounds did not work.
  
  I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
  Sounds did not work.
  
  After googling I found this solution in the comments:
  https://askubuntu.com/ques

[Touch-packages] [Bug 1899286] [NEW] package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 failed to install/upgrade: »installiertes nvidia-kernel-common-450-Skript des Paketes post-installation«-U

[Niklas]

Public bug reported:

Occured after apt update && apt upgrade. System has zfs root partition.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Oct 10 21:37:21 2020
ErrorMessage: »installiertes nvidia-kernel-common-450-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2020-04-12 (181 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 failed to 
install/upgrade: »installiertes nvidia-kernel-common-450-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1899286

Title:
  package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 failed to
  install/upgrade: »installiertes nvidia-kernel-common-450-Skript des
  Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Occured after apt update && apt upgrade. System has zfs root
  partition.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Oct 10 21:37:21 2020
  ErrorMessage: »installiertes nvidia-kernel-common-450-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2020-04-12 (181 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 failed to 
install/upgrade: »installiertes nvidia-kernel-common-450-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899286/+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 1879150] [NEW] apport-kde shows 'text' instead of text in message box

[Niklas Sombert]

Public bug reported:

I had some other software crashing and wanting to report a bug, Apport
displayed a pretty nonsensical message box (see the screenshot).

$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy apport-kde
apport-kde:
  Installed: 2.20.11-0ubuntu27
  Candidate: 2.20.11-0ubuntu27
  Version table:
 *** 2.20.11-0ubuntu27 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport-kde 2.20.11-0ubuntu27
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sun May 17 14:11:30 2020
InstallationDate: Installed on 2015-12-11 (1618 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal patch third-party-packages

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1879150/+attachment/5372875/+files/3e98f10f63f78f74.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1879150

Title:
  apport-kde shows 'text' instead of text in message box

Status in apport package in Ubuntu:
  New

Bug description:
  I had some other software crashing and wanting to report a bug, Apport
  displayed a pretty nonsensical message box (see the screenshot).

  $ lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04
  $ apt-cache policy apport-kde
  apport-kde:
Installed: 2.20.11-0ubuntu27
Candidate: 2.20.11-0ubuntu27
Version table:
   *** 2.20.11-0ubuntu27 500
  500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport-kde 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 17 14:11:30 2020
  InstallationDate: Installed on 2015-12-11 (1618 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1879150] Re: apport-kde shows 'text' instead of text in message box

[Niklas Sombert]

** Patch added: "apport-kde.patch"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+attachment/5372882/+files/apport-kde.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1879150

Title:
  apport-kde shows 'text' instead of text in message box

Status in apport package in Ubuntu:
  New

Bug description:
  I had some other software crashing and wanting to report a bug, Apport
  displayed a pretty nonsensical message box (see the screenshot).

  $ lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04
  $ apt-cache policy apport-kde
  apport-kde:
Installed: 2.20.11-0ubuntu27
Candidate: 2.20.11-0ubuntu27
Version table:
   *** 2.20.11-0ubuntu27 500
  500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport-kde 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 17 14:11:30 2020
  InstallationDate: Installed on 2015-12-11 (1618 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+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 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

[Niklas Sombert]

** Patch added: "patch removing pk_backend_get_distro_upgrades and disabling 
the feature"
   
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1709699/+attachment/5360831/+files/remove-get-distro-upgrades.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1709699

Title:
  gpk-update-viewer fails with "Spawn of helper
  'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
  (No such file or directory)"

Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  New

Bug description:
  gpk-update-viewer fails with
  Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' 
failed: failed to spawn 
/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to execute 
child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No 
such file or directory)

  This was detected by Robert Reinsch on a Ubuntu 17.04 system and was
  verified by me on a 17.10 daily build from 2017-08-09

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-packagekit 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  9 21:00:48 2017
  ExecutablePath: /usr/bin/gpk-update-viewer
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gnome-packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+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 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

[Niklas Sombert]

I think this is really a bug in packagekit. On 18.04 I can also trigger
this by just running pkcon get-distro-upgrades in a terminal:

Transaction:Getting upgrades
Status: Waiting in queue
Status: Starting
Status: Finished
Results:
Fatal error: Spawn of helper 
'/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed: failed to 
spawn /usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to 
execute child process 
?/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py?

The problem seems to be that in debian/rules this file is being deleted:

  58   │ # Ubuntu-specific, broken
  59   │ rm -f 
$(INSTALLDIR)/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py


But it is still referenced in backends/aptcc/pk-backend-aptcc.cpp:

 287   │ /**
 288   │  * pk_backend_get_distro_upgrades:
 289   │  */
 290   │ void pk_backend_get_distro_upgrades(PkBackend *backend, PkBackendJob 
*job)
 291   │ {
 292   │ pk_backend_spawn_helper(spawn, job, "get-distro-upgrade.py", 
"get-distro-upgrades", NULL);
 293   │ }

Newer upstream versions of PackageKit (1.1.13) seem to have this file
removed - and also the reference in backends/aptcc/pk-backend-aptcc.cpp.

** Also affects: packagekit (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1709699

Title:
  gpk-update-viewer fails with "Spawn of helper
  'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
  (No such file or directory)"

Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  New

Bug description:
  gpk-update-viewer fails with
  Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' 
failed: failed to spawn 
/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to execute 
child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No 
such file or directory)

  This was detected by Robert Reinsch on a Ubuntu 17.04 system and was
  verified by me on a 17.10 daily build from 2017-08-09

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-packagekit 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  9 21:00:48 2017
  ExecutablePath: /usr/bin/gpk-update-viewer
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gnome-packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+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 1867949] [NEW] It's time to increase the default pid_max from 32768 to avoid PID wraparounds/collossions

[Niklas Edmundsson]

Public bug reported:

The kernel.pid_max sysctl defaults to 32768. This is a very historic
limit to provide compatibility with ancient binaries.

Moving on to the year 2020 multicore CPU:s for desktops, laptops and
servers is the standard, and together with PID randomization wraparound
happens rather quickly on many-core machines with lots of activity.
Wraparounds in itself is not a big issue, but there are corner cases
like scripts that checks if a PID is alive etc that run into trouble if
another process has started using the PID it expects, scripts
(erroneously) using PIDs for work/temporary files, etc.

To avoid problems within the lifetime of Ubuntu Focal, it's time to
increase kernel.pid_max by default in the distribution by including
tuning in a file in /etc/sysctl.d/

Our suggestion is to ship the following tuning by default:

# Make PID-rollover not happen as often.
# Default is 32768
kernel.pid_max = 99

with the following motivation:

1) It achieves a 30-fold increase in the available number-space,
reducing the likelihood of PID wraparound/collisions.

2) It only adds one digit to the PID, so it's still possible to remember
a PID

3) Output in top, ps, etc is still nicely readable

3) We have used it for years on Ubuntu 14.04 and onwards, on 1000+
machines and with a wide array of commercial and scientific software
without any issues.

4) One could argue that it is a preventive security measure, there are a
lot of weirdly written scripts and software out there that behaves badly
upon PID reuse/collissions.

** Affects: procps (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1867949

Title:
  It's time to increase the default pid_max from 32768 to avoid PID
  wraparounds/collossions

Status in procps package in Ubuntu:
  New

Bug description:
  The kernel.pid_max sysctl defaults to 32768. This is a very historic
  limit to provide compatibility with ancient binaries.

  Moving on to the year 2020 multicore CPU:s for desktops, laptops and
  servers is the standard, and together with PID randomization
  wraparound happens rather quickly on many-core machines with lots of
  activity. Wraparounds in itself is not a big issue, but there are
  corner cases like scripts that checks if a PID is alive etc that run
  into trouble if another process has started using the PID it expects,
  scripts (erroneously) using PIDs for work/temporary files, etc.

  To avoid problems within the lifetime of Ubuntu Focal, it's time to
  increase kernel.pid_max by default in the distribution by including
  tuning in a file in /etc/sysctl.d/

  Our suggestion is to ship the following tuning by default:

  # Make PID-rollover not happen as often.
  # Default is 32768
  kernel.pid_max = 99

  with the following motivation:

  1) It achieves a 30-fold increase in the available number-space,
  reducing the likelihood of PID wraparound/collisions.

  2) It only adds one digit to the PID, so it's still possible to
  remember a PID

  3) Output in top, ps, etc is still nicely readable

  3) We have used it for years on Ubuntu 14.04 and onwards, on 1000+
  machines and with a wide array of commercial and scientific software
  without any issues.

  4) One could argue that it is a preventive security measure, there are
  a lot of weirdly written scripts and software out there that behaves
  badly upon PID reuse/collissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867949/+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 682662] Re: pam-auth-update ignores debconf settings

[Niklas Andersson]

...sorry ^^^ - %s/debconf-get-selections/debconf-set-selections/

of course :-)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/682662

Title:
  pam-auth-update ignores debconf settings

Status in dpkg package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Triaged
Status in pam package in Debian:
  Won't Fix

Bug description:
  pam-auth-update ignores the current debconf-settings. This makes it
  impossible to do automatically configure pam in noninteractive
  installations.

  Demonstration:

  ~ # debconf-get-selections | grep libpam-runtime
  libpam-runtimelibpam-runtime/override boolean true
  libpam-runtimelibpam-runtime/conflictserror   
  libpam-runtimelibpam-runtime/no_profiles_chosen   error   
  libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, 
ldap, tmpdir, gnome-keyring, consolekit
  libpam-runtimelibpam-runtime/you-had-no-auth  error   

  ~ # DEBIAN_FRONTEND=noninteractive pam-auth-update

  ~ # debconf-get-selections | grep libpam-runtime
  libpam-runtimelibpam-runtime/override boolean false
  libpam-runtimelibpam-runtime/conflictserror   
  libpam-runtimelibpam-runtime/no_profiles_chosen   error   
  libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, 
winbind, ldap
  libpam-runtimelibpam-runtime/you-had-no-auth  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/682662/+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 682662] Re: pam-auth-update ignores debconf settings

[Niklas Andersson]

This VERY ugly hack works on Ubuntu 18.04...

-- /usr/share/pam-config/mkhomedir -
Default: yes
Priority: 0
Session-Type: Additional
Session:
required pam_mkhomedir.so skel=/etc/skel umask=0027



apt-get install debconf-utils
echo libpam-runtime libpam-runtime/profiles multiselect mkhomedir | 
debconf-get-selections
rm /var/lib/pam/seen
rm /etc/pam.d/common-*
DEBIAN_FRONTEND=noninteractive pam-auth-update --force

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/682662

Title:
  pam-auth-update ignores debconf settings

Status in dpkg package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Triaged
Status in pam package in Debian:
  Won't Fix

Bug description:
  pam-auth-update ignores the current debconf-settings. This makes it
  impossible to do automatically configure pam in noninteractive
  installations.

  Demonstration:

  ~ # debconf-get-selections | grep libpam-runtime
  libpam-runtimelibpam-runtime/override boolean true
  libpam-runtimelibpam-runtime/conflictserror   
  libpam-runtimelibpam-runtime/no_profiles_chosen   error   
  libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, 
ldap, tmpdir, gnome-keyring, consolekit
  libpam-runtimelibpam-runtime/you-had-no-auth  error   

  ~ # DEBIAN_FRONTEND=noninteractive pam-auth-update

  ~ # debconf-get-selections | grep libpam-runtime
  libpam-runtimelibpam-runtime/override boolean false
  libpam-runtimelibpam-runtime/conflictserror   
  libpam-runtimelibpam-runtime/no_profiles_chosen   error   
  libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, 
winbind, ldap
  libpam-runtimelibpam-runtime/you-had-no-auth  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/682662/+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 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.

[Jan Niklas Hasse]

New upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/322

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/410636

Title:
  Right-click should not pre-light first option, too easy to
  accidentally select the first Context-menu option.

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  When I right click in nautilus, the context menu appear. If I right
  click on a menu item, the function of that menu item is performed.
  This is very annoying, because when the context menu appears, the
  mouse is at the first menu item, so if you accidentally right click
  two times, you will surely perform the function of the first menu
  item! Everytime I right click in desktop, i probably create a new
  Folder!

  I think there maybe 2 solutions to this:
  - To perform the function of a menu item, only left click is allowed.
  - When the user right click, the context menu will appear at a bit lower 
position, so the mouse will not be at the first menu item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/410636/+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 1689299] Re: ssh-agent systemd user service failed to start, trying to set environment in Upstart way.

[Niklas Holm]

I don't get why this fix isn't backported to zesty yet since it's such a
trivial fix. I spent hours troubleshooting this before finding the
cause.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1689299

Title:
  ssh-agent systemd user service failed to start, trying to set
  environment in Upstart way.

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  "systemctl --user status ssh-agent.service" give me the following info:
  agent-launch[11327]: initctl: Name "com.ubuntu.Upstart" does not exist

  As I'm running Systemd session instead of Upstart one, it shouldn't
  try to run initctl. So, I take a look at /usr/lib/openssh/agent-
  launcher. And this is what's in the file:

  if type initctl >/dev/null 2>&1; then
  initctl set-env --global SSH_AUTH_SOCK=$S
  fi

  So, the script checks if Upstart is installed, but doesn't actually
  check if the current session is Upstart session or not. It has to
  check if $UPSTART_SESSION is defined or not.

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  $ LANG=C apt policy openssh-client
  openssh-client:
Installed: 1:7.4p1-10
Candidate: 1:7.4p1-10
Version table:
   *** 1:7.4p1-10 500
  500 http://th.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-client 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon May  8 17:51:09 2017
  InstallationDate: Installed on 2013-04-23 (1475 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:7.4p1-10
  SSHClientVersion: OpenSSH_7.4p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-29 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1689299/+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 1686614] Re: MOTD tross upgrade flag on newer systems

[Niklas]

** Package changed: sysvinit (Ubuntu) => update-motd (Ubuntu)

** Summary changed:

- MOTD tross upgrade flag on newer systems 
+ MOTD throws upgrade flag on newer systems

** Description changed:

  Hey,
  
  There is an error in MOTD on Ubuntu 17.04 after upgrade from 16.04 ->
- 16.10 -> 17.04. Which tross updateflag from 12.04. This error shows on
+ 16.10 -> 17.04. Which throws updateflag from 12.04. This error shows on
  startup of every ssh session.
- 
  
  Last login: to. april 27 01:19:42 CEST 2017 from 2a02::f:fff:AA:BB::be41 
on pts/2
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-20-generic x86_64)
  
  Ubuntu 12.04 LTS end-of-life is April 25, 2017 -- Upgrade your Precise 
systems!
-  $ sudo do-release-upgrade -m server
+  $ sudo do-release-upgrade -m server
  
  0 packages can be updated.
  0 updates are security updates.
  
  By the look of "etc/default/motd-news" it it is a curl som staticly
  linked motd https://motd.ubuntu.com which prints this.
  
- 
  Quick fix is setting etc/default/motd-news  | ENABLED to 0.
  
- 
  update-motd:
-   Installed: 3.6-0ubuntu1
-   Candidate: 3.6-0ubuntu1
-   Version table:
-  *** 3.6-0ubuntu1 500
- 500 http://no.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
- 500 http://no.archive.ubuntu.com/ubuntu zesty/main i386 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.6-0ubuntu1
+   Candidate: 3.6-0ubuntu1
+   Version table:
+  *** 3.6-0ubuntu1 500
+ 500 http://no.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
+ 500 http://no.archive.ubuntu.com/ubuntu zesty/main i386 Packages
+ 100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1686614

Title:
  MOTD throws upgrade flag on newer systems

Status in update-motd package in Ubuntu:
  New

Bug description:
  Hey,

  There is an error in MOTD on Ubuntu 17.04 after upgrade from 16.04 ->
  16.10 -> 17.04. Which throws updateflag from 12.04. This error shows
  on startup of every ssh session.

  Last login: to. april 27 01:19:42 CEST 2017 from 2a02::f:fff:AA:BB::be41 
on pts/2
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-20-generic x86_64)

  Ubuntu 12.04 LTS end-of-life is April 25, 2017 -- Upgrade your Precise 
systems!
   $ sudo do-release-upgrade -m server

  0 packages can be updated.
  0 updates are security updates.

  By the look of "etc/default/motd-news" it it is a curl som staticly
  linked motd https://motd.ubuntu.com which prints this.

  Quick fix is setting etc/default/motd-news  | ENABLED to 0.

  update-motd:
    Installed: 3.6-0ubuntu1
    Candidate: 3.6-0ubuntu1
    Version table:
   *** 3.6-0ubuntu1 500
  500 http://no.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://no.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1686614/+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 1686614] [NEW] MOTD tross upgrade flag on newer systems

[Niklas]

Public bug reported:

Hey,

There is an error in MOTD on Ubuntu 17.04 after upgrade from 16.04 ->
16.10 -> 17.04. Which tross updateflag from 12.04. This error shows on
startup of every ssh session.


Last login: to. april 27 01:19:42 CEST 2017 from 2a02::f:fff:AA:BB::be41 on 
pts/2
Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-20-generic x86_64)

Ubuntu 12.04 LTS end-of-life is April 25, 2017 -- Upgrade your Precise systems!
 $ sudo do-release-upgrade -m server

0 packages can be updated.
0 updates are security updates.

By the look of "etc/default/motd-news" it it is a curl som staticly
linked motd https://motd.ubuntu.com which prints this.


Quick fix is setting etc/default/motd-news  | ENABLED to 0.


update-motd:
  Installed: 3.6-0ubuntu1
  Candidate: 3.6-0ubuntu1
  Version table:
 *** 3.6-0ubuntu1 500
500 http://no.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
500 http://no.archive.ubuntu.com/ubuntu zesty/main i386 Packages
100 /var/lib/dpkg/status

** Affects: update-motd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1686614

Title:
  MOTD tross upgrade flag on newer systems

Status in update-motd package in Ubuntu:
  New

Bug description:
  Hey,

  There is an error in MOTD on Ubuntu 17.04 after upgrade from 16.04 ->
  16.10 -> 17.04. Which tross updateflag from 12.04. This error shows on
  startup of every ssh session.


  Last login: to. april 27 01:19:42 CEST 2017 from 2a02::f:fff:AA:BB::be41 
on pts/2
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-20-generic x86_64)

  Ubuntu 12.04 LTS end-of-life is April 25, 2017 -- Upgrade your Precise 
systems!
   $ sudo do-release-upgrade -m server

  0 packages can be updated.
  0 updates are security updates.

  By the look of "etc/default/motd-news" it it is a curl som staticly
  linked motd https://motd.ubuntu.com which prints this.

  
  Quick fix is setting etc/default/motd-news  | ENABLED to 0.

  
  update-motd:
Installed: 3.6-0ubuntu1
Candidate: 3.6-0ubuntu1
Version table:
   *** 3.6-0ubuntu1 500
  500 http://no.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://no.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1686614/+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 1652918] Re: systemd-sysctl crashes when there's a comment at the end of a line

[Niklas Sombert]

This seems to be fixed in systemd 231. (Tested with a recent version of
Fedora.)

-- 
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/1652918

Title:
  systemd-sysctl crashes when there's a comment at the end of a line

Status in systemd package in Ubuntu:
  New

Bug description:
  I have this line in /etc/sysrq.d/10-magic-sysrq.conf:

  kernel.sysrq = 1 #176

  This has worked in Ubuntu 14.04.

  Although there are errors and warnings, the setting seems to be
  applied on boot.

  niklas@panzersperre~> systemctl status systemd-sysctl.service
  ● systemd-sysctl.service - Apply Kernel Variables
 Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Di 2016-12-27 18:31:50 CET; 16h 
ago
   Docs: man:systemd-sysctl.service(8)
 man:sysctl.d(5)
Process: 770 ExecStart=/lib/systemd/systemd-sysctl (code=exited, 
status=1/FAILURE)
   Main PID: 770 (code=exited, status=1/FAILURE)

  Dez 27 18:31:50 panzersperre systemd[1]: Starting Apply Kernel Variables...
  Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Main process 
exited, code=exited, stat
  Dez 27 18:31:50 panzersperre systemd[1]: Failed to start Apply Kernel 
Variables.
  Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Unit entered 
failed state.
  Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Failed with 
result 'exit-code'.

  niklas@panzersperre~> sudo /lib/systemd/systemd-sysctl
  Couldn't write '1 #176' to 'kernel/sysrq', ignoring: Invalid argument

  niklas@panzersperre~> sysctl kernel.sysrq
  kernel.sysrq = 1

  niklas@panzersperre~> lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  niklas@panzersperre~> env LANG=C apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  niklas@panzersperre~> /lib/systemd/systemd-sysctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652918/+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 1652918] [NEW] systemd-sysctl crashes when there's a comment at the end of a line

[Niklas Sombert]

Public bug reported:

I have this line in /etc/sysrq.d/10-magic-sysrq.conf:

kernel.sysrq = 1 #176

This has worked in Ubuntu 14.04.

Although there are errors and warnings, the setting seems to be applied
on boot.

niklas@panzersperre~> systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Di 2016-12-27 18:31:50 CET; 16h ago
 Docs: man:systemd-sysctl.service(8)
   man:sysctl.d(5)
  Process: 770 ExecStart=/lib/systemd/systemd-sysctl (code=exited, 
status=1/FAILURE)
 Main PID: 770 (code=exited, status=1/FAILURE)

Dez 27 18:31:50 panzersperre systemd[1]: Starting Apply Kernel Variables...
Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Main process 
exited, code=exited, stat
Dez 27 18:31:50 panzersperre systemd[1]: Failed to start Apply Kernel Variables.
Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Unit entered 
failed state.
Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Failed with 
result 'exit-code'.

niklas@panzersperre~> sudo /lib/systemd/systemd-sysctl
Couldn't write '1 #176' to 'kernel/sysrq', ignoring: Invalid argument

niklas@panzersperre~> sysctl kernel.sysrq
kernel.sysrq = 1

niklas@panzersperre~> lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

niklas@panzersperre~> env LANG=C apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu13
  Candidate: 229-4ubuntu13
  Version table:
 *** 229-4ubuntu13 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

niklas@panzersperre~> /lib/systemd/systemd-sysctl --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1652918

Title:
  systemd-sysctl crashes when there's a comment at the end of a line

Status in systemd package in Ubuntu:
  New

Bug description:
  I have this line in /etc/sysrq.d/10-magic-sysrq.conf:

  kernel.sysrq = 1 #176

  This has worked in Ubuntu 14.04.

  Although there are errors and warnings, the setting seems to be
  applied on boot.

  niklas@panzersperre~> systemctl status systemd-sysctl.service
  ● systemd-sysctl.service - Apply Kernel Variables
 Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Di 2016-12-27 18:31:50 CET; 16h 
ago
   Docs: man:systemd-sysctl.service(8)
 man:sysctl.d(5)
Process: 770 ExecStart=/lib/systemd/systemd-sysctl (code=exited, 
status=1/FAILURE)
   Main PID: 770 (code=exited, status=1/FAILURE)

  Dez 27 18:31:50 panzersperre systemd[1]: Starting Apply Kernel Variables...
  Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Main process 
exited, code=exited, stat
  Dez 27 18:31:50 panzersperre systemd[1]: Failed to start Apply Kernel 
Variables.
  Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Unit entered 
failed state.
  Dez 27 18:31:50 panzersperre systemd[1]: systemd-sysctl.service: Failed with 
result 'exit-code'.

  niklas@panzersperre~> sudo /lib/systemd/systemd-sysctl
  Couldn't write '1 #176' to 'kernel/sysrq', ignoring: Invalid argument

  niklas@panzersperre~> sysctl kernel.sysrq
  kernel.sysrq = 1

  niklas@panzersperre~> lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  niklas@panzersperre~> env LANG=C apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  niklas@panzersperre~> /lib/systemd/systemd-sysctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652918/+subscriptions

-- 
Mailing l

[Touch-packages] [Bug 1610519] Re: apport-gtk crashes with segmentation fault

[Niklas Edmundsson]

*** This bug is a duplicate of bug 1574886 ***
https://bugs.launchpad.net/bugs/1574886

** This bug has been marked a duplicate of bug 1574886
   All gtk applications Segfault if no GLX context is active

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1610519

Title:
  apport-gtk crashes with segmentation fault

Status in apport package in Ubuntu:
  New

Bug description:
  apport-bug calling apport-gtk crashes with a segmentation fault.

  ~ $ lsb_release -rd
  Description: Ubuntu 16.04.1 LTS
  Release: 16.04
  ~ $ dpkg -l apport-gtk
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  Architecture 
Description
  
+++-===---
  ii  apport-gtk  2.20.1-0ubuntu2.1all  
GTK+ frontend for the apport crash report system

  
  This look related to #1610518.

  
  The backtrace from the core:

  ~ $ apport-bug 
  Segmentation fault (core dumped)
  ~ $ gdb64 /usr/bin/python3 core 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/bin/python3...(no debugging symbols found)...done.

  warning: core file may not match specified executable file.
  [New LWP 4932]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  warning: the debug information found in "/lib64/ld-2.23.so" does not
  match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

  Core was generated by `/usr/bin/python3 /usr/share/apport/apport-gtk'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37

  warning: Source file is more recent than executable.
  37movdqu  (%rdi), %xmm0
  (gdb) backtrace full
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
  No locals.
  #1  0x7f89cc55bf22 in _IO_str_init_static_internal 
(sf=sf@entry=0x7ffc1fa72690, ptr=ptr@entry=0x0, size=size@entry=0, 
pstart=pstart@entry=0x0)
  at strops.c:41
  fp = 0x7ffc1fa72690
  end = 
  #2  0x7f89cc54ab67 in __GI___isoc99_vsscanf (string=0x0, 
format=0x7f89c5e972f2 "%d.%d", args=args@entry=0x7ffc1fa727b8) at 
isoc99_vsscanf.c:41
  ret = -863365216
  sf = {_sbf = {_f = {_flags = -72515584, _IO_read_ptr = 0x0, 
_IO_read_end = 0x0, _IO_read_base = 0x0, _IO_write_base = 0x0, 
_IO_write_ptr = 0x0, _IO_write_end = 0x0, _IO_buf_base = 0x0, 
_IO_buf_end = 0x0, _IO_save_base = 0x0, _IO_backup_base = 0x0, 
_IO_save_end = 0x0, _markers = 0x0, _chain = 0x0, _fileno = 0, 
_flags2 = 0, _old_offset = 71776119061217280, _cur_column = 0, 
_vtable_offset = 0 '\000', _shortbuf = "", _lock = 0x0, _offset 
= 0, _codecvt = 0x0, _wide_data = 0x, 
_freeres_list = 0x0, _freeres_buf = 0xff00ff00, __pad5 
= 18446462598732840960, _mode = -1, 
_unused2 = '\000' }, vtable = 0x7f89cc8a17a0 
<_IO_str_jumps>}, _s = {_allocate_buffer = 0x0, _free_buffer = 0x0}}
  #3  0x7f89cc54ab07 in __isoc99_sscanf (s=, 
format=) at isoc99_sscanf.c:31
  arg = 
  done = -863365216
  #4  0x7f89c5e79d22 in epoxy_glx_version () from 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0
  No symbol table info available.
  #5  0x7f89c8b18509 in gdk_x11_screen_init_gl 
(screen=screen@entry=0xdf6160)
  at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:774
  display = 0xdf1020
  display_x11 = 0xdf1020
  dpy = 0xde3800
  error_base = 172
  event_base = 104
  screen_num = 0
  #6  0x7f89c8b1882a in _gdk_x11_screen_update_visuals_for_gl 
(screen=screen@entry=0xdf6160)
  at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:1114
  x11_screen = 0xdf6160
  display = 0xdf1020
  display_x11 = 0xdf1020

[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Niklas Janz]

** No longer affects: linuxmint

-- 
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/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1577051/+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 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Niklas Janz]

You're the best! Thanks ;-)

-- 
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/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1577051/+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 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Niklas Janz]

Hello Martin.

Although I'm not getting exact "reweive"-crashes with aa-logprof anymore
it still crashed on other similar events:

~# aa-logprof 
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 409, in 
read_log
self.add_event_to_tree(event)
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
e = self.parse_event_for_tree(e)
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 310, in 
parse_event_for_tree
raise AppArmorException(_('Log contains unknown mode %s') % rmask)
apparmor.common.AppArmorException: 'Log contains unknown mode senw reweive'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/aa-logprof", line 50, in 
apparmor.do_logprof_pass(logmark)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
log = log_reader.read_log(logmark)
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 414, in 
read_log
raise AppArmorBug(ex_msg)  # py3-only: from None
apparmor.common.AppArmorBug: Log contains unknown mode senw reweive

This error was caused by the log line:
Jul 29 11:42:05 files kernel: [483212.877816] audit: type=1400 
audit(1469785325.122:21021): apparmor="ALLOWED" operation="file_inherit" 
profile="/usr/bin/nginx-amplify-agent.py//null-/bin/dash" pid=18239 comm="sh" 
laddr=192.168.10.3 lport=50758 faddr=54.153.70.241 fport=443 family="inet" 
sock_type="stream" protocol=6 requested_mask="send receive" denied_mask="send 
receive"

-- 
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/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java"

[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Niklas Janz]

** Attachment added: "apparmor-bugreport-dxclyajj.txt"
   
https://bugs.launchpad.net/apparmor/+bug/1577051/+attachment/4709351/+files/apparmor-bugreport-dxclyajj.txt

-- 
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/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1577051/+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 1211102] Re: Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

[Niklas Keller]

Same issue here. More or less often small disruptions. Seems like those
add up and create the latency. Currently using Ubuntu 15.10. Speaker
works totally fine with my phone.

-- 
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/1211102

Title:
  Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 13.04
  Release:  13.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  bluez:
Instalados: 4.101- 0ubuntu8b1
Candidato:  4.101-0ubuntu8b1
Tabla de versión:
   *** 4.101-0ubuntu8b1 0
  500 http://es.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  The audio always is sync when i listen music on my bluetooth device 
  If i listen music or have a videoconference with skype.. it receive audio 
perfectly without delay.

  4) What happened instead
   I experience a half a second delay when playing audio over Bluetooth with 
A2DP.
  This makes watching movies not possible as the sound is not synchronised with 
the video.

  + If i listen music, then stop about 5 minutes and then restart to listen 
music, it gets work bad.
  + If i get a skype videoconference, it gets too much delay.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Aug 12 01:24:24 2013
  InstallationDate: Installed on 2013-07-13 (29 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer Inc. UX31E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=89d221ec-829a-456e-963d-ec7ac2c7d47d ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash rootfstype=ext4 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 74:2F:68:CE:17:57  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:407502 acl:14820 sco:0 events:8796 errors:0
TX bytes:7391611 acl:8717 sco:0 commands:45 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1211102/+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 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Niklas Janz]

** Also affects: linuxmint
   Importance: Undecided
   Status: New

-- 
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/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed

Bug description:
  Ubuntu 16.04.

  Profiling apache tomcat.
   
  1) aa-genprof on the catalina.sh script that is used to start and stop 
tomcat. 
  2) Start and stop tomcat. 
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1577051/+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 1421923] Re: No notifications for new mails

[Niklas Wenzel]

Hi all,

It took me ages to reply to this thread due to very important personal
issues. Sadly, I can't afford spending time on account-polld right now
as it is too big of a project to handle for me at the moment. Sorry!

However, I have to say that I really like the long-term solution Alberto
proposed here. I'm looking forward to it being implemented some time. :)

Cheers,
Niklas

** Changed in: account-plugins
 Assignee: Niklas Wenzel (nikwen) => (unassigned)

** Changed in: account-plugins (Ubuntu)
     Assignee: Niklas Wenzel (nikwen) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1421923

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Canonical System Image:
  In Progress
Status in Dekko:
  In Progress
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Niklas Janz]

-- 
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/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed

Bug description:
  Ubuntu 16.04.

  Profiling apache tomcat.
   
  1) aa-genprof on the catalina.sh script that is used to start and stop 
tomcat. 
  2) Start and stop tomcat. 
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1577051/+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 1578138] [NEW] 'BadRegion (invalid Region parameter)' causes WM to exit

[Niklas Andersson]

Public bug reported:

Same as https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May  4 12:03:42 2016
DistUpgraded: 2016-04-22 15:24:35,321 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.10, 4.2.0-35-generic, x86_64: installed
 vboxhost, 5.0.10, 4.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 
280X] [1002:6798] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Tahiti XT [Radeon HD 7970/8970 OEM / R9 
280X] [1043:0442]
InstallationDate: Installed on 2014-03-29 (766 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash swapaccount=1 nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
dmi.bios.date: 07/05/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X79-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd07/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May  4 11:51:49 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu xenial

-- 
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/1578138

Title:
  'BadRegion (invalid Region parameter)' causes WM to exit

Status in xorg package in Ubuntu:
  New

Bug description:
  Same as https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May  4 12:03:42 2016
  DistUpgraded: 2016-04-22 15:24:35,321 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.10, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.10, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Tahiti XT [Radeon HD 7970/8970 OEM / R9 
280X] [1043:0442]
  InstallationDate: Installed on 2014-03-29 (766 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineTy

[Touch-packages] [Bug 1565782] Re: APT doesn't respect pin-priority when using APT::Default-Release option

[Niklas Holm]

> This is a feature, so you can pin a release (like backports) to a low
value, but raise it easily if you need to.

I know, except in this case it actually _lowers_ the value.

> It is also explicitly documented in the apt_preferences manpage, which
also mentions a "workaround": Note that this [= the target release
setting] has precedence over any general priority you set in the
/etc/apt/preferences file described later, but not over specifically
pinned packages.

Ok, but specifically naming all packages I want to pin is very
inconvenient if I want it to apply to all packages in that PPA.

It seems to me you simply dismissed my report without trying to
understand my use case. If this is indeed "a feature", imho it's
problematic and should be discussed. Is there any good reason why the
target release setting should lower the priority of a package? The
intuitive thing would be that the priority never gets set below the
manually specified value.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1565782

Title:
  APT doesn't respect pin-priority when using APT::Default-Release
  option

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I'm trying to pin packages from the proprietary graphics drivers PPA,
  and I want APT to use this PPA even if a newer version is available in
  a target release, so I put it at a pin-priority of 999

  --- /etc/apt/preferences.d/graphics-drivers-ppa-pin-999
  Package: *
  Pin: release o=LP-PPA-graphics-drivers
  Pin-Priority: 999
  ---

  If I test this with 'apt-cache policy', the priorities seems to be
  correct.

  ---
  $ apt-cache policy nvidia-346
  nvidia-346:
Installerad: 346.96-0ubuntu0~gpu14.04.2
Kandidat:346.96-0ubuntu0~gpu14.04.2
Versionstabell:
   352.63-0ubuntu0.14.04.1 0
  500 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted 
amd64 Packages
   *** 346.96-0ubuntu0~gpu14.04.2 0
  999 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
  ---

  But if I use the 'APT::Default-Release' configuration option, the
  priority gets lowered to 990, resulting in the wrong candidate.

  ---
  $ apt-cache -o 'APT::Default-Release=trusty' policy nvidia-346
  nvidia-346:
Installerad: 346.96-0ubuntu0~gpu14.04.2
Kandidat:352.63-0ubuntu0.14.04.1
Versionstabell:
   352.63-0ubuntu0.14.04.1 0
  990 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
  990 http://security.ubuntu.com/ubuntu/ trusty-security/restricted 
amd64 Packages
   *** 346.96-0ubuntu0~gpu14.04.2 0
  990 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
  ---

  The same thing happens when using apt-get/aptitude's '-t' flag, i.e.
  the wrong version gets marked for installation. It seems the policy
  engine sets the priority to 990 if the package matches the target
  release, regardless of the previous (higher) value. I think this
  behavior is a bug and should be fixed so that a certain package's
  priority doesn't get lowered for belonging to the target release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.11
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Apr  4 14:11:26 2016
  InstallationDate: Installed on 2014-08-08 (605 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=sv_SE.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1565782/+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 1565782] [NEW] APT doesn't respect pin-priority when using APT::Default-Release option

[Niklas Holm]

Public bug reported:

I'm trying to pin packages from the proprietary graphics drivers PPA,
and I want APT to use this PPA even if a newer version is available in a
target release, so I put it at a pin-priority of 999

--- /etc/apt/preferences.d/graphics-drivers-ppa-pin-999
Package: *
Pin: release o=LP-PPA-graphics-drivers
Pin-Priority: 999
---

If I test this with 'apt-cache policy', the priorities seems to be
correct.

---
$ apt-cache policy nvidia-346
nvidia-346:
  Installerad: 346.96-0ubuntu0~gpu14.04.2
  Kandidat:346.96-0ubuntu0~gpu14.04.2
  Versionstabell:
 352.63-0ubuntu0.14.04.1 0
500 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted amd64 
Packages
 *** 346.96-0ubuntu0~gpu14.04.2 0
999 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ trusty/main 
amd64 Packages
100 /var/lib/dpkg/status
---

But if I use the 'APT::Default-Release' configuration option, the
priority gets lowered to 990, resulting in the wrong candidate.

---
$ apt-cache -o 'APT::Default-Release=trusty' policy nvidia-346
nvidia-346:
  Installerad: 346.96-0ubuntu0~gpu14.04.2
  Kandidat:352.63-0ubuntu0.14.04.1
  Versionstabell:
 352.63-0ubuntu0.14.04.1 0
990 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
990 http://security.ubuntu.com/ubuntu/ trusty-security/restricted amd64 
Packages
 *** 346.96-0ubuntu0~gpu14.04.2 0
990 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ trusty/main 
amd64 Packages
100 /var/lib/dpkg/status
---

The same thing happens when using apt-get/aptitude's '-t' flag, i.e. the
wrong version gets marked for installation. It seems the policy engine
sets the priority to 990 if the package matches the target release,
regardless of the previous (higher) value. I think this behavior is a
bug and should be fixed so that a certain package's priority doesn't get
lowered for belonging to the target release.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.11
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
Uname: Linux 3.13.0-83-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Mon Apr  4 14:11:26 2016
InstallationDate: Installed on 2014-08-08 (605 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=sv_SE.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1565782

Title:
  APT doesn't respect pin-priority when using APT::Default-Release
  option

Status in apt package in Ubuntu:
  New

Bug description:
  I'm trying to pin packages from the proprietary graphics drivers PPA,
  and I want APT to use this PPA even if a newer version is available in
  a target release, so I put it at a pin-priority of 999

  --- /etc/apt/preferences.d/graphics-drivers-ppa-pin-999
  Package: *
  Pin: release o=LP-PPA-graphics-drivers
  Pin-Priority: 999
  ---

  If I test this with 'apt-cache policy', the priorities seems to be
  correct.

  ---
  $ apt-cache policy nvidia-346
  nvidia-346:
Installerad: 346.96-0ubuntu0~gpu14.04.2
Kandidat:346.96-0ubuntu0~gpu14.04.2
Versionstabell:
   352.63-0ubuntu0.14.04.1 0
  500 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted 
amd64 Packages
   *** 346.96-0ubuntu0~gpu14.04.2 0
  999 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
  ---

  But if I use the 'APT::Default-Release' configuration option, the
  priority gets lowered to 990, resulting in the wrong candidate.

  ---
  $ apt-cache -o 'APT::Default-Release=trusty' policy nvidia-346
  nvidia-346:
Installerad: 346.96-0ubuntu0~gpu14.04.2
Kandidat:352.63-0ubuntu0.14.04.1
Versionstabell:
   352.63-0ubuntu0.14.04.1 0
  990 http://se.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
  990 http://security.ubuntu.com/ubuntu/ trusty-security/restricted 
amd64 Packages
   *** 346.96-0ubuntu0~gpu14.04.2 0
  990 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
  ---

  The same thing happens when using apt-get/aptitude's '-t' flag, i.e.
  the wrong version gets marked for installation. It seems the policy
  engine sets the priority to 990 if the package matches the target
  release, re

[Touch-packages] [Bug 1565293] Re: OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted

[Niklas Keller]

Didn't you forget to rehash the certificates? But nevertheless, it's
working without the root and with a fresh rehash.

Found your patch, but didn't find a bug related to the patch. Don't know
whether this should be closed as invalid or duplicate.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1565293

Title:
  OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Google has it's own certificate authority "Google Internet Authority
  G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate
  is already in the trust stores, but it's cross-signed by an older root
  named "Equifax Secure Certificate Authority".

  The Equifax uses a 1024 bit private key and has therefore been removed
  by Mozilla in their library (NSS), see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1156844.

  Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and
  1024 bit keys are no longer safe enough, so the root has been excluded
  from their root program. However, Ubuntu 12.04 and 14.04 do still ship
  with that root in their trust store.

  A bug in the currently default OpenSSL 1.0.1f (at least in 14.04)
  causes OpenSSL to error if that root is missing, even if the previous
  root certificate "GeoTrust Global CA" is already in the root and
  therefore trusted. It seems like it doesn't stop on the first trusted
  certificate but instead requires a complete chain, so requires the
  "Equifax Secure Certificate Authority" to be in the trust store. That
  behavior is fixed in OpenSSL 1.0.2.

  All 1024 bit roots should be removed from the default trust stores as
  soon as possible. For this to work, the OpenSSL bug has to be
  backported first.

  If this is not going to be fixed, at least in 2018, we'll have an
  issue, because that's the date where "Equifax Secure Certificate
  Authority" will expire. If Google and various other sites will not
  change their root to be non-cross-signed, many connections will break
  and fail.

  Domains I know to use old cross-signed certificates: google.com,
  yahoo.com. I didn't do any scans, those were just the first two I
  tried.

  The following will happen on Aug 22 2018 without a fix:

  kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet 
-verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs
  depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority
  verify error:num=10:certificate has expired
  notAfter=Aug 22 16:41:51 2018 GMT
  verify return:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1565293/+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 1565293] Re: OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted

[Niklas Keller]

We originally encountered that issue on Travis. After I couldn't
reproduce it locally on my 15.10 machine, I downloaded Ubuntu Server
14.04 and could verify it in a VM. Seems like I forgot to install the
latest updates, verified it's fixed in the latest version.

I'll notify the Travis team, so they can update their images.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1565293

Title:
  OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Google has it's own certificate authority "Google Internet Authority
  G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate
  is already in the trust stores, but it's cross-signed by an older root
  named "Equifax Secure Certificate Authority".

  The Equifax uses a 1024 bit private key and has therefore been removed
  by Mozilla in their library (NSS), see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1156844.

  Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and
  1024 bit keys are no longer safe enough, so the root has been excluded
  from their root program. However, Ubuntu 12.04 and 14.04 do still ship
  with that root in their trust store.

  A bug in the currently default OpenSSL 1.0.1f (at least in 14.04)
  causes OpenSSL to error if that root is missing, even if the previous
  root certificate "GeoTrust Global CA" is already in the root and
  therefore trusted. It seems like it doesn't stop on the first trusted
  certificate but instead requires a complete chain, so requires the
  "Equifax Secure Certificate Authority" to be in the trust store. That
  behavior is fixed in OpenSSL 1.0.2.

  All 1024 bit roots should be removed from the default trust stores as
  soon as possible. For this to work, the OpenSSL bug has to be
  backported first.

  If this is not going to be fixed, at least in 2018, we'll have an
  issue, because that's the date where "Equifax Secure Certificate
  Authority" will expire. If Google and various other sites will not
  change their root to be non-cross-signed, many connections will break
  and fail.

  Domains I know to use old cross-signed certificates: google.com,
  yahoo.com. I didn't do any scans, those were just the first two I
  tried.

  The following will happen on Aug 22 2018 without a fix:

  kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet 
-verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs
  depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority
  verify error:num=10:certificate has expired
  notAfter=Aug 22 16:41:51 2018 GMT
  verify return:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1565293/+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 1565293] [NEW] OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted

[Niklas Keller]

Public bug reported:

Google has it's own certificate authority "Google Internet Authority
G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate is
already in the trust stores, but it's cross-signed by an older root
named "Equifax Secure Certificate Authority".

The Equifax uses a 1024 bit private key and has therefore been removed
by Mozilla in their library (NSS), see
https://bugzilla.mozilla.org/show_bug.cgi?id=1156844.

Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and
1024 bit keys are no longer safe enough, so the root has been excluded
from their root program. However, Ubuntu 12.04 and 14.04 do still ship
with that root in their trust store.

A bug in the currently default OpenSSL 1.0.1f (at least in 14.04) causes
OpenSSL to error if that root is missing, even if the previous root
certificate "GeoTrust Global CA" is already in the root and therefore
trusted. It seems like it doesn't stop on the first trusted certificate
but instead requires a complete chain, so requires the "Equifax Secure
Certificate Authority" to be in the trust store. That behavior is fixed
in OpenSSL 1.0.2.

All 1024 bit roots should be removed from the default trust stores as
soon as possible. For this to work, the OpenSSL bug has to be backported
first.

If this is not going to be fixed, at least in 2018, we'll have an issue,
because that's the date where "Equifax Secure Certificate Authority"
will expire. If Google and various other sites will not change their
root to be non-cross-signed, many connections will break and fail.

Domains I know to use old cross-signed certificates: google.com,
yahoo.com. I didn't do any scans, those were just the first two I tried.

The following will happen on Aug 22 2018 without a fix:

kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet 
-verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs
depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority
verify error:num=10:certificate has expired
notAfter=Aug 22 16:41:51 2018 GMT
verify return:0

** Affects: openssl (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1565293

Title:
  OpenSSL 1.0.1 fails to recognize cross-signed roots as trusted

Status in openssl package in Ubuntu:
  New

Bug description:
  Google has it's own certificate authority "Google Internet Authority
  G2", which is signed by "GeoTrust Global CA". GeoTrust's certificate
  is already in the trust stores, but it's cross-signed by an older root
  named "Equifax Secure Certificate Authority".

  The Equifax uses a 1024 bit private key and has therefore been removed
  by Mozilla in their library (NSS), see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1156844.

  Issuance from 1024 bit roots has been stopped in 2010 or 2011 IIRC and
  1024 bit keys are no longer safe enough, so the root has been excluded
  from their root program. However, Ubuntu 12.04 and 14.04 do still ship
  with that root in their trust store.

  A bug in the currently default OpenSSL 1.0.1f (at least in 14.04)
  causes OpenSSL to error if that root is missing, even if the previous
  root certificate "GeoTrust Global CA" is already in the root and
  therefore trusted. It seems like it doesn't stop on the first trusted
  certificate but instead requires a complete chain, so requires the
  "Equifax Secure Certificate Authority" to be in the trust store. That
  behavior is fixed in OpenSSL 1.0.2.

  All 1024 bit roots should be removed from the default trust stores as
  soon as possible. For this to work, the OpenSSL bug has to be
  backported first.

  If this is not going to be fixed, at least in 2018, we'll have an
  issue, because that's the date where "Equifax Secure Certificate
  Authority" will expire. If Google and various other sites will not
  change their root to be non-cross-signed, many connections will break
  and fail.

  Domains I know to use old cross-signed certificates: google.com,
  yahoo.com. I didn't do any scans, those were just the first two I
  tried.

  The following will happen on Aug 22 2018 without a fix:

  kelunik@example:~$ faketime '2018-08-23 00:00:00' openssl s_client -quiet 
-verify_return_error -connect google.com:443 -CApath /usr/lib/ssl/certs
  depth=3 C = US, O = Equifax, OU = Equifax Secure Certificate Authority
  verify error:num=10:certificate has expired
  notAfter=Aug 22 16:41:51 2018 GMT
  verify return:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1565293/+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 1554189] Re: Can no longer swipe between scope results

[Niklas Wenzel]

Thank you, Jean-Baptiste, for agreeing that this still makes sense to
have! :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1554189

Title:
  Can no longer swipe between scope results

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Until a few days ago, when browsing through an RSS feed scope, it was
  possible to switch to the previous/next article by using swipe
  gestures. This does no longer work for me now and basically makes RSS
  feed scopes useless, as I do not want to click on each article and
  then go back to the overview again just to browse through the article
  summaries.

  $ system-image-cli -i
  current build number: 382
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-05 18:18:13
  version version: 382
  version ubuntu: 20160305
  version device: 20160304.2
  version custom: 20160305

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554189/+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 1554189] [NEW] Can no longer swipe between scope results

[Niklas Wenzel]

Public bug reported:

Until a few days ago, when browsing through an RSS feed scope, it was
possible to switch to the previous/next article by using swipe gestures.
This does no longer work for me now and basically makes RSS feed scopes
useless, as I do not want to click on each article and then go back to
the overview again just to browse through the article summaries.

$ system-image-cli -i
current build number: 382
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-03-05 18:18:13
version version: 382
version ubuntu: 20160305
version device: 20160304.2
version custom: 20160305

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1554189

Title:
  Can no longer swipe between scope results

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Until a few days ago, when browsing through an RSS feed scope, it was
  possible to switch to the previous/next article by using swipe
  gestures. This does no longer work for me now and basically makes RSS
  feed scopes useless, as I do not want to click on each article and
  then go back to the overview again just to browse through the article
  summaries.

  $ system-image-cli -i
  current build number: 382
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-05 18:18:13
  version version: 382
  version ubuntu: 20160305
  version device: 20160304.2
  version custom: 20160305

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554189/+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 1442670] Re: Ubuntu Phone BQ: Camera makes blur images

[Niklas Wenzel]

I just tested capturing some text documents on my Nexus 4 today and it
really  improved. Might be a good day or it has been fixed for me. Let's
see if it comes back again in the future. Thank you anyway. :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1442670

Title:
  Ubuntu Phone BQ: Camera makes blur images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Hi!
  A lot of times the camera is getting a really bad images (blur effect) in all 
resolutions.

  And yes, I click previously for a focus.

  I'm sending you an example: That picture looked perfect in the mobile,
  but in the PC is really bad :(

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442670/+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 1537248] Re: Disabling haptics in the system settings only affects Unity8 and a few system apps

[Niklas Wenzel]

*** This bug is a duplicate of bug 1433590 ***
https://bugs.launchpad.net/bugs/1433590

Zsombor, although I'm late to the party, I'd like to say thank you for
linking me to the other bug. This way I can focus on other bugs again.
:)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1537248

Title:
  Disabling haptics in the system settings only affects Unity8 and a few
  system apps

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:

  1) Uncheck "Other vibrations" in System Settings > Sound
  2) Open the dialer and press a few buttons
  3) You will notice that the phone does not vibrate when pressing a button
  4) Now open the clock app and press a few buttons
  5) The selection in the system settings does not seem to affect the clock app 
and the phone still vibrates when pressing an AbstractButton or a derived item

  Components to which the setting does apply:

  * Unity 8
  * System Settings
  * Dialer
  * Messaging app
  * Address book

  Components to which it does NOT apply:

  * Webbrowser
  * Camera
  * Clock
  * Terminal app
  * File manager
  * Document viewer
  * Any click app from the store which I have tried so far

  Debugging efforts so far:

  I have added a few console.log() calls and saw that in Haptics.qml,
  when the play() method is called, vibra.otherVibrate is true. So it
  seems as if the ServiceProperties object fails to fetch the proper
  value when running the aforementioned apps.

  A few observations:

  * All apps for which it works are legacy (e.g. non-click) applications.
  * However, the webbrowser app is a legacy one, too, but it doesn't work there.
  * All apps for which it works run unconfined.
  * However, the terminal and the file manager apps are unconfined, too.
  * The apps for which it works seem to use the most recent UITK version.
  * However, the document viewer does that as well.

  
  =

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 218
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-21 23:18:06
  version version: 218
  version ubuntu: 20160121.2
  version device: 20160112
  version custom: mako-1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1537248/+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 1537248] Re: Disabling haptics in the system settings only affects Unity8 and a few system apps

[Niklas Wenzel]

Any help/hints on how to fix this would be greatly appreciated. We first
observed this in the calculator app and really want to fix this. (LP:
#1428606)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1537248

Title:
  Disabling haptics in the system settings only affects Unity8 and a few
  system apps

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:

  1) Uncheck "Other vibrations" in System Settings > Sound
  2) Open the dialer and press a few buttons
  3) You will notice that the phone does not vibrate when pressing a button
  4) Now open the clock app and press a few buttons
  5) The selection in the system settings does not seem to affect the clock app 
and the phone still vibrates when pressing an AbstractButton or a derived item

  Components to which the setting does apply:

  * Unity 8
  * System Settings
  * Dialer
  * Messaging app
  * Address book

  Components to which it does NOT apply:

  * Webbrowser
  * Camera
  * Clock
  * Terminal app
  * File manager
  * Document viewer
  * Any click app from the store which I have tried so far

  Debugging efforts so far:

  I have added a few console.log() calls and saw that in Haptics.qml,
  when the play() method is called, vibra.otherVibrate is true. So it
  seems as if the ServiceProperties object fails to fetch the proper
  value when running the aforementioned apps.

  A few observations:

  * All apps for which it works are legacy (e.g. non-click) applications.
  * However, the webbrowser app is a legacy one, too, but it doesn't work there.
  * All apps for which it works run unconfined.
  * However, the terminal and the file manager apps are unconfined, too.
  * The apps for which it works seem to use the most recent UITK version.
  * However, the document viewer does that as well.

  
  =

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 218
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-21 23:18:06
  version version: 218
  version ubuntu: 20160121.2
  version device: 20160112
  version custom: mako-1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1537248/+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 1537248] [NEW] Disabling haptics in the system settings only affects Unity8 and a few system apps

[Niklas Wenzel]

Public bug reported:

How to reproduce:

1) Uncheck "Other vibrations" in System Settings > Sound
2) Open the dialer and press a few buttons
3) You will notice that the phone does not vibrate when pressing a button
4) Now open the clock app and press a few buttons
5) The selection in the system settings does not seem to affect the clock app 
and the phone still vibrates when pressing an AbstractButton or a derived item

Components to which the setting does apply:

* Unity 8
* System Settings
* Dialer
* Messaging app
* Address book

Components to which it does NOT apply:

* Webbrowser
* Camera
* Clock
* Terminal app
* File manager
* Document viewer
* Any click app from the store which I have tried so far

Debugging efforts so far:

I have added a few console.log() calls and saw that in Haptics.qml, when
the play() method is called, vibra.otherVibrate is true. So it seems as
if the ServiceProperties object fails to fetch the proper value when
running the aforementioned apps.

A few observations:

* All apps for which it works are legacy (e.g. non-click) applications.
* However, the webbrowser app is a legacy one, too, but it doesn't work there.
* All apps for which it works run unconfined.
* However, the terminal and the file manager apps are unconfined, too.
* The apps for which it works seem to use the most recent UITK version.
* However, the document viewer does that as well.


=

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 218
device name: mako
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-01-21 23:18:06
version version: 218
version ubuntu: 20160121.2
version device: 20160112
version custom: mako-1.1

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
     Assignee: Niklas Wenzel (nikwen)
 Status: In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Niklas Wenzel (nikwen)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1537248

Title:
  Disabling haptics in the system settings only affects Unity8 and a few
  system apps

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:

  1) Uncheck "Other vibrations" in System Settings > Sound
  2) Open the dialer and press a few buttons
  3) You will notice that the phone does not vibrate when pressing a button
  4) Now open the clock app and press a few buttons
  5) The selection in the system settings does not seem to affect the clock app 
and the phone still vibrates when pressing an AbstractButton or a derived item

  Components to which the setting does apply:

  * Unity 8
  * System Settings
  * Dialer
  * Messaging app
  * Address book

  Components to which it does NOT apply:

  * Webbrowser
  * Camera
  * Clock
  * Terminal app
  * File manager
  * Document viewer
  * Any click app from the store which I have tried so far

  Debugging efforts so far:

  I have added a few console.log() calls and saw that in Haptics.qml,
  when the play() method is called, vibra.otherVibrate is true. So it
  seems as if the ServiceProperties object fails to fetch the proper
  value when running the aforementioned apps.

  A few observations:

  * All apps for which it works are legacy (e.g. non-click) applications.
  * However, the webbrowser app is a legacy one, too, but it doesn't work there.
  * All apps for which it works run unconfined.
  * However, the terminal and the file manager apps are unconfined, too.
  * The apps for which it works seem to use the most recent UITK version.
  * However, the document viewer does that as well.

  
  =

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 218
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-21 23:18:06
  version version: 218
  version ubuntu: 20160121.2
  version device: 20160112
  version custom: mako-1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1537248/+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 1395118] Re: ActionSelectionPopover does not handle the 'visible' property of actions properly

[Niklas Wenzel]

** Changed in: ubuntu-filemanager-app
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1395118

Title:
  ActionSelectionPopover does not handle the 'visible' property of
  actions properly

Status in Canonical System Image:
  Fix Released
Status in Ubuntu File Manager App:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
  New
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Fix Released

Bug description:
  When setting the 'visible' property of an action in an ActionList of
  an ActionSelectionPopover to false, the delegate will not be hidden
  but instead be shown at the top of the list behind the first visible
  delegate. (Check out the screenshot.)

  Demo code (containing an outcommented workaround):

  import QtQuick 2.3
  import Ubuntu.Components 1.1
  import Ubuntu.Components.Popups 1.0
  import Ubuntu.Components.ListItems 1.0

  MainView {
  width: units.gu(50)
  height: units.gu(75)

  Page {
  title: i18n.tr("ActionSelectionPopover Fix")

  Button {
  id: button
  width: parent.width

  text: i18n.tr("Show popover")

  onClicked: {
  PopupUtils.open(actionSelectionPopoverComponent, button)
  }
  }

  Component {
  id: actionSelectionPopoverComponent

  ActionSelectionPopover {
  actions: ActionList {
  Action {
  text: "Action one"
  }
  Action {
  text: "Action two"
  }
  Action {
  text: "Hidden action"
  visible: false
  }
  }

  // Uncomment the following for a temporary workaround:

  //delegate: Empty {
  //id: listItem
  //Label {
  //text: listItem.text
  //anchors {
  //verticalCenter: parent.verticalCenter
  //horizontalCenter: parent.horizontalCenter
  //}
  //wrapMode: Text.Wrap
  //color: Theme.palette.normal.overlayText
  //}
  ///*! \internal */
  //onTriggered: popover.hide()
  //visible: enabled && ((action === undefined) || 
action.visible)
  //height: visible ? implicitHeight : 0
  //}
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1395118/+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 1417261] Re: On app removal, account access permissions persist

[Niklas Wenzel]

Thanks, Alberto. :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1417261

Title:
  On app removal, account access permissions persist

Status in Online Accounts setup for Ubuntu Touch:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1) Install an app which uses online accounts.
  2) Uninstall it.
  3) Reinstall the application OR ANOTHER APP WITH THE SAME NAMESPACE and it 
will still be able to access the online account.

  I could see this being used for phishing when the user is asked to manually 
install a click package with the same namespace as another app, which would 
then allow bad entities to have access to the online accounts of the original 
app.
  It could either be presented as a completely seperate app when the user has 
removed the original one or as an "official version" by the people doing the 
phishing.

  Therefore, I vote for removing account information from apps when they
  are uninstalled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1417261/+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 1421923] Re: No notifications for new mails

[Niklas Wenzel]

Ok, I spent some time on replacing the golang.org/x/text package with
the packaged one from the archives today and discovered that the package
is only available for wily at the moment. Thus, I'll revert those
changes and keep its source code in place.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1421923

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Dekko:
  Triaged
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1421923] Re: No notifications for new mails

[Niklas Wenzel]

Wow, Alberto! I didn't expect anyone to have a look at the code that
fast!

I agree that OAuth authentication for Gmail in connection with using the
Gmail accounts plugin would be great. Having a quick look at the Gmail
docs, I also think that our IMAP library should be compatible with it.
However, as we already have working Gmail notifications using OAuth in
the images (although not open to third-party developers at the moment),
I'd like to postpone this after we have released the normal password
authentication IMAP notifications into the wild as they are supported by
basically all IMAP servers.

Furthermore, thank you for the link to the SASL plugin. As that part is
being dealt with by our IMAP library though, I don't think it will be
too useful here.

The data files you found are indeed from libraries for character
encoding. I noticed a few days ago that we can import some of the
libraries via Debian packages that are already in the Ubuntu archives so
that should reduce that part of the code.

Thanks again! :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1421923

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Dekko:
  Triaged
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1421923] Re: No notifications for new mails

[Niklas Wenzel]

As a reference for all of those who didn't see the blog post:
http://nikwen.github.io/ubuntu/2015/09/17/my-work-on-email-
notifications.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1421923

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Dekko:
  Triaged
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1421923] Re: No notifications for new mails

[Niklas Wenzel]

Hey Dan,

I didn't know about that rfc yet! Let me dig into it a big more to check
if we can support that. What I can definitely say is that we can add the
message partid to the URI. If that is helpful, this shouldn't be a
problem. ;)

The application for which the notification is being displayed is the one
which the user authorizes the online account for. What I need to check
myself is whether the URI from the notification is then sent directly to
the application or if other apps can "compete" for it as well. If the
former is true, the situation is clear. If the second one is what
happens, then the new UI you mentioned should be used automatically by
the URI dispatcher. To be honest, I'd prefer the first one as in that
case the user could simply give another application access to the
account if they wanted it to receive email notifications.

The reason why I wanted to put the app id in there was to enable
applications to filter for "their" notifications in case they want to
use different email clients for different accounts (e.g. the Gmail app
for a Gmail one and Dekko for their Yahoo account). This would only be
needed in the second case outlined above though.

I'll look into the questions brought up here. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1421923

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Dekko:
  Triaged
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1421923] Re: No notifications for new mails

[Niklas Wenzel]

Thought I'd let you know I've been working on this for some time now. The 
current version is far from ready but it can already display notifications for 
incoming emails.
You can follow my progress on Google Plus if you want: 
https://plus.google.com/u/0/101390620047921378812/posts

** Also affects: account-polld (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: account-polld (Ubuntu)
 Assignee: (unassigned) => Niklas Wenzel (nikwen)

** Changed in: account-polld (Ubuntu)
   Status: New => In Progress

** Also affects: account-plugins (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: account-plugins (Ubuntu)
   Status: New => In Progress

** Changed in: account-plugins (Ubuntu)
 Assignee: (unassigned) => Niklas Wenzel (nikwen)

** Also affects: account-plugins
   Importance: Undecided
   Status: New

** Changed in: account-plugins
 Assignee: (unassigned) => Niklas Wenzel (nikwen)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1421923

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Dekko:
  Triaged
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Niklas Keller]

Unfortunately, it only fixed it in the first reboot. The one now had
that problem again, even with vivid-proposed.

-- 
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/1464917

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Niklas Keller]

I can confirm that updating to vivid-proposed fixes that behavior.

-- 
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/1464917

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Niklas Keller]

** Changed in: systemd (Ubuntu)
   Status: Expired => Confirmed

-- 
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/1464917

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

Here's the bug report for that:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1484664

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1484664] [NEW] Visual feadback when the message one is writing is going to be split into multiple ones

[Niklas Wenzel]

Public bug reported:

It would be nice to have some sort of visual indication when the message
we are currently writing is going to be broken down into multiple SMS
because it is too long. That would help those of us who are on prepaid
plans save some money.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  It would be nice to have some sort of visual indication when the message
  we are currently writing is going to be broken down into multiple SMS
- because it is too long. That would help those of us who have prepaid
+ because it is too long. That would help those of us who are on prepaid
  plans save some money.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1484664

Title:
  Visual feadback when the message one is writing is going to be split
  into multiple ones

Status in messaging-app package in Ubuntu:
  New

Bug description:
  It would be nice to have some sort of visual indication when the
  message we are currently writing is going to be broken down into
  multiple SMS because it is too long. That would help those of us who
  are on prepaid plans save some money.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1484664/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

Ok, forget about this! I just found something out. Using some special 
characters (including some accents included in the name of the messages' 
recipient) lowers the character count per message to 70!!!
With that in mind, the length of each message perfectly translates to its 
costs. Sorry for all the inconvenience caused by this bug report!
I just wish we had some way to tell when messages get broken into multiple ones.

Anyway, thanks a lot for your help!!!

** Changed in: telephony-service (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

Ok, it looks like I need to correct something here. The messages
actually had to be splitted into multiple smaller ones. However, the
number of messages being sent according to the provider is still too
high.

The one from August 10 had 356 chars, the one from August 11 had 334
ones, so with 160 characters per message both should have fitted into 3
messages each if I'm not mistaken, right?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

Oh, and I decided to send you the syslog via email as it is simply to
long to go through looking for information to censor. While it doesn't
contain the part from August 10, it contains the part when the issue
appeared yesterday.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

@Alfonso, here you go. :)
I x-ed out all phone numbers and all personal identifiers.

** Attachment added: "upload.tar"
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443509/+files/upload.tar

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

@Alfonso Thanks. :)
I just built the tar file and will x out any personal information when I come 
home and then upload them.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

@Alfonso, It's not that I can't but that I don't want to upload all of
my application logs. So which ones do you need?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

@Alfonso, I'll do that later today. Thank you for your reply. :)
What logs from ~/.cache/upstart/ do you need? There are so many in there...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

Yes, that's true. Instead, there is an "assertion failed" block less
than 5 secons after each SMS that shows up in the web interface.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

And it just happened again. I think I'll stop using my phone for SMS
now!

** Attachment added: "again.png"
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443024/+files/again.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

Here's the new screenshot from my provider.

** Attachment added: "provider.png"
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443015/+files/provider.png

** Description changed:

- When sending text messages, Ubuntu displays the loading spinner forever.
- In the provider's monthly reports, I can see that the message has been
- sent multiple times, even though I only sent one message to one
- recipient and the message was short enough not to be broken into
- separate ones.
- 
+ When sending text messages, Ubuntu displays the loading spinner for a
+ very long time. In the provider's monthly reports, I can see that the
+ message has been sent multiple times, even though I only sent one
+ message to one recipient and the message was short enough not to be
+ broken into separate ones.
  
  === Old description: ===
  
  When having a bad network connection, Ubuntu tries to send SMS multiple
  times but fails to recognize which messages have already been sent,
  resulting in very high costs due to the same message actually being sent
  several times.
  
  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.
  
  ==
  
  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

(Btw, I'm using a SIM card from the German provider "Aldi Talk".)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times

[Niklas Wenzel]

Here's the log. (I x-ed out what I thought were some personal
identifiers.)

** Attachment added: "radio.out"
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4443013/+files/radio.out

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner for a
  very long time. In the provider's monthly reports, I can see that the
  message has been sent multiple times, even though I only sent one
  message to one recipient and the message was short enough not to be
  broken into separate ones.

  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

This happened again yesterday. With GOOD network connection!!! But this
time I was able to fetch the log file using the command Matthias posted.

** Description changed:

+ When sending text messages, Ubuntu displays the loading spinner forever.
+ In the provider's monthly reports, I can see that the message has been
+ sent multiple times, even though I only sent one message to one
+ recipient and the message was short enough not to be broken into
+ separate ones.
+ 
+ 
+ === Old description: ===
+ 
  When having a bad network connection, Ubuntu tries to send SMS multiple
  times but fails to recognize which messages have already been sent,
  resulting in very high costs due to the same message actually being sent
  several times.
  
  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.
  
  ==
  
  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

** Summary changed:

- High costs due to SMS being sent multiple times when having a bad network 
connection
+ High costs due to SMS being sent multiple times

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When sending text messages, Ubuntu displays the loading spinner
  forever. In the provider's monthly reports, I can see that the message
  has been sent multiple times, even though I only sent one message to
  one recipient and the message was short enough not to be broken into
  separate ones.

  
  === Old description: ===

  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1372051] Re: ntp postinst user/group add commands are not idempotent

[Niklas Ögren]

Ryan,

Yes you are right. My passwd/group files has been alive for a long time
..

Case can be closed.

/n

Quoting Ryan Harper <1372...@bugs.launchpad.net>:

> addgroup is a perl script, so you can inspect it to see what's going on.
> You can get additional information about the error running with:
>
> sudo VERBOSE=1 addgroup --system ntp
>
> I think what we're seeing is that your ntp group is a user group (gid >=
> 1000) instead of a system group (gid < 1000).
>
>> From your output above, it looks like you're hitting this logic:
>
>
> if ($action eq "addsysgroup") {
>
> # Check if requested group already exists and we can exit safely
> my $ret = existing_group_ok($new_name, $new_gid);
>
> if ($ret == 3) {
> print STDERR "$0: " if $verbose;
> printf STDERR (gtx("The group `%s' already exists as a  
> system group. Exiting.\n"), $new_name) if $verbose;
> exit RET_OK;
> }
>
> if ($ret == 1) {
> print STDERR "$0: " if $verbose;
> printf STDERR (gtx("The group `%s' already exists and is not  
> a system group. Exiting.\n"), $new_name) if $verbose;
> exit RET_OBJECT_ALREADY_EXISTS;
> }
>
>
> So, you're exiting 1 due to the gid of group ntp being > 1000.  The  
> fix here would be to apt-get remove --purge ntp ; the --purge flag  
> will trigger the ntp.postrm script to remove the group first.  Then  
> when you re-install, it will install the ntp group with --system  
> flag and allocate a GID under <1000.
>
> See if that helps you moving forward.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1372051
>
> Title:
>   ntp postinst user/group add commands are not idempotent
>
> Status in ntp package in Ubuntu:
>   Incomplete
>
> Bug description:
>   At do release upgrade from 12.04.05 to 14.04.01, the ntp package failed:
>   Errors were encountered while processing:
>ntp
>   Error in function:
>
>
>   A fatal error occurred
>
>   Please report this as a bug and include the files
>   /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
>   your report. The upgrade has aborted.
>   Your original sources.list was saved in
>   /etc/apt/sources.list.distUpgrade.
>
>   SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
>
>
>   Could not install the upgrades
>
>   The upgrade has aborted. Your system could be in an unusable state. A
>   recovery will run now (dpkg --configure -a).
>
>   Please report this bug in a browser at
>   http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug
>   and attach the files in /var/log/dist-upgrade/ to the bug report.
>   installArchives() failed
>
>   Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2) ...
>   dpkg: error processing package ntp (--configure):
>subprocess installed post-installation script returned error exit status 1
>   Errors were encountered while processing:
>ntp
>
>   Upgrade complete
>
>   The upgrade has completed but there were errors during the upgrade
>   process.
>
>
>   In /var/lib/dpkg/info/ntp.postinst the add group / adduser  
> commands fail due to already existing group / user.
>   Appended “ || /bin/true” to those lines, and “dpkg —configure ntp”  
> succeeded.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1372051/+subscriptions


-- 
/n

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1372051

Title:
  ntp postinst user/group add commands are not idempotent

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  At do release upgrade from 12.04.05 to 14.04.01, the ntp package failed:
  Errors were encountered while processing:
   ntp
  Error in function: 

  
  A fatal error occurred 

  Please report this as a bug and include the files 
  /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in 
  your report. The upgrade has aborted. 
  Your original sources.list was saved in 
  /etc/apt/sources.list.distUpgrade. 

  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)


  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  Please report this bug in a browser at 
  http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
  and attach the files in /var/log/dist-upgrade/ to the bug report. 
  installArchives() failed 

  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2) ...
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade 
  process. 


  In /var/lib/dpkg/info/ntp.postinst the add group / adduser commands fail d

Re: [Touch-packages] [Bug 1372051] Re: ntp postinst user/group add commands are not idempotent

[Niklas Ögren]

Ryan,

no@trillian:~$ cat /etc/issue
Ubuntu 14.04.2 LTS \n \l

no@trillian:~$ dpkg --list | grep ntp
ii  ntp  1:4.2.6.p5+dfsg-3ubuntu2.14.04.3   
  amd64Network Time Protocol daemon and utility programs
ii  ntpdate  1:4.2.6.p5+dfsg-3ubuntu2.14.04.3   
  amd64client for setting system time from NTP servers
no@trillian:~$ grep ntp /etc/group
ntp:x:1004:
no@trillian:~$ sudo addgroup --system --quiet ntp; echo $?
1


I have run this on the 12.04 system as well, most likely, during that upgrade. 
But I also saw this issue when updating my 14.04 system, when there was a 
security patch on ntp. (Using apt-get upgrade)

no@trillian:~$ which addgroup
/usr/sbin/addgroup
no@trillian:~$ addgroup --version
adduser version 3.113+nmu3ubuntu3

Adds a user or group to the system.
  
Copyright (C) 1997, 1998, 1999 Guy Maor 
Copyright (C) 1995 Ian Murdock ,
   Ted Hajek 

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version.

This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
General Public License, /usr/share/common-licenses/GPL, for more details.
no@trillian:~$ dpkg -S /usr/sbin/addgroup 
adduser: /usr/sbin/addgroup
no@trillian:~$ dpkg -l adduser
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture   
 Description
+++--===-===-==
ii  adduser  3.113+nmu3ubuntu3   all
 add and remove users and groups

/n

> On 04 Aug 2015, at 23:09, Ryan Harper <1372...@bugs.launchpad.net> wrote:
> 
> This command:
> 
> addgroup --system --quiet ntp
> 
> is idempotent on default precise systems, so it's not quite clear why it
> fails on your system.  Maybe it's possible to do some debugging on
> running that command.
> 
> ubuntu@ubuntu:~$ cat /etc/issue
> Ubuntu 12.04.5 LTS \n \l
> 
> ubuntu@ubuntu:~$ dpkg --list | grep ntp
> ii  ntp  1:4.2.6.p3+dfsg-1ubuntu3.4
> Network Time Protocol daemon and utility programs
> ii  ntpdate  1:4.2.6.p3+dfsg-1ubuntu3.4client 
> for setting system time from NTP servers
> ubuntu@ubuntu:~$ grep ntp /etc/group
> ntp:x:112:
> ubuntu@ubuntu:~$ sudo addgroup --system --quiet ntp; echo $?
> 0
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1372051
> 
> Title:
>  ntp postinst user/group add commands are not idempotent
> 
> Status in ntp package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  At do release upgrade from 12.04.05 to 14.04.01, the ntp package failed:
>  Errors were encountered while processing:
>   ntp
>  Error in function: 
> 
> 
>  A fatal error occurred 
> 
>  Please report this as a bug and include the files 
>  /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in 
>  your report. The upgrade has aborted. 
>  Your original sources.list was saved in 
>  /etc/apt/sources.list.distUpgrade. 
> 
>  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
> 
> 
>  Could not install the upgrades
> 
>  The upgrade has aborted. Your system could be in an unusable state. A 
>  recovery will run now (dpkg --configure -a). 
> 
>  Please report this bug in a browser at 
>  http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
>  and attach the files in /var/log/dist-upgrade/ to the bug report. 
>  installArchives() failed 
> 
>  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2) ...
>  dpkg: error processing package ntp (--configure):
>   subprocess installed post-installation script returned error exit status 1
>  Errors were encountered while processing:
>   ntp
> 
>  Upgrade complete
> 
>  The upgrade has completed but there were errors during the upgrade 
>  process. 
> 
> 
>  In /var/lib/dpkg/info/ntp.postinst the add group / adduser commands fail due 
> to already existing group / user.
>  Appended “ || /bin/true” to those lines, and “dpkg —configure ntp” succeeded.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1372051/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1372051

Title:
  ntp postinst user/gr

Re: [Touch-packages] [Bug 1372051] ntp postinst user/group add commands are not idempotent

[Niklas Ögren]

Ryan,

Thanks for looking into this.
Yes, the machine in question has been running for many years, might even have 
started with a non LTS ubuntu before 12.04.
Attached you can find my current copy. It’s a bit weird that it’s not replaced 
when upgrading to the 12.04 version of ntp package ..



/n


> On 04 Aug 2015, at 21:01, Ryan Harper <1372...@bugs.launchpad.net> wrote:
> 
> I booted a precise server image:
> 
> ubuntu@ubuntu:~$ cat /etc/issue
> Ubuntu 12.04.5 LTS \n \l
> 
> ubuntu@ubuntu:~$ uname -a
> Linux ubuntu 3.2.0-88-virtual #126-Ubuntu SMP Mon Jul 6 21:50:59 UTC 2015 
> x86_64 x86_64 x86_64 GNU/Linux
> 
> Installed ntp:
> 
> % sudo apt-get install ntp
> ...
> http://archive.ubuntu.com/ubuntu/ precise-updates/main ntp amd64 
> 1:4.2.6.p3+dfsg-1ubuntu3.4
> 
> ubuntu@ubuntu:~$ grep ntp /etc/group
> ntp:x:112:
> 
> Then do-release-upgrade to move to 14.04 with no issues.
> 
> Examining the postinst scripts in current precise ( ), and various
> trusty versions of the ntp package, the script is always idempotent
> w.r.t adding the ntp group.  It's not clear to me which version of the
> ntp package had a post-inst script that wasn't idempotent.  Getting a
> copy of the ntp.postinst script that is failing would be most useful.
> 
> One workaround to the dist-upgrade issue is to apt-get remove --purge
> ntp (which will run the postrm hook to remove the ntp group) prior to
> upgrading.
> 
> ** Changed in: ntp (Ubuntu)
>   Status: New => Incomplete
> 
> ** Changed in: ntp (Ubuntu)
> Assignee: Ryan Harper (raharper) => (unassigned)
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1372051
> 
> Title:
>  ntp postinst user/group add commands are not idempotent
> 
> Status in ntp package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  At do release upgrade from 12.04.05 to 14.04.01, the ntp package failed:
>  Errors were encountered while processing:
>   ntp
>  Error in function: 
> 
> 
>  A fatal error occurred 
> 
>  Please report this as a bug and include the files 
>  /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in 
>  your report. The upgrade has aborted. 
>  Your original sources.list was saved in 
>  /etc/apt/sources.list.distUpgrade. 
> 
>  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
> 
> 
>  Could not install the upgrades
> 
>  The upgrade has aborted. Your system could be in an unusable state. A 
>  recovery will run now (dpkg --configure -a). 
> 
>  Please report this bug in a browser at 
>  http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
>  and attach the files in /var/log/dist-upgrade/ to the bug report. 
>  installArchives() failed 
> 
>  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2) ...
>  dpkg: error processing package ntp (--configure):
>   subprocess installed post-installation script returned error exit status 1
>  Errors were encountered while processing:
>   ntp
> 
>  Upgrade complete
> 
>  The upgrade has completed but there were errors during the upgrade 
>  process. 
> 
> 
>  In /var/lib/dpkg/info/ntp.postinst the add group / adduser commands fail due 
> to already existing group / user.
>  Appended “ || /bin/true” to those lines, and “dpkg —configure ntp” succeeded.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1372051/+subscriptions


** Attachment added: "ntp.postinst"
   
https://bugs.launchpad.net/bugs/1372051/+attachment/4439204/+files/ntp.postinst

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1372051

Title:
  ntp postinst user/group add commands are not idempotent

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  At do release upgrade from 12.04.05 to 14.04.01, the ntp package failed:
  Errors were encountered while processing:
   ntp
  Error in function: 

  
  A fatal error occurred 

  Please report this as a bug and include the files 
  /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in 
  your report. The upgrade has aborted. 
  Your original sources.list was saved in 
  /etc/apt/sources.list.distUpgrade. 

  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)


  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  Please report this bug in a browser at 
  http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
  and attach the files in /var/log/dist-upgrade/ to the bug report. 
  installArchives() failed 

  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2) ...
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp

  Upgrade complete

  The upgrade has com

[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

@Alfonso: Thank you very much for your response. I really hope that this
will be fixed soon because I agree with your comment from the mailing
list that this is "worrying".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

Yes, after converting it to the right time zone (UTC+2) it becomes

21:31:58.664   21:32:05 ... 21:32:45
13:31:17.015   13:31:21 ... 13:31:32.

As I remember seeing the phone trying to send it for a relatively long
time on July 12th, it really seems as if there is some issue with
queueing the messages and recognizing when sending one failed.

Btw, thank you for your help. :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

a) I sent one SMS every time.
b) Those were short enough to be sent as one SMS by the provider.
c) The receivers' phones are displaying only one SMS.
d) The MySQL database has only one entry both times.
   For the first screenshot its timestamp is 2015-07-12T19:31:58.664
   for the second one it says 2015-05-30T11:31:17.015.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

Thank you for your reply, Matthias!

There is only one line in the database per message. Both rows have a
messageStatus of 4 which seems to be correct.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

The worst one.

** Attachment added: "SMS.png"
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4437379/+files/SMS.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  New

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

Another one.

** Attachment added: "SMS2.png"
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4437380/+files/SMS2.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  New

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1480554] [NEW] High costs due to SMS being sent multiple times when having a bad network connection

[Niklas Wenzel]

Public bug reported:

When having a bad network connection, Ubuntu tries to send SMS multiple
times but fails to recognize which messages have already been sent,
resulting in very high costs due to the same message actually being sent
several times.

I found this when looking through my provider's monthly reports and I
remember being on train journeys with very bad network connections on
these days. See the attached screenshots.

==

This happened on a Nexus 4 running on the stable channel (with up-to-
date images at the given times).

** Affects: telephony-service (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  New

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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 1430769] Re: Does not detect hidden WiFi on first attempt

[Niklas Wenzel]

I have been testing this for a few days now. I removed the network and
readded it. While I am inclined to believe that it detects the network a
bit faster now, most of the time I still have to turn it on and off for
about 5 times until the network is finally recognized. Therefore, the
bug still remains unresolved for me.

** Changed in: canonical-devices-system-image
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1430769

Title:
  Does not detect hidden WiFi on first attempt

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Confirmed

Bug description:
  The WiFi network I use at home is a hidden one. While it works with my
  Ubuntu Phone, I always have to toggle WiFi on and off about 3 times
  until it is detected.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 129
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-11 13:19:54
  version version: 129
  version ubuntu: 20150310.3
  version device: 20150210
  version custom: 20150310.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1430769/+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 1124071] Re: [tabs] Cannot add Tabs programmatically

[Niklas Wenzel]

Thanks a lot for the clarification, Zsombor!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1124071

Title:
  [tabs] Cannot add Tabs programmatically

Status in Ubuntu Shorts App:
  Confirmed
Status in Ubuntu UI Toolkit:
  Fix Released
Status in Ubuntu UX:
  Won't Fix
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Trusty:
  Confirmed
Status in ubuntu-ui-toolkit source package in Vivid:
  New

Bug description:
  There seems to be no easy way to add a Tab to Tabs programmatically.

  I would be nice to be able add, remove and edit Tabs dynamically. So
  far I haven't found a way to do this.

  I have made an Android style ViewPager based on ListView. It is quite
  easy to update the pages with ListModel methods.

  UX Comments
  Tabs are deprecated, use the new header instead, or headers sections

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1124071/+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 1476027] [NEW] When changing a *.settings file, the libsignon-glib accounts database is not updated and still contains the old information

[Niklas Wenzel]

Public bug reported:

When developing an application, you often need to change your *.service
files. However, the ~/.config/libsignon-glib/accounts.db file is
unexpectedly not updated when you install a newer version of your app on
your device. It still holds the old information and therefore causes
huge problems as existing and newly configured accounts won't work
properly.

Finding this out costed me a few hours today!

** Affects: accounts-qml-module
 Importance: Undecided
 Status: New

** Affects: libsignon-glib (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: accounts-qml-module
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1476027

Title:
  When changing a *.settings file, the libsignon-glib accounts database
  is not updated and still contains the old information

Status in accounts-qml-module:
  New
Status in libsignon-glib package in Ubuntu:
  New

Bug description:
  When developing an application, you often need to change your
  *.service files. However, the ~/.config/libsignon-glib/accounts.db
  file is unexpectedly not updated when you install a newer version of
  your app on your device. It still holds the old information and
  therefore causes huge problems as existing and newly configured
  accounts won't work properly.

  Finding this out costed me a few hours today!

To manage notifications about this bug go to:
https://bugs.launchpad.net/accounts-qml-module/+bug/1476027/+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 1476004] [NEW] UserCanceled error thrown when trying to access an unexisting providerId with the QML Setup element

[Niklas Wenzel]

Public bug reported:

How to reproduce:

Add the following to your application:

Setup {
id: setup
applicationId: "YOUR APP ID HERE"
providerId: "asdf"
}

and call setup.exec().

When having debugging enabled as described in
https://developer.ubuntu.com/en/start/platform/guides/online-accounts-
developer-guide/, the following error can be found in the logs:

RequestAccess failed:
QDBusError("com.ubuntu.OnlineAccountsUi.UserCanceled", "Canceled")

I spent hours trying to find the reason for that error as it does not at
all hint you at what you actually have done wrong. I think there should
be a more specific error message here.

** Affects: accounts-qml-module
 Importance: Undecided
 Status: New

** Affects: ubuntu-system-settings-online-accounts
 Importance: Undecided
 Status: New

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: accounts-qml-module
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1476004

Title:
  UserCanceled error thrown when trying to access an unexisting
  providerId with the QML Setup element

Status in accounts-qml-module:
  New
Status in Online Accounts setup for Ubuntu Touch:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  How to reproduce:

  Add the following to your application:

  Setup {
  id: setup
  applicationId: "YOUR APP ID HERE"
  providerId: "asdf"
  }

  and call setup.exec().

  When having debugging enabled as described in
  https://developer.ubuntu.com/en/start/platform/guides/online-accounts-
  developer-guide/, the following error can be found in the logs:

  RequestAccess failed:
  QDBusError("com.ubuntu.OnlineAccountsUi.UserCanceled", "Canceled")

  I spent hours trying to find the reason for that error as it does not
  at all hint you at what you actually have done wrong. I think there
  should be a more specific error message here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accounts-qml-module/+bug/1476004/+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 1395118] Re: ActionSelectionPopover does not handle the 'visible' property of actions properly

[Niklas Wenzel]

** Branch linked: lp:~nikwen/ubuntu-filemanager-app/remove-popover-
workaround

** Changed in: ubuntu-filemanager-app
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1395118

Title:
  ActionSelectionPopover does not handle the 'visible' property of
  actions properly

Status in the base for Ubuntu mobile products:
  Fix Released
Status in File Manager application for Ubuntu devices:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Fix Released

Bug description:
  When setting the 'visible' property of an action in an ActionList of
  an ActionSelectionPopover to false, the delegate will not be hidden
  but instead be shown at the top of the list behind the first visible
  delegate. (Check out the screenshot.)

  Demo code (containing an outcommented workaround):

  import QtQuick 2.3
  import Ubuntu.Components 1.1
  import Ubuntu.Components.Popups 1.0
  import Ubuntu.Components.ListItems 1.0

  MainView {
  width: units.gu(50)
  height: units.gu(75)

  Page {
  title: i18n.tr("ActionSelectionPopover Fix")

  Button {
  id: button
  width: parent.width

  text: i18n.tr("Show popover")

  onClicked: {
  PopupUtils.open(actionSelectionPopoverComponent, button)
  }
  }

  Component {
  id: actionSelectionPopoverComponent

  ActionSelectionPopover {
  actions: ActionList {
  Action {
  text: "Action one"
  }
  Action {
  text: "Action two"
  }
  Action {
  text: "Hidden action"
  visible: false
  }
  }

  // Uncomment the following for a temporary workaround:

  //delegate: Empty {
  //id: listItem
  //Label {
  //text: listItem.text
  //anchors {
  //verticalCenter: parent.verticalCenter
  //horizontalCenter: parent.horizontalCenter
  //}
  //wrapMode: Text.Wrap
  //color: Theme.palette.normal.overlayText
  //}
  ///*! \internal */
  //onTriggered: popover.hide()
  //visible: enabled && ((action === undefined) || 
action.visible)
  //height: visible ? implicitHeight : 0
  //}
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1395118/+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 1450739] Re: Missing icons following update

[Niklas Wenzel]

I don't think this is a problem with the calculator app. Should be a
Unity8 issue.

** Changed in: ubuntu-calculator-app
   Status: New => Invalid

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1450739

Title:
  Missing icons following update

Status in Default calculator application for Ubuntu devices:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Icons on the core apps are missing on the Apps scope (and left slide-
  menu)  after latest system update. These include:

  - Camera
  - Calc
  - Gallery
  - Music
  - Reminders
  - Weather
  - Twitter

  Non-core apps (that were present in previous boot):
  - Realtai

  Where are they going? Did the config pointing to them change?

  Not a problem on the app menu as they are labeled, but they are not
  labeled on the left slide-menu - no visual clues unless I touch and
  hold.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1450739/+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 1430769] Re: Does not detect hidden WiFi on first attempt

[Niklas Wenzel]

Forgot to add: the hidden wifi was not in the list which was returned by
wpa_supplicant.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1430769

Title:
  Does not detect hidden WiFi on first attempt

Status in indicator-network package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  The WiFi network I use at home is a hidden one. While it works with my
  Ubuntu Phone, I always have to toggle WiFi on and off about 3 times
  until it is detected.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 129
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-11 13:19:54
  version version: 129
  version ubuntu: 20150310.3
  version device: 20150210
  version custom: 20150310.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1430769/+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 1430769] Re: Does not detect hidden WiFi on first attempt

[Niklas Wenzel]

If you need any other logs, feel free to ask. :)

(This one was taken after booting with wifi enabled and toggling wifi
off and on once. It did not connect to the network during that.)

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1430769/+attachment/4412688/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1430769

Title:
  Does not detect hidden WiFi on first attempt

Status in indicator-network package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  The WiFi network I use at home is a hidden one. While it works with my
  Ubuntu Phone, I always have to toggle WiFi on and off about 3 times
  until it is detected.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 129
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-11 13:19:54
  version version: 129
  version ubuntu: 20150310.3
  version device: 20150210
  version custom: 20150310.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1430769/+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 1430769] Re: Does not detect hidden WiFi on first attempt

[Niklas Wenzel]

Of course. :)

Here's the output of wpa_supplicant: http://paste.ubuntu.com/11690994/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1430769

Title:
  Does not detect hidden WiFi on first attempt

Status in indicator-network package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  The WiFi network I use at home is a hidden one. While it works with my
  Ubuntu Phone, I always have to toggle WiFi on and off about 3 times
  until it is detected.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 129
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-11 13:19:54
  version version: 129
  version ubuntu: 20150310.3
  version device: 20150210
  version custom: 20150310.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1430769/+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 1430769] Re: Does not detect hidden WiFi on first attempt

[Niklas Wenzel]

I don't think this is a duplicate bug as the other bug mentions some
behaviour which I do not see.

Here is the behaviour I do *not* see (copied from the other bug):

"Instead of the "connected" icon in the top bar there's just a blank
space, the hidden network shows up in the indicator's network list
twice, and there's no check mark next to either of the entries in the
network list"

Here is what I see:

Nothing happens. There is no blank space (the icon displays the state of
my mobile connection or the "not connected" wifi icon), nor does the
network show up in the list even once.

** This bug is no longer a duplicate of bug 1354560
   Indicator doesn't show connected status when associated with hidden network

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1430769

Title:
  Does not detect hidden WiFi on first attempt

Status in indicator-network package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  The WiFi network I use at home is a hidden one. While it works with my
  Ubuntu Phone, I always have to toggle WiFi on and off about 3 times
  until it is detected.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 129
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-11 13:19:54
  version version: 129
  version ubuntu: 20150310.3
  version device: 20150210
  version custom: 20150310.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1430769/+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 1460809] Re: Context menu issues if the link contains extra HTML elements

[Niklas Wenzel]

*** This bug is a duplicate of bug 1326070 ***
https://bugs.launchpad.net/bugs/1326070

Thanks, Olivier. I'm looking forward to it as I'm seeing this on
multiple pages. :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1460809

Title:
  Context menu issues if the link contains extra HTML elements

Status in Oxide Webview:
  Invalid
Status in Web Browser App:
  Invalid
Status in oxide-qt package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:

  1) Open www.zeit.de on a mobile device
  2) Long-press on the first article

  Expected behaviour:

  A context menu should pop up with a "Open link in new background
  tab" option (among others).

  Actual behaviour:

  There's only a "Copy" entry in the context menu.

  
  (This happens on other sites, too.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1460809/+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 1460809] [NEW] Context menu issues if the link contains extra HTML elements

[Niklas Wenzel]

Public bug reported:

How to reproduce:

1) Open www.zeit.de on a mobile device
2) Long-press on the first article

Expected behaviour:

A context menu should pop up with a "Open link in new background
tab" option (among others).

Actual behaviour:

There's only a "Copy" entry in the context menu.


(This happens on other sites, too.)

** Affects: oxide
 Importance: Undecided
 Status: New

** Affects: webbrowser-app
 Importance: Undecided
 Status: New

** Affects: oxide-qt (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: oxide
   Importance: Undecided
   Status: New

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1460809

Title:
  Context menu issues if the link contains extra HTML elements

Status in Oxide Webview:
  New
Status in Web Browser App:
  New
Status in oxide-qt package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  How to reproduce:

  1) Open www.zeit.de on a mobile device
  2) Long-press on the first article

  Expected behaviour:

  A context menu should pop up with a "Open link in new background
  tab" option (among others).

  Actual behaviour:

  There's only a "Copy" entry in the context menu.

  
  (This happens on other sites, too.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1460809/+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 1458235] Re: Allow users to set arbitrary location for scopes.

[Niklas Wenzel]

I added the Ubuntu UX project as this would probably need design input.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1458235

Title:
  Allow users to set arbitrary location for scopes.

Status in Ubuntu UX bugs:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  Currently I can't set my location manually for any scope. They get it
  somehow automatically, most of the time wrongly. It would be nice if a
  user could somehow select the location he/she wants.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1458235/+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 1458235] Re: Allow users to set arbitrary location for scopes.

[Niklas Wenzel]

I'd really like to see this as I don't like giving apps/scopes access to
my current location via GPS. Therefore, I cannot use any location based
scopes.

However, it may even be useful even if you do give them access. Here are
some examples

1) Checking for the weather in your home town using the weather scope while 
you're in another city
2) Checking for points of interest using the Nearby scope while you are still 
on the train

** Description changed:

- Currently I can't set location for any scope. They get it somehow
- automatically, most of the time wrongly. It would be nice if a user
- could somehow select a location she wants.
+ Currently I can't set my location manually for any scope. They get it
+ somehow automatically, most of the time wrongly. It would be nice if a
+ user could somehow select the location he/she wants.

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1458235

Title:
  Allow users to set arbitrary location for scopes.

Status in Ubuntu UX bugs:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  Currently I can't set my location manually for any scope. They get it
  somehow automatically, most of the time wrongly. It would be nice if a
  user could somehow select the location he/she wants.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1458235/+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 1431564] Re: [switcher] Can't use mouse to access spread or bottom edge

[Niklas Wenzel]

@huangzhiquan You can get that on Unity7 by installing the unity-tweak-
tool package. However, to me it looks like the Unity8 behaviour will be
different though. ;)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1431564

Title:
  [switcher] Can't use mouse to access spread or bottom edge

Status in Ubuntu UX bugs:
  In Progress
Status in unity8 package in Ubuntu:
  New

Bug description:
  If I connect my BT mouse to my Nexus 4 running devel-proposed with
  silo 0 (the MWC demo), I can neither open the app spread nor the
  manage scopes overview. Using the touch screen, both actions work
  fine, even when the mouse is connected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1431564/+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 1418626] Re: Embedded YouTube videos stuttering and not playing back smoothly

[Niklas Wenzel]

Anything new here? I watched a movie on YouTube yesterday and due to the 
stuttering it took me two hours instead of the movie's normal length of one and 
a half hours.
This makes Youtube quite useless on my phone right now...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1418626

Title:
  Embedded YouTube videos stuttering and not playing back smoothly

Status in Oxide Webview:
  New
Status in Web Browser App:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Related to bug https://bugs.launchpad.net/webbrowser-app/+bug/1417258.

  Embedded youtube videos, like this:
  
http://m.bleacherreport.com/articles/2352016-papa-johns-airs-wrong-commercial-congratulates-seahawks-after-super-bowl

  or this:
  http://pages.ebay.com/shoptheworld/

  do not play back correctly. They exhibit stuttering and stopping, with
  oxide-renderer process using over 100% CPU.

  This was worked around on YouTube.com (and webapp) by using overriden
  UA string which makes YouTube send us a stream that we can playback
  smoothly. But this UA string is not presented to embedded videos
  within other sites.

  We should figure out how we can send the UA override to embedded
  videos (if possible), and if not what change could we make to our
  default UA string such that YouTube gives us content that we can
  render more efficiently.

  Other ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1418626/+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 1442670] Re: Ubuntu Phone BQ: Camera makes blur images

[Niklas Wenzel]

@Florian: "Managed" to snap a proper example for you. However, since
it's copyright protected material, I will not upload it to Launchpad.
Check your emails. ;)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1442670

Title:
  Ubuntu Phone BQ: Camera makes blur images

Status in Camera App:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Hi!
  A lot of times the camera is getting a really bad images (blur effect) in all 
resolutions.

  And yes, I click previously for a focus.

  I'm sending you an example: That picture looked perfect in the mobile,
  but in the PC is really bad :(

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1442670/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1449188] White bar when playing video fullscreen

[Niklas Wenzel]

Thank you very much for fixing this that fast!

-- 
Sent using Dekko from my Ubuntu device

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1449188

Title:
  White bar when playing video fullscreen

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.7 series:
  Fix Committed
Status in oxide-qt package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:

  1) Open Youtube in the webbrowser-app.
  2) Start a video and switch to fullscreen mode.

  What happens:

  A white (and on some other sites black) bar is shown at the bottom of the 
screen on top of the video.
  Check out the screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1449188/+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 1449188] Re: White bar when playing video fullscreen

[Niklas Wenzel]

Christian, silo 0 is the citrain silo which hosts the Slimport/MHL and
full shell rotation code:
http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=ubuntu%2Flanding-000

Thanks to both of you for looking into this and confirming this. :)

(I'm really looking forward to the Meizu device!)

** Description changed:

  How to reproduce:
  
- 1) Install the full shell rotation code from silo 0.
- 2) Open Youtube in the webbrowser-app.
- 3) Start a video and switch to fullscreen mode.
+ 1) Open Youtube in the webbrowser-app.
+ 2) Start a video and switch to fullscreen mode.
  
  What happens:
  
  A white (and on some other sites black) bar is shown at the bottom of the 
screen on top of the video.
  Check out the screenshot.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1449188

Title:
  White bar when playing video fullscreen

Status in oxide-qt package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:

  1) Open Youtube in the webbrowser-app.
  2) Start a video and switch to fullscreen mode.

  What happens:

  A white (and on some other sites black) bar is shown at the bottom of the 
screen on top of the video.
  Check out the screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1449188/+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 1449188] Re: [Full shell rotation] White bar when playing video fullscreen

[Niklas Wenzel]

** Attachment added: "screenshot20150427_200412513.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1449188/+attachment/4385878/+files/screenshot20150427_200412513.png

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1449188

Title:
  [Full shell rotation] White bar when playing video fullscreen

Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  How to reproduce:

  1) Install the full shell rotation code from silo 0.
  2) Open Youtube in the webbrowser-app.
  3) Start a video and switch to fullscreen mode.

  What happens:

  A white (and on some other sites black) bar is shown at the bottom of the 
screen on top of the video.
  Check out the screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1449188/+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 1449188] [NEW] [Full shell rotation] White bar when playing video fullscreen

[Niklas Wenzel]

Public bug reported:

How to reproduce:

1) Install the full shell rotation code from silo 0.
2) Open Youtube in the webbrowser-app.
3) Start a video and switch to fullscreen mode.

What happens:

A white (and on some other sites black) bar is shown at the bottom of the 
screen on top of the video.
Check out the screenshot.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1449188

Title:
  [Full shell rotation] White bar when playing video fullscreen

Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  How to reproduce:

  1) Install the full shell rotation code from silo 0.
  2) Open Youtube in the webbrowser-app.
  3) Start a video and switch to fullscreen mode.

  What happens:

  A white (and on some other sites black) bar is shown at the bottom of the 
screen on top of the video.
  Check out the screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1449188/+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