[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

[Balint Reczey]

This was fixed in several steps with the last one landing in 0.99. The
issue should be fixed now.

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: hundredpapercuts
   Status: Confirmed => Fix Released

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in One Hundred Papercuts:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[Martin Pitt]

Thanks Gunnar, nice work! I cherry-picked the patches in
https://salsa.debian.org/systemd-team/systemd/commit/87f54958bc24 . The
debian/ changes were already in Debian master.

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

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

Title:
  systemd translations are not synced with upstream

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

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[Bug Watch Updater]

** Changed in: systemd
   Status: New => Fix Released

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

Title:
  systemd translations are not synced with upstream

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

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[Federico Cupellini]

Similar situation with a 5 monitor setup
4 exit on Radeon R7 370 / R9 270X/370X
1 through displaylink (usb 17e9:4300)
Mouse flickers:
-Really fast on two DVI exits of the radeon card
-Slower on DP & HDMI exits of radeon card
No flickering on the displaylink monitor
Monitors are 4 x ASUS VS247H 1 x Sony Bravia TV

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719579] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From balamuruh...@in.ibm.com 2018-02-19 03:35 EDT---
> Get me right I use virsh save/restore on a regular base and it works in the 
> paths that are open by default, > which are the places the images usually are 
> from like /var/lib/libvirt/images/.

> If that does not work that might be a modified apparmor rule, but for that 
> I'd need to know way more
> about the case and see if it is actually a bug or really just using an 
> uncommon dir.

Even with uncommon dir, the denial should be consistent if the path used
by the user is not permitted then apparmor should block/deny when virsh
save is performed and not during the virsh restore.

Observation in Ubuntu 16.04.3,

# virsh save virt-tests-vm1 /var/tmp/virt-tests-vm1.save

Domain virt-tests-vm1 saved to /var/tmp/virt-tests-vm1.save

By default virsh restore fails with same error,
# virsh restore /var/tmp/virt-tests-vm1.save
error: Failed to restore domain from /var/tmp/virt-tests-vm1.save
error: operation failed: job: unexpectedly failed

But as suggested by paelzer,
> If you want to look into potential config issues, remove the silent denies to 
> /var and /var temp
> at the end of "/etc/apparmor.d/abstractions/libvirt-qemu".
> Then run your case again, report back with

commenting denials,

# silence spurious denials (see lp#1403648)
deny /tmp/{,**} r,
# deny /var/tmp/{,**} r,

restart libvirtd

# virsh restore /var/tmp/virt-tests-vm1.save
error: Failed to restore domain from /var/tmp/virt-tests-vm1.save
error: internal error: Process exited prior to exec: libvirt:  error : unable 
to set AppArmor profile 'libvirt-81b387d9-1dfc-4f55-8b98-0318f1f94442' for 
'/usr/bin/kvm': No such file or directory

But file exists,
# file /var/tmp/virt-tests-vm1.save
/var/tmp/virt-tests-vm1.save: Libvirt QEMU Suspend Image, version 2, XML length 
1970, running

dmesg:
[Mon Feb 19 03:19:16 2018] virbr0: port 2(vnet0) entered blocking state
[Mon Feb 19 03:19:16 2018] virbr0: port 2(vnet0) entered disabled state
[Mon Feb 19 03:19:16 2018] device vnet0 entered promiscuous mode
[Mon Feb 19 03:19:16 2018] virbr0: port 2(vnet0) entered blocking state
[Mon Feb 19 03:19:16 2018] virbr0: port 2(vnet0) entered listening state
[Mon Feb 19 03:19:16 2018] audit: type=1400 audit(1519028363.683:12417): 
apparmor="DENIED" operation="change_profile" info="label not found" error=-2 
profile="/usr/sbin/libvirtd" 
name="libvirt-81b387d9-1dfc-4f55-8b98-0318f1f94442" pid=12949 comm="libvirtd"
[Mon Feb 19 03:19:16 2018] virbr0: port 2(vnet0) entered disabled state
[Mon Feb 19 03:19:16 2018] device vnet0 left promiscuous mode
[Mon Feb 19 03:19:16 2018] virbr0: port 2(vnet0) entered disabled state

Attaching full dmesg with this bugzilla

Environment:

Kernel
# uname -a
Linux ltc-test-ci1 4.13.0-35-generic #39~16.04.1-Ubuntu SMP Mon Feb 12 15:01:58 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

Libvirt
# dpkg -l | grep libvirt
ii  libvirt-bin 1.3.1-1ubuntu10.18  
   ppc64el  programs for the libvirt library
ii  libvirt-dev:ppc64el 1.3.1-1ubuntu10.18  
   ppc64el  development files for the libvirt library
ii  libvirt0:ppc64el1.3.1-1ubuntu10.18  
   ppc64el  library for interfacing with different virtualization systems
ii  python-libvirt  1.3.1-1ubuntu1.1
   ppc64el  libvirt Python bindings

Qemu
# dpkg -l | grep qemu
ii  ipxe-qemu   1.0.0+git-20150424.a25a16d-1ubuntu1.2   
   all  PXE boot firmware - ROM images for qemu
ii  qemu-block-extra:ppc64el1:2.5+dfsg-5ubuntu10.21 
   ppc64el  extra block backend modules for qemu-system and qemu-utils
ii  qemu-kvm1:2.5+dfsg-5ubuntu10.21 
   ppc64el  QEMU Full virtualization
ii  qemu-slof   20151103+dfsg-1ubuntu1.1
   all  Slimline Open Firmware -- QEMU PowerPC version
ii  qemu-system-common  1:2.5+dfsg-5ubuntu10.21 
   ppc64el  QEMU full system emulation binaries (common files)
ii  qemu-system-ppc 1:2.5+dfsg-5ubuntu10.21 
   ppc64el  QEMU full system emulation binaries (ppc)
ii  qemu-utils  1:2.5+dfsg-5ubuntu10.21 
   ppc64el  QEMU utilities

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

