[Touch-packages] [Bug 2079964] [NEW] w shows no session information after upgrade from 22.04 to 24.04

2024-09-09 Thread Florian Piekert
Public bug reported:

strace from w on 24.04.1
execve("/usr/bin/w", ["w"], 0x7ffd12dba020 /* 21 vars */) = 0
brk(NULL)   = 0x59941c3b7000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x73a1b1bdf000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=34415, ...}) = 0
mmap(NULL, 34415, PROT_READ, MAP_PRIVATE, 3, 0) = 0x73a1b1bd6000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libproc2.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=203400, ...}) = 0
mmap(NULL, 205200, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x73a1b1ba3000
mmap(0x73a1b1bb, 86016, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd000) = 0x73a1b1bb
mmap(0x73a1b1bc5000, 40960, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x22000) = 0x73a1b1bc5000
mmap(0x73a1b1bcf000, 28672, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2b000) = 0x73a1b1bcf000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libsystemd.so.0", O_RDONLY|O_CLOEXEC) = 
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=910592, ...}) = 0
mmap(NULL, 915016, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x73a1b1ac3000
mmap(0x73a1b1ad9000, 585728, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x16000) = 0x73a1b1ad9000
mmap(0x73a1b1b68000, 188416, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0xa5000) = 0x73a1b1b68000
mmap(0x73a1b1b96000, 49152, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd2000) = 0x73a1b1b96000
mmap(0x73a1b1ba2000, 1608, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x73a1b1ba2000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220\243\2\0\0\0\0\0"..., 832) = 
832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
fstat(3, {st_mode=S_IFREG|0755, st_size=2125328, ...}) = 0
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
mmap(NULL, 2170256, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x73a1b180
mmap(0x73a1b1828000, 1605632, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x28000) = 0x73a1b1828000
mmap(0x73a1b19b, 323584, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1b) = 0x73a1b19b
mmap(0x73a1b19ff000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1fe000) = 0x73a1b19ff000
mmap(0x73a1b1a05000, 52624, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x73a1b1a05000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libcap.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\201\0\0\0\0\0\0"..., 832) = 
832
fstat(3, {st_mode=S_IFREG|0644, st_size=51536, ...}) = 0
mmap(NULL, 49224, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x73a1b1ab6000
mmap(0x73a1b1ab9000, 24576, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x73a1b1ab9000
mmap(0x73a1b1abf000, 8192, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x9000) = 0x73a1b1abf000
mmap(0x73a1b1ac1000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xb000) = 0x73a1b1ac1000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libgcrypt.so.20", O_RDONLY|O_CLOEXEC) = 
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=1340976, ...}) = 0
mmap(NULL, 1340272, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x73a1b16b8000
mmap(0x73a1b16c7000, 999424, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0x73a1b16c7000
mmap(0x73a1b17bb000, 241664, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x103000) = 0x73a1b17bb000
mmap(0x73a1b17f6000, 36864, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13e000) = 0x73a1b17f6000
mmap(0x73a1b17ff000, 880, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x73a1b17ff000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/liblz4.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=137440, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x73a1b1ab4000
mmap(NULL, 135264, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x73a1b1a92000
mmap(0x73a1b1a95000, 110592, PROT_READ|PROT_EXEC, 

[Touch-packages] [Bug 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)

2024-02-15 Thread Florian Bach
Given that systemd-v255 has just migrated from noble-proposed to noble
yesterday, this bug is now present in Ubuntu 24.04 as-is, without the
proposed repo enabled. Can this fix be backported before 22.04 releases
so people don't run into network issues with a newly-installed 22.04?

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

Title:
  Broken IPv4 support on IPv6-preferring networks (v255)

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed a bug in systemd version 255 which is currently available in
  noble-proposed (255.2-3ubuntu1).

  I have already reported to upstream at
  https://github.com/systemd/systemd/issues/30891 but there's no fix
  available yet as of today.

  I'm still reporting the bug here anyways because this bug can, under
  some conditions, result in the loss of IPv4 network connectivity in a
  completely standard Ubuntu 24.04 installation just by updating to
  systemd 255. I'm hoping that that's okay even though it's a bug caused
  by upstream not by Ubuntu; just because it could have a bad impact if
  this version ends up in 24.04 as it is.

  ---

  In systemd version 255, a feature has been added to "support" the
  IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
  quotation marks because one functionality that this RFC marks as a
  requirement is not implemented in systemd yet.

  To summarize: Option 108 can be sent by a DHCPv4 client to signal to
  the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
  support and a working NAT64 gateway, I don't really need my own IPv4
  address, I can handle it using 464XLAT and NAT64". The point of that
  option is to be able to run a Dual Stack network, where only clients
  that really need IPv4 (older Linux, Windows, etc.) will receive an
  IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
  Linux with systemd >=255, etc.) won't receive one from DHCP and
  instead set up a 464XLAT for outgoing IPv4 connectivity.

  This new code in systemd is enabled by default (the option
  "IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
  have code to set up a 464XLAT yet (which violates the RFC).

  This means that systemd signals to the DHCPv4 server "Hey, I don't
  need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
  actually do that. Updating systemd on an Ubuntu 24.04 installation
  (where systemd-networkd is used) will result in the loss of the DHCP-
  assigned IPv4 address, breaking network connectivity for all IPv4-only
  applications.

  ---

  Information on how to reproduce this issue can be found in detail in
  the github bug report linked above, but to summarize:

  1. Have a Dual Stack network that announces a NAT64 through RAs or through 
DNS (or, ideally, both)
  2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
  3. Connect an Ubuntu machine with systemd < 255.
  4. Notice that IPv4 connectivity is working fine.
  5. Update to systemd = 255.
  6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.

  ---

  The proper fix for this issue to make systemd conform to the RFC would
  be to implement a 464XLAT. However that's not an easy task and most
  certainly not something that would end up as a hotfix / patch release.
  A good workaround for this bug would be, in my opinion, to change the
  default value for the "IPv6OnlyMode" to "no" when compiling systemd.

  That way, the RFC-violating code doesn't run by default, and if a user
  does set up a 464XLAT on their machine in some other way (outside of
  systemd) they can just change their config to include
  "IPv6OnlyMode=yes" and it'll be working as intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.2-3ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jan 13 07:05:42 2024
  InstallationDate: Installed on 2024-01-12 (0 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64 
(20231011)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 001: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
  dmi.bios.date: 1

[Touch-packages] [Bug 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)

2024-02-07 Thread Florian Bach
Upstream has fixed this for v256 and has indicated the fix will be
backported to v255.

https://github.com/systemd/systemd/commit/7dc431839eeeffe6ed65acbe9bfe2a6e89422086

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

Title:
  Broken IPv4 support on IPv6-preferring networks (v255)

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed a bug in systemd version 255 which is currently available in
  noble-proposed (255.2-3ubuntu1).

  I have already reported to upstream at
  https://github.com/systemd/systemd/issues/30891 but there's no fix
  available yet as of today.

  I'm still reporting the bug here anyways because this bug can, under
  some conditions, result in the loss of IPv4 network connectivity in a
  completely standard Ubuntu 24.04 installation just by updating to
  systemd 255. I'm hoping that that's okay even though it's a bug caused
  by upstream not by Ubuntu; just because it could have a bad impact if
  this version ends up in 24.04 as it is.

  ---

  In systemd version 255, a feature has been added to "support" the
  IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
  quotation marks because one functionality that this RFC marks as a
  requirement is not implemented in systemd yet.

  To summarize: Option 108 can be sent by a DHCPv4 client to signal to
  the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
  support and a working NAT64 gateway, I don't really need my own IPv4
  address, I can handle it using 464XLAT and NAT64". The point of that
  option is to be able to run a Dual Stack network, where only clients
  that really need IPv4 (older Linux, Windows, etc.) will receive an
  IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
  Linux with systemd >=255, etc.) won't receive one from DHCP and
  instead set up a 464XLAT for outgoing IPv4 connectivity.

  This new code in systemd is enabled by default (the option
  "IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
  have code to set up a 464XLAT yet (which violates the RFC).

  This means that systemd signals to the DHCPv4 server "Hey, I don't
  need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
  actually do that. Updating systemd on an Ubuntu 24.04 installation
  (where systemd-networkd is used) will result in the loss of the DHCP-
  assigned IPv4 address, breaking network connectivity for all IPv4-only
  applications.

  ---

  Information on how to reproduce this issue can be found in detail in
  the github bug report linked above, but to summarize:

  1. Have a Dual Stack network that announces a NAT64 through RAs or through 
DNS (or, ideally, both)
  2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
  3. Connect an Ubuntu machine with systemd < 255.
  4. Notice that IPv4 connectivity is working fine.
  5. Update to systemd = 255.
  6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.

  ---

  The proper fix for this issue to make systemd conform to the RFC would
  be to implement a 464XLAT. However that's not an easy task and most
  certainly not something that would end up as a hotfix / patch release.
  A good workaround for this bug would be, in my opinion, to change the
  default value for the "IPv6OnlyMode" to "no" when compiling systemd.

  That way, the RFC-violating code doesn't run by default, and if a user
  does set up a 464XLAT on their machine in some other way (outside of
  systemd) they can just change their config to include
  "IPv6OnlyMode=yes" and it'll be working as intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.2-3ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jan 13 07:05:42 2024
  InstallationDate: Installed on 2024-01-12 (0 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64 
(20231011)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 001: Dev 002, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor:

[Touch-packages] [Bug 2049247] [NEW] Broken IPv4 support on IPv6-preferring networks (v255)

2024-01-12 Thread Florian Bach
Public bug reported:

I noticed a bug in systemd version 255 which is currently available in
noble-proposed (255.2-3ubuntu1).

I have already reported to upstream at
https://github.com/systemd/systemd/issues/30891 but there's no fix
available yet as of today.

I'm still reporting the bug here anyways because this bug can, under
some conditions, result in the loss of IPv4 network connectivity in a
completely standard Ubuntu 24.04 installation just by updating to
systemd 255. I'm hoping that that's okay even though it's a bug caused
by upstream not by Ubuntu; just because it could have a bad impact if
this version ends up in 24.04 as it is.

---

In systemd version 255, a feature has been added to "support" the
IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
quotation marks because one functionality that this RFC marks as a
requirement is not implemented in systemd yet.

To summarize: Option 108 can be sent by a DHCPv4 client to signal to the
DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
support and a working NAT64 gateway, I don't really need my own IPv4
address, I can handle it using 464XLAT and NAT64". The point of that
option is to be able to run a Dual Stack network, where only clients
that really need IPv4 (older Linux, Windows, etc.) will receive an IPv4
from DHCP, and clients that don't need IPv4 (Android, MacOS, Linux with
systemd >=255, etc.) won't receive one from DHCP and instead set up a
464XLAT for outgoing IPv4 connectivity.

This new code in systemd is enabled by default (the option
"IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
have code to set up a 464XLAT yet (which violates the RFC).

This means that systemd signals to the DHCPv4 server "Hey, I don't need
IPv4, I'll just use 464XLAT and NAT64" but then it doesn't actually do
that. Updating systemd on an Ubuntu 24.04 installation (where systemd-
networkd is used) will result in the loss of the DHCP-assigned IPv4
address, breaking network connectivity for all IPv4-only applications.

---

Information on how to reproduce this issue can be found in detail in the
github bug report linked above, but to summarize:

1. Have a Dual Stack network that announces a NAT64 through RAs or through DNS 
(or, ideally, both)
2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
3. Connect an Ubuntu machine with systemd < 255.
4. Notice that IPv4 connectivity is working fine.
5. Update to systemd = 255.
6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.

---

The proper fix for this issue to make systemd conform to the RFC would
be to implement a 464XLAT. However that's not an easy task and most
certainly not something that would end up as a hotfix / patch release. A
good workaround for this bug would be, in my opinion, to change the
default value for the "IPv6OnlyMode" to "no" when compiling systemd.

That way, the RFC-violating code doesn't run by default, and if a user
does set up a 464XLAT on their machine in some other way (outside of
systemd) they can just change their config to include "IPv6OnlyMode=yes"
and it'll be working as intended.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 255.2-3ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Jan 13 07:05:42 2024
InstallationDate: Installed on 2024-01-12 (0 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64 
(20231011)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Lsusb-t:
 /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 
12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
SourcePackage: systemd
UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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


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

** Bug watch added: github.com/systemd/systemd/issu

[Touch-packages] [Bug 1998111] Re: Quectel EM05-G not being unlocked

2023-10-22 Thread Florian Beier
Works fine for me with Ubuntu 23.10.

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

Title:
  Quectel EM05-G not being unlocked

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Despite support being in fcc-unlock.d

  Bus 001 Device 003: ID 2c7c:030a Quectel Wireless Solutions Co., Ltd.
  Quectel EM05-G

  the modem remains locked and enabling it fails:

  jak@jak-t14-g3:~:master$ mmcli -m any -e
  error: couldn't enable the modem: 
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'

  
  Doing something like

  # modprobe -r cdc_mbim
  # modprobe cdc_mbim
  # mbimcli --device-open-proxy --device="/dev/wwan0mbim0" 
--quectel-set-radio-state=on 
  # systemctl RestartModemManager
  # mmcli -m any -e

  makes it work.

  Peculiar it seems that the mbim-proxy process that ModemManager
  started is hanging and causing the mbimcli command to time out (if I
  just run it manually).

  
  Further investigation warranted, tips welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: modemmanager 1.20.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Nov 28 13:54:07 2022
  InstallationDate: Installed on 2022-11-26 (1 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1998111/+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 2016252]

2023-09-15 Thread Florian Weimer
Fixed for 2.39 via:

commit dcad5c8578130dec7f35fd5b0885304b59f9f543
Author: Sajan Karumanchi 
Date:   Tue Aug 1 15:20:55 2023 +

x86: Fix for cache computation on AMD legacy cpus.

Some legacy AMD CPUs and hypervisors have the _cpuid_ '0x8000_001D'
set to Zero, thus resulting in zeroed-out computed cache values.
This patch reintroduces the old way of cache computation as a
fail-safe option to handle these exceptions.
Fixed 'level4_cache_size' value through handle_amd().

Reviewed-by: Premachandra Mallappa 
    Tested-by: Florian Weimer 

It seems that we are still missing the backport to 2.37.

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

Title:
  qemu-system-x86_64 crashes inside nested VM

Status in GLibC:
  Confirmed
Status in glibc package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Systemd package has autopkgtests
  the upstream-2 test cases use upstream systemd testsuite, i.e. make -C 
str/test/TEST-70-TPM2 setup run
  it launches a nested VM to do quick tests inside it.

  It appears that qemu-system-x86_64 crashes in such cases:

  TEST-70-TPM2 RUN: cryptenroll/cryptsetup with TPM2 devices
  + timeout --foreground 1800 /bin/qemu-system-x86_64 -smp 4 -net none -m 1024M 
-nographic -vga none -kernel /boot/vmlinuz-6.2.0-1003-lowlatency -drive 
format=raw,cache=unsafe,file=/var/tmp/systemd-test.G2RH6i/tpm2.img -device 
virtio-rng-pci,max-bytes=1024,period=1000 -chardev 
socket,id=chrtpm,path=/tmp/tmp.cRBa43SrLC/sock -tpmdev 
emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 -initrd 
/boot/initrd.img-6.2.0-1003-lowlatency -append 'root=LABEL=systemd_boot rw 
raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0 
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-70.units:/usr/lib/systemd/tests/testdata/units:
 systemd.unit=testsuite.target systemd.wants=testsuite-70.service oops=panic 
panic=1 softlockup_panic=1 systemd.wants=end.service'
  qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info: Assertion 
`(isize & (isize - 1)) == 0' failed.
  timeout: the monitored command dumped core
  ..//test-functions: line 377: 152120 Aborted ( set -x; 
"${qemu_cmd[@]}" "${qemu_options[@]}" -append "${kernel_params[*]}" )
  E: qemu failed with exit code 134

  The important bit seems to be:

  qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info:
  Assertion `(isize & (isize - 1)) == 0' failed.

  Which is an assert inside qemu source code.

  Is the systemd test suite VM setup doing something wrong, or is there
  something wrong in qemu?

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/2016252/+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 1991491] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwe

2022-10-02 Thread Florian Hars
Public bug reported:

I undated from 20.04.5 to 22.04.1 and this is what the update ended
with.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13
ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
Uname: Linux 5.4.0-126-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Oct  2 19:06:19 2022
ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2017-06-03 (1946 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago)

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


** Tags: amd64 apport-package jammy

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  »installiertes initramfs-tools-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I undated from 20.04.5 to 22.04.1 and this is what the update ended
  with.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
  Uname: Linux 5.4.0-126-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Oct  2 19:06:19 2022
  ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2017-06-03 (1946 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991491/+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 1920794] Re: tc tool does not accept ipset match

2021-11-23 Thread Florian Lohoff
This is caused be mismatch between Kernel and iproute2 version. The kernel v5 
offers ipset v7 which causes iproute to not be built with ematch ipset 
functionality.

This has been fixed in iproute upstream in - its a one line fix -
Pulling this into iproute2 and rebuilding (After committing it) works.


https://github.com/shemminger/iproute2/commit/650591a7a70cd79d826fcdc579a20c168c987cf2


commit 650591a7a70cd79d826fcdc579a20c168c987cf2
Author: Tony Ambardar 
Date:   Tue Jul 7 00:58:33 2020 -0700

configure: support ipset version 7 with kernel version 5

The configure script checks for ipset v6 availability but doesn't test
for v7, which is backward compatible and used on kernel v5.x systems.
Update the script to test for both ipset versions. Without this change,
the tc ematch function em_ipset will be disabled.

Signed-off-by: Tony Ambardar 
Signed-off-by: Stephen Hemminger 


** Changed in: iproute2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  tc tool does not accept ipset match

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  tc qdisc add dev eth0 root handle 1: htb
  tc class add dev eth0 parent 1: classid 1:1 htb rate 1024Kbit
  ipset create mytest hash:net
  tc filter add dev eth0 protocol ip parent 1:0 prio 1 basic match 
'ipset(mytest src)' classid 1:1

  Last command fails with the message:

  Unknown ematch "ipset"
  Illegal "ematch"

  It works well with 18.04. On 20.04 machine it also works fine inside
  Ubuntu 18.04 LXD container.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: iproute2 5.5.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Mar 22 16:18:17 2021
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1920794/+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 1924861] [NEW] nvidia random crashes back to login screen

2021-04-17 Thread Florian
Public bug reported:

sometimes, when I click on some application in the panel e.g
discord/firefox/chrome Xorg crashes and takes me back to login screen

dmesg error:
[205084.240560] NVRM: Xid (PCI::01:00): 31, pid=1673, Ch 0009, intr 
1000. MMU Fault: ENGINE CE0 HUBCLIENT_CE0 faulted @ 0x1_02764000. Fault is 
of type FAULT_PTE ACCESS_TYPE_READ


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.102.04  Tue Dec 29 
06:51:23 UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:

CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sat Apr 17 17:12:48 2021
DistUpgraded: 2020-11-28 16:24:27,019 DEBUG entry '# deb 
http://ppa.launchpad.net/jeremysanders/ppa/ubuntu focal main # Bei 
Aktualisierung zu bionic deaktiviert Bei Aktualisierung zu focal deaktiviert' 
was disabled (unknown mirror)
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 450.102.04, 5.4.0-70-generic, x86_64: installed
 nvidia, 450.102.04, 5.4.0-72-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-71-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-72-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 
6GB] [1462:3283]
InstallationDate: Installed on 2016-09-09 (1681 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=21ee0900-9162-4298-bd0e-5dbd103514f0 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-11-28 (139 days ago)
dmi.bios.date: 01/26/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: Default string
dmi.board.name: B150 PRO GAMING/AURA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/26/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150PROGAMING/AURA:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Description changed:

  sometimes, when I click on some application in the panel e.g
  discord/firefox/chrome Xorg crashes and takes me back to login screen
+ 
+ dmesg error:
+ [205084.240560] NVRM: Xid (PCI::01:00): 31, pid=1673, Ch 0009, intr 
1000. MMU Fault: ENGINE CE0 HUBCLIENT_CE0 faulted @ 0x1_02764000. Fault is 
of type FAULT_PTE ACCESS_TYPE_READ
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mi

[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-02-27 Thread Florian Weimer
To paper over the faccessat2 issue, a libseccomp update is enough *if*
the container runtime already knows about the faccessat2 system call and
mentions it in its profiles. But with the current design, every new
system call will need similar updates to several components (not just
libseccomp) just to produce the ENOSYS error, which is not a sustainable
development model. Hence the runc pull request mentioned in comment 8.

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

Title:
  test -x fails inside shell scripts in containers

Status in glibc package in Ubuntu:
  Triaged
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in glibc source package in Hirsute:
  Triaged
Status in libseccomp source package in Hirsute:
  Fix Committed

Bug description:
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  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  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."

  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -

  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+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 1916485] Re: test -x fails inside shell scripts in containers

2021-02-22 Thread Florian Weimer
Patches have been proposed for that, but were rejected:

[PATCH] syscalls: Document OCI seccomp filter interactions & workaround
https://lore.kernel.org/linux-api/87lfer2c0b@oldenburg2.str.redhat.com/

[RFC PATCH] Linux: Add seccomp probing to faccessat2
https://sourceware.org/pipermail/libc-alpha/2020-November/119955.html

We *really* need to clean this up properly, so that we are prepared if
we need to add a new system call as part of a security fix.

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

Title:
  test -x fails inside shell scripts in containers

Status in glibc package in Ubuntu:
  Triaged
Status in libseccomp package in Ubuntu:
  Fix Committed

Bug description:
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  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  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."

  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -

  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+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 1916485] Re: apt-key add fails in docker - Fails to run gnupg

2021-02-22 Thread Florian Lohoff
Bug also applies to apt 2.2.0


root@72aa01291622:/# dpkg -l apt gnupg
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  apt2.2.0   amd64commandline package manager
ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free PGP 
replacement

root@72aa01291622:/# curl https://syncthing.net/release-key.txt | apt-key add -
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is 
required for this operation
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0

100  2462  100  24620 0   1969  0  0:00:01  0:00:01 --:--:--
1969

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

Title:
  apt-key add fails in docker - Fails to run gnupg

Status in apt package in Ubuntu:
  New

Bug description:
  
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt 
  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  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement


  
  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."


  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
&& DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
&& curl https://syncthing.net/release-key.txt | apt-key add -


  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916485/+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 1916485] [NEW] apt-key add fails in docker - Fails to run gnupg

2021-02-22 Thread Florian Lohoff
Public bug reported:


root@84b750e443f8:/# lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
root@84b750e443f8:/# dpkg -l gnupg apt 
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  apt2.1.20  amd64commandline package manager
ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free PGP 
replacement


Hi,
for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

The build fails with:

0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
them is required for this operation

The simple Dockerfile to reproduce the error - "docker build -t foo ."


FROM amd64/ubuntu:hirsute
MAINTAINER Florian Lohoff 

USER root

RUN apt-get update \
&& DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
&& curl https://syncthing.net/release-key.txt | apt-key add -


Breaking it down it this seems to be an issue that there is new
functionality in apt/apt-key e.g. security hardening that docker
prohibits in its containers. Running this manually works only in an
--privileged container.

So adding keys in unpriviledged container or possibly kubernetes will
not work anymore.

Flo

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

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

Title:
  apt-key add fails in docker - Fails to run gnupg

Status in apt package in Ubuntu:
  New

Bug description:
  
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt 
  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  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement


  
  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."


  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
&& DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
&& curl https://syncthing.net/release-key.txt | apt-key add -


  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1916485/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

2020-11-14 Thread Florian Beier
I can confirm that the updated packages fix the issue for me (Groovy on
a ThinkPad T14 w/ Ryzen 7 Pro 4750U). However, the LED on the keyboard
for muting the microphone (on the F4 key) doesn't work for the internal
microphone. It works as expected when another microphone is present and
selected as input device (I plugged a headset into the audio jack).

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: L

[Touch-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

2020-11-06 Thread Florian Beier
@Hui Wang

I installed your package and rebooted. It seems to fix the issue, audio
is working as expected again.

One thing I noticed is that when I mute the speakers or microphone via
their media keys (F1 and F4) the LEDs on the keys don't light up. It may
not be related to this issue though because when I activate the FnLock
the LED on the Esc key also doesn't light up.

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

Title:
  [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output 
didn't work anymore. 
  Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 
5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get 
the exact same problem (On 20.04 Livesystem it works) 
  An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device 
uses the wrong Kernel Module (Audio Input is working since it uses the correct 
kernel module and driver)

  
  07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Lenovo Device [17aa:5081]
Kernel modules: snd_hda_intel
  --
  07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor 
[17aa:5081]
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
  07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller 
[17aa:5081]
Kernel modules: snd_hda_intel

  Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.8.16-050816-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Oct 23 10:17:36 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed
  Symptom_Card: Webcam Vitade AF - USB 2.0 Camera
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [acp - acp, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD0013GE
  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: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD0013GE
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

2020-11-05 Thread Florian Beier
I use this small script based on Giuseppe's findings as a workaround:

#!/bin/bash
sudo modprobe -r snd_rn_pci_acp3x
systemctl --user restart pulseaudio
sudo modprobe snd_rn_pci_acp3x

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

Title:
  [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output 
didn't work anymore. 
  Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 
5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get 
the exact same problem (On 20.04 Livesystem it works) 
  An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device 
uses the wrong Kernel Module (Audio Input is working since it uses the correct 
kernel module and driver)

  
  07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Lenovo Device [17aa:5081]
Kernel modules: snd_hda_intel
  --
  07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor 
[17aa:5081]
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
  07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller 
[17aa:5081]
Kernel modules: snd_hda_intel

  Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.8.16-050816-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Oct 23 10:17:36 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed
  Symptom_Card: Webcam Vitade AF - USB 2.0 Camera
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [acp - acp, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD0013GE
  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: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD0013GE
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1902519] [NEW] KDE shows bad pixels after hibernate

2020-11-02 Thread Florian Moll
Public bug reported:

After hibernation to disk kde shows bad pixels on home screen (look at attached 
screenshot)
sometimes there are also graphics related bugs in other applications
when I logout and login again or I do a reboot it works like before

maybe it has something to do with the nvidia graphics card?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Nov  2 13:03:10 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.100, 5.4.0-52-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:850a]
   Subsystem: CLEVO/KAPOK Computer GP107M [GeForce GTX 1050 Mobile] [1558:850a]
MachineType: XMG N85_N87,HJ,HJ1,HK1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=UUID=ef695d35-e2d0-422a-bb31-ef1dec2df0e0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.19
dmi.board.asset.tag: Tag 12345
dmi.board.name: N85_N87,HJ,HJ1,HK1
dmi.board.vendor: XMG
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: XMG
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.19:bd12/02/2017:svnXMG:pnN85_N87,HJ,HJ1,HK1:pvrNotApplicable:rvnXMG:rnN85_N87,HJ,HJ1,HK1:rvrNotApplicable:cvnXMG:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N85_N87,HJ,HJ1,HK1
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: XMG
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal kubuntu third-party-packages ubuntu

** Attachment added: "This is a screenshot"
   
https://bugs.launchpad.net/bugs/1902519/+attachment/5430234/+files/nvidia-bug.png

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

Title:
  KDE shows bad pixels after hibernate

Status in xorg package in Ubuntu:
  New

Bug description:
  After hibernation to disk kde shows bad pixels on home screen (look at 
attached screenshot)
  sometimes there are also graphics related bugs in other applications
  when I logout and login again or I do a reboot it works like before

  maybe it has something to do with the nvidia graphics card?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Nov  2 13:03:10 2020
  DistUpgrad

[Touch-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-07-08 Thread Florian Weimer
Is this a native s390x build, or something qemu-user? Thanks.

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+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 1878233] Re: Unable to locate package/Headers missing

2020-06-05 Thread Florian Hars
So you are saying that ubuntu 20.04 is unsuitable as the basis for a
developer system because the stability criteria actually forbid to fix a
packaging bug that makes it unusable?

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

Title:
  Unable to locate package/Headers missing

Status in qt3d-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  I am a scientific software developper and I'm trying to use Qt3D on Ubuntu 
20.04LTS.
  I am not used to filing bugs here, sorry if its not following the standards, 
any comments on this will also be appreciated.

  Here is a list of the packages I installed prior to this bug.
  sudo apt install qt3d5-dev
  sudo apt install qt3d5-dev-tools
  sudo apt install qt3d-assimpsceneimport-plugin
  sudo apt install qt3d-defaultgeometryloader-plugin
  sudo apt install qt3d-gltfsceneio-plugin
  sudo apt install qt3d-scene2d-plugin
  sudo apt install qml-module-qt3d

  I also ran the command line:
  sudo strip --remove-section=.note.ABI-tag 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

  as per my computer science colleague request

  But I am having errors left and right concerning the headers, as much
  as I actually have to include in my CMakleLists.txt those lines (I
  started to debug from Windows to Linux since our scientific build
  machine uses this target):

  #- *target*
  # Note: 3D Disabled on build machine because of 3D in QT
  if( ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
add_subdirectory(*target*)
set_target_properties(*target* PROPERTIES FOLDER "apps/*target*")
#Tell CMake to produce a visual studio Qt Project for integration with Qt 
Vs Tools
set_target_properties(*target* PROPERTIES VS_GLOBAL_KEYWORD Qt4VSv1.0)
  else
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DCore")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DRender")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras") ->this 
one useless
  endif()

  as you can see:
  /usr/include/x86_64-linux-gnu/qt5$ ls
  Qt3DCoreQt3DQuickRender   QtDBusQtNetwork   
QtPositioning   QtQuick   QtSerialPort  QtUiTools   QtWebKit
  Qt3DInput   Qt3DQuickScene2D  QtDesignerQtOpenGL
QtPositioningQuick  QtQuickParticles  QtSql QtWebChannel
QtWebKitWidgets
  Qt3DLogic   Qt3DRenderQtDesignerComponents  QtOpenGLExtensions  
QtPrintSupport  QtQuickShapes QtSvg QtWebEngine 
QtWidgets
  Qt3DQuick   QtConcurrent  QtGui QtPacketProtocol
QtQml   QtQuickTest   QtTestQtWebEngineCore QtXml
  Qt3DQuickInput  QtCoreQtHelpQtPlatformHeaders   
QtQmlDebug  QtQuickWidgetsQtUiPluginQtWebEngineWidgets

  And this sub-package that you have does not contain the headers.
  https://packages.ubuntu.com/focal/amd64/libqt53dextras5/filelist

  I think I will also be submitting there I find it weird.
  I will probably download Qt3D sources and temporarily link the headers 
directly there but this is far from optimal for a build machine, as you might 
expect. 

  And finaly, this packages appear when I tab on: apt install qt3d-op...
  but when I run the install it cant find it. This is probably the issue that 
you want to look at, as I will be going to this other package to see why the 
headers are not following.

  Thank you very much and I hope I followed the guidelines here are my infos:
  /usr/include/x86_64-linux-gnu/qt5$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy qt3d-opensource-src 
  N: Unable to locate package qt3d-opensource-src

  /usr/include/x86_64-linux-gnu/qt5$ apt-cache policy libqt53dextras5 
  libqt53dextras5:
Installed: 5.12.8+dfsg-0ubuntu1
Candidate: 5.12.8+dfsg-0ubuntu1
Version table:
   *** 5.12.8+dfsg-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  /usr/include/x86_64-linux-gnu/qt5$ sudo apt install qt3d-opensource-src 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package qt3d-opensource-src

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1878233/+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 1882249] [NEW] Qt3DQuickExtras headers are never packaged

2020-06-05 Thread Florian Hars
Public bug reported:

All the headers for the libraries in the Qt3DQuick packages
(called libqt53dquick5) are in the qt3d5-dev package, except
for those for libqt53dquickextras5, which I have not been able to find.

This makes it for example impossible to compile the code from
qt3d5-examples:

main.cpp:51:10: fatal error: Qt3DQuickExtras/qt3dquickwindow.h: No such file or 
directory
   51 | #include 
  |  ^~~
compilation terminated.

The file is missing in xenial, eoan, and focal, and present in qt3d5-dev
in bionic and groovy:

https://packages.ubuntu.com/search?searchon=contents&keywords=qt3dquickwindow.h&mode=exactfilename&suite=focal&arch=any

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libqt53dquickextras5 5.12.8+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-33.37-lowlatency 5.4.34
Uname: Linux 5.4.0-33-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  5 15:45:20 2020
InstallationDate: Installed on 2020-05-28 (7 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: qt3d-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt3d-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Qt3DQuickExtras headers are never packaged

Status in qt3d-opensource-src package in Ubuntu:
  New

Bug description:
  All the headers for the libraries in the Qt3DQuick packages
  (called libqt53dquick5) are in the qt3d5-dev package,
  except for those for libqt53dquickextras5, which I have not been able
  to find.

  This makes it for example impossible to compile the code from
  qt3d5-examples:

  main.cpp:51:10: fatal error: Qt3DQuickExtras/qt3dquickwindow.h: No such file 
or directory
 51 | #include 
|  ^~~
  compilation terminated.

  The file is missing in xenial, eoan, and focal, and present in
  qt3d5-dev in bionic and groovy:

  
https://packages.ubuntu.com/search?searchon=contents&keywords=qt3dquickwindow.h&mode=exactfilename&suite=focal&arch=any

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt53dquickextras5 5.12.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-lowlatency 5.4.34
  Uname: Linux 5.4.0-33-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 15:45:20 2020
  InstallationDate: Installed on 2020-05-28 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: qt3d-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1882249/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-05-21 Thread Florian Obradovic
Same here:

/etc/netplan/01-netcfg.yaml

network:
  version: 2
  renderer: networkd
  ethernets:
eno1:
  dhcp4: no
  bridges:
br0:
  dhcp4: yes
  interfaces:
- eno1
  addresses:
- 192.168.xx.xx/24
- 2a02:...::xx/64
  gateway4: 192.168.xx.xx
  gateway6: fe80::...
  nameservers:
   addresses: [192.168.xx.xx]

sudo add-apt-repository ppa:ddstreet/lp1860926
sudo apt-get update

FIXED it for me.

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true
  is reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network c

[Touch-packages] [Bug 1838181] Re: 3D Application cannot run anymore

2019-07-28 Thread Florian
For information the last update was:

$ less /var/log/apt/history.log
> Start-Date: 2019-07-28  08:23:57
> Commandline: aptdaemon role='role-commit-packages' sender=':1.107'
> Install: xdg-desktop-portal-gtk:amd64 (1.0.2-0ubuntu1.1, automatic), 
> xdg-desktop-portal:amd64 (1.0.3-0ubuntu0.2, automatic)
> Upgrade: language-pack-gnome-fr:amd64 (1:18.04+20190117, 1:18.04+20190718), 
> gir1.2-gtk-3.0:amd64 (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), 
> libegl1-mesa-dev:amd64 (18.2.8-0ubuntu0~18.04.2, 19.0.2-1ubuntu1.1~18.04.2), 
> sane-utils:amd64 (1.0.27-1~experimental3ubuntu2, 
> 1.0.27-1~experimental3ubuntu2.1), libegl-mesa0:amd64 
> (18.2.8-0ubuntu0~18.04.2, 19.0.2-1ubuntu1.1~18.04.2), libgtk-3-common:amd64 
> (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), libgtk-3-0:amd64 (3.22.30-1ubuntu3, 
> 3.22.30-1ubuntu4), libglapi-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libglapi-mesa:i386 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), mesa-common-dev:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libxatracker2:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libegl1-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), language-pack-en:amd64 (1:18.04+20180712, 
> 1:18.04+20190718), language-pack-fr:amd64 (1:18.04+20190117, 
> 1:18.04+20190718), libgbm1:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libsane1:amd64 (1.0.27-1~experimental3ubuntu2, 
> 1.0.27-1~experimental3ubuntu2.1), libgtk-3-bin:amd64 (3.22.30-1ubuntu3, 
> 3.22.30-1ubuntu4), libwayland-egl1-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libgail-3-0:amd64 (3.22.30-1ubuntu3, 
> 3.22.30-1ubuntu4), libgl1-mesa-dri:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-dri:i386 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-glx:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-glx:i386 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libsane-common:amd64 
> (1.0.27-1~experimental3ubuntu2, 1.0.27-1~experimental3ubuntu2.1), 
> gtk-update-icon-cache:amd64 (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), 
> mesa-vdpau-drivers:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), mesa-va-drivers:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libglx-mesa0:amd64 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2), libglx-mesa0:i386 (18.2.8-0ubuntu0~18.04.2, 
> 19.0.2-1ubuntu1.1~18.04.2)
> End-Date: 2019-07-28  08:24:59

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

Title:
  3D Application cannot run anymore

Status in xorg package in Ubuntu:
  New

Bug description:
  Since a recent update (done today 2019-07-28) I cannot start
  application that requires 3D (openGL support). It start being slow
  with degraded graphics, then freeze and finally crash with the
  following message :

   > i965: Failed to submit batchbuffer: Input/output error

  It also happened to me when I updated from Bionic Beaver to Disco. The
  Workaround was to reinstall a Bionic Beaver version. Now it does not
  work on this version anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 08:58:45 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:80df]
  InstallationDate: Installed on 2019-04-30 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.72
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook
  dmi.product.sku: W6X73EA#ABF
  dmi.produ

[Touch-packages] [Bug 1838181] [NEW] 3D Application cannot run anymore

2019-07-28 Thread Florian
Public bug reported:

Since a recent update (done today 2019-07-28) I cannot start application
that requires 3D (openGL support). It start being slow with degraded
graphics, then freeze and finally crash with the following message :

 > i965: Failed to submit batchbuffer: Input/output error

It also happened to me when I updated from Bionic Beaver to Disco. The
Workaround was to reinstall a Bionic Beaver version. Now it does not
work on this version anymore.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 28 08:58:45 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df]
InstallationDate: Installed on 2019-04-30 (89 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: HP HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.45
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80DF
dmi.board.vendor: HP
dmi.board.version: 87.72
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.sku: W6X73EA#ABF
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  3D Application cannot run anymore

Status in xorg package in Ubuntu:
  New

Bug description:
  Since a recent update (done today 2019-07-28) I cannot start
  application that requires 3D (openGL support). It start being slow
  with degraded graphics, then freeze and finally crash with the
  following message :

   > i965: Failed to submit batchbuffer: Input/output error

  It also happened to me when I updated from Bionic Beaver to Disco. The
  Workaround was to reinstall a Bionic Beaver version. Now it does not
  work on this version anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 08:58:45 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:80df]
  InstallationDate: Installed on 2019-04-30 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.72
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  d

[Touch-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync

2019-06-13 Thread Florian Schwarz
Issue may get closed.

Solved with upgrading to Ubuntu 19.04.

Nevertheless thanks for your help.

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

Title:
  cifs - poor upload speed with nautilus compared to rsync

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with
  cifs. Copying an 8 GB file...

  Upload (local -> mounted)
  - Nautilus/Nemo -> 6 MB/s
  - rsync -> 50-60 MB/s

  Download performance is also strange, but not my biggest concern.
  Download (mounted -> local)
  - Nautilus/Nemo -> 90 MB/s
  - rsync -> 50-60 MB/s

  rsync command (upload):
  rsync --progress /home/me/file.iso /mnt/cifs_media/

  fstab entry:
  //nas/media /mnt/cifs_media cifs 
vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700
 0 0

  Any idea, why Nautilus is uploading up to 10 times more slowly than
  rsync, although both using the same cifs, os, hardware, network etc.?

  PS: Further info for bug report
  1) The release of Ubuntu: Ubuntu 18.04 LTS
  2) The version of the package: Nautilus 3.26.3
  3) What you expected to happen: At least same speed as with using rsync
  4) What happened instead: See above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1782535/+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 1824205] Re: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem

2019-04-15 Thread Florian Richer
Only Line Out works

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

Title:
  [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My card is detected and with ubuntu-bug all output is detected but on
  Sound Control only SPDIF Output is showed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:47:50 2019
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B09
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824205/+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 1824205] Re: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem

2019-04-10 Thread Florian Richer
Line Out it work but Headphone output doesn't appear.

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

Title:
  [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My card is detected and with ubuntu-bug all output is detected but on
  Sound Control only SPDIF Output is showed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:47:50 2019
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B09
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824205/+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 1824205] [NEW] [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem

2019-04-10 Thread Florian Richer
Public bug reported:

My card is detected and with ubuntu-bug all output is detected but on
Sound Control only SPDIF Output is showed.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 18:47:50 2019
InstallationDate: Installed on 2019-04-10 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: Only some of outputs are working
Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.B0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B09
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My card is detected and with ubuntu-bug all output is detected but on
  Sound Control only SPDIF Output is showed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:47:50 2019
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B09
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824205/+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 305901]

2019-03-01 Thread Florian Weimer
(In reply to Szabolcs Nagy from comment #16)
> (In reply to Kees Cook from comment #14)
> > So I'd like to bring this back up and reiterate the issue: there is no
> > benefit to the early truncation, and it actively breaks lots of existing
> > software (which is why Debian and Ubuntu have had this fix for 10 years 
> > now).
> > 
> > What is the _benefit_ of early truncation that justifies breaking so many
> > existing cases?

I wonder if the early truncation was introduced to avoid cases where
aliasing can be used to avoid fortify length checks.  But then again,
truncation might not effectively prevent that after all.  And we do not
seem to use strlen followed by strcpy in vfprintf.

I haven't looked at this in detail, though.

> ideally sprintf, snprintf and sprintf_chk would be able to share code and
> have identical behaviour (currently there is a lot of duplicated logic in
> glibc with a potential for inconsistent behaviour).

Not sure what you mean by this.  The core vfprintf engine is shared, of
course.

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

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FOR

[Touch-packages] [Bug 1756516] Re: update libvorbis to 1.3.6

2019-02-25 Thread Florian Schlichting
libvorbis 1.3.6 is in cosmic and the CVEs were already fixed in bionic
(and earlier through security updates, I believe)

** Changed in: libvorbis (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  update libvorbis to 1.3.6

Status in libvorbis package in Ubuntu:
  Fix Released

Bug description:
  libvorbis 1.3.6 (2018-03-16) -- "Xiph.Org libVorbis I 20180316 (Now
  100% fewer shells)"

  * Fix CVE-2018-5146 - out-of-bounds write on codebook decoding.
  * Fix CVE-2017-14632 - free() on unitialized data
  * Fix CVE-2017-14633 - out-of-bounds read
  * Fix bitrate metadata parsing.
  * Fix out-of-bounds read in codebook parsing.
  * Fix residue vector size in Vorbis I spec.
  * Appveyor support
  * Travis CI support
  * Add secondary CMake build system.
  * Build system fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/1756516/+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 1782535] Re: cifs - poor upload speed with nautilus compared to rsync

2019-02-16 Thread Florian Schwarz
As you proposed:
https://gitlab.gnome.org/GNOME/glib/issues/1688

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

Title:
  cifs - poor upload speed with nautilus compared to rsync

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with
  cifs. Copying an 8 GB file...

  Upload (local -> mounted)
  - Nautilus/Nemo -> 6 MB/s
  - rsync -> 50-60 MB/s

  Download performance is also strange, but not my biggest concern.
  Download (mounted -> local)
  - Nautilus/Nemo -> 90 MB/s
  - rsync -> 50-60 MB/s

  rsync command (upload):
  rsync --progress /home/me/file.iso /mnt/cifs_media/

  fstab entry:
  //nas/media /mnt/cifs_media cifs 
vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700
 0 0

  Any idea, why Nautilus is uploading up to 10 times more slowly than
  rsync, although both using the same cifs, os, hardware, network etc.?

  PS: Further info for bug report
  1) The release of Ubuntu: Ubuntu 18.04 LTS
  2) The version of the package: Nautilus 3.26.3
  3) What you expected to happen: At least same speed as with using rsync
  4) What happened instead: See above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1782535/+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 1812095] Re: console login loop after entering username followed by RETURN

