date:20180731

Launchpad has imported 4 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=105779.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-03-28T07:24:17+00:00 Daniel van Vugt wrote:

Created attachment 138392
gnome-shell-all-mmaps-at-startup.pdf

80% (512MB) of gnome-shell's memory mappings at start-up are due to
PulseAudio. This seems excessive.

Memory profile from Google heap profiler attached.

Although this may not be a bug. It might just be reserved address space
with very little physical memory impact...?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/3


On 2018-03-28T07:36:07+00:00 Daniel van Vugt wrote:

Looks like maybe gnome-shell's use of libcanberra might be one of the
triggers.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/4


On 2018-03-28T16:07:45+00:00 Tanu Kaskinen wrote:

Each "mempool" in pulseaudio is 64 MB by default, and there's one
mempool per client. Maybe gnome-shell has multiple connections to
pulseaudio? 8 connections sounds excessive, though... Maybe the server's
own mempool is visible in the client memory mapping too, so perhaps two
mempools per connection are visible in the client memory map. 4
connections sounds still a bit much, though.

The mempools should indeed not have full "physical" impact unless
they're actually fully used.

What if you set "shm-size-bytes = 33554432" (i.e. 32 MB) in
/etc/pulse/client.conf and /etc/pulse/daemon.conf and reboot? Does the
gnome-shell memory usage go down by 256 MB?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/6


On 2018-07-30T09:41:07+00:00 Gitlab-migration wrote:

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/92.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1759497/comments/10


** Changed in: pulseaudio
   Status: Confirmed => Unknown

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

Title:
  80% (512MB) of gnome-shell's memory mappings at start up are due to
  PulseAudio

Status in PulseAudio:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libcanberra package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  80% (512MB) of gnome-shell's memory mappings at start-up are due to
  PulseAudio.

  This seems excessive.

  Memory profile from Google heap profiler attached.

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

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

[Touch-packages] [Bug 1743489] Missing required logs.

2018-07-31 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1743489

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  iwlwifi firmware panic on 4.13, ucode 29.610311.0

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  On random occasion, or with certain wifi loads, iwlwifi panics with
  the wifi nolonger being wakeable;

  [   14.548729] iwlwifi :05:00.0: loaded firmware version 29.610311.0 
op_mode iwlmvm
  [   14.611562] iwlwifi :05:00.0: Detected Intel(R) Dual Band Wireless AC 
3165, REV=0x210
  [   14.631936] iwlwifi :05:00.0: base HW address: 08:d4:0c:ef:9b:4c
  [   15.094132] iwlwifi :05:00.0 wlo1: renamed from wlan0
  [  436.462157] WARNING: CPU: 3 PID: 0 at 
/build/linux-4LIBhY/linux-4.13.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1873
 iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi]
  [  436.462159] Modules linked in: ccm rfcomm cmac bnep binfmt_misc 
nls_iso8859_1 amd_freq_sensitivity edac_mce_amd kvm_amd kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek 
aesni_intel snd_hda_codec_generic arc4 snd_hda_codec_hdmi aes_x86_64 
crypto_simd glue_helper snd_hda_intel cryptd uvcvideo snd_hda_codec 
videobuf2_vmalloc videobuf2_memops snd_hda_core snd_seq_midi videobuf2_v4l2 
snd_hwdep videobuf2_core snd_seq_midi_event joydev snd_rawmidi videodev iwlmvm 
input_leds hp_wmi sparse_keymap media wmi_bmof mac80211 snd_pcm btusb serio_raw 
btrtl snd_seq btbcm btintel k10temp fam15h_power bluetooth snd_seq_device 
snd_timer i2c_piix4 iwlwifi ecdh_generic cfg80211 snd soundcore shpchp i2c_scmi 
mac_hid hp_wireless parport_pc ppdev lp parport ip_tables x_tables autofs4
  [  436.462351] RIP: 0010:iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi]
  [  436.462417]  iwl_read_prph+0x32/0x80 [iwlwifi]
  [  436.462444]  iwl_trans_pcie_log_scd_error+0x120/0x1e0 [iwlwifi]
  [  436.462477]  ? iwl_pcie_txq_inc_wr_ptr+0xf0/0xf0 [iwlwifi]
  [  436.462499]  iwl_pcie_txq_stuck_timer+0x4b/0x70 [iwlwifi]
  [  436.516736] iwlwifi :05:00.0: Queue 10 is active on fifo 2 and stuck 
for 1 ms. SW [22, 107] HW [90, 90] FH TRB=0x05a5a5a5a
  [  440.022480] iwlwifi :05:00.0: Failed to wake NIC for hcmd
  [  440.022600] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  440.022607] iwlwifi :05:00.0: Scan failed! ret -5
  [  441.041965] iwlwifi :05:00.0: Failed to wake NIC for hcmd
  [  441.042121] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  441.042128] iwlwifi :05:00.0: Scan failed! ret -5
  [  442.061856] iwlwifi :05:00.0: Failed to wake NIC for hcmd
  ...recurring

  Kubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jan 16 14:14:26 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-05 (375 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto static metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.80 metric 600 
   192.168.30.0/24 dev vpn_vectrobe proto kernel scope link src 192.168.30.11
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2018-01-15 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1784768] [NEW] Setup fails with OSError: [Errno 22] Invalid argument (full /var/log available)

2018-07-31 Thread VF

Public bug reported:

Tried to install Ubuntu 18.04.1 amd64 from USB stick.

Chose manual partitioning of 4 physical disks.

After partitioning I started to enter my name and the hostname. During
that setup suddenly failed with an exception:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 201, in 
main
ret = args.func(args)
  File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 58, 
in block_meta
meta_custom(args)
  File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
1471, in meta_custom
clear_holders.clear_holders(disk_paths)
  File "/usr/lib/python3/dist-packages/curtin/block/clear_holders.py", line 
587, in clear_holders
shutdown_function(dev_info['device'])
  File "/usr/lib/python3/dist-packages/curtin/block/clear_holders.py", line 
310, in wipe_superblock
if is_swap_device(blockdev):
  File "/usr/lib/python3/dist-packages/curtin/swap.py", line 108, in 
is_swap_device
decode=False)
  File "/usr/lib/python3/dist-packages/curtin/util.py", line 549, in load_file
fp.seek(offset)
OSError: [Errno 22] Invalid argument

This happened three times in a row.

I tried to have a 2GB /boot partition, then creating vg0 on two physical
partitions with a logical partition for /root. Also tried to add a swap,
but it did not make a difference.

Machine is stable, has 32GB of memory.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: console disk exception install manual partition partitioning server 
setup

** Attachment added: "Contents of the entire /var/log folder"
   
https://bugs.launchpad.net/bugs/1784768/+attachment/5170189/+files/var-log.tar.gz

** Description changed:

  Tried to install Ubuntu 18.04.1 amd64 from USB stick.
  
  Chose manual partitioning of 4 physical disks.
  
  After partitioning I started to enter my name and the hostname. During
  that setup suddenly failed with an exception:
  
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 201, in 
main
- ret = args.func(args)
-   File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
58, in block_meta
- meta_custom(args)
-   File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
1471, in meta_custom
- clear_holders.clear_holders(disk_paths)
-   File "/usr/lib/python3/dist-packages/curtin/block/clear_holders.py", line 
587, in clear_holders
- shutdown_function(dev_info['device'])
-   File "/usr/lib/python3/dist-packages/curtin/block/clear_holders.py", line 
310, in wipe_superblock
- if is_swap_device(blockdev):
-   File "/usr/lib/python3/dist-packages/curtin/swap.py", line 108, in 
is_swap_device
- decode=False)
-   File "/usr/lib/python3/dist-packages/curtin/util.py", line 549, in load_file
- fp.seek(offset)
+   File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 201, in 
main
+ ret = args.func(args)
+   File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
58, in block_meta
+ meta_custom(args)
+   File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
1471, in meta_custom
+ clear_holders.clear_holders(disk_paths)
+   File "/usr/lib/python3/dist-packages/curtin/block/clear_holders.py", line 
587, in clear_holders
+ shutdown_function(dev_info['device'])
+   File "/usr/lib/python3/dist-packages/curtin/block/clear_holders.py", line 
310, in wipe_superblock
+ if is_swap_device(blockdev):
+   File "/usr/lib/python3/dist-packages/curtin/swap.py", line 108, in 
is_swap_device
+ decode=False)
+   File "/usr/lib/python3/dist-packages/curtin/util.py", line 549, in load_file
+ fp.seek(offset)
  OSError: [Errno 22] Invalid argument
+ 
+ This happened three times in a row.
+ 
+ I tried to have a 2GB /boot partition, then creating vg0 on two physical
+ partitions with a logical partition for /root. Also tried to add a swap,
+ but it did not make a difference.
+ 
+ Machine is stable, has 32GB of memory.

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

Title:
  Setup fails with OSError: [Errno 22] Invalid argument (full /var/log
  available)

Status in console-setup package in Ubuntu:
  New

Bug description:
  Tried to install Ubuntu 18.04.1 amd64 from USB stick.

  Chose manual partitioning of 4 physical disks.

  After partitioning I started to enter my name and the hostname. During
  that setup suddenly failed with an exception:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 201, in 
main
  ret = args.func(args)
    File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
58, in block_meta
  meta_custom(args)
    File

[Touch-packages] [Bug 1743489] Re: iwlwifi firmware panic on 4.13, ucode 29.610311.0

