[Touch-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card

2019-09-07 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

-- 
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:
  Expired

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 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial

2019-09-07 Thread Linda
Yes, this fixed it for me, too, but I couldn't get it to work, just on
the explanation above.  Here's a little more detail.  Follow the
instructions at:

https://forums.linuxmint.com/viewtopic.php?t=295649#p1644426

Worked on Firefox Quantum 69.0 (64-bit) on Ubuntu 18.04.3 LTS bionic.

Now I can watch the Great Courses and other movies on Kanopy for free
through my local library account.  Yay!  Only 6 hours after my first
attempt, LOL.

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

Title:
  firefox plugin libwidevinecdm.so crashes due to apparmor denial

Status in apparmor package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04, Firefox 60.0.1+build2-0ubuntu0.18.04.1

  Running firefix, then going to netflix.com and attempting to play a
  movie.  The widevinecdm plugin crashes, the following is found in
  syslog:

  
  Jun 15 19:13:22 xplt kernel: [301351.553043] audit: type=1400 
audit(1529046802.585:246): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16118 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:22 xplt kernel: [301351.553236] audit: type=1400 
audit(1529046802.585:247): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:22 xplt kernel: [301351.553259] plugin-containe[16118]: segfault 
at 0 ip 7fcdfdaa76af sp 7ffc1ff03e28 error 6 in 
libxul.so[7fcdfb77a000+6111000]
  Jun 15 19:13:22 xplt snmpd[2334]: error on subcontainer 'ia_addr' insert (-1)
  Jun 15 19:13:22 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!! 
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
  Jun 15 19:13:24 xplt kernel: [301353.960182] audit: type=1400 
audit(1529046804.994:248): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16135 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:24 xplt kernel: [301353.960373] audit: type=1400 
audit(1529046804.994:249): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:24 xplt kernel: [301353.960398] plugin-containe[16135]: segfault 
at 0 ip 7fe3b57f46af sp 7ffe6dc0b488 error 6 in 
libxul.so[7fe3b34c7000+6111000]
  Jun 15 19:13:28 xplt kernel: [301357.859177] audit: type=1400 
audit(1529046808.895:250): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16139 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:28 xplt kernel: [301357.859328] audit: type=1400 
audit(1529046808.895:251): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:28 xplt kernel: [301357.859349] plugin-containe[16139]: segfault 
at 0 ip 7fcf32ae06af sp 7ffeb8a136c8 error 6 in 
libxul.so[7fcf307b3000+6111000]
  Jun 15 19:13:25 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!! 
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
  Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ERROR block_reap:328: 
[hamster] bad exit code 1
  Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!! 
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
  Jun 15 19:13:29 xplt kernel: [301358.227635] audit: type=1400 
audit(1529046809.263:252): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16188 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:29 xplt kernel: [301358.227811] audit: type=1400 
audit(1529046809.263:253): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:29 xplt kernel: [301358.227844] plugin-containe[16188]: segfault 
at 0 ip 7fe5667c66af sp 7fffe8cc0da8 error 6 in 
libxul.so[7fe564499000+6111000]
  Jun 15 

[Touch-packages] [Bug 1813112] Re: avahi-discover failed to display selected service details with UnicodeDecodeError

2019-09-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  avahi-discover failed to display selected service details with
  UnicodeDecodeError

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  ## Bug reproduce instruction
  (As this is a Unicode decode issue it might not be reproducible in all 
network environments)

  1. Launch avahi-discover
  2. Select certain service

  ## Expected behavior
  The service details properly rendered on the bottom pane

  ## Current behavior
  The service details remain "No service currently selected" with the following 
error traceback:

  ```
  Found service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 
2.0.
  Service data for service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 
'local' on 2.0:
  Host Buo-ren-TS453A.local (192.168.1.10), port 8080, TXT data: 
['accessType=http,accessPort=8080,model=TS-X53II,displayModel=TS-453A,fwVer=4.3.4,fwBuildNum=20180830,serialNum=Q169I13903,myCloudNASName=LinBuoRenNAS,myCloudNASDomain=myqnapcloud.com,webAdmPort=0,webAdmSslPort=0,webPort=0,webSslPort=0']
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in 
msg_reply_handler
  reply_handler(*message.get_args_list(**get_args_opts))
File "/usr/bin/avahi-discover", line 113, in service_resolved
  self.update_label(interface, protocol, name, stype, domain, host, 
aprotocol, address, port, avahi.txt_array_to_string_array(txt))
File "/usr/bin/avahi-discover", line 246, in update_label
  infos = infos % (stype, name, domain, self.siocgifname(interface), 
self.protoname(protocol), host, address, port, txts.strip())
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 6: 
ordinal not in range(128)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1813112/+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 1840965] Re: dhclient initramfs code writes invalid net-eth0.conf

2019-09-07 Thread Alkis Georgopoulos
** No longer affects: initramfs-tools (Ubuntu)

** No longer affects: initramfs-tools (Ubuntu Eoan)

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

Title:
  dhclient initramfs code writes invalid net-eth0.conf

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Eoan:
  Fix Released

Bug description:
  Since 18.10, Ubuntu switched to using dhclient instead of ipconfig in 
initramfs configure_networking(). And now a malformed /run/net-enp0s3.conf is 
generated, with unquoted values like the following, which are a shell syntax 
error:
  IPV4DNS0=1.2.3.1 1.2.3.2 1.2.3.3

  This file is sourced by initramfs-tools/init in various places, and produces 
the following message a lot of times:
  /init: /run/net-enp0s3.conf: line 8: 1.2.3.2: not found

  I.e. values should be quoted, and 2 DNS entries should go in
  IPV4DNS0/IPV4DNS1, not multiple unquoted ones in IPV4DNS0.

  Here is the erroneous file that dhclient-enter-hooks.d/config produces:
  DEVICE=enp0s3
  PROTO=dhcp
  IPV4PROTO=dhcp
  IPV4ADDR=10.161.254.38
  IPV4NETMASK=255.255.255.0
  IPV4BROADCAST=10.161.254.255
  IPV4GATEWAY=10.161.254.1
  IPV4DNS0=194.63.237.4 194.63.239.164 194.63.238.4
  ROOTSERVER=10.161.254.1
  HOSTNAME=
  DNSDOMAIN=

  Here is the correct one that ipconfig produces:
  DEVICE='enp0s3'
  PROTO='dhcp'
  IPV4ADDR='10.161.254.38'
  IPV4BROADCAST='10.161.254.255'
  IPV4NETMASK='255.255.255.0'
  IPV4GATEWAY='10.161.254.1'
  IPV4DNS0='194.63.237.4'
  IPV4DNS1='194.63.239.164'
  HOSTNAME=''
  DNSDOMAIN=''
  NISDOMAIN=''
  ROOTSERVER='10.161.254.1'
  ROOTPATH=''
  filename=''
  UPTIME='594'
  DHCPLEASETIME='25200'
  DOMAINSEARCH=''

  I.e. please either fix dhclient-enter-hooks.d/config, or revert the
  ipconfig => dhclient change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1840965/+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 1812466] Re: netboot: failed to parse DNS settings set by dhclient

2019-09-07 Thread Sandro
*** This bug is a duplicate of bug 1840965 ***
https://bugs.launchpad.net/bugs/1840965

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: dropbear (Ubuntu)
   Status: Confirmed => Fix Committed

** This bug has been marked a duplicate of bug 1840965
   dhclient initramfs code writes invalid net-eth0.conf

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

Title:
  netboot: failed to parse DNS settings set by dhclient

Status in dropbear package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  I am setting up diskless netboot for Ubuntu LiveCDs, with following
  kernel arguments:

  ```
  boot=casper netboot=nfs nfsroot=192.168.89.10:/extracted/livecd toram
  ```

  I have noticed the following strange error messages after dhcp (also
  see the attachment):

  ```
  /init: /run/net-ens3.conf: line 8: 202.38.64.56: not found
  /init: /run/net-ens3.conf: line 8: 202.38.64.56: not found
  /init: /run/net-ens3.conf: line 8: 202.38.64.56: not found
  no search or nameservers found in /run/net-ens3.conf /run/net-ens3.conf 
/run/net6-*.conf
  /init: /run/net-ens3.conf: line 8: 202.38.64.56: not found
  /init: /run/net-ens3.conf: line 8: 202.38.64.56: not found
  ```

  I manually broke the init process, and found line 8 of /run/net-
  ens3.conf is:

  ```
  IPV4DNS0=192.168.88.1 202.38.64.56 202.38.64.17
  ```

  The problematic code is in the `netinfo_to_resolv_conf` function of
  `scripts/functions`. It sources `/run/net-ens3.conf` (which is
  obviously not in correct shell syntax due to the space inserted
  between multiple DNS servers) to get network settings:

  ```
  . "$f" || { echo "WARN: failed '. \"$f\"'" 1>&2; return 1; }
  ```

  The bug is introduced by commit a77729e9, which replaced IP-config
  with dhclient. While IP-config seems to write each DNS in `IPV4DNS0`,
  `IPV4DNS1`, etc., dhclient write all DNS in `IPV4DNS0`, which is not
  expected by `netinfo_to_resolv_conf`.

  I can confirm 18.10 LiveCDs are affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1812466/+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 1840965] Re: dhclient initramfs code writes invalid net-eth0.conf

2019-09-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  dhclient initramfs code writes invalid net-eth0.conf

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Confirmed
Status in isc-dhcp source package in Eoan:
  Fix Released

Bug description:
  Since 18.10, Ubuntu switched to using dhclient instead of ipconfig in 
initramfs configure_networking(). And now a malformed /run/net-enp0s3.conf is 
generated, with unquoted values like the following, which are a shell syntax 
error:
  IPV4DNS0=1.2.3.1 1.2.3.2 1.2.3.3

  This file is sourced by initramfs-tools/init in various places, and produces 
the following message a lot of times:
  /init: /run/net-enp0s3.conf: line 8: 1.2.3.2: not found

  I.e. values should be quoted, and 2 DNS entries should go in
  IPV4DNS0/IPV4DNS1, not multiple unquoted ones in IPV4DNS0.

  Here is the erroneous file that dhclient-enter-hooks.d/config produces:
  DEVICE=enp0s3
  PROTO=dhcp
  IPV4PROTO=dhcp
  IPV4ADDR=10.161.254.38
  IPV4NETMASK=255.255.255.0
  IPV4BROADCAST=10.161.254.255
  IPV4GATEWAY=10.161.254.1
  IPV4DNS0=194.63.237.4 194.63.239.164 194.63.238.4
  ROOTSERVER=10.161.254.1
  HOSTNAME=
  DNSDOMAIN=

  Here is the correct one that ipconfig produces:
  DEVICE='enp0s3'
  PROTO='dhcp'
  IPV4ADDR='10.161.254.38'
  IPV4BROADCAST='10.161.254.255'
  IPV4NETMASK='255.255.255.0'
  IPV4GATEWAY='10.161.254.1'
  IPV4DNS0='194.63.237.4'
  IPV4DNS1='194.63.239.164'
  HOSTNAME=''
  DNSDOMAIN=''
  NISDOMAIN=''
  ROOTSERVER='10.161.254.1'
  ROOTPATH=''
  filename=''
  UPTIME='594'
  DHCPLEASETIME='25200'
  DOMAINSEARCH=''

  I.e. please either fix dhclient-enter-hooks.d/config, or revert the
  ipconfig => dhclient change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1840965/+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 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon

2019-09-07 Thread Khurshid Alam
** Changed in: indicator-session (Ubuntu)
 Assignee: (unassigned) => Khurshid Alam (khurshid-alam)

** Also affects: ubuntu-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Khurshid Alam (khurshid-alam)

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

Title:
  Port schemas from gnome-settings-daemon-common to com.canonical.unity
  .settings-daemon

Status in indicator-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Unity-settings-daemon still depends on gnome-settings-daemon schemas.
  It is undesired as it requires to modify code in all unity related
  components when upstream drops some gsettings schemas.

  gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an
  undesired way that it can't easily be reverted. Keyboard & mouse
  schemas are modified and unity-settings-daemon is crashing. So it's
  better unity uses it's own schema as suggested by Laney. We will of-
  course keep using settings migration (org.gnome.settings-daemon->
  org.gnome.desktop) wherever possible.

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768

  Since this is a huge task it can be achieved gradually.

  1) Ubuntu 19.10

  - Port media keys to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - u-s-d will still respects activation toggle in org.gnome.settings-
  daemon

  - everything else remains the same

  2) Ubuntu 20.04

  - Port rest of plugins to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - Activation toggle key will now use com.canonical.unity.settings-
  daemon

  - Everything else will remain the same

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+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 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

2019-09-07 Thread Jiri Kanicky
You can use the following workaround.

List devices which can wake up the notebook from sleep:

# cat /proc/acpi/wakeup | grep enable
PEG0 S4 *enabled pci::00:01.0
RP01 S4 *enabled pci::00:1c.0
RP05 S4 *enabled pci::00:1c.4
RP09 S4 *enabled pci::00:1d.0
RP17 S4 *enabled pci::00:1b.0
PXSX S4 *enabled pci::02:00.0
XHC S0 *enabled pci::00:14.0
LID0 S3 *enabled platform:PNP0C0D:00
PBTN S3 *enabled platform:PNP0C0C:00

Look for XHC device. You can match the device by running "lspci"

Disable wakeup
# echo XHC > /proc/acpi/wakeup

If I send the notebook to sleep "echo freeze > /sys/power/state" it
should stay in sleep even if you move BT mouse or hit key on BT
keyboard.

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

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session

2019-09-07 Thread Rachel Greenham
as of this morning's updates, this problem seems to have disappeared.
I've been able to log out and back in several times to my ubuntu wayland
session, at least on my i915 machine (the dell laptop).

nb: this morning's updates updated gnome-session-bin and ubuntu-session
to 3.33.92-1ubuntu1, gdm3 to 3.33.92-2ubuntu1, but mutter and gnome-
shell remain at 3.33.91.. (Also and probably not
coincidentally seeing some unrelated dash-or-ubuntudock issues, but i'll
wait to see if they're resolved when gnome-shell goes up to 3.33.92
too.)

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

Title:
  black screen, unresponsive, after logout from gnome Wayland session

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  on logout the screen is black, the system is unresponsive and has to
  be restarted. (Untested by me yet, but I expect ssh-ing in and
  restarting gdm would work.)

  I believe this may be already reported upstream here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've
  reported this against gdm3 even though I honestly don't know if it
  might be a gnome-shell, gnome-session or mutter based error. (FWIW
  without the upstream bug to link to I'd maybe suspect gnome-shell
  first.)

  NB: This machine's conf has AutomaticLogin enabled, but another
  machine also on 19.10 does not, and it's showing the same thing. On
  *this* machine I found that the *first* time I logged out, it was OK,
  but not the second time. On the other machine, it fails first time
  too. It's as if the gdm login screen can appear exactly once. That
  (and being on gnome 3.33) is why I don't think this is a dupe of
  #1824588.

  Nothing appears in /var/crash as a result of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 29 10:51:22 2019
  InstallationDate: Installed on 2018-09-11 (351 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641

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