2019-02-01 Thread Florian
I'm also unable to login to my machine anymore. I can confirm the issue
for

linux-image-4.15.0-44-generic

I'm currently booting into linux-image-4.15.0-43-generic where the bug
doesn't exist.

Using Ubuntu 18.04.1 server.

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

Title:
  console login loop after entering username followed by RETURN

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
   login: 
  password:

  Just do nothing. About two seconds later ...

  login:
  password:

  login:
  password:

  login:
  password:

  After this being displayed three times:

  "Too many failure" or so and login is restarting.

  You cant login at all. Only solution: clear the password for the
  account you want to login with.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 16 19:34:30 2019
  InstallationDate: Installed on 2011-10-19 (2645 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1759836] Re: systemd-udevd consumes 100% of CPU

2018-12-14 Thread Florian Dittmer
Had the same problem on Dell Latitude E6400 laptop using Gentoo Linux
with udev versions newer than udev-233. Disabling Bluetooth in BIOS
solved the issue, however, I need bluetooth. Researching the web
resulted in this page:

https://askubuntu.com/questions/1028883/ubuntu-18-04-systemd-udevd-uses-
high-cpu-conflict-with-wifi

Following the instructions mentioned by one user in the comments helped
me to solve the cpu load issue with udev-239 and kernel 4.18.17,  while
Bluetooth still works.