2018-07-31 Thread Kai-Heng Feng

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

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

Title:
  iwlwifi firmware panic on 4.13, ucode 29.610311.0

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

Bug description:
  On random occasion, or with certain wifi loads, iwlwifi panics with
  the wifi nolonger being wakeable;

  [   14.548729] iwlwifi :05:00.0: loaded firmware version 29.610311.0 
op_mode iwlmvm
  [   14.611562] iwlwifi :05:00.0: Detected Intel(R) Dual Band Wireless AC 
3165, REV=0x210
  [   14.631936] iwlwifi :05:00.0: base HW address: 08:d4:0c:ef:9b:4c
  [   15.094132] iwlwifi :05:00.0 wlo1: renamed from wlan0
  [  436.462157] WARNING: CPU: 3 PID: 0 at 
/build/linux-4LIBhY/linux-4.13.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1873
 iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi]
  [  436.462159] Modules linked in: ccm rfcomm cmac bnep binfmt_misc 
nls_iso8859_1 amd_freq_sensitivity edac_mce_amd kvm_amd kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek 
aesni_intel snd_hda_codec_generic arc4 snd_hda_codec_hdmi aes_x86_64 
crypto_simd glue_helper snd_hda_intel cryptd uvcvideo snd_hda_codec 
videobuf2_vmalloc videobuf2_memops snd_hda_core snd_seq_midi videobuf2_v4l2 
snd_hwdep videobuf2_core snd_seq_midi_event joydev snd_rawmidi videodev iwlmvm 
input_leds hp_wmi sparse_keymap media wmi_bmof mac80211 snd_pcm btusb serio_raw 
btrtl snd_seq btbcm btintel k10temp fam15h_power bluetooth snd_seq_device 
snd_timer i2c_piix4 iwlwifi ecdh_generic cfg80211 snd soundcore shpchp i2c_scmi 
mac_hid hp_wireless parport_pc ppdev lp parport ip_tables x_tables autofs4
  [  436.462351] RIP: 0010:iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi]
  [  436.462417]  iwl_read_prph+0x32/0x80 [iwlwifi]
  [  436.462444]  iwl_trans_pcie_log_scd_error+0x120/0x1e0 [iwlwifi]
  [  436.462477]  ? iwl_pcie_txq_inc_wr_ptr+0xf0/0xf0 [iwlwifi]
  [  436.462499]  iwl_pcie_txq_stuck_timer+0x4b/0x70 [iwlwifi]
  [  436.516736] iwlwifi :05:00.0: Queue 10 is active on fifo 2 and stuck 
for 1 ms. SW [22, 107] HW [90, 90] FH TRB=0x05a5a5a5a
  [  440.022480] iwlwifi :05:00.0: Failed to wake NIC for hcmd
  [  440.022600] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  440.022607] iwlwifi :05:00.0: Scan failed! ret -5
  [  441.041965] iwlwifi :05:00.0: Failed to wake NIC for hcmd
  [  441.042121] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  441.042128] iwlwifi :05:00.0: Scan failed! ret -5
  [  442.061856] iwlwifi :05:00.0: Failed to wake NIC for hcmd
  ...recurring

  Kubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jan 16 14:14:26 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-05 (375 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto static metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.80 metric 600 
   192.168.30.0/24 dev vpn_vectrobe proto kernel scope link src 192.168.30.11
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2018-01-15 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-07-31 Thread Trent Lloyd

Hoping to get attention to this again. Since 18.04.1 is out now, more
and more users are likely to hit this issue as more users will be
upgrading. This issue applies equally to desktop and server scenarios.

I would like to get lp1752411-avahi-host-timeout.diff sponsored for
upload please

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Confirmed
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in avahi package in Debian:
  New

Bug description:
  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

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

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

[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

** Changed in: pulseaudio
   Status: Confirmed => Unknown

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1583801]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193.

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

2018-07-31 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1697120

** Tags added: iso-testing

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

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt-file is now difficult to use with about a dozen warnings like this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

  [Test case]
  Install apt-file and update, make sure that the warnings are gone.

  [Regression potential]
  Warnings about duplicate index targets containing "legacy" in their 
configured name are not shown anymore, thus it's harder to "fix" servers. But 
apart from that, which was the goal, I don't see any.

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

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

[Touch-packages] [Bug 1784760] [NEW] package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-07-31 Thread Kamden Rampley

Public bug reported:

Im not sure what this bug report is.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1090 F pulseaudio
  kamden 1945 F pulseaudio
 /dev/snd/controlC1:  gdm1090 F pulseaudio
  kamden 1945 F pulseaudio
Date: Sun Jul 22 13:14:59 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2018-07-19 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP ProBook 4520s
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=3d2b2963-aa15-45ee-ba3e-bc9fbf3e595b ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.1
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68AZZ Ver. F.21
dmi.board.name: 1411
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 57.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.21:bd06/13/2012:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP ProBook 4520s
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Im not sure what this bug report is.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1090 F pulseaudio
kamden 1945 F pulseaudio
   /dev/snd/controlC1:  gdm1090 F pulseaudio
kamden 1945 F pulseaudio
  Date: Sun Jul 22 13:14:59 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-07-19 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP ProBook 4520s
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=3d2b2963-aa15-45ee-ba3e-bc9fbf3e595b ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.21
  dmi.board.name: 1411
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.21:bd06/13/2012:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4520s
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1784760/+subscriptions

-- 
Mailing list:

[Touch-packages] [Bug 1784760] Re: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-07-31 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Im not sure what this bug report is.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1090 F pulseaudio
kamden 1945 F pulseaudio
   /dev/snd/controlC1:  gdm1090 F pulseaudio
kamden 1945 F pulseaudio
  Date: Sun Jul 22 13:14:59 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-07-19 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP ProBook 4520s
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=3d2b2963-aa15-45ee-ba3e-bc9fbf3e595b ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.21
  dmi.board.name: 1411
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.21:bd06/13/2012:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4520s
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1784760/+subscriptions

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

Chris Guiver, you may need to use:
sudo ubuntu-bug /var/crash/FILENAME.crash

when filing crash reports in order for the upload/uploaded files to be
generated, and, in turn, to get the errors reported successfully.

Given the reproducibility of the crash, and how you are using the latest
Ubuntu release, I'll mark this Triaged for now, and an xorg developer
may further review.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined")

[Touch-packages] [Bug 1784595] Re: takes forever to boot

2018-07-31 Thread Daniel van Vugt

** Package changed: xorg (Ubuntu) => ubuntu

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

Title:
  takes forever to boot

Status in Ubuntu:
  New

Bug description:
  I apologise I really have no idea, this report was generated automatically.
  I resized some partitions and merged some partitions.
  I then went through a "Grub Rescue>" to get up and running again.
  the system now takes about 3 minutes to get to the login screen. 
  I updated and installed grub as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 31 19:34:12 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb01]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Toshiba America Info Systems GF108M [GeForce GT 630M] 
[1179:fb01]
  InstallationDate: Installed on 2018-07-13 (17 days ago)
  InstallationMedia: Robolinux_9.3 16.04 - Release amd64
  MachineType: TOSHIBA Satellite P850
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=fd6d67e8-fc11-4624-b9a6-3cd136a622e4 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 6.70
  dmi.board.asset.tag: *
  dmi.board.name: QFKAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr6.70:bd02/20/2013:svnTOSHIBA:pnSatelliteP850:pvrPSPKFA-049001:rvnTOSHIBA:rnQFKAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name: Satellite P850
  dmi.product.version: PSPKFA-049001
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Aug  1 05:03:53 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1390474]

(In reply to Tanu Kaskinen from comment #39)
> The log shows that you're not using module-udev-detect. I don't know if
> that's why things stopped working, but that would anyway be the first thing
> to fix. Debian changed the packaging so that "pulseaudio-module-udev" is now
> a separate package. You have probably disabled automatic installation of
> recommended packages, because by default that package should get installed
> automatically.

Thanks a lot! My system really didn't install module-udev-detect
(package pulseaudio-module-udev in debian stretch/testing). Now it works
again!

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

** Description changed:

  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end
  
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)
  
  I sleep my XFCE (xubuntu) machine rather than turning it off at night.
  
  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank screen
  with a RADEON two-line text message top left on screen which appear only
  momentarily as screen is erased and I get the login/greeter screen.
  
  (it's happened 4-5 times, but does NOT happen every time)
  
  I can login fine, but my xfce session is new.
  
  I have grep'd for the message I see (yesterday & today), but can't find
  it as i usually recall little but the radeon word...
  
  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d
  
  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)
  
  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   67 May 22 09:36:29 d960-ubu2 systemd-logind[1108]: Removed session 166.
   68 May 22 09:37:39 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session opened for user guiverc by (uid=0)
   69 May 22 09:37:39 d960-ubu2 systemd-logind[1108]: New session 178 of user 
guiverc.
   70 May 22 09:38:11 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out

[Touch-packages] [Bug 1251127] Re: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] Pulseaudio fails to detect card

** Changed in: pulseaudio
   Status: Confirmed => Unknown

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

Title:
  [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear]
  Pulseaudio fails to detect card

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  apt-cache policy pkgname:
  pulseaudio:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
   *** 1:4.0-0ubuntu6 0
  500 http://ftp.nluug.nl/os/Linux/distr/ubuntu/ trusty/main i386 
