[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares

[Tronde]

Good Moring,

I would like to add some news. I have removed and purged autofs from one
of my Thinkpads and installed autofs 5.1.2-1 from Bionic in Xenial. I
have used the packages from
http://archive.ubuntu.com/ubuntu/pool/main/a/autofs/autofs_5.1.2-1ubuntu2_amd64.de

Surprise, the behaviour is exactly the same as in version 5.1.1. It
won't work until the autofs.service is restarted.

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

Title:
  [SRU] [xenial] autofs needs to be restarted to pick up some shares

Status in autofs package in Ubuntu:
  Fix Released
Status in autofs5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid
Status in autofs source package in Xenial:
  Incomplete

Bug description:
  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and
  Dapper.

  EDIT:  confirmed with similar configuration on Intrepid with a NetApp
  filer hosting NFS.  Server OS removed from summary.

  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs
  (/etc/init.d/autofs restart) everythin then works OK.  My config files
  are:

  auto.master

  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc/etc/auto.misc --timeout=60
  #/misc/etc/auto.misc
  #/net /etc/auto.net

  /petunia /etc/petunia.misc --timeout=60

  
  petunia.misc

  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage

  cd  -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

  tony  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/tony
  chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/chris
  shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/SharedDocs
  linuxbackups  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/linuxbackups

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

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

[Touch-packages] [Bug 1758619] [NEW] lxc-update-config incorrectly converts network settings

[Alexander E. Patrakov]

Public bug reported:

Before the update, on LXC 2.0.8, I had:

lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.ipv4 = 10.0.3.205/24
lxc.network.ipv4.gateway = 10.0.3.1
lxc.network.hwaddr = 00:16:3e:ae:79:d7

After the update to LXC 3.0.0beta3, I have:

lxc.net.0.type = veth
lxc.net.0.flags = up
lxc.net.0.link = lxcbr0
lxc.net.0.ipv4 = 10.0.3.205/24
lxc.net.0.ipv4.gateway = 10.0.3.1
lxc.net.0.hwaddr = 00:16:3e:ae:79:d7

The conversion is wrong. lxc.network.ipv4 (which was the correct
spelling, according to the man page in the old package) should have been
converted to lxc.net.0.ipv4.address, not to lxc.net.0.ipv4.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lxc-utils 3.0.0~beta3-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Mar 25 14:24:16 2018
InstallationDate: Installed on 2018-01-25 (58 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.net.0.type = veth
 lxc.net.0.link = lxcbr0
 lxc.net.0.flags = up
 lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: amd64 apparmor apport-bug bionic

** Attachment removed: "lxcsyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089681/+files/lxcsyslog.txt

** Attachment removed: "KernLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089675/+files/KernLog.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089674/+files/JournalErrors.txt

** Attachment removed: "dnsmasq.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089678/+files/dnsmasq.conf.txt

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

Title:
  lxc-update-config incorrectly converts network settings

Status in lxc package in Ubuntu:
  New

Bug description:
  Before the update, on LXC 2.0.8, I had:

  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = lxcbr0
  lxc.network.ipv4 = 10.0.3.205/24
  lxc.network.ipv4.gateway = 10.0.3.1
  lxc.network.hwaddr = 00:16:3e:ae:79:d7

  After the update to LXC 3.0.0beta3, I have:

  lxc.net.0.type = veth
  lxc.net.0.flags = up
  lxc.net.0.link = lxcbr0
  lxc.net.0.ipv4 = 10.0.3.205/24
  lxc.net.0.ipv4.gateway = 10.0.3.1
  lxc.net.0.hwaddr = 00:16:3e:ae:79:d7

  The conversion is wrong. lxc.network.ipv4 (which was the correct
  spelling, according to the man page in the old package) should have
  been converted to lxc.net.0.ipv4.address, not to lxc.net.0.ipv4.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lxc-utils 3.0.0~beta3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 25 14:24:16 2018
  InstallationDate: Installed on 2018-01-25 (58 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.net.0.type = veth
   lxc.net.0.link = lxcbr0
   lxc.net.0.flags = up
   lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-to-hibernate

[Jeremy Bicha]

** Tags added: bionic rls-bb-incoming

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

Title:
  FFe: Support suspend-to-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions

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

[Touch-packages] [Bug 243105] Re: When Wubi is installed from CD, ubiquity crashes at the end of the installation

[Simon Quigley]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. When you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 243105

and any other logs that are relevant for this particular issue.

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

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

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

Title:
  When Wubi is installed from CD, ubiquity crashes at the end of the
  installation

Status in Wubi:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Because of bug #207137 Wubi now copies the CD content as opposed to
  extract an ISO. This was implemented via bug #230716 which allows
  casper to boot off a directory. That directory is bindmounted to
  /cdrom in the initrd. But that makes ubiquity/install.py >
  install_extras > do_install > cache.commit fail, since apt/python-apt
  does not work correctly when /cdrom is bind-mounted.

  That in turn can be tracked down to fetcher.Run() in apt/cache.py

  cache.py > Cache.commit > Cache._fetchArchives >
  self._runFetcher(fetcher) > fetcher.Run()

  Where

  fetcher = apt_pkg.GetAcquire(fetchProgress) -> Acquire instance

  When installing Wubi from an ISO (no bindmount) or when setting up
  /cdrom via a symlink in casper, the installation proceeds correctly.

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

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

[Touch-packages] [Bug 1758596] Re: package libpam-systemd:amd64 229-4ubuntu21.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

Title:
  package libpam-systemd:amd64 229-4ubuntu21.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

Status in systemd package in Ubuntu:
  New

Bug description:
  no further info

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu21.2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar 24 18:06:10 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-07-28 (604 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu21.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1525150] Re: Ubuntu font missing part of 8 and 3 in hexchat

[Adolfo Jayme]

** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-ubuntu
(Ubuntu)

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

Title:
  Ubuntu font missing part of 8 and 3 in hexchat

Status in fonts-ubuntu package in Ubuntu:
  New

Bug description:
  Not noticed this elsewhere, but in hexchat part of 8 and 3 is missing.

  Attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 11 10:06:33 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-10-29 (42 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications

[gregrwm]

regarding
http://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645485/comments/3

when Xorg hangs but does not crash (as in this bug description as well
as Bug #1645485 and Bug #1744429), how shall i produce the requested
crash report?

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

Title:
  [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after
  launching applications

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The problem is that after launching a few applications, the GUI may
  become unresponsive, although this is not consistently reproducible.
  When the GUI is unresponsive, it is correlated to high CPU utilization
  of xorg.

  An example reproduction scenario is launch the following in order, and 
quickly:
  startx
  xterm via twm
  another xterm via the first xterm
  tmux
  firefox-esr
  bluetooth-manager
  pavucontrol

  While the above are launching, maximize the xterm running tmux, and
  the GUI immediately becomes unresponsive. For example, Ctrl+Alt+Fn
  don't respond.

  After this, I logged in via ssh, attached to tmux, launched htop,
  copied htop output, which shows xorg at 94.6 CPU%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
    * Starting AppArmor profiles   
  [ OK ]
    * Restoring resolver state...   
  [ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
   -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  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+git20171229-1
  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/1757299/+subscriptions

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

[Touch-packages] [Bug 1731904] Re: Font has a big line hight

[Adolfo Jayme]

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

** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-ubuntu
(Ubuntu)

** This bug has been marked a duplicate of bug 1394914
   [nc] Line spacing causes major UI problems

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

Title:
  Font has a big line hight

Status in fonts-ubuntu package in Ubuntu:
  New

Bug description:
  Comparing to normal Ubuntu fonts, the Arabic Ubuntu fonts has an extra
  line hight.

  Please correct this so it matchs the Ubuntu family fonts

  
  System release :
  Description:  Arch Linux
  Release:  rolling

  Version of the package :
  0.84~mono0.83+arabicfontconfig-0ubuntu1

  What you expected to happen: 
  Correct the line hight to matchs the main Ubuntu fonts

  What happened instead:
  Well an extra line hight for example the menu takes almost the double size in 
the nautilus file manager.

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

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

[Touch-packages] [Bug 1758596] [NEW] package libpam-systemd:amd64 229-4ubuntu21.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Robert Bell]

Public bug reported:

no further info

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-systemd:amd64 229-4ubuntu21.2
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sat Mar 24 18:06:10 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2016-07-28 (604 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: systemd
Title: package libpam-systemd:amd64 229-4ubuntu21.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpam-systemd:amd64 229-4ubuntu21.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

Status in systemd package in Ubuntu:
  New

Bug description:
  no further info

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu21.2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar 24 18:06:10 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-07-28 (604 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu21.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 851084] Re: [pkg] does not show up in list returned by xfontsel, don't know 14-part font name

[Adolfo Jayme]

** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-ubuntu
(Ubuntu)

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

Title:
  [pkg] does not show up in list returned by xfontsel, don't know
  14-part font name

Status in Ubuntu Font Family:
  New
Status in fonts-ubuntu package in Ubuntu:
  New

Bug description:
  Hi,

  Attempting to use xfontsel to find the 14-part font name (with the
  hopes of using this name to set this font as the default for Emacs),
  it appears that the font is not known to xfontsel.  Similarly the font
  is not returned as an option by the Emacs `x-list-fonts' function.

  Is it possible that the apt-get instillation did not properly register
  the 14-part font name with the X server?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/851084/+subscriptions

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

[Touch-packages] [Bug 677150] Re: [nc] Generate TeX files of the Ubuntu Font Family during build time

[Adolfo Jayme]

** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-ubuntu
(Ubuntu)

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

Title:
  [nc] Generate TeX files of the Ubuntu Font Family during build time

Status in Ubuntu Font Family:
  New
Status in fonts-ubuntu package in Ubuntu:
  New

Bug description:
  At the moment it is not possible to use the Ubuntu Font Family in
  LaTeX  without importing it manually. It would be great if this font
  would be made available in LaTeX by default, so you can choose to use
  a modern font without too much of a hassle.

  Vincent-Xavier Jumel posted an article on his blog with some
  instructions for converting the font for use with TeX at .

  I'm requesting to generate these files at build time. We could then
  make LaTeX recommend the resulting package, so every user on Ubuntu
  who installs LaTeX will be able to use the font straight away.

  Related: bug #603574 (errors showing up during AFM build)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/677150/+subscriptions

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

[Touch-packages] [Bug 863358] Re: [pkg] Can't easily use Ubuntu without using Ubuntu Mono

[Adolfo Jayme]

** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-ubuntu
(Ubuntu)

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

Title:
  [pkg] Can't easily use Ubuntu without using Ubuntu Mono

Status in Ubuntu Font Family:
  New
Status in fonts-ubuntu package in Ubuntu:
  New

Bug description:
  I find the Ubuntu font fairly attractive. On the other hand, I find
  the Ubuntu Mono font unpleasant and likely to slow down my work. I
  understand it is a matter of personal taste, but the reasons should be
  obvious from the attached image.

  On popular operating systems, it is easy to use one font but not
  another, even if they are related. I suggest that this be possible on
  Ubuntu with the Ubuntu fonts too. Probably the simplest way of
  implementing this would be to package them separately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/863358/+subscriptions

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

[Touch-packages] [Bug 1758595] [NEW] grahics drivers not found

[nishant sikarwar]

Public bug reported:

grahics drivers not found

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
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: Sun Mar 25 06:29:40 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:81ec]
   Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 
M330 / M430] [103c:81ec]
InstallationDate: Installed on 2017-12-19 (95 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=bc6c8bb6-22cf-4f6d-a9ea-8a998b634d42 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EC
dmi.board.vendor: HP
dmi.board.version: 61.28
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.28:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
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

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


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

Title:
  grahics drivers not found

Status in xorg package in Ubuntu:
  New

Bug description:
  grahics drivers not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  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: Sun Mar 25 06:29:40 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:81ec]
 Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / 
R5 M330 / M430] [103c:81ec]
  InstallationDate: Installed on 2017-12-19 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=bc6c8bb6-22cf-4f6d-a9ea-8a998b634d42 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.28:cvnHP:ct10:cvrCha

[Touch-packages] [Bug 1636395] Re: dnsmasq not working with OpenVPN

[franck]

Nicholas @nstommel I'm using dnscrypt-proxy and now I can successfully
connect to internet and to vpn server.  Thank you! Will test this
further.

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

Title:
  dnsmasq not working with OpenVPN

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in openvpn-systemd-resolved package in Ubuntu:
  Confirmed

Bug description:
  I'm using OpenVPN configured with Network Manager. My VPN have a DNS
  server configured by OpenVPN and config pushed by it while connecting.
  This server is not registered by dnsmasq so domain names are not
  resolved but pinging by IP address works. When I test name resolving
  by pointing to DNS server (172.16.1.1) from VPN provider it's works.
  For example:

  $ host google.com 172.16.1.1
  Using domain server:
  Name: 172.16.1.1
  Address: 172.16.1.1#53
  Aliases: 

  google.com has address 172.217.0.174
  google.com has IPv6 address 2607:f8b0:400b:807::200e
  google.com mail is handled by 30 alt2.aspmx.l.google.com.
  google.com mail is handled by 20 alt1.aspmx.l.google.com.
  google.com mail is handled by 40 alt3.aspmx.l.google.com.
  google.com mail is handled by 10 aspmx.l.google.com.
  google.com mail is handled by 50 alt4.aspmx.l.google.com.

  But if I test without pointing DNS server is not working:

  $ host google.com
  ;; connection timed out; no servers could be reached

  My /etc/resolv.conf:
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 127.0.1.1

  To repair this bug I have to kill dnsmasq and it's automatically
  reloaded.

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

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

[Touch-packages] [Bug 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop

[Zhenqing Hu]

** Description changed:

- First of all, I am not sure whether it's true that this is a bug of 
network-manager, but it's true that it should be a bug related with network 
(wifi connection)
+ First of all, I am not sure whether it's true that this is a bug of 
network-manager, but it is true that this should be a bug related with network 
(wifi connection).
  Here is the issue:
- Every time after I login into the account, about 20 minutes later, the wifi 
connection will be disconnected automatically. I even cannot reconnect the wifi 
manually, the only thing that I can do is to reboot the laptop. After login 
again, wifi can be connected (but through the manual way).
- By the way, during the period of the wifi disconnection, I checked the "Wi-Fi 
Networks" by click "Select Network" in order to try to reconnect it manually, 
but I found that there was only one SSID which previously the laptop connected 
to. However, I was definitely sure that there should be more than one SSID 
being showed in the wifi list. Even for this only one SSID, like I mentioned 
above, I cannot reconnect manually unless I reboot the system.
- Finally, I set the wifi to be connected automatically if I login to the 
system, however, it just can't. I can only to manually connect the wifi after I 
login to the account.
+ Every time after I login into the account, about 20 minutes later, the wifi 
will be disconnected automatically. I even cannot reconnect the wifi manually, 
the only thing that I can do is to reboot the laptop. After login again, wifi 
can be connected (but through manual way).
+ By the way, during the period of wifi disconnection, I checked the "Wi-Fi 
Networks" by click "Select Network" in order to try to reconnect it manually. 
But I found that there is only one SSID which previously the laptop connected 
to. However, I was definitely sure that there should be more than one SSID 
being showed in the wifi list. Even for this only one SSID, like I mentioned 
before, I cannot reconnect manually unless I reboot the system.
+ Finally, I set the wifi to be connected automatically after I login to the 
system, however, it just can't. I can only connect to the wifi manually after I 
login to the system.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 19:02:12 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-01-15 (68 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
   172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
WolfieNet-Secure  eb45c742-ba31-4f31-acf2-13a2768bcc29  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp5s0  ethernet  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.10.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

Title:
  The wifi will be disconnected and the only thing I can do is to reboot
  the laptop

Status in network-manager package in Ubuntu:
  New

Bug description:
  First of all, I am not sure whether it's true that this is a bug of 
network-manager, but it is true that this should be a bug related with network 
(wifi connection).
  Here is the issue:
  Every time after I login into the account, about 20 minutes later, the wifi 
will be disconnected automatically. I even cannot reconnect the wifi manually, 
the only thing that I can do is to reboot the laptop. After login again, wifi 
can be connected (but through manual way).
  By the way, during the period of wifi d

[Touch-packages] [Bug 1758589] [NEW] The wifi will be disconnected and the only thing I can do is to reboot the laptop

[Zhenqing Hu]

Public bug reported:

First of all, I am not sure whether it's true that this is a bug of 
network-manager, but it's true that it should be a bug related with network 
(wifi connection)
Here is the issue:
Every time after I login into the account, about 20 minutes later, the wifi 
connection will be disconnected automatically. I even cannot reconnect the wifi 
manually, the only thing that I can do is to reboot the laptop. After login 
again, wifi can be connected (but through the manual way).
By the way, during the period of the wifi disconnection, I checked the "Wi-Fi 
Networks" by click "Select Network" in order to try to reconnect it manually, 
but I found that there was only one SSID which previously the laptop connected 
to. However, I was definitely sure that there should be more than one SSID 
being showed in the wifi list. Even for this only one SSID, like I mentioned 
above, I cannot reconnect manually unless I reboot the system.
Finally, I set the wifi to be connected automatically if I login to the system, 
however, it just can't. I can only to manually connect the wifi after I login 
to the account.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 24 19:02:12 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-01-15 (68 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600
 169.254.0.0/16 dev wlp4s0 scope link metric 1000
 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
 wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
WolfieNet-Secure  eb45c742-ba31-4f31-acf2-13a2768bcc29  
/org/freedesktop/NetworkManager/ActiveConnection/5
 enp5s0  ethernet  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.10.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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


** Tags: amd64 apport-bug bionic

** Description changed:

- First of all, I am not sure whether it's true that this is a bug of 
network-manager.
+ First of all, I am not sure whether it's true that this is a bug of 
network-manager, but it's true that it is a bug related with network (wifi 
connection)
  Here is the issue:
- Every time when I login into the account, then after about 20 minutes, the 
wifi will be disconnected automatically. I even cannot reconnect the wifi 
manually, the only thing that I can do is to reboot the laptop. After login 
again, wifi can be connected. 
+ Every time when I login into the account, then after about 20 minutes, the 
wifi will be disconnected automatically. I even cannot reconnect the wifi 
manually, the only thing that I can do is to reboot the laptop. After login 
again, wifi can be connected.
  By the way, during the period after wifi disconnected, I checked the "Wi-Fi 
Networks" by click "Select Network" in order to try to reconnect it manually, I 
found that there is only one SSID which previously the laptop connected to. 
However, I was definitely sure that there should be more than one SSID being 
showed in the wifi list. Even for this only one SSID, like I mentioned above, I 
cannot reconnect manually unless I reboot the system.
  Finally, I set the wifi to be connected automatically if I login to the 
system, however, it just can't. I can only to manually connect the wifi after I 
login to the account.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 19:02:12 2018
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file 

[Touch-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off

[Alberto Donato]

** Changed in: hplip (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: cups (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Installed network printer removed automatically when turned off

Status in cups package in Ubuntu:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  After installing artful, I configured my HP LaserJet M1212nf via network as 
usual via hp-setup.
  Installation worked and I could print/scan via network, but next time I 
needed to print, the printer was gone from the system.
  Basically, every time I need to print, I have to install the printer again.
  I'm not sure when the printer disappears, but I can reproduce consistently.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:33:12 2017
  InstallationDate: Installed on 2017-07-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.26

[Jeremy Bicha]

At this point, this would require a Feature Freeze Exception to be
considered for Ubuntu 18.04 LTS.

https://wiki.ubuntu.com/FreezeExceptionProcess

You would need to be sure that you would be able to complete the transition:
https://people.canonical.com/~ubuntu-archive/transitions/html/exiv2.html

Also, why don't you ask the Debian maintainer why this was uploaded to
experimental but not unstable yet?

** No longer affects: exiv2 (Ubuntu Bionic)

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

Title:
  Update to exiv2 version 0.26

Status in exiv2 package in Ubuntu:
  Triaged

Bug description:
  0.26 was released in April

  http://www.exiv2.org/whatsnew.html

  "This release contains a large collection of new features, new lenses
  and bugfixes across all areas of Exiv2. "

  Presumably debian stretch freeze interfered with a prompter update

  Currently in debian exp here:

  https://packages.debian.org/experimental/exiv2

  I was hoping to to get a new feature release of the very popular
  Digikam (5.7.0) into artful under a FFE, but that has bumped the
  minimum exiv2 build depend from 0.25 -> 0.26.

  If due to rdeps etc an update in artful turns out not to be possible,
  I would like to target this for early in 18.04 LTS cycle.

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

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

[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic

[Alejandro Mery]

I had to install ifupdown manually, and got 0.8.17ubuntu1. everything
fine now, but shouldn't this package be pulled in automatically somehow?

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in ifupdown package in Ubuntu:
  Fix Released

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

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

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

Re: [Touch-packages] [Bug 1757256] Re: Apparmor profile gajim

[george jetson]

Hello

I would really appreciate if you could tell me why this is being denied.
I'm trying to run truecrypt and it doesn't allow me to mount. I've
attached my profile.


AVC apparmor="DENIED" operation="mount" info="failed mntpnt match"
error=-13 profile="/usr/bin/truecrypt" name="/tmp/.truecrypt_aux_mnt4/"
pid=3769 comm="truecrypt" fstype="fuse.truecrypt"

SYSCALL arch=c03e syscall=165 success=no exit=-13 a0=160d4ff0
a1=160f9190 a2=1610a0c0 a3=6 items=1 ppid=949 pid=3769 auid=1000 uid=0
gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 t>



On 03/21/2018 10:09 PM, Seth Arnold wrote:
> (You will need to add it to all child subprofiles that execute in the
> other filesystem namespaces.)
>


** Attachment added: "usr.bin.truecrypt"
   
https://bugs.launchpad.net/bugs/1757256/+attachment/5089463/+files/usr.bin.truecrypt

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

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  New

Bug description:
  Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and 
saved usr.bin.gajim after scanning.
  After I restart machine and run Gajim from terminal I get:

  Fatal Python error: Py_Initialize: Unable to get the locale encoding
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0x6a383a1d5540 (most recent call first):
  Aborted (core dumped)

  If I delete the profile and restart machine it runs (to confirm it is
  profile causing).

  This is my current profile

  
  # vim:syntax=apparmor
  # --
  #
  #Copyright (C) 2015-2018 Mikhail Morfikov
  #
  #This program is free software; you can redistribute it and/or
  #modify it under the terms of version 2 of the GNU General Public
  #License published by the Free Software Foundation.
  #
  # --

  #include 

  /usr/bin/gajim {
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/usr/bin/gajim mr,

/usr/bin/ r,
/usr/local/bin/ r,

# Gajim plugins
/usr/share/gajim/plugins/ r,
/usr/share/gajim/plugins/** r,

# Gajim home files
owner @{HOME}/.config/gajim/ rw,
owner @{HOME}/.config/gajim/** rw,
owner @{HOME}/.local/share/gajim/ rw,
owner @{HOME}/.local/share/gajim/** rwk,

# User downloads
owner @{HOME}/[dD]ownload{,s}/ r,
owner @{HOME}/[dD]ownload{,s}/** rwl,
owner @{HOME}/[dD]esktop/ r,
owner @{HOME}/[dD]esktop/** rwl,

# Cache
owner /tmp/morfik_cache/.cache/gajim/ rwk,
owner /tmp/morfik_cache/.cache/gajim/** rwk,
owner @{HOME}/.cache/gajim/ rwk,
owner @{HOME}/.cache/gajim/** rwk,

# Deny access to webcam and mic
deny /dev/video0 rw,
deny /dev/v4l/by-path/ r,
deny /dev/snd/pcmC0D0c rw,

owner @{PROC}/@{pid}/mounts r,
owner @{PROC}/@{pid}/fd/ r,
owner @{PROC}/@{pid}/mountinfo r,

# External apps
/usr/lib/firefox/firefox rPUx,
/usr/bin/gpg rPUx,

/usr/share/glib-2.0/schemas/gschemas.compiled r,

owner /{,var/}run/user/[0-9]*/dconf/user rw,

# Silencer
deny /usr/lib/python3/dist-packages/** w,
deny /usr/share/gajim/plugins/** w,
deny @{HOME}/ r,

# Sounds
/usr/bin/aplay Cx -> audio,
/usr/bin/pacat Cx -> audio,
profile audio {
  #include 
  #include 

  /usr/bin/aplay mr,
  /usr/bin/pacat mr,

  owner @{HOME}/.Xauthority r,

  /etc/machine-id r,
  /var/lib/dbus/machine-id r,

}

/sbin/ldconfig Cx -> ldconfig,
profile ldconfig {
  #include 

  /sbin/ldconfig mr,

}

/bin/dash Cx -> dash,
profile dash {
  #include 

  /bin/dash mr,

  /bin/uname rix,

  /usr/bin/gpg rPUx,

}

  }

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

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

[Touch-packages] [Bug 1747460] Re: [MIR] py-macaroon-bakery, protobuf, pyrfc3339

[Steve Langasek]

FYI since the proximate dependency of maas has been promoted and
therefore allowed to migrate, but python-nacl has not, this currently
causes build failures of the ubuntu-server live image.

I am going to pre-promote python-nacl to unblock image builds.  Security
Team, can you please prioritize this review?

** Changed in: python-nacl (Ubuntu)
   Importance: Undecided => High

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

Title:
  [MIR] py-macaroon-bakery, protobuf, pyrfc3339

Status in protobuf package in Ubuntu:
  Invalid
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pyrfc3339 package in Ubuntu:
  Fix Released
Status in python-nacl package in Ubuntu:
  Incomplete

Bug description:
  py-macaroon-bakery
  ==

  1. Availability: all

  2. Rationale:
  Macaroons is a new form of authorization mechanism. The macaroon bakery 
builds on pymacaroons, which allows it working at a higher level.

  In order for MAAS (and other projects) to support macaroon based
  authentication, this needs to be in main. This will allow projects to
  support remote/centralized authentication based on macaroons.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:

  Dependencies in universe:
   - python3-pymacaroons (MIR LP: #1746772)
   - python3-nacl
   - python3-protobuf
   - python3-rfc3339

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 4.4.1

  8. Maintenance:
  Easy.

  9. Background information:
  This is a required dependency to implement third party/centralized 
authentication alongside with pymacaroons. This is a new dependency that's 
required by MAAS.

  python3-protobuf
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery. The library from this same source 
package, libprotobuf10, is already in main.

  3. Security:
  No CVE's

  4. QA:
  protobuf source, 10 bugs in debian, 11 ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 3.9.8

  8. Maintenance:
  Easy.

  9. Background information:
  protobuf source already has binaries in main. This is just the python 
bindings that are required by macaroonbakery.

  rfc3339
  ==

  1. Availability: all

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors. 1 warning:
  W: pyrfc3339 source: ancient-standards-version 3.9.6 (released 2014-09-17) 
(current is 4.1.3)

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  Parser and generator of RFC 3339-compliant timestamps. This is a dependency 
for python3-macaroonbakery.

  
  python-nacl
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Uses standards version 3.9.8

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  PyNaCl is a Python binding to the Networking and Cryptography library. This 
is a dependency for python3-macaroonbakery.

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

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

[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares

[Tronde]

Hello,

It's me again. So with today I've checked with three different hosts.
All running Xenial with autofs 5.1.1-1ubuntu3.1 and Kernel
4.4.0-116-generic. The host are a Thinkpad T410, X201 and a VirtualBox
guest system.

While the VirtualBox guest system works just fine, the autofs on the
Thinkpads did not work directly after boot. The autofs.service needs to
be restarted first in order to get autofs to work.

I have used tcpdump an strace to get some better look on what is
happening on the Thinkpads. So I did the following:

1. Boot Thinkpad
2. Setup tcpdump/wireshark snoop
3. Check that autofs is running with `sudo systemctl status autofs.service`
4. Run `strace ls -ld $MOUNTPOINT` where $MOUNTPOINT is the automounter share 
from automounter map

In strace I see:
lstat("$MOUNTPOINT", 0x14861a0)   = -1 ENOENT (No such file or directory)

The snoop shows that no single packet goes over the network to the NAS.
Next step:

5. Run `sudo systemctl status autofs.service`
6. Run `strace ls -ld $MOUNTPOINT` where $MOUNTPOINT is the automounter share 
from automounter map

Now, in strace I see:
lstat("$MOUNTPOINT", {st_mode=S_IFDIR|0777, st_size=0, ...}) = 0

And in the snoop I see the expected packages crossing the network.

That's it. I do not know what else I could do to help with this matter.
If you need additional information tell me what you need, please.

Regards,
Tronde

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

Title:
  [SRU] [xenial] autofs needs to be restarted to pick up some shares

Status in autofs package in Ubuntu:
  Fix Released
Status in autofs5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid
Status in autofs source package in Xenial:
  Incomplete

Bug description:
  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and
  Dapper.

  EDIT:  confirmed with similar configuration on Intrepid with a NetApp
  filer hosting NFS.  Server OS removed from summary.

  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs
  (/etc/init.d/autofs restart) everythin then works OK.  My config files
  are:

  auto.master

  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc/etc/auto.misc --timeout=60
  #/misc/etc/auto.misc
  #/net /etc/auto.net

  /petunia /etc/petunia.misc --timeout=60

  
  petunia.misc

  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage

  cd  -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

  tony  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/tony
  chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/chris
  shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/SharedDocs
  linuxbackups  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/linuxbackups

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

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

[Touch-packages] [Bug 1758569] [NEW] can't switch to bluetooth speakers

[david braun]

Public bug reported:

I'm not really sure this problem is with bluez, pulseaudio or firefox.
The main symptom is that Firefox refuses to send audio to my AD2P
compliant bluetooth speakers. I can select the speakers with the gnome-
control-center for bluetooth and play the test sounds (even while FF is
playing sound through the computer (DELL N7010 laptop) speakers. Even
VLC has the same problem so I suspect this is a system problem and not
an application problem.

Note - I installed pavucontrol and was able to switch the audio of a
playing youtube to the bluetooth speakers.

now for your recommended info
lsb_release says
Ubuntu 17.10
Firefox is Version 59.0.1
dpkg -l | grep -i blue  says
ii  bluez   5.46-0ubuntu3  amd64 Bluetooth 
tools and daemons
ii  bluez-cups  5.46-0ubuntu3  amd64 Bluetooth 
printer driver for CUPS
ii  bluez-obexd 5.46-0ubuntu3  amd64 bluez obex 
daemon
ii  bluez-tools 0.2.0~20140808-5build1 amd64 Set of 
tools to manage Bluetooth devices for linux
ii  gir1.2-gnomebluetooth-1.0:amd64 3.26.1-1   amd64 
Introspection data for GnomeBluetooth
ii  gnome-bluetooth 3.26.1-1   amd64 GNOME 
Bluetooth tools
ii  libbluetooth3:amd64 5.46-0ubuntu3  amd64 Library to 
use the BlueZ Linux Bluetooth stack
ii  libgnome-bluetooth13:amd64  3.26.1-1   amd64 GNOME 
Bluetooth tools - support library
ii  pulseaudio-module-bluetooth 1:10.0-2ubuntu3.1  amd64 Bluetooth 
module for PulseAudio sound server

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: bluez 5.46-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 24 14:10:02 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-03-19 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Inspiron N7010
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=94a7c54a-20a6-4bd0-905c-918de9b5ff61 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 08VFX1
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11:
dmi.product.name: Inspiron N7010
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: C0:CB:38:C2:18:51  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING INQUIRY 
RX bytes:234685 acl:43 sco:0 events:33407 errors:0
TX bytes:56372584 acl:66043 sco:0 commands:212 errors:0

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


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

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

Title:
  can't switch to bluetooth speakers

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm not really sure this problem is with bluez, pulseaudio or firefox.
  The main symptom is that Firefox refuses to send audio to my AD2P
  compliant bluetooth speakers. I can select the speakers with the
  gnome-control-center for bluetooth and play the test sounds (even
  while FF is playing sound through the computer (DELL N7010 laptop)
  speakers. Even VLC has the same problem so I suspect this is a system
  problem and not an application problem.

  Note - I installed pavucontrol and was able to switch the audio of a
  playing youtube to the bluetooth speakers.

  now for your recommended info
  lsb_release says
  Ubuntu 17.10
  Firefox is Version 59.0.1
  dpkg -l | grep -i blue  says
  ii  bluez   5.46-0ubuntu3  amd64 
Bluetooth tools and daemons
  ii  bluez-cups  5.46-0ubuntu3  amd64 
Bluetooth printer driver for CUPS
  ii  bluez-obexd 5.46-0ubuntu3  amd64 bluez 
obex daemon
  ii  bluez-tools 0.2.0~20140808-5build1 amd64 Set of 
tools to manage Bluetooth devices for linux
  ii  gir1.2-gnomebluetooth-1.0:amd64 3.26.1-1   amd64 
Introspection data for GnomeBluetooth
  ii  gnome-bluetooth 3.26.1-1   amd64 GNOME 
Bluetooth tools
  ii  libbluetooth3:amd64  

[Touch-packages] [Bug 1758565] 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/1758565/+attachment/5089343/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758565/+attachment/5089353/+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/1758565

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in perl package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 18:26:45 2018
  ExecutablePath: /usr/bin/perl
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-03-11 (13 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin lxd plugdev sambashare sudo

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

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

Re: [Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

[Serge Hallyn]

Could you find the pid of cgmanager ( 353 below)‎ and do

Strafe -f -p 353 -o trace.txt

for maybe 5 seconds, ctrl-c it, and attach trace.txt here?

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

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in cgmanager package in Ubuntu:
  Invalid
Status in libnih package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
 
676 root  20   0   43644   2144   1568 R 100.0  0.0  74:43.77 
systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

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

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

[Touch-packages] [Bug 1738582] Re: [MIR] ibus-libpinyin and dependencies

[Ping-Wu]

As of today, the ibus-libpinyin package has replaced ibus-sunpinyin.
This is a move in the right direction.  (Finally !)

However, the default Chinese input still points to ibus-sunpinyin,
resulting in users unable to input Chinese characters, even when
selecting (simplified) Chinese locale during the liveUSB boot.

The default Chinese input method should also change to ibus-libpinyin.

Thanks.

Related bug report:

https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1756205

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

Title:
  [MIR] ibus-libpinyin and dependencies

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released

Bug description:
  Please include these packages in Ubuntu's component main:

  * ibus-libpinyin
  * libpinyin (the ibus-libpinyin binary depends on libpinyin13)

  As has been discussed at bug #1735362 we would like to replace ibus-
  sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
  and as the default input method for typing Simplified Chinese. Reasons
  for the switch are:

  - ibus-libpinyin is better maintained
  - ibus-libpinyin is built with and depends on Python3
  - ibus-libpinyin is default input method in GNOME

  Bugs ibus-libpinyin
  ---
  https://github.com/libpinyin/ibus-libpinyin/issues

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin

  https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin

  Bugs libpinyin
  --
  https://github.com/libpinyin/libpinyin/issues

  (no open Debian or Ubuntu bugs)

  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
  and haven't found any issues that would prevent the proposed main
  inclusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+subscriptions

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

[Touch-packages] [Bug 1689239] Re: Headerbar used as toolbars in unity are missing proper css classes

[Jeremy Bicha]

Marco, can we close this bug as obsolete now?

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

Title:
  Headerbar used as toolbars in unity are missing proper css classes

Status in Mahjongg:
  Confirmed
Status in GNOME Software:
  Fix Released
Status in baobab package in Ubuntu:
  In Progress
Status in eog package in Ubuntu:
  Triaged
Status in epiphany package in Ubuntu:
  Triaged
Status in evince package in Ubuntu:
  In Progress
Status in file-roller package in Ubuntu:
  In Progress
Status in gnome-contacts package in Ubuntu:
  In Progress
Status in gnome-mahjongg package in Ubuntu:
  Triaged
Status in gnome-software package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  In Nautilus, Gnome-Software, Gnome-Contacts, gnome-mahjongg the
  headerbar in unity is used as a toolbar, but without applying the
  proper .primary-toolbar class, which leads to make impossible to use
  Unity themes properly in other environments (as GS) as they try to
  apply a toolbar-like theme to any headerbar that is not a titlebar
  (which might be in cases such as gedit, where custom widgets are
  heavily used).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-mahjongg/+bug/1689239/+subscriptions

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

Re: [Touch-packages] [Bug 1674078] Re: PCI/internal sound card not detected

[mippo]

Just tested 18.08 Bionic.
Nothing changed, sound card and touchpad not recognized.
Sadly still using windows

2018-03-01 23:17 GMT+01:00 Simon Quigley :

> Marking as Invalid because the release is EOL is not correct. Marking as
> Incomplete. Also, 18.04 is (at the time of writing) still in development,
> and you should expect some breakage.
> https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_
> End_of_Life_.28EOL.29
>
> Reporter, is this still present on 17.10 or 16.04?
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: Invalid => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1674078
>
> Title:
>   PCI/internal sound card not detected
>
> Status in alsa-driver package in Ubuntu:
>   Incomplete
>
> Bug description:
>   hello,
>
>   on a PC: HP-x2-Detachable-10-p008
>   the System Setting, in the Audio section, shows: "Output dummy"
>
>   the command: cat /proc/asound/cards
>
>   returns: - - - no souncard - - -
>
>   (under windows the sound works)
>
>
>   thanks for help
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   Uname: Linux 4.10.3-041003-lowlatency x86_64
>   ApportVersion: 2.20.3-0ubuntu8.2
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   Date: Sun Mar 19 11:10:11 2017
>   InstallationDate: Installed on 2017-02-26 (21 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: PCI/internal sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 09/30/2016
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F.11
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 827C
>   dmi.board.vendor: HP
>   dmi.board.version: 93.22
>   dmi.chassis.type: 32
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:
> pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:
> ct32:cvrChassisVersion:
>   dmi.product.name: HP x2 Detachable 10-p0XX
>   dmi.sys.vendor: HP
>   mtime.conffile..etc.modprobe.d.alsa-base.conf:
> 2017-02-27T02:14:40.994094
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+
> bug/1674078/+subscriptions
>

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  hello,

  on a PC: HP-x2-Detachable-10-p008
  the System Setting, in the Audio section, shows: "Output dummy"

  the command: cat /proc/asound/cards

  returns: - - - no souncard - - -

  (under windows the sound works)

  
  thanks for help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.10.3-041003-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Mar 19 11:10:11 2017
  InstallationDate: Installed on 2017-02-26 (21 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.22
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-27T02:14:40.994094

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

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

Re: [Touch-packages] [Bug 1674078] Re: PCI/internal sound card not detected

[mippo]

18.04 ;-)

2018-03-24 18:02 GMT+01:00 Mario Ippoliti :

> Just tested 18.08 Bionic.
> Nothing changed, sound card and touchpad not recognized.
> Sadly still using windows
>
> 2018-03-01 23:17 GMT+01:00 Simon Quigley :
>
>> Marking as Invalid because the release is EOL is not correct. Marking as
>> Incomplete. Also, 18.04 is (at the time of writing) still in development,
>> and you should expect some breakage.
>> https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_E
>> nd_of_Life_.28EOL.29
>>
>> Reporter, is this still present on 17.10 or 16.04?
>>
>> ** Changed in: alsa-driver (Ubuntu)
>>Status: Invalid => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1674078
>>
>> Title:
>>   PCI/internal sound card not detected
>>
>> Status in alsa-driver package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   hello,
>>
>>   on a PC: HP-x2-Detachable-10-p008
>>   the System Setting, in the Audio section, shows: "Output dummy"
>>
>>   the command: cat /proc/asound/cards
>>
>>   returns: - - - no souncard - - -
>>
>>   (under windows the sound works)
>>
>>
>>   thanks for help
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 16.10
>>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>>   Uname: Linux 4.10.3-041003-lowlatency x86_64
>>   ApportVersion: 2.20.3-0ubuntu8.2
>>   Architecture: amd64
>>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
>> '/dev/snd/timer'] failed with exit code 1:
>>   CurrentDesktop: Unity
>>   Date: Sun Mar 19 11:10:11 2017
>>   InstallationDate: Installed on 2017-02-26 (21 days ago)
>>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
>> (20161012.2)
>>   PackageArchitecture: all
>>   SourcePackage: alsa-driver
>>   Symptom: audio
>>   Title: PCI/internal sound card not detected
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 09/30/2016
>>   dmi.bios.vendor: American Megatrends Inc.
>>   dmi.bios.version: F.11
>>   dmi.board.asset.tag: Base Board Asset Tag
>>   dmi.board.name: 827C
>>   dmi.board.vendor: HP
>>   dmi.board.version: 93.22
>>   dmi.chassis.type: 32
>>   dmi.chassis.vendor: HP
>>   dmi.chassis.version: Chassis Version
>>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:
>> bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP
>> :rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
>>   dmi.product.name: HP x2 Detachable 10-p0XX
>>   dmi.sys.vendor: HP
>>   mtime.conffile..etc.modprobe.d.alsa-base.conf:
>> 2017-02-27T02:14:40.994094
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/
>> 1674078/+subscriptions
>>
>
>

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  hello,

  on a PC: HP-x2-Detachable-10-p008
  the System Setting, in the Audio section, shows: "Output dummy"

  the command: cat /proc/asound/cards

  returns: - - - no souncard - - -

  (under windows the sound works)

  
  thanks for help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.10.3-041003-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Mar 19 11:10:11 2017
  InstallationDate: Installed on 2017-02-26 (21 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.22
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-27T02:14:40.994094

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

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

[Touch-packages] [Bug 1758318] Re: Sync 0.0.12 from Debian

[Jeremy Bicha]

This bug was fixed in the package sensible-utils - 0.0.12
Sponsored for Amr Ibrahim (amribrahim1987)

---
sensible-utils (0.0.12) unstable; urgency=medium

  * Fix sensible-browser launches $BROWSER with empty argument
(Closes: #885688)
  * Bug fix: "[INTL:de] updated German man page translation", thanks to
Helge Kreutzmann (Closes: #877553).
  * Add basic testing.
  * Bump compat and policy (no changes)

 -- Bastien Roucariès   Mon, 12 Mar 2018 11:17:53
+0100

** Changed in: sensible-utils (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync 0.0.12 from Debian

Status in sensible-utils package in Ubuntu:
  Fix Released

Bug description:
  Please sync 0.0.12 from Debian. It's a bug-fix release.

  sensible-utils (0.0.12) unstable; urgency=medium

* Fix sensible-browser launches $BROWSER with empty argument
  (Closes: #885688)
* Bug fix: "[INTL:de] updated German man page translation", thanks to
  Helge Kreutzmann (Closes: #877553).
* Add basic testing.
* Bump compat and policy (no changes)

   -- Bastien Roucariès   Mon, 12 Mar 2018 11:17:53
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1758318/+subscriptions

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

[Touch-packages] [Bug 1751261] Re: libgweather-locations.pot generation fails with bionic meson

[Jeremy Bicha]

This bug was fixed in the package gettext - 0.19.8.1-5

---
gettext (0.19.8.1-5) unstable; urgency=medium

  * Fix heap corruption in msgunfmt. Patch from Bruno Haible taken from
upstream git. Thanks to Jakub Wilk. Closes: #876498.
  * Recommend lynx instead on lynx-cur.
Thanks to Axel Beckert for the report. Closes: #882284.
  * Stop xgettext() from crashing when run with --its=FILE option.
Patch taken from git. Thanks to Gunnar Hjalmarsson. Closes: #891347.
  * Support "nojava" instead of "stage1" in DEB_BUILD_PROFILES.
Thanks to Manuel Fernández Montecelo. Closes: #893064.
  * Build with OpenJDK 9. Patch from Tiago Stürmer Daitx, adapted
from openSUSE. Thanks a lot. Closes: #893739.
  * Move libgettextsrc, libgettextlib, and preloadable_libintl
to multiarch directory as done on Ubuntu.
  * Use https in Bug-Debian field of Debian patches.

 -- Santiago Vila   Sat, 24 Mar 2018 12:24:50 +0100

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

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

Title:
  libgweather-locations.pot generation fails with bionic meson

Status in libgweather:
  Unknown
Status in Ubuntu Translations:
  Fix Released
Status in gettext package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gettext package in Debian:
  New

Bug description:
  From bionic:

  Change to the libgweather source directory and run

  sudo apt build-dep libgweather
  dh_auto_configure
  dh_auto_build

  ninja -v -C obj-x86_64-linux-gnu/ libgweather-3.0-pot
  ninja -v -C obj-x86_64-linux-gnu/ libgweather-locations-pot

  For reference, the second to last command succeeds with this output:
  ---
  ninja -v -C obj-x86_64-linux-gnu/ libgweather-3.0-pot
  ninja: Entering directory `obj-x86_64-linux-gnu/'
  [0/1] /usr/bin/python3 /usr/bin/meson --internal commandrunner 
/home/jeremy/devel/libgweather 
/home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po /usr/bin/python3 
/usr/bin/meson /usr/bin/python3 /usr/bin/meson --internal gettext pot 
--pkgname=libgweather-3.0 
--extra-args=--keyword=_@@--add-comments@@--flag=g_set_error:4:c-format@@--flag=N_:1:pass-c-format@@--flag=g_dngettext:2:pass-c-format@@--keyword=NC_:1c,2@@--flag=g_error_new:3:c-format@@--from-code=UTF-8@@--keyword=g_dpgettext2:2c,3@@--keyword=C_:1c,2@@--keyword=g_dngettext:2,3@@--keyword=N_@@--flag=g_string_printf:2:c-format@@--flag=g_string_append_printf:2:c-format@@--flag=C_:2:pass-c-format@@--keyword=g_dcgettext:2@@--flag=NC_:2:pass-c-format@@--flag=g_strdup_printf:1:c-format

  The last command fails with this output:
  ---
  ninja: Entering directory `obj-x86_64-linux-gnu/'
  [0/1] /usr/bin/python3 /usr/bin/meson --internal commandrunner
   /home/jeremy/devel/libgweather
   /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po-locations
   /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson
   --internal gettext pot --pkgname=libgweather-locations
   
--extra-args=--its@@/home/jeremy/devel/libgweather/po-locations/../data/locations.its
  FAILED: meson-libgweather-locations-pot
  /usr/bin/python3 /usr/bin/meson --internal commandrunner
   /home/jeremy/devel/libgweather
   /home/jeremy/devel/libgweather/obj-x86_64-linux-gnu po-locations
   /usr/bin/python3 /usr/bin/meson /usr/bin/python3 /usr/bin/meson
   --internal gettext pot --pkgname=libgweather-locations
   
--extra-args=--its@@/home/jeremy/devel/libgweather/po-locations/../data/locations.its
  ninja: build stopped: subcommand failed.

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

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

[Touch-packages] [Bug 1758551] Re: bionic install uses 3.26 gnome snaps instead of 3.28 packages

[Jeremy Bicha]

This issue is being tracked by the Ubuntu Desktop Team at

https://trello.com/c/1R0lryqL/183-gnome-328-platform-snap

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

** Package changed: ubuntu-meta (Ubuntu) => gnome-platform-snap

** Changed in: gnome-platform-snap
   Status: Invalid => Triaged

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

Title:
  bionic install uses 3.26 gnome snaps instead of 3.28 packages

Status in gnome-platform-snap:
  Triaged

Bug description:
  The current bionic installer is incorrectly installing snap versions
  of gnome-calculator, gnome-characters and gnome-system-monitor from
  the Gnome 3.26 release rather than the newer 3.28 normal deb packages
  present in the bionic repo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-platform-snap/+bug/1758551/+subscriptions

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

[Touch-packages] [Bug 1758551] Re: bionic install uses 3.26 gnome snaps instead of 3.28 packages

[Simon Quigley]

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

** No longer affects: ubuntu

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

Title:
  bionic install uses 3.26 gnome snaps instead of 3.28 packages

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The current bionic installer is incorrectly installing snap versions
  of gnome-calculator, gnome-characters and gnome-system-monitor from
  the Gnome 3.26 release rather than the newer 3.28 normal deb packages
  present in the bionic repo.

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

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

[Touch-packages] [Bug 331749] Re: Adding %armel% to NOJAVA_ARCHS ...

[Jeremy Bicha]

Ubuntu no longer supports the armel architecture so I'm closing this
bug.

I apologize that we aren't always able to respond to bug reports
promptly. Please do report any other issues you find.

** Changed in: gettext (Ubuntu)
   Status: New => Invalid

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

Title:
  Adding %armel% to NOJAVA_ARCHS ...

Status in gettext package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gettext

  When I have rebuilded the source of gettext ( apt-get source gettext ) and 
repacked it by dpkg-buildpackage on the crosscompiler I had to change 
NOJAVA_ARCHS = %hppa% to NOJAVA_ARCHS = %hppa%armel% before,
  because there is no java available for this target (armel)... 

  Finally I have edited the control-file, too, because of the
  dependences of java, which I simply removed instead of editing [!hppa]
  to [!hppa,!armel], or however it has to be...

  It would be very kind if you take care of this in your next source-
  package of gettext :)

  greetings

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

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

[Touch-packages] [Bug 1758544] [NEW] On unsuspend, a black screen delays login screen

[linsnux]

Public bug reported:

Every time I suspend the notebook (close lid, not sure about suspension
by command) when I unsuspend (open lid) a long time black screen with
only mouse pointer visible delays the login screen to display (about
10~15 seconds of delaying). The mouse pointer works but with brief
freezings when moving, something like 0,5s of freezing for each 1,5s
moving.

This notebook is a i7 16GB ram 120GB SSD so it should never happen, in
fact, it never happened in Deepin Linux or even Ubuntu 16.04.

I will be available to provide some other information you need.
Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1)
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 24 12:26:54 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.42, 4.15.0-12-generic, x86_64: installed
 virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840]
InstallationDate: Installed on 2018-03-09 (14 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 009: ID 04f2:b446 Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 248a:8366  
 Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite S55t-C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.20
dmi.board.name: 06F4
dmi.board.vendor: FF50
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: Satellite S55t-C
dmi.product.version: PSPUGU-00200D
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic reproducible 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/1758544

Title:
  On unsuspend, a black screen delays login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time I suspend the notebook (close lid, not sure about
  suspension by command) when I unsuspend (open lid) a long time black
  screen with only mouse pointer visible delays the login screen to
  display (about 10~15 seconds of delaying). The mouse pointer works but
  with brief freezings when moving, something like 0,5s of freezing for
  each 1,5s moving.

  This notebook is a i7 16GB ram 120GB SSD so it should never happen, in
  fact, it never happened in Deepin Linux or even Ubuntu 16.04.

  I will be available to provide some other information you need.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretóri

[Touch-packages] [Bug 1758539] Re: totem-video-thumbnailer crashed with signal 5 in g_malloc()

[Apport retracing service]

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

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 #1697234, 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/1758539/+attachment/5089157/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1697234
   totem-video-thumbnailer crashed with SIGTRAP in g_malloc() from 
g_slice_alloc() from _sysmem_new_block() from gst_buffer_new_allocate()

** 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 gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1758539

Title:
  totem-video-thumbnailer crashed with signal 5 in g_malloc()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Happened when using Chromium

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Mar 24 16:07:12 2018
  ExecutablePath: /usr/bin/totem-video-thumbnailer
  InstallationDate: Installed on 2017-09-11 (193 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 
file:///home/username/Downloads/PE2_Leopard_4K.mkv 
/tmp/.gnome_desktop_thumbnail.CAFRGZ
  Signal: 5
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_malloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_buffer_new_allocate () at /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
  Title: totem-video-thumbnailer crashed with signal 5 in g_malloc()
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (126 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[mm]

Its just a shame that no one is interested in this bug. Debian Stretch
doesn't have this bug btw and bugs get fixed more quickly there ...

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Confirmed
Status in cryptsetup package in Ubuntu:
  Confirmed

Bug description:
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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

[Touch-packages] [Bug 1758449] Re: skype snap does not work when home directory is not located in /home

[Georges]

I did the HOMEDIRS thing, still not working

$ cat /etc/apparmor.d/tunables/home.d/my-homes 
# set to parent directory of your user's directories. Eg, if user's dir is 
/foo/bar/USER,
# set this to /foo/bar/
@{HOMEDIRS}+=/data/home/

$ sudo service apparmor reload
$ skype
2018/03/24 14:01:56.276095 cmd_run.go:343: WARNING: XAUTHORITY environment 
value is not a clean path: "/data/home/georges/.Xauthority"
cannot create user data directory: /data/home/georges/snap/skype/23: Permission 
denied

$ sudo tail -2 /var/log/syslog
Mar 24 14:00:13 breeze anacron[30046]: Normal exit (0 jobs run)
Mar 24 14:01:56 breeze kernel: [6636053.148494] audit: type=1400 
audit(1521896516.286:6903): apparmor="DENIED" operation="open" 
profile="/snap/core/4206/usr/lib/snapd/snap-confine" name="/data/" pid=30123 
comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0


I would like to add /data/home to 
/etc/apparmor.d/snap.core.4206.usr.lib.snapd.snap-confine but it's 
uncomprehensible to me.

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

Title:
  skype snap does not work when home directory is not located in /home

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi

  similar to this bug around libreoffice
  (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005),
  apparmor makes the skype snap not work without any information except
  this:

  cannot create user data directory: /data/home/georges/snap/skype/23:
  Permission denied

  despite the directory being writeable.

  It would really be advisable to make apparmor specific errors, else
  end-users will never determine where the error comes from.

  The error is here:
  Mar 23 22:35:08 breeze kernel: [6580445.024083] audit: type=1400 
audit(1521840908.018:6807): apparmor="DENIED" operation="open" 
profile="/snap/core/4206/usr/lib/snapd/snap-confine" name="/data/" pid=7213 
comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0

  I tried to remove the problem like this:
  sudo apparmor_parser -R 
/etc/apparmor.d/snap.core.4206.usr.lib.snapd.snap-confine 

  Which gives a new issue
  $ skype
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 23 22:38:16 2018
  InstallationDate: Installed on 2017-09-20 (184 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to artful on 2018-01-31 (50 days ago)

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

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

[Touch-packages] [Bug 1706126] Re: XDG_DATA_DIRS XDG_CONFIG_DIRS MANDATORY_PATH DEFAULTS_PATH are not set correctly

[Timo Aaltonen]

fixed in bionic

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

** Changed in: xorg-server
   Status: New => Fix Released

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

Title:
  XDG_DATA_DIRS XDG_CONFIG_DIRS MANDATORY_PATH DEFAULTS_PATH are not set
  correctly

Status in X.Org X server:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  after login to my plasma session I noticed the following strange path
  in some XDG env variables missing the : separator

  pascal@minipc:~$ env | grep XDG 
  XDG_VTNR=7
  XDG_SESSION_ID=264
  XDG_SESSION_TYPE=x11
  
XDG_DATA_DIRS=/home/pascal/kde/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
  XDG_SESSION_DESKTOP=KDE
  XDG_SESSION_CLASS=user
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  XDG_CURRENT_DESKTOP=KDE
  XDG_SEAT=seat0
  XDG_RUNTIME_DIR=/run/user/1026
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session5
  
XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings

  pascal@minipc:~$ env | grep PATH
  LD_LIBRARY_PATH=/home/pascal/kde/lib:
  MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
  DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session5
  
PATH=/usr/lib/ccache:/home/pascal/kde/bin:/home/pascal/bin:/home/pascal/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

  As you see the following 2 env variables are not setup correctly :

  pascal@minipc:~$ env | grep PATH | grep '//'
  MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
  DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path

  The same for :

  pascal@minipc:~$ env | grep XDG | grep '//'
  
XDG_DATA_DIRS=/home/pascal/kde/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop

  You can also notice the 'xdg-/usr/xxx' in the following :

  XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share
  /kubuntu-default-settings/kf5-settings

  For XDG variables they seem to be set up here :

  pascal@minipc:~$ dpkg -S /etc/X11/Xsession.d/60x11-common_xdg_path
  x11-common: /etc/X11/Xsession.d/60x11-common_xdg_path

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-common 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32-lowlatency 4.10.17
  Uname: Linux 4.10.0-28-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jul 24 18:51:03 2017
  Dependencies: lsb-base 9.20160110ubuntu5
  InstallationDate: Installed on 2016-05-14 (436 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1706126/+subscriptions

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

[Touch-packages] [Bug 1706126] Re: XDG_DATA_DIRS XDG_CONFIG_DIRS MANDATORY_PATH DEFAULTS_PATH are not set correctly

[Kenneth Hanson]

I have the this problem on Xenial. Double slash in XDG_DATA_DIRS and a
minus in XDG_CONFIG_DIRS.

Even worse, when I tried to append paths for Flatpak to XDG_DATA_DIRS
using an .env file in my home directory, the result was so broken that
Plasma failed to start. I've undone the change since then, but I
remember a double colon in there, and my additions appearing in the
middle of the string rather than the beginning or end as expected.

This seems rather serious to me.

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

Title:
  XDG_DATA_DIRS XDG_CONFIG_DIRS MANDATORY_PATH DEFAULTS_PATH are not set
  correctly

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after login to my plasma session I noticed the following strange path
  in some XDG env variables missing the : separator

  pascal@minipc:~$ env | grep XDG 
  XDG_VTNR=7
  XDG_SESSION_ID=264
  XDG_SESSION_TYPE=x11
  
XDG_DATA_DIRS=/home/pascal/kde/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
  XDG_SESSION_DESKTOP=KDE
  XDG_SESSION_CLASS=user
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  XDG_CURRENT_DESKTOP=KDE
  XDG_SEAT=seat0
  XDG_RUNTIME_DIR=/run/user/1026
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session5
  
XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings

  pascal@minipc:~$ env | grep PATH
  LD_LIBRARY_PATH=/home/pascal/kde/lib:
  MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
  DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session5
  
PATH=/usr/lib/ccache:/home/pascal/kde/bin:/home/pascal/bin:/home/pascal/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

  As you see the following 2 env variables are not setup correctly :

  pascal@minipc:~$ env | grep PATH | grep '//'
  MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
  DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path

  The same for :

  pascal@minipc:~$ env | grep XDG | grep '//'
  
XDG_DATA_DIRS=/home/pascal/kde/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop

  You can also notice the 'xdg-/usr/xxx' in the following :

  XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share
  /kubuntu-default-settings/kf5-settings

  For XDG variables they seem to be set up here :

  pascal@minipc:~$ dpkg -S /etc/X11/Xsession.d/60x11-common_xdg_path
  x11-common: /etc/X11/Xsession.d/60x11-common_xdg_path

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-common 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32-lowlatency 4.10.17
  Uname: Linux 4.10.0-28-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jul 24 18:51:03 2017
  Dependencies: lsb-base 9.20160110ubuntu5
  InstallationDate: Installed on 2016-05-14 (436 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1706126/+subscriptions

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

[Touch-packages] [Bug 1706126] Re: XDG_DATA_DIRS XDG_CONFIG_DIRS MANDATORY_PATH DEFAULTS_PATH are not set correctly

[Launchpad Bug Tracker]

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

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

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

Title:
  XDG_DATA_DIRS XDG_CONFIG_DIRS MANDATORY_PATH DEFAULTS_PATH are not set
  correctly

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after login to my plasma session I noticed the following strange path
  in some XDG env variables missing the : separator

  pascal@minipc:~$ env | grep XDG 
  XDG_VTNR=7
  XDG_SESSION_ID=264
  XDG_SESSION_TYPE=x11
  
XDG_DATA_DIRS=/home/pascal/kde/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
  XDG_SESSION_DESKTOP=KDE
  XDG_SESSION_CLASS=user
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  XDG_CURRENT_DESKTOP=KDE
  XDG_SEAT=seat0
  XDG_RUNTIME_DIR=/run/user/1026
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session5
  
XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings

  pascal@minipc:~$ env | grep PATH
  LD_LIBRARY_PATH=/home/pascal/kde/lib:
  MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
  DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path
  XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session5
  
PATH=/usr/lib/ccache:/home/pascal/kde/bin:/home/pascal/bin:/home/pascal/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

  As you see the following 2 env variables are not setup correctly :

  pascal@minipc:~$ env | grep PATH | grep '//'
  MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
  DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path

  The same for :

  pascal@minipc:~$ env | grep XDG | grep '//'
  
XDG_DATA_DIRS=/home/pascal/kde/share:/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop

  You can also notice the 'xdg-/usr/xxx' in the following :

  XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share
  /kubuntu-default-settings/kf5-settings

  For XDG variables they seem to be set up here :

  pascal@minipc:~$ dpkg -S /etc/X11/Xsession.d/60x11-common_xdg_path
  x11-common: /etc/X11/Xsession.d/60x11-common_xdg_path

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-common 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32-lowlatency 4.10.17
  Uname: Linux 4.10.0-28-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jul 24 18:51:03 2017
  Dependencies: lsb-base 9.20160110ubuntu5
  InstallationDate: Installed on 2016-05-14 (436 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1706126/+subscriptions

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

[Touch-packages] [Bug 1758519] Re: apport-gtk crashed with SIGSEGV

[Apport retracing service]

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

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 #1552577, 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/1758519/+attachment/5088992/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV in 
_gtk_style_provider_private_get_settings(provider=0x0) 
[gtkstyleproviderprivate.c:123]

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  When I connect with xrdp from remote computer, this error happens
  mostly.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.8-0ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 24 12:12:11 2018
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-10-07 (168 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171006)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  SegvAnalysis:
   Segfault happened at: 0x7f194d3a55a9:mov(%rbx),%rdi
   PC (0x7f194d3a55a9) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (27 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video

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

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

[Touch-packages] [Bug 1485258] Re: Nvidia 340+NVidia Prime + external monitor = system unusable, continuous xorg crashes, external monitor never works

[Kecskés Krisztián]

** Also affects: xorg-server
   Importance: Undecided
   Status: New

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

Title:
  Nvidia 340+NVidia Prime + external monitor = system unusable,
  continuous xorg crashes, external monitor never works

Status in X.Org X server:
  New
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  SUMMARY

  - laptop with NVidia card and Optimus technology
  - xorg configured ages ago to automatically switch between built-in and 
external monitor when plugging/unplugging
  - "clean" Ubuntu 15.04 after upgrading from 14.10 from 14.04
  - no nvidia-* nor bumblebee-* was installed (that's what I mean by "clean")
  - everything was working perfectly fine while only using integrated intel GPU
  - I installed NVidia-340 and nvidia-prime (and whatever) via Software & 
Updates -> Additional Driver

  Result:
  * Boot with external monitor connected => keeps crashing forever at the login 
screen
  * Boot without external monitor connected => seems to work with built-in 
screen (at least for the few minutes I tested)
  * Connect external monitor after boot at login screen => xorg crashes once or 
twice, then both screens go black
  * Connect external monitor after logging in => both screens go black
  * Disconnect external monitor => built-in screen remains black, never turns 
on again, unless Xorg crashes

  Basically, the laptop is completely unusable. NVidia-prime and nvidia-340 
screw everything up beyond imagination.
  I was lucky tojust  be able to recover from that, uninstall all nvidia-stuff, 
and get my working system back.

  
  MORE DETAIL

  Until recently I had Ubuntu 14.04.
  I had nvidia-331 installed but unused since ages ago. I had disabled them (if 
I remember correctly) by going to 
Software & Updates -> Additional drivers 
  (the same I had used to install them)
  and choosing to use Nouveau instead (back), because I had experiencing a lot 
of glitches with NVidia-331.
  This was even before I upgraded to 14.04.

  Because my laptop has Optimus technology, I was only using the
  integrated Intel GPU.

  At some point I had also installed bumblebee, but I had never figured
  out how to actually make any use of it.

  I had Xorg configured so that, when plugging an external monitor, only
  the external monitor would be used and the built-in one would turn
  off; and when unplugging the external monitor, the built-in monitor
  would automatically turn on. So I only use one monitor at a time. I
  guess I configured this via the System Settings -> Displays

  All this was working fine.

  When the fix for #1431753  was released, nvidia-340 got installed and,
  against my will and without notice, they were somehow enabled, so I
  started experiencing  #1220426 and  #1483388 (but nothing comparable
  to what I'm describing in this report).

  So, I apt-get removed nvidia-* and bumblebee.

  After that (and across several reboots) all was working perfectly fine
  again. Again, I was only using the shitty integrated Intel GPU
  (without even the hardware acceleration that it supports, btw, but
  that's another story), but I had no issues.

  Then today I upgraded to 14.10 and immediately after, to 15.04.

  Everything kept working smoothly, including automatic screen switching
  when plugging/unplugging the external monitor.

  
  Then I thoughy I'd give NVidia-340 another try. I thought maybe a fresh 
install on 15.04 would work.

  I went to Software & updates -> Additional Drivers and I selected "use
  NVidia-340"

  That installed nvidia-340, nvidia-settings, nvidia-prime, and
  something-nvidia-else.

  I rebooted.

  At the first reboot, I had the external screen already connected.

  After the boot completed, xorg started to crash again and again like crazy. 
The login screen would appear and disappear from both screen at a few seconds 
intervals, and I would hear the drum sound every time (and could not finish 
typing my password and logging in).
  THE SYSTEM WAS UNUSABLE, I COULD NOT LOG IN.

  So I rebooted without the external monitor connected.
  I then connected the external monitor while still at the login screen. Xorg 
crashed one or a couple of times, then the built-in screen turned off but the 
external one didn't turn on either.
  So I disconnected the screen; after a while Xorg crashed again and only then 
the built-in screen turned on again
  I rebooted again, and fully logged in without the external screen connected.
  Then I plugged in the screen
  => again, the built-in screen turned off but the external one didn't turn on.
  I disconnected the screen, and the built-in screen never turned on again.

  
  So, I rebooted without the external monitor, uninstalled all the 
nvidia-related

[Touch-packages] [Bug 1757952] Re: FFe request for Mir 0.31.0.1

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.31.0.1-0ubuntu1

---
mir (0.31.0.1-0ubuntu1) bionic; urgency=medium

  * New upstream release 0.31.0 (LP: #1757952)
- ABI summary:
  + mirclient ABI unchanged at 9
  + miral ABI bumped to 3
  + mirserver ABI bumped to 46
  + mircommon ABI unchanged at 7
  + mirplatform ABI unchanged at 16
  + mirprotobuf ABI unchanged at 3
  + mirplatformgraphics ABI unchanged at 13
  + mirclientplatform ABI unchanged at 5
  + mirinputplatform ABI unchanged at 7
  + mircore ABI unchanged at 1
- Enhancements:
  + Miral version 2.0 - API cleanup and support for CSD initiated "resize"
  + Reorganized examples and reworked miral server examples
  + Better organization of, and fixes to, Wayland server code
  + Initial support for Wayland xdg-shell
- Bugs fixed:
  + [miral] CommandLineOption should accept lambdas (Fixes #215)
  + [miral] Implement the policy addenda in WindowManagementTrace
(Fixes #192)
  + [Wayland] Send repeat info (Fixes #180)
  + Explicitly initialise glm matricies, (Fixes #200)
  + KMS platform - fallback if crtc mode invalid (LP: #1661295)
  + Many fixes to Wayland support
  * debian/patches/:
- Drop all patches; in new upstream release.
  * debian/rules:
- Support DEB_BUILD_OPTIONS="nocheck"

 -- Christopher James Halse Rogers   Thu, 22 Mar 2018
16:36:52 +1100

** Changed in: mir (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  FFe request for Mir 0.31.0.1

Status in mir package in Ubuntu:
  Fix Released

Bug description:
  We'd like a freeze exception for Mir 0.31.0.1 in Bionic.

  The primary urgency for this is to get the miral ABI bump into 18.04;
  we've cleaned up the ABI and would prefer not to support the libmiral2
  ABI for the duration of 18.04.

  The Wayland protocol support is also significantly better, running
  GTK+3 apps mostly without issue.

  Upstream changelog:
  - ABI summary:
. mirclient ABI unchanged at 9
. miral ABI bumped to 3
. mirserver ABI bumped to 46
. mircommon ABI unchanged at 7
. mirplatform ABI unchanged at 16
. mirprotobuf ABI unchanged at 3
. mirplatformgraphics ABI unchanged at 13
. mirclientplatform ABI unchanged at 5
. mirinputplatform ABI unchanged at 7
. mircore ABI unchanged at 1
  - Enhancements:
. Miral version 2.0 - API cleanup and support for CSD initiated "resize"
. Reorganized examples and reworked miral server examples
. Better organization of, and fixes to, Wayland server code
. Initial support for Wayland xdg-shell
  - Bugs fixed:
. [miral] CommandLineOption should accept lambdas (Fixes #215)
. [miral] Implement the policy addenda in WindowManagementTrace
  (Fixes #192)
. [Wayland] Send repeat info (Fixes #180)
. Explicitly initialise glm matricies, (Fixes #200)
. KMS platform - fallback if crtc mode invalid (LP: #1661295)

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

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

[Touch-packages] [Bug 1661295] Re: [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [CHECK failed: (index) >= (0)]

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.31.0.1-0ubuntu1

---
mir (0.31.0.1-0ubuntu1) bionic; urgency=medium

  * New upstream release 0.31.0 (LP: #1757952)
- ABI summary:
  + mirclient ABI unchanged at 9
  + miral ABI bumped to 3
  + mirserver ABI bumped to 46
  + mircommon ABI unchanged at 7
  + mirplatform ABI unchanged at 16
  + mirprotobuf ABI unchanged at 3
  + mirplatformgraphics ABI unchanged at 13
  + mirclientplatform ABI unchanged at 5
  + mirinputplatform ABI unchanged at 7
  + mircore ABI unchanged at 1
- Enhancements:
  + Miral version 2.0 - API cleanup and support for CSD initiated "resize"
  + Reorganized examples and reworked miral server examples
  + Better organization of, and fixes to, Wayland server code
  + Initial support for Wayland xdg-shell
- Bugs fixed:
  + [miral] CommandLineOption should accept lambdas (Fixes #215)
  + [miral] Implement the policy addenda in WindowManagementTrace
(Fixes #192)
  + [Wayland] Send repeat info (Fixes #180)
  + Explicitly initialise glm matricies, (Fixes #200)
  + KMS platform - fallback if crtc mode invalid (LP: #1661295)
  + Many fixes to Wayland support
  * debian/patches/:
- Drop all patches; in new upstream release.
  * debian/rules:
- Support DEB_BUILD_OPTIONS="nocheck"

 -- Christopher James Halse Rogers   Thu, 22 Mar 2018
16:36:52 +1100

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

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

Title:
  [vmware] mir 0.26 failing with nested server in protobuf when bringing
  up NestedDisplay [CHECK failed: (index) >= (0)]

Status in Mir:
  New
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Setup:
  1. VMWare 12, with the following line added to ~/.vmware/preferences:
    mks.gl.allowBlacklistedDrivers = "TRUE"
  2. Created a VM with Xenial + Overlay PPA
  3. Installed unity8-desktop-session-mir, rebooted
  4. Tried to log in to a Unity8 session

  Problem: Unity8 fails to start, but is exiting cleanly as opposed to
  crashing. The following is all that is printed of the log:

  [2017-02-02:07:18:21.137] qtmir.screens: ScreensModel::ScreensModel
  [2017-02-02 07:18:21.143261] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:18:21.143413] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:18:21.144063] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  [2017-02-02:07:18:21.165] CHECK failed: (index) >= (0):
  initctl: No such variable: UNITY_MIR_SOCKET

  USC is coming up correctly however.

  If I try to launch miral-shell manually, I get similar error:

  MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_PROMPT_FILE=1 
MIR_SERVER_HOST_SOCKET=/run/mir_socket 
MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_NAME=session-0 
miral-shell
  [2017-02-02 07:55:56.686669] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:55:56.687395] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:55:56.689036] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  ERROR: Dynamic exception type: google::protobuf::FatalException
  std::exception::what: CHECK failed: (index) >= (0):

  I tried to grab a backtrace at the location of the last call to
  /usr/include/google/protobuf/repeated_field.h:885 which might print
  the error:

  http://pastebin.ubuntu.com/23911595/

  Thread 4 "MirServerThread" hit Breakpoint 1, 
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  8417  in 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc
  #0  
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  #1  0x7fffeba5c3e8 in 
mir::protobuf::DisplayConfiguration::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804b830, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:11436
  #2  0x7fffeb38a615 in 
google::protobuf::MessageLite::SerializeWithCachedSizesToArray(unsigned char*) 
const () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #3  0x7fffed696798 in mir_blob_from_display_config () from 
/usr/

[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

[Cameron Paine]

FWIW I'm experiencing similar symptoms on an ancient desktop that has
been stable, reliable and used every day for years. I too ran dist-
upgrade a couple of days ago. I've no idea what repos I use. That config
hasn't been touched for a long time. Can investigate if the information
might be useful.

$ top -b -n 1 | head
top - 19:17:12 up 1 day, 11:17,  2 users,  load average: 1.74, 1.65, 1.96
Tasks: 191 total,   2 running, 189 sleeping,   0 stopped,   0 zombie
%Cpu(s): 47.8 us, 51.4 sy,  0.3 ni,  0.3 id,  0.1 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem:   1025144 total,   720844 used,   304300 free,   171616 buffers
KiB Swap:  1048572 total,30508 used,  1018064 free.   190468 cached Mem

  PID USER  PR  NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
  353 root  20   03076   1172   1068 R 31.6  0.1 922:38.21 cgmanager
  892 root  20   04216   1344   1248 S 31.6  0.1 911:28.89 
systemd-logind
 1539 root  20   0   89256  37060  14232 S  7.9  3.6  45:56.98 Xorg
$ uname -a
Linux lab-netvista 3.13.0-87-generic #133-Ubuntu SMP Tue May 24 18:33:01 UTC 
2016 i686 i686 i686 GNU/Linux
zaphod@lab-netvista:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:   trusty

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

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in cgmanager package in Ubuntu:
  Invalid
Status in libnih package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
 
676 root  20   0   43644   2144   1568 R 100.0  0.0  74:43.77 
systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

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

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

[Touch-packages] [Bug 1756526] Re: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

[dino99]

With the recent upgrades, that error is now gone.

** No longer affects: xorg-server (Ubuntu)

** No longer affects: gdm3 (Ubuntu)

** No longer affects: systemd (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

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

Title:
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Gnome-shell session on xorg, with no opened apps

  Getting this logged:

  oem@ubuntu:~$ journalctl -b | grep XSERV
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransSocketUNIXCreateListener: 
...SocketCreateListener() failed
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransMakeAllCOTSServerListeners: 
server already running

  per https://www.x.org/wiki/FAQErrorMessages/

  i join the listening.txt output

  and there is no XO-lock file on the system, which seems abnormal.

  As this missing XO-lock file should be set by system and/or app,
  report also against gdm3 & systemd & gnome-shell (no idea which one to
  blame).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar 17 12:10:02 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: r8168, 8.045.08, 4.15.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 28 14:50:36 2018
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756526/+subscriptions

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