Run the following command:

/lib/systemd/systemd-udevd -D
 
This should print garbage in endless loop containing ".../97-hid2hci.rules:"

If so, edit /lib/udev/rules.d/97-hid2hci.rules

and add

ACTION=="add",

in front of line mentioned by above command.

In my case, I had to change the following lines in 97-hid2hci.rules
from:

ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

to:

ACTION=="add", ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

And this fixed the issue (after reboot).

Best regards
Florian

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+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 1770195] [NEW] OpenSSL missing ciphers

2018-05-09 Thread Florian Lentz
Public bug reported:

In OpenSSL 1.1.0 several ciphers were simply removed. They can be re-
enabled by using "enable-weak-ssl-ciphers" option when building. This
should be done to increase compatibility.

** 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/1770195

Title:
  OpenSSL missing ciphers

Status in openssl package in Ubuntu:
  New

Bug description:
  In OpenSSL 1.1.0 several ciphers were simply removed. They can be re-
  enabled by using "enable-weak-ssl-ciphers" option when building. This
  should be done to increase compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1770195/+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 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

2018-01-27 Thread Florian Weimer
I believe systemd-resolved is still active on the system.  It's just not
queried over whatever interface nss_resolved uses, but over DNS, via the
stub resolver at 127.0.0.53.  If the systemd-resolved has bad data, it
will probably return bad data on the DNS interface as well.

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

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Suppose that:

  1. you have a "search" line in your /etc/resolv.conf file;
  2. it has two domains in it; and
  3. the first of the two domains does DNSSEC, including returning NSEC records 