Title:
  [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in
  /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  Fix Released
Status in apparmor package in Ubuntu:
  Invalid
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please 

[Touch-packages] [Bug 1719579] Ubuntu160404_dmesg

[bugproxy]

--- Comment (attachment only) From balamuruh...@in.ibm.com 2018-02-19 03:38 
EDT---


** Attachment added: "Ubuntu160404_dmesg"
   https://bugs.launchpad.net/bugs/1719579/+attachment/5058133/+files/dmesg.txt

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

Title:
  [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in
  /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  Fix Released
Status in apparmor package in Ubuntu:
  Invalid
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : 
OBJECT_DISPOSE: obj=0x100133d2870
  2017

[Touch-packages] [Bug 629258] Re: Battery life estimation never comes around

[Matthew Paul Thomas]

This bug was fixed over six years ago. If you experience similar systems
on multiple operating systems, contact your PC vendor. Otherwise, report
a separate bug.

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

Title:
  Battery life estimation never comes around

Status in DeviceKit-Power:
  Fix Released
Status in gnome-power:
  Invalid
Status in One Hundred Papercuts:
  Invalid
Status in System76:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in upower source package in Maverick:
  Won't Fix

Bug description:
  Binary package hint: gnome-power-manager

  When running on battery, the mouse over text for the battery icon (when 
running on battery) permanently says "Battery life (estimating...)". An 
estimate never shows up.
  Computer: HP Envy 14

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-power-manager 2.31.90-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic-pae 2.6.35.3
  Uname: Linux 2.6.35-19-generic-pae i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Fri Sep  3 06:38:47 2010
  ExecutablePath: /usr/bin/gnome-power-manager
  GConfNonDefault:
   /apps/gnome-power-manager/lock/blank_screen=false
   /apps/gnome-power-manager/lock/use_screensaver_settings=false
   /apps/gnome-power-manager/notify/sleep_failed_uri=
   /apps/gnome-power-manager/ui/icon_policy=charge
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  MachineType: Hewlett-Packard HP ENVY 14 Notebook PC
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic-pae 
root=UUID=76ae939d-2ce2-466e-88d5-98b11aad6098 ro quiet splash
  ProcEnviron:
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 07/21/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1436
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 59.20
  dmi.chassis.asset.tag: CNU0274F2B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.12:bd07/21/2010:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 14 Notebook PC
  dmi.product.version: 0492102419162
  dmi.sys.vendor: Hewlett-Packard

  See also bug #629257 (one lower) for previous (lukewarm) discussions
  on the implications of showing "(estimating...)" via the user
  interface. This two bugs might want re-splitting/sorting again based
  on those that relate to the chrono estimate not being known, and those
  that relate to the pointless display of that unknown data for long
  periods of time to the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devicekit-power/+bug/629258/+subscriptions

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

[Touch-packages] [Bug 1729491] Re: ubuntu-bug says that snap packages are not installed

[Julian Andres Klode]

** Changed in: apport (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Bionic)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Bionic:
  In Progress

Bug description:
  1. 
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed. 

  2. 
  Expected that the program will be identified as installed. 

  3. 
  sudo apt -f install 
  [sudo] password for Alexander: 
  Reading package lists... Done
  Building dependency tree 
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree 
  Reading state information... Ready
  E: unable to locate package gnome-recipes 

  I installed via software-center

  gnome-recipes 
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1. 
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен. 

  2. 
  Ожидал что программа будет идентифицироваться как установленная. 

  3. 
  sudo apt -f install
  [sudo] пароль для alexandr: 
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes 

  произвёл установку через software-center

  gnome-recipes 
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719612] Re: non-us keyboard layout not setup in initramfs

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu1

---
console-setup (1.178ubuntu1) bionic; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- Add an apport hook.
- If the locale is C during configuration, only set CHARMAP to ISO-8859-15
  on kFreeBSD; otherwise restore the previous behaviour from before the
  kFreeBSD port of using UTF-8 in that case.
- Change the default font from Fixed to VGA for Lat15; while it's not
  entirely complete, it looks better and is largely good enough.
- Set keymap and font in the initramfs if possible and sensible.
- debian/vtrgb, debian/vtrgb.vga,
  debian/console-setup-linux.setvtrgb.service, debian/rules,
  debian/console-setup-linux.postinst: use Ubuntu's virtual terminal color
  scheme by default, with a VGA color scheme available as an alternative.
- Don't copy keyboard-configuration questions to /target in OEM mode.
  oem-config will ask them later, and copying these confuses it.
- Tolerate absence of setupcon in postinst scripts.
- Added templates for keyboard detection.
- If the detect-keyboard debconf plugin is available
  (cdebconf-newt-detect-keys in the installer), then offer to use it to
  detect the keyboard layout.
- Fix default keyboard selection for language/country combinations
  lacking a proper combined locale.
- Map ppc64el/* to XKBMODEL=pc105.
- keyboard_present.sh: Quiet config/postinst when we have no USB devices.
- debian/preprocessor: revert the removal of keyboard names (for size) of
  console-setup-udeb: we do need those, since we don't use the simplified
  xkb-keymap template from Debian just yet: this way we can still show
  country/language names when selecting a keyboard, layout or variant.
- Don't make debian/copyright a symlink to COPYRIGHT, this is disallowed
  by the Ubuntu archive installer.
- Include pc105.tree for ubiquity; make sure it gets built.
- Add Keyboard/Makefile rule to build pc105.tree.
- Fix command injection in ckbcomp.
- Generate a locale locally for translating keyboard names in
  kbdnames-maker.
- xmlreader, KeyboardNames.pl: Added model entry to skip model selection.
- setupcon:
  - the variables are taken from a config file which, if changed,
invalidates the cache.
  - there is only ever one keyboard map per system.
  - the system should not have to resolve filenames to find the keymap cache
on boot.
  - Map XKBMODEL=SKIP to '' for compatibility with existing
configs.
  - Explicitly exit 0, so that postinsts don't fail in the event that
loadkeys can't find a console.
- Handle unattended upgrades without breaking plymouth when updating
  console fonts.
- debian/rules: revert hard-coding of a list of "debconf-selectable"
  layouts for the udebs, since we don't use this debconf question in Ubuntu
  and all layouts are selectable.
- Make sure we give a meaningful name to ch layouts: "Switzerland" instead
  of "German (Switzerland), since it includes French too.
- Add console-setup-tty and the udev rule that uses it to set Unicode, font,
  and keyboard mode at early boot.
- Keyboard/Makefile: make sure KeyboardNames.pl is built with accurate data
  from xkb-data.
- Don't cat over the keymaps; they're already moved to the right place.
- debian/console-setup.postinst: Replace the checking of fgconsole in [1-6]
  with checking if fgconsole is a tty according to logind. The previous
  assumption was that a graphical environment would be on vt7, which isn't
  true with gnome-shell any more.
- debian/console-setup.postinst, debian/keyboard-configuration.postinst:
  Don't call setupcon --force -k any more - it breaks wayland sessions.
  (LP: #1710637)
- debian/control: drop console-setup-freebsd: we don't keep it around since
  it's uninstallable because vidcontrol/kbdcontrol.
- debian/keyboard-configuration.config: re-lower the priority for the layout
  question that got garbled in the merge.
- Don't use console-setup-tty or its udev rule. This dates back to lucid and
  now systemd is apparently able to handle this correctly. It's now actively
  breaking graphical sessions. (LP: #1710637)
- debian/control: we also need xkb-data-i18n as a Build-Depends-Indep to
  build a complete set of translated keyboard layout/variant names.
- Drop dependency from console-setup to initramfs-tools |
  linux-initramfs-tool; this was a versioned dependency used for upgrades,
  now long obsolete.
  * Fix previous patches:
- Correctly setup console in initramfs again (LP: #1719612)
- Make COPYRIGHT a symlink to debian/copyright, and keep various
  other symlinks in place that were dropped in earlier uploads.
- Do some extra work to disable kfreebsd, dh was complaining about
  

[Touch-packages] [Bug 1747814] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for libunity has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Released

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Touch-packages] [Bug 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update

[Launchpad Bug Tracker]

This bug was fixed in the package libunity -
7.1.4+16.04.20180209.1-0ubuntu1

---
libunity (7.1.4+16.04.20180209.1-0ubuntu1) xenial; urgency=medium

  * UnityLauncher: Prepend snap namespace to desktop file or desktop-id
(LP: #1747814)

 -- Marco Trevisan (Treviño)   Fri, 09 Feb 2018 15:48:43
+

** Changed in: libunity (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Released

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Touch-packages] [Bug 1750308] Re: FAIL: test_one_adapter (__main__.TestBlueZ5)

[Daniel van Vugt]

OK. I have tracked down the regression to bluez, with a simple test
case. However since the bug doesn't affect normal user operation of
bluez, we don't really need to wait for a bluez fix. We could work
around it in python-dbusmock if necessary. Or even ignore the failing
test.

It may turn out to be a matter of opinion as to whether this is a bug in
bluez at all, or if python-dbusmock was always using it wrong...

https://bugzilla.kernel.org/show_bug.cgi?id=198819

** Bug watch added: Linux Kernel Bug Tracker #198819
   https://bugzilla.kernel.org/show_bug.cgi?id=198819

** Also affects: bluez via
   https://bugzilla.kernel.org/show_bug.cgi?id=198819
   Importance: Unknown
   Status: 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/1750308

Title:
  FAIL: test_one_adapter (__main__.TestBlueZ5)

Status in Bluez Utilities:
  Unknown
Status in bluez package in Ubuntu:
  In Progress
Status in python-dbusmock package in Ubuntu:
  In Progress

Bug description:
  When bluez 5.48 is installed, we see this failure:

  ==
  FAIL: test_one_adapter (__main__.TestBlueZ5)
  --
  Traceback (most recent call last):
File "test_bluez5.py", line 128, in test_one_adapter
  self.assertIn('Controller ' + address, out)
  AssertionError: 'Controller 00:01:02:03:04:05' not found in ['Waiting to 
connect to bluetoothd...', '[\x1b[0;92mNEW\x1b[0m] Controller 00:01:02:03:04:05 
my-computer [default]', '[SIGNAL] org.freedesktop.DBus.Mock.MethodCalled', 
'Agent registered', 'Controller 00:01:02:03:04:05 my-computer [default]', 
'Agent unregistered', '[\x1b[0;91mDEL\x1b[0m] Controller 00:01:02:03:04:05 
my-computer [default]']

  --

  However the failure only occurs in the Ubuntu package of python-
  dbusmock. It does not occur with the upstream git repo (run as 'tests
  /run-ubuntu-chroot').

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python-dbusmock 0.17-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 11:42:48 2018
  InstallationDate: Installed on 2017-12-12 (68 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  PackageArchitecture: all
  SourcePackage: python-dbusmock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  In Progress

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1719579] Re: [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[ChristianEhrhardt]

Thanks for the full dmesg.
It seems to me that:
"unable to set AppArmor profile 'libvirt-81b387d9-1dfc-4f55-8b98-0318f1f94442'"
means there is an issue in loading the profile after your change.

That matches:
 audit: type=1400 audit(1519028363.683:12417): apparmor="DENIED" 
operation="change_profile" info="label not found" error=-2 
profile="/usr/sbin/libvirtd" 
name="libvirt-81b387d9-1dfc-4f55-8b98-0318f1f94442" pid=12949 comm="libvirtd"

It is not getting to the actual restore, it is failing when spawning the
guest to to the changes in the apparmor profile.

I tried to check what you hit:
$ virsh save bionic-test --file /var/tmp/bionic-test.save --verbose
Guest is shut-off and I have
-rw--- 1 root root 527808329 Feb 19 12:34 /var/tmp/bionic-test.save
The restore hits the (silent) denial we discussed.
   #deny /tmp/{,**} r,  
  
   #deny /var/tmp/{,**} r,
Changed the two lines above to a comment.
Then restored again, just worked:
$ virsh restore /var/tmp/bionic-test.save
Domain restored from /var/tmp/bionic-test.save

To quote jdstrand from bug 1403648:
"We should not allow access to /tmp and /var/tmp as that breaks application 
isolation."

That said we are in the following situation:
1. /tmp and /var/tmp are not allowed to be read (apparmor default for app 
isolation)
2. read denies there are silenced via explicit denies in 
/etc/apparmor.d/abstractions/libvirt-qemu
3. I see your point:
3.1 on save libvirt writes to that place (libvirt is allowed to do so, while 
qemu is not)
3.2 on restore qemu wants to read it and is denied.

And you wonder about the asymetric behavior of 3.1 and 3.2.
I agree that it is somewhat unexpected, but wonder what would be better
1. We could also deny /var /tmp for the lbivirt daemon (which intentionally has 
a rather lenient apparmor profile). Then already on the save people would be 
denied, maybe for a new release - but not as an SRU to not break people relying 
on that access working.
2. And on the new release we already have the --bypass-cache fixes you referred 
to to get the restore working there as a workaround - so the benefit of 
preventing libvirt to access there isn't too big either. So forbidding the 
access on "save" for libvirt there would make that useless.

I'm unsure how to continue. To better brain-storm with you on how to
proceed do you have a clear preferred solution (other than the already
included bypass-cache fixes) or is it just "not nice in general" that
the denial should be consistent for save/restore?


Separate to the discussion above:
To find how your modified apparmor profile breaks your guest start you could 
share it - as I mentioned it worked for me right away (no need to restart 
libvirt after changing btw, the one we change it loaded on guest load).

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

Title:
  [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in
  /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  Fix Released
Status in apparmor package in Ubuntu:
  Invalid
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+:

[Touch-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

Hello ddstreet

I confirmed that glib2.0 patch is needed.

I installed patched_pacemaker only on my system and running just 1 hour.

it started with 4700(RES) but now it is 8000(RES).

after installing glib2.0

it started with 4612, now is is 4688

Thanks

[1] is script to reproduce this issue. need to adjust some code but just
uploading

[1] https://pastebin.ubuntu.com/p/CGrGhjdr4g/

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Touch-packages] [Bug 1750364] [NEW] systemd autopkgtest upstream test cases failing in v237

[Dimitri John Ledkov]

Public bug reported:

TEST-16-EXTEND-TIMEOUT

started to fail, in a nested qemu VM for the casess success_all &
success_start

sed -i 's/wait_for success_all/# wait_for success_all/' 
test/TEST-16-EXTEND-TIMEOUT/assess.sh
sed -i 's/wait_for success_start/# wait_for success_start/' 
test/TEST-16-EXTEND-TIMEOUT/assess.sh
sed -i 's/Wants=testsuite-success-all.service/# 
Wants=testsuite-success-all.service/' 
test/TEST-16-EXTEND-TIMEOUT/testsuite.service
sed -i 's/Wants=testsuite-success-start.service/# 
Wants=testsuite-success-start.service/' 
test/TEST-16-EXTEND-TIMEOUT/testsuite.service

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


** Tags: autopkgtest autopkgtest-fail

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

Title:
  systemd autopkgtest upstream test cases failing in v237

Status in systemd package in Ubuntu:
  New

Bug description:
  TEST-16-EXTEND-TIMEOUT

  started to fail, in a nested qemu VM for the casess success_all &
  success_start

  sed -i 's/wait_for success_all/# wait_for success_all/' 
test/TEST-16-EXTEND-TIMEOUT/assess.sh
  sed -i 's/wait_for success_start/# wait_for success_start/' 
test/TEST-16-EXTEND-TIMEOUT/assess.sh
  sed -i 's/Wants=testsuite-success-all.service/# 
Wants=testsuite-success-all.service/' 
test/TEST-16-EXTEND-TIMEOUT/testsuite.service
  sed -i 's/Wants=testsuite-success-start.service/# 
Wants=testsuite-success-start.service/' 
test/TEST-16-EXTEND-TIMEOUT/testsuite.service

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Francis Ginther]

** Tags added: id-5a8aa637d86af5a17d52e696

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  In Progress

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1746765] Re: systemd FTBFS on arm64

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  systemd FTBFS on arm64

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  Fix Released
Status in gnu-efi package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Released
Status in gnu-efi source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Might be a bug in the toolchain, gnu-efi or systemd.

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Julian Andres Klode]

Fixed in 1.6~alpha7ubuntu2, just uploaded.

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

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1750379] [NEW] Distortion Realtek ALC887

[fleamour]

Public bug reported:

Sounds can distort even when not amplified. Amplification worked well
for years before recent PulseAudio update. The audio is Realtek ALC887
under an IntelG41 Chipset with GA-G41M-Combo main board;

Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

I am seeking to engage upstream for April LTS release. Windows have
abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user going!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  fleamour   1049 F pulseaudio
 /dev/snd/controlC2:  fleamour   1049 F pulseaudio
 /dev/snd/controlC0:  fleamour   1049 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 19 13:54:33 2018
InstallationDate: Installed on 2018-02-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FB
dmi.board.name: G41M-Combo
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G41M-Combo
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1750379

Title:
  Distortion Realtek ALC887

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 982499] Re: dconf-editor always prints warnings: "Unknown property on "

[Bug Watch Updater]

** Changed in: d-conf (Debian)
   Status: New => Incomplete

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

Title:
  dconf-editor always prints warnings: "Unknown property on "

Status in d-conf package in Ubuntu:
  Confirmed
Status in d-conf package in Debian:
  Incomplete

Bug description:
  When I start dconf-editor, these four warnings are logged:

  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown 
property on , extends
  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown 
property on , extends
  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag 

  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag 


  It doesn't seem to affect operations so I'm setting the initial
  importance to "Low".

  This is reproducible for me every time I start dconf-editor from the
  command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/982499/+subscriptions

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ansgar Bohmann]

** Information type changed from Public to Public Security

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system starts successfully
  on battery.

  The user installed a fresh instance of 1

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ansgar Bohmann]

** Information type changed from Public Security to Public

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system starts successfully
  on battery.

  The user installed a fresh instance of 1

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Dimitri John Ledkov]

I think cloud-init is the oracle of information of which ntp daemon to
use, and which ntp servers to use. Thus on bionic+ cloud-init, when
configuring ntp, should also "disable systemd-timesyncd" if some
alternative NTP server is to be used.

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

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the NTP module configures ntpd during cloud-init install by
  installing and configuring ntpd.

  ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
  Xenial.

  Ideally the NTP module should configure systemd-timesyncd where
  present, falling back to ntpd where not present.

  This stops two separate daemons (ntpd and systemd-timesyncd) competing
  with each other to set the time, where systemd-timesyncd (on Ubuntu at
  least) has an internal hardcoded compiled in timeserver to fall back
  on if no timeserver is configured (which is bad, but what can you do).

  The competing timeserver behaviour is invisible when the machine can
  see the net, but logs this error constantly when the machine cannot
  see the net:

  systemd-timesyncd[527]: Timed out waiting for reply from
  91.189.94.4:123 (ntp.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions

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

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Dimitri John Ledkov]

"if some alternative NTP server is to be used." should read "if some
alternative NTP client daemon is to be used." obviously =)

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

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the NTP module configures ntpd during cloud-init install by
  installing and configuring ntpd.

  ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
  Xenial.

  Ideally the NTP module should configure systemd-timesyncd where
  present, falling back to ntpd where not present.

  This stops two separate daemons (ntpd and systemd-timesyncd) competing
  with each other to set the time, where systemd-timesyncd (on Ubuntu at
  least) has an internal hardcoded compiled in timeserver to fall back
  on if no timeserver is configured (which is bad, but what can you do).

  The competing timeserver behaviour is invisible when the machine can
  see the net, but logs this error constantly when the machine cannot
  see the net:

  systemd-timesyncd[527]: Timed out waiting for reply from
  91.189.94.4:123 (ntp.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions

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

[Touch-packages] [Bug 1750396] [NEW] Screen constantly crashes/refreshes

[Otto]

Public bug reported:

I've just reluctantly upgraded to 17.10 and am experiencing an annoying
bug where the display jolts/refreshes randomly once every 10/15 seconds
or so.

Specifically, the screen blacks out, appears for half a second upside-
down, then blacks out again before returning.

It corresponds very closely to the following errors found initially in
syslog:

otto@computer:~$ journalctl /usr/bin/gnome-shell -f -o cat

Window manager warning: Overwriting existing binding of keysym 73 with keysym 
73 (keycode 27).
Failed to apply DRM plane transform 0: Permission denied
Failed to read EDID from 'eDP-1': No such file or directory
Failed to read EDID from 'eDP-1': No such file or directory
Failed to read EDID from 'eDP-1': No such file or directory
WARNING: addSignalMethods is replacing existing [0x55ddb578d5c0 
Gjs_ShowAppsIcon.dash-item-container] connect method
WARNING: addSignalMethods is replacing existing [0x55ddb578d5c0 
Gjs_ShowAppsIcon.dash-item-container] disconnect method
WARNING: addSignalMethods is replacing existing [0x55ddb578d5c0 
Gjs_ShowAppsIcon.dash-item-container] emit method

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 19 15:31:08 2018
DistUpgraded: 2018-02-19 11:42:52,000 ERROR Bad upgrade: 'yakkety' != 'zesty'
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81d2]
InstallationDate: Installed on 2016-11-11 (465 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Notebook
MonitorsUser.xml:
 
 
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=c0b32388-dd3d-4fdd-9490-e2de1250484f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2018-02-19 (0 days ago)
dmi.bios.date: 07/08/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81D2
dmi.board.vendor: HP
dmi.board.version: KBC Version 87.13
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/08/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.13:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Feb 19 12:08:47 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Screen constantly crashes/refreshes

Status in xorg package in Ubuntu:
  New

Bug description:
  I've just reluctantly upgraded to 17.10 and am experiencing an
  annoying bug where the display jolts/refreshes randomly once every
  10/15 seconds or so.

  Specifically, the screen blacks out, appears for half a second upside-
  down, then blacks out again before returning.

  It corresponds very closely to the following errors found initially in
  syslog:

  otto@computer:~$ journalctl /usr/bin/gnome-shell -f -o cat

  Window manager warning: Overwriting existing bindin

Re: [Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Ryan Harper]

On Mon, Feb 19, 2018 at 9:33 AM, Dimitri John Ledkov  wrote:

> I think cloud-init is the oracle of information of which ntp daemon to
> use, and which ntp servers to use. Thus on bionic+ cloud-init, when
> configuring ntp, should also "disable systemd-timesyncd" if some
> alternative NTP server is to be used.
>

I'm not opposed to having cloud-init do that.  But systemd and ntp clients
are
installable outside of cloud images and they should behave consistently
there.
I think a combination of the override which prevents timesyncd from
starting if a client
is present *and* the Conflicts= that's present in Bionic should be in the
packaging.

Such a configuration would prevent timesyncd starting from stopping other
clients.


> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1749722
>
> Title:
>   NTP: take into account systemd-timesyncd where present
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions
>

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

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the NTP module configures ntpd during cloud-init install by
  installing and configuring ntpd.

  ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
  Xenial.

  Ideally the NTP module should configure systemd-timesyncd where
  present, falling back to ntpd where not present.

  This stops two separate daemons (ntpd and systemd-timesyncd) competing
  with each other to set the time, where systemd-timesyncd (on Ubuntu at
  least) has an internal hardcoded compiled in timeserver to fall back
  on if no timeserver is configured (which is bad, but what can you do).

  The competing timeserver behaviour is invisible when the machine can
  see the net, but logs this error constantly when the machine cannot
  see the net:

  systemd-timesyncd[527]: Timed out waiting for reply from
  91.189.94.4:123 (ntp.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[Gunnar Hjalmarsson]

Thanks!

I changed the source tree path of the template in Rosetta from build-
deb/po/systemd.pot to po/systemd.pot.

Let's follow up it when systemd 237-4 has been built on Ubuntu.

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
   Status: New => In Progress

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  Fix Released
Status in Ubuntu Translations:
  In Progress
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ansgar Bohmann]

(Sorry for accidentally hitting the wrong button earlier.)

Same problem here on a fresh installation of Xubuntu 17.10 on a Tuxedo
Book BU1406 (with Tuxedo-modifications tuxedo.sh ).

Storage:
1 × M.2 SSD: 250 GB Samsung 960 EVO (/dev/nvme0n1).
1 × SATA III HDD: 1 TB Seagate Thin / 5400 rpm / 2.5" (/dev/sda).

Disk encryption with LUKS, dm-crypt and LVM are active.

The workaround from #15 seems to do the trick.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd

[Touch-packages] [Bug 789479]

[PJBrs]

I can confirm for wine-3.0.

I just overwrote the wine font with its Microsoft counterparts, and now
bullets in pdf documents no longer appear as infinity signs.

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

Title:
  Improper encoding of the "Symbol" font

Status in Wine:
  New
Status in poppler package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released
Status in wine1.3 package in Ubuntu:
  Fix Released

Bug description:
  The characters 'm' and 'p' are mapped to wrong glphys in the base-14
  font "Symbol". This problem has not occurred in maverick.

  I'm attaching a pdf-file that uses all base-14 fonts without embedding
  them, and screenshots from maverick and natty. Note the differences in
  the 5th word in the "Symbol" line. The screenshots were made in
  TeXworks which is based on poppler-qt4 (evince in natty gives the same
  result as TeXworks, but I don't have a maverick-screenshot of it at
  hand).

  $ lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  $apt-cache policy libpoppler-qt4-3 
  libpoppler-qt4-3:
Installed: 0.16.4-0ubuntu1.1
Candidate: 0.16.4-0ubuntu1.1
Version table:
   *** 0.16.4-0ubuntu1.1 0
  500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ 
natty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.16.4-0ubuntu1 0
  500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ natty/main 
amd64 Packages

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

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

[Touch-packages] [Bug 1750405] Re: perl crashed with SIGABRT in _dbus_abort()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1743216, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1750405/+attachment/5058239/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1750405/+attachment/5058241/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1750405/+attachment/5058246/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1750405/+attachment/5058247/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1750405/+attachment/5058248/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1750405/+attachment/5058249/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1750405/+attachment/5058250/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1743216

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in perl package in Ubuntu:
  New

Bug description:
  absolutely no idea why perl was called and what it was doing

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-4build1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb 19 10:48:22 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/perl
  InstallationDate: Installed on 2018-02-14 (5 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  Signal: 6
  SourcePackage: perl
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so
   Perl_pp_entersub ()
  Title: perl crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ritesh Raj Sarraf]

That's because what I instructed in #15 makes laptop-mode-tools
ineffective to USB hotplug events. Not something that a user would want.

As I see from the reports, this is what I think is happening.

1) Users have some combination of usb devices, getting hotplugged upon 
discovery.
2) Step 1 results in early invocation of LMT.
3) Which further results in file systems getting ro mounted. This step is still 
erratic and I have no clue what the calling parent is, to this ro mount.

For users who've confirmed that #15 in the workaround works.
Can you please apply the workaround, successfully boot, then change back the 
changes to its original, and then hotplug a USB device ?
This will trigger the same chain of events, just that they'll be triggered upon 
full boot. Which should give us some insight into what may actually be behaving 
erratic.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23

[Touch-packages] [Bug 1750410] [NEW] display lock up if addition display not present

[Pietro A. Barbieri]

Public bug reported:

display lock up if addition display not present

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.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb 19 12:07:50 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fb]
 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00fc]
InstallationDate: Installed on 2018-02-16 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Apple Inc. MacBookPro9,1
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.efi.signed 
root=UUID=4e57a30a-5941-45af-b5d4-53ee5dd4a074 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D3.B0B.1506081214
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-4B7AC7E43945597E
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-4B7AC7E43945597E
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B0B.1506081214:bd06/08/2015:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Mon Feb 19 12:01:37 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)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  display lock up if addition display not present

Status in xorg package in Ubuntu:
  New

Bug description:
  display lock up if addition display not present

  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.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb 19 12:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fb]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00fc]
  InstallationDate: Installed on 2018-02-16 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Apple Inc. MacBookPro9,1
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.6~alpha7ubuntu2

---
apt (1.6~alpha7ubuntu2) bionic; urgency=medium

  [ David Kalnischkies ]
  * allow the apt/lists/auxfiles/ directory to be missing (Closes: 887624)

  [ Julian Andres Klode ]
  * indexcopy: Copy uncompressed indices from cdrom again (LP: #1746807)

 -- Julian Andres Klode   Mon, 19 Feb 2018 14:43:47
+0100

** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1746807

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1729357] Re: unprivileged user can drop supplementary groups

[Aleksa Sarai]

https://github.com/shadow-maint/shadow/pull/99 includes the
allow_setgroups/deny_setgroups feature that we discussed earlier.

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

Title:
  unprivileged user can drop supplementary groups

Status in shadow package in Ubuntu:
  Confirmed
Status in shadow package in openSUSE:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04.3 LTS
  Kernel: 4.4.0-97-generic
  uidmap package version: 1:4.2-3.1ubuntu5.3

  The newgidmap setuid executable allows any user to write a single
  mapping line to the gid_map of a process whose identity is the same as
  the calling process, as long as that mapping line maps the process's
  own GID outside of the user namespace to GID 0 inside the user
  namespace.

  Newgidmap will write the mapping regardless of the content of
  /proc/$process_being_mapped/setgroups, which will initially contain
  the string "allow". After this mapping is performed, and also after
  the process' uid_map is written with newuidmap, the process in the
  user namespace will be able to use the setgroups system call to drop
  supplementary groups.

  This is possible even if there is no entry for the user in
  /etc/subgid, because no subordinate GIDs are actually being used.

  This allows any user to circumvent the use of supplementary groups as
  blacklists, e.g. for some file owned by root:blacklist with permission
  bits 0604 (octal). Normally any process whose identity included the
  group "blacklist" in its supplementary groups would not be able to
  read that file. By performing this exploit using newgidmap, they can
  drop all supplementary groups and read that file.

  If newgidmap was not available, unprivileged users would not be able
  to write a process's gid_map until writing "deny" to
  /proc/$pid/setgroups. A fix for this might be for newgidmap to check
  the content of /proc/$process_being_mapped/setgroups is "deny", but we
  have not tried to patch this ourselves.

  An example using 2 login shells for a user named "someone" on Ubuntu
  Xenial, with the uidmap package installed:

  Shell 1

  someone@ubuntu-xenial:~$ id
  uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted)

  someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict
  -rwr-- 1 root restricted 8 Nov  1 12:23 /tmp/should_restrict

  someone@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  someone@ubuntu-xenial:~$ unshare -U --setgroups allow #
  /proc/self/setgroups already contains 'allow', but let's be explicit

  nobody@ubuntu-xenial:~$ echo $$
  1878

  Shell 2

  someone@ubuntu-xenial:~$ cat /etc/subuid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  someone@ubuntu-xenial:~$ cat /etc/subgid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  # There are no entries in /etc/sub{u,g}id for someone, but this
  doesn't matter that much as subordinate IDs are not being requested.

  someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1

  someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1

  Back to shell 1

  nobody@ubuntu-xenial:~$ id
  uid=0(root) gid=0(root) groups=0(root),65534(nogroup)

  # The presence of the "nogroup" supplementary group indicates that
  some unmapped GIDs are present as supplementary GIDs. The kernel knows
  that this process still has "restricted" in its supplementary groups,
  so it can't read the restricted file yet.

  nobody@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  # The process has gained CAP_SETGID in its user namespace by becoming
  UID 0. /proc/$pid/setgroups contains "allow", so it can call
  setgroups(2). By su-ing to root (itself, in the user namespace), it
  can drop the supplementary groups. It can't read /root/.bashrc as that
  file is owned by UID 0 in the initial user namespace, which creates
  some distracting error output but doesn't matter in this case.

  nobody@ubuntu-xenial:~$ su root
  su: Authentication failure
  (Ignored)
  bash: /root/.bashrc: Permission denied

  # Supplementary groups have been dropped

  root@ubuntu-xenial:~# id
  uid=0(root) gid=0(root) groups=0(root)

  # It can read the restricted file

  root@ubuntu-xenial:~# cat /tmp/should_restrict
  content

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Simon Quigley]

I just manually triggered a rebuild for Lubuntu Alternate since this
landed, and after that, things should be good.

Thanks everyone!

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1750411] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit stat

[Ben Glanton]

Public bug reported:

No observed failure in user space - but I got a pop-up warning, so here
we go...

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 gcc-7-base:i386: Install
 libgcc1:i386: Install
 libc6:i386: Install
 libssl1.0.0:i386: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Feb 19 17:40:49 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-06-19 (245 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 172.26.45.1 dev enx8cae4cf6075e proto static metric 100 
 169.254.0.0/16 dev enx8cae4cf6075e scope link metric 1000 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 172.26.45.0/24 dev enx8cae4cf6075e proto kernel scope link src 172.26.45.67 
metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: Upgraded to artful on 2018-02-19 (0 days ago)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 docker0  bridgeconnected
/org/freedesktop/NetworkManager/Devices/4  docker0 
7cea7338-7829-47c6-979a-8ffd94d5819d  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 enx8cae4cf6075e  ethernet  connected
/org/freedesktop/NetworkManager/Devices/3  Wired connection 2  
0b257ca3-b031-4a10-b4ec-319e8c4fcd2b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 wlp58s0  wifi  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
 lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  No observed failure in user space - but I got a pop-up warning, so
  here we go...

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   gcc-7-base:i386: Install
   libgcc1:i386: Install
   libc6:i386: Install
   libssl1.0.0:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb 19 17:40:49 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-06-19 (245 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 172.26.45.1 dev enx8cae4cf6075e proto static metric 100 
   169.254.0.0/16 dev enx8cae4cf6075e scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.26.45.0/24 dev enx8cae4cf6075e proto kernel scope link src 172.26.45.67 
metric 100
  NetworkManager.state:
   [main]
   Networ

[Touch-packages] [Bug 1750157] Re: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Emily Ratliff]

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

** This bug has been marked a duplicate of bug 1385817
   initscripts package fails to upgrade if there are local init scripts on the 
system with no LSB headers

** Information type changed from Private Security to Public

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

Title:
  package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  My wifi gets disconnect again and again in short time of interval

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Feb 16 20:50:26 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-16 (915 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-26 (539 days ago)

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

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

[Touch-packages] [Bug 1750154] Re: grafika

[Emily Ratliff]

** Information type changed from Private Security to Public

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

Title:
  grafika

Status in xorg package in Ubuntu:
  New

Bug description:
  bad repo and zawiesza sie

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Feb 17 16:00:06 2018
  DistUpgraded: 2018-02-17 11:31:49,932 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:1401]
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 001 Device 004: ID 05e3:070e Genesys Logic, Inc. USB 2.0 Card Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 413c:2101 Dell Computer Corp. SmartCard Reader 
Keyboard
   Bus 002 Device 009: ID :0538  
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M61SME-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-35-generic 
root=UUID=daf44daf-c1c8-4605-87c3-2306d5c5513a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (0 days ago)
  dmi.bios.date: 07/15/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: M61SME-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd07/15/2008:svnGigabyteTechnologyCo.,Ltd.:pnM61SME-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM61SME-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M61SME-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Feb 17 15:34:18 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)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output DVI-I-1   
VGA-1
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1747711] Re: file mis-identifies modern executables as application/x-sharedlib

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  file mis-identifies modern executables as application/x-sharedlib

Status in file package in Ubuntu:
  New

Bug description:
  file doesn't recognize modern PIE (Position Independent Executable)
  x86 executables as such, reporting them as “application/x-sharedlib”.
  Consequently, only non-PIE executables can be opened in graphical file
  managers such as nautilus. This may cause a minor (?) security risk if
  a commonly-published workaround is attempted.

  Expected behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-executable

  Actual behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-sharedlib

  Workaround (unsafe?):

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo-nopie foo.c -no-pie
  $ file foo-nopie
  foo-nopie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=3eb8c581f43c19997e3c828f5a9730dbdc794470, not stripped
  $ file --mime-type foo-nopie
  foo-nopie: application/x-executable

  gcc now defaults to building with PIE enabled for security reasons.

  Also affects: nautilus (and likely other graphical file managers like
  those on Lubuntu) - because nautilus uses mime-type to determine if a
  file is executable, double-click to run a program no longer works.

  Also noted on: Gnome Bugs -
  https://bugzilla.gnome.org/show_bug.cgi?id=737849 (2014) - before PIE
  became the default build option.

  This may be an upstream issue. This may not affect architectures
  outside x86.*

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: file 1:5.32-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb  6 11:21:20 2018
  InstallationDate: Installed on 2017-05-11 (270 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: file
  UpgradeStatus: Upgraded to artful on 2017-10-21 (108 days ago)

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

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

[Touch-packages] [Bug 1749149] Re: Frezze of my ubuntu 17.10

[Emily Ratliff]

** Information type changed from Private Security to Public

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

Title:
  Frezze of my ubuntu 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  while watching video it frezzes my full laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 15:43:26 2018
  DistUpgraded: 2017-12-08 18:23:43,105 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   anbox-modules-ashmem, 9~zesty1, 4.13.0-19-generic, x86_64: installed
   anbox-modules-ashmem, 9~zesty1, 4.13.0-32-generic, x86_64: installed
   anbox-modules-binder, 9~zesty1, 4.13.0-19-generic, x86_64: installed
   anbox-modules-binder, 9~zesty1, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:06b0]
  InstallationDate: Installed on 2017-01-18 (391 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3558
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=1084155d-0138-4d5d-a47a-091b41af6441 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-12-08 (66 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0XCR91
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1748909] Re: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Emily Ratliff]

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

** This bug has been marked a duplicate of bug 1628868
   package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

** Information type changed from Private Security to Public

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

Title:
  package udev 229-4ubuntu10 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  No other errors to report

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Feb 11 19:14:59 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-11  19:14:48
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: thunderbird-gnome-support:amd64 (1:52.5.0+build1-0ubuntu0.16.04.1, 
1:52.6.0+build1-0ubuntu0.16.04.1), thunderbird-locale-en-us:amd64 
(1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1), 
libwebkit2gtk-4.0-37:amd64 (2.18.5-0ubuntu0.16.04.1, 2.18.6-0ubuntu0.16.04.1), 
thunderbird:amd64 (1:52.5.0+build1-0ubuntu0.16.04.1, 
1:52.6.0+build1-0ubuntu0.16.04.1), gir1.2-webkit2-4.0:amd64 
(2.18.5-0ubuntu0.16.04.1, 2.18.6-0ubuntu0.16.04.1), 
libjavascriptcoregtk-4.0-18:amd64 (2.18.5-0ubuntu0.16.04.1, 
2.18.6-0ubuntu0.16.04.1), thunderbird-locale-en:amd64 
(1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1), 
libwebkit2gtk-4.0-37-gtk2:amd64 (2.18.5-0ubuntu0.16.04.1, 
2.18.6-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:amd64 
(2.18.5-0ubuntu0.16.04.1, 2.18.6-0ubuntu0.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-24 (506 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. XPS 12 9Q23
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=850f95ab-9dbc-452d-9b61-44c426778782 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: systemd
  Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 011Y0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/01/2013:svnDellInc.:pnXPS129Q23:pvrA08:rvnDellInc.:rn011Y0K:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS 12 9Q23
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1749036] Re: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed in

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all
  1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which
  has multiple installed instances

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  This happened during a partial upgrade of Bionic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcomerr2 1.43.8-2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb 12 15:51:57 2018
  Dependencies:
   gcc-7-base 7.2.0-18ubuntu2
   libc6 2.26-0ubuntu2
   libgcc1 1:7.2.0-18ubuntu2
  DpkgTerminalLog:
   Preparing to unpack .../comerr-dev_2.1-1.43.9-1_amd64.deb ...
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  DuplicateSignature:
   package:libcomerr2:1.43.8-2
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  ErrorMessage: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable 
with libcomerr2 which has multiple installed instances
  InstallationDate: Installed on 2013-01-16 (1853 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: e2fsprogs
  Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 
1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has 
multiple installed instances
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750421] [NEW] package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado

[Leonardo Müller]

Public bug reported:

Hi

I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this
post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4

When libfontconfig-dev:amd64 tried to update it failed. I tried again
and it failed again, then I opened synaptic and noticed that the
libfontconfig-dev:i386 was already updated to the last version. After
the i386 version was purged, the amd64 version could be updated and the
upgrade finished.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfontconfig1-dev 2.12.6-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Mon Feb 19 14:38:06 2018
ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
InstallationDate: Installed on 2017-06-13 (250 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu2
SourcePackage: fontconfig
Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a 
tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

** Affects: fontconfig (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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1750421

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-
  devel.pdf.gz' partilhado, que é diferente de outras instâncias do
  pacote libfontconfig1-dev:amd64

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi

  I "upgraded" from Xubuntu 17.10 to 18.04 using the information from
  this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4

  When libfontconfig-dev:amd64 tried to update it failed. I tried again
  and it failed again, then I opened synaptic and noticed that the
  libfontconfig-dev:i386 was already updated to the last version. After
  the i386 version was purged, the amd64 version could be updated and
  the upgrade finished.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 14:38:06 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  InstallationDate: Installed on 2017-06-13 (250 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

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

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

[Touch-packages] [Bug 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades

[Gunnar Hjalmarsson]

The new string is currently untranslated in most languages including
German, but that's a regular condition and does not motivate a bug
report. Dropping the Ubuntu Translations bug task.

** No longer affects: ubuntu-translations

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

Title:
  Wrong/confuse text on shutdown at unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades-0.90ubuntu0.9
  Uname: 4.4.0-104-generic #127-Ubuntu SMP
  Architecture: amd64

  I've german systems, so when updates will be installed at shutdown
  this text will be displayed at the screen.

  German:
  "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf 
Sekunden lange gewartet"

  English:
  "unattended upgrade runs during the shutdown, it waits for five seconds"

  This sentence make absolutly no sence for me. Maybe it is an 
translationproblem? Don't know text on the english ubuntuversion. 
  The problem is that some customer turned of some computers, because the 
updates need more time then 5 seconds ;)

  A better message will that was Windows10 displays at shutdown ...don't
  turn off the computer, updates will be installed...

  Thanks and best Reagards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1741579/+subscriptions

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

[Touch-packages] [Bug 1750421] Re: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado,

[Leonardo Müller]

** Description changed:

  Hi
  
  I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this
  post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4
  
- When libfontconfig-dev:amd64 tried to update it failed. I tried again
+ When libfontconfig1-dev:amd64 tried to update it failed. I tried again
  and it failed again, then I opened synaptic and noticed that the
- libfontconfig-dev:i386 was already updated to the last version. After
+ libfontconfig1-dev:i386 was already updated to the last version. After
  the i386 version was purged, the amd64 version could be updated and the
  upgrade finished.
  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 14:38:06 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  InstallationDate: Installed on 2017-06-13 (250 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
-  dpkg 1.19.0.5ubuntu1
-  apt  1.6~alpha7ubuntu2
+  dpkg 1.19.0.5ubuntu1
+  apt  1.6~alpha7ubuntu2
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

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

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-
  devel.pdf.gz' partilhado, que é diferente de outras instâncias do
  pacote libfontconfig1-dev:amd64

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi

  I "upgraded" from Xubuntu 17.10 to 18.04 using the information from
  this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4

  When libfontconfig1-dev:amd64 tried to update it failed. I tried again
  and it failed again, then I opened synaptic and noticed that the
  libfontconfig1-dev:i386 was already updated to the last version. After
  the i386 version was purged, the amd64 version could be updated and
  the upgrade finished.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 14:38:06 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  InstallationDate: Installed on 2017-06-13 (250 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Jb]

Glad this fix is in the pipeline.  :)

Thank you.

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Jb]

I tried 20180219.1 but that must before the rebuild as it still had
1.6~alpha7ubuntu1.

I'll re-test again when the version changes.

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1747783] Re: Software & Updates > Other software can not authenticate to allow changes

[Doug McMahon]

Fixed in 18.04 so marking invalid

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

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

Title:
  Software & Updates > Other software can not authenticate to allow
  changes

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  Test case:
  Open Software & Updates, click on Other Software tab
  Try to check or un-check any listing

  What happens: Nothing, though one is prompted to reload after..

  Now go to main tab, make any change that requires auth. Enter password.
  Return to Other Software tab, now clicking on a listing does have affect.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.19
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 18:04:40 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1747783/+subscriptions

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

[Touch-packages] [Bug 1750433] [NEW] fatal error launching grub

[John A Peters]

Public bug reported:

Somehow a beta version of grub is installed.  I get a long list of code
on startup and get a black and white box with a -e option. nothing works

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.376
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb 19 20:34:28 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0309
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-A/USB 3.1
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Feb 19 20:33:15 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  fatal error launching grub

Status in xorg package in Ubuntu:
  New

Bug description:
  Somehow a beta version of grub is installed.  I get a long list of
  code on startup and get a black and white box with a -e option.
  nothing works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb 19 20:34:28 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0309
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A

[Touch-packages] [Bug 1628868] Re: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dimitri John Ledkov]

There appears to be an init.d scripts loop between cups & plymouth


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

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

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

Title:
  package udev 229-4ubuntu10 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in cups package in Ubuntu:
  New
Status in plymouth package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Устанавливал Kodi. После этого попытался его обновить. И при
  обновлении ошибки сыплются.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 29 11:17:56 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-10 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80HW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B6CN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G70-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G70-70
  dmi.modalias: 
dmi:bvnLENOVO:bvrB6CN16WW:bd07/20/2015:svnLENOVO:pn80HW:pvrLenovoG70-70:rvnLENOVO:rnLenovoG70-70:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG70-70:
  dmi.product.name: 80HW
  dmi.product.version: Lenovo G70-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup

[Curtis Schroeder]

I am running Ubuntu 14.04.5 LTS and the offset parameter to preserve the
UUID simply does not work for me. A later version of Ubuntu on the same
PC shows there is a PARTUUID for the encrypted swap partition, but this
is not visible in 14.04. The UUID for the cryptswap partition is always
lost after reboot of 14.04.

Reverting back to using a device ID in conjunction with the solution in
Comment #22 works, but I would like to add an additional piece of
helpful information. I have a multi-disk system and periodically the
/dev/sd_ drive IDs re-order themselves. Normally, UUIDs would solve this
problem, but we can't use a UUID in this instance. This post pointed me
in the direction of a solution
(https://gebloggendings.wordpress.com/2016/06/14/cryptsetup-
etccrypttab-a-workaround-for-gpt-partuuid-support/). Turns out you can
use the /dev/disk/by-id alias for the partition ID in /etc/crypttab, as
these drive IDs are also unique, i.e. drive make, model & serial number.

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

Title:
  Encrypted swap no longer mounted at bootup

Status in eCryptfs:
  Fix Released
Status in systemd:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Trusty:
  Triaged
Status in ubiquity source package in Trusty:
  Triaged
Status in ecryptfs-utils source package in Vivid:
  Fix Released
Status in systemd source package in Vivid:
  Fix Released
Status in ubiquity source package in Vivid:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  SUMMARY
  ===
  During installation with "encrypt my home folder" mode, a broken 
/etc/crypttab gets created which defines a non-existing swap device (usually 
"cryptswap1") with a UUID. This will also be put into /etc/fstab. As after 
installation the UUID does not exist, such systems don't have any actual swap.

  UPGRADE FIX
  ===
  An upgrade to Ubuntu 15.04 ("vivid") will detect and comment out these broken 
swap devices from /etc/fstab and /etc/crypttab. If you actually want  to use 
those, do these steps:

   - Find the swap device that was meant to be used in "sudo fdisk -l" (it 
should say "Linux swap" in the last column), remember the device name 
(something like "/dev/sda5")
   - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=)
   - Run "sudo mkswap -U 1234... /dev/sda5", replacing "1234" with the above 
UUID, and /dev/sda5 with the device name from step 1.
   - Edit /etc/crypttab to append ",offset=1024" in the fourth (last) column of 
the cryptswap1 line; ensure that there is *no space* between the 
"cipher=aes-cbc-essiv:sha256" and the appended option. If there is a leading 
"#" in the file, remove that too.
   - If there is a leading "#" in /etc/fstab in the line starting with 
/dev/mapper/cryptswap1 line, remove that.
   - Run "sudo update-initramfs -u".

  
  ORIGINAL REPORT
  ===

  Clean install of 12.04 and with encrypted home for my user. Did all
  updates and now the bootup hangs waiting for swap to become available
  and it never seems to ever finish. The 200GB SSD below is my boot
  drive and root filesystem.

  alan@mesh:~$ sudo swapon -a
  [sudo] password for alan:
  swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory

  alan@mesh:~$ grep swap /etc/fstab
  # swap was on /dev/sdg5 during installation
  #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 
 0   0
  /dev/mapper/cryptswap1 none swap sw 0 0

  alan@mesh:~$ sudo fdisk -l

  Disk /dev/sda: 115.0 GB, 115033153536 bytes
  255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x000ba2ed

     Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  206847  1024007  HPFS/NTFS/exFAT
  /dev/sda2  206848   224671743   1122324487  HPFS/NTFS/exFAT

  Disk /dev/sdb: 200.0 GB, 200049647616 bytes
  255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xf0fa0806

     Device Boot  Start End  Blocks   Id  System
  /dev/sdb12048   349304831   1746513927  HPFS/NTFS/exFAT
  /dev/sdb2   374722558   390721535 79994895  Extended
  /dev/sdb3   *   349304832   37472051112707840   83  Linux
  /dev/sdb5   374722560   390721535 7999488   82  Linux swap / Solaris

  Partition table entries are not in 

[Touch-packages] [Bug 1615856] Re: cannnot set phase2 peap auth to none

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  cannnot set phase2 peap auth to none

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In my university, they use PEAP auth, with no certificate and phase 2 
authentication set to none.
  On windows and android I am able to set this, however network-manager offers 
no such option, and I cant connect to that network.

  I have tried to work around using this:
  https://ubuntuforums.org/showthread.php?t=1726522
  However I could not make it to work.

  
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  network-manager:
Installed: 1.2.0-0ubuntu0.16.04.3
Candidate: 1.2.0-0ubuntu0.16.04.3
Version table:
   *** 1.2.0-0ubuntu0.16.04.3 500
  500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615856/+subscriptions

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

[Touch-packages] [Bug 1615856] Re: cannnot set phase2 peap auth to none

[Jan Vlug]

See also: https://bugzilla.gnome.org/show_bug.cgi?id=773126

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

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

Title:
  cannnot set phase2 peap auth to none

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In my university, they use PEAP auth, with no certificate and phase 2 
authentication set to none.
  On windows and android I am able to set this, however network-manager offers 
no such option, and I cant connect to that network.

  I have tried to work around using this:
  https://ubuntuforums.org/showthread.php?t=1726522
  However I could not make it to work.

  
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  network-manager:
Installed: 1.2.0-0ubuntu0.16.04.3
Candidate: 1.2.0-0ubuntu0.16.04.3
Version table:
   *** 1.2.0-0ubuntu0.16.04.3 500
  500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615856/+subscriptions

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

[Touch-packages] [Bug 1750453] [NEW] Apt does not ask for authentication unless sudo is specified

[Harald H.]

Public bug reported:

If a user try to install for example Gimp with "apt install gimp"
(without sudo) he will be met with these errors:

E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

If the software is available as a snap and he instead tries to install
it with "snap install gimp" (still without sudo) he won't get any
errors, but will instead be prompted for the sudo password. This is
pretty neat, but is there somehow we can have this same function when
using apt to make the behavior consistent?

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

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

Title:
  Apt does not ask for authentication unless sudo is specified

Status in apt package in Ubuntu:
  New

Bug description:
  If a user try to install for example Gimp with "apt install gimp"
  (without sudo) he will be met with these errors:

  E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
  E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

  If the software is available as a snap and he instead tries to install
  it with "snap install gimp" (still without sudo) he won't get any
  errors, but will instead be prompted for the sudo password. This is
  pretty neat, but is there somehow we can have this same function when
  using apt to make the behavior consistent?

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

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

[Touch-packages] [Bug 1750454] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1745797, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1750454/+attachment/5058467/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1750454/+attachment/5058469/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1750454/+attachment/5058472/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1750454/+attachment/5058473/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1750454/+attachment/5058474/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1750454/+attachment/5058475/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1750454/+attachment/5058476/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1745797

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  i do not know nothing more all was automatically informed

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.26.5-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 23:43:58 2018
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2018-02-11 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180129)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_weak_ref_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_clear () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libedataserver-1.2.so.22
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1739532] Re: apport-collect SHOULD prune out /home/%USER/ from JournalErrors

[Brian Murray]

** Tags added: vionic

** Tags removed: vionic
** Tags added: bionic

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

Title:
  apport-collect SHOULD prune out /home/%USER/ from JournalErrors

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  During https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525, I ran apport-collect.

  I was happy to see that my hostname from the system logs was pruned to
  "hostname". Great!

  However, there are some logs that complain about /home/FOO user ... we
  SHOULD NOT leak a user's $HOME directory contents (a potential list of
  local user accounts) into these reports. This MAY be considered as
  sensitive information.

  The JournalErrors.txt should prune it.

  Example of CULPRITS:
  {{{
  Dec 20 21:39:20 hostname com.ubuntu.OneConf[3069]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/FOO/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts'
  Dec 20 21:39:33 hostname com.ubuntu.OneConf[18688]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/BAR/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts'
  }}}

  The suggestion here, is simply to also prune out usernames from ANY
  "/home/%USER" or "~%USER" type regexes.

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

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

[Touch-packages] [Bug 1739532] Re: apport-collect SHOULD prune out /home/%USER/ from JournalErrors

[Brian Murray]

I recently modified apport so JournalErrors.txt actually consists of
errors and not also warnings and I believe that resolves this specific
issue although we could do a better job of searching for and replacing
user home directory names.

apport (2.20.8-0ubuntu9) bionic; urgency=medium

  * data/general-hooks/generic.py: change JournalErrors to contain errors not
warnings. (LP: #1738581)

** Changed in: apport (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  apport-collect SHOULD prune out /home/%USER/ from JournalErrors

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  During https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525, I ran apport-collect.

  I was happy to see that my hostname from the system logs was pruned to
  "hostname". Great!

  However, there are some logs that complain about /home/FOO user ... we
  SHOULD NOT leak a user's $HOME directory contents (a potential list of
  local user accounts) into these reports. This MAY be considered as
  sensitive information.

  The JournalErrors.txt should prune it.

  Example of CULPRITS:
  {{{
  Dec 20 21:39:20 hostname com.ubuntu.OneConf[3069]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/FOO/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts'
  Dec 20 21:39:33 hostname com.ubuntu.OneConf[18688]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/BAR/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts'
  }}}

  The suggestion here, is simply to also prune out usernames from ANY
  "/home/%USER" or "~%USER" type regexes.

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

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

[Touch-packages] [Bug 1750474] Re: package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/ch

[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 kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1750474

Title:
  package libkmod2 22-1ubuntu5 [modified:
  usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from
  other instances of package libkmod2:i386

Status in kmod package in Ubuntu:
  New

Bug description:
  I'm not sure if this is a new bug or not but I haven't been able to
  install new software for quite some time.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libkmod2 22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Feb 19 19:31:53 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2018-02-19  19:31:46
   Commandline: apt-get -f install
   Requested-By: robert (1000)
   Install: libkmod2:i386 (22-1ubuntu5, automatic)
   Upgrade: udev:amd64 (229-4ubuntu19, 229-4ubuntu21.1), libudev1:amd64 
(229-4ubuntu19, 229-4ubuntu21.1), libudev1:i386 (229-4ubuntu19, 
229-4ubuntu21.1), libudev-dev:i386 (229-4ubuntu19, 229-4ubuntu21.1)
  DpkgTerminalLog:
   Preparing to unpack .../libkmod2_22-1ubuntu5_i386.deb ...
   Unpacking libkmod2:i386 (22-1ubuntu5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
  DuplicateSignature:
   package:libkmod2:22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
   Unpacking libkmod2:i386 (22-1ubuntu5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
  InstallationDate: Installed on 2017-03-28 (328 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: kmod
  Title: package libkmod2 22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is 
different from other instances of package libkmod2:i386
  UpgradeStatus: Upgraded to xenial on 2017-07-05 (229 days ago)

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

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

[Touch-packages] [Bug 1750474] [NEW] package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/

[Robert Joyner]

Public bug reported:

I'm not sure if this is a new bug or not but I haven't been able to
install new software for quite some time.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libkmod2 22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Feb 19 19:31:53 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
DpkgHistoryLog:
 Start-Date: 2018-02-19  19:31:46
 Commandline: apt-get -f install
 Requested-By: robert (1000)
 Install: libkmod2:i386 (22-1ubuntu5, automatic)
 Upgrade: udev:amd64 (229-4ubuntu19, 229-4ubuntu21.1), libudev1:amd64 
(229-4ubuntu19, 229-4ubuntu21.1), libudev1:i386 (229-4ubuntu19, 
229-4ubuntu21.1), libudev-dev:i386 (229-4ubuntu19, 229-4ubuntu21.1)
DpkgTerminalLog:
 Preparing to unpack .../libkmod2_22-1ubuntu5_i386.deb ...
 Unpacking libkmod2:i386 (22-1ubuntu5) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
DuplicateSignature:
 package:libkmod2:22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
 Unpacking libkmod2:i386 (22-1ubuntu5) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
InstallationDate: Installed on 2017-03-28 (328 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: kmod
Title: package libkmod2 22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is 
different from other instances of package libkmod2:i386
UpgradeStatus: Upgraded to xenial on 2017-07-05 (229 days ago)

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


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package libkmod2 22-1ubuntu5 [modified:
  usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from
  other instances of package libkmod2:i386

Status in kmod package in Ubuntu:
  New

Bug description:
  I'm not sure if this is a new bug or not but I haven't been able to
  install new software for quite some time.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libkmod2 22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Feb 19 19:31:53 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2018-02-19  19:31:46
   Commandline: apt-get -f install
   Requested-By: robert (1000)
   Install: libkmod2:i386 (22-1ubuntu5, automatic)
   Upgrade: udev:amd64 (229-4ubuntu19, 229-4ubuntu21.1), libudev1:amd64 
(229-4ubuntu19, 229-4ubuntu21.1), libudev1:i386 (229-4ubuntu19, 
229-4ubuntu21.1), libudev-dev:i386 (229-4ubuntu19, 229-4ubuntu21.1)
  DpkgTerminalLog:
   Preparing to unpack .../libkmod2_22-1ubuntu5_i386.deb ...
   Unpacking libkmod2:i386 (22-1ubuntu5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
  DuplicateSignature:
   package:libkmod2:22-1ubuntu5 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
   Unpacking libkmod2:i386 (22-1ubuntu5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
  InstallationDate: Installed on 2017-03-28 (

[Touch-packages] [Bug 1750475] [NEW] atualização

[Jose Acacio]

Public bug reported:

quando instalei compiz

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb 19 21:23:34 2018
DistUpgraded: 2018-02-03 00:15:21,540 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho 
“./xorg_fix_proprietary.py” (Arquivo ou diretório não encontrado) (8))
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
InstallationDate: Installed on 2017-06-04 (260 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=c11a0bb6-5ab4-4b2c-af3b-b92bc7ac4a87 ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2018-02-03 (16 days ago)
dmi.bios.date: 05/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41T-M LX3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Feb 19 21:15:03 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Optical Mouse MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful compiz-0.9 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/1750475

Title:
  atualização

Status in xorg package in Ubuntu:
  New

Bug description:
  quando instalei compiz

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb 19 21:23:34 2018
  DistUpgraded: 2018-02-03 00:15:21,540 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho 
“./xorg_fix_proprietary.py” (Arquivo ou diretório não encontrado) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
  InstallationDate: Installed on 2017-06-04 (260 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG

[Touch-packages] [Bug 1750282] Re: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

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

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

Title:
  package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  this occurred during routine updates

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Feb 18 22:26:32 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-07-26 (938 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: dbus
  Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-27 (22 days ago)

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

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

[Touch-packages] [Bug 1750379] Re: Distortion Realtek ALC887

[Daniel van Vugt]

This may be related to bug 1576420 with the same audio chip, but let's
keep it separate for now...

Please tell us:
 * Does the bug exist in Ubuntu 17.10.1 if you live boot that?
 * Does the bug persist if you try installing older or newer kernels?
   http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
 * If there is a kernel version that doesn't have the bug, are you able to 
narrow it down to find the kernel version that introduced it?

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

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

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1750379

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[Gunnar Hjalmarsson]

systemd 237-3ubuntu1 has been uploaded including these changes, and a
complete systemd.pot was imported to LP. Case closed. :)

** Changed in: ubuntu-translations
   Status: In Progress => Fix Released

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1739509] Re: Why was gstreamer0.10 dropped from Ubuntu

[Launchpad Bug Tracker]

[Expired for gstreamer0.10 (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gstreamer0.10 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Why was gstreamer0.10 dropped from Ubuntu

Status in gstreamer0.10 package in Ubuntu:
  Expired

Bug description:
  Why was gstreamer0.10 dropped from Ubuntu? It is still available in
  debian and many applications do use it
  
https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all
  , e.g. proprietary eTXT Antiplagiat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1739509/+subscriptions

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

[Touch-packages] [Bug 1733143] Re: Network sound devices are always set as default

[Daniel van Vugt]

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

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

Title:
  Network sound devices are always set as default

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I notice that when I connect to a wireless network with an Apple TV,
  the network device is set as the default audio device. This happens
  even if I have manually set it otherwise.

  STEPS TO REPRODUCE:
  1. Connect to network with an Apple TV.
  2. PulseAudio picks up the Apple TV device and sets it as default.
  3. Manually set the built-in audio card as default.
  4. Disconnect from the audio network, and reconnect.
  5. PulseAudio again sets the Apple TV device as default.

  EXPECTED BEHAVIOR:
  Step 2 is debatable, but step 5 definitely should not happen.

  This is on Kubuntu 17.04 with pulseaudio 1:10.0-1ubuntu2 and plasma-pa
  4:5.9.5-0ubuntu0.1.

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

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

[Touch-packages] [Bug 1692454] Re: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

[Daniel van Vugt]

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

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

Title:
  [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  no audio at all

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 14:08:44 2017
  InstallationDate: Installed on 2017-05-17 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / 
Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Touch-packages] [Bug 1689555] Re: Scrolling + "Terminal bell" crashes pulseaudio

[Daniel van Vugt]

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

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

Title:
  Scrolling + "Terminal bell" crashes pulseaudio

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  If "Terminal bell" is enabled (in "Profile Preferences" > "General"),
  and I scroll fast in the output of e.g less to cause the "alert sound"
  to be played repeatably very fast, pulseaudio crashes.

  From /var/log/syslog:
  May  9 15:05:13 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:15 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
sink
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
source
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Unable to find stream 
for bar '(null)'
  May  9 15:05:17 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:06:01 ubuntu-laptop indicator-sound[2948]: message repeated 22 
times: [ volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 14:58:51 2017
  InstallationDate: Installed on 2017-05-01 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[Daniel van Vugt]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

Status in alsa-driver package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

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

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

[Touch-packages] [Bug 1693464] Re: Bluetooth Audio broken for Bose SoundLink Mini

[Daniel van Vugt]

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

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Touch-packages] [Bug 1666696] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card

[Daniel van Vugt]

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

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

Title:
  [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  No sound when play video, music or clips in the internet. In audio
  setting it's shown as dummy device

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-5.7+IntelAtom-linuxium 4.10.0-rc6
  Uname: Linux 4.10.0-5-linuxium x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  2541 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 00:52:54 2017
  InstallationDate: Installed on 2017-02-19 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" Linuxium - Alpha  (20170127)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: bytcr-rt5651 - bytcr-rt5651
  Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: IRBIS.WI310D.NWNNRBN01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrIRBIS.WI310D.NWNNRBN01:bd11/04/2016:svnIRBIS:pnNB20:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NB20
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: IRBIS

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

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

[Touch-packages] [Bug 1661975] Re: No sound only silence

[Daniel van Vugt]

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

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

Title:
  No sound only silence

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After the updates on gsstreamer the sound stopped working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   bertadmin   2423 F...m pulseaudio
   /dev/snd/controlC1:  bertadmin   2423 F pulseaudio
   /dev/snd/controlC0:  bertadmin   2423 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb  5 12:09:51 2017
  InstallationDate: Installed on 2014-10-05 (854 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F6 v01.09
  dmi.board.name: 3029h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F6v01.09:bd04/09/2008:svnHewlett-Packard:pnHPCompaqdc5850Microtower:pvr:rvnHewlett-Packard:rn3029h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc5850 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Daniel van Vugt]

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

-- 
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:
  Confirmed
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 1490937] Re: Unavailable port selected by default

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  Unavailable port selected by default

Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project trusty series:
  Won't Fix
Status in PulseAudio:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In case one card has only unavailable ports, it might be still be
  selected as default, even though there are available ports on other
  cards.

  E g, on a HTPC which have only Headphone and HDMI outputs, and these
  two outputs are on separate cards, the headphone port might be
  selected even if the HDMI port is available and the headphone port is
  not.

  Probably PulseAudio's routing system needs to be rewritten to be more
  port based to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1490937/+subscriptions

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

[Touch-packages] [Bug 1416228] Re: pulseaudio crashed with SIGABRT in pa_hook_fire()

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_hook_fire()

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  ,,,

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:4.0-0ubuntu23
  Uname: Linux 3.19.0-031900rc6-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   caravena   3850 F...m pulseaudio
   /dev/snd/controlC0:  caravena   3850 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Jan 30 00:54:42 2015
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-09-25 (127 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  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: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  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/ubuntu/+source/pulseaudio/+bug/1416228/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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()

[Daniel van Vugt]

Closed due to no response.

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

-- 
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:
  Confirmed
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 1288055] Re: Nvidia and Pulseaudio

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  Nvidia and Pulseaudio

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Nvidia está causando incompatibilidade no Ubuntu 13.10.
  Minha placa de vídeo e uma nVidia GeoForce 550 ti.
  A um bug também no pulseaudio, eu tenho que instalar um painel de controle 
pulseaudio para poder abilitar o microfone
  frontal para poder falar no Skype.
  Obrigado pela paciência.
  ASS : THAUAN7020

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-17-generic 3.11.0-17.31
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  soneca 1417 F pulseaudio
   /dev/snd/controlC0:  soneca 1417 F pulseaudio
  CurrentDmesg:
   [   17.861452] atl1c :03:00.0: atl1c: eth0 NIC Link is Up<1000 Mbps Full 
Duplex>
   [   41.596084] systemd-hostnamed[1896]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [   86.328044] usb 1-8: reset high-speed USB device number 3 using ehci-pci
   [  299.136040] atl1c :03:00.0: vpd r/w failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update.
  Date: Wed Mar  5 01:58:20 2014
  HibernationDevice: RESUME=UUID=caa5d39c-44e4-4f1d-b2cc-529628b1c907
  InstallationDate: Installed on 2014-03-03 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. G41MT-S2P
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=544fb0e8-c375-4dca-9e2d-c1d058564b2e ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-17-generic N/A
   linux-backports-modules-3.11.0-17-generic  N/A
   linux-firmware 1.116.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1444102] Re: [USB-Audio - Xonar U7, playback] dummy output

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  [USB-Audio - Xonar U7, playback] dummy output

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I can see my soundcard in 'aplay -l' output, but can't see it in
  pavucontrol.

  URL https://help.ubuntu.com/community/SoundTroubleshootingProcedure
  are readed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Tue Apr 14 21:40:16 2015
  InstallationDate: Installed on 2015-04-04 (10 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Xonar U7 - Xonar U7
  Symptom_Type: Volume slider, or mixer problems
  Title: [USB-Audio - Xonar U7, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: 945GCM-S2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd06/04/2008:svnGigabyteTechnologyCo.,Ltd.:pn945GCM-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCM-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GCM-S2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1267803] Re: Some time Speech-dispatcher speech rate changing faster, this is resulting distorted speech output when Espeak module is used

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  Some time Speech-dispatcher speech rate changing faster, this is
  resulting distorted speech output when Espeak module is used

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Dear Developers,

  Some time if Speech-dispatcher Espeak module active and Speech-dispatcher 
using Pulseaudio, the speech rate changing very fast rate, and this problem 
resulting distorted, not understandable speech quality.
  Affected Ubuntu releases:
  Ubuntu 13.10: Speech-dispatcher packaged version is 0.7
  Ubuntu 14.04 development release: packaged Speech-dispatcher version is 0.8
  Upstream git master branc speech-dispatcher version with affected too: 
Speech-dispatcher 0.8
  In Ubuntu a11y list Luke wrote following issue:
  "What fix is this exactly, and in what package? I am aware of audio issues 
with espeak and speech-dispatcher in 13.10, and its a combination of 
speech-dispatcher's pulseaudi ocode and pulseaudio itself. Speech-dispatcher is 
probably not using pulse as well as it could be, at the same time, pulse has 
had changes made that somtimes cause audio issues. I've tried following this up 
with upstream, and some work has been done to try and look into this, but it 
seems we're not there yet. I need to try git master of pulse myself to see if 
things are resolved.

  Luke"
  Don't surprise the modified package components, I using now Speech-dispatcher 
latest git master version.

  Attila

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

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

[Touch-packages] [Bug 1078704] Re: headphone jack sense not enabled

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  headphone jack sense not enabled

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  bug is present in Ubuntu 12.04 and Xubuntu 12.04 and Lubuntu 12.04.1 64bit 
  alsa-base 1.0.25+dfsg-0ubuntu1 on this machine (64 bit)
  I except Ubuntu to automatically sense the presence of headphones and disable 
the speakers.  This is not the case, the speakers and headphones play 
simultaneously.  I must install gnome-alsamixer to manually set the jack sense. 
 Alsa should have this enabled as the default setting.  This seems as though it 
should be a very easy bug to fix, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  love   1330 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'nForce3'/'NVidia nForce3 with AD1981B at irq 21'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 33
 Simple ctrls  : 22
  Date: Wed Nov 14 06:42:21 2012
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2004
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.11
  dmi.board.name: 08A0
  dmi.board.vendor: Compal
  dmi.board.version: 32.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.11:bd04/30/2004:svnHewlett-Packard:pnPresarioR3200(PF153UA#ABA):pvrF.11:rvnCompal:rn08A0:rvr32.22:cvnCompal:ct10:cvr:
  dmi.product.name: Presario R3200 (PF153UA#ABA)
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1210470] Re: Switching to integrated card with vgaswitcheroo makes the kernel to hang, until pulseaudio is killed

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  Switching to integrated card with vgaswitcheroo makes the kernel to
  hang, until pulseaudio is killed

Status in Linux:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a dual-GPU notebook, with a Intel Ironlake integrated GPU and a
  AMD 5650m dedicated GPU (muxed system). The AMD gpu is also connected
  to an HDMI port that implies an audio card (I'm running radeon module
  with radeon.audio=1).

  If I switch to the integrated card after that the UI is up and
  pulseaudio is loaded, as soon as I exit from lightdm (both to reload X
  or to shutdown the PC) the kernel hangs (both in 12.10, 13.04 and
  13.10):

  [ 489.177732] hda-intel :01:00.1: Disabling via VGA-switcheroo
  [ 489.297129] hda-intel :01:00.1: Cannot lock devices!
  [ 489.297139] radeon: switched off
  [ 489.300356] [drm] Disabling audio support
  [ 489.319552] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x0015e418 and cpu addr 0xc90009df0418
  [ 489.973886] ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event: unsupported
  [ 489.973903] _handle_hotplug_event_root: Bus check notify on \_SB_.PCI0
  [ 678.992375] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 678.992453] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 683.996303] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 683.996377] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 683.996453] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing C3DC (len 871, WS 0, PS 0) @ 0xC439
  [ 689.000275] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 689.000349] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 694.004285] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 694.004363] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 699.008330] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 699.008414] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 699.514458] init: tty1 main process (2460) killed by QUIT signal
  [ 699.514489] init: tty1 main process ended, respawning
  [ 704.012405] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 704.012492] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28
  [ 709.016515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 
5secs aborting
  [ 709.016596] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing CD0C (len 62, WS 0, PS 0) @ 0xCD28

  
  At the contrary, if once lightdm starts I go to tty1 → sudo service lighdm 
stop → sudo killall pulseaudio → echo OFF| sudo tee 
/sys/kernel/debug/vgaswitcheroo/switch #switch to integrated card

  Everything works well instead.

  So it seems that pulseaudio should disable the powered-off card on
  switch (or is this something that the kernel should do?).

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

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

[Touch-packages] [Bug 1465167] Re: No sound with dual headphones jacks of Toshiba QOSMIO G40

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  No sound with dual headphones jacks of Toshiba QOSMIO G40

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I've made a clean install of Ubuntu 15.04 but I'm having this issue
  when using headphones. Volume is very low, even when turning it to
  maximum. Everything worked fine under Ubuntu 14.04 that I was using
  before 15.04.

  I've reset the audio configuration with the command "rm -r
  ~/.config/pulse; pulseaudio -k" but it only fixes the issue
  temporarily. After each restart, the issue happens again and I have to
  execute the above command to get normal volume with headphones.

  Volume is normal with built-in speakers however.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erik   1836 F pulseaudio
   /dev/snd/controlC0:  erik   1836 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jun 15 09:34:28 2015
  InstallationDate: Installed on 2015-04-24 (52 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/29/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 2.20
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 10
  dmi.chassis.vendor: TS
  dmi.chassis.version: IBA
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion2.20:bd02/29/2008:svnTOSHIBA:pnQOSMIOG40:pvrPQG40E-01G019FR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTS:ct10:cvrIBA:
  dmi.product.name: QOSMIO G40
  dmi.product.version: PQG40E-01G019FR
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1071593] Re: padsp segfaults in VLC call to freopen()

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  padsp segfaults in VLC call to freopen()

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

Bug description:
  vlc segfaults when i launch it with:

  PULSE_SERVER=localhost:4716 ALSA_PCM_NAME=pulse padsp vlc /dev/cdrom
  >>/tmp/vlc.$$.ort 2>&1

  and if i just launch it with "vlc", it shows a window with a orange
  striped cone, i select media->open disc, and the window ceases to
  render, staying all grey.

  works fine in natty.

  failures are in freshly installed (and updated) quantal:

  ii  vlc  2.0.4-0ubuntu1
  i386 multimedia player and streamer

  reinstalled from scratch, same result.

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

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

[Touch-packages] [Bug 1019693] Re: [HDA-Intel - HDA Intel, playback] Audio stuttering

[Daniel van Vugt]

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

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

Title:
  [HDA-Intel - HDA Intel, playback] Audio stuttering

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in Arch Linux:
  New

Bug description:
  My audio has always worked perfectly on this hardware and 12.04. On 30
  June 2012 (Australian time) I received an update, including a kernel
  update. Since then the sound is stuttering.

  Audio will play normally for 10 seconds or so, but then about 1/4 of a
  second of the audio stream will be replayed in a loop 5 or 6 times.
  Even during the audio-test executed from the ubuntu-bug application (a
  solid beep), there was a noticeable stop and restart of the beep.
  i.e. what should be bp became
  beee.bebebebebe.beeep

  Others have reported a similar issue since the same patch:
  http://ubuntuforums.org/showthread.php?p=12064710&posted=1#post12064710

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15.1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jem2029 F pulseaudio
   /dev/snd/controlC0:  jem2029 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbcf8000 irq 44'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0887,1028040d,00100202 
HDA:80862804,80860101,0010'
 Controls  : 52
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfbdbc000 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Sun Jul  1 10:08:19 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Juniper HDMI Audio [Radeon HD 5700 Series] - HD-Audio Generic
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_SpeakerTestPulseStderr: W r i t e   e r r o r :   - 3 2 , B r o k e n 
  p i p e
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [HDA-Intel - HDA Intel, playback] Underruns, dropouts or crackling 
sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0G3HR7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd12/09/2009:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0G3HR7:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 8100
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 986817] Re: UA-101 - UA-101, playback Pulseaudio fails to detect card

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
   UA-101 - UA-101, playback  Pulseaudio fails to detect card

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

Bug description:
  This bug has been created with apport-bug.

  After upgrade from 10.04, the UA-101 inputs and outputs seem unavailable in 
standard audio settings.
  Sound works with VLC when UA-101 is selected via ALSA.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   19895 F pulseaudio
   /dev/snd/controlC0:  michael   19895 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   19895 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6ff8000 irq 44'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1043829f,0012'
 Controls  : 46
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'UA101'/'EDIROL UA-101 (serial ZT82634), 192000 Hz at 
usb-:00:1a.7-3, high speed'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'MIDI Input Mode',0
 Capabilities: enum
 Items: 'High Load' 'Light Load'
 Item0: 'Light Load'
  Card2.Amixer.info:
   Card hw:2 'CX8811'/'Conexant CX8811 at 0xfb00'
 Mixer name : 'CX88'
 Components : ''
 Controls  : 3
 Simple ctrls  : 2
  Date: Sun Apr 22 13:03:21 2012
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] - 
Conexant CX8811
  Title: [UA-101 - UA-101, playback] Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to precise on 2012-04-18 (3 days ago)
  dmi.bios.date: 10/14/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/14/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5K
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 875660] Re: PA and knotify startup race leads to wrong device selection

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  PA and knotify startup race leads to wrong device selection

Status in Phonon:
  Unknown
Status in kde-runtime package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  This appears to be a regression in Oneiric.
  I'm running Kubuntu with pulseaudio.
  I have on my motherboard intel hda analog audio and my graphics card (an ATI) 
had an HDMI out; by default I like the audio to come out of the analog output 
that is the only one connected.

  Sometimes logging into KDE I find that it's decided to switch to the
  HDMI as the default; today I caught it and did an lsof /dev/snd/* and
  found:

  knotify4  2276   dg  memCHR  116,3  6691 /dev/snd/pcmC0D0p
  knotify4  2276   dg   20r   CHR 116,33  0t0 9995 /dev/snd/timer
  knotify4  2276   dg   21u   CHR  116,3  0t0 6691 /dev/snd/pcmC0D0p
  pulseaudi 2893   dg   24u   CHR  116,9  0t0 6698 /dev/snd/controlC1   


  
  pulseaudi 2893   dg   31u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  
  pulseaudi 2893   dg   38u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  

  So knotify4 has hogged the analog output, and hence pa can't get in.

  So I kill knotify4, and do a pactl exit to restart pa - but pa then
  still lists the HDMI as the default output in paman, and I can't see a
  way to get it back to default without restarting everything.

  I'm also going to subscribe this bug to kde-runtime; I'm not sure who
  is supposed to manage the race between pa startup and anything else,
  and I'm not sure if it's a kubuntu special or KDE in general.

  Dave

  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: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dg 4889 F pulseaudio
   /dev/snd/controlC0:  dg 4889 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbcf8000 irq 47'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,18490397,0010'
 Controls  : 37
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570
  CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
  Date: Sun Oct 16 12:31:37 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to oneiric on 2011-09-24 (21 days ago)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: P55M Pro
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/10/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 878028] Re: [USB-Audio - UAC3553B, playback] No sound at all

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  [USB-Audio - UAC3553B, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Bug occured after upgrading to 11.10. Previously, I was able to plug
  in the usb audio (or turn it on, if it was alredy plugged in) and
  select it as an output device in the sound settings dialogue (or via
  pavucontrol). Now, the device only shows up in the hardware list
  (listed with 1 output), but no longer in the output list.

  USB audio device is a Philips FW-M567 compact stereo system.

  If it is any help: apport performed two sound tests. The first one
  played correctly on the USB audio device, the second one, however,
  played on the Intel sound card, which is why I hit the "not played
  back correctly" button.

  Another interesting fact: It worked yesterday after I upgraded a few
  packages. I didn't change anything after that. Today I turn on my
  computer and it's non-functional again.

  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
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chrisipk   2562 F pulseaudio
chrisipk   3170 F xfce4-volumed
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7ff8000 irq 47'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,14627522,0011'
 Controls  : 34
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'UAC3553B'/'Philips UAC3553B at usb-:00:1a.1-1, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0471:0110'
 Controls  : 6
 Simple ctrls  : 5
  Date: Wed Oct 19 11:26:13 2011
  ProcEnviron:
   LANGUAGE=de_DE:de:en_GB:en
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:UAC3553B 
successful
  Symptom_Card: UAC3553B - UAC3553B
  Symptom_DevicesInUse:
   2562  3170  2285  chrisipk  F pulseaudio
chrisipk  F xfce4-volumed
   /dev/snd/seq:timidity  F timidity
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - UAC3553B, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (1 days ago)
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.5
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MSI X58 PLATINUM SLI(MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.5:bd06/19/2009:svnMSI:pnMS-7522:pvr1.0:rvnMSI:rnMSIX58PLATINUMSLI(MS-7522):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7522
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 792098] Re: pulseaudio does not remember channel volumes after reboot

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  pulseaudio does not remember channel volumes after reboot

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  What I expect to happen:

  Volume levels of channels "Master", "Master Mono", "Headphones", "PCM"
  are stored at shutdown and restored when restarted.

  What happens instead:

  Volume levels are reset to Master=56, Master Mono=0 (and muted),
  Headphones=100, and PCM=56 on every restart. Possibly other settings
  are reset as well, but these are the only ones I use.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: pulseaudio 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1236 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'ICH6'/'Intel ICH6 with STAC9750,51 at irq 16'
 Mixer name : 'SigmaTel STAC9750,51'
 Components : 'AC97a:83847650'
 Controls  : 38
 Simple ctrls  : 24
  Date: Thu Jun  2 18:01:28 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0C5668
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2005:svnDellInc.:pnInspiron9300:pvr:rvnDellInc.:rn0C5668:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 9300
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 840777] Re: Muting sound indicator in Unity Greeter does not mute sound on login

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  Muting sound indicator in Unity Greeter does not mute sound on login

Status in Ayatana Design:
  Fix Committed
Status in The Sound Menu:
  Invalid
Status in Unity Greeter:
  Invalid
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I am using beta edition of Ubuntu 11.10,with lightdm 0.9.3-0ubuntu8,and unity 
4.12.0-0ubuntu2,
  There is a new feature in Display Manager(well,I didn't notice it in gdm,but 
it might have been there as well),That you can mute the sound so that login 
sound wont play(This option exists in the top of the lightdm login page,when 
you turn on ubuntu and load it)However,Login sound will still play and sound 
settings will change regardless of what you choose.
  I should add that,this happens only after a reboot or shutdown,boot again,and 
not when you logout and login again

  : "Sound volume should also be
  independent of which user — or whether any user — is logged in. This
  way, if you mute or turn down sound at the login screen, you will not
  be surprised or frustrated by sound playing loudly after you log in."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/840777/+subscriptions

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

[Touch-packages] [Bug 1696301] Re: Enabling the EQ causes audio corruption and stutter

[Daniel van Vugt]

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

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

Title:
  Enabling the EQ causes audio corruption and stutter

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Enabling pulseaudio-equalizer causes audio corruption and stutter
  globally, including with bluetooth streaming, despite using little CPU
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio-equalizer 1:10.0-1ubuntu2
  Uname: Linux 4.11.0-041100-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh 26275 F pulseaudio
   /dev/snd/controlC0:  paulh 26275 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jun  7 14:58:21 2017
  InstallationDate: Installed on 2017-01-05 (153 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (53 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-06-07T14:45:08.795195

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

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

[Touch-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1738907

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


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

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

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

Title:
  Bluetooth audio latency / delay increasing on video streamig

Status in bluez package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  With my bluetooth headset (A2DP audio protocole) when I watch videos
  streaming with Google Chrome for example. there is a delay increasing
  between audio and video. I tried to change and set up the audio
  latency, but the delay increase, as much as I play bigger video

  
  ubuntu 17.04 or 17.10 64bit

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

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

[Touch-packages] [Bug 1727914] Re: bluetoothd crashed with SIGEMT in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk

[Daniel van Vugt]

Fix Released (no crash reports after 17.04)

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

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

Title:
  bluetoothd crashed with SIGEMT in malloc_consolidate() from
  _int_malloc() from __libc_calloc() from __GI___open_memstream() from
  __GI___vsyslog_chk

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 
5.43-0ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/98da419ed3c25ad6b4e2fe408d176d1abed4d08c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1694455] Re: Bluetooth: Cannot receive files

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test.

If you then find the bug is still present in the newer Ubuntu version,
please add a comment here telling us which new version it is in and
change the bug status to Confirmed.


** Changed in: bluez (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Bluetooth: Cannot receive files

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  # Use case

  Ubuntu 17.04, quite fresh installation, updated.

  Bluetooth file transmission

  I want to send files to my smartphone, and receive files sent by my
  smartphone via bluetooth. I pair both devices, initiate file transfer
  from one of the devices, and the other device asks me what to do.

  # Problems

  This is a mix from usability and technical issues.

  1. OBEX disabled (bug 1645631)

  The bluetooth file transmission service OBEX was not started. I started and 
enabled OBEX:
  `systemctl --user start obex`
  `systemctl --user enable obex`

  ```
  Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service...
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  ```

  2. OBEX silently fails (this bug)

  After having OBEX enabled, I was able to transmit files from laptop to
  smartphone, yet I could not receive files on the laptop. In the system
  log, you could see that OBEX fails (please note `FORBIDDEN`):

  ```
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  I did not receive a popup notification asking me to receive the file
  or not.

  In the file sharing preferences `gnome-file-share-properties`, there
  is a setting to automatically receive files via bluetooth. With this
  box checked, you're finally able to receive files from your
  smartphone.

  Successful log for comparison:
  ```
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  # Expected behaviour

  OBEX is started by default to handle bluetooth file transfers.

  If no automatic file receipt is configured, a popup notification asks
  me if I want to receive the file or not.

  If this is not possible, there should be a notification pointing the
  user to the configuration.

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

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

[Touch-packages] [Bug 1665589] Re: Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS Mobile Mouse 3600

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test.

If you then find the bug is still present in the newer Ubuntu version,
please add a comment here telling us which new version it is in and
change the bug status to Confirmed.


** Changed in: bluez (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS
  Mobile Mouse 3600

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I saw number of posts here about Mobile Mouse 3600 but sadly none of
  them helped me to debug the issue.

  I have Killer 1535 card on my Dell XPS 13. According to specs it's
  Bluetooth 4.1 device. Mobile Mouse 3600 is Bluetooth Low Energy device
  of version 4.0.

  In theory these two devices should be able to communicate.
  Unfortunately they don't :(

  I'm on Ubuntu MATE 16.10 but I also tested it on Linux Mint 18 and
  Element OS. I have bluez 5.41 installed.

  Here is what info I have abut my devices

  usb-devices | awk '/e301/' RS=

  T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#=  4 Spd=12  MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0cf3 ProdID=e301 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  
  hciconfig -a | grep HCI

  HCI Version: 4.1 (0x7)  Revision: 0x0

  lsusb | grep Ath

  Bus 001 Device 004: ID 0cf3:e301 Atheros Communications, Inc.

  `sudo hcitool lescan` finds nothing.

  After clean installation `dmesg | grep ath10` gives

  [   14.979939] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [   14.981966] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
  [   15.263691] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:3a:00.0.bin failed with error -2
  [   15.263709] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/cal-pci-:3a:00.0.bin failed with error -2
  [   15.263734] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [   15.263736] ath10k_pci :3a:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [   15.440154] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [   15.440156] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 
1 dfs 0 testmode 0
  [   15.440582] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  [   15.532098] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
  [   17.658135] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
  [   17.770412] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0

  My WiFi works. I can also pair Bluetooth keyboard. Since I don't
  really know how device drivers work in Linux I noticed line with error
  about `firmware-5.bin` in output of dmesg. So I took missing file from
  https://github.com/kvalo/ath10k-
  firmware/tree/master/QCA6174/hw3.0/4.4. It turned out to be bad idea
  because it botched wifi/bluetooth completely. Here is what I had in
  log

  [3.519354] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [3.521259] ath10k_pci :3a:00.0: pci irq msi-x interrupts 8 
irq_mode 0 reset_mode 0
  [3.765880] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/cal-pci-:3a:00.0.bin failed with error -2
  [3.831220] ath10k_pci :3a:00.0: failed to fetch board data for 
ath10k/QCA6174/hw3.0 from bus=pci,bmi-chip-id=0,bmi-board-id=0/board-2.bin
  [5.887772] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [5.887786] ath10k_pci :3a:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff bmi 0:0) fw WLAN.RM.4.4-00022-QCARMSWPZ-2 fwapi 5 bdapi 1 htt-ver 
3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features 
wowlan,ignore-otp
  [5.887789] ath10k_pci :3a:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.884160] ath10k_pci :3a:00.0: could not suspend target (-11)
  [8.966789] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0
  [   11.178547] ath10k_pci :3a:00.0: Unknown eventid: 90

[Touch-packages] [Bug 687689] Re: Audacity ruins bluetooth

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  Audacity ruins bluetooth

Status in Audacity:
  Confirmed
Status in audacity package in Ubuntu:
  Incomplete
Status in portaudio package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: audacity

  Apparently Audacity is not smart enough to know that it's running
  under a Gnome environment. Everything in terms of audio devices is
  managed quite well with pulseaudio, bluetooth-applet, and other Gnome
  desktop infrastructure. It tries to hard and breaks it. It tries to
  hack into my bluetooth in a vain attempt to find a headset or
  something like that and it ruins my bluetooth support in the desktop.
  I am no longer able to send files or use bluetooth in anyway.

  First thing it does when you launch it is that it does nothing. It'll
  just hang. You click on the icon in the menu and you won't get any
  feedback. Even if you run it from the command line it will give no
  feedback and display no errors. It just hangs.

  Then you kill it and restart it a couple times and it launches successfully. 
Sorta. Besides the globalmenu bug reported in another report it displays this 
error on my terminal:
  $ audacity 
  bt_audio_service_open: connect() failed: Connection refused (111)
  bt_audio_service_open: connect() failed: Connection refused (111)
  bt_audio_service_open: connect() failed: Connection refused (111)
  bt_audio_service_open: connect() failed: Connection refused (111)
  Cannot connect to server socket err = No such file or directory
  Cannot connect to server socket
  jack server is not running or cannot be started
  Expression 'stream->capture.pcm' failed in 
'src/hostapi/alsa/pa_linux_alsa.c', line: 3653

  
  Here is the errors reported by dmesg:

  [  807.086761] EXT4-fs (dm-0): re-mounted. Opts: commit=0
  [  812.790151] usb 6-1: USB disconnect, address 2
  [  812.790881] btusb_intr_complete: hci0 urb 88010e8e1600 failed to 
resubmit (19)
  [  812.790905] btusb_bulk_complete: hci0 urb 88010e8e1c00 failed to 
resubmit (19)
  [  812.791892] btusb_bulk_complete: hci0 urb 8801185a93c0 failed to 
resubmit (19)
  [  812.792064] btusb_send_frame: hci0 urb 8800c0872e40 submission failed
  [  813.322598] usb 6-1: new full speed USB device using uhci_hcd and address 3
  [  900.790130] usb 6-1: USB disconnect, address 3
  [  900.790753] btusb_intr_complete: hci0 urb 8800cba0d6c0 failed to 
resubmit (19)
  [  900.790784] btusb_bulk_complete: hci0 urb 8800c0805d80 failed to 
resubmit (19)
  [  900.791836] btusb_bulk_complete: hci0 urb 8800c0805180 failed to 
resubmit (19)
  [  900.792039] btusb_send_frame: hci0 urb 8800c08ddf00 submission failed
  [  900.807505] bluetooth-apple[2004]: segfault at a ip 7f65d520c9ee sp 
7fffba728880 error 4 in libdbusmenu-glib.so.1.0.17[7f65d5208000+1]
  [  901.320309] usb 6-1: new full speed USB device using uhci_hcd and address 4
  [ 1308.540165] usb 6-1: USB disconnect, address 4
  [ 1308.541015] btusb_intr_complete: hci0 urb 8800c0b18840 failed to 
resubmit (19)
  [ 1308.541045] btusb_bulk_complete: hci0 urb 8800c099eb40 failed to 
resubmit (19)
  [ 1308.542097] btusb_bulk_complete: hci0 urb 8800c0b180c0 failed to 
resubmit (19)
  [ 1308.542300] btusb_send_frame: hci0 urb 88010f313540 submission failed


  At that point my bluetooth support is broken and thus Audacity will
  successfully open. After hitting ctrl-f to work around the globalmenu
  bug (even though I am not using global menu) I can then edit files and
  such. Save them. Everything works.

  Of course I can no longer connect to the internet through my phone,
  send files, upload ringtones, use my bluetooth headset, etc. To work
  around you can remove the USB bluetooth adapter if you use a external
  one, plug it back in, and launch bluetooth-applet from the command
  line and it should be working again.

  It's not the end of the world, but Audacity should be configured to
  work properly in the default environment.

  I suggest eliminating Alsa and bluetooth support and have it not try
  to fight proper daemons handle it as they do a much better job. At
  least with PA and Bluetooth. I don't know how well Jack supports
  bluetooth audio devices, but Audacity really should not be allowed to
  do this sort of thing. I understand that it seems like a nice feature
  to be able to use a headset outside of Gnome, but it seems to be
  fundamentally incompatible with having a bluetooth adapter that is
  able to work with any other device.

  
  For people that may run into this problem in the future through Google or 
whatever here is two work arounds I suggest:

  1. Remove or otherwise disable all 

[Touch-packages] [Bug 483812] Re: Pulseaudio will not route internal/external mic to the speakers/headphones Karmic

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  Pulseaudio will not route internal/external mic to the
  speakers/headphones Karmic

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  Recording works just fine with both MICs, Skype works fine with no
  issues at all. what i wanted to do is just route the MIC specially the
  exteranl MIC to the internal or external speaker by means if when i
  grap the mic and say Hellewwwo i can hear my voice through the
  speaker. this had always worked perior to Karmic. i didt tried all
  Pulseausio tutorials and installed all the extra bells and whistles
  but there seems no option to route the MIC to the speakers or even
  sing a Karaoke song.

  example: this works in windows7 by ticking on the option listen to
  this device at the MIC preferences

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

[Daniel van Vugt]

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

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1694827] Re: [VIZIO SB3820, playback] Bluetooth speaker not listed in Sound and can't be used without workarounds.

[Daniel van Vugt]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  [VIZIO SB3820, playback] Bluetooth speaker not listed in Sound and
  can't be used without workarounds.

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When I try to connect to my Bluetooth speaker using Ubuntu GNOME (a
  Vizio SB3820 sound bar) it is not listed in the sound devices until I
  use a workaround from this site:

  https://askubuntu.com/questions/824404/bluetooth-speaker-connected-
  but-not-listed-in-sound-output

  Specifically,

  "Install blueman sudo apt install blueman
  Delete the paired device in the bluetooth settings.
  Run these commands in terminal: bash
  sudo pkill pulseaudio
  sudo /etc/init.d/bluetooth restart
  Turn off headphones.
  Turn on headphones, and press green/go until headphones notification voice 
says "Ready to pair."
  Launch blueman, and from the upper right menu, right-click the icon to bring 
up the blueman menu. Select Setup new device.
  Pair the device, and when you are given an option, not headphones, not 
handsfree. Use the Audio sink option.
  Then when you look into the audio settings panel, the device should be 
displayed."

  In my case, the situation is more like killing pulseaudio, restarting
  the bluetooth service, and reconnecting to the device using Blueman as
  an audio sink, NOT using the GNOME Bluetooth applet.

  If I do this, the device appears as a sound device and worksuntil
  I reboot the computer.

  I was told to file a bug on this by the #ubuntu-gnome IRC channel
  using ubuntu-bug audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ryan   3043 F...m pulseaudio
   /dev/snd/controlC0:  ryan   3043 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed May 31 15:47:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: VIZIO SB3820
  Symptom_Type: None of the above
  Title: [VIZIO SB3820, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2UCN10T
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK2
  dmi.modalias: 
dmi:bvnLENOVO:bvr2UCN10T:bd10/14/2016:svnLENOVO:pn80UE:pvrLenovoYOGA900-13ISK2:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK2:
  dmi.product.name: 80UE
  dmi.product.version: Lenovo YOGA 900-13ISK2
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 566449] Re: No Sound Through USB Headset

[Daniel van Vugt]

Closed due to no response.

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

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

Title:
  No Sound Through USB Headset

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  Ubuntu 10.04
  64-bit

  When using a standard USB headset, sound will not play through the
  headphones. Both input (microphone) and output are detected, but only
  the microphone works. When switching to use the headphones, no audio
  seems to play. It previously worked in 9.10 and intermittently after
  first installing 10.04.

  
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryan   7099 F pulseaudio
   /dev/snd/controlC0:  ryan   7099 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xfbffc000 irq 17'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,10438290,00100101'
 Controls  : 36
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'default'/'C-Media USB Headphone Set   at usb-:00:10.2-2, full 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:000c'
 Controls  : 7
 Simple ctrls  : 3
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Tags: lucid
  Uname: Linux 2.6.32-21-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/15/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5VD2-VM SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/15/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5VD2-VMSE:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work

[Daniel van Vugt]

** Changed in: blueman (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  Bluetooth headset profile HSP/HFP doesn't work

Status in blueman package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP 
profile, but when i try change sound profile in blueman-manager to HSP/HFP - 
then i get error "Failed to change profile to headset_head_unit".
  With profile a2dp headphones work good(clementine, chromium etc..), but I 
could not get work output headphones in steam games, i listen only silence(i 
think it's problem of pulseaudio)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Nov 28 19:51:59 2017
  InstallationDate: Installed on 2016-06-22 (524 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Bluedio
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Bluedio, recording] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
  dmi.bios.date: 07/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L2.38
  dmi.board.name: AM2NF6G-VSTA
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810

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

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