[Touch-packages] [Bug 1762912] [NEW] package liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: usr/share/doc/liblzma5/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/sh

2018-04-10 Thread Fauzi Nugraha
Public bug reported:

this bug appear when i issued "sudo apt-get install -f" command

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz]
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
AptOrdering:
 liblzma5: Install
 liblzma5: Configure
 libxml2: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Apr 11 11:53:39 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu10
DpkgHistoryLog:
 Start-Date: 2018-04-11  11:53:32
 Commandline: apt-get install -f
 Requested-By: fauzi (1001)
 Install: liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2, automatic)
DpkgTerminalLog:
 Preparing to unpack .../liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb ...
 Unpacking liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', 
which is different from other instances of package liblzma5:i386
DuplicateSignature:
 package:liblzma5:5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz]
 Unpacking liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', 
which is different from other instances of package liblzma5:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/liblzma5/changelog.Debian.gz', which is different from other 
instances of package liblzma5:i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: xz-utils
Title: package liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', which is 
different from other instances of package liblzma5:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xz-utils (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified:
  usr/share/doc/liblzma5/changelog.Debian.gz] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/liblzma5/changelog.Debian.gz', which is different from
  other instances of package liblzma5:i386

Status in xz-utils package in Ubuntu:
  New

Bug description:
  this bug appear when i issued "sudo apt-get install -f" command

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz]
  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
  AptOrdering:
   liblzma5: Install
   liblzma5: Configure
   libxml2: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr 11 11:53:39 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu10
  DpkgHistoryLog:
   Start-Date: 2018-04-11  11:53:32
   Commandline: apt-get install -f
   Requested-By: fauzi (1001)
   Install: liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2, automatic)
  DpkgTerminalLog:
   Preparing to unpack .../liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb ...
   Unpacking liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', 
which is different from other instances of package liblzma5:i386
  DuplicateSignature:
   package:liblzma5:5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz]
   Unpacking liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', 
which is different from other instances of package liblzma5:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/liblzma5/changelog.Debian.gz', which is different from other 
instances of package liblzma5:i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: xz-utils
  Title: package liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz] failed to 

[Touch-packages] [Bug 1762912] Re: package liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: usr/share/doc/liblzma5/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/shar

2018-04-10 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified:
  usr/share/doc/liblzma5/changelog.Debian.gz] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/liblzma5/changelog.Debian.gz', which is different from
  other instances of package liblzma5:i386

Status in xz-utils package in Ubuntu:
  New

Bug description:
  this bug appear when i issued "sudo apt-get install -f" command

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz]
  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
  AptOrdering:
   liblzma5: Install
   liblzma5: Configure
   libxml2: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr 11 11:53:39 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu10
  DpkgHistoryLog:
   Start-Date: 2018-04-11  11:53:32
   Commandline: apt-get install -f
   Requested-By: fauzi (1001)
   Install: liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2, automatic)
  DpkgTerminalLog:
   Preparing to unpack .../liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb ...
   Unpacking liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', 
which is different from other instances of package liblzma5:i386
  DuplicateSignature:
   package:liblzma5:5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz]
   Unpacking liblzma5:i386 (5.1.1alpha+20120614-2ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/liblzma5_5.1.1alpha+20120614-2ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', 
which is different from other instances of package liblzma5:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/liblzma5/changelog.Debian.gz', which is different from other 
instances of package liblzma5:i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: xz-utils
  Title: package liblzma5 5.1.1alpha+20120614-2ubuntu2 [modified: 
usr/share/doc/liblzma5/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/liblzma5/changelog.Debian.gz', which is 
different from other instances of package liblzma5:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1762912/+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 1408275] Re: Unable to log in with lightdm

2018-04-10 Thread Rolf Leggewie
ping aanno

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

Title:
  Unable to log in with lightdm

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Unable to log in with lightdm

  This is a bug report against an up-to-date version of (k)ubuntu
  14.10/utopic. The issue seems to have been triggered by ubuntu updates
  between 23.12.2014 and 07.01.2015 (today).

  I'm unable to log in with lightdm. No matter what user, and I also
  tried guest. However I'm able to log on a (non-graphical) console/vt
  (i.e. without X).

  I found the following in /var/log/lightdm/x-0-greeter.log:

  QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
  QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
  Bus::open: Can not get ibus-daemon's address. 
  IBusInputContext::createInputContext: no connection to ibus-daemon 
  QDBusError("org.freedesktop.DBus.Error.AccessDenied", "Permission denied") 
  QDBusError("org.freedesktop.DBus.Error.AccessDenied", "Permission denied") 
  QDBusError("org.freedesktop.DBus.Error.AccessDenied", "Permission denied") 
  QDBusError("org.freedesktop.DBus.Error.AccessDenied", "Permission denied") 
  
file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:246:5: 
QML ListView: Bei der für die Eigenschaft 
âÂÂcurrentIndexâÂÂ
   angegebenen Bindung wurde eine Endlosschleife festgestellt
  
file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:246:5: 
QML ListView: Bei der für die Eigenschaft 
âÂÂcurrentIndexâÂÂ
   angegebenen Bindung wurde eine Endlosschleife festgestellt
  file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession

  Hence the bug maybe releated to some ibus, dbus, systemd and/or
  upstart problem. But I don't care. This is the most severe problem for
  me in Ubuntu for nearly 10 years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1408275/+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 1358479] Re: after typing password on login screen, login screen returns

2018-04-10 Thread Rolf Leggewie
*** This bug is a duplicate of bug 1268283 ***
https://bugs.launchpad.net/bugs/1268283

Do you still have that old home directory lying around?  I suspect your
.Xauthority file was owned by root.  That would make this ticket a dupe
of bug 1268283.

** This bug has been marked a duplicate of bug 1268283
   Lightdm doesn't give any error message when .XAutority is owned by root

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

Title:
  after typing password on login screen, login screen returns

Status in lightdm package in Ubuntu:
  New

Bug description:
  I am running a dual boot system.
  Installed trusty (amd64) from usb stick - without formatting the install 
partition. 
  Upon restart the login screen appears all right. But after typing the 
password, the screen turns black for a split second - and the login screen 
appears again - without any comments.
  If I type a wrong password, I get the incorrect password message on the login 
screen.
  If I choose the guest login, unity appears and is perfectly operational.
  What can I do?
  Thanks so much!
  Hans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1358479/+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 1718863] Re: VLC malfunction

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  VLC malfunction

Status in xorg package in Ubuntu:
  Expired

Bug description:
  VLC will no longer function.
  When attempting to play a DVD movie, the screen goes white with black 
speckled effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep 22 17:23:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-92-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-96-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104M [GeForce GTX 880M] [10de:1198] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GK104M [GeForce GTX 880M] [1028:05ae]
  InstallationDate: Installed on 2017-08-20 (33 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Alienware Alienware 17
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=5d561490-ed57-4448-9388-c0aa28db7add ro drm.debug=0xe plymouth:debug 
vesafb.invalid=1 nopat
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A14
  dmi.board.name: 04WT2G
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnAlienware:bvrA14:bd09/24/2014:svnAlienware:pnAlienware17:pvrA14:rvnAlienware:rn04WT2G:rvrA00:cvnAlienware:ct8:cvrA14:
  dmi.product.name: Alienware 17
  dmi.product.version: A14
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718863/+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 1330524] Re: Can't login. Seems to login and kick me out. Also I don't see the secondary account on the greeter.

2018-04-10 Thread Rolf Leggewie
*** This bug is a duplicate of bug 1268283 ***
https://bugs.launchpad.net/bugs/1268283

** This bug has been marked a duplicate of bug 1268283
   Lightdm doesn't give any error message when .XAutority is owned by root

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

Title:
  Can't login. Seems to login and kick me out. Also I don't see the
  secondary account on the greeter.

Status in lightdm package in Ubuntu:
  New

Bug description:
  Started since a few weeks after I started switching from 2 monitors to 1 and 
viceversa (working environment and home env.). Might be just a coincidence.
  Last three times, I've got dropped into the command line.
  First time, I reboot and It worked normally.
  Second, I had to startx from command line. It worked with problems. I 
rebooted and worked well.
  Today it didn't go through, so I started on failsafe mode and reconfigure 
packages. It removed unused 3 packages. Unfortunately I didn't see which ones.
  After that, I starts X system, but on greeter I can't see the second account 
(primary, secondary, guest) and trying to login, it goes black come back to 
greeter like nothing happened. No wrong password, just like restarting.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.4
  ProcVersionSignature: Ubuntu 3.2.0-63.95-generic 3.2.57
  Uname: Linux 3.2.0-63-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Jun 16 11:16:18 2014
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1330524/+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 1716686] Re: Black screen

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Black screen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  black screen when starting linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Sep 12 10:40:20 2017
  DistUpgraded: 2016-08-11 16:50:28,751 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 945GSE Express Integrated Graphics Controller 
[17aa:3870]
 Subsystem: Lenovo Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [17aa:3870]
  InstallationDate: Installed on 2016-02-03 (586 days ago)
  InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1450): WARNING **: Failed to load user image: Falha 
ao abrir o arquivo "/home/net/.face": Arquivo ou diretório não encontrado
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: LENOVO ideapad S10
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=689cdd2d-3ab0-49ab-8165-f8dc9fc86f2d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-11 (396 days ago)
  dmi.bios.date: 04/13/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 14CN66WW
  dmi.board.name: Mariana
  dmi.board.vendor: Lenovo
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr14CN66WW:bd04/13/2009:svnLENOVO:pnideapadS10:pvrLenovo:rvnLenovo:rnMariana:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: ideapad S10
  dmi.product.version: Lenovo
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 12 10:11:25 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   0 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1716686/+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 1715453] Re: compis makes desktop slow

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  compis makes desktop slow

Status in xorg package in Ubuntu:
  Expired

Bug description:
  i need more than 60 sec for start X... ?!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Sep  6 19:57:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:0655]
  InstallationDate: Installed on 2016-11-02 (307 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Notebook W65_67SZ
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=7aaeecb0-efd9-4bcf-a22b-296c637d59ed ro quiet splash plymouth:debug 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd02/26/2014:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715453/+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 1717706] Re: My desktop is not showing correctly

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  My desktop is not showing correctly

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have Ubuntu  14.04 LTS and I have nvidia X.org X server install but the 
desktop does not show what it expected to be. when I took an screen shot I just 
saw it and more detail is available in the attachment.
  thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 16 20:51:52 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-42-generic, x86_64: installed
   virtualbox, 4.3.36, 4.2.0-27-generic, x86_64: installed
   virtualbox, 4.3.36, 4.2.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
  InstallationDate: Installed on 2017-09-12 (3 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Micro-Star International Co., Ltd. GE620/GE620DX/FX620DX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=5e956ab8-3c28-4702-9d97-784cad737c27 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16G5IMS V1.0F
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16G5
  dmi.board.vendor: Micro-Star International 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: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.name: GE620/GE620DX/FX620DX
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Sep 16 19:53:10 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 489 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1717706/+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 1647943] Re: guest session leaves cruft behind