for nonexisting hosts.

  In this situation, when you try to look up a host name in the second
  domain without specifying the domain part of the host name, the libc
  resolver will stop after it gets back the NSEC record and report that
  the host name doesn't exist, rather than moving on to the second
  domain in the search list and searching for the host in that domain.

  See also https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libc6 2.24-9ubuntu2.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 13 16:00:45 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
  InstallationDate: Installed on 2016-08-09 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: glibc
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (147 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717015/+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 1070873] Re: kde-telepathy, impossible to connect to gmail accounts

2018-01-09 Thread Florian Fainelli
I can confirm that signon-ui-service
(0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) and signon-ui-x11
(0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) allow me to get past
the Google account error. The account shows up, but going online does
not quite work yet (which I have seen before).

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

Title:
  kde-telepathy, impossible to connect to gmail accounts

Status in meta-kde-telepathy package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  Im running ubuntu 12.10 quantal and i have installed kde, when running
  kde-telepathy i have added a gmail account, and after entering the
  password it has revealed impossible to connect to it, it always says
  that the password is wrong when that is false.

  When using empathy, i have removed the gmail account and have added it
  again, now appears a XMLL window asking ubuntu permission to conenct
  to it, and now i was able to conenct to the gmail account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+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 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

2017-12-26 Thread Florian W.
Using artful, I updated these packages (everything that used to have version 
"17.2.2-0ubuntu1" on my system) to version "17.2.4-0ubuntu1~17.10.1" from 
-proposed:
libegl1-mesa:amd64 libgbm1:amd64 libgl1-mesa-dev:amd64 libgl1-mesa-dri:amd64 
libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-glx:i386 
libglapi-mesa:amd64 libglapi-mesa:i386 libgles2-mesa:amd64 
libwayland-egl1-mesa:amd64 libxatracker2:amd64 mesa-common-dev:amd64 
mesa-vdpau-drivers:amd64 mesa-vulkan-drivers:amd64

