[Touch-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se

2019-07-09 Thread Daniel van Vugt
I see it is queued here:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1556439/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2019-07-09 Thread Daniel van Vugt
Please don't upload anything for bionic till this is done:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/32

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2019-07-09 Thread Hui Wang
OK, let us skip the cosmic, I will upload a debdiff for bionic.

Thanks.

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-07-09 Thread Matthew Geier
>> FWIW, I think not booting a 19.04 ISO is probably fine,

Unless like me, you have just upgraded your hardware to a Ryzen 3600x
and find you have to downgrade from the version you are using on your
old machine to use the new machine you just purchased.

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se

2019-07-09 Thread Daniel van Vugt
I can't see the SRU anywhere yet...?

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1556439/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2019-07-09 Thread ADTopkek
Upgraded from Ubuntu server 16 to 18 and I too am having this issue.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

2019-07-09 Thread Bryan Quigley
I've confirmed, that #9 is is not reproducible with systemd from Debian.
The runs from there with our without DNSSEC=yes are the same.  They
differ on Ubuntu.

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1835181] Re: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS

2019-07-09 Thread Andreas Hasenack
Same thing on bionic now.


a) SSL with incorrect name fails as expected:
ubuntu@bionic-ldap-start-tls-1835181:~$ sudo truncate -s 0 /var/log/syslog 

ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -H 
ldaps://bionic-ldap-start-tls-1835181.lxd
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)

ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -H 
ldaps://bionic-ldap-start-tls-1835181.lxd -d -1 2>&1 | grep ^TLS
TLS: hostname (bionic-ldap-start-tls-1835181.lxd) does not match common name in 
certificate (ubuntu).

ubuntu@bionic-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 21:02:07 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1015 fd=14 
ACCEPT from IP=10.0.100.234:45518 (IP=0.0.0.0:636)
Jul  9 21:02:07 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1015 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 21:02:07 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1015 fd=14 
closed (connection lost)
Jul  9 21:02:13 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1016 fd=14 
ACCEPT from IP=10.0.100.234:45520 (IP=0.0.0.0:636)
Jul  9 21:02:13 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1016 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 21:02:13 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1016 fd=14 
closed (connection lost)

b) START_TLS with incorrect hostname fails as expected:
ubuntu@bionic-ldap-start-tls-1835181:~$ sudo truncate -s 0 /var/log/syslog 
ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -ZZ -h 
bionic-ldap-start-tls-1835181.lxd
ldap_start_tls: Connect error (-11)
additional info: TLS: hostname does not match CN in peer certificate
ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -ZZ -h 
bionic-ldap-start-tls-1835181.lxd -d -1 2>&1 | grep ^TLS
TLS: hostname (bionic-ldap-start-tls-1835181.lxd) does not match common name in 
certificate (ubuntu).
ubuntu@bionic-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 21:03:01 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1017 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 21:03:01 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1017 op=1 UNBIND
Jul  9 21:03:01 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1017 fd=14 
closed
Jul  9 21:03:09 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1018 fd=14 
ACCEPT from IP=10.0.100.234:37820 (IP=0.0.0.0:389)
Jul  9 21:03:09 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1018 op=0 EXT 
oid=1.3.6.1.4.1.1466.20037
Jul  9 21:03:09 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1018 op=0 
STARTTLS
Jul  9 21:03:09 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1018 op=0 
RESULT oid= err=0 text=
Jul  9 21:03:09 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1018 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 21:03:09 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1018 op=1 UNBIND
Jul  9 21:03:09 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1018 fd=14 
closed


Now the good cases, to show the ssl setup is correct:

a) SSL with ubuntu host:
ubuntu@bionic-ldap-start-tls-1835181:~$ sudo truncate -s 0 /var/log/syslog 
ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -H ldaps://ubuntu/
anonymous
ubuntu@bionic-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 fd=14 
ACCEPT from IP=10.0.100.234:45528 (IP=0.0.0.0:636)
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 op=0 BIND 
dn="" method=128
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 op=0 
RESULT tag=97 err=0 text=
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 op=1 EXT 
oid=1.3.6.1.4.1.4203.1.11.3
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 op=1 WHOAMI
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 op=1 
RESULT oid= err=0 text=
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 op=2 UNBIND
Jul  9 21:03:48 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1019 fd=14 
closed

b) START_TLS with ubuntu host:
ubuntu@bionic-ldap-start-tls-1835181:~$ sudo truncate -s 0 /var/log/syslog 
ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -ZZ -h ubuntu
anonymous
ubuntu@bionic-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 21:04:14 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1020 op=0 
STARTTLS
Jul  9 21:04:14 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1020 op=0 
RESULT oid= err=0 text=
Jul  9 21:04:14 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1020 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 21:04:14 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1020 op=1 BIND 
dn="" method=128
Jul  9 21:04:14 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1020 op=1 
RESULT tag=97 err=0 text=
Jul  9 21:04:14 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1020 op=2 EXT 
oid=1.3.6.1.4.1.4203.1.11.3
Jul  9 21:04:14 bionic-ldap-start-tls-1835181 slapd[2600]: conn=1020 op=2 WHOAMI
Jul  9 

[Touch-packages] [Bug 1835181] Re: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS

2019-07-09 Thread Andreas Hasenack
I didn't have TLS_REQCERT set in /etc/ldap/ldap.conf during these tests,
but the manpage says the value "demand" (equal to "hard") is the default
in eoan at least.

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

Title:
  OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between
  ldaps:// and ldap:// with STARTTLS

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  This is the same bug as
  https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927 which
  has been closed.

  Tested and confirmed present with vivid, wily, xenial and bionic

  Also logged with openldap as
  http://www.openldap.org/its/index.cgi/Incoming?id=8374 however I think
  that this is a packaging issue caused by using GNUTLS rather than
  OpenSSL.

  Important: to replicate the issue you need to connect to an LDAP
  server which presents a certificate with a CN that DOES NOT MATCH the
  connection URI passed to the OpenLDAP client. In practice, this is
  simple enough to achieve by using the IP address of a server rather
  than the FQDN.

  The core of the issue is that the handling of the
  LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between
  servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs.

  When accessing server with an invalid certificate, the results are:

  ldaps://

  never  OK
  hard   Error: can't contact LDAP server
  demand Error: can't contact LDAP server
  allow  OK
  tryError: can't contact LDAP server

  ldap:// plus explicit ldap_start_tls_s()

  never  OK
  hard   OK
  demand OK
  allow  OK
  tryOK

  Based on all the documentation, the results should be the same between
  approaches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1835181/+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 1835181] Re: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS

2019-07-09 Thread Andreas Hasenack
It seems to be working fine in eoan. I setup a CA and issued a server
certificate, and setup openldap with ssl/start_tls.

The hostname of the container:
ubuntu@eoan-ldap-start-tls-1835181:~$ hostname -f
eoan-ldap-start-tls-1835181.lxd

ubuntu@eoan-ldap-start-tls-1835181:~$ ping -c 1 $(hostname -f)
PING eoan-ldap-start-tls-1835181.lxd (10.0.100.137) 56(84) bytes of data.
64 bytes from ubuntu (10.0.100.137): icmp_seq=1 ttl=64 time=0.009 ms

The certificate has a CN of "ubuntu", however, so I expect all ssl related 
connections to fail unless I use that name:
ubuntu@eoan-ldap-start-tls-1835181:~$ openssl x509 -in /etc/ldap/ubuntu.pem 
-noout -subject
subject=C = UK, ST = Some-State, O = Internet Widgits Pty Ltd, CN = ubuntu