Packages
  500 http://ftp.tudelft.nl/archive.ubuntu.com/ saucy/main i386 Packages
  100 /var/lib/dpkg/status
   1:3.0-0ubuntu6 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic i686
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cschilder   2392 F mixer_applet2
  Date: Thu Nov 14 07:35:59 2013
  InstallationDate: Installed on 2013-11-01 (12 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Title: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (12 days ago)
  dmi.bios.date: 01/23/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.10
  dmi.board.asset.tag: CZC3211FPH
  dmi.board.name: 2ADE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: CZC3211FPH
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.10:bd01/23/2013:svnHewlett-Packard:pnHPCompaqPro4300SFFPC:pvr:rvnHewlett-Packard:rn2ADE:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Pro 4300 SFF PC
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

** Changed in: pulseaudio
   Status: Confirmed => Unknown

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Touch-packages] [Bug 1251127]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/426.

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

Title:
  [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear]
  Pulseaudio fails to detect card

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  apt-cache policy pkgname:
  pulseaudio:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
   *** 1:4.0-0ubuntu6 0
  500 http://ftp.nluug.nl/os/Linux/distr/ubuntu/ trusty/main i386 
Packages
  500 http://ftp.tudelft.nl/archive.ubuntu.com/ saucy/main i386 Packages
  100 /var/lib/dpkg/status
   1:3.0-0ubuntu6 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic i686
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cschilder   2392 F mixer_applet2
  Date: Thu Nov 14 07:35:59 2013
  InstallationDate: Installed on 2013-11-01 (12 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Title: [HP Compaq Pro 4300 SFF PC, Realtek ID 221, Green Line Out, Rear] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (12 days ago)
  dmi.bios.date: 01/23/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.10
  dmi.board.asset.tag: CZC3211FPH
  dmi.board.name: 2ADE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: CZC3211FPH
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.10:bd01/23/2013:svnHewlett-Packard:pnHPCompaqPro4300SFFPC:pvr:rvnHewlett-Packard:rn2ADE:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Compaq Pro 4300 SFF PC
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1390474] Re: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels

** Changed in: pulseaudio
   Status: Fix Released => Unknown

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1390474]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/457.

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

fyi: looking at the wiki,
/etc/gdm3/custom.conf now has Enable=true  (it was commented out sorry)

"Reporting a crash in the stable release" may not apply, but I couldn't
find a problem_types  (only mentioned this as I noted you were last wiki
editor; thank you!)

Thank you for link - appreciated.  I still get nothing since 11-july on
https://errors.ubuntu.com/user/ceaac5c412433432f0beca83292fc33804be2fdae3b13b7fc7185e6a52d5fd6941294dff354c0cc3a5000fce6202e51c04e867a10ca60bb60b3682028253f96e

(I checked the ID; and copied it twice into browser from `sudo cat
/var/lib/whoopsie/whoopsie-id` getting same result)

Thanks Christopher - I do appreciate your help (hopefully I'm learning
slowly!)

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May

[Touch-packages] [Bug 1390474]

http://pastebin.com/CzQQhvET

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1390474]

2018-07-31 Thread Raymond

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/pci/rme9652/hdsp.c

static struct snd_pcm_hardware snd_hdsp_capture_subinfo =
{
.info = (SNDRV_PCM_INFO_MMAP |
 SNDRV_PCM_INFO_MMAP_VALID |
 SNDRV_PCM_INFO_NONINTERLEAVED |
 SNDRV_PCM_INFO_SYNC_START),
#ifdef SNDRV_BIG_ENDIAN
.formats =  SNDRV_PCM_FMTBIT_S32_BE,
#else
.formats =  SNDRV_PCM_FMTBIT_S32_LE,
#endif
.rates =(SNDRV_PCM_RATE_32000 |
 SNDRV_PCM_RATE_44100 |
 SNDRV_PCM_RATE_48000 |
 SNDRV_PCM_RATE_64000 |
 SNDRV_PCM_RATE_88200 |
 SNDRV_PCM_RATE_96000),
.rate_min = 32000,
.rate_max = 96000,
.channels_min = 5,
.channels_max = HDSP_MAX_CHANNELS,
.buffer_bytes_max = HDSP_CHANNEL_BUFFER_BYTES * HDSP_MAX_CHANNELS,
.period_bytes_min = (64 * 4) * 10,
.period_bytes_max = (8192 * 4) * HDSP_MAX_CHANNELS,
.periods_min =  2,
.periods_max =  2,
.fifo_size =0
};


only support 2 periods and non-interleaved access mode

pulseaudio cannot use 4 fragments

this mean one period of channel 1 , follow by one period of channel 2
,..., one period of channel n

seem has flag to control the precision of hw pointer


static snd_pcm_uframes_t hdsp_hw_pointer(struct hdsp *hdsp)
{
int position;

position = hdsp_read(hdsp, HDSP_statusRegister);

if (!hdsp->precise_ptr)
return (position & HDSP_BufferID) ? (hdsp->period_bytes / 4) : 
0;

position &= HDSP_BufferPositionMask;
position /= 4;
position &= (hdsp->period_bytes/2) - 1;
return position;
}

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1390474]

Created attachment 125150
attachment-5407-0.html

Meaning what exactly?

It worked with previous versions. And even if it doesn't work - what is
the recommended step here? Remove pulseaudio?

Thanks & best regards
Benjamin

Am 19. Juli 2016 16:09:10 MESZ, schrieb bugzilla-dae...@freedesktop.org:
>https://bugs.freedesktop.org/show_bug.cgi?id=84804
>
>--- Comment #37 from Raymond  ---
>https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=55a25246ee80aa950bf27f811c0cc176d0821a4e
>
>
>pulseaudio does not support non-interlaved mode
>
>
>static void check_access(snd_pcm_t *pcm_handle, snd_pcm_hw_params_t
>*hwparams,
>bool use_mmap) {
>  if ((use_mmap && !snd_pcm_hw_params_test_access(pcm_handle, hwparams,
>SND_PCM_ACCESS_MMAP_INTERLEAVED)) ||
>!snd_pcm_hw_params_test_access(pcm_handle, hwparams,
>SND_PCM_ACCESS_RW_INTERLEAVED))
> pa_log_error("Weird, PCM claims to support interleaved access, but
>snd_pcm_hw_params_set_access() failed.");
>+
>
>-- 
>You are receiving this mail because:
>You reported the bug.

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1390474]

The log shows that you're not using module-udev-detect. I don't know if
that's why things stopped working, but that would anyway be the first
thing to fix. Debian changed the packaging so that "pulseaudio-module-
udev" is now a separate package. You have probably disabled automatic
installation of recommended packages, because by default that package
should get installed automatically.

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1438510]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/525.

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Touch-packages] [Bug 1390474]

2018-07-31 Thread Raymond

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=55a25246ee80aa950bf27f811c0cc176d0821a4e


pulseaudio does not support non-interlaved mode


static void check_access(snd_pcm_t *pcm_handle, snd_pcm_hw_params_t *hwparams, 
bool use_mmap) {
if ((use_mmap && !snd_pcm_hw_params_test_access(pcm_handle, hwparams, 
SND_PCM_ACCESS_MMAP_INTERLEAVED)) ||
!snd_pcm_hw_params_test_access(pcm_handle, hwparams, 
SND_PCM_ACCESS_RW_INTERLEAVED))
pa_log_error("Weird, PCM claims to support interleaved access, but 
snd_pcm_hw_params_set_access() failed.");
+

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1390474]

Hi,

I'm not sure if this is 100% the same issue, but my problems started
again when Debian upgraded from pulseaudio 8 to 9 recently.

Even though I still use tsched=0, I hear huge amounts of clicks and pops
while playing back (everything sounds like a very old vinyl recording
now...). Enabling tsched makes no difference, in fact I think that it is
still of even though I tried tsched=1.

I'll attach the verbose log.

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

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

guiverc@d960-ubu2:/var/crash$   ls -la
total 64408
drwxrwsrwt  3 rootwhoopsie 4096 Aug  1 08:32 .
drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
drwxrwsr-x  2 guiverc whoopsie 4096 Jul 30 09:19 2018-05-22
-rw-r-  1 guiverc whoopsie70917 Jul 30 08:28 
_usr_bin_caffeine.1000.crash
-rw-r-  1 guiverc whoopsie 44980186 Jul 30 08:29 _usr_bin_vlc.1000.crash
-rw-r-  1 guiverc whoopsie 20876029 Aug  1 08:28 
_usr_lib_xorg_Xorg.1000.crash

these .crash files have been filed (now twice) with `ubuntu-bug
_usr_bin_caffeine.1000.crash` using my username (guiverc), no paths as I
navigated to the directory first. A "Sorry, Ubuntu 18.10 has experienced
an internal error" box appears each time, I just hit continue, and I get
returned to shell.

guiverc@d960-ubu2:/var/crash$   ubuntu-bug _usr_lib_xorg_Xorg.1000.crash 
Gtk-Message: 09:55:58.212: Failed to load module "appmenu-gtk-module"
Gtk-Message: 09:55:58.212: Failed to load module "appmenu-gtk-module"
Gtk-Message: 09:55:58.213: Failed to load module "appmenu-gtk-module"
guiverc@d960-ubu2:/var/crash$ 

None have the .upload* in directory; and the 2018-07-30 Xorg crash file
was overwritten by today's crash.

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

** Attachment added: "syslog.2018-08.01"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5170143/+files/syslog.2018-08.01

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   66 May 22

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

Chris Guiver:

1) While the issue is being root caused, please keep light-locker, and
caffeine uninstalled.