2018-04-10 Thread Rolf Leggewie
** Package changed: unity-greeter (Ubuntu) => lightdm (Ubuntu)

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

Title:
  guest session leaves cruft behind

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not sure this is a bug in unity-greeter, most likely it is another
  component.

  After using the guest session feature (log in as guest) a couple of
  times I find the following cruft on my system.  This shouldn't happen.

  $ grep guest /etc/shadow
  guest-ceyM7L:*:15982:0:9:7:::
  guest-Qb2HtL:*:15989:0:9:7:::
  guest-9KbZAI:*:15995:0:9:7:::
  guest-Jz5Iz0:*:16011:0:9:7:::
  guest-kWc1MQ:*:16014:0:9:7:::
  guest-iqcR95:*:16026:0:9:7:::
  guest-5UTOnm:*:16082:0:9:7:::
  guest-iXkNz7:*:16101:0:9:7:::
  guest-nHX8MC:*:16502:0:9:7:::
  guest-lrkBHN:*:16572:0:9:7:::
  guest-Ltux49:*:16698:0:9:7:::
  guest-oggaCN:*:16756:0:9:7:::
  guest-y5JvoT:*:16756:0:9:7:::
  guest-YBXQ1O:*:16762:0:9:7:::
  guest-d2N35B:*:17043:0:9:7:::
  guest-B222qB:*:17073:0:9:7:::
  guest-B4IqVx:*:17110:0:9:7:::
  guest-51gqiH:*:17142:0:9:7:::

  Other files seem to be affected as well.

  $ sudo rgrep -l guest-ceyM7L /etc/
  /etc/group-
  /etc/group.org
  /etc/gshadow-
  /etc/passwd-
  /etc/passwd.org
  /etc/shadow-
  /etc/shadow.org
  /etc/group
  /etc/gshadow
  /etc/shadow
  /etc/passwd

  I'm running unity-greeter 14.04.11-0ubuntu1 on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1647943/+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 1718861] Re: Ubuntu won't shutdown or restart

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu won't shutdown or restart

Status in xorg package in Ubuntu:
  Expired

Bug description:
  When i try to shutdown it keeps showing shutting down. I have Hp
  probook 450 G2 where i recently installed ubuntu. I've dual boot
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep 22 13:23:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.10.0-33-generic, x86_64: installed
   acpi-call, 1.1.0, 4.10.0-35-generic, x86_64: installed
   tp_smapi, 0.42, 4.10.0-33-generic, x86_64: installed
   tp_smapi, 0.42, 4.10.0-35-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:2248]
 Subsystem: Hewlett-Packard Company Topaz PRO [Radeon R5 M255] [103c:224a]
  InstallationDate: Installed on 2017-09-15 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP ProBook 450 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=40e2d4cd-48e2-45fe-84df-f4fe24732c1d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.15
  dmi.board.name: 2248
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.15:bd07/24/2015:svnHewlett-Packard:pnHPProBook450G2:pvrA3008CD10003:rvnHewlett-Packard:rn2248:rvrKBCVersion59.22:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 450 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Sep 22 13:13:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718861/+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 1268283] Re: Lightdm doesn't give any error message when .XAutority is owned by root

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Lightdm doesn't give any error message when .XAutority is owned by
  root

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  (Orignal problem at the end)

  I understood the problem : As I had to sudo startx previously,
  .XAutority was owned by root. So Lightdm wasn't able to log me in. But
  Lightdm doesn't display any error message explaining why it can't log
  me in, as there was previously in GDM.

  HOW to reproduce : made root the owner of the .XAutority file at the
  root of your personal home, then try to login via Lightdm. It doesn't
  display any message but it doesn't log you.

  -Original problem :

  So here is what happened : To test if an old bug with menus is still
  present in Trusty I updated to it, but it went very wrong (no screen
  at all, I filed this bug by going to recovery mode and FailsafeX). So
  I tried installing Trusty "from scratch", but I kept my /home. I used
  the same ID and Password during the installation as I do each
  reinstall. Reinstall corrected the problem of no screen : I was on
  lightdm login screen. Then, impossible to log me in : It tried and
  immediately go back to login screen. I changed the password from tty1
  but same problem. But I can open the guest session (from which I make
  this bug report).

  What I expected : To be able to login from lightdm as I do each time I
  have to reinstall the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 12 11:50:36 2014
  InstallationDate: Installed on 2014-01-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140111)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1268283/+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 1268283] Re: Lightdm doesn't give any error message when .XAutority is owned by root

2018-04-10 Thread Rolf Leggewie
just ran into this myself a few days ago when updating to bionic.  It
was pure luck that I discovered the problem and fix.

** Tags added: bionic

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

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

Title:
  Lightdm doesn't give any error message when .XAutority is owned by
  root

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  (Orignal problem at the end)

  I understood the problem : As I had to sudo startx previously,
  .XAutority was owned by root. So Lightdm wasn't able to log me in. But
  Lightdm doesn't display any error message explaining why it can't log
  me in, as there was previously in GDM.

  HOW to reproduce : made root the owner of the .XAutority file at the
  root of your personal home, then try to login via Lightdm. It doesn't
  display any message but it doesn't log you.

  -Original problem :

  So here is what happened : To test if an old bug with menus is still
  present in Trusty I updated to it, but it went very wrong (no screen
  at all, I filed this bug by going to recovery mode and FailsafeX). So
  I tried installing Trusty "from scratch", but I kept my /home. I used
  the same ID and Password during the installation as I do each
  reinstall. Reinstall corrected the problem of no screen : I was on
  lightdm login screen. Then, impossible to log me in : It tried and
  immediately go back to login screen. I changed the password from tty1
  but same problem. But I can open the guest session (from which I make
  this bug report).

  What I expected : To be able to login from lightdm as I do each time I
  have to reinstall the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 12 11:50:36 2014
  InstallationDate: Installed on 2014-01-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140111)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1268283/+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 1721028] Re: system hang

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  system hang

Status in xorg package in Ubuntu:
  Expired

Bug description:
  battery draining system slow and hanged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
   [  OK  ] Started LSB: daemon to balance interrupts for SMP 
systems.
   [  OK  ] Started LSB: automatic crash report generation.
   [  OK  ] Started Network Manager.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Oct  3 18:29:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0835]
  InstallationDate: Installed on 2017-09-19 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer Aspire E1-570
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=38b773dc-55e2-487f-a83b-78384cd0babf ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_CX
  dmi.board.vendor: Acer
  dmi.board.version: V2.02
  dmi.chassis.asset.tag: Acer Asset Tag String
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd07/30/2013:svnAcer:pnAspireE1-570:pvrV2.02:rvnAcer:rnEA50_CX:rvrV2.02:cvnInsydeCorp.:ct10:cvrV2.02:
  dmi.product.name: Aspire E1-570
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct  3 17:58:25 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1721028/+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 1718255] Re: installing xorg-video-intel trying to coorect my disappeared launcher and desktop

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  installing xorg-video-intel trying to coorect my disappeared launcher
  and desktop

Status in xorg package in Ubuntu:
  Expired

Bug description:
  installing xorg-video-intel trying to correct my disappeared launcher
  and desktop on ubuntu 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Sep 19 19:23:46 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2017-09-13 (5 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20B7S1QP03
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=75f04494-8989-4e4c-9cb3-aa017d1859af ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET92WW (2.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S1QP03
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET92WW(2.42):bd03/03/2017:svnLENOVO:pn20B7S1QP03:pvrThinkPadT440:rvnLENOVO:rn20B7S1QP03:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B7S1QP03
  dmi.product.version: ThinkPad T440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Sep 19 19:21:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718255/+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 1716809] Re: choppy graphics

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  choppy graphics

Status in xorg package in Ubuntu:
  Expired

Bug description:
  graphics frame-rate is choppy in chrome, both stills and video, no
  problems before recent-ish update(s)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep 12 19:04:52 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. BeaverCreek [Radeon HD 6520G] [1043:2122]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 
6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-04-05 (160 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK Computer Inc. K53TK
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=f4c1c213-4cf8-455f-a1d4-76311b393c40 ro vesafb.invalid=1 nopat 
plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 206
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53TK
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd03/20/2012:svnASUSTeKComputerInc.:pnK53TK:pvr1.0:rvnASUSTeKComputerInc.:rnK53TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53TK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Sep  5 11:56:19 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1716809/+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 1720529] Re: ~/dmesg and your /var/log/Xorg.0.log.

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ~/dmesg and your /var/log/Xorg.0.log.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  i am unable to use my wireless mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 275992/60309504 files, 5656499/241220352 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 30 16:46:23 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0792]
  InstallationDate: Installed on 2017-08-08 (53 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 138a:0010 Validity Sensors, Inc. VFS Fingerprint 
sensor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 14-3468
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed 
root=UUID=de326c40-9285-4350-b59e-15e9b09834cb ro acpi_rev_override quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 14-3468
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Sep 30 16:33:28 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1767 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1720529/+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 1722835] Re: I was working and everything freeze.

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  I was working and everything freeze.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Running Netbeans, Firefox, Audacious, Filemanager...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct 11 11:28:40 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
  InstallationDate: Installed on 2017-10-10 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=ab28a80a-2036-46f7-af84-696df85b60bf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B85M-DS3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722835/+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 1722067] Re: HP Probook 4515s

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HP Probook 4515s

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Update Problems

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct  8 14:28:59 2017
  DistUpgraded: 2017-07-09 14:18:03,311 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3077]
  InstallationDate: Installed on 2017-03-06 (215 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Hewlett-Packard HP ProBook 4515s
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 nopat 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2017-07-09 (91 days ago)
  dmi.bios.date: 06/17/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPI Ver. F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3077
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 25.0C
  dmi.chassis.asset.tag: CNU9320V0W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPIVer.F.06:bd06/17/2009:svnHewlett-Packard:pnHPProBook4515s:pvrF.06:rvnHewlett-Packard:rn3077:rvrKBCVersion25.0C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4515s
  dmi.product.version: F.06
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Oct  8 14:11:08 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.9
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722067/+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 1722622] Re: Brightness