Via /etc/hosts, ubuntu points at the same ip as the hostname:
ubuntu@eoan-ldap-start-tls-1835181:~$ ping -c 1 ubuntu
PING ubuntu (10.0.100.137) 56(84) bytes of data.
64 bytes from ubuntu (10.0.100.137): icmp_seq=1 ttl=64 time=0.034 ms

So let's begin!

a) SSL with incorrect name fails as expected:
ubuntu@eoan-ldap-start-tls-1835181:~$ ldapwhoami -x -H 
ldaps://eoan-ldap-start-tls-1835181.lxd/
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)

ubuntu@eoan-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 20:39:30 eoan-ldap-start-tls-1835181 slapd[220]: conn=1002 fd=14 ACCEPT 
from IP=10.0.100.137:58498 (IP=0.0.0.0:636)
Jul  9 20:39:30 eoan-ldap-start-tls-1835181 slapd[220]: conn=1002 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 20:39:30 eoan-ldap-start-tls-1835181 slapd[220]: conn=1002 fd=14 closed 
(connection lost)

Debugging shows:
ubuntu@eoan-ldap-start-tls-1835181:~$ ldapwhoami -x -H 
ldaps://eoan-ldap-start-tls-1835181.lxd/ -d -1 2>&1|grep ^TLS
TLS: hostname (eoan-ldap-start-tls-1835181.lxd) does not match common name in 
certificate (ubuntu).
TLS: can't connect: (unknown error code).

b) START TLS with incorrect name also fails as expected:
ubuntu@eoan-ldap-start-tls-1835181:~$ ldapwhoami -x -ZZ -h 
eoan-ldap-start-tls-1835181.lxd
ldap_start_tls: Connect error (-11)
additional info: (unknown error code)

Note that the log confirms start tls was used:
ubuntu@eoan-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 20:40:44 eoan-ldap-start-tls-1835181 slapd[220]: conn=1004 fd=14 ACCEPT 
from IP=10.0.100.137:52990 (IP=0.0.0.0:389)
Jul  9 20:40:44 eoan-ldap-start-tls-1835181 slapd[220]: conn=1004 op=0 EXT 
oid=1.3.6.1.4.1.1466.20037
Jul  9 20:40:44 eoan-ldap-start-tls-1835181 slapd[220]: conn=1004 op=0 STARTTLS
Jul  9 20:40:44 eoan-ldap-start-tls-1835181 slapd[220]: conn=1004 op=0 RESULT 
oid= err=0 text=
Jul  9 20:40:44 eoan-ldap-start-tls-1835181 slapd[220]: conn=1004 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 20:40:44 eoan-ldap-start-tls-1835181 slapd[220]: conn=1004 fd=14 closed 
(connection lost)

Debugging explains why, and it's the same reason:
ubuntu@eoan-ldap-start-tls-1835181:~$ ldapwhoami -x -ZZ -h 
eoan-ldap-start-tls-1835181.lxd -d -1 2>&1 | grep ^TLS
TLS: hostname (eoan-ldap-start-tls-1835181.lxd) does not match common name in 
certificate (ubuntu).
TLS: can't connect: (unknown error code).


Now let's try the working case, by using "ubuntu" as the target hostname.

a) SSL works fine:
ubuntu@eoan-ldap-start-tls-1835181:~$ ldapwhoami -x -H ldaps://ubuntu/ 
anonymous
ubuntu@eoan-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 fd=14 ACCEPT 
from IP=10.0.100.137:58524 (IP=0.0.0.0:636)
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 op=0 BIND 
dn="" method=128
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 op=0 RESULT 
tag=97 err=0 text=
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 op=1 EXT 
oid=1.3.6.1.4.1.4203.1.11.3
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 op=1 WHOAMI
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 op=1 RESULT 
oid= err=0 text=
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 op=2 UNBIND
Jul  9 20:42:31 eoan-ldap-start-tls-1835181 slapd[220]: conn=1006 fd=14 closed

b) START_TLS too:
ubuntu@eoan-ldap-start-tls-1835181:~$ ldapwhoami -x -ZZ -h ubuntu
anonymous
ubuntu@eoan-ldap-start-tls-1835181:~$ tail /var/log/syslog 
Jul  9 20:43:28 eoan-ldap-start-tls-1835181 slapd[220]: conn=1007 op=0 STARTTLS
Jul  9 20:43:28 eoan-ldap-start-tls-1835181 slapd[220]: conn=1007 op=0 RESULT 
oid= err=0 text=
Jul  9 20:43:28 eoan-ldap-start-tls-1835181 slapd[220]: conn=1007 fd=14 TLS 
established tls_ssf=256 ssf=256
Jul  9 20:43:28 eoan-ldap-start-tls-1835181 slapd[220]: conn=1007 op=1 BIND 
dn="" method=128
Jul  9 20:43:28 eoan-ldap-start-tls-1835181 slapd[220]: conn=1007 op=1 RESULT 
tag=97 err=0 text=
Jul  9 20:43:28 eoan-ldap-start-tls-1835181 slapd[220]: conn=1007 op=2 EXT 
oid=1.3.6.1.4.1.4203.1.11.3
Jul  9 20:43:28 eoan-ldap-start-tls-1835181 

[Touch-packages] [Bug 1835957] Re: cupsd gobbles up resources

2019-07-09 Thread Sebastien Bacher
Thank you for your bug report, could you add your 'journalctl -b 0' log
after a boot having the issue?

Could you also try if downgrading to the debs from
https://bugs.launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.8/+build/16742546
makes the issue got away?

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

Title:
  cupsd gobbles up resources

Status in cups package in Ubuntu:
  New

Bug description:
  My computer has got very slow since 4 or 5 weeks. Finally, I checked
  resource usage with  and the culprit seems to be cupsd. Here is
  an output line from a few minutes after boot:

  30900 root  20   0  305452 287396   5768 S   5,3  9,3   0:41.34
  cupsd

  Then after an hour and a half (with nothing printed):

  30900 root  20   0 2565692 2,125g   2240 R  79,0 71,9  93:01.45
  cupsd

  So %CPU grows 5,3 -> 79,0 and %MEM, 9,3 -> 71,9. Not good.

  A user on a local forum asked whether printing anything helped, and,
  certainly, it did. After I did (print something), cupsd was happy with
  less than 1% of CPU and MEM.

  So if I print something after every boot, the problem does go away.
  But that is not really a solution, is it?

  Running Lubuntu 16.04.6 LTS (32-bit). cups version is
  2.1.3-4ubuntu0.9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1835957/+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 1835957] [NEW] cupsd gobbles up resources

2019-07-09 Thread Sakari Aaltonen
Public bug reported:

My computer has got very slow since 4 or 5 weeks. Finally, I checked
resource usage with  and the culprit seems to be cupsd. Here is an
output line from a few minutes after boot:

30900 root  20   0  305452 287396   5768 S   5,3  9,3   0:41.34
cupsd

Then after an hour and a half (with nothing printed):

30900 root  20   0 2565692 2,125g   2240 R  79,0 71,9  93:01.45
cupsd

So %CPU grows 5,3 -> 79,0 and %MEM, 9,3 -> 71,9. Not good.

A user on a local forum asked whether printing anything helped, and,
certainly, it did. After I did (print something), cupsd was happy with
less than 1% of CPU and MEM.