After a reboot, I can confirm Lawrence's observation that vulkan-
smoketest segfaulted on the old version, but seems to work fine using
the version from -proposed.

Since Lawrence forgot to remove the verification-needed-artful tag, I'm
going to remove it now.

** Tags removed: verification-needed-artful

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1184328] Re: xpdf crashes with SIGSEGV in GlobalParams::findFontFile()

2017-11-26 Thread Florian Schlichting
attached PDF files display without crashing in xpdf 3.04-5, hence
marking as "Fix Released"

** Changed in: xpdf (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  xpdf crashes with SIGSEGV in GlobalParams::findFontFile()

Status in Fontconfig:
  New
Status in Poppler:
  New
Status in xpdf-intl:
  New
Status in fontconfig package in Ubuntu:
  Confirmed
Status in poppler package in Ubuntu:
  Confirmed
Status in xpdf package in Ubuntu:
  Fix Released

Bug description:
  xpdf crashes with SIGSEGV when opening the public available document
  DOSB_Pruefungswegweiser_Komplett_web_11_12.pdf

  The document can be viewed with mupdf, but there are also issues (non-
  crash) with other viewers, see Bug 429.

  xpdf crashes with SIGSEGV when opening the public available document
  033_avv.pdf

  That document can be viewed with mupdf and other viewers without any
  issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xpdf 3.02-21build1
  ProcVersionSignature: Ubuntu 3.2.0-44.69-generic-pae 3.2.44
  Uname: Linux 3.2.0-44-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  Date: Sun May 26 13:57:27 2013
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: xpdf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1184328/+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 1380380] Re: free(1) translated output columns misaligned/translation bug

2017-11-02 Thread Florian Diesch
Problem still/again exists in 17.10

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

Title:
  free(1) translated output columns misaligned/translation bug

Status in Ubuntu Translations:
  Fix Committed
Status in procps package in Ubuntu:
  Invalid

Bug description:
  The free output is misaligned in German locale, but OK in POSIX/C
  locale.

  Since this does not properly render in text here, please see the
  attached screenshot.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: procps 1:3.3.9-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sun Oct 12 21:27:02 2014
  SourcePackage: procps
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (44 days ago)
  modified.conffile..etc.sysctl.conf: [modified]
  modified.conffile..etc.sysctl.d.10.network.security.conf: [modified]
  modified.conffile..etc.sysctl.d.10.ptrace.conf: [modified]
  mtime.conffile..etc.sysctl.conf: 2013-04-10T05:50:02.401636
  mtime.conffile..etc.sysctl.d.10.network.security.conf: 
2011-06-20T15:08:33.518598
  mtime.conffile..etc.sysctl.d.10.ptrace.conf: 2011-11-27T13:47:30.815492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1380380/+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 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

2017-10-09 Thread Florian Weimer
I filed a glibc bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=22273

However, I do not know if that bug is the root cause of the issue
reported here.

** Bug watch added: Sourceware.org Bugzilla #22273
   https://sourceware.org/bugzilla/show_bug.cgi?id=22273

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1719004/+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 1719959] Re: eglibc 2.19 leaks memory on getaddrinfo

2017-09-27 Thread Florian Weimer
Looks like this issue

  https://sourceware.org/bugzilla/show_bug.cgi?id=21336#c16

Quoting:

The announcement of CVE-2015-7547 said:

“
- Always malloc the second response buffer if needed.

  - Requires fix for sourceware bug 16574 to avoid memory leak.
commit d668061994a7486a3ba9c7d5e7882d85a2883707
commit ab09bf616ad527b249aca5f2a4956fd526f0712f
”



Coincidentally, this regression originally delayed the disclosure of
CVE-2015-7547.  The upstream glibc 2.19 branch already had the fix for
bug 16574 when CVE-2015-7547 was fixed, but our downstream 2.12 and 2.17
branches still needed it.

If you have you own resolv backports, you should really try to get a
valgrind-clean pass with the external resolv test suite:



** Bug watch added: Sourceware.org Bugzilla #21336
   https://sourceware.org/bugzilla/show_bug.cgi?id=21336

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-7547

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

Title:
  eglibc 2.19 leaks memory on getaddrinfo

Status in eglibc package in Ubuntu:
  New

Bug description:
  eglibc 2.19-0ubuntu6.13 is leaking memory when getaddrinfo is called
  with a bad address.

  Ubuntu version: 14.04.5 LTS

  We're using Travis CI to do our CI. https://travis-ci.org/curl/curl-
  fuzzer/builds/279417251 exhibits a memory leak when attempting to do a
  lookup on the fqdn "t.."

  I've done a bit of investigation - the memory is allocated here:

  Direct leak of 65536 byte(s) in 1 object(s) allocated from:
  #0 0x4be69c in __interceptor_malloc 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:64:3
  #1 0x7513bd05 in send_dg 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:1369
  #2 0x7513bd05 in __libc_res_nsend 