2) Regarding the file:
-rw-r- 1 guiverc whoopsie 20M Aug 1 08:28 _usr_lib_xorg_Xorg.1000.crash

No error reports have been reported to errors since 2018-07-11. One may
further confirm is if in the folder /var/crash there are files .upload
and .uploaded found along with the same .crash file (or a bug report is
created on Launchpad). Clicking on the crash GUI doesn't indicate if a
crash was successfully reported. For more on this, please see
https://help.ubuntu.com/community/ReportingBugs .

Hence, could you please report the crash, and advise to the additional
files in /var/crash?

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

** Attachment added: "journalctl-a.2018-08-01.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5170140/+files/journalctl-a.2018-08-01.txt

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

today's crash
-rw-r- 1 guiverc whoopsie  20M Aug  1 08:28 _usr_lib_xorg_Xorg.1000.crash
// this has was reported (ubuntu-bug)

no caffeine or light-locker are installed

on screen I had 4 'repeats' but was able to look closer and not it's not
a message repeated, but it's part of `dmesg` log, which contained today
the following

[116686.756961] radeon :01:00.0: couldn't schedule ib
[116686.756995] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)!

[118941.608308] radeon :01:00.0: couldn't schedule ib
[118941.608344] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)!
[118941.608308] radeon :01:00.0: couldn't schedule ib
[118941.608344] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)!
[171718.127155] radeon :01:00.0: couldn't schedule ib
[171718.127190] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)!
[218598.613273] radeon :01:00.0: couldn't schedule ib
[218598.613308] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)!

NOTE: I didn't write down the numbers but counted four 'repeats' only so
one of my copy/pastes (from dmesg) wasn't there (I'm assuming the
top/first one).  The left 'dmesg' time part is what I missed yesterday.
The message appears near top left (maybe a few lines down) on both
screens, stays there awhile then screen blanks and I'm back at login
greeter (my xfce session gone)


** Attachment added: "dmesg.2018-08-01"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5170138/+files/dmesg.2018-08-01

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item

[Touch-packages] [Bug 1782802] Re: ditch ipconfig in favor of dhclient -4 in 18.10

2018-07-31 Thread Michael Hudson-Doyle

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)

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

Title:
  ditch ipconfig in favor of dhclient -4 in 18.10

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  When adding ipv6 netboot support to initramfs-tools in yakkety/zesty,
  this was initially attempted with replacing ipconfig with dhclient.
  As described in LP: #1621507, the use of dhclient for ipv4 dhcp was
  backed out in favor of ipconfig.  So at the moment, we are using both
  ipconfig from klibc-utils and dhclient from isc-dhcp-client in the
  initramfs.

  We want to switch off of klibc-utils completely and use isc-dhcp-
  client for both ipv4 and ipv6 in initramfs-tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782802/+subscriptions

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

[Touch-packages] [Bug 1202754] Re: update-manager crashed with SystemExit in exit(): 0

2018-07-31 Thread Walter

** Changed in: click-update-manager (Ubuntu)
 Assignee: faiz (starone-faiz) => Walter (s-walter)

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

Title:
  update-manager crashed with SystemExit in exit(): 0

Status in Ubuntu Kylin:
  Fix Released
Status in Software Updater:
  New
Status in click-update-manager package in Ubuntu:
  Fix Released

Bug description:
  Errors bucket
  