So if I print something after every boot, the problem does go away. But
that is not really a solution, is it?

Running Lubuntu 16.04.6 LTS (32-bit). cups version is 2.1.3-4ubuntu0.9.

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

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

Title:
  cupsd gobbles up resources

Status in cups package in Ubuntu:
  New

Bug description:
  My computer has got very slow since 4 or 5 weeks. Finally, I checked
  resource usage with  and the culprit seems to be cupsd. Here is
  an output line from a few minutes after boot:

  30900 root  20   0  305452 287396   5768 S   5,3  9,3   0:41.34
  cupsd

  Then after an hour and a half (with nothing printed):

  30900 root  20   0 2565692 2,125g   2240 R  79,0 71,9  93:01.45
  cupsd

  So %CPU grows 5,3 -> 79,0 and %MEM, 9,3 -> 71,9. Not good.

  A user on a local forum asked whether printing anything helped, and,
  certainly, it did. After I did (print something), cupsd was happy with
  less than 1% of CPU and MEM.

  So if I print something after every boot, the problem does go away.
  But that is not really a solution, is it?

  Running Lubuntu 16.04.6 LTS (32-bit). cups version is
  2.1.3-4ubuntu0.9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1835957/+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 1797282] Re: fsck not running at all on reboot

2019-07-09 Thread Ewan Mellor
In my case, Ubuntu 18.04 running on AWS, the problem was as follows:

1. /etc/fstab had 0 in the 6th (passno) field.  I presume this is the default 
that AWS places there, or maybe this is determined by the Ubuntu template on 
AWS.
2. According to a comment that I found on Stack Overflow, this is used by 
mkinitramfs to decide not to put fsck in the initrd.  This is *in no way* 
obvious.
3. Without fsck in the initrd, it can't run the fsck, so it just prints a 
message instead.  This message tells you that a fsck is recommended, but it 
doesn't tell you why it hasn't done one.

To fix this:
1. I changed /etc/fstab to have a "1" in the passno field
2. update-initramfs -u
3. reboot, and the check runs as expected.

I think the following changes should be made:

1. There should be a console warning during startup if the root volume cannot 
be checked because fsck is not available.
2. If /etc/fstab is coming from an Ubuntu-controlled template, then passno for 
the root volume should be set to 1.  I know that AWS will fail to boot the 
instance if the fsck goes interactive, necessitating manual repairs, but surely 
failing to boot the instance is better than silently running on a corrupt root 
filesystem.
3. This should be in some documentation somewhere.  The fact that mkinitramfs 
will exclude fsck from the initrd if it thinks you don't need it is 
particularly obscure.  If there is some kind of "getting started with Ubuntu on 
AWS" then this should be in there.

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

Title:
  fsck not running at all on reboot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD
  that says:

  *** /dev/xvda1 should be checked for errors ***

  I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in
  /etc/default/grub before running 'sudo update-grub'. I also verified
  that fsck was present in /boot/grub/grub.cfg afterwards, before
  rebooting the server.

  Surprisingly I was met with the same error message in MOTD when
  logging in. I then ran tune2fs to see when the last check was
  performed and this is the output:

  $ sudo tune2fs -l /dev/xvda1  | grep checked
  Last checked: Wed Sep 12 16:17:00 2018

  I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1,
  but after another reboot I was still met with the same error message
  and the timestamp for last checked was unchanged.

  I have the same problem on all the servers that was upgraded from
  16.04 to 18.04, but also on a new server installed directly with
  18.04.

  In should be mentioned that the servers are AWS EC2 instances, so I
  have no way of trying to run fsck from a liveusb.

  Another user has reported the same issue here:
  https://ubuntuforums.org/showthread.php?t=2403368

  I'm not quite sure what information is needed, but attached are some
  basic information about the system.

  Please let me know if you need any any other outputs or logs.

  Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1
  LTS (Xubuntu) and it works fine. Seems to be related to the server
  edition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797282/+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 1830858] Re: TOCTOU vulnerability in _get_ignore_dom (report.py)

2019-07-09 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/eoan/apport/ubuntu

** Branch linked: lp:apport

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