/build/eglibc-SvCtMH/eglibc-2.19/resolv/res_send.c:576

  
  Backtrace at point of allocation is:

  (gdb) bt
  #0  __libc_res_nsend (statp=statp@entry=0x702ffdb8, 
buf=buf@entry=0x702fc360 "\t:\001", buflen=19, 
buf2=buf2@entry=0x702fc374 "\371%\001", buflen2=buflen2@entry=19,
  ans=ans@entry=0x702fcf70 "\t:\201\203", anssiz=anssiz@entry=2048, 
ansp=ansp@entry=0x702fd7e0, ansp2=ansp2@entry=0x702fd7f0, 
nansp2=nansp2@entry=0x702fd7a0,
  resplen2=resplen2@entry=0x702fd7b0, 
ansp2_malloced=ansp2_malloced@entry=0x702fd7c0) at res_send.c:580
  #1  0x75138e2c in __GI___libc_res_nquery 
(statp=statp@entry=0x702ffdb8, name=0x702fcaf0 "t.", 
class=class@entry=1, type=type@entry=62321, answer=answer@entry=0x702fcf70 
"\t:\201\203",
  anslen=anslen@entry=2048, answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
  answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at 
res_query.c:227
  #2  0x75139863 in __libc_res_nquerydomain (domain=0x0, 
answerp2_malloced=0x702fd7c0, resplen2=0x702fd7b0, 
nanswerp2=0x702fd7a0, answerp2=0x702fd7f0, answerp=0x702fd7e0, 
anslen=2048,
  answer=0x702fcf70 "\t:\201\203", type=62321, class=1, 
name=0x60323f28 "t..", statp=0x702ffdb8) at res_query.c:591
  #3  __GI___libc_res_nsearch (statp=0x702ffdb8, 
name=name@entry=0x60323f28 "t..", class=class@entry=1, 
type=type@entry=62321, answer=answer@entry=0x702fcf70 "\t:\201\203", 
anslen=anslen@entry=2048,
  answerp=answerp@entry=0x702fd7e0, 
answerp2=answerp2@entry=0x702fd7f0, 
nanswerp2=nanswerp2@entry=0x702fd7a0, 
resplen2=resplen2@entry=0x702fd7b0,
  answerp2_malloced=answerp2_malloced@entry=0x702fd7c0) at 
res_query.c:381
  #4  0x7fffef6f0c73 in _nss_dns_gethostbyname4_r 
(name=name@entry=0x60323f28 "t..", pat=pat@entry=0x702fde00, 
buffer=buffer@entry=0x702fd890 "\177", buflen=buflen@entry=1064,
  errnop=errnop@entry=0x702fddd0, herrnop=herrnop@entry=0x702fde30, 
ttlp=ttlp@entry=0x0) at nss_dns/dns-host.c:315
  #5  0x7595a636 in gaih_inet (name=, 
name@entry=0x60323f28 "t..", service=, 
req=req@entry=0x60d0cfb8, pai=pai@entry=0x702fdf40, 
naddrs=naddrs@entry=0x702fdf30)
  at ../sysdeps/posix/getaddrinfo.c:858
  #6  0x7595d93d in __GI_getaddrinfo (name=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, pai=0x702fe9a0) at 
../sysdeps/posix/getaddrinfo.c:2414
  #7  0x00449825 in __interceptor_getaddrinfo () at 
/home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:2169
  #8  0x0051dbe5 in curl_dogetaddrinfo (hostname=0x60323f28 "t..", 
service=0x702fec60 "80", hints=0x60d0cfb8, result=0x702fe9a0, 
line=12

[Touch-packages] [Bug 661640] Re: no sound after resume from suspend [Conexant ID 2c06] PA test tone failed (alsa tone succeeded)

2017-05-09 Thread Florian Heinle
David,

thanks for your reply.
As you may have guessed from the date I opened the bug, that was seven years 
ago. I no longer have the machine that was affected by this problem.

However, I do remember the sound working in later Ubuntu versions. So I
guess... fix released?

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

Title:
  no sound after resume from suspend [Conexant ID 2c06] PA test tone
  failed (alsa tone succeeded)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: pulseaudio

  Before suspending my laptop, sound sent to my external monitor via
  HDMI works perfectly. However, after waking from suspend, all I hear
  from my speakers is low frequency buzzing and sound playback has
  stopped working

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florian   16250 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 47'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:14f12c06,14f1000f,0010 
HDA:10951392,10280242,0010 HDA:83847616,10280242,00100201'
 Controls  : 31
 Simple ctrls  : 19
  Date: Sat Oct 16 11:15:04 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 
(20100928)
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: pulseaudio
  Symptom: audio
  Title: [Conexant ID 2c06] PA test tone failed (alsa tone succeeded)
  dmi.bios.date: 01/07/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0WP007
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd01/07/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0WP007:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/661640/+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 178442] Re: Pulseaudio fails to initialize ICE1712 chipsets

2017-05-08 Thread Florian Zeitz
Unfortunately I must say I've moved on from using both Ubuntu and the
affected card within the last 10 years. Maybe one of the several other
affected people can provide some feedback.

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

Title:
  Pulseaudio fails to initialize ICE1712 chipsets

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in alsa-lib source package in Lucid:
  Won't Fix
Status in pulseaudio source package in Lucid:
  Won't Fix

Bug description:
  Binary package hint: pulseaudio

  I have a problem that makes pulseaudio unusable for me.
  I noticed the only device listed by pulseaudio is my webcam (as an input 
device obviously), so I tried starting pulseaudio from the command line to see 
what was happening.
  This resulted in:
  "ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 
'cards.ICE1712.pcm.surround71.0:CARD=0'
  ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned 
error: No such file or directory
  ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No such file or 
directory
  ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM surround71:0
  W: alsa-util.c: Device hw:0 doesn't support 2 channels, changed to 10.
  W: alsa-util.c: Device hw:0 doesn't support sample format s16le, changed to 
s32le.
  W: alsa-util.c: Cannot find fallback mixer control "PCM".
  E: module-alsa-sink.c: Failed to create sink object
  E: module.c: Failed to load  module "module-alsa-sink" (argument: 
"device_id=0 
sink_name=alsa_output.pci_1412_1712_sound_card_0_alsa_playback_0"): 
initialization failed.ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find 
definition 'cards.ICE1712.pcm.surround71.0:CARD=0'
  ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned 
error: No such file or directory
  ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No such file or 
directory
  ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM surround71:0
  W: alsa-util.c: Device hw:0 doesn't support 2 channels, changed to 12.
  W: alsa-util.c: Device hw:0 doesn't support sample format s16le, changed to 
s32le.
  W: alsa-util.c: Cannot find fallback mixer control "Mic".
  E: module-alsa-source.c: Failed to create source object
  E: module.c: Failed to load  module "module-alsa-source" (argument: 
"device_id=0 
source_name=alsa_input.pci_1412_1712_sound_card_0_alsa_capture_0"): 
initialization failed."

  This is an up to date Hardy installation.
  Soundcard is a M-Audio Audiophile 2496.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/178442/+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 443004] Fw: a piece of useful info

2017-04-10 Thread Florian Reinheimer
Hi,

I found  some interesting information  that seems to be very  useful,
check it out here http://tekky.net/alive.php?7978


Speak to you later, gibking

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

Title:
  Buttons disappear or do not respond to mouse clicks in Eclipse

Status in Azureus:
  Invalid
Status in Eclipse:
  Fix Released
Status in LibGTK:
  Fix Released
Status in eclipse package in Ubuntu:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released

Bug description:
  After update from alpha 6 to beta Karmic Koala - Eclispe is no longer working 
correct. It seems to be a problem with GTK.
  Few buttons are not working - nothing happens when pressing the button or the 
expected dialog is not shown as expected.
  I also tested other eclispe package with same result.

  eclipse 3.5.1 downloaded directly from www.eclipse.org has this bug.

  Solution: Install eclipse 3.5.1-0ubuntu7 (or later) from the Ubuntu
  archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/azureus/+bug/443004/+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 1677290] Re: Add automated tests run for all MRs on staging branch

2017-04-05 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Add automated tests run for all MRs on staging branch

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Currently the system apps jenkins instance doesn't run CI for merge
  requests targeting lp:webbrowser-app/staging. It should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677290/+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 1677291] Re: Implement readable feedback on automated tests on MRs

2017-04-05 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

Title:
  Implement readable feedback on automated tests on MRs

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The output from jenkins on merge requests is hard to read. It could be
  made much more developer-friendly allow seeing at a glance what tests
  passed and what tests failed without having to navigate through
  several layers of jenkins.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677291/+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 1457661] Re: facebook image upload not working in the webapp

2017-04-05 Thread Florian Boucault
** Changed in: webapps-sprint
   Status: Fix Committed => Fix Released

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

Title:
  facebook image upload not working in the webapp

Status in Canonical System Image:
  Fix Released
Status in The Webapps-core project:
  Invalid
Status in webapps-sprint:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  the facebook webapp does not support image upload. not really a bug,
  perhaps is just something you missed! What woould it take to
  implement that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1457661/+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 1677218] Re: Facebook uses mobile UI on desktop; probably wrong UA

2017-04-05 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Facebook uses mobile UI on desktop; probably wrong UA

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Facebook uses mobile UI on desktop; probably wrong UA

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677218/+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 1670715] Re: Last browser tab not fully displayed at app startup despite being current

2017-04-05 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
 Assignee: Andrew Hayzen (ahayzen) => Florian Boucault (fboucault)

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-ui-extras (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-ui-extras (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

Title:
  Last browser tab not fully displayed at app startup despite being
  current

Status in Canonical System Image:
  New
Status in ubuntu-ui-extras package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  I have a browser session with 9 tabs open (more than fit in the app’s
  window’s width). The last tab is the current one. After I close the
  app and open it again, the current tab is correctly restored, but the
  tab handle is not fully in view. See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670715/+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 1679996] [NEW] Move unit tests execution from package build to autopkgtest

2017-04-05 Thread Florian Boucault
Public bug reported:

Unit tests are currently executed during deb package build
(debian/rules) and should be moved to be executed by autopkgtest
(debian/tests/control).

** Affects: webbrowser-app (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: next-candidates

** Tags added: next-candidates

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

Title:
  Move unit tests execution from package build to autopkgtest

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Unit tests are currently executed during deb package build
  (debian/rules) and should be moved to be executed by autopkgtest
  (debian/tests/control).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1679996/+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 1677660] Re: [browser] Missing tab asset in narrow mode

2017-04-05 Thread Florian Boucault
Original reporter cannot reproduce the issue on Zesty. Tested with deb, snap 
and from source.
Same here on Xenial.

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

Title:
  [browser] Missing tab asset in narrow mode

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  This looks like a fairly recent regression (which might have happened
  when switching to the TabsBar component provided by ubuntu-ui-extras).

  On desktop, when resizing the window to its minimum width and opening
  the tabs view, it can be clearly seen that there's a missing asset for
  the tab. See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677660/+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 1677660] Re: [browser] Missing tab asset in narrow mode