https://errors.ubuntu.com/bucket/?id=/usr/bin/update-manager:SystemExit:commit:_inline_callbacks:_show_transaction:_inline_callbacks:commit:_action_done:exit

  I was going to check for updates, but the Update-Manager has closed
  itself.

  ProblemType: CrashDistroRelease: Ubuntu 13.10
  Package: update-manager 1:0.189
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: i386
  Date: Thu Jul 18 20:46:05 2013
  ExecutablePath: /usr/bin/update-manager
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  PythonArgs: ['/usr/bin/update-manager', '--no-update', 
'--no-focus-on-map']SourcePackage: update-manager
  Title: update-manager crashed with SystemExit in exit(): 0
  UpgradeStatus: Upgraded to saucy on 2013-03-21 (118 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2018-07-31 Thread Romano Giannetti

I also think it's an upgrade artifact. It happened on my upgraded laptop but 
not in the freshly installed desktop machine. 
The problem in the laptop now (I think) hostapd that requires dnsmasq. 
The workaround cited by @ahasenack in #49 seems to work.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name:

[Touch-packages] [Bug 1521987]

Sure, if you write a patch I will compile and test it.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

2018-07-31 Thread Pablow-1422

(In reply to pablow.1422 from comment #44)
> Created attachment 131569 [details]
> pulse audio verbose log
> 
> Same problem and use case: analog line-out speakers, headphone plugged-in,
> headphone unplugged, digital output profile set instead of analog line-out
> (Analog Duplex to be precise). 
> 
> It happens on Fedora 25 (10.0-2.fc25) and openSUSE tumbleweed (can't have
> access to that PC right now), both running KDE Plasma desktop (5.9.5).
> 
> KDE devs said it should be reported here
> [https://bugs.kde.org/show_bug.cgi?id=380316#add_comment]

Never mind. Something in the miniplug speaker contact was preventing the
detection of the port as being connected. Sorry for the useless reply.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

(In reply to flat from comment #40)
> Same issue on xfce4, so it's not budgie.

It certainly was Budgie according to the log. Maybe xfce4 has a similar
bug in its volume control thingy.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

2018-07-31 Thread Pablow-1422

Created attachment 131569
pulse audio verbose log

Same problem and use case: analog line-out speakers, headphone plugged-
in, headphone unplugged, digital output profile set instead of analog
line-out (Analog Duplex to be precise).

It happens on Fedora 25 (10.0-2.fc25) and openSUSE tumbleweed (can't
have access to that PC right now), both running KDE Plasma desktop
(5.9.5).

KDE devs said it should be reported here
[https://bugs.kde.org/show_bug.cgi?id=380316#add_comment]

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Created attachment 129175
0001-card-log-the-reason-for-profile-changes.patch

Here's the patch. It's written against the git master branch. If you
need it for some other PulseAudio version, let me know and I'll rebase
it.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Created attachment 129265
pulse audio verbose log with 0001-card-log-the-reason-for-profile-changes.patch 
10.0

Here is the log from the new rebased patch. The bug did occur in git
master but not as often.

>The first log shows four "audio-volume-change" sounds being played in quick
>succession during the crash. The volume changes are initiated by 
>gnome-settings-daemon.
>Did you change the volume manually while disconnecting the headphones, or is 
>this something that gnome-settings-daemon does automatically?

I'm not sure if that was me or not. I usually tap the volume key a
couple times to see what output configuration it is set on because it's
quick. This time I didn't touch the volume manually.

The log should show it switching from 5.1 to digital then digital to 5.1
and then 5.1 to stereo duplex and then stereo duplex to digital.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

(In reply to Tanu Kaskinen from comment #42)
> (In reply to flat from comment #40)
> > Same issue on xfce4, so it's not budgie.
> 
> It certainly was Budgie according to the log. Maybe xfce4 has a similar bug
> in its volume control thingy.

No problem on the delay, thanks for taking the time to look into this.
I'll file a bug report with budgie.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/390.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Created attachment 129226
0001-card-log-the-reason-for-profile-changes.patch (for 10.0)

Here's the updated patch.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Created attachment 129184
pulse verbose log with 0001-card-log-the-reason-for-profile-changes.patch

So interestingly enough I can't reproduce the issue using git master.
Attached are two logs as one attachment. The second log starts at line
5308 (Didn't want to spam attachments). The first log shows pulse
crashing upon disconnecting the headphones. The second log shows pulse
switching between 5.1-stereo and Analog Stereo working fine. If you
rebase the patch on 10.0 I can try it again to see what was going on.
Version 10.0 is the current version from Arch Linux's repos. I assume a
commit since then must have fixed something either intentionally or
unintentionally.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

The new log doesn't seem to have the patch applied. Can you try again?
You can check that pulseaudio is running with the patch by searching the
log for messages that contain "XXX" that are printed whenever the card
profile changes.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Same issue on xfce4, so it's not budgie.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Created attachment 129322
pulse audio verbose log with 0001-card-log-the-reason-for-profile-changes.patch 
10.0

Sorry it took a couple days for it to happen again. Guess it helps when
you compile to actually apply the patch... haha. Here's a log from it
switching between digital and normal, even after I set it to the correct
configurations it seems to switch. Looking through the log I think it
might have to do with budgie-panel, but I'm not sure. Also got another
crash so that's the first log. Second log starts on line 4424

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

(In reply to flat from comment #34)
> Created attachment 129184 [details]
> pulse verbose log with 0001-card-log-the-reason-for-profile-changes.patch
> 
> So interestingly enough I can't reproduce the issue using git master.

The first log with the crash shows a switch to the digital profile.
Unfortunately, the crash happens before the log message I added is
printed.

The first log shows four "audio-volume-change" sounds being played in
quick succession during the crash. The volume changes are initiated by
gnome-settings-daemon. Did you change the volume manually while
disconnecting the headphones, or is this something that gnome-settings-
daemon does automatically?

> Attached are two logs as one attachment. The second log starts at line 5308
> (Didn't want to spam attachments). The first log shows pulse crashing upon
> disconnecting the headphones. The second log shows pulse switching between
> 5.1-stereo and Analog Stereo working fine. If you rebase the patch on 10.0 I
> can try it again to see what was going on. Version 10.0 is the current
> version from Arch Linux's repos. I assume a commit since then must have
> fixed something either intentionally or unintentionally.

I don't think it's fixed in master, but I can anyway make a patch for
10.0. I'll change it so that the profile change reason is printed in an
earlier phase. I'll also add some logging in an attempt to make it
easier to track down the reason for the crash if it happens again.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Sorry for the long delay, I have trouble keeping up with all email...

(In reply to flat from comment #39)
> Created attachment 129322 [details]
> pulse audio verbose log with
> 0001-card-log-the-reason-for-profile-changes.patch 10.0
> 
> Sorry it took a couple days for it to happen again. Guess it helps when you
> compile to actually apply the patch... haha. Here's a log from it switching
> between digital and normal, even after I set it to the correct
> configurations it seems to switch. Looking through the log I think it might
> have to do with budgie-panel, but I'm not sure.

Yes, "Budgie Volume Control" changes the profile to digital.

> Also got another crash so
> that's the first log. Second log starts on line 4424

It's not a crash, it's a failure to start the daemon. module-esound-
protocol-unix can't setup itself, because the socket it needs is
reserved by some other process (probably another pulseaudio instance).
I'm not sure why this happens, but you can safely remove module-esound-
protocol-unix from /etc/pulse/default.pa. It's extremely unlikely that
you have any applications that still use esound.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Thanks, the log is interesting. At line 5943 the headphones are plugged
in. Pulseaudio then decides to switch from the 5.1 profile to the analog
stereo profile, as expected. After switching the profile, however,
pulseaudio decides to immediately switch to digital output instead.
Unfortunately the log doesn't show why this happens.

If I write a patch that adds better logging, will you be able to apply
and test it? Here are some instructions for building and installing
pulseaudio from source:
https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/PulseAudioFromGit/

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

Title:
Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Invalid

Bug description:
When plugging in headphones, sound output is correctly switched from
speakers (line out) to the headphones. When the headphones are
unplugged, sound is NOT automatically switched back to the speakers.

This bug started happening on my system after I upgraded from 14.04 to
15.10 so it is a regression. Attached is pulseaudio log of what
happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

2018-07-31 Thread Htd-c

Just to let you know:

I had a similar bug with Fedora 24 which drove me nuts. Analog output
was always switched back to digital, losing sound. Changing it in
pavucontrol didn't last longer than a few seconds. With the patch from
comment 12, my problem is fixed!

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

I believe PulseAudio 9.0 will handle your use case well. Please report
back if it doesn't.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

2018-07-31 Thread Eugene Crosser

I am not sure that the suggested patch is a good fix for the problem.
As I understand it, with the patch, when the currently active destination 
becomes unavailable, new destination is chosen on the basis of its priority.

Now consider my own use case:
I have S/PDIF and Analog outputs on the chip, but S/PDIF is not connected to 
anywhere (there is no connector on the box). I have speakers permanently 
connected to the analog "line out" socket. And I use headphones intermittently. 
Normally, desktop's audio widget configures "line out" as active, which is what 
I want. When I plug the headphones, they automatically become active, and 
speakers are muted, which is what I want, again. But, when I unplug the 
headphones, (unconnected) S/PDIF becomes active instead of the speakers, and I 
lose sound until I manually reconfigure the output via the audio widget.

I think that my scenario is quite typical (it happens both on my desktop
and notebook computers), and should be addressed better.

Thank you.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Created attachment 128999
digital/5.1 - stereo out/digital

Sorry, this bug isn't consistent so that last log may not have reflected
the issue. This _should_ show that it starts my headphones as digital
out, upon unplugging the line out should be switched to 5.1. Again
plugging in headphones changes the output to digital. After setting the
headphones to stereo out via pulse audio volume control, unplugging the
headphones sets the configuration back to digital.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

The log doesn't match your problem description. The digital profile is
not activated at all. The log shows switching between headphones and
lineout in 2.1 mode. You wanted to use 5.1, so is your problem actually
that you get 2.1 audio instead of 5.1?

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Created attachment 128797
Pulse Log incorrect switching

Log that should show pulse incorrectly switching to digital when it
should switch back to the previous configuration for speakers.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

2018-07-31 Thread Eugene Crosser

(In reply to Tanu Kaskinen from comment #24)
> Do you happen to have the audio settings application open? If you do, it can
> mess up the device selection:
> https://bugzilla.gnome.org/show_bug.cgi?id=762932

It happens when audio control application running and not running
likewise, but desktop's audio widget in the panel is indeed running
(Cinnamon and Unity, same manifestations). It is possible that this
audio widget is indeed the culprit.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

In my case speakers should be set to Analog Surround 5.1 Output + Analog
Stereo Input, however after unplugging headphones they are switched to
digital out.

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

(In reply to Eugene Crosser from comment #25)
> It happens when audio control application running and not running likewise,
> but desktop's audio widget in the panel is indeed running (Cinnamon and
> Unity, same manifestations). It is possible that this audio widget is indeed
> the culprit.

It's possible, but I don't think it's likely.

Can you attach a log file that shows what happens when you start with
analog output selected and headphones plugged in, and then unplug them
and plug them back in? Instructions for getting the log:
https://wiki.ubuntu.com/PulseAudio/Log

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

Do you happen to have the audio settings application open? If you do, it
can mess up the device selection:
https://bugzilla.gnome.org/show_bug.cgi?id=762932

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

2018-07-31 Thread Eugene Crosser

(In reply to Tanu Kaskinen from comment #22)
> I believe PulseAudio 9.0 will handle your use case well. Please report back
> if it doesn't.

It does not.
Version: 1:9.0-2ubuntu2
Same behavior: after plugging and unplugging the headset some nonexistent 
device becomes active, and I have no sound until I manually select "line out".

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987]

*** Bug 96237 has been marked as a duplicate of this bug. ***

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1521987] Re: Sound is not automatically switched back from headphones to speakers

** Changed in: pulseaudio
   Status: Confirmed => Unknown

** Bug watch added: GNOME Bug Tracker #762932
   https://bugzilla.gnome.org/show_bug.cgi?id=762932

** Bug watch added: KDE Bug Tracking System #380316
   https://bugs.kde.org/show_bug.cgi?id=380316

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

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Touch-packages] [Bug 1784706] [NEW] [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front] Background noise or low volume

2018-07-31 Thread MD Intisar

Public bug reported:

I am having the same problem with Linux Mint. I play any audio(from
YouTube or hard disk) and the volume is very low. And the background
noise is very high. Apparently Ubuntu did not have such a problem. But
unfortunately I am facing this problem which I tried not to face by
abandoning Linux mint and switching to Ubuntu.

I am expecting:

1. Stopping background noise
2. Stable and decent volume.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mdintisar   3307 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  1 01:51:48 2018
InstallationDate: Installed on 2018-07-29 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: High background noise, or volume is too low
Title: [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front] Background 
noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 0F1J0W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5459:pvr:rvnDellInc.:rn0F1J0W:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5459
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front]
  Background noise or low volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am having the same problem with Linux Mint. I play any audio(from
  YouTube or hard disk) and the volume is very low. And the background
  noise is very high. Apparently Ubuntu did not have such a problem. But
  unfortunately I am facing this problem which I tried not to face by
  abandoning Linux mint and switching to Ubuntu.

  I am expecting:

  1. Stopping background noise
  2. Stable and decent volume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdintisar   3307 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  1 01:51:48 2018
  InstallationDate: Installed on 2018-07-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [Inspiron 5459, Realtek ALC3234, Black Headphone Out, Front] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 0F1J0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5459:pvr:rvnDellInc.:rn0F1J0W:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5459
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784706/+subscriptions

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

[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

2018-07-31 Thread dann frazier

** Description changed:

- On a HiSilicon D06 system we noticed that interfaces provided by a plug-
- in "HINIC" network card are not getting assigned predictable names.
- We're getting "ethX" names instead of the expected "enPblah" names.
+ [Impact]
+ Interfaces associated with Huawei "hinic" PCI adapters will not be assigned 
predictable names[*] and instead remain using the kernel names (e.g. eth0). 
This can lead to races where the interface names are not the same on every 
boot. For example, in a system with both 2-port hinic and 2-port igb devices, 
the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic 
before igb loaded. But if igb completes loading first, the hinic interfaces 
would be eth2 & eth3.
+ 
+ [*]
+ 
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
+ 
+ [Test Case]
+ grep ^eth /proc/net/dev
+ 
+ [Fix]
+ There's an upstream fix that properly associates the hinic interfaces with 
their PCI devices, providing udev with the info it needs to generate a 
predictable name.
+ 
+ [Regression Risk]
+ The big regression risk here is with existing bionic installs w/ hinic 
devices. They will be currently using "eth" names by default, and this change 
will cause those names to change to "enP" names after upgrade. However, in only 
certain configs are those "eth" names reliable (e.g. only NIC in the system is 
a hinic plug-in card). It sucks to introduce such a change in a stable release 
- but users will be bitten by this when they upgrade or transition to the HWE 
kernel anyway if we don't.

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

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Interfaces associated with Huawei "hinic" PCI adapters will not be assigned 
predictable names[*] and instead remain using the kernel names (e.g. eth0). 
This can lead to races where the interface names are not the same on every 
boot. For example, in a system with both 2-port hinic and 2-port igb devices, 
the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic 
before igb loaded. But if igb completes loading first, the hinic interfaces 
would be eth2 & eth3.

  [*]
  
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

  [Test Case]
  grep ^eth /proc/net/dev

  [Fix]
  There's an upstream fix that properly associates the hinic interfaces with 
their PCI devices, providing udev with the info it needs to generate a 
predictable name.

  [Regression Risk]
  The big regression risk here is with existing bionic installs w/ hinic 
devices. They will be currently using "eth" names by default, and this change 
will cause those names to change to "enP" names after upgrade. However, in only 
certain configs are those "eth" names reliable (e.g. only NIC in the system is 
a hinic plug-in card). It sucks to introduce such a change in a stable release 
- but users will be bitten by this when they upgrade or transition to the HWE 
kernel anyway if we don't.

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

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

[Touch-packages] [Bug 1575109] Re: Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation (0x2a) in section `.init'

2018-07-31 Thread James Niland

since the update my gcc-4.8 will not compile (Make) Ubuntu 140.4.5 
(Linux-...generic-..131.)
So far I have had to r-sync a backup on my system because of updates, 4 times 
the last 2 months due to upstates. I am confused, frustrated and dismayed 
recently with Ubuntu. This bug is no allowing me to compile the driver from 
http://foo2hbpl.rkkda.com for my printer. Now not working either!

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

Title:
  Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation
  (0x2a) in section `.init'

Status in binutils:
  New
Status in binutils package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in binutils package in Debian:
  Fix Released

Bug description:
  Running sa-compile (may take a long time)
  /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: unrecognized 
relocation (0x2a) in section `.init'
  /usr/bin/ld: final link failed: Bad value
  collect2: error: ld returned 1 exit status
  make: *** [blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so] 
Error 1
  command 'make >>/tmp/.spamassassin6654c6JaRRtmp/log' failed: exit 2
  dpkg: error processing package sa-compile (--configure):
   subprocess installed post-installation script returned error exit status 25
  Errors were encountered while processing:
   libgmp-dev:amd64
   systemd
   sa-compile

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:15.10.14.4
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Apr 26 11:38:01 2016
  InstallationDate: Installed on 2012-02-04 (1542 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root

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

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

[Touch-packages] [Bug 1509950]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/211.

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

Title:
  DELL XPS M1210 STAC9221 Dual Headphone jacks not working

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 15.10 after latest update headphones stopped working. When I
  ran alsamixer in the terminal, I saw they were muted. after unmuting
  them I pressed F6 and saw the soundcard id, then pressed esc and esc
  to exit alsamixer then entered  sudo alsactl store Intel  After
  rebooting they worked!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1272 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 02:15:01 2015
  InstallationDate: Installed on 2015-10-20 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151019)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd09/11/2008:svnDellInc.:pnMXC062:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXC062
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1509950/+subscriptions

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

[Touch-packages] [Bug 1509950] Re: DELL XPS M1210 STAC9221 Dual Headphone jacks not working

** Changed in: alsa-driver
   Status: Confirmed => Unknown

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

Title:
  DELL XPS M1210 STAC9221 Dual Headphone jacks not working

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 15.10 after latest update headphones stopped working. When I
  ran alsamixer in the terminal, I saw they were muted. after unmuting
  them I pressed F6 and saw the soundcard id, then pressed esc and esc
  to exit alsamixer then entered  sudo alsactl store Intel  After
  rebooting they worked!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1272 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 02:15:01 2015
  InstallationDate: Installed on 2015-10-20 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151019)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd09/11/2008:svnDellInc.:pnMXC062:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXC062
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1509950/+subscriptions

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

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2018-07-31 Thread Si Dedman

In case it helps anyone else on *buntu systems:
sudo apt-get install libcap-dev
sudo apt-get install libsndfile-dev
Warning: UDEV & SPEEX not enabled:
./configure --enable-udev --enable-speex
didn't work for me. See 
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/28 and comment 4 
here: 
https://www.linuxquestions.org/questions/linux-software-2/audio-problems-pulseaudio-installation-938130/
./configure --enable-speex
make
sudo make install
pulseaudio --version

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1784107] Re: package python3-update-manager 1:18.04.11.4 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd

2018-07-31 Thread Brian Murray

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

** This bug has been marked a duplicate of bug 1779237
   package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4

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

Title:
  package python3-update-manager 1:18.04.11.4 failed to install/upgrade:
  vereistenproblemen - blijft ongeconfigureerd

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.1 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-update-manager 1:18.04.11.4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   linux-headers-4.15.0-23:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jul 27 06:02:05 2018
  ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-06-12 (45 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: update-manager
  Title: package python3-update-manager 1:18.04.11.4 failed to install/upgrade: 
vereistenproblemen - blijft ongeconfigureerd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1784107/+subscriptions

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

[Touch-packages] [Bug 1784514] Re: Update evolution-data-server to 3.28.5

This bug was fixed in the package evolution-data-server -
3.28.5-3ubuntu1

---
evolution-data-server (3.28.5-3ubuntu1) cosmic; urgency=medium

  * debian/libebook-contacts-1.2-2.symbols: Mark a symbol as optional
since it isn't present in Ubuntu's ppc64el build

evolution-data-server (3.28.5-3) unstable; urgency=medium

  * debian/libebook-contacts-1.2-2.symbols: Adjust for hppa

evolution-data-server (3.28.5-2) unstable; urgency=medium

  * Update symbols files for new release

evolution-data-server (3.28.5-1) unstable; urgency=medium

  * New upstream release (LP: #1784514)

 -- Jeremy Bicha   Tue, 31 Jul 2018 10:11:35 -0400

** Changed in: evolution-data-server (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update evolution-data-server to 3.28.5

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Bionic:
  In Progress

Bug description:
  Impact
  ==
  3.28.5 is the final scheduled bug fix release in the 3.28 series.

  Updating e-d-s is required to update evolution to 3.28.5 (LP:
  #1784522)

  https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS
  https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.28 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+subscriptions

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

[Touch-packages] [Bug 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions

** Branch linked: lp:~ubuntu-core-dev/ubuntu/cosmic/apport/ubuntu

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

Title:
  Add a remember option to whoopsie so that users can diminish crash
  interactions

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]
  A lot of users are bother by the number of whoopsie dialog. We introduced on 
"G-C-C privacy option don't allow sending manual report" bug 
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a 
way for users to change from always reporting manually (prompting an UI) to 
auto reporting or never reporting, via a "Remember this in future".

  This only impacts the apport gtk UI, still offering the underlying
  capability to other UIs type without changing them.

  This was a goal for 18.04, but due to a lack of time, we want to
  introduce this in 18.04.1

  [ Test Case ]
   * There are multiples dialog forms (a good 20 of them), but they are all 
covered by unit tests which have been updates. One use case would be:
   * Install the new version and trigger a crash
   * Check that the dialog has a "Remember this in future" option, check it, 
and click send.
   * Check in g-c-c UI, privacy option, that the crash reporting is now in auto 
mode, always send.
   * Revert in g-c-c to manual
   * Create another crash, check "Remember this…" and click don't send
   * Check in g-c-c UI that crash reporting is now disabled.

  [ Regression potential ]
   * The impacted code is both UI and fileutils. It's covered by an extensive 
testsuite, and checking under KDE has also been done to not trigger a crash.

  

  We introduce 5 new strings to translate:
  "Can't remember send report status settings"
  "Saving crash reporting state failed. Can't set auto or never reporting mode."
  "Remember this in future"
  "Relaunch this application"
  "Don't send"

  We are reusing an existing transalted string "Send problem report to
  the developers?"

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

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

[Touch-packages] [Bug 1776074] Re: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead)

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

Title:
  indicator-datetime shouldn't recommend big ubuntu-touch-sounds package
  (maybe Suggests should be used instead)

Status in Default settings and artwork for Baltix OS:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  indicator-datetime package has big ubuntu-touch-sounds package in
  Recommends field even in latest Ubuntu Bionic release.

  gnome-panel recommends indicator-applet-complete and indicator-applet-
  complete recommends indicator-datetime, so big and not useful ubuntu-
  touch-sounds is installed in all desktop systems, where gnome-
  flashback (gnome-panel) desktop environment is used.

  I think ubuntu-touch-sounds should be removed from Recommends field
  and if there are some cases, where ubuntu-touch-sounds is usefull for
  indicator-datetime, then Suggests should be used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1776074/+subscriptions

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

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

** Branch linked: lp:~ubuntu-core-dev/ubuntu/cosmic/apport/ubuntu

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

Title:
  In autoreport mode in whoopsie-preferences API, reports are not sent
  by whoopsie

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]
  * The goal for autoreporting via whoopsie is to have a silent mode where 
whoopsie automatically reports crashes. However, this one requires apport-noui 
to be installed, which we don't by default.
  apport-noui is just a set of systemd unit starting whoopsie-upload-all (part 
of apport binary package).
  We should move the unit to apport package itself.

  [ Test Case ]
  * Install the new apport package from proposed
  * Set in g-c-c, privacy panel, to report bugs automatically
  * Make one program dumping a core dump
  * Wait for a while, you should have a .upload and .uploaded files in addition 
to the .crash one in /var/crash

  [ Regression potential ]
  The systemd units were in apport-noui previously, we moved them and made them 
conditional to whoopsie being installed.
  apport-noui is still useful by turning autoreport on, so people upgrading 
shouldn't have any impact or difference.
  The units have been renamed to make sense and avoid package files overwrite.

  -
  There are 2 possible solutions:
  - promoting apport-noui to main, and seeding it.
  - or considering there is no reason anymore to have a separate apport-noui 
pacakge (no more phone factor), and so move the systemd units to apport, having 
a conditional file on whoopsie installed (no more dependency) and autoreport 
enabled, shipping those units binary package shipping those units (renamed to 
apport-autoreport.*) directly.

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2018-07-31 Thread jnns

initramfs-tools-0.130ubuntu3.2 seems to remove the wait time on my
system as well!

What I did:

> rm /etc/initramfs-tools/conf.d/resume
> sudo update-initramfs -u

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions

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

[Touch-packages] [Bug 1784669] [NEW] package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de ou

2018-07-31 Thread Anderson Porto

Public bug reported:

I was trying to install nautilus-image-converter-0-3-1-en-ubu.deb and
then crashed!

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libunity9 7.1.4+18.04.20180209.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 31 13:03:49 2018
ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, 
que é diferente de outras instâncias do pacote libunity9:i386
InstallationDate: Installed on 2018-05-15 (76 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: libunity
Title: package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to 
install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to
  install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader'
  partilhado, que é diferente de outras instâncias do pacote
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  I was trying to install nautilus-image-converter-0-3-1-en-ubu.deb and
  then crashed!

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libunity9 7.1.4+18.04.20180209.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 31 13:03:49 2018
  ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
  InstallationDate: Installed on 2018-05-15 (76 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: libunity
  Title: package libunity9 7.1.4+18.04.20180209.1-0ubuntu2 failed to 
install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2018-07-31 Thread Si Dedman

"pulseaudio --version" to check
v12.2 link 
https://www.freedesktop.org/software/pulseaudio/releases/pulseaudio-12.2.tar.xz

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1421002]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/57.

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

Title:
  pulseaudio crashed with SIGABRT in transport_speaker_gain_changed_cb()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Change Bluethooth

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:4.0-0ubuntu23
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2991 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 11 20:01:45 2015
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-09-25 (139 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/pulse-4.0/modules/module-bluetooth-device.so
   pa_hook_fire () from /usr/lib/libpulsecore-4.0.so
   ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so
   ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: pulseaudio crashed with SIGABRT in pa_hook_fire()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1421002] Re: pulseaudio crashed with SIGABRT in transport_speaker_gain_changed_cb()

** Changed in: pulseaudio
   Status: Confirmed => Unknown

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

Title:
  pulseaudio crashed with SIGABRT in transport_speaker_gain_changed_cb()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Change Bluethooth

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:4.0-0ubuntu23
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2991 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 11 20:01:45 2015
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-09-25 (139 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/pulse-4.0/modules/module-bluetooth-device.so
   pa_hook_fire () from /usr/lib/libpulsecore-4.0.so
   ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so
   ?? () from /usr/lib/pulse-4.0/modules/libbluetooth-util.so
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: pulseaudio crashed with SIGABRT in pa_hook_fire()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

2018-07-31 Thread Brian Murray

On an Ubuntu 14.04 system I installed the libglib2.0-0 package, then
modified my /etc/apt/sources.list file from trusty to xenial, tried to
install libglib2.0-0 and then experienced the crash in this bug report.

I performed the same steps but added xenial-proposed to my
/etc/apt/sources.list file and then the upgrade wanted to also install
dpkg among other things.

(trusty-amd64)root@impulse:/home/bdmurray# apt-get install libglib2.0-0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libboost-date-time1.54.0 libboost-system1.54.0 libcdr-0.0-0 libcmis-0.4-4
  libelfg0 libevdev2 libgnome-desktop-3-12 libinput-bin libinput10
  libmspub-0.0-0 liborcus-0.6-0 librhythmbox-core8 libvisio-0.0-0 libwpd-0.9-9
  libwpg-0.2-2 libwps-0.2-2 overlay-scrollbar-gtk2 pidgin-data
  rhythmbox-mozilla xfonts-mathml
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  adwaita-icon-theme apt apt-utils console-setup console-setup-linux cups
  cups-bsd cups-client cups-common cups-core-drivers cups-daemon
  cups-server-common dbus dpkg fontconfig fontconfig-config fonts-stix
  gcc-5-base gir1.2-javascriptcoregtk-4.0 gir1.2-rb-3.0 gir1.2-webkit2-4.0
...

Then in /var/log/apt/term.log we can see:

...
Setting up dpkg (1.18.4ubuntu1.4) ...^M$
Installing new version of config file /etc/cron.daily/dpkg ...^M$
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database 
... 25%^M(Re
ading database ... 30%^M(Reading database ... 35%^M(Reading database ... 
40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database 
... 55%^M(R
eading database ... 60%^M(Reading database ... 65%^M(Reading database ... 
70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database 
... 85%^M(
Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 
100%^M(Reading database ... 132743 files and directories currently 
installed.)^M$
Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu4_amd64.deb ...^M$
Unpacking libglib2.0-0:amd64 (2.48.2-0ubuntu4) over (2.40.2-0ubuntu1) ...^M$
...

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

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

Title:
  upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Xenial:
  Fix Committed

Bug description:
  [Test case]
  Verify that a release-upgrade of an Ubuntu desktop works from trusty to 
xenial with -proposed enabled.

  Package failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0 2.48.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jul 27 18:31:08 2018
  DuplicateSignature:
   package:libglib2.0-0:2.48.2-0ubuntu3
   Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack):
    triggers ci file contains unknown directive `interest-await'
  ErrorMessage: triggers ci file contains unknown directive `interest-await'
  InstallationDate: Installed on 2015-03-31 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: 
triggers ci file contains unknown directive `interest-await'
  UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions

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

[Touch-packages] [Bug 1784514] Re: Update evolution-data-server to 3.28.5

2018-07-31 Thread Jeremy Bicha

** Changed in: evolution-data-server (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  Update evolution-data-server to 3.28.5

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Bionic:
  In Progress

Bug description:
  Impact
  ==
  3.28.5 is the final scheduled bug fix release in the 3.28 series.

  Updating e-d-s is required to update evolution to 3.28.5 (LP:
  #1784522)

  https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS
  https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.28 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+subscriptions

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

[Touch-packages] [Bug 884336]

2018-07-31 Thread Arun Raghavan

This looks very much like an ALSA driver issue, so I'm dropping it as a
2.0 blocker.

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

Title:
[Oneiric] HDMI output does not work immediately

Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Invalid

Bug description:
In Oneiric, the output of 5.1 sound (not AC3 passthrough, but multi-
channel PCM) via the HDMI connector of my onboard Intel graphics card
is finally working. This is really great!

For this to work, I have configured Pulseaudio to use the "Digital
Surround 5.1 (HDMI) Output". The HDMI output of my computer is
connected to a 5.1 receiver.

However, there is one nuisance: Whenever I start playing sound on the
computer (e.g., rhythmbox or VLC, both playing via PulseAudio), I hear
no sound. On my receiver I have to re-select the input source for the
computer, which seems to initiate a HDMI handshake (it lasts 3
seconds). Only after this I am able to hear sound.

If I press pause and continue in Rhythmbox, the sound continues fine.
If I stop and restart Rhythmbox, I have to do the above procedure
again. The same is true for VLC and probably for all other players.

While playing around, I have noticed that sound is also working after
killing pulseaudio while playing something in Rhythmbox. When the
connection to Pulseaudio is killed, Rhythmbox tries a fallback to
ALSA. As the Pulseaudio daemon was immediately restarted, this will
result in Rhythmbox being connected via the ALSA plugin (before the
connection was direct). It seems that Pulseaudio is doing the
necessary things here, because after this I do hear sound (as long as
Rhythmbox runs). However, this trick does not work for other players
like VLC which don't fall back to ALSA.

Note that while for me this is just a nuisance, it may be a real
blocker for other users. As long as you don't try to fiddle with the
receiver inputs while playing sound on the computer, you hear
absolutely nothing via HDMI. This includes the sounds from the speaker
test dialog of Pulseaudio. I guess a lot of users would give up and
think that HDMI output is broken in Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: pulseaudio 1:1.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: philipp7706 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 50'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0892,80862002,00100302
HDA:80862805,80862805,0010'
Controls : 31
Simple ctrls : 16
Date: Mon Oct 31 18:07:22 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcEnviron:
LANGUAGE=de:en
PATH=(custom, no user)
LANG=de_DE.UTF-8
LC_MESSAGES=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to oneiric on 2011-10-31 (0 days ago)
dmi.bios.date: 11/15/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0076.2010.1115.1959
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67BL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10189-205
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0076.2010.1115.1959:bd11/15/2010:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-205:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 884336]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/147.

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

Title:
[Oneiric] HDMI output does not work immediately

Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Invalid

Bug description:
In Oneiric, the output of 5.1 sound (not AC3 passthrough, but multi-
channel PCM) via the HDMI connector of my onboard Intel graphics card
is finally working. This is really great!

For this to work, I have configured Pulseaudio to use the "Digital
Surround 5.1 (HDMI) Output". The HDMI output of my computer is
connected to a 5.1 receiver.

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

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

[Touch-packages] [Bug 884336]

2018-07-31 Thread Matt Horan

I'm seeing a similar issue with a similar setup. I've got a media
center connected to a receiver via HDMI. Sometimes when I'm playing
audio and power-cycle devices in the chain (TV, receiver, etc), pulse
will stop playing audio. I don't get any errors or anything, and
issuing pulseaudio -k will bring it all back.

I tried commenting out the module-suspend-on-idle module. It seemed to
work at first, but I eventually got into a state where PA applications
complained about not being able to play back, and audio went silent.

I think this could be an ALSA issue, but it's quite difficult to debug.
Has anyone else come up with a solution to this problem?

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

Title:
[Oneiric] HDMI output does not work immediately

Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Invalid

Bug description:
In Oneiric, the output of 5.1 sound (not AC3 passthrough, but multi-
channel PCM) via the HDMI connector of my onboard Intel graphics card
is finally working. This is really great!

For this to work, I have configured Pulseaudio to use the "Digital
Surround 5.1 (HDMI) Output". The HDMI output of my computer is
connected to a 5.1 receiver.

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

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

[Touch-packages] [Bug 884336] Re: [Oneiric] HDMI output does not work immediately

** Changed in: pulseaudio
Status: Confirmed => Unknown

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

Title:
[Oneiric] HDMI output does not work immediately

Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
Invalid

Bug description:
In Oneiric, the output of 5.1 sound (not AC3 passthrough, but multi-
channel PCM) via the HDMI connector of my onboard Intel graphics card
is finally working. This is really great!

For this to work, I have configured Pulseaudio to use the "Digital
Surround 5.1 (HDMI) Output". The HDMI output of my computer is
connected to a 5.1 receiver.

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

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

[Touch-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-N (N > 1) in daemon.conf

Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=104486.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2018-01-04T07:49:20+00:00 Amr Ibrahim wrote:

I suggest changing the default resample-method to speex-float-10,
instead of speex-float-1, which is the current default now, in
/etc/pulse/daemon.conf.

In my day-to-day usage, it gives better sound quality without
sacrificing CPU power.

I have always done that since at least 2012. I was not satisfied with
the sound quality in Ubuntu compared to Windows, so I changed the
resample-method.

It would look like this in daemon.conf:
resample-method = speex-float-10

I have not tried other resample methods. Maybe there are better options
I don't know about.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1741045/comments/3

On 2018-07-30T10:16:36+00:00 Gitlab-migration wrote:

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/310.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1741045/comments/6

** Changed in: pulseaudio
Status: Confirmed => Unknown

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

Title:
Change the default resample-method to speex-float-N (N > 1) in
daemon.conf

Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
New

Bug description:
I suggest changing the default resample-method to speex-float-10,
instead of speex-float-1, which is the current default now, in
/etc/pulse/daemon.conf.

It would look like this in daemon.conf:
resample-method = speex-float-10

I have always done that since at least 12.04 LTS. I was not satisfied
with the sound quality in Ubuntu compared to Windows, so I changed the
resample-method.

In my day-to-day usage, it gives better sound quality without
sacrificing CPU power.

I have not tried other resample methods. Maybe there are better
options I don't know about.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: amr1696 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 3 14:37:25 2018
InstallationDate: Installed on 2017-10-02 (92 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-S2P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-S2P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

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

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

[Touch-packages] [Bug 1784637] [NEW] Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

2018-07-31 Thread grofaty

Public bug reported:

I have updated Ubuntu: sudo apt update && sudo apt -y full-upgrade

and the warnings at the end appear (actually this warnings appeared
several times during few weeks/months and today I decided to report bug
report):

W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915


I am attaching whole update procedure in file.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libudev1 229-4ubuntu21.4
ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-29-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Tue Jul 31 16:02:06 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
InstallationDate: Installed on 2018-01-20 (191 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial

** Attachment added: "whole_update.log"
   
https://bugs.launchpad.net/bugs/1784637/+attachment/5170005/+files/whole_update.log

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

Title:
  Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for
  module i915

Status in systemd package in Ubuntu:
  New

Bug description:
  I have updated Ubuntu: sudo apt update && sudo apt -y full-upgrade

  and the warnings at the end appear (actually this warnings appeared
  several times during few weeks/months and today I decided to report
  bug report):

  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  
  I am attaching whole update procedure in file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libudev1 229-4ubuntu21.4
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Tue Jul 31 16:02:06 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2018-01-20 (191 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1784514] Re: Update evolution-data-server to 3.28.5

2018-07-31 Thread Jeremy Bicha

** Changed in: evolution-data-server (Ubuntu Bionic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  Update evolution-data-server to 3.28.5

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Bionic:
  Triaged

Bug description:
  Impact
  ==
  3.28.5 is the final scheduled bug fix release in the 3.28 series.

  Updating e-d-s is required to update evolution to 3.28.5 (LP:
  #1784522)

  https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS
  https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.28 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+subscriptions

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2018-07-31 Thread Andreas Hasenack

I don't know what is the use case you guys have that you have to have
dnsmasq and resolvconf installed. Maybe there is none and this is just
an artifact from a release upgrade.

In Bionic, I only have dnsmasq-base (not dnsmasq) installed, and no
resolvconf.

Looking at the initscript from dnsmasq, there seem to be a few options to 
disable it for local dns resolving, like the one suggested in 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670959/comments/32, 
which I reproduce below:
Added this line to /etc/default/dnsmasq:

DNSMASQ_EXCEPT=lo

Then restarting dnsmasq:

sudo systemctl daemon-reload
sudo systemctl restart dnsmasq


That will prevent the code quoted in 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670959/comments/47 from 
running.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date:

[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches

2018-07-31 Thread Kleber Sacilotto de Souza

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  locking sockets broken due to missing AppArmor socket mediation
  patches

Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Triaged
Status in apparmor source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in apparmor source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Hey,

  Newer systemd makes use of locks placed on AF_UNIX sockets created
  with the socketpair() syscall to synchronize various bits and pieces
  when isolating services. On kernels prior to 4.18 that do not have
  backported the AppArmor socket mediation patchset this will cause the
  locks to be denied with EACCESS. This causes systemd to be broken in
  LXC and LXD containers that do not run unconfined which is a pretty
  big deal. We have seen various bug reports related to this. See for
  example [1] and [2].

  If feasible it would be excellent if we could backport the socket
  mediation patchset to all LTS kernels. Afaict, this should be 4.4 and
  4.15. This will unbreak a whole range of use-cases.

  The socket mediation patchset is available here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4

  
  [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779
  [2]: https://github.com/systemd/systemd/issues/9493

  Thanks!
  Christian

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

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

[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath

2018-07-31 Thread Francis Ginther

** Tags added: id-5b5f9c7990f052a107d9963c

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk. 
  Running the fdisk -l and ls -l showing the conflict name for the mpath. 

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot  StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part12048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2   419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3   838862848  964691967 125829120   60G 83 Linux
  /dev/mapper/mpatha-part4   964691968 1258291199 293599232  140G  5 
Extended
  /dev/mapper/mpatha-part5   964694016 1006637055  41943040   20G 83 Linux
  /dev/mapper/mpatha-part6  1006639104 1048582143  41943040   20G 83 Linux
  /dev/mapper/mpatha-part7  1048584192 1090527231  41943040   20G 83 Linux
  /dev/mapper/mpatha-part8  1090529280 1132472319  41943040   20G 83 Linux

  == Comment: #5 - Kyle Mahlkuch  - 2018-06-26 13:50:12 
==
  I have created and submitted a patch that should help with this bug. I will 
update when/if the patch is accepted.

  == Comment: #9 - Kyle Mahlkuch  - 2018-07-27 09:10:44 
==
  Here is the patch: 
  
https://github.com/karelzak/util-linux/commit/73775189767195f1d9f5b6b6f6a54e51f61c4356

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784347/+subscriptions

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

[Touch-packages] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

2018-07-31 Thread Łukasz Zemczak

Thanks for verifying!

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

Title:
  kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC 
image on a z/VM guest
  leads to a kernel panic:

  /lib/debian-installer/start-udev: line 15: can't create 
/sys/module/scsi_mod/par
  ameters/scan: Permission denied 
  ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ 
exitcode=0x00
  000100 
  ¬0.845071|  
  ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic 
#157-Ubun
  tu 
  ¬0.845077|7d107c20 7d107cb0 0002 
000
  0  
 7d107d50 7d107cc8 7d107cc8 00114732  
 008b 009a304c 009f11d0 000b  
 7d107d10 7d107cb0    
 040001cdf800 00114732 7d107cb0 7d107d10  
  ¬0.845089| Call Trace: 
  ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) 
  ¬0.845095|  ¬<001146e2>| show_stack+0x72/0xf8 
  ¬0.845099|  ¬<00555752>| dump_stack+0x82/0xb8 
  ¬0.845101|  ¬<00286390>| panic+0x108/0x250 
  ¬0.845104|  ¬<00166228>| do_exit+0xac0/0xba0 
  ¬0.845106|  ¬<001663c8>| do_group_exit+0x50/0xe0 
  ¬0.845108|  ¬<00166488>| __wake_up_parent+0x0/0x28 
  ¬0.845111|  ¬<007eadda>| system_call+0xee/0x28c 
  ¬0.845113|  ¬<03ff8953983a>| 0x3ff8953983a 
  00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  
0010F8CA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

Vinícius Milanez Couto, in order to allow additional upstream mainline kernel 
developers to examine the issue, at your earliest convenience, could you please 
test the latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Project changed: bluez => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: Linux Kernel Bug Tracker #199035 => None

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

** Tags added: bios-outdated-a15 regression-potential

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

Title:
  systemd-udevd consumes 100% of CPU

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

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

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

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

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

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

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2018-07-31 Thread riki34

Guys, try to switch at PulseAudio 12. As for me audio freezes when
watching videos is now gone.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1784023] Re: Update profiles for usrmerge