Title:
  TOCTOU vulnerability in _get_ignore_dom (report.py)

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Dear Ubuntu Security Team,

  I would like to report a privilege escalation vulnerability in Apport.
  The vulnerability is a TOCTOU which enables me to trick Apport into
  reading any file on the system and including it in a crash report
  file.

  I have attached a proof-of-concept which triggers the vulnerability. I
  have tested it on an up-to-date Ubuntu 18.04. Run it as follows:

  bunzip2 PoC.tar.bz2
  tar -xf PoC.tar
  cd PoC
  make
  ./gencrashreport /etc/shadow

  At this point the following file has been created:

  /var/crash/_usr_share_apport_apport.0.crash

  You can use the apport-unpack tool to decompress this file. If you
  look at the contents of the CoreDump file then you will see that it
  contains the contents of /etc/shadow (or whichever other file you
  passed on the command line of gencrashreport).

  The bug has a couple of mitigations:

  1. My PoC does not work if a file named /var/crash/.lock already
  exists and is owned by root. This file will only exist if Apport has
  previously generated a crash report. Based on an informal survey of my
  own 4 computers (yes - maybe I don't need that many), it usually does
  not exist (unless the computer is used for security research).

  2. The generated crash report file,
  /var/crash/_usr_share_apport_apport.0.crash, is only readable by root
  and by the whoopsie user. It will be uploaded to daisy.ubuntu.com if
  you create a file named /var/crash/_usr_share_apport_apport.0.upload,
  but that is not a huge security concern because it wouldn't be of much
  benefit to an attacker. However, I have found some integer overflow
  vulnerabilities in whoopsie (which I will report separately). If those
  overflows can be exploited to gain code execution in whoopsie, then
  this will enable an attacker to read the contents of the crash report
  file.

  To improve the effectiveness of the first mitigation, I would
  recommend that you make sure that /var/crash/.lock is created (and
  owned by root) by the Ubuntu installer and/or whoopsie when it starts
  up. It does not fix the root cause though, which I will describe next.

  This is the source location of the TOCTOU vulnerability:

  
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu
  /bionic-devel=2fc8fb446c78e950d643bf49bb7d4a0dc3b05429#n962

  Apport allows the user to place a file in their home directory named
  `~/.apport-ignore.xml`. The call to os.access() on line 962 is
  intended to check that this file belongs to the correct user. But on
  line 967, the file is read again using xml.dom.minidom.parse. This
  creates a window of opportunity for an attacker to replace the file
  with a symlink. The symlink does not need to point to a valid XML
  file, because there is a try-except around the call to the parser, so
  if the file is invalid then Apport just ignores it and continues.
  However, the contents of the file still ends up in Apport's heap.

  Here's a summary of how the PoC works:

  1. Start a /bin/sleep and kill it with a SIGSEGV.
  2. Apport starts up to generate a crash report for /bin/sleep
  3. Replace ~/.apport-ignore.xml with a symlink at exactly the right moment, 
so that Apport loads a forbidden file into memory.
  4. Wait until Apport drops privileges so that we can kill it with a SIGTRAP.
  5. A second Apport starts up to generate a crash report for the first Apport.
  6. The second Apport writes out a crash report for the first, containing a 
copy of the forbidden file in the core dump.

  Apport tries quite hard to not run recursively on itself, so I had to
  jump through a few hoops to make the PoC work:

  1. Apport sets a lock on /var/crash/.lock, using lockf. But locks
  created by lockf are only "advisory". If I own the file, then I can
  replace it with a different file, thereby deactivating the lock. This
  is why my PoC only works if /var/crash/.lock doesn't already exist. I
  need to create it before Apport does, so that I can maintain ownership
  of it.

  2. Apport has signal handlers for most of the core-generating signals,
  like SIGSEGV. But it doesn't have a handler for SIGTRAP, so that's
  what my PoC uses.

  3. Apport is started with an RLIMIT_CORE value of 1, which is another
  recursion detection mechanism (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/498525/comments/3).
  But it is possible for another process to change it to zero, using
  prlimit.

  As I mentioned earlier, I have also found a few other vulnerabilities
  in whoopsie and Apport. I will file them as 

[Touch-packages] [Bug 1818902] Re: The io.elementary.camera package installs on Ubuntu Disk 19.04 normally, but does not open the video image.

2019-07-09 Thread Chris Mayo
I think a change in Ubuntu broke ClutterGstCamera.

I don't use io.elementary.camera but have my own program that also uses
ClutterGstCamera. Up until about a month ago it was working fine on
18.04. Now it gives the same error:

Clutter-Gst-CRITICAL **: Unable to setup device without element factory,
node and name set 0x2c83820 0x2fe26f0 (nil)

It doesn't work on 19.04 either. Still works on Gentoo Linux.


** Package changed: camera-app (Ubuntu) => clutter-gst-3.0 (Ubuntu)

** Changed in: clutter-gst-3.0 (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  The io.elementary.camera package installs on Ubuntu Disk 19.04
  normally, but does not open the video image.

Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed

Bug description:
  Hello guys

  I installed the io.elementary.camera package from Elementary OS on
  Ubuntu Disk 19.04 normally, but message appears that it does not
  recognize the webcam. Note I have the Juno Elementary OS installed on
  the same machine and the Webcam works normally.

  I installed through the repository:

  sudo add-apt-repository ppa: elementary-os / daily
  sudo apt update
  sudo apt install io.elementary.camera

  In the description, there is the option pantheon-camera, but this one
  says to be with broken package and does not install. Could it be this
  that does not let the webcam work? Look!

  sudo apt install pantheon-camera
  [sudo] password for edson:
  Reading package lists ... Ready
  Building dependency tree
  Reading status information ... Ready
  Some packages could not be installed. This may mean that
  you asked for an impossible situation or, if you are using the
  unstable distribution, that some required packages have not been created yet 
or have been removed from Incoming.
  The following information may help resolve the situation:

  The following packages have mismatched dependencies:
  pantheon-camera: Depends: io.elementary.camera but will not install
  E: Impossible to fix problems, you kept (hold) broken packages.

  Note When I enter synaptcis there is no broken package.

  If you uninstall io.elementary.camera and try to install the pantheon-
  camera the same broken package information appears.

  The installation of io.elementary.camera is performed successfully on
  Ubuntu 19.04 Disk, but does not appear the image of the video and nor
  does it recognize the webcam, video attachments.

  When you try to open the camera through the terminal the following
  error message appears:

  edson @ edson-p6540br: ~ $ io.elementary.camera

  (io.elementary.camera:10218): Clutter-WARNING **: 16: 43: 29.698:
  Whoever translated default: LTR did so wrongly.

  (io.elementary.camera:10218): Clutter-Gst-CRITICAL **: 16: 43: 29.753: Unable 
to setup device without element factory, node and name set 0x55a19aa51200 
0x7fc2ec00e240 (nil)
  edson @ edson-p6540br: ~ $

  I ask you to forward the responsible team so that the correction can
  be carried out.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gst-3.0/+bug/1818902/+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 1797282] Re: fsck not running at all on reboot

2019-07-09 Thread Ewan Mellor
** Changed in: systemd (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  fsck not running at all on reboot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD
  that says:

  *** /dev/xvda1 should be checked for errors ***

  I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in
  /etc/default/grub before running 'sudo update-grub'. I also verified
  that fsck was present in /boot/grub/grub.cfg afterwards, before
  rebooting the server.

  Surprisingly I was met with the same error message in MOTD when
  logging in. I then ran tune2fs to see when the last check was
  performed and this is the output:

  $ sudo tune2fs -l /dev/xvda1  | grep checked
  Last checked: Wed Sep 12 16:17:00 2018

  I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1,
  but after another reboot I was still met with the same error message
  and the timestamp for last checked was unchanged.

  I have the same problem on all the servers that was upgraded from
  16.04 to 18.04, but also on a new server installed directly with
  18.04.

  In should be mentioned that the servers are AWS EC2 instances, so I
  have no way of trying to run fsck from a liveusb.

  Another user has reported the same issue here:
  https://ubuntuforums.org/showthread.php?t=2403368

  I'm not quite sure what information is needed, but attached are some
  basic information about the system.

  Please let me know if you need any any other outputs or logs.

  Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1
  LTS (Xubuntu) and it works fine. Seems to be related to the server
  edition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797282/+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 1835940] [NEW] perf core dump at tool/perf/util/namespaces.c:144

2019-07-09 Thread Qin Li
Public bug reported:

Running the following perf collect inside a running docker could
potentially crash:

$ perf record -F 100 -ag -o /tmp/perf-100Hz-10s -- sleep 10

The dump is caused by SIGSEGV for de-referencing nullptr in
nsinfo__copy() in at namespaces.c:144

$ lldb -c /tmp/cores/perf.core.07092019
(lldb) target create --core "/tmp/cores/perf.core.07092019"
Core file '/tmp/cores/perf.core.07092019' (x86_64) was loaded.
(lldb) bt
* thread #1, name = 'perf', stop reason = signal SIGSEGV
  * frame #0: 0x558f2dda2014 perf`nsinfo__copy(nsi=0x) at 
namespaces.c:144
frame #1: 0x558f2dd98779 perf`map__new(machine=0x558f31213c48, 
start=140723782385664, len=8192, pgoff=0, d_maj=, 
d_min=, ino=0, ino_gen=0, prot=5, flags=4098, filename="", 
type=MAP__FUNCTION, thread=0x558f316f94c0) at map.c:192
frame #2: 0x558f2dd96a39 
perf`machine__process_mmap2_event(machine=0x558f31213c48, 
event=0x7fdd8f1105f0, sample=) at machine.c:1428
frame #3: 0x558f2dd9d7bc perf`ordered_events__deliver_event at 
session.c:1343
frame #4: 0x558f2dd9d798 perf`ordered_events__deliver_event
frame #5: 0x558f2dd9d790 
perf`ordered_events__deliver_event(oe=0x558f31219e00, event=) 
at session.c:120
frame #6: 0x558f2dda1073 perf`ordered_events__flush at 
ordered-events.c:211
frame #7: 0x558f2dda0fb6 
perf`ordered_events__flush(oe=0x558f31219e00, how=OE_FLUSH__ROUND) at 
ordered-events.c:278
frame #8: 0x558f2dd9e854 perf`perf_session__process_event at 
session.c:1383
frame #9: 0x558f2dd9e570 
perf`perf_session__process_event(session=0x558f31213b60, 
event=0x7fdd8f148050, file_offset=565328) at session.c:1511
frame #10: 0x558f2dd9ff40 perf`perf_session__process_events at 
session.c:1903
frame #11: 0x558f2dd9fec0 
perf`perf_session__process_events(session=0x558f31213b60) at session.c:1957
frame #12: 0x558f2dcd76bc perf`cmd_record at builtin-record.c:442
frame #13: 0x558f2dcd7695 perf`cmd_record at builtin-record.c:574
frame #14: 0x558f2dcd7695 perf`cmd_record at builtin-record.c:1115
frame #15: 0x558f2dcd7601 perf`cmd_record(argc=, 
argv=) at builtin-record.c:1809
frame #16: 0x558f2dd3da01 perf`run_builtin(p=0x558f2e1f12b8, 
argc=9, argv=0x7ffc21201e30) at perf.c:297
frame #17: 0x558f2dd3dcfe perf`handle_internal_command(argc=9, 
argv=0x7ffc21201e30) at perf.c:349
frame #18: 0x558f2dcc17b9 perf`main [inlined] 
run_argv(argcp=, argv=) at perf.c:393
frame #19: 0x558f2dcc17ae perf`main(argc=, 
argv=0x7ffc21201e30) at perf.c:537
frame #20: 0x7fdd8fad5b97 libc.so.6`__libc_start_main + 231
frame #21: 0x558f2dcc1c3a perf`_start + 42