2018-04-10 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Brightness

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I can't change the brightness

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-132.181-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-132-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 10 21:51:19 2017
  DistUpgraded: 2017-10-09 23:27:38,749 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2213]
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-132-generic 
root=UUID=f74ed4d8-459a-4372-9992-efa8be3f558e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2017-10-09 (0 days ago)
  dmi.bios.date: 05/26/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.39
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2213
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.54
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2213:rvr57.54:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Oct 10 21:42:38 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5547 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722622/+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 1647943] [NEW] guest session leaves cruft behind

2018-04-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I'm not sure this is a bug in unity-greeter, most likely it is another
component.

After using the guest session feature (log in as guest) a couple of
times I find the following cruft on my system.  This shouldn't happen.

$ grep guest /etc/shadow
guest-ceyM7L:*:15982:0:9:7:::
guest-Qb2HtL:*:15989:0:9:7:::
guest-9KbZAI:*:15995:0:9:7:::
guest-Jz5Iz0:*:16011:0:9:7:::
guest-kWc1MQ:*:16014:0:9:7:::
guest-iqcR95:*:16026:0:9:7:::
guest-5UTOnm:*:16082:0:9:7:::
guest-iXkNz7:*:16101:0:9:7:::
guest-nHX8MC:*:16502:0:9:7:::
guest-lrkBHN:*:16572:0:9:7:::
guest-Ltux49:*:16698:0:9:7:::
guest-oggaCN:*:16756:0:9:7:::
guest-y5JvoT:*:16756:0:9:7:::
guest-YBXQ1O:*:16762:0:9:7:::
guest-d2N35B:*:17043:0:9:7:::
guest-B222qB:*:17073:0:9:7:::
guest-B4IqVx:*:17110:0:9:7:::
guest-51gqiH:*:17142:0:9:7:::

Other files seem to be affected as well.

$ sudo rgrep -l guest-ceyM7L /etc/
/etc/group-
/etc/group.org
/etc/gshadow-
/etc/passwd-
/etc/passwd.org
/etc/shadow-
/etc/shadow.org
/etc/group
/etc/gshadow
/etc/shadow
/etc/passwd

I'm running unity-greeter 14.04.11-0ubuntu1 on trusty.

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


** Tags: trusty
-- 
guest session leaves cruft behind
https://bugs.launchpad.net/bugs/1647943
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lightdm in Ubuntu.

-- 
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 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40

2018-04-10 Thread Steve Langasek
I think we need to handle this via removal of the resolvconf package on
upgrade.  Removal (not purge) seems to be sufficient.

Dimitri, is there any remaining reason for systemd to not conflict: with
resolvconf?

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

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

** Also affects: resolvconf (Ubuntu Bionic)
   Importance: High
   Status: Triaged

** Package changed: resolvconf (Ubuntu Bionic) => systemd (Ubuntu
Bionic)

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

Title:
  /etc/resolv.conf empty after upgrading from 16.04 to 18.40

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I just upgraded one of my LXC containers to 18.04 and after rebooting,
  the /etc/resolv.conf contains no nameservers. systemd-resolve,
  however, resolves fine and the --status returns the DNS server details
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 22:53:30 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762899/+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 1748095] Re: Non-root user can reboot machine from the command line

2018-04-10 Thread Rocko
Doesn't the shutdown icon warn you if there are other users logged in
who might lose work? So shouldn't the reboot command do the same thing
if you are not root?

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

Title:
  Non-root user can reboot machine from the command line

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  Open a gnome-terminal as your normal user and type 'reboot' and ENTER.
  The PC reboots immediately, losing all unsaved work for all users
  (this is the case on both my VM and laptop running Ubuntu 18.04, so I
  don't think it's a weird configuration issue).

  In the old days, didn't you have to be root (or sudoed) for this
  command to work?

  While we're on the subject, wouldn't it be nicer if the reboot command
  (ie when run as root) asked you to confirm before executing, pointing
  out that all unsaved work for all users will be lost?

  Note that you can't reboot a server if you are logged in via ssh as a
  non-root user:

  Failed to set wall message, ignoring: Interactive authentication required.
  Failed to reboot system via logind: Interactive authentication required.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  
  I am assuming this is a systemd issue, because reboot just links to 
systemctl, and systemctl can be executed by non-root users:

  $ ll /sbin/reboot /bin/systemctl
  -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl*
  lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl*

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  8 12:49:33 2018
  InstallationDate: Installed on 2017-12-18 (51 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=dd72d916-58fc-49a1-9798-feded5ce6eff ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748095/+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 1748095] Re: Non-root user can reboot machine from the command line

2018-04-10 Thread Rocko
(And pulling the power cord on my laptop doesn't reboot or even shutdown
the computer, so I don't think it's a good comparison. Holding the power
button down for ten seconds is a better comparison, but it's still not a
good one because reboot acts immediately, not after you confirm it by
typing it in ten times or something.)

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

Title:
  Non-root user can reboot machine from the command line

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  Open a gnome-terminal as your normal user and type 'reboot' and ENTER.
  The PC reboots immediately, losing all unsaved work for all users
  (this is the case on both my VM and laptop running Ubuntu 18.04, so I
  don't think it's a weird configuration issue).

  In the old days, didn't you have to be root (or sudoed) for this
  command to work?

  While we're on the subject, wouldn't it be nicer if the reboot command
  (ie when run as root) asked you to confirm before executing, pointing
  out that all unsaved work for all users will be lost?

  Note that you can't reboot a server if you are logged in via ssh as a
  non-root user:

  Failed to set wall message, ignoring: Interactive authentication required.
  Failed to reboot system via logind: Interactive authentication required.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  
  I am assuming this is a systemd issue, because reboot just links to 
systemctl, and systemctl can be executed by non-root users:

  $ ll /sbin/reboot /bin/systemctl
  -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl*
  lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl*

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  8 12:49:33 2018
  InstallationDate: Installed on 2017-12-18 (51 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=dd72d916-58fc-49a1-9798-feded5ce6eff ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748095/+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 1735415] Re: VNC client does not exits after logout

2018-04-10 Thread Robert Ancell
Was fixed in lightdm 1.25.1

** Changed in: lightdm
   Status: Fix Committed => Fix Released

** Changed in: lightdm (Ubuntu Bionic)
   Importance: Undecided => Medium

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

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

Title:
  VNC client does not exits after logout

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  New
Status in lightdm source package in Xenial:
  New
Status in lightdm source package in Zesty:
  New
Status in lightdm source package in Artful:
  New
Status in lightdm source package in Bionic:
  Fix Released

Bug description:
  I have setup the remote desktop using the "[VNCServer]" configuration section.
  When I log in using a VNC client and log out with the desktop panel menu,
  the VNC client(remmina) does not exits.

  I found that a VNC connection(TCP 5900) remains alive even though the Xvnc 
server exits.
  I also found the cause, GSocket instance is leaking in the "src/vnc-server.c".

  static gboolean
  read_cb (GSocket *socket, GIOCondition condition, VNCServer *server)
  {
  ...
  client_socket = g_socket_accept (socket, NULL, );
  ...
  if (client_socket)
  {
  ...
  g_signal_emit (server, signals[NEW_CONNECTION], 0, client_socket);
  }
  return TRUE;
  }

  I think that "g_object_unref(client_socket)" should be called after
  g_signal_emit().

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1735415/+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 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40

2018-04-10 Thread Dawid Wróbel
Yes it is, at 1.79ubuntu9

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

Title:
  /etc/resolv.conf empty after upgrading from 16.04 to 18.40

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded one of my LXC containers to 18.04 and after rebooting,
  the /etc/resolv.conf contains no nameservers. systemd-resolve,
  however, resolves fine and the --status returns the DNS server details
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 22:53:30 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1762899/+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 1762725] Re: Linux reports Samson Meteor USB mic as an output device

2018-04-10 Thread Kai-Heng Feng
Oops, didn't see Daniel already triaged this.

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

** No longer affects: pulseaudio (Ubuntu)

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

Title:
  Linux reports Samson Meteor USB mic as an output device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I reboot my system, pulseaudio selects my Samson Meteor USB
  mic as the default output device. I have to manually select the analog
  output every time. Also, the Default effect sound does not make any
  noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2355 F pulseaudio
   /dev/snd/controlC1:  guru   2355 F pulseaudio
   /dev/snd/controlC0:  guru   2355 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr 10 08:54:30 2018
  InstallationDate: Installed on 2018-04-07 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2402 F pulseaudio
   /dev/snd/controlC1:  guru   2402 F pulseaudio
   /dev/snd/controlC0:  guru   2402 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-07 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  IwConfig:
   enp30s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2402 F pulseaudio
   /dev/snd/controlC1:  guru   2402 F pulseaudio
   /dev/snd/controlC0:  guru   2402 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-07 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  IwConfig:
   enp30s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  

[Touch-packages] [Bug 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40

2018-04-10 Thread Steve Langasek
Thanks for reporting.  After this upgrade, is the resolvconf package
still installed?

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

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

Title:
  /etc/resolv.conf empty after upgrading from 16.04 to 18.40

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded one of my LXC containers to 18.04 and after rebooting,
  the /etc/resolv.conf contains no nameservers. systemd-resolve,
  however, resolves fine and the --status returns the DNS server details
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 22:53:30 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1762899/+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 1568897] Re: Disable Guest Access by default.

2018-04-10 Thread Rolf Leggewie
Guest sessions have been disabled -> bug 1663157

But might become enabled again when bug 1742912 has been dealt with

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

** Changed in: unity-control-center (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Disable Guest Access by default.

Status in lightdm package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  "Guest Access" should be disabled by default. It is an unexpected
  "feature", on an otherwise secure system. Until a GUI option is added
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/886415), it is also an un-intuitive feature to disable.

  I've found it only invites trouble. For me, trouble had the face of my
  children while I was at work. =) They found that they were able to use
  my laptop, without logging in.

  Then on their PC they found that, while logged into their account,
  using the "Guest Access" bypassed the proxy settings setup in their
  Firefox profile.

  Please consider defaulting both pre-logon and post-logon Guest Access
  to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1568897/+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 1762899] [NEW] /etc/resolv.conf empty after upgrading from 16.04 to 18.40

2018-04-10 Thread Dawid Wróbel
Public bug reported:

I just upgraded one of my LXC containers to 18.04 and after rebooting,
the /etc/resolv.conf contains no nameservers. systemd-resolve, however,
resolves fine and the --status returns the DNS server details as
expected.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: resolvconf 1.79ubuntu9
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Tue Apr 10 22:53:30 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: resolvconf
UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)

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


** Tags: amd64 apport-bug bionic uec-images

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

Title:
  /etc/resolv.conf empty after upgrading from 16.04 to 18.40

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I just upgraded one of my LXC containers to 18.04 and after rebooting,
  the /etc/resolv.conf contains no nameservers. systemd-resolve,
  however, resolves fine and the --status returns the DNS server details
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 22:53:30 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1762899/+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 1718927] Re: No hdmi sound after suspend/resume on 16.04

2018-04-10 Thread Daniel van Vugt
** Tags added: hdmi-audio

** Summary changed:

- No hdmi sound after suspend/resume on 16.04
+ No HDMI sound after suspend/resume on 16.04

** Tags added: xenial

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

Title:
  No HDMI sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1762725] Re: Ubuntu Budgie selects USB mic as default audio output after every reboot.

2018-04-10 Thread Daniel van Vugt
PulseAudio is selecting the USB device for output because that's correct
behaviour for USB speakers. And PulseAudio thinks the mic is a speaker
because that's what ALSA seems to be telling it.

The real problem here is that the Linux kernel seems to be reporting the
mic is an output device. Much like bug 1749207.

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

** Summary changed:

- Ubuntu Budgie selects USB mic as default audio output after every reboot.
+ Linux reports Samson Meteor USB mic as an output device

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

Title:
  Linux reports Samson Meteor USB mic as an output device

Status in linux package in Ubuntu:
  New

Bug description:
  Whenever I reboot my system, pulseaudio selects my Samson Meteor USB
  mic as the default output device. I have to manually select the analog
  output every time. Also, the Default effect sound does not make any
  noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2355 F pulseaudio
   /dev/snd/controlC1:  guru   2355 F pulseaudio
   /dev/snd/controlC0:  guru   2355 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr 10 08:54:30 2018
  InstallationDate: Installed on 2018-04-07 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762725/+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 1759961] Re: Update to 5.49 in Bionic (mostly bug-fix release)

2018-04-10 Thread Daniel van Vugt
I think we're waiting for version 5.50 or later (for bug 1759628). And
even if that was available today we'd still not introduce it till 18.10.

I'd like to keep bluez and pulseaudio in a maturing state, which means
they haven't changed in a long time when 18.04 is released.

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

Title:
  Update to 5.49 (mostly bug-fix release)

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1759961] Re: Update to 5.49 in Bionic (mostly bug-fix release)

2018-04-10 Thread Daniel van Vugt
Oh it looks like bug 1759628 is fixed in v5.49, but still, same plan.

** Summary changed:

- Update to 5.49 in Bionic (mostly bug-fix release)
+ Update to 5.49 (mostly bug-fix release)

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

Title:
  Update to 5.49 (mostly bug-fix release)

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1759961] Re: Update to 5.49 (mostly bug-fix release)

2018-04-10 Thread Daniel van Vugt
We also discussed 5.49 at the last Bluetooth meeting, and came to the
same conclusion.

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

Title:
  Update to 5.49 (mostly bug-fix release)

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1718927] Re: No hdmi sound after suspend/resume on 16.04

2018-04-10 Thread Henrique Andrade
I can confirm this also happens for me. A workaround is to change the
video resolution to something else and then back to what it was. That
will bring back the HDMI sound device too.

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1718927] Re: No hdmi sound after suspend/resume on 16.04

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1759795] Re: Unreadable text in dconf-editor header-bar when searching.

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Unreadable text in dconf-editor header-bar when searching.

Status in Ubuntu theme:
  In Progress
Status in dconf-editor package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759795/+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 1762551] Re: Scroll bar in Firefox is very thin and does not widen when hovered

2018-04-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1575896 ***
https://bugs.launchpad.net/bugs/1575896

No problem. In that case we should ideally use the oldest relevant
duplicate: bug 1575896

The only case in which you shouldn't choose the oldest one is if a newer
one contains significantly more useful information.

** This bug has been marked a duplicate of bug 1575896
   Scrollbar thumb not drawn in firefox 46 (gtk3?)

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

Title:
  Scroll bar in Firefox is very thin and does not widen when hovered

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  In Ambiance, the scroll bar in Firefox is very thin and does not widen
  when hovered or pressed. In Adwaita, the scroll bar is thicker and
  easier to see and pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 22:56:52 2018
  InstallationDate: Installed on 2017-10-02 (189 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762551/+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 1759795] Re: Unreadable text in dconf-editor header-bar when searching.

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: dconf-editor (Ubuntu)
   Status: New => Confirmed

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

Title:
  Unreadable text in dconf-editor header-bar when searching.

Status in Ubuntu theme:
  In Progress
Status in dconf-editor package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759795/+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 1759795] Re: Unreadable text in dconf-editor header-bar when searching.

2018-04-10 Thread Daniel van Vugt
** Changed in: ubuntu-themes
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

** Branch linked: lp:~3v1n0/ubuntu-themes/theme-colors-definitions

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

Title:
  Unreadable text in dconf-editor header-bar when searching.

Status in Ubuntu theme:
  In Progress
Status in dconf-editor package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759795/+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 1762841] Re: dconf-editor path bar color is unreadable when in search mode

2018-04-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1759795 ***
https://bugs.launchpad.net/bugs/1759795

Andy beat you to it -> bug 1759795

** This bug has been marked a duplicate of bug 1759795
   Unreadable text in dconf-editor header-bar when searching.

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

Title:
  dconf-editor path bar color is unreadable when in search mode

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Open d-conf editor, hit ctrl+f:
   See https://imgur.com/kU7H1j1.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1762841/+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 1762780] Re: gst-plugin-scanner crashed with signal 7 in memset()

2018-04-10 Thread Sean Cleary
** Description changed:

- Xfce Panel Switch was the only application I had open.  If by chance
- it's not in the attached datadumps, I'm trying the 20180410 xubuntu
- bionic daily build.
+ Xfce Panel Switch was the only application I had open.  If by chance it's not 
in the attached datadumps, I'm trying the 20180410 xubuntu bionic daily build.
+ Update: this occurred after installation failed.  These problems may be due 
to the usb drive, made with Rufus on Win 7.  I haven't had so many problems 
using linux-made drives.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
-  memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
-  _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
-  _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
-  _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
-  openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
+  memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
+  _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
+  _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
+  _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
+  openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-scanner crashed with signal 7 in memset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

  Xfce Panel Switch was the only application I had open.  If by chance it's not 
in the attached datadumps, I'm trying the 20180410 xubuntu bionic daily build.
- Update: this occurred after installation failed.  These problems may be due 
to the usb drive, made with Rufus on Win 7.  I haven't had so many problems 
using linux-made drives.
+ Update: this also occurred after installation failed.  These problems may be 
due to the usb drive, made with Rufus on Win 7.  I haven't had so many problems 
using linux-made drives.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
   memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
   _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
   _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
   _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
   openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-s

[Touch-packages] [Bug 1762780] Re: gst-plugin-scanner crashed with signal 7 in memset()

2018-04-10 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  gst-plugin-scanner crashed with signal 7 in memset()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Xfce Panel Switch was the only application I had open.  If by chance it's not 
in the attached datadumps, I'm trying the 20180410 xubuntu bionic daily build.
  Update: this also occurred after installation failed.  These problems may be 
due to the usb drive, made with Rufus on Win 7.  I haven't had so many problems 
using linux-made drives.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
   memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
   _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
   _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
   _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
   openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-scanner crashed with signal 7 in memset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1762780/+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 1732002] Re: cloud images in lxc get ipv6 address

2018-04-10 Thread Ryan Harper
The MP has been moved to a github PR:

https://github.com/CanonicalLtd/netplan/pull/19

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system 
bus, ignoring transient hostname.
  Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
  Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nplan 0.30
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 18:27:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-04-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~raharper/netplan/+git/netplan/+merge/342976

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system 
bus, ignoring transient hostname.
  Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
  Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nplan 0.30
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 18:27:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1762807] Re: gnome-session-bin installed on Ubuntu MATE

2018-04-10 Thread Simon Quigley
** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+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 1762476] Re: cupsd crashed with SIGSEGV in create_local_bg_thread()

2018-04-10 Thread Launchpad Bug Tracker
This bug was fixed in the package cups - 2.2.7-1ubuntu2

---
cups (2.2.7-1ubuntu2) bionic; urgency=medium

  * Fixed another crash when creating temporary queues for IPP printers
(Issue #5290, LP: #1762476).

 -- Till Kamppeter   Mon,  9 Apr 2018 21:44:01
+0200

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

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

Title:
  cupsd crashed with SIGSEGV in create_local_bg_thread()

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  Crashed immediately after boot in ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Mon Apr  9 18:25:22 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-03-11 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  Lpstat:
   device for HP-Officejet-4620-series: 
hp:/net/Officejet_4620_series?hostname=HPA0481CC8AFF7.local
   device for Officejet_4620_series_C8AFF7_: 
ipp://HPA0481CC8AFF7.local:631/ipp/print
  MachineType: Acer Aspire VN7-791
  Papersize: a4
  PpdFiles:
   Officejet_4620_series_C8AFF7_: Officejet 4620 series
   HP-Officejet-4620-series: HP Officejet 4620 Series, hpcups 3.17.10
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=4df58e27-105a-45d5-8b11-76dcc3e66407 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=4df58e27-105a-45d5-8b11-76dcc3e66407 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x558440aec7fb:cmpb   $0x0,(%rax)
   PC (0x558440aec7fb) ok
   source "$0x0" ok
   destination "(%rax)" (0x392e373431783130) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? ()
   start_thread (arg=0x7f583f621700) at pthread_create.c:463
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: cupsd crashed with SIGSEGV in start_thread()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-791
  dmi.board.vendor: Acer
  dmi.board.version: V1.07
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2014:svnAcer:pnAspireVN7-791:pvrV1.07:rvnAcer:rnAspireVN7-791:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.family: Sharkbay System
  dmi.product.name: Aspire VN7-791
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1762476/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed

2018-04-10 Thread Bug Watch Updater
** Changed in: apt (Debian)
   Status: Unknown => Fix Released

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

Title:
  apt-get update hangs when apt-transport-https is not installed

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  When "apt-get update" is run on a docker container running Ubuntu
  v16.04 and containing an additional apt source repository hosted on an
  https webserver, the "apt-get update" command hangs.

  The hang happens after connections to http ubuntu hosts are complete,
  and apt-get remains stuck on "Working" at 0%. Removing the sources
  file for the https repo causes apt-get to complete normally.

  The source file contains 4 separate entries to 4 different repos on
  the same https server. When the source file is modified so that just
  *one* entry exists to one repo on the https server, we suddenly get a
  sensible error message that tells us that apt-transport-https needs to
  be installed.

  Installing apt-transport-https into the docker container before adding
  the sources list to the https servers works around the problem and
  sanity returns.

  Key notes:

  - The use of docker isn't related to the bug, except that the docker
  image doesn't contain the apt-transport-https package whereas our
  cloud images do contain this package by default. This can give the
  impression that this is a docker bug when it's not.

  - The hang in "apt-get update" seems to occur when the sources file
  contains more than one entry in the file. When just one entry exists
  in the file (and all other entries are commented out) a sensible error
  messages appears.

  - We encountered this on a host that didn't support cut and paste,
  sorry :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1762841] Re: dconf-editor path bar color is unreadable when in search mode