2017-04-04 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  [browser] Missing tab asset in narrow mode

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  This looks like a fairly recent regression (which might have happened
  when switching to the TabsBar component provided by ubuntu-ui-extras).

  On desktop, when resizing the window to its minimum width and opening
  the tabs view, it can be clearly seen that there's a missing asset for
  the tab. See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677660/+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 1672444] Re: Negative number of tabs at left of the browser

2017-04-04 Thread Florian Boucault
** Changed in: ubuntu-ui-extras (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: ubuntu-ui-extras (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

Title:
  Negative number of tabs at left of the browser

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-extras package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  I am not able to reproduce it. I opened the webbrowser-app after
  updating the silo to the new build, and maximized it. After minimizing
  it again, I spotted the negative number of hidden tabs at left. Not
  sure what steps do trigger this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672444/+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 1666554] Re: webbrowser - when you drop back a tab it always places the tab at the last position, should be placed where the mouse pointer is, i think

2017-04-03 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Tags added: current-milestone next-candidates

** Changed in: webbrowser-app (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  webbrowser - when you drop back a tab it always places the tab at the
  last position, should be placed where the mouse pointer is, i think

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  webbrowser - when you drop back a tab it always places the tab at the
  last position, should be placed where the mouse pointer is, i think

  open the webbrowser app, open many tabs, drag a random tab out into a
  new window, drop the tab back into the tabs bar, it always places the
  tab at the last position on the tabs bar. this not like a bug bug,
  maybe i'm just to used to the google's chrome tab management way

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666554/+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 1677292] Re: Generate test coverage metrics

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Generate test coverage metrics

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  We need to enable code coverage metrics in webbrowser-app. Ideally
  this would include coverage from the QML tests, not just C++ unit
  tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677292/+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 1677289] Re: Provide clean-state test runners

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Provide clean-state test runners

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Make sure that executing tests:

  1) does not depend on the state of the developer's system (using a LXD
  container)

  2) does not take over your desktop (using a nested display server)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677289/+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 1677290] Re: Add automated tests run for all MRs on staging branch

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  Add automated tests run for all MRs on staging branch

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Currently the system apps jenkins instance doesn't run CI for merge
  requests targeting lp:webbrowser-app/staging. It should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677290/+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 1677288] Re: Make sure all types of automated tests are obvious to run

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Make sure all types of automated tests are obvious to run

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  This includes some high-level documentation on how to run all the
  tests and how to run individual tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677288/+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 1677291] Re: Implement readable feedback on automated tests on MRs

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Implement readable feedback on automated tests on MRs

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The output from jenkins on merge requests is hard to read. It could be
  made much more developer-friendly allow seeing at a glance what tests
  passed and what tests failed without having to navigate through
  several layers of jenkins.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677291/+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 1253784] Re: Webbrowser doesn't respect the HTML5 "required" attribute

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Webbrowser doesn't respect the HTML5 "required" attribute

Status in Canonical System Image:
  New
Status in Oxide:
  Triaged
Status in webbrowser-app:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The browser should prevent the form from being submitted

  ex: http://www.w3schools.com/html/tryhtml5_input_required.htm

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1253784/+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 1377033] Re: [Browser] Ability to switch to the desktop mode (desktop version)

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  [Browser] Ability to switch to the desktop mode (desktop version)

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  
  As a mobile phone user I want to view the desktop version of website so that 
I can get most features out of the web.

  In stead of supporting to change user agents, I thinks it's fairly
  reasonable to be able to switch in between mobile and desktop mode for
  both desktop and touch version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1377033/+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 1672444] Re: Negative number of tabs at left of the browser

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Negative number of tabs at left of the browser

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-extras package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I am not able to reproduce it. I opened the webbrowser-app after
  updating the silo to the new build, and maximized it. After minimizing
  it again, I spotted the negative number of hidden tabs at left. Not
  sure what steps do trigger this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672444/+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 1675012] Re: browser not switching to picking mode when launched by the peer picker

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  browser not switching to picking mode when launched by the peer picker

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

Bug description:
  When choose webbrowser-app as a source for content from the peer
  picker when the browser is not already running, it doesn't go into
  picking mode.  However, if the browser is already running it switches
  nicely to picking mode.  Maybe a race condition at startup missing the
  signal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675012/+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 1656252] Re: Applications fail to start on the second use

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Applications fail to start on the second use

Status in Canonical System Image:
  In Progress
Status in address-book-app package in Ubuntu:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  zesty desktop
  unity8 session snap 349

  Test Case:
  1. Launch the webbrowser from the app scope
  2. close it (or the app crashes)
  3. Launch the webbrowser from the app scope

  Expected result:
  It starts twice

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+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 1670715] Re: Last browser tab not fully displayed at app startup despite being current

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Last browser tab not fully displayed at app startup despite being
  current

Status in Canonical System Image:
  New
Status in ubuntu-ui-extras package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I have a browser session with 9 tabs open (more than fit in the app’s
  window’s width). The last tab is the current one. After I close the
  app and open it again, the current tab is correctly restored, but the
  tab handle is not fully in view. See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670715/+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 1677295] Re: Add automated check that prevents merging if test coverage decreases

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Low

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Add automated check that prevents merging if test coverage decreases

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Once code coverage is enabled (see bug #1677292), it would be good to
  set up a mechanism that prevents merging if a merge request decreases
  significantly the code coverage. There would need to be a way to
  manually override this mechanism, of course.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677295/+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 1677286] Re: Convert autopilot tests to QML tests

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Convert autopilot tests to QML tests

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Work is in progress to convert existing autopilot tests to QML tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677286/+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 1677288] Re: Make sure all types of automated tests are obvious to run

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Make sure all types of automated tests are obvious to run

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  This includes some high-level documentation on how to run all the
  tests and how to run individual tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677288/+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 1677289] Re: Provide clean-state test runners

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Provide clean-state test runners

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Make sure that executing tests:

  1) does not depend on the state of the developer's system (using a LXD
  container)

  2) does not take over your desktop (using a nested display server)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677289/+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 1677291] Re: Implement readable feedback on automated tests on MRs

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Implement readable feedback on automated tests on MRs

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The output from jenkins on merge requests is hard to read. It could be
  made much more developer-friendly allow seeing at a glance what tests
  passed and what tests failed without having to navigate through
  several layers of jenkins.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677291/+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 1677258] Re: keyboard navigation from url search should populate field

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  keyboard navigation from url search should populate field

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  when searching from the url field, we should populate the url field
  with the search results when using arrow key to navigate the result
  list.

  For example:
  1) type pastebin.ub
  2) results show me
  http://pastebin.ubuntu.com/43434343434
  http://pastebin.ubuntu.com/23232323232
  3) use the arrow keys to navigate

  Expected results:
  the url field  should be populated with the entry that has been navigated to. 
The enter button should not be executed so user can modify the url that is in 
the field

  Actual results:
  nothing is populated in the url field until a search result is selected, and 
this executes the search giving user no opportunity to edit the url string

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677258/+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 1677298] Re: Transfer manual tests from wiki to bzr branch

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Transfer manual tests from wiki to bzr branch

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The webbrowser-app test plan is currently published at
  https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app.

  It should be transferred to a text file in the code repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677298/+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 1677294] Re: Publish test coverage metrics automatically

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Publish test coverage metrics automatically

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Code coverage metrics, once enabled (see bug #1677292), should be
  automatically published by the system apps jenkins instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677294/+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 1677218] Re: Facebook uses mobile UI on desktop; probably wrong UA

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Facebook uses mobile UI on desktop; probably wrong UA

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Facebook uses mobile UI on desktop; probably wrong UA

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677218/+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 1677290] Re: Add automated tests run for all MRs on staging branch

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Add automated tests run for all MRs on staging branch

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Currently the system apps jenkins instance doesn't run CI for merge
  requests targeting lp:webbrowser-app/staging. It should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677290/+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 1677292] Re: Generate test coverage metrics

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Generate test coverage metrics

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  We need to enable code coverage metrics in webbrowser-app. Ideally
  this would include coverage from the QML tests, not just C++ unit
  tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677292/+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 1677295] Re: Add automated check that prevents merging if test coverage decreases

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Add automated check that prevents merging if test coverage decreases

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Once code coverage is enabled (see bug #1677292), it would be good to
  set up a mechanism that prevents merging if a merge request decreases
  significantly the code coverage. There would need to be a way to
  manually override this mechanism, of course.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677295/+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 1677660] Re: Missing tab asset in narrow mode

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Missing tab asset in narrow mode

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  This looks like a fairly recent regression (which might have happened
  when switching to the TabsBar component provided by ubuntu-ui-extras).

  On desktop, when resizing the window to its minimum width and opening
  the tabs view, it can be clearly seen that there's a missing asset for
  the tab. See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677660/+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 1677300] Re: Investigate what manual tests could be automated

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Investigate what manual tests could be automated

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The webbrowser-app test plan (currently at
  https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app , see
  bug #1677298) has a number of tests that could be automated, with some
  development effort.

  Let’s try to identify which ones can be automated, and file followup
  bugs to track their automation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677300/+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 1677301] Re: Investigate if tests can emulate touch devices

2017-03-31 Thread Florian Boucault
** Tags added: current-milestone

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

Title:
  Investigate if tests can emulate touch devices

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Investigate if there is a way to create an automated test environment
  that resembles devices (phone, tablet) as closely as possible (e.g.
  run under Unity8, simulate touch events, with the right resolutions,
  etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677301/+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 1677294] Re: Publish test coverage metrics automatically

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Low

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Publish test coverage metrics automatically

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Code coverage metrics, once enabled (see bug #1677292), should be
  automatically published by the system apps jenkins instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677294/+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 1677300] Re: Investigate what manual tests could be automated

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Investigate what manual tests could be automated

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The webbrowser-app test plan (currently at
  https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app , see
  bug #1677298) has a number of tests that could be automated, with some
  development effort.

  Let’s try to identify which ones can be automated, and file followup
  bugs to track their automation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677300/+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 1677298] Re: Transfer manual tests from wiki to bzr branch

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Transfer manual tests from wiki to bzr branch

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The webbrowser-app test plan is currently published at
  https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app.

  It should be transferred to a text file in the code repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677298/+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 1677301] Re: Investigate if tests can emulate touch devices

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Investigate if tests can emulate touch devices

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Investigate if there is a way to create an automated test environment
  that resembles devices (phone, tablet) as closely as possible (e.g.
  run under Unity8, simulate touch events, with the right resolutions,
  etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677301/+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 1672444] Re: Negative number of tabs at left of the browser