The fix for this has already been merged to Linux 4.19-rc, since
8/10/2018, see the original lkml post
https://lore.kernel.org/lkml/20180810133614.9925-1-bev...@mesosphere.com/.

bf2e710b3cb84 (Krister Johansen         2017-07-05 18:48:09 -0700 137) struct 
nsinfo *nsinfo__copy(struct nsinfo *nsi)
bf2e710b3cb84 (Krister Johansen         2017-07-05 18:48:09 -0700 138) {
bf2e710b3cb84 (Krister Johansen         2017-07-05 18:48:09 -0700 139)  struct 
nsinfo *nnsi;
bf2e710b3cb84 (Krister Johansen         2017-07-05 18:48:09 -0700 140) 
3f4417d693b43 (Benno Evers              2018-08-10 15:36:13 +0200 141)  if (nsi 
== NULL)
3f4417d693b43 (Benno Evers              2018-08-10 15:36:13 +0200 142)          
return NULL;
3f4417d693b43 (Benno Evers              2018-08-10 15:36:13 +0200 143) 
bf2e710b3cb84 (Krister Johansen         2017-07-05 18:48:09 -0700 144)  nnsi = 
calloc(1, sizeof(*nnsi));

I verified locally that this fix works by manually applying to 4.15 and
rebuild perf executable after that.

To port the fix to 4.15, or other versions earlier than 4.19-rc, we could run:
$ git cherry-pick 3f4417d693b43

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

** Attachment added: "perf.core.07092019.gz"
   
https://bugs.launchpad.net/bugs/1835940/+attachment/5275915/+files/perf.core.07092019.gz

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

Title:
  perf core dump at tool/perf/util/namespaces.c:144

Status in linux package in Ubuntu:
  New

Bug description:
  Running the following perf collect inside a running docker could
  potentially crash:

  $ perf record -F 100 -ag -o /tmp/perf-100Hz-10s -- sleep 10

  The dump is caused by SIGSEGV for de-referencing nullptr in
  nsinfo__copy() in at namespaces.c:144

  $ lldb -c /tmp/cores/perf.core.07092019
  (lldb) target create --core "/tmp/cores/perf.core.07092019"
  Core file '/tmp/cores/perf.core.07092019' (x86_64) was loaded.
  (lldb) bt
  * thread #1, name = 'perf', stop reason = signal SIGSEGV
* frame #0: 0x558f2dda2014 

[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-07-09 Thread Brian Murray
** Tags removed: rls-ee-incoming

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-07-09 Thread Brian Murray
** Tags added: rls-ee-incoming

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1835922] [NEW] missing gl* symbols in version 19.0.2

2019-07-09 Thread Jean-Marc Le Roux
Public bug reported:

Linking with libosmesa6-dev version 19.0.2 will fail because all the gl*
symbols are missing:

```
[100%] Linking CXX executable bin/minko-converter
../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o):
 In function `jas_stream_tmpfile':
jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better 
use `mkstemp'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::clear(unsigned int, float, 
float, float, float, float, unsigned int, unsigned int)':
OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask'
OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth'
OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor'
OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
unsigned int, int)':
OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, 
int)':
OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned 
int, unsigned int, unsigned int, void*)':
OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned 
int)':
OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer'
OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData'
OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)':
OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer'
OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData'
OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, 
unsigned int, unsigned int, unsigned int, unsigned int)':
OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer'
OpenGLES2Context.cpp:(.text+0x559): undefined reference to 
`glVertexAttribPointer'
OpenGLES2Context.cpp:(.text+0x59a): undefined reference to 
`glDisableVertexAttribArray'
OpenGLES2Context.cpp:(.text+0x61e): undefined reference to 
`glEnableVertexAttribArray'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::createVertexAttributeArray()':
OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function 
`minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)':
OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to 
`glDeleteVertexArrays'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned 
int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned 
int, void*)':
OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture'
OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::uploadTexture2dData(unsigned 
int, unsigned int, unsigned int, unsigned int, void*)':
OpenGLES2Context.cpp:(.text+0x7c5): undefined reference to `glBindTexture'
OpenGLES2Context.cpp:(.text+0x7ec): undefined reference to `glTexSubImage2D'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function `minko::render::OpenGLES2Context::setShaderSource(unsigned int, 
std::__cxx11::basic_string, std::allocator > 
const&)':
OpenGLES2Context.cpp:(.text+0x888): undefined reference to `glShaderSource'
../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o):
 In function 

[Touch-packages] [Bug 1817537] Re: libsoup should support ntlmv2

2019-07-09 Thread Sebastien Bacher
I've uploaded a backport for the NTLMv2 support to Bionic now

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

Title:
  libsoup should support ntlmv2

Status in libsoup2.4 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  Without NTLMv2 support evolution-ews can't connect to some exchange servers

  * Test case
  Try connecting from evolution-ews to an exchange server which enforces NTLMV2

  * Regression potential
  The change adds extra cases in the ntlm handling support, it should impact 
existing feature but check out for any potential regression in libsoup user 
(check at least evolution and epiphany-browser).
  Note that the patch include additional code tests

  ---

  Our Exchange admins recently made NTLMv2 obligatory. Since then
  interaction with Exchange through Evolution isn't possible anymore.

  In newer versions of libsoup that has been implemented, see
  https://gitlab.gnome.org/GNOME/evolution-ews/issues/38

  Could that be backported to Ubuntu 18.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsoup2.4-1 2.62.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb 25 12:10:26 2019
  SourcePackage: libsoup2.4
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1817537] Re: libsoup should support ntlmv2

2019-07-09 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ Without NTLMv2 support evolution-ews can't connect to some exchange servers
+ 
+ * Test case
+ Try connecting from evolution-ews to an exchange server which enforces NTLMV2
+ 
+ * Regression potential
+ The change adds extra cases in the ntlm handling support, it should impact 
existing feature but check out for any potential regression in libsoup user 
(check at least evolution and epiphany-browser).
+ Note that the patch include additional code tests
+ 
+ ---
+ 
  Our Exchange admins recently made NTLMv2 obligatory. Since then
  interaction with Exchange through Evolution isn't possible anymore.
  
  In newer versions of libsoup that has been implemented, see
  https://gitlab.gnome.org/GNOME/evolution-ews/issues/38
  
  Could that be backported to Ubuntu 18.04?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsoup2.4-1 2.62.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb 25 12:10:26 2019
  SourcePackage: libsoup2.4
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago)

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

Title:
  libsoup should support ntlmv2

Status in libsoup2.4 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  Without NTLMv2 support evolution-ews can't connect to some exchange servers

  * Test case
  Try connecting from evolution-ews to an exchange server which enforces NTLMV2

  * Regression potential
  The change adds extra cases in the ntlm handling support, it should impact 
existing feature but check out for any potential regression in libsoup user 
(check at least evolution and epiphany-browser).
  Note that the patch include additional code tests

  ---

  Our Exchange admins recently made NTLMv2 obligatory. Since then
  interaction with Exchange through Evolution isn't possible anymore.

  In newer versions of libsoup that has been implemented, see
  https://gitlab.gnome.org/GNOME/evolution-ews/issues/38

  Could that be backported to Ubuntu 18.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsoup2.4-1 2.62.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb 25 12:10:26 2019
  SourcePackage: libsoup2.4
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-07-09 Thread Jeremy Soller
I tested 240-6ubuntu5.2, it fixes the issue on Ubuntu 19.04

** Tags removed: verification-needed-disco
** Tags added: verification-done-disco

** Tags removed: verification-needed

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Autopkgtest regression report (systemd/240-6ubuntu5.2)

2019-07-09 Thread Łukasz Zemczak
All autopkgtests for the newly accepted systemd (240-6ubuntu5.2) for disco have 
finished running.
There have been regressions in tests triggered by the package. Please visit the 
sru report page and investigate the failures.

https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se

2019-07-09 Thread Sebastien Bacher
Thanks, I've sponsored the Bionic SRU now

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1556439/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2019-07-09 Thread Sebastien Bacher
Thanks for the new debdiff but I don't think it makes sense to do a
Cosmic SRU at this point since it's a deprecated serie

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1782263] Re: NetworkManager authentication problems caused by polkit

2019-07-09 Thread ALinuxUser
@Anton

Thanks. However, is that safe to do, i.e. it won't compromise security,
will it?

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

Title:
  NetworkManager authentication problems caused by polkit

Status in network-manager package in Ubuntu:
  New
Status in policykit package in Ubuntu:
  Confirmed

Bug description:
  The following message, or variations upon it, appears dozens of times,
  one immediately after the other, in my system log.

[1531853719.4893] error requesting auth for
  org.freedesktop.NetworkManager.settings.modify.hostname: Authorization
  check failed: Failed to open file “/proc/10006/status”: No such file
  or directory

  The problem began when I did the following package update.

  apt-cache policy policykit-1
  policykit-1:
Installed: 0.105-20
Candidate: 0.105-20ubuntu0.18.04.1
Version table:
   0.105-20ubuntu0.18.04.1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   *** 0.105-20 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  When (via the TimeShift backup program) I restored my system to a state 
before the package was installed, the problem stopped. When I did have the 
problem, some networks would have trouble connecting.

  I asked about the issue on Mint's IRC channel, and no solution - save
  reinstalling - emerged; but by that point I had not traced the problem
  to policykit.

  Mint 19 x64 Cinnamon. I report this problem here because it seems to
  me - I might be wrong - an Ubuntu rather than Mint problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782263/+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 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

2019-07-09 Thread Kai-Heng Feng
Can you find out how it was inverted for x, y and z?

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my hardware. 
Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sharper1380 F pulseaudio
   /dev/snd/controlC1:  sharper1380 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/12/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.44
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG4430MGN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: D1F44AV
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-07-09 Thread Jeremy Soller
Thanks, I will get it tested soon

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835711] Re: Ubuntu-bug collects bug data but does not upload it

2019-07-09 Thread fcole90
Is there any way to do it by CLI?

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

Title:
  Ubuntu-bug collects bug data but does not upload it

Status in apport package in Ubuntu:
  New

Bug description:
  I'm trying to report some bugs from a stable release, 18.04. I enabled
  apport reporting as suggested
  
here:https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash_in_the_stable_release
  and also here: https://www.linuxbabe.com/ubuntu/disable-apport-error-
  reporting-ubuntu-16-04-lts

  I also have whoopsie package installed.

  When I try to report a bug using `ubuntu-bug $package_name` it seem to
  be collecting data, but then it doesn't send them to launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1835711/+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 1835711] Re: Ubuntu-bug collects bug data but does not upload it

2019-07-09 Thread fcole90
I don't even have any option of this kind in my settings :/

** Attachment added: "Screenshot from 2019-07-09 16-11-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1835711/+attachment/5275879/+files/Screenshot%20from%202019-07-09%2016-11-29.png

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

Title:
  Ubuntu-bug collects bug data but does not upload it

Status in apport package in Ubuntu:
  New

Bug description:
  I'm trying to report some bugs from a stable release, 18.04. I enabled
  apport reporting as suggested
  
here:https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash_in_the_stable_release
  and also here: https://www.linuxbabe.com/ubuntu/disable-apport-error-
  reporting-ubuntu-16-04-lts

  I also have whoopsie package installed.

  When I try to report a bug using `ubuntu-bug $package_name` it seem to
  be collecting data, but then it doesn't send them to launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1835711/+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 1835911] Re: Handle applying status

2019-07-09 Thread Sebastien Bacher
The issue was fixed in Eoan with https://launchpad.net/ubuntu/+source
/software-properties/0.98.1

It doesn't make sense to SRU to Disco since livepatch is nor available
there

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Released

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

Title:
  Handle applying status

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  Sometime the livepatch status goes through an 'applying' intermediate value 
which can confuse the UI which then reports an non existing error

  * Test case
  Enable livepatch, go to software-properties->livepatch, check that the status 
matches the one reported by 'canonical-livepatch status' on a command line

  * Regression potential
  The change is simply adding an extra value to the list of handled status, 
check that the reporting is correct

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1835911/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window

2019-07-09 Thread fcole90
This is still a UX bug, as thomas303 said, ubuntu-bug should still
inform the user of what happened and why.

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1835910] Re: Include a control to display or not the livepatch indicator

2019-07-09 Thread Sebastien Bacher
The issue was fixed in Eoan with https://launchpad.net/ubuntu/+source
/software-properties/0.98.1

It doesn't make sense to SRU to Disco since livepatch is nor available
there

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Released

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

Title:
  Include a control to display or not the livepatch indicator

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  The livepatch UI design includes a control in software-properties which let 
you enable the indicator or not, that UI element is currently missing from 
bionic

  * Test case
  - start software-properties
  - go the livepatch tab and enable livepatch by adding an account
  -> the UI should include a toggle that let you activate/disactive the 
indicator
  - click on the control button
  -> the indicator status should reflect the control one

  * Regression potential
  The change is adding a new widget, it shouldn't impact on existing code but 
check that the page layout is still correct. The change also include 
translatable strings, they are being handled the same way as the other 
livepatch strings added in the previous upload (shared translations between 
serie included in langpack updates)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1835910/+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 1835911] [NEW] Handle applying status

2019-07-09 Thread Sebastien Bacher
Public bug reported:

* Impact
Sometime the livepatch status goes through an 'applying' intermediate value 
which can confuse the UI which then reports an non existing error

* Test case
Enable livepatch, go to software-properties->livepatch, check that the status 
matches the one reported by 'canonical-livepatch status' on a command line

* Regression potential
The change is simply adding an extra value to the list of handled status, check 
that the reporting is correct

** Affects: software-properties (Ubuntu)
 Importance: Low
 Status: Fix Released

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

Title:
  Handle applying status

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  Sometime the livepatch status goes through an 'applying' intermediate value 
which can confuse the UI which then reports an non existing error

  * Test case
  Enable livepatch, go to software-properties->livepatch, check that the status 
matches the one reported by 'canonical-livepatch status' on a command line

  * Regression potential
  The change is simply adding an extra value to the list of handled status, 
check that the reporting is correct

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1835911/+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 1835910] [NEW] Include a control to display or not the livepatch indicator

2019-07-09 Thread Sebastien Bacher
Public bug reported:

* Impact
The livepatch UI design includes a control in software-properties which let you 
enable the indicator or not, that UI element is currently missing from bionic

* Test case
- start software-properties
- go the livepatch tab and enable livepatch by adding an account
-> the UI should include a toggle that let you activate/disactive the indicator
- click on the control button
-> the indicator status should reflect the control one

* Regression potential
The change is adding a new widget, it shouldn't impact on existing code but 
check that the page layout is still correct. The change also include 
translatable strings, they are being handled the same way as the other 
livepatch strings added in the previous upload (shared translations between 
serie included in langpack updates)

** Affects: software-properties (Ubuntu)
 Importance: Wishlist
 Status: Fix Released

** Summary changed:

- Include control to display or not the indicator
+ Include a control to display or not the livepatch indicator

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

Title:
  Include a control to display or not the livepatch indicator

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  The livepatch UI design includes a control in software-properties which let 
you enable the indicator or not, that UI element is currently missing from 
bionic

  * Test case
  - start software-properties
  - go the livepatch tab and enable livepatch by adding an account
  -> the UI should include a toggle that let you activate/disactive the 
indicator
  - click on the control button
  -> the indicator status should reflect the control one

  * Regression potential
  The change is adding a new widget, it shouldn't impact on existing code but 
check that the page layout is still correct. The change also include 
translatable strings, they are being handled the same way as the other 
livepatch strings added in the previous upload (shared translations between 
serie included in langpack updates)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1835910/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-07-09 Thread Adam Conrad
Note that the fix is committed to git for eoan, but not uploaded as
systemd currently fails its testsuite on eoan.  This needs
investigation.

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-07-09 Thread Adam Conrad
Hello Jeremy, or anyone else affected,

Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-07-09 Thread Balint Reczey
** Description changed:

+ [Impact]
+ 
+  * Systems with AMD Ryzen 3000 series CPUs don't boot.
+ 
+ [Test Case]
+ 
+  * Boot with fixed systemd on an AMD Ryzen 3000 series system.
+ 
+ [Regression Potential]
+ 
+  * The fix itself is very small, it ignores known to be faulty random
+ values returned by the rdrand instruction and use a different random
+ source. Those values can still be returned by a properly working rdrand
+ implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64
+ cases on 64 bit arches, but the fallback to the other random source
+ ensures that in those rare occasions a random number can be generated.
+ 
+ [Original Bug Text]
+ 
  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not affect
  the older systemd version in 18.04, but affects the 19.04 version.
  
  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show
  
  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536
  
  This is a high severity issue, as I do not believe there is no potential
  workaround without either a firmware update or an ISO respin.
  
  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1782263] Re: NetworkManager authentication problems caused by polkit

2019-07-09 Thread Anton
To disable warning (and authentication) you can add:

[main]
auth-polkit=false

To the /etc/NetworkManager/NetworkManager.conf (if you already have
[main] section, just add value to it)

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

Title:
  NetworkManager authentication problems caused by polkit

Status in network-manager package in Ubuntu:
  New
Status in policykit package in Ubuntu:
  Confirmed

Bug description:
  The following message, or variations upon it, appears dozens of times,
  one immediately after the other, in my system log.

[1531853719.4893] error requesting auth for
  org.freedesktop.NetworkManager.settings.modify.hostname: Authorization
  check failed: Failed to open file “/proc/10006/status”: No such file
  or directory

  The problem began when I did the following package update.

  apt-cache policy policykit-1
  policykit-1:
Installed: 0.105-20
Candidate: 0.105-20ubuntu0.18.04.1
Version table:
   0.105-20ubuntu0.18.04.1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   *** 0.105-20 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  When (via the TimeShift backup program) I restored my system to a state 
before the package was installed, the problem stopped. When I did have the 
problem, some networks would have trouble connecting.

  I asked about the issue on Mint's IRC channel, and no solution - save
  reinstalling - emerged; but by that point I had not traced the problem
  to policykit.

  Mint 19 x64 Cinnamon. I report this problem here because it seems to
  me - I might be wrong - an Ubuntu rather than Mint problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782263/+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 1835809] Re: AMD Ryzen 3000 series fails to boot

2019-07-09 Thread Balint Reczey
** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Disco)
   Status: New => In Progress

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1511244] Re: Mouse pointer flickers at using DisplayLink

2019-07-09 Thread toabm
Hi! This bug is still happening with the latest DisplayLInk Driver for Ubuntu 
(5.2). The mouse flickers and moves around alone. It also dissapears on click. 
I am using a DELL 7300 laptop and a Asus MB16AC display. As soon as I connect 
the mponitor with the display link adapter uysing an USB a cable the mouse 
pointer starts to blink. 
It does no happen if I turn off the built in monitor, or if I connect the 
second monitor using the DP Alt mode, only with both monitors on and the 
DisplayLink usb adapter...:(

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a three screen setup, the built-in laptop screen, a monitor
  connected directly into the laptop via DisplayPort, and a monitor
  connected via a USB DisplayLink Adapter.

  What happens is that when a monitor is connected via the USB
  DisplayLink Adapter, the mouse icon flickers only on the laptop screen
  and monitor connected via DisplayPort (not on the monitor connected
  via USB DisplayLink Adapter).

  However, this is also reproducible if I either deactivate the built-in
  laptop screen, or disconnect the DisplayPort connected monitor.

  WORKAROUND: Disconnect the USB DisplayLink Adapter for the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511244/+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 1833527] Re: in gnome settings audio section does not see any sound card

2019-07-09 Thread Daniel van Vugt
Next time the problem happens, please check if you have a 'pulseaudio'
process running. If not then please follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

If you do however have a 'pulseaudio' process running (as yourself) and
still no audio then please run:

  apport-cli --hanging -P  PID

where PID is the process ID of the pulseaudio process. Then tell us the
new bug ID created.

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card

2019-07-09 Thread Mike
also before restart i need to run

pulseaudio -k
pulseaudio -D

and then restart computer

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card

2019-07-09 Thread Mike
Unfortunately it is a recurring bug, and yet again I have no sound
detected in gnome settings

@Daniel van Vugt

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

Title:
  in gnome settings audio section does not see any sound card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  in gnome settings audio section does not see any sound card. if i run
  alsamixer it can detect the sound card and all works fine. in gnome
  sound settings everything seems to be disabled.

  I have excatly same problem on PC where configuration is completely
  different than my laptops one.

  All the problems started recently, after upgrading to 19.04 some time
  later one of the updates destroyed all sound

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 12:28:49 2019
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GEX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GEX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se

2019-07-09 Thread Daniel van Vugt
** Also affects: pulseaudio (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Eoan)
   Importance: High
   Status: Fix Released

** Also affects: pulseaudio (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: pulseaudio (Ubuntu Disco)
   Importance: Undecided => High

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1556439/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-07-09 Thread Daniel van Vugt
** Also affects: pulseaudio (Ubuntu Eoan)
   Importance: High
   Status: Fix Released

** Also affects: pulseaudio (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: pulseaudio (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu Disco)
   Importance: Undecided => High

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Other Info]

  SRU sponsorship tracked in bug 1556439.

  [Original Report]

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1663528/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1825940] Re: [graphics] Enable ICL

2019-07-09 Thread quanxian
--- icl_commit_20190702.list_kernv_drm-tip  2019-07-02 13:55:00.666216695 
+0800
+++ icl_commit_20190709.list_kernv_drm-tip  2019-07-09 13:40:15.070144631 
+0800
@@ -1,13 +1,52 @@
+patches series of drm/i915: Random plane stuff,,,
+1/6 26443a4bc44 ADDED!,drm/i915: Add windowing for primary planes on gen2/3 
and chv,2019-07-03 23:08:19,next-20190708
+2/6 423ee8e99aa ADDED!,drm/i915: Disable sprite gamma on ivb-bdw,2019-07-03 
23:08:20,next-20190708
+3/6 94e15723df8 ADDED!,drm/i915: Program plane gamma ramps,2019-07-03 
23:08:21,next-20190708
+4/6 d56e823ac32 ADDED!,drm/i915: Deal with cpp==8 for g4x 
watermarks,2019-07-03 23:08:22,next-20190708
+5/6 94e35ce2217 ADDED!,drm/i915: Cosmetic fix for skl+ plane switch 
statement,2019-07-03 23:08:23,next-20190708
+6/6 3e69db291bd,drm/i915: Clean up skl vs. icl plane formats,2019-07-03 
23:08:24,next-20190708
+patches series of More mmio and intel_gt cleanups and refactorings,,,
+1/3 9b77011e412 ADDED!,drm/i915: Rework some interrupt handling functions to 
take intel_gt,2019-07-04 13:17:54,next-20190708
+2/3 f0818984fa5,drm/i915: Remove some legacy mmio accessors from interrupt 
handling,2019-07-04 13:17:55,next-20190708
+3/3 NOT-IN-UPSTREAM,drm/i915: Move dev_priv->pm_i{m,e}r into intel_gt,,
+56e9371bc3f,drm/i915: Deal with machines that expose less than three QGV 
points,2019-06-06 15:42:10,next-20190708
+8e9ecb3e1e3,drm/i915/display: Handle lost primary_port across 
suspend,2019-07-02 15:09:50,next-20190708
+patches series of drm/i915: CTS fixes,,,
+1/3 361b6905132 ADDED!,drm/i915: fix whitelist selftests with readonly 
registers,2019-06-29 14:13:50,next-20190703
+2/3 2c903da50f5 ADDED!,drm/i915: whitelist 
PS_(DEPTH|INVOCATION)_COUNT,2019-06-28 15:07:19,next-20190703
+3/3 3fe0107e45a,drm/i915/icl: whitelist PS_(DEPTH|INVOCATION)_COUNT,2019-06-28 
15:07:20,next-20190703
+4a8134d57c6,drm/i915/icl: Drop port parameter to 
icl_get_combo_buf_trans(),2019-06-25 17:03:48,next-20190703
+patches series of drm/i915: Fix TypeC port mode switching,,,
+01/23 39a5883f867,drm/i915/icl: Add support to read out the TBT PLL HW 
state,2019-06-28 17:36:13,next-20190703
+02/23 28212321622 ADDED!,drm/i915: Tune down WARNs about TBT AUX power well 
enabling,2019-06-28 17:36:14,next-20190703
+03/23 bc85328ff43,drm/i915: Move the TypeC port handling code to a separate 
file,2019-06-28 17:36:15,next-20190703
+04/23 e9b7e1422d4 ADDED!,drm/i915: Sanitize the terminology used for TypeC 
port modes,2019-06-28 17:36:16,next-20190703
+05/23 3b2ed431342 ADDED!,drm/i915: Don't enable the DDI-IO power in the TypeC 
TBT-alt mode,2019-06-28 17:36:17,next-20190703
+06/23 29ae36abf08 ADDED!,drm/i915: Fix the TBT AUX power well 
enabling,2019-06-28 17:36:18,next-20190703
+07/23 dd7239c545b ADDED!,drm/i915: Use the correct AUX power domain in TypeC 
TBT-alt mode,2019-06-28 17:36:19,next-20190703
+08/23 ab7bc4e1a55,drm/i915: Unify the TypeC port notation in debug/error 
messages,2019-06-28 17:36:20,next-20190703
+09/23 c905eb28bd3,drm/i915: Factor out common parts from TypeC port handling 
functions,2019-06-28 17:36:21,next-20190703
+10/23 ddec362724f ADDED!,drm/i915: Wait for TypeC PHY complete flag to clear 
in safe mode,2019-06-28 17:36:22,next-20190703
+11/23 424f109f5c5,drm/i915: Handle the TCCOLD power-down event,2019-06-28 
17:36:23,next-20190703
+12/23 1cd5ef6ee23 ADDED!,drm/i915: Sanitize the TypeC connect/detect 
sequences,2019-06-28 17:36:24,next-20190703
+13/23 32691b58d15 ADDED!,drm/i915: Fix the TypeC port mode sanitization during 
loading/resume,2019-06-28 17:36:25,next-20190703
+14/23 8c10e226266 ADDED!,drm/i915: Keep the TypeC port mode fixed for 
detect/AUX transfers,2019-06-28 17:36:26,next-20190703
+15/23 4f36afb26cb ADDED!,drm/i915: Sanitize the TypeC FIA lane configuration 
decoding,2019-06-28 17:36:27,next-20190703
+16/23 866955fa452 ADDED!,drm/i915: Sanitize the shared DPLL reserve/release 
interface,2019-06-28 17:36:28,next-20190703
+17/23 01b24f50b67 ADDED!,drm/i915: Sanitize the shared DPLL find/reference 
interface,2019-06-28 17:36:29,next-20190703
+18/23 726ca99666d,drm/i915/icl: Split getting the DPLLs to port type specific 
functions,2019-06-28 17:36:30,next-20190703
+19/23 eea72c4c216,drm/i915/icl: Reserve all required PLLs for TypeC 
ports,2019-06-28 17:36:31,next-20190703
+20/23 24a7bfe0c2d,drm/i915: Keep the TypeC port mode fixed when the port is 
active,2019-06-28 17:36:32,next-20190703
+21/23 d5ce34da314 ADDED!,drm/i915: Add state verification for the TypeC port 
mode,2019-06-28 17:36:33,next-20190703
+22/23 a171f8e7f46 ADDED!,drm/i915: Remove unneeded disconnect in TypeC legacy 
port mode,2019-06-28 17:36:34,next-20190703
+23/23 3ee2771e47b ADDED!,drm/i915: WARN about invalid lane reversal in 
TBT-alt/DP-alt modes,2019-06-28 17:36:35,next-20190703
+patches series of 9c811fce8a4,,,
+1/3 9c811fce8a4,drm/i915/icl: Add new supported CD clocks,2019-06-25 
18:40:51,next-20190628
+2/3 6e63790efdf,drm/i915/ehl: Remove unsupported cd clocks,2019-06-25