2018-04-10 Thread Launchpad Bug Tracker
** Branch linked: lp:~3v1n0/ubuntu-themes/theme-colors-definitions

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

Title:
  dconf-editor path bar color is unreadable when in search mode

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Open d-conf editor, hit ctrl+f:
   See https://imgur.com/kU7H1j1.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1762841/+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 1762841] Re: dconf-editor path bar color is unreadable when in search mode

2018-04-10 Thread Treviño
** Changed in: ubuntu-themes (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  dconf-editor path bar color is unreadable when in search mode

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Open d-conf editor, hit ctrl+f:
   See https://imgur.com/kU7H1j1.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1762841/+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 1762841] [NEW] dconf-editor path bar color is unreadable when in search mode

2018-04-10 Thread Treviño
Public bug reported:

Open d-conf editor, hit ctrl+f:
 See https://imgur.com/kU7H1j1.png

** Affects: ubuntu-themes (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Triaged

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

Title:
  dconf-editor path bar color is unreadable when in search mode

Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Open d-conf editor, hit ctrl+f:
   See https://imgur.com/kU7H1j1.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1762841/+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 1749822] Re: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libvorbis package in Ubuntu:
  Confirmed

Bug description:
  after installing pdfsam from the appstore the progam did not start. I
  have update ubuntu in terminal and I have got the error. I have
  removed and reinstalled the program but no solution. Check the issue
  on forums and try the solution. The problem maintain the same

  Earlier today I have installed dropbox but this is function fine.

  Ubuntu 16.04.3 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvorbisenc2:amd64 1.3.5-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   libvorbis0a: Install
   libvorbis0a: Configure
   libvorbisenc2: Configure
   libvorbisfile3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Feb 15 22:05:56 2018
  DuplicateSignature:
   package:libvorbisenc2:amd64:1.3.5-3ubuntu0.1
   Setting up libvorbis0a:amd64 (1.3.5-3ubuntu0.1) ...
   dpkg: error processing package libvorbisenc2:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-11 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: libvorbis
  Title: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/1749822/+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 1501773] Re: ubiquity hook 'str' object has no attribute 'decode'

2018-04-10 Thread Wellington Torrejais da Silva
Maybe related to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1762228

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

Title:
  ubiquity hook 'str' object has no attribute 'decode'

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Ubiquity reports from wily have an hookerror

  Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
  symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_ubiquity.py", line 60, in 
add_info
  syslog = report['UbiquitySyslog'].decode('UTF-8')
  AttributeError: 'str' object has no attribute 'decode'

  That can be reproduce with "sudo ubuntu-bug ubiquity"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1501773/+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 1754686] Re: libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop

2018-04-10 Thread Hicks
*** This bug is a duplicate of bug 1754294 ***
https://bugs.launchpad.net/bugs/1754294

I have a problem with the library too. My conflict is with spotify-client and 
hosty.
Spotify-client requires libcurl3, and installing it uninstalls curl, which is 
required to run hosty.

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

Title:
  libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like
  slack-desktop

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Updating the curl package pulls in libcurl4, which for some reason
  forces libcurl3 to be removed. This prevents 3rd party apps that still
  build against libcurl3 from being installed. Isn't there a more
  graceful way to effect the transition from libcurl3 to libcurl4?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4 7.58.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:10:10 2018
  EcryptfsInUse: Yes
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686/+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 1762807] Re: gnome-session-bin installed on Ubuntu MATE

2018-04-10 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

2018-04-10 Thread Ryan Harper
ubuntu@foufoune:~$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
ubuntu@foufoune:~$ apt-cache policy systemd
systemd:
  Installed: 234-2ubuntu12.3
  Candidate: 234-2ubuntu12.3
  Version table:
 *** 234-2ubuntu12.3 500
500 http://azure.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 234-2ubuntu12.1 500
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
 234-2ubuntu12 500
500 http://azure.archive.ubuntu.com/ubuntu artful/main amd64 Packages


ubuntu@foufoune:~$ time ping  __cloud_init_expected_not_found
ping: __cloud_init_expected_not_found: Temporary failure in name resolution

real0m15.016s
user0m0.000s
sys 0m0.003s

After applying the workaround from comment #11, I see fast lookups
again.

ubuntu@foufoune:~$ cat /etc/systemd/resolved.conf 
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
#FallbackDNS=
#Domains=
#LLMNR=yes
#MulticastDNS=yes
#DNSSEC=no
#Cache=yes
#DNSStubListener=udp
LLMNR=no

ubuntu@foufoune:~$ time ping  __cloud_init_expected_not_found
ping: __cloud_init_expected_not_found: Name or service not known

real0m0.006s
user0m0.000s
sys 0m0.001s

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  New
Status in linux source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-04-10 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-session - 3.28.1-0ubuntu1

---
gnome-session (3.28.1-0ubuntu1) bionic; urgency=medium

  * New upstream release
- Don't create ~/.config as world-readable. (LP: #1735929)
  * Drop xsmp-don-t-check-for-HAVE_XTRANS.patch: Applied in new release

 -- Jeremy Bicha   Tue, 10 Apr 2018 10:09:40 -0400

** Changed in: gnome-session (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Fix Released
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Released
Status in session-migration package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  Fix Released
Status in session-migration source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

2018-04-10 Thread Ryan Harper
I'm seeing this on Artful as well, in Azure cloud.

** Also affects: glibc (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  New
Status in linux source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-10 Thread Luke Williams
I have an Asus ROG GL703VD and have a similar issue. The display shows the ROG 
display, then flashes purple for a second (Grub menu splash before the Ubuntu 
splash logo, which doesn't display on the laptop, but does on the HDMI display) 
then goes blank and never comes online. Even pressing CTRL+ALT+F1-6 does not 
switch between virtual terminals on the laptop display, it does shift on the 
mirrored HDMI display. The only way to get a display is to hook up a monitor to 
the HDMI port and then logging in and setting the display to mirror mode. In 
fact, this is the only way to install Bionic on the device as even booting the 
install media with nouveau blacklisted doesn't work. In previous releases, 
running nouveau.modeset=0 would bring up the display properly and then you 
could install, but with Bionic, this is does not work. Also, installing the 
Bionic kernel in Xenial or Artful creates the same condition for those 
releases.  
I have looked at the logs and settings everywhere, and from what I can tell 
everything appears to be loading properly. Gnome sees both displays when 
connected, but the laptop display remains black.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1758712] Re: GNOME Builder Omnibar theming issue with Ambiance

2018-04-10 Thread Treviño
This fix has to be done inside gnome-builder itself, as it provides a
way to define custom theming for various styles [1], and it can't be
overridden at theme level. Being gnome-builder in universe I think we
can lower this issue and not really something critical for release.

A rule like

omnibar:not(.building) entry {
  color: alpha(@dark_fg_color, 0.8);
}


Should already fix it.

[1] https://github.com/GNOME/gnome-builder/tree/master/data/themes

** No longer affects: ubuntu-themes (Ubuntu Bionic)

** Package changed: ubuntu-themes (Ubuntu) => gnome-builder (Ubuntu)

** Changed in: gnome-builder (Ubuntu)
   Importance: High => Medium

** Changed in: gnome-builder (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

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

Title:
  GNOME Builder Omnibar theming issue with Ambiance

Status in gnome-builder package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04
  GNOME Builder 3.28.0 (from the GNOME3 Staging PPA, will be uploaded directly 
to 18.04 soon)

  In the center of the headerbar is a widget the GNOME Builder
  documentation calls the Omnibar.

  In the Adwaita screenshot, it has a pale green background showing that
  the build has completed successfully.

  In the Ambiance screenshot, the Omnibar is unreadable because it's
  basically dark grey text on dark grey background with only minimal
  contrast.

  (Note there is a screenshot problem because of a mutter bug. Ambiance
  should have orange highlights and Adwaita should be blue, but it's
  basically reversed! The screenshot bug doesn't really affect this
  theming bug).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-builder/+bug/1758712/+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 1762818] Re: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor

2018-04-10 Thread Roger Binns
** Attachment added: "Xorg log when booting with 18.04 kernel"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+attachment/5109717/+files/newkernel.txt

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

Title:
  Regression: Upgrading from 17.10 to 18.04 reduces resolution available
  on monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptom: booting 18.04 kernel reduces resolution available while 17.10
  kernel (on 18.04) does not

  I have a 3 identical monitor setup - all at 2560x1600 native
  resolution.  If I boot the current 18.04 kernel 4.15.0-13-generic then
  the third monitor does not have the native resolution available.  If I
  reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors
  have the native resolution available.

  On the video card the monitors are connected to HDMI, DisplayPort and
  DVI.  On the monitors themselves the connectors are HDMI, DisplayPort
  and HDMI.  (3rd monitor is using DVI to HDMI cable.)

  Xorg logs show identical EDID information between the kernels.
  18.04's just decides to not make 2560x1600 available, having 2048x1080
  or 1920x1200 as the highest.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Apr 10 12:17:31 2018
  DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] 
(rev e5) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 
450/455/460/560] [1458:230a]
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1456) killed by TERM signal
  MachineType: Supermicro C7Z170-SQ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago)
  dmi.bios.date: 12/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: C7Z170-SQ
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: C7Z170-SQ
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  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.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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+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 1762818] [NEW] Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor

2018-04-10 Thread Roger Binns
Public bug reported:

Symptom: booting 18.04 kernel reduces resolution available while 17.10
kernel (on 18.04) does not

I have a 3 identical monitor setup - all at 2560x1600 native resolution.
If I boot the current 18.04 kernel 4.15.0-13-generic then the third
monitor does not have the native resolution available.  If I reboot with
the last 17.10 kernel 4.13.0-37-generic then all monitors have the
native resolution available.

On the video card the monitors are connected to HDMI, DisplayPort and
DVI.  On the monitors themselves the connectors are HDMI, DisplayPort
and HDMI.  (3rd monitor is using DVI to HDMI cable.)

Xorg logs show identical EDID information between the kernels.  18.04's
just decides to not make 2560x1600 available, having 2048x1080 or
1920x1200 as the highest.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Apr 10 12:17:31 2018
DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev 
e5) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 
450/455/460/560] [1458:230a]
LightdmGreeterLogOld:
 ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
 ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
 upstart: indicator-application main process (1456) killed by TERM signal
MachineType: Supermicro C7Z170-SQ
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago)
dmi.bios.date: 12/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: Default string
dmi.board.name: C7Z170-SQ
dmi.board.vendor: Supermicro
dmi.board.version: 1.01A
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: Default string
dmi.product.name: C7Z170-SQ
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
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.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 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 resolution ubuntu

** Attachment added: "Xorg log when booting with 17.10 kernel"
   
https://bugs.launchpad.net/bugs/1762818/+attachment/5109700/+files/oldkernel.txt

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

Title:
  Regression: Upgrading from 17.10 to 18.04 reduces resolution available
  on monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptom: booting 18.04 kernel reduces resolution available while 17.10
  kernel (on 18.04) does not

  I have a 3 identical monitor setup - all at 2560x1600 native
  resolution.  If I boot the current 18.04 kernel 4.15.0-13-generic then
  the third monitor does not have the native resolution available.  If I
  reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors
  have the native resolution available.

  On the video card the monitors are connected to HDMI, DisplayPort and
  DVI.  On the monitors themselves the connectors are HDMI, DisplayPort
  and HDMI.  (3rd monitor is using DVI to HDMI cable.)

  Xorg logs show identical EDID information between the kernels.
  18.04's just decides to not make 2560x1600 available, having 2048x1080
  or 1920x1200 as the highest.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

2018-04-10 Thread Stephan Woidowski
It affects me too. I have the LTS of this version and the network
connection can't still be established because of a network connection
failure. All devices are there and Linux told me that the connection is
established but it is directly interrupted with the told message that
there is no connection available.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1762813] Re: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-04-10 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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

Status in util-linux package in Ubuntu:
  New

Bug description:
  Regular software upgrade fails

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Tue Apr 10 20:02:57 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-17 (906 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (619 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1762813/+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 1762807] Re: gnome-session-bin installed on Ubuntu MATE

2018-04-10 Thread Martin Wimpress
** Branch linked: lp:~ubuntu-mate-dev/software-properties/lp1762807

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+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 1762813] [NEW] package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-04-10 Thread Stephen Hayward
Public bug reported:

Regular software upgrade fails

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.5
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Tue Apr 10 20:02:57 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-10-17 (906 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: util-linux
Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-30 (619 days ago)

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


** Tags: amd64 apport-package package-from-proposed xenial

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

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

Status in util-linux package in Ubuntu:
  New

Bug description:
  Regular software upgrade fails

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Tue Apr 10 20:02:57 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-17 (906 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (619 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1762813/+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 1563945] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2018-04-10 Thread carlos
I had this issue before with ubuntu 16.04lts. The weird part is that it worked 
fine until one update that failed, i believe it was by end of 2017. 
unfortunately and go figure ;),had same issue with  the previous version of 
elementaryOS, mint and now ubuntu mate. 
Weirdly enough for me, with solusOS as well. i'm not a tec./linux savvy but i 
was always able to install  different linux distros by myself but lately ... or 
its me that arrived at the end of my linux learning curve or i will need to 
replace soon my 11 year old x61s.

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess installed pre-removal script returned
  error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  interesting issues while updating packages this morning...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 30 09:33:28 2016
  DpkgTerminalLog:
   Removing avahi-discover (0.6.32~rc+dfsg-1ubuntu2) ...
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  DuplicateSignature:
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-01-06 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1563945/+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 1762807] Re: gnome-session-bin installed on Ubuntu MATE

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+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 1762807] [NEW] gnome-session-bin installed on Ubuntu MATE

2018-04-10 Thread Martin Wimpress
Public bug reported:

Ubuntu MATE seeds software-properties-gtk which causes gnome-session-bin
to be pulled into the Ubuntu MATE image. This issue arises because
debian/control doesn't Recommends: mate-session-manager for software-
properties-gtk.

To resolve this issue debian/control for software-properties-gtk should
be updated to:

Recommends: gnome-session-bin | xfce4-session | lubuntu-default-settings
| lxqt-session | mate-session-manager, gnome-keyring

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+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 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-10 Thread Raul Dias
The simplest solution was to add the configuration:

Section "InputClass"
Identifier "NextWindows 1900 HID Touchscreen"
MatchUSBID "1926:0003"
Driver "evdev"
EndSection

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

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg package in Ubuntu:
  New

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  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.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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1730028] Re: logspam about Duplicate line for path "/var/log"

2018-04-10 Thread Brian Murray
** Also affects: rsyslog (Ubuntu Bionic)
   Importance: High
   Status: Fix Committed

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: 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/1730028

Title:
  logspam about Duplicate line for path "/var/log"