2017-03-31 Thread Florian Boucault
** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Negative number of tabs at left of the browser

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-extras package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I am not able to reproduce it. I opened the webbrowser-app after
  updating the silo to the new build, and maximized it. After minimizing
  it again, I spotted the negative number of hidden tabs at left. Not
  sure what steps do trigger this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672444/+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 1677258] Re: keyboard navigation from url search should populate field

2017-03-31 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  keyboard navigation from url search should populate field

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  when searching from the url field, we should populate the url field
  with the search results when using arrow key to navigate the result
  list.

  For example:
  1) type pastebin.ub
  2) results show me
  http://pastebin.ubuntu.com/43434343434
  http://pastebin.ubuntu.com/23232323232
  3) use the arrow keys to navigate

  Expected results:
  the url field  should be populated with the entry that has been navigated to. 
The enter button should not be executed so user can modify the url that is in 
the field

  Actual results:
  nothing is populated in the url field until a search result is selected, and 
this executes the search giving user no opportunity to edit the url string

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677258/+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 1377033] Re: [Browser] Ability to switch to the desktop mode (desktop version)

2017-03-30 Thread Florian Boucault
** Tags added: next-candidates

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

Title:
  [Browser] Ability to switch to the desktop mode (desktop version)

Status in Ubuntu UX:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  
  As a mobile phone user I want to view the desktop version of website so that 
I can get most features out of the web.

  In stead of supporting to change user agents, I thinks it's fairly
  reasonable to be able to switch in between mobile and desktop mode for
  both desktop and touch version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1377033/+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 1677258] Re: keyboard navigation from url search should populate field

2017-03-30 Thread Florian Boucault
** Tags added: next-candidates

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

Title:
  keyboard navigation from url search should populate field

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  when searching from the url field, we should populate the url field
  with the search results when using arrow key to navigate the result
  list.

  For example:
  1) type pastebin.ub
  2) results show me
  http://pastebin.ubuntu.com/43434343434
  http://pastebin.ubuntu.com/23232323232
  3) use the arrow keys to navigate

  Expected results:
  the url field  should be populated with the entry that has been navigated to. 
The enter button should not be executed so user can modify the url that is in 
the field

  Actual results:
  nothing is populated in the url field until a search result is selected, and 
this executes the search giving user no opportunity to edit the url string

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677258/+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 1295567] Re: White block above web content

2017-03-29 Thread Florian Boucault
** Changed in: webbrowser-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  White block above web content

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  I've seen this a few times. See screenshot.
  Randomly on various websites I see a white box above the content being 
rendered.
  If you tap the screen the website moves up to cover (and fix the issue) the 
white area.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: webbrowser-app 0.23+14.04.20140319-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Fri Mar 21 08:48:55 2014
  InstallationDate: Installed on 2014-03-21 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140321)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1295567/+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 1677218] [NEW] Facebook uses mobile UI on desktop; probably wrong UA

2017-03-29 Thread Florian Boucault
Public bug reported:

Facebook uses mobile UI on desktop; probably wrong UA

** 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/1677218

Title:
  Facebook uses mobile UI on desktop; probably wrong UA

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Facebook uses mobile UI on desktop; probably wrong UA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677218/+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 1671034] Re: Cannot use apt or other binaries installed on the system from the ubuntu-terminal-app snap

2017-03-28 Thread Florian Boucault
** Also affects: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-terminal-app (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Cannot use apt or other binaries installed on the system from the
  ubuntu-terminal-app snap

Status in Canonical System Image:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  unity8 deb
  terminal app 0.11 (57) 483kB devmode

  On a unity8 desktop session as a deb a user cannot execute binaries
  installed on the system. For example:

  $ apt-cache policy unity8
  Ubuntu Core does not use apt-get, see 'snap --help'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671034/+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 1605327] Re: Opening terminal-app does not focus on password prompt

2017-03-28 Thread Florian Boucault
** Changed in: ubuntu-terminal-app
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: ubuntu-terminal-app
   Status: New => Fix Released

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

Title:
  Opening terminal-app does not focus on password prompt

Status in Ubuntu Terminal App:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid

Bug description:
  When I open the terminal app, I get asked for my password. If I just
  start typing, the password gets written in the terminal bash and not
  in the correct popup prompt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1605327/+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 1676454] Re: Window size not always remembered

2017-03-27 Thread Florian Boucault
** Attachment added: "Test program, QML code"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+attachment/4847463/+files/MyWindow.qml

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

Title:
  Window size not always remembered

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Launch window_size QML program
  2. Resize the window
  3. Close the window
  4. Re-launch the program

  Expected result:
  Size of the window was saved and reused when launching the app the second 
time.

  Current result:
  Only the width of the window is correctly saved and re-applied. The height is 
back to the default size specified in the QML Window element.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+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 1676454] Re: Window size not always remembered

2017-03-27 Thread Florian Boucault
** Attachment added: "Test program, standalone binary"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+attachment/4847464/+files/window_size

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

Title:
  Window size not always remembered

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Launch window_size QML program
  2. Resize the window
  3. Close the window
  4. Re-launch the program

  Expected result:
  Size of the window was saved and reused when launching the app the second 
time.

  Current result:
  Only the width of the window is correctly saved and re-applied. The height is 
back to the default size specified in the QML Window element.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+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 1676454] Re: Window size not always remembered

2017-03-27 Thread Florian Boucault
** Attachment added: "Video of the same bug in terminal"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+attachment/4847465/+files/terminal_bug.mov

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

Title:
  Window size not always remembered

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Launch window_size QML program
  2. Resize the window
  3. Close the window
  4. Re-launch the program

  Expected result:
  Size of the window was saved and reused when launching the app the second 
time.

  Current result:
  Only the width of the window is correctly saved and re-applied. The height is 
back to the default size specified in the QML Window element.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+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 1676454] Re: Window size not always remembered

2017-03-27 Thread Florian Boucault
Note that the issue is only reproduceable by some people on some
systems. We were not able to figure out what the difference was between
those systems

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

Title:
  Window size not always remembered

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Launch window_size QML program
  2. Resize the window
  3. Close the window
  4. Re-launch the program

  Expected result:
  Size of the window was saved and reused when launching the app the second 
time.

  Current result:
  Only the width of the window is correctly saved and re-applied. The height is 
back to the default size specified in the QML Window element.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+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 1676454] [NEW] Window size not always remembered

2017-03-27 Thread Florian Boucault
Public bug reported:

Steps to reproduce:

1. Launch window_size QML program
2. Resize the window
3. Close the window
4. Re-launch the program

Expected result:
Size of the window was saved and reused when launching the app the second time.

Current result:
Only the width of the window is correctly saved and re-applied. The height is 
back to the default size specified in the QML Window element.

** 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/1676454

Title:
  Window size not always remembered

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Launch window_size QML program
  2. Resize the window
  3. Close the window
  4. Re-launch the program

  Expected result:
  Size of the window was saved and reused when launching the app the second 
time.

  Current result:
  Only the width of the window is correctly saved and re-applied. The height is 
back to the default size specified in the QML Window element.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676454/+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 1675424] [NEW] Window geometries not saved until unity8 exits when number of CPU cores too low

2017-03-23 Thread Florian Boucault
Public bug reported:

WindowStateStorage uses QtConcurrent::run with the default QThreadPool
to write in the SQLite database. But the functions passed are not
guaranteed to be executed if there is no available thread in the pool.

Steps to reproduce reliably:
1. Use a computer (or a VM) with only one CPU core
2. Start any app
3. Resize the app window
4. Close the app
5. Restart the same app

Expected result:
After the app is restarted the window size is back to the size given by the 
user.

Current result:
After the app is restarted the window size is the default size.

However if unity8 is restarted the geometry is then correctly saved to
DB and correctly restored after the app is launched.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Florian Boucault (fboucault)
 Status: In Progress

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: unity8 (Ubuntu)
   Status: New => In Progress

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

Title:
  Window geometries not saved until unity8 exits when number of CPU
  cores too low

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  WindowStateStorage uses QtConcurrent::run with the default QThreadPool
  to write in the SQLite database. But the functions passed are not
  guaranteed to be executed if there is no available thread in the pool.

  Steps to reproduce reliably:
  1. Use a computer (or a VM) with only one CPU core
  2. Start any app
  3. Resize the app window
  4. Close the app
  5. Restart the same app

  Expected result:
  After the app is restarted the window size is back to the size given by the 
user.

  Current result:
  After the app is restarted the window size is the default size.

  However if unity8 is restarted the geometry is then correctly saved to
  DB and correctly restored after the app is launched.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1675424/+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 1534771] Re: Automatically switching to downloads page awkward in large layout

2017-03-22 Thread Florian Boucault
** Branch linked: lp:~fboucault/webbrowser-app/downloads_emblem

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

Title:
  Automatically switching to downloads page awkward in large layout

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Currently in small or expanded mode, we automatically switch to the
  Downloads page when requesting to download a file from the browser. We
  should consider changing this behavior, especially on expanded mode,
  the main reason being it's quite disruptive if you want to download a
  file and continue to browse. In expanded mode, all of the tabs get
  obscured by the Downloads header and page and you have to use the back
  arrow to get back to the tabs.

  Couple of possible options:

  1. In expanded mode, don't switch to page but instead show some sort
  of download icon while it's in progress, possibly next to the drawer
  icon or in the tab bar if there is room. Clicking on it would bring
  you to the downloads page. Note there is already a download indicator
  in the top system toolbar but it's not super obvious, especially on a
  large screen. Might be better for app to display it in addition..

  2. Prompt with dialog when downloading, with options to "Automatically
  show Downloads", "Never show Downloads", "Prompt each time.." or
  something along those lines

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1534771/+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 1674296] Re: In Terminal app, when settings window is already opened clicking on the settings icon does not raise it

2017-03-21 Thread Florian Boucault
Test app is a QML app that reproduces the behaviour. Click on the
content of the root window and observe that the child window is not
raised.

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1674296/+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 1674296] Re: When preference window is already opened clicking on the settings icon does not raise it

2017-03-21 Thread Florian Boucault
** Description changed:

  Steps:
  
+ 0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon
  
  Expected:
  Settings window is raised and focused

** Summary changed:

- When preference window is already opened clicking on the settings icon does 
not raise it
+ In Terminal app, when settings window is already opened clicking on the 
settings icon does not raise it

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

Title:
  In Terminal app, when settings window is already opened clicking on
  the settings icon does not raise it

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-terminal-app package in Ubuntu:
  New

Bug description:
  Steps:

  0. Start ubuntu-terminal-app
  1. Click on settings icon to open settings window
  2. Click on terminal window
  3. Click again on settings icon

  Expected:
  Settings window is raised and focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1674296/+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


  1   2   3   4   5   6   7   8   >