Status in rsyslog package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in rsyslog source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Similar to bug 1484027, but that's marked 'Fix released', so something
  must have regressed in the meantime.

  $ journalctl | grep "Duplicate line" | wc -l
  58

  $ grep "/var/log " /usr/lib/tmpfiles.d/*
  /usr/lib/tmpfiles.d/00rsyslog.conf:# Override systemd's default 
tmpfiles.d/var.conf to make /var/log writable by
  /usr/lib/tmpfiles.d/00rsyslog.conf:d /var/log 0775 root syslog -
  /usr/lib/tmpfiles.d/var.conf:d /var/log 0755 - - -

  
  Ideally I'd see at most one line about this in my logs.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu20
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Nov  3 19:42:41 2017
  InstallationDate: Installed on 2016-04-04 (578 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  MachineType: Supermicro SSG-6038R-E1CR16L
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=UUID=d1ab8bd8-41d5-4142-92d6-d0926539807b ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/systemd-resolved.service → 
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRH-iT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/17/2015:svnSupermicro:pnSSG-6038R-E1CR16L:pvr123456789:rvnSupermicro:rnX10DRH-iT:rvr1.01:cvnSupermicro:ct1:cvrDefaultstring:
  dmi.product.name: SSG-6038R-E1CR16L
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1730028/+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 1762603] Re: bluetooth keeps turning off

2018-04-10 Thread Aurélien PIERRE
Ok I troubleshot this problem.

Apparently, it came from the package `connman`, an Intel utility to
manage wlan and bluetooth that I installed wrongly since it's intended
for embedded systems.

Removing it solved all my problems.

** Package changed: bluez (Ubuntu) => connman (Ubuntu)

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

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

Title:
  bluetooth keeps turning off

Status in connman package in Ubuntu:
  Invalid

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/connman/+bug/1762603/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed

2018-04-10 Thread Julian Andres Klode
I'm not sure when we fixed that, but we did. So bionic works fine. Not
sure about artful.

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Bug watch added: Debian Bug tracker #870675
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870675

** Also affects: apt (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870675
   Importance: Unknown
   Status: Unknown

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

Title:
  apt-get update hangs when apt-transport-https is not installed

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  When "apt-get update" is run on a docker container running Ubuntu
  v16.04 and containing an additional apt source repository hosted on an
  https webserver, the "apt-get update" command hangs.

  The hang happens after connections to http ubuntu hosts are complete,
  and apt-get remains stuck on "Working" at 0%. Removing the sources
  file for the https repo causes apt-get to complete normally.

  The source file contains 4 separate entries to 4 different repos on
  the same https server. When the source file is modified so that just
  *one* entry exists to one repo on the https server, we suddenly get a
  sensible error message that tells us that apt-transport-https needs to
  be installed.

  Installing apt-transport-https into the docker container before adding
  the sources list to the https servers works around the problem and
  sanity returns.

  Key notes:

  - The use of docker isn't related to the bug, except that the docker
  image doesn't contain the apt-transport-https package whereas our
  cloud images do contain this package by default. This can give the
  impression that this is a docker bug when it's not.

  - The hang in "apt-get update" seems to occur when the sources file
  contains more than one entry in the file. When just one entry exists
  in the file (and all other entries are commented out) a sensible error
  messages appears.

  - We encountered this on a host that didn't support cut and paste,
  sorry :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed

2018-04-10 Thread Julian Andres Klode
Queued the fix for xenial in my repo for CI.

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

Title:
  apt-get update hangs when apt-transport-https is not installed

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  When "apt-get update" is run on a docker container running Ubuntu
  v16.04 and containing an additional apt source repository hosted on an
  https webserver, the "apt-get update" command hangs.

  The hang happens after connections to http ubuntu hosts are complete,
  and apt-get remains stuck on "Working" at 0%. Removing the sources
  file for the https repo causes apt-get to complete normally.

  The source file contains 4 separate entries to 4 different repos on
  the same https server. When the source file is modified so that just
  *one* entry exists to one repo on the https server, we suddenly get a
  sensible error message that tells us that apt-transport-https needs to
  be installed.

  Installing apt-transport-https into the docker container before adding
  the sources list to the https servers works around the problem and
  sanity returns.

  Key notes:

  - The use of docker isn't related to the bug, except that the docker
  image doesn't contain the apt-transport-https package whereas our
  cloud images do contain this package by default. This can give the
  impression that this is a docker bug when it's not.

  - The hang in "apt-get update" seems to occur when the sources file
  contains more than one entry in the file. When just one entry exists
  in the file (and all other entries are commented out) a sensible error
  messages appears.

  - We encountered this on a host that didn't support cut and paste,
  sorry :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1197808] Re: SFTP Support ! Still nothing ?

2018-04-10 Thread David Lechner
*** This bug is a duplicate of bug 311029 ***
https://bugs.launchpad.net/bugs/311029

** This bug has been marked a duplicate of bug 311029
   curl and pycurl is not compiled with sftp support

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

Title:
  SFTP Support ! Still nothing ?

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I don't understand why I can't use on a fresh install of Ubuntu 13.04 some 
tools relying on curl with SFTP support. I have to recompile curl myself and it 
cause tons of errors when I run apt-get upgrade. It would be nice to have the 
possibility to enable it easily. 
  It's around 1+ hour to compile everything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1197808/+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 1762780] Stacktrace.txt

2018-04-10 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1762780/+attachment/5109504/+files/Stacktrace.txt

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

Title:
  gst-plugin-scanner crashed with signal 7 in memset()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Xfce Panel Switch was the only application I had open.  If by chance
  it's not in the attached datadumps, I'm trying the 20180410 xubuntu
  bionic daily build.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
   memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
   _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
   _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
   _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
   openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-scanner crashed with signal 7 in memset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1762780/+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 1762780] ThreadStacktrace.txt

2018-04-10 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1762780/+attachment/5109506/+files/ThreadStacktrace.txt

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

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Medium

** 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/1762780

Title:
  gst-plugin-scanner crashed with signal 7 in memset()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Xfce Panel Switch was the only application I had open.  If by chance
  it's not in the attached datadumps, I'm trying the 20180410 xubuntu
  bionic daily build.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
   memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
   _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
   _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
   _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
   openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-scanner crashed with signal 7 in memset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1762780/+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 1762780] StacktraceSource.txt

2018-04-10 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1762780/+attachment/5109505/+files/StacktraceSource.txt

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

Title:
  gst-plugin-scanner crashed with signal 7 in memset()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Xfce Panel Switch was the only application I had open.  If by chance
  it's not in the attached datadumps, I'm trying the 20180410 xubuntu
  bionic daily build.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
   memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
   _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
   _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
   _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
   openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-scanner crashed with signal 7 in memset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1762780/+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 1762780] gst-plugin-scanner crashed with signal 7 in memset()

2018-04-10 Thread Apport retracing service
StacktraceTop:
 memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
 _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
 _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
 _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
 openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63

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

Title:
  gst-plugin-scanner crashed with signal 7 in memset()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Xfce Panel Switch was the only application I had open.  If by chance
  it's not in the attached datadumps, I'm trying the 20180410 xubuntu
  bionic daily build.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
   memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
   _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
   _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
   _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
   openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-scanner crashed with signal 7 in memset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1762780/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed

2018-04-10 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: New => Fix Released

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

Title:
  apt-get update hangs when apt-transport-https is not installed

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  When "apt-get update" is run on a docker container running Ubuntu
  v16.04 and containing an additional apt source repository hosted on an
  https webserver, the "apt-get update" command hangs.

  The hang happens after connections to http ubuntu hosts are complete,
  and apt-get remains stuck on "Working" at 0%. Removing the sources
  file for the https repo causes apt-get to complete normally.

  The source file contains 4 separate entries to 4 different repos on
  the same https server. When the source file is modified so that just
  *one* entry exists to one repo on the https server, we suddenly get a
  sensible error message that tells us that apt-transport-https needs to
  be installed.

  Installing apt-transport-https into the docker container before adding
  the sources list to the https servers works around the problem and
  sanity returns.

  Key notes:

  - The use of docker isn't related to the bug, except that the docker
  image doesn't contain the apt-transport-https package whereas our
  cloud images do contain this package by default. This can give the
  impression that this is a docker bug when it's not.

  - The hang in "apt-get update" seems to occur when the sources file
  contains more than one entry in the file. When just one entry exists
  in the file (and all other entries are commented out) a sensible error
  messages appears.

  - We encountered this on a host that didn't support cut and paste,
  sorry :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1761684] Re: Regression in lists like gnome-boxes

2018-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-boxes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Regression in lists like gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+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 1762780] [NEW] gst-plugin-scanner crashed with signal 7 in memset()

2018-04-10 Thread Sean Cleary
Public bug reported:

Xfce Panel Switch was the only application I had open.  If by chance
it's not in the attached datadumps, I'm trying the 20180410 xubuntu
bionic daily build.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: libgstreamer1.0-0 1.14.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CasperVersion: 1.393
Date: Tue Apr 10 16:23:52 2018
ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 7
SourcePackage: gstreamer1.0
StacktraceTop:
 memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
 _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
 _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
 _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
 openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
Title: gst-plugin-scanner crashed with signal 7 in memset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gst-plugin-scanner crashed with signal 7 in memset()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Xfce Panel Switch was the only application I had open.  If by chance
  it's not in the attached datadumps, I'm trying the 20180410 xubuntu
  bionic daily build.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.393
  Date: Tue Apr 10 16:23:52 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l 
/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 7
  SourcePackage: gstreamer1.0
  StacktraceTop:
   memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
   _dl_map_segments (loader=0x7ffd5f9af650, has_holes=, 
maplength=, nloadcmds=2, loadcmds=, 
type=, header=, fd=, 
l=0x557b3af33280) at ./dl-map-segments.h:131
   _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf "libgomp.so.1", 
origname=origname@entry=0x0, fd=, fbp=fbp@entry=0x7ffd5f9af990, 
realname=, loader=loader@entry=0x557b3af2feb0, l_type=, mode=, stack_endp=, nsid=) 
at dl-load.c:1126
   _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf "libgomp.so.1", 
type=2, trace_mode=0, mode=, nsid=) at 
dl-load.c:2389
   openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63
  Title: gst-plugin-scanner crashed with signal 7 in memset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1762780/+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 1762766] [NEW] apt-get update hangs when apt-transport-https is not installed

2018-04-10 Thread Graham Leggett
Public bug reported:

When "apt-get update" is run on a docker container running Ubuntu v16.04
and containing an additional apt source repository hosted on an https
webserver, the "apt-get update" command hangs.

The hang happens after connections to http ubuntu hosts are complete,
and apt-get remains stuck on "Working" at 0%. Removing the sources file
for the https repo causes apt-get to complete normally.

The source file contains 4 separate entries to 4 different repos on the
same https server. When the source file is modified so that just *one*
entry exists to one repo on the https server, we suddenly get a sensible
error message that tells us that apt-transport-https needs to be
installed.

Installing apt-transport-https into the docker container before adding
the sources list to the https servers works around the problem and
sanity returns.

Key notes:

- The use of docker isn't related to the bug, except that the docker
image doesn't contain the apt-transport-https package whereas our cloud
images do contain this package by default. This can give the impression
that this is a docker bug when it's not.

- The hang in "apt-get update" seems to occur when the sources file
contains more than one entry in the file. When just one entry exists in
the file (and all other entries are commented out) a sensible error
messages appears.

- We encountered this on a host that didn't support cut and paste, sorry
:(

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

** Summary changed:

- apt-get update hangs when apt-transport-https is no installed
+ apt-get update hangs when apt-transport-https is not installed

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

Title:
  apt-get update hangs when apt-transport-https is not installed

Status in apt package in Ubuntu:
  New

Bug description:
  When "apt-get update" is run on a docker container running Ubuntu
  v16.04 and containing an additional apt source repository hosted on an
  https webserver, the "apt-get update" command hangs.

  The hang happens after connections to http ubuntu hosts are complete,
  and apt-get remains stuck on "Working" at 0%. Removing the sources
  file for the https repo causes apt-get to complete normally.

  The source file contains 4 separate entries to 4 different repos on
  the same https server. When the source file is modified so that just
  *one* entry exists to one repo on the https server, we suddenly get a
  sensible error message that tells us that apt-transport-https needs to
  be installed.

  Installing apt-transport-https into the docker container before adding
  the sources list to the https servers works around the problem and
  sanity returns.

  Key notes:

  - The use of docker isn't related to the bug, except that the docker
  image doesn't contain the apt-transport-https package whereas our
  cloud images do contain this package by default. This can give the
  impression that this is a docker bug when it's not.

  - The hang in "apt-get update" seems to occur when the sources file
  contains more than one entry in the file. When just one entry exists
  in the file (and all other entries are commented out) a sensible error
  messages appears.

  - We encountered this on a host that didn't support cut and paste,
  sorry :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-10 Thread Raul Dias
Removing xserver-xorg-input-libinput did the tricky.
Now it uses evdev.  However, that shouldn't need be necessary.

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

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg package in Ubuntu:
  New

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  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.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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-10 Thread Raul Dias
The problem might also involve udev, as by these lines:

[   800.429] (II) event5  - NextWindow Touchscreen: is tagged by udev as: Tablet
[   800.429] (EE) event5  - NextWindow Touchscreen: libinput bug: missing 
tablet capabilities: btn-stylus resolution.Ignoring this device.
[   800.429] (II) event5  - NextWindow Touchscreen: device is a tablet
[   800.429] (II) event5  - failed to create input device '/dev/input/event5'.

udev should recognize as TouchScreen, not Tablet.

On previous Xorgs, evdev was used, not libinput.

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

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg package in Ubuntu:
  New

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  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.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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-04-10 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-session/ubuntu

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Fix Released
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Committed
Status in session-migration package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  Fix Committed
Status in session-migration source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-04-10 Thread Jeremy Bicha
** Changed in: gnome-session (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Fix Released
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Committed
Status in session-migration package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  Fix Committed
Status in session-migration source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1757565] Re: btrfs and tar sparse truncate archives

2018-04-10 Thread Ryan Harper
Verified artful-proposed.

root@ubuntu:~# cat /etc/cloud/build.info 
build_name: server
serial: 20180404
root@ubuntu:~# uname -a
Linux ubuntu 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:~# mount /dev/sda /mnt 
root@ubuntu:~# grep sda /proc/mounts 
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0
root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir 
-p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
0ce8c4139740198926273853defcb12a  -
root@ubuntu:~# dpkg --list | grep virtual
ii  linux-headers-virtual  4.13.0.38.41 
amd64Virtual Linux kernel headers
ii  linux-image-virtual4.13.0.38.41 
amd64Virtual Linux kernel image
ii  linux-virtual  4.13.0.38.41 
amd64Minimal Generic Linux kernel and headers
ii  open-vm-tools  2:10.1.10-3ubuntu0.1 
amd64Open VMware Tools for virtual machines hosted on 
VMware (CLI)
root@ubuntu:~# apt update && apt install linux-image-virtual 
Hit:1 http://archive.ubuntu.com/ubuntu artful InRelease
Hit:2 http://security.ubuntu.com/ubuntu artful-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu artful-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu artful-backports InRelease
Get:5 http://archive.ubuntu.com/ubuntu artful-proposed InRelease [235 kB]
Get:6 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 
[62.3 kB]
Get:7 http://archive.ubuntu.com/ubuntu artful-proposed/main Translation-en 
[26.1 kB]
Fetched 323 kB in 1s (206 kB/s)   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
29 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  grub-pc-bin
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  linux-headers-4.13.0-39 linux-headers-4.13.0-39-generic linux-headers-generic 
linux-headers-virtual linux-image-4.13.0-39-generic
  linux-virtual
Suggested packages:
  fdutils linux-doc-4.13.0 | linux-source-4.13.0 linux-tools
The following NEW packages will be installed:
  linux-headers-4.13.0-39 linux-headers-4.13.0-39-generic 
linux-image-4.13.0-39-generic
The following packages will be upgraded:
  linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual
4 upgraded, 3 newly installed, 0 to remove and 25 not upgraded.
Need to get 32.5 MB of archives.
After this operation, 156 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-4.13.0-39 all 4.13.0-39.44 [10.9 MB]
Get:2 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-4.13.0-39-generic amd64 4.13.0-39.44 [704 kB]
Get:3 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-image-4.13.0-39-generic amd64 4.13.0-39.44 [20.9 MB]
Get:4 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-virtual 
amd64 4.13.0.39.42 [1780 B]
Get:5 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-image-virtual amd64 4.13.0.39.42 [2308 B]
Get:6 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-virtual amd64 4.13.0.39.42 [1766 B]
Get:7 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-generic amd64 4.13.0.39.42 [2294 B]
Fetched 32.5 MB in 5s (5459 kB/s)
Selecting previously unselected package linux-headers-4.13.0-39.
(Reading database ... 57609 files and directories currently installed.)
Preparing to unpack .../0-linux-headers-4.13.0-39_4.13.0-39.44_all.deb ...
Unpacking linux-headers-4.13.0-39 (4.13.0-39.44) ...
Selecting previously unselected package linux-headers-4.13.0-39-generic.
Preparing to unpack 
.../1-linux-headers-4.13.0-39-generic_4.13.0-39.44_amd64.deb ...
Unpacking linux-headers-4.13.0-39-generic (4.13.0-39.44) ...
Selecting previously unselected package linux-image-4.13.0-39-generic.
Preparing to unpack .../2-linux-image-4.13.0-39-generic_4.13.0-39.44_amd64.deb 
...
Done.
Unpacking linux-image-4.13.0-39-generic (4.13.0-39.44) ...
Preparing to unpack .../3-linux-virtual_4.13.0.39.42_amd64.deb ...
Unpacking linux-virtual (4.13.0.39.42) over (4.13.0.38.41) ...
Preparing to unpack .../4-linux-image-virtual_4.13.0.39.42_amd64.deb ...
Unpacking linux-image-virtual (4.13.0.39.42) over (4.13.0.38.41) ...
Preparing to unpack .../5-linux-headers-virtual_4.13.0.39.42_amd64.deb ...
Unpacking linux-headers-virtual 

[Touch-packages] [Bug 1762630] Re: Why does not python3 depend on dh-python?

2018-04-10 Thread dino99
in the past days i've seen a few packages been rebuild with dh-python. I
suppose the job is not yet complete, as your request. So the report
makes sense.

About your 'base packages' i'm scared it cant be stable as it is.

** Changed in: python3-defaults (Ubuntu)
   Status: Incomplete => New

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

Title:
  Why does not python3 depend on dh-python?

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I get the following while trying to install python3 on Bionic.

  dpkg-query: package 'dh-python' is not installed
  Use dpkg --info (= dpkg-deb --info) to examine archive files,
  and dpkg --contents (= dpkg-deb --contents) to list their contents.

  What I can tell, every other Ubuntu release has this dependency but
  not Bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1762630/+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 1762603] Re: bluetooth keeps turning off

2018-04-10 Thread Aurélien PIERRE
Yes it looks like the same bug (at least for the GUI part), and it's a
Thinkpad as well.

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

Title:
  bluetooth keeps turning off

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1762603/+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 1761782] Re: do-release-upgrade from 12.04 to 14.04 - package linux-firmware 1.127.24 failed to install/upgrade: subprocess installed post-installation script returned error exit

2018-04-10 Thread Theo
*** This bug is a duplicate of bug 1746326 ***
https://bugs.launchpad.net/bugs/1746326

Bug https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/1746326 does not look like a problem of the /boot filesystem
out of space.

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

Title:
  do-release-upgrade from 12.04 to 14.04 - package linux-firmware
  1.127.24 failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried do-release-upgrade from 12.04 to 14.04

  Not sure what is going on but doing the following on another login
  screen indicates that the upgrade has occurred

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

  Hmm /boot is 100%

  apt-get autoremove

  failed again after /boot filled up again
  manuall removed stuff Eg.
  root@host1:/boot# rm initrd.img-3.2.0-75-generic initrd.img-3.2.0-77-generic 
initrd.img-3.2.0-80-generic initrd.img-3.2.0-83-generic 
initrd.img-3.2.0-95-generic

  repeated apt-get autoremove which just re-creates the above and
  results in the following

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-3.13.0-145-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-image-extra-3.13.0-145-generic
   linux-image-generic
   linux-generic
   linux-image-server
   linux-server
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Tried the following

  apt-get update (also did that before the do-release-upgrade)
  apt-get autoremove

  and that worked

  rebooting - wish me luck

  rebooted

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.24
  ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Apr  6 16:50:21 2018
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-03-12 (1486 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2018-04-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1761782/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

2018-04-10 Thread Olivier Tilloy
There's active work going on upstream (see
https://bugzilla.gnome.org/show_bug.cgi?id=746422 and
https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=bg
/dns-bgo746422) to fix the issue.

https://bugzilla.gnome.org/show_bug.cgi?id=746422#c36 explains how.

Once in master, it would probably be doable to backport those changes
(including
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b2f306ac3d84283fdebb225079f354afb8c2a752)
to the 1.10 branch, which is what's in bionic (1.10.6-2ubuntu1).
Backporting to xenial (currently 1.2.6-0ubuntu0.16.04.2) would likely be
an entirely different story.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1762725] [NEW] Ubuntu Budgie selects USB mic as default audio output after every reboot.

2018-04-10 Thread Carlos Echenique
Public bug reported:

Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic
as the default output device. I have to manually select the analog
output every time. Also, the Default effect sound does not make any
noise.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  guru   2355 F pulseaudio
 /dev/snd/controlC1:  guru   2355 F pulseaudio
 /dev/snd/controlC0:  guru   2355 F pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Tue Apr 10 08:54:30 2018
InstallationDate: Installed on 2018-04-07 (2 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.52
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 4
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A37
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug bionic

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

Title:
  Ubuntu Budgie selects USB mic as default audio output after every
  reboot.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Whenever I reboot my system, pulseaudio selects my Samson Meteor USB
  mic as the default output device. I have to manually select the analog
  output every time. Also, the Default effect sound does not make any
  noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2355 F pulseaudio
   /dev/snd/controlC1:  guru   2355 F pulseaudio
   /dev/snd/controlC0:  guru   2355 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr 10 08:54:30 2018
  InstallationDate: Installed on 2018-04-07 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1762725/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-04-10 Thread Aurélien PIERRE
Same bug on Ubuntu 18.04 / Thinkpad P51.

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+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 1757388] Re: bridge device is missing

2018-04-10 Thread Marco
Re-installing Ubuntu 18.04 server solved the issue.

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

Title:
  bridge device is missing

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04: Since last dist-upgrade of the bridge-utils (2018-03-21)
  the bridge netwok device 'br0' is missing. A 'ls /sys/class/net'
  prints the devices 'enp3s0  lo  lxcbr0  virbr0  virbr0-nic' only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1757388/+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 1762630] Re: Why does not python3 depend on dh-python?

2018-04-10 Thread Markus Lindberg
I'm sorry the environment I'm using does not have all the base packages.
But I'm still curious why the dh-python dependency was removed from the
python3 package.

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

Title:
  Why does not python3 depend on dh-python?

Status in python3-defaults package in Ubuntu:
  Incomplete

Bug description:
  I get the following while trying to install python3 on Bionic.

  dpkg-query: package 'dh-python' is not installed
  Use dpkg --info (= dpkg-deb --info) to examine archive files,
  and dpkg --contents (= dpkg-deb --contents) to list their contents.

  What I can tell, every other Ubuntu release has this dependency but
  not Bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1762630/+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 1762622] Re: libu2f-udev still not installed by upgrade

2018-04-10 Thread Jeremy Bicha
ubuntu-desktop depends on libu2f-udev so if you intentionally
uninstalled ubuntu-desktop, it is expected that you won't get new
ubuntu-desktop dependencies installed automatically.

If you don't have ubuntu-desktop installed, it's your responsibility to
keep up with changes to ubuntu-desktop.

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

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

Title:
  libu2f-udev still not installed by  upgrade

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Got that proposed update:

  ---
  ubuntu-meta (1.415) bionic; urgency=medium

* Refreshed dependencies
* Added libu2f-udev to desktop LP: #1752202
* Removed vlan from server

   -- Dimitri John Ledkov  Mon, 09 Apr 2018 15:54:40 +0100
  ---

  BUT

  Still not installed via that upgrade

  Test case:
  - system with ubuntu-desktop uninstalled due to unwanted apps and fonts
  - upgrade ubuntu-meta that should add libu2f-udev dependency
  - libu2f-udev is not added by the upgrade script; in fact it is still not a 
dependency

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-standard 1.415
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 10 07:52:22 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1762622/+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 1697377] Re: Change TextBoxes Direction for RTL languages

2018-04-10 Thread Reza-irdev
** Package changed: ubuntu => gtk+3.0 (Ubuntu)

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

Title:
  Change TextBoxes  Direction for RTL languages

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  My and all RTL language users problem is that there us no option to
  change text direction in a text-box! for example in windows when i
  press left CTRL+SHIFT text direction sets to LTR and when press right
  CTRL+SHIFT direction changes to RTL. It is a really big problem for us
  and its a essential feature. Also automatic direction detection base
  on language direction is not good solution at all.

  From: https://support.microsoft.com/en-us/help/12445/windows-keyboard-
  shortcuts

  Ctrl + Shift = Switch the keyboard layout when multiple keyboard
  layouts are available.

  
  See: 
https://blogs.technet.microsoft.com/office_global_experience/2010/02/19/useful-tricks-and-shortcuts-for-users-around-the-world/

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


  1   2   >