[Touch-packages] [Bug 1760078] [NEW] Double login required from suspend

[Kev Bowring]

Public bug reported:

Following a suspend.

Get unlock screen - which then gets me a desktop.

Returned to unlock screen to enter password a second time.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 30 12:09:46 2018
InstallationDate: Installed on 2018-03-08 (21 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Double login required from suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  Following a suspend.

  Get unlock screen - which then gets me a desktop.

  Returned to unlock screen to enter password a second time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 12:09:46 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  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/1760078/+subscriptions

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

[Touch-packages] [Bug 1759271] Re: Xorg freeze

[arcane]

I had no more freeze for the last day I think I gonna close this report
soon.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  I already had a freezing problem whith my computer that i resolved
  this way:

  Ubuntu 16&17 don't stop. Toshiba C50 B 19H [SOLVED]

  but, now i just had another freeze will the computer working (not
  during shutdown).

  I hope you can fix the problem or help me,

  Thanks,

  Thomas.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar 27 15:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Atom Processor Z36xxx/Z37xxx 
Series Graphics & Display [1179:f910]
  InstallationDate: Installed on 2018-03-26 (1 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: TOSHIBA SATELLITE C50-B
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=385e28ce-7be5-4689-b130-a0b80a6af38c ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 5.10
  dmi.board.asset.tag: *
  dmi.board.name: ZBWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-09100FFR:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name: SATELLITE C50-B
  dmi.product.version: PSCMLE-09100FFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Mar 27 15:09:36 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1759796] Related fix proposed to kolla (stable/queens)

[OpenStack Infra]

Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/557906

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

Title:
  Ubuntu images fail to build due to broken dh-python package

Status in kolla:
  New
Status in dh-python package in Ubuntu:
  New

Bug description:
  Some ubuntu images fails to build and block the gate.

  2018-03-28 15:07:13.498244 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-controller' to succeed!
  2018-03-28 15:07:13.498650 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-northd' to succeed!
  2018-03-28 15:07:13.498957 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'bifrost-base' to succeed!
  2018-03-28 15:07:13.499241 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovsdpdk' to succeed!
  2018-03-28 15:07:13.499559 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-sb-db-server' to succeed!
  2018-03-28 15:07:13.499867 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-nb-db-server' to succeed!

  http://logs.openstack.org/33/555733/1/check/kolla-build-ubuntu-
  source/72f9085/job-output.txt.gz#_2018-03-28_15_07_13_498244

  Looking more closely, it appears they fail to install lsb-release that
  depends on python3. Going up the dependency chain, the issue seems to
  be in dh-python that added a dependency on python3-distuils. However
  python3-distuils doesn't exist and should probably be
  python3-distutils.

  ()[root@f8bc5d1d504e bifrost-5.0.1.dev43]# apt-cache show dh-python
  Package: dh-python
  Priority: optional
  Section: python
  Installed-Size: 429
  Maintainer: Piotr Ożarowski 
  Architecture: all
  Version: 3.20180325ubuntu1~cloud0
  Replaces: python3 (<< 3.3.2-4~)
  Suggests: libdpkg-perl, dpkg-dev
  Depends: python3:any (>= 3.3.2-2~), python3-distuils
  Breaks: python3 (<< 3.3.2-4~)
  Supported: 60m
  Filename: pool/main/d/dh-python/dh-python_3.20180325ubuntu1~cloud0_all.deb
  Size: 89382
  SHA256: 5d31a348f141d7ca366eeb21b58633bed96a0b27417ce8759e1cb785cb1db8bc
  SHA1: a817acac0042ab6e22dd686376717a20e449ae03
  MD5sum: d89b5e505bbb93b57efe4bfb85fc353d
  Description: Debian helper tools for packaging Python libraries and 
applications
  Description-md5: b21cd6f99d6093fdc7e0ba30c8dd949f
  Multi-Arch: foreign
  Original-Maintainer: Piotr Ożarowski 

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

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

[Touch-packages] [Bug 1758930] Re: software-properties-gtk crashed with GLib.GError in __init__(): g-dbus-error-quark: Error calling StartServiceByName for org.gnome.OnlineAccounts: GDBus.Error:org.fr

[Andrea Azzarone]

Hey lewis this looks like a crash in gnome-online-accounts rather than
in software-properties. Do you get this all the times?

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

Title:
  software-properties-gtk crashed with GLib.GError in __init__(): g
  -dbus-error-quark: Error calling StartServiceByName for
  org.gnome.OnlineAccounts:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process
  org.gnome.OnlineAccounts received signal 11 (26)

Status in gnome-online-accounts package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Just showed up while I was working.  System was left desktop at work
  build with this guide.  www.tinyurl.com/donofrio1804

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.24
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 26 10:20:51 2018
  ExecutablePath: /usr/bin/software-properties-gtk
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonArgs: ['/usr/bin/software-properties-gtk']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with GLib.GError in __init__(): 
g-dbus-error-quark: Error calling StartServiceByName for 
org.gnome.OnlineAccounts: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process 
org.gnome.OnlineAccounts received signal 11 (26)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video

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

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

[Touch-packages] [Bug 1760073] [NEW] No network from suspend resume

[Kev Bowring]

Public bug reported:

Following a resume from suspend - no network available on machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 30 11:53:22 2018
InstallationDate: Installed on 2018-03-08 (21 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  No network from suspend resume

Status in lightdm package in Ubuntu:
  New

Bug description:
  Following a resume from suspend - no network available on machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:53:22 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  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/1760073/+subscriptions

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

[Touch-packages] [Bug 1759601] Re: [UIFe] 18.04 LTS Bionic Beaver Mascot

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity-slideshow-ubuntu - 136

---
ubiquity-slideshow-ubuntu (136) bionic; urgency=medium

  [ Jean-Baptiste Lallement ]
  * Kubuntu slideshow FTBFS:
- Fixed closing div tag (LP: #1760035)

 -- Jean-Baptiste Lallement   Fri,
30 Mar 2018 09:41:27 +0200

** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
   Status: New => Fix Released

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

Title:
  [UIFe] 18.04 LTS Bionic Beaver Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The mascots for this release needed adding to the welcome page of the
  slideshow.  The final versions of the mascots arrived after UIF and I
  updated the slideshow yesterday.

  As part of that updated I changed the string describing what software
  was available to include mention of the snap store.  Since snaps are
  core component of the desktop and GNOME Software (promoted snaps
  appearing on the front page of Software for example) I think this is
  an important change.

  The string changes are:

  -Say goodbye to searching the web for new software. With access to
  the Ubuntu Software Store, you can find and install new apps with
  ease. Just type in what you’re looking for, or explore categories such
  as Science, Education and Games, alongside helpful reviews from other
  users.

  +Say goodbye to searching the web for new software. With access to
  the Snap Store and the Ubuntu software archive, you can find and
  install new apps with ease. Just type in what you’re looking for, or
  explore categories such as Games, Graphics & Photography and
  Productivity, alongside helpful reviews from other users.

  
  Post to doc-team: 
https://lists.ubuntu.com/archives/ubuntu-doc/2018-March/020580.html
  Post to translators: 
https://lists.ubuntu.com/archives/ubuntu-translators/2018-March/007454.html

  
  Beavers and branch attached.

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Hans Joachim Desserud]

** Tags added: upgrade-software-version

-- 
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 in Bionic (mostly bug-fix release)

Status in bluez package in Ubuntu:
  New

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 1266675] Re: newusers error adding more than one user

[Ray]

lucenze...@gmail.com

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

** Changed in: ubuntu
   Status: Confirmed => Fix Committed

** Package changed: shadow (Debian) => debian

** Changed in: debian
   Importance: Unknown => Undecided

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

** Changed in: debian
 Remote watch: Debian Bug tracker #756630 => None

** Changed in: debian
 Assignee: (unassigned) => Ray (lucenzeo00)

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

Title:
  newusers error adding more than one user

Status in Ubuntu:
  Fix Committed
Status in Debian:
  New

Bug description:
  1)
  mcegielka@ftp-geodezja:~$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  2)
  mcegielka@ftp-geodezja:~$ sudo apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu6
Candidate: 1:4.1.5.1-1ubuntu6

  3)
  Expected: add system users from file given as argument:

  mcegielka@ftp-geodezja:~$ cat testusers.txt
  test1:a:::test user 1,,,:/home/test1:/bin/bash
  test2:b:::test user 2,,,:/home/test2:/bin/bash

  4)
  Instead: errors:

  mcegielka@ftp-geodezja:~$ sudo newusers testusers.txt
  *** Error in `newusers': free(): invalid next size (fast): 0x09319cd0 ***
  *** Error in `newusers': malloc(): memory corruption: 0x09319d00 ***

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: passwd 1:4.1.5.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Tue Jan  7 09:04:11 2014
  InstallationDate: Installed on 2014-01-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release i386 
(20131016)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760049] [NEW] [UIFe] Optional (hidden by default) communitheme snap session

[Didier Roche]

Public bug reported:

This session isn't displayed and available in GDM by default.

If the communitheme snap is installed, 2 new session options appears,
selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
cursor). All session/theme assets will be in the snap. We only expose
here default gsettings settings, session files and extension override.

There are 2 new strings for GDM:
* Ubuntu with communitheme snap
* Ubuntu with communitheme snap on Wayland


This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
This doesn't impact any default UI has nothing will appear before you install 
the snap.

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

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

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

[Touch-packages] [Bug 1760129] [NEW] Tiny mouse cursor on hidpi screens after logging in

[David Cesarino de Sousa]

Public bug reported:

=== System comments

Lenovo Yoga 910 with 13.9" UHD screen.
Bionic Beta 1. 
Using 200% scaling.

=== Problem description

Mouse cursor size alternates between tiny size and normal size depending
on where I hover the cursor, tiny on top and left bars, normal on
desktop and everywhere else.

Of course I expected size to stay normal wherever I positioned the
cursor.

=== How to fix the problem

1. Wait for some time or event to pass (have no idea how much/which); AND
2. Click the mouse.

=== Other comments

Must meet both conditions 1 and 2 above in order to fix the issue. That
is, cursor size behavior is restored only immediatelly after clicking,
but also only after the click has happened after event 1 (and I have no
idea what that may be) has passed.

I have noticed this before on 17.10 as well when I briefly tested it
last year, but since 1) there are other bug reports dealing with it; and
2) I only use LTS releases anyway, I never got time to test and report
it.

This happens on a fresh install of Bionic beta 1. Also today with all
updated applied.

=== Required stuff (not sure if it is xorg, if not just ask me and I'll
post what you need)

david@buzz:~$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

david@buzz:~$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu5
  Candidate: 1:7.7+19ubuntu5
  Version table:
 *** 1:7.7+19ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 30 11:10:19 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:3801]
InstallationDate: Installed on 2018-03-15 (15 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 003: ID 138a:0094 Validity Sensors, Inc. 
 Bus 001 Device 002: ID 5986:2104 Acer, Inc 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80VF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=0bf3fe9c-33ec-4653-b53e-adc64d7b62a0 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JCN39WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Agera
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 910-13IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
dmi.product.family: IDEAPAD
dmi.product.name: 80VF
dmi.product.version: Lenovo YOGA 910-13IKB
dmi.sys.vendor: LENOVO
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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic reproducible ubuntu

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

Title:
  Tiny mouse cursor on hidpi screens after logging in

Status in xorg package in Ubuntu:
  New

Bug description:
  === System comments

  Lenovo Yoga 910 with 13.9" UHD screen.
  Bionic Beta 1. 
  Using 200% scaling.

  === Problem description

  Mouse cursor size alternates between tiny size and normal size
  depending on where I hover the cursor, tiny on top and left bars,
  normal on desktop and everywhere else.

  Of course I expected size to stay normal wherever I positioned the
  cursor.

  === How to fix the problem

  1. Wait for some time or event to pass (have no idea how 

[Touch-packages] [Bug 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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

Status in avahi package in Ubuntu:
  New

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/1760128/+subscriptions

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

[Touch-packages] [Bug 1760128] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Rolf MetziRolf Metzingernger]

Public bug reported:

Ubuntu Update 30.03.18

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Mar 30 16:32:50 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-01-31 (788 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

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

Status in avahi package in Ubuntu:
  New

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/1760128/+subscriptions

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

[Touch-packages] [Bug 1760096] [NEW] /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-properties-gtk@101:__init__:init_livepatch:__init__:_load

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.96.24.24, the problem page at 
https://errors.ubuntu.com/problem/bc7b8c44b21fcb9ca4160c4e348a57b6c6c3d54b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress


** Tags: bionic

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

Title:
  /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-
  properties-gtk@101:__init__:init_livepatch:__init__:_load

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.96.24.24, the problem page at 
https://errors.ubuntu.com/problem/bc7b8c44b21fcb9ca4160c4e348a57b6c6c3d54b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1760117] [NEW] software-properties-gtk installs canonical-livepatch from edge

[Andrea Azzarone]

Public bug reported:

software-properties installs canonical-livepatch from edge. Switch to
stable before release.

** Affects: software-properties (Ubuntu)
 Importance: High
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

** Package changed: gnome-software (Ubuntu) => software-properties
(Ubuntu)

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

Title:
  software-properties-gtk installs canonical-livepatch from edge

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  software-properties installs canonical-livepatch from edge. Switch to
  stable before release.

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

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

[Touch-packages] [Bug 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/+junk/ubuntu-settings

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[siddesh kadam]

same problem i got black flickering screen on del 5558 , i have 920m
please suggest me which stable graphics driver can i use right now i am
unable to use tensorflow because of this , right now it is working on
nouveau drivers which has got set automatically by the sysytem , m
running linux ubuntu 64 bit .

** Attachment added: "this is the problem plaese twkl me which stable version , 
that i can install right now"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+attachment/5095870/+files/alternate_drivers

-- 
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 1760117] Re: software-properties-gtk installs canonical-livepatch from edge

[Launchpad Bug Tracker]

** Branch linked: lp:~azzar1/software-properties/livepatch-install-from-
stable

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

Title:
  software-properties-gtk installs canonical-livepatch from edge

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  software-properties installs canonical-livepatch from edge. Switch to
  stable before release.

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Jarno Suni]

Brian, I tested the update-manager version you told. It is true that
update-manager removes the unused packages, but step 3. (unattended-
upgrades) does not remove the unused kernels.

I add failed tag as this bug is originally about unattended-upgrades.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

 sudo apt-get install -y ca-certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]
   
  The unattended-upgrades fix is uploaded with many other fixes and those may 
cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760117] [NEW] software-properties-gtk installs canonical-livepatch from edge

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

software-properties installs canonical-livepatch from edge. Switch to
stable before release.

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: In Progress

-- 
software-properties-gtk installs canonical-livepatch from edge
https://bugs.launchpad.net/bugs/1760117
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties 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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Jarno Suni]

Testing is painfully slow because connection to e.g.
archive.canonical.com is very slow.

Downgrading in step 2 does not work without --allow-downgrades

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

 sudo apt-get install -y ca-certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]
   
  The unattended-upgrades fix is uploaded with many other fixes and those may 
cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760096] Re: /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-properties-gtk@101:__init__:init_livepatch:__init__:_load

[Launchpad Bug Tracker]

** Branch linked: lp:~azzar1/software-properties/depends-on-keyring

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

Title:
  /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-
  properties-gtk@101:__init__:init_livepatch:__init__:_load

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.96.24.24, the problem page at 
https://errors.ubuntu.com/problem/bc7b8c44b21fcb9ca4160c4e348a57b6c6c3d54b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1760096] Re: /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-properties-gtk@101:__init__:init_livepatch:__init__:_load

[Andrea Azzarone]

We need to add gnome-keyring as a dep in order to avoid the crash.

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-
  properties-gtk@101:__init__:init_livepatch:__init__:_load

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.96.24.24, the problem page at 
https://errors.ubuntu.com/problem/bc7b8c44b21fcb9ca4160c4e348a57b6c6c3d54b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

[Serge]

Unfortunately this is really a deal-breaker for me and forces me to drop
Nautilus and experiment with other, perhaps not so well
developed/maintained, GUI file managers. What a pity.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Mario Limonciello]

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

** Description changed:

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this attribute
  is important to be able to make hibernation work "out of the box".
  
  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9
  
  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.
+ 
+ Klibc support for adopting this change is available here:
+ https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

Title:
  Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

[Touch-packages] [Bug 1760132] [NEW] package systemd-sysv 237-3ubuntu6 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

[Sebastian Schlatow]

Public bug reported:

Ubuntu Bionic Beaver (development branch) 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu6
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
Date: Fri Mar 30 11:56:50 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2013-03-31 (1824 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu6 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-03-30 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package systemd-sysv 237-3ubuntu6 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu Bionic Beaver (development branch) 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu6
  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
  Date: Fri Mar 30 11:56:50 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-03-31 (1824 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 
(20130328)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu6 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-03-30 (0 days ago)

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

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

[Touch-packages] [Bug 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

[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 ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1760049

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

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

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

[Touch-packages] [Bug 1756446] Re: Include JournalErrors.txt

[Brian Murray]

Rather than having to futz about changing the number of lines of
JournalErrors collected in SRUs I've modified whoopsie to upload the
whole JournalErrors file however daisy will only write the last 50 lines
to the database.  By having this in daisy we can adjust the number of
lines as needed without having to SRU whoopsie multiple times.

** Also affects: daisy
   Importance: Undecided
   Status: New

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

Title:
  Include JournalErrors.txt

Status in Daisy:
  New
Status in whoopsie package in Ubuntu:
  Triaged
Status in whoopsie source package in Bionic:
  Triaged

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

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

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

[Touch-packages] [Bug 1756446] Re: Include JournalErrors.txt

[Francis Ginther]

** Tags added: id-5abd1582d291011d54313163

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

Title:
  Include JournalErrors.txt

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

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

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

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

[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Ubuntu Kernel Bot]

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

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

Title:
  Enable configuring resume offset via sysfs

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

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

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

[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Mario Limonciello]

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

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

Title:
  Enable configuring resume offset via sysfs

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

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

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

[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Mario Limonciello]

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

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

Title:
  Enable configuring resume offset via sysfs

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

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

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

[Touch-packages] [Bug 1760113] [NEW] System does not display video after waking up from sleep

[Daniel]

Public bug reported:

Hello,

I'm using the latest daily development snapshot iso of Ubuntu Bionic
Beaver.

My issue is that after issuing a sleep command with systemctl suspend
-i, the system cannot doesn't display any video or seems to work at all
when waking it up. It does detect the keypress of my keyboards, because
the fans will start spinning up and the HDD LED will flicker, confirming
that it did wake up, but I can't do anything with it. All I could do was
to shut off the computer entirely with my hardware button.

As this was my first bug report I'm willing to provide any more
debugging information, I just don't know how. I'm using a desktop
computer and I'm certain the motherboard supports this sleep state and
it worked fine in previous versions of several linux distros. I blamed
the error to xorg in particular because it seems to be waking up, it
just won't start up my screens.

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
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 30 15:47:01 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 950] [1458:36c5]
InstallationDate: Installed on 2018-03-30 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=cf158901-6c71-4345-89dd-371337d8426a ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88TD-V EVO/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic regression reproducible ubuntu

** Description changed:

  Hello,
  
  I'm using the latest daily development snapshot iso of Ubuntu Bionic
  Beaver.
  
  My issue is that after issuing a sleep command with systemctl suspend
  -i, the system cannot doesn't display any video or seems to work at all
  when waking it up. It does detect the keypress of my keyboards, because
  the fans will start spinning up and the HDD LED will flicker, confirming
  that it did wake up, but I can't do anything with it. All I could do was
  to shut off the computer entirely with my hardware button.
  
  As this was my first bug report I'm willing to provide any more
 

[Touch-packages] [Bug 1738581] Re: apport attachment JounralErrors should only be included for crash reports which are private

[Brian Murray]

** Summary changed:

- apport is leaking environment variables  (including passwords!) to public bug 
reports
+ apport attachment JounralErrors should only be included for crash reports 
which are private

** Description changed:

+ [Impact]
+ apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 
information.
+ 
+ [Test Case]
+ 1) Run ubuntu-bug apport
+ 2) Observe JournalErrors attachment in the .crash file
+ 
+ With the version of apport from -proposed JournalErrors will only be
+ included in crash reports not regular bug reports. So follow the same
+ test case and ensure JournalErrors is not included then run:
+ 
+ 1) d-feet
+ 2) pkill -11 d-feet
+ 3) Observe JournalErrors in the d-feet .crash file
+ 
+ [Regression Potential]
+ Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.
+ 
  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.
+ 
+ Original Description
+ 
  
  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org
  
- 
- Normally it would be not problem that gdm-x-session write this to the 
journal, because the journal is not intended to be published on the internet. 
+ Normally it would be not problem that gdm-x-session write this to the
+ journal, because the journal is not intended to be published on the
+ internet.
  
  Setting confidential informations via environment is maybe not the best
  idea, but a legal procedure and for `mpc` the only way to set this
  information.
  
  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.
  
- 
- Note: I manually delete the attachment in the mentioned bug report. But how 
can I sure that a web crawlser hasn't read/preserved that attachment?
+ Note: I manually delete the attachment in the mentioned bug report. But
+ how can I sure that a web crawlser hasn't read/preserved that
+ attachment?

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

Title:
  apport attachment JounralErrors should only be included for crash
  reports which are private

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Artful:
  Triaged

Bug description:
  [Impact]
  apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 
information.

  [Test Case]
  1) Run ubuntu-bug apport
  2) Observe JournalErrors attachment in the .crash file

  With the version of apport from -proposed JournalErrors will only be
  included in crash reports not regular bug reports. So follow the same
  test case and ensure JournalErrors is not included then run:

  1) d-feet
  2) pkill -11 d-feet
  3) Observe JournalErrors in the d-feet .crash file

  [Regression Potential]
  Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.

  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Original Description
  

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  Normally it would be not problem that gdm-x-session write this to the
  journal, because the journal is not intended to be published on the
  internet.

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  Note: I manually delete the attachment in the mentioned bug report.
  But how can I sure that a web crawlser hasn't read/preserved that
  attachment?

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

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

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

[Henrik Holmboe]

Perhaps a legit workaround: https://askubuntu.com/questions/980855/make-
nemo-produce-desktop-icons-gnome-3-26-1-on-ubuntu-17-10

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Touch-packages] [Bug 1760102] [NEW] Ubuntu 18.04: Please don't enable automatic suspend!

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

As already reported on
https://www.phoronix.com/scan.php?page=news_item=Ubuntu-18.04-Auto-
Suspend, automatic suspend is enabled on desktop installations on 18.04.
This is a very, very bad thing, because many installations are used as a
server. Even on a desktop usage this is a very problematic setting (long
downloads or calculations, demonstrations etc.) So, do NOT enable this
without asking the user!

To make things worse, it seems to be both a user specific and a system
wide setting.

But by far the biggest problem is that this shitty setting is even
enabled during an upgrade from 16.04 to 18.04 - without any warning! I
know, Ubuntu 18.04 is still in beta, but this is major problem which
will cause big headaches to many users which use their system as a
server. Luckily I have an IPMI as I have no physical access to this test
machine...

It seems that this happens only to Unity/Gnome, not on mate desktops,
but could be that this is caused by different desktop managers
(gdm/lightdm).

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


** Tags: dist-upgrade regression-release regression-update update
-- 
Ubuntu 18.04: Please don't enable automatic suspend!
https://bugs.launchpad.net/bugs/1760102
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta 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 1693609] Re: The "Minimize", " Maximize" and "Close" buttons are too small to click

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20180328-0ubuntu1

---
ubuntu-themes (16.10+18.04.20180328-0ubuntu1) bionic; urgency=medium

  * Ambiance, Radiance: use static bg imgs for window buttons and add
padding (LP: #1693609)
  * Ambiance, Radiance: don't use any background image (gradient) when
in backdrop
  * Ambiance, Radiance: add more specific selectors for scale states
(LP: #1759481)
  * Ambiance, Radiance: set top and bottom margins for switch and
separators in headerbar (LP: #1693474)

 -- Marco Trevisan (Treviño)   Wed, 28 Mar 2018 06:27:32
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  The "Minimize", " Maximize" and "Close" buttons are too small to click

Status in Ubuntu UX:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  The window control buttons ( _  X ) in Ambiance are noticeably
  smaller than other icon buttons in the headerbar of a "native" GNOME3
  app.

  I think this is both a visual issue and an accessibility issue since
  it is harder to click the window control buttons than the other
  buttons. Please compare with Adwaita which has a much larger click
  area for the window control buttons.

  Commentary
  --
  Remember that one of the major strengths of GNOME 3 is that it is usable on a 
touch-enabled laptop.

  And while there are many people that complain about Adwaita, I believe
  many more actually like the proportions and padding of the default
  GNOME theme!

  ubuntu-themes  16.10+17.10.20170518-0ubuntu1
  Ubuntu 17.10 Alpha

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

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

[Touch-packages] [Bug 1760178] [NEW] package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Prasad Challa]

Public bug reported:

Error invoking sudo command

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12.9
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Mar 22 08:59:13 2018
DhclientLeases:
 
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-02-09 (48 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=1fd42b9f-fe42-47e2-a9b7-f6a3a0a84af5 ro quiet splash vt.handoff=7
SourcePackage: isc-dhcp
Title: package isc-dhcp-client 4.3.3-5ubuntu12.9 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)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Error invoking sudo command

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.9
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 22 08:59:13 2018
  DhclientLeases:
   
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-02-09 (48 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=1fd42b9f-fe42-47e2-a9b7-f6a3a0a84af5 ro quiet splash vt.handoff=7
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12.9 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/isc-dhcp/+bug/1760178/+subscriptions

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

[Touch-packages] [Bug 1760178] Re: package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

[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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1760178

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Error invoking sudo command

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.9
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 22 08:59:13 2018
  DhclientLeases:
   
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-02-09 (48 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=1fd42b9f-fe42-47e2-a9b7-f6a3a0a84af5 ro quiet splash vt.handoff=7
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12.9 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/isc-dhcp/+bug/1760178/+subscriptions

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

[Touch-packages] [Bug 1693474] Re: Switches in Ambiance CSD headerbar are disproportionately big

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20180328-0ubuntu1

---
ubuntu-themes (16.10+18.04.20180328-0ubuntu1) bionic; urgency=medium

  * Ambiance, Radiance: use static bg imgs for window buttons and add
padding (LP: #1693609)
  * Ambiance, Radiance: don't use any background image (gradient) when
in backdrop
  * Ambiance, Radiance: add more specific selectors for scale states
(LP: #1759481)
  * Ambiance, Radiance: set top and bottom margins for switch and
separators in headerbar (LP: #1693474)

 -- Marco Trevisan (Treviño)   Wed, 28 Mar 2018 06:27:32
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Switches in Ambiance CSD headerbar are disproportionately big

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Look at the screenshot, is it expected for the switch in the top right
  corner to be so large?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 25 12:36:16 2017
  InstallationDate: Installed on 2017-04-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759481] Re: Horizontal single-child disabled scale isn't properly themed

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20180328-0ubuntu1

---
ubuntu-themes (16.10+18.04.20180328-0ubuntu1) bionic; urgency=medium

  * Ambiance, Radiance: use static bg imgs for window buttons and add
padding (LP: #1693609)
  * Ambiance, Radiance: don't use any background image (gradient) when
in backdrop
  * Ambiance, Radiance: add more specific selectors for scale states
(LP: #1759481)
  * Ambiance, Radiance: set top and bottom margins for switch and
separators in headerbar (LP: #1693474)

 -- Marco Trevisan (Treviño)   Wed, 28 Mar 2018 06:27:32
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Horizontal single-child disabled scale isn't properly themed

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  The last scale selector should be disabled in gtk3-widget-factory (cfr
  with Adwaita), but it's not:

  https://imgur.com/jLMa0Rd.png

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

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

[Touch-packages] [Bug 1756446] Re: Include JournalErrors.txt

[Launchpad Bug Tracker]

** Branch linked: lp:whoopsie

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

Title:
  Include JournalErrors.txt

Status in Daisy:
  New
Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

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

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

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Mark-pcnetspec]

No it's not that clicking the .deb doesn't fire up gdebi-gtk (it does),
it's that gdebi-gtk crashes whilst installing the .deb throwing the
error:-

dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

Changing (or dropping) the %f option makes no difference :(

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Jeremy Bicha]

Maybe this is related to the fix for LP: #1719746 and the reason why the
%f option was dropped in Ubuntu 17.10.

(I don't use gdebi and am not working on fixing this bug.)

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Mark-pcnetspec]

Yep, definitely something in vte 0.52 because downgrading to 0.48 by
installing these packages from artful:-

gir1.2-vte-2.91_0.48.4-0ubuntu1_amd64.deb
libvte-2.91-0_0.48.4-0ubuntu1_amd64.deb
libvte-2.91-0-udeb_0.48.4-0ubuntu1_amd64.udeb
libvte-2.91-common_0.48.4-0ubuntu1_all.deb

fixes the issue.

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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

[Touch-packages] [Bug 1756446] Re: Include JournalErrors.txt

[Brian Murray]

I've fixed this in daisy revision number 793 and submitted an RT
regrading updating staging.

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

Title:
  Include JournalErrors.txt

Status in Daisy:
  New
Status in whoopsie package in Ubuntu:
  Triaged
Status in whoopsie source package in Bionic:
  Triaged

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

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

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

[Touch-packages] [Bug 1738581] Re: apport attachment JounralErrors should only be included for crash reports which are private

[Brian Murray]

** Changed in: apport (Ubuntu Artful)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  apport attachment JounralErrors should only be included for crash
  reports which are private

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Artful:
  Triaged

Bug description:
  [Impact]
  apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 
information.

  [Test Case]
  1) Run ubuntu-bug apport
  2) Observe JournalErrors attachment in the .crash file

  With the version of apport from -proposed JournalErrors will only be
  included in crash reports not regular bug reports. So follow the same
  test case and ensure JournalErrors is not included then run:

  1) d-feet
  2) pkill -11 d-feet
  3) Observe JournalErrors in the d-feet .crash file

  [Regression Potential]
  Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.

  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Original Description
  

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  Normally it would be not problem that gdm-x-session write this to the
  journal, because the journal is not intended to be published on the
  internet.

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  Note: I manually delete the attachment in the mentioned bug report.
  But how can I sure that a web crawlser hasn't read/preserved that
  attachment?

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

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

[Touch-packages] [Bug 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session - 3.28.0-0ubuntu2

---
gnome-session (3.28.0-0ubuntu2) bionic; urgency=medium

  * Add new communitheme session to the ubuntu session package. This
session only appears if the communitheme snap is installed. (LP: #1760049)
- debian/patches/50_ubuntu_sessions.patch, debian/ubuntu-session.install:
  generate and install session file.
- add Recommends on gtk adwaita and pixbuf theme engine.
- debian/rules: enable communitheme to override the default ubuntu-dock
  stylesheet from the snap.
- debian/rules: workaround for Xorg to pick up communitheme cursor theme
  from the snap.
  * Refresh debian/patches/revert_remove_gnome_session_properties.patch

 -- Didier Roche   Fri, 30 Mar 2018 11:03:17 +0200

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

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

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

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

[Touch-packages] [Bug 1756446] Re: Include JournalErrors.txt

[Launchpad Bug Tracker]

This bug was fixed in the package whoopsie - 0.2.60

---
whoopsie (0.2.60) bionic; urgency=medium

  * Include JournalErrors in information uploaded to the Error Tracker.
(LP: #1756446)

 -- Brian Murray   Fri, 30 Mar 2018 08:32:35 -0700

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

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

Title:
  Include JournalErrors.txt

Status in Daisy:
  New
Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

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

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

[Touch-packages] [Bug 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 18.04

---
ubuntu-settings (18.04) bionic; urgency=medium

  * Add gsettings override for communitheme session (LP: #1760049)

 -- Didier Roche   Fri, 30 Mar 2018 17:29:10 +0200

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

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

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

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Jeremy Bicha]

One other person suggested that updating vte from 0.50 to 0.52 triggered this 
bug
LP: #1758918

I haven't investigated that either.

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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

[Touch-packages] [Bug 1759134] Re: software-properties-gtk (TypeError) detect_drivers → system_device_drivers → system_driver_packages → packages_for_modalias

[Brian Murray]

** Changed in: python-apt (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  software-properties-gtk (TypeError) detect_drivers →
  system_device_drivers → system_driver_packages → packages_for_modalias

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.96.24.24, the problem page at 
https://errors.ubuntu.com/problem/a98c6a0ffa437bac3d8c239431e0eedecffdbdfe 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1205, in detect_drivers
  self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 390, in 
system_device_drivers
  for pkg, pkginfo in system_driver_packages(apt_cache).items():
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 294, in 
system_driver_packages
  for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 145, in 
packages_for_modalias
  apt_cache_hash = hash(apt_cache)
  TypeError: unhashable type: 'Cache'

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

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

[Touch-packages] [Bug 1760117] Re: software-properties-gtk installs canonical-livepatch from edge

[Brian Murray]

** Also affects: software-properties (Ubuntu Bionic)
   Importance: High
 Assignee: Andrea Azzarone (azzar1)
   Status: In Progress

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

Title:
  software-properties-gtk installs canonical-livepatch from edge

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Bionic:
  In Progress

Bug description:
  software-properties installs canonical-livepatch from edge. Switch to
  stable before release.

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

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

[Touch-packages] [Bug 1760234] Re: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which i

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

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libfontconfig1-dev
  /fontconfig-devel.pdf.gz', which is different from other instances of
  package libfontconfig1-dev:i386

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I was installing dependencies to compile wine git.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-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-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 30 23:51:17 2018
  DuplicateSignature:
   package:libfontconfig1-dev:2.12.6-0ubuntu1
   Unpacking libfontconfig1-dev:i386 (2.12.6-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MaYTZY/067-libfontconfig1-dev_2.12.6-0ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180330)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760234] [NEW] package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which

[TuroLate]

Public bug reported:

I was installing dependencies to compile wine git.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfontconfig1-dev 2.12.6-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-0ubuntu2
Architecture: amd64
Date: Fri Mar 30 23:51:17 2018
DuplicateSignature:
 package:libfontconfig1-dev:2.12.6-0ubuntu1
 Unpacking libfontconfig1-dev:i386 (2.12.6-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-MaYTZY/067-libfontconfig1-dev_2.12.6-0ubuntu1_i386.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
InstallationDate: Installed on 2018-03-30 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180330)
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: fontconfig
Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libfontconfig1-dev
  /fontconfig-devel.pdf.gz', which is different from other instances of
  package libfontconfig1-dev:i386

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I was installing dependencies to compile wine git.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-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-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 30 23:51:17 2018
  DuplicateSignature:
   package:libfontconfig1-dev:2.12.6-0ubuntu1
   Unpacking libfontconfig1-dev:i386 (2.12.6-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MaYTZY/067-libfontconfig1-dev_2.12.6-0ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180330)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1760240] [NEW] Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

[Kirk Wolff]

Public bug reported:

In all repositories there is a buffer-overrun in the function
gtk_rc_add_default_file(), where if the dynamic array
gtk_rc_default_files has exactly max_default_files entries, a NULL will
be written past the allocated memory.  The resize function does not
resize the null terminated array in this case, and address sanitizer
(and valgrind) detects a memory access violation in any code leading to
this function.

The following code is in error ( from 
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596
 )
{{{
  for (n = 0; n < max_default_files; n++) 
{
  if (gtk_rc_default_files[n] == NULL)
break;
}

  if (n == max_default_files)
{
  max_default_files += 10;
  gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
}
  
  gtk_rc_default_files[n++] = g_strdup (filename);
  gtk_rc_default_files[n] = NULL;
}}}

Proposed modified implementation is as follows:
{{{
  for (n = 0; n < (max_default_files-1); n++) 
{
  if (gtk_rc_default_files[n] == NULL)
break;
}

  if (n >= (max_default_files-1))
{
  max_default_files += 10;
  gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
}
  
  gtk_rc_default_files[n++] = g_strdup (filename);
  gtk_rc_default_files[n] = NULL;
}}}

This implementation should be changed in all branches:

https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty/view/head:/gtk/gtkrc.c#L569
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-updates/view/head:/gtk/gtkrc.c#L569
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-proposed/view/head:/gtk/gtkrc.c#L569
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise/view/head:/gtk/gtkrc.c#L590
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-updates/view/head:/gtk/gtkrc.c#L596
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  In all repositories there is a buffer-overrun in the function
  gtk_rc_add_default_file(), where if the dynamic array
  gtk_rc_default_files has exactly max_default_files entries, a NULL
  will be written past the allocated memory.  The resize function does
  not resize the null terminated array in this case, and address
  sanitizer (and valgrind) detects a memory access violation in any code
  leading to this function.

  The following code is in error ( from 
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596
 )
  {{{
for (n = 0; n < max_default_files; n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n == max_default_files)
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  Proposed modified implementation is as follows:
  {{{
for (n = 0; n < (max_default_files-1); n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n >= (max_default_files-1))
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  This implementation should be changed in all branches:

  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-updates/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-proposed/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise/view/head:/gtk/gtkrc.c#L590
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-updates/view/head:/gtk/gtkrc.c#L596
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1760240/+subscriptions

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

[Touch-packages] [Bug 989961] Re: no gmake symlink created

[mcandre]

+1

Especially helpful for projects that wish to build for both GNU/Linux
and BSD, where "make" is an unreliable command, whereas calling "gmake"
guarantees the appropriate parser is executed.

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

Title:
  no gmake symlink created

Status in make-dfsg package in Ubuntu:
  Triaged

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

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

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

[Touch-packages] [Bug 1759921] Re: printing system doesn't work

[Carlos Rodriguez]

I've installed Debian 9.4.0 with Gnome desktop and CUPS print server to
test, and it works OK, so the problem is in Ubuntu.

Thank again.

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

Title:
  printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1303531] Re: Fix for misplaced tooltips (upper-left corner) - upstream pending patch

[Bug Watch Updater]

** Changed in: gtk
   Status: Confirmed => Invalid

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

Title:
  Fix for misplaced tooltips (upper-left corner) - upstream pending
  patch

Status in GTK+:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Hi,

  Any chance this:

  https://bugzilla.gnome.org/show_bug.cgi?id=698730#c4

  could make it in?

  Current Gtk+3.0 has had a bug since Saucy where gtk tooltips will
  briefly appear in the upper left corner before repositioning to their
  proper location.

  I will do the legwork if necessary (as a quilt patch)

  Thanks!

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

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

[Touch-packages] [Bug 1643901] Re: flxdec security update tracking bug

[Amr Ibrahim]

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  flxdec security update tracking bug

Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good0.10 source package in Precise:
  Fix Released
Status in gst-plugins-good0.10 source package in Trusty:
  Fix Released
Status in gst-plugins-good1.0 source package in Trusty:
  Fix Released
Status in gst-plugins-good0.10 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Yakkety:
  Fix Released
Status in gst-plugins-good1.0 source package in Zesty:
  Confirmed

Bug description:
  This bug is to track the security update to fix the flxdec out-of-
  bounds write.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1643901/+subscriptions

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

[Touch-packages] [Bug 1760190] Re: Useless icon themes

[dino99]

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

** This bug has been marked a duplicate of bug 1760201
   ubuntu 18.04 GDM - missing icons and letters

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

Title:
  Useless icon themes

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

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

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

[Touch-packages] [Bug 1760190] Re: Useless icon themes

[Ahmet Aksoy]

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

I think duplicate status is wrong. this bug not about gdm. its about
unused but installed icons themes

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

Title:
  Useless icon themes

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Lysenko Denis]

You may try this ppa https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa just updated driver from this rep on 18.04
and succesfully booted.

-- 
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 1760102] Re: Ubuntu 18.04: Please don't enable automatic suspend!

[Jeremy Bicha]

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

Yes, this only affects desktops that uses GNOME settings (Ubuntu, GNOME,
Unity, Budgie).

We will probably be changing the setting to only auto-suspend by default
when on battery power. That addresses most people's concerns while still
being useful to someone who accidentally left their laptop unplugged for
a while.

This is being tracked in LP: #1759008 so I'm marking this bug a
duplicate of that bug.

** This bug has been marked a duplicate of bug 1759008
   Revert automatic suspend by default for bionic?

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

Title:
  Ubuntu 18.04: Please don't enable automatic suspend!

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As already reported on
  https://www.phoronix.com/scan.php?page=news_item=Ubuntu-18.04-Auto-
  Suspend, automatic suspend is enabled on desktop installations on
  18.04. This is a very, very bad thing, because many installations are
  used as a server. Even on a desktop usage this is a very problematic
  setting (long downloads or calculations, demonstrations etc.) So, do
  NOT enable this without asking the user!

  To make things worse, it seems to be both a user specific and a system
  wide setting.

  But by far the biggest problem is that this shitty setting is even
  enabled during an upgrade from 16.04 to 18.04 - without any warning! I
  know, Ubuntu 18.04 is still in beta, but this is major problem which
  will cause big headaches to many users which use their system as a
  server. Luckily I have an IPMI as I have no physical access to this
  test machine...

  It seems that this happens only to Unity/Gnome, not on mate desktops,
  but could be that this is caused by different desktop managers
  (gdm/lightdm).

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

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

[Touch-packages] [Bug 1760102] Re: Ubuntu 18.04: Please don't enable automatic suspend!

[Steve Langasek]

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

** Tags removed: regression-update

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

Title:
  Ubuntu 18.04: Please don't enable automatic suspend!

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As already reported on
  https://www.phoronix.com/scan.php?page=news_item=Ubuntu-18.04-Auto-
  Suspend, automatic suspend is enabled on desktop installations on
  18.04. This is a very, very bad thing, because many installations are
  used as a server. Even on a desktop usage this is a very problematic
  setting (long downloads or calculations, demonstrations etc.) So, do
  NOT enable this without asking the user!

  To make things worse, it seems to be both a user specific and a system
  wide setting.

  But by far the biggest problem is that this shitty setting is even
  enabled during an upgrade from 16.04 to 18.04 - without any warning! I
  know, Ubuntu 18.04 is still in beta, but this is major problem which
  will cause big headaches to many users which use their system as a
  server. Luckily I have an IPMI as I have no physical access to this
  test machine...

  It seems that this happens only to Unity/Gnome, not on mate desktops,
  but could be that this is caused by different desktop managers
  (gdm/lightdm).

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

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

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Mark-pcnetspec]

I may have gone overboard with libvte-2.91-0-udeb which isn't a default
package so is unnecessary.

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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

[Touch-packages] [Bug 1760102] Re: Ubuntu 18.04: Please don't enable automatic suspend!

[Brian Murray]

** Package changed: update-manager (Ubuntu) => ubuntu-meta (Ubuntu)

** Tags added: rls-bb-incoming

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

Title:
  Ubuntu 18.04: Please don't enable automatic suspend!

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As already reported on
  https://www.phoronix.com/scan.php?page=news_item=Ubuntu-18.04-Auto-
  Suspend, automatic suspend is enabled on desktop installations on
  18.04. This is a very, very bad thing, because many installations are
  used as a server. Even on a desktop usage this is a very problematic
  setting (long downloads or calculations, demonstrations etc.) So, do
  NOT enable this without asking the user!

  To make things worse, it seems to be both a user specific and a system
  wide setting.

  But by far the biggest problem is that this shitty setting is even
  enabled during an upgrade from 16.04 to 18.04 - without any warning! I
  know, Ubuntu 18.04 is still in beta, but this is major problem which
  will cause big headaches to many users which use their system as a
  server. Luckily I have an IPMI as I have no physical access to this
  test machine...

  It seems that this happens only to Unity/Gnome, not on mate desktops,
  but could be that this is caused by different desktop managers
  (gdm/lightdm).

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

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

[Touch-packages] [Bug 1760187] [NEW] the sound is broken

[Oscar]

Public bug reported:

--2018-03-30 14:22:36--  http://www.alsa-project.org/alsa-info.sh
Resolviendo www.alsa-project.org (www.alsa-project.org)... 77.48.224.243
Conectando con www.alsa-project.org (www.alsa-project.org)[77.48.224.243]:80... 
conectado.
Petición HTTP enviada, esperando respuesta... 302 Found
Ubicación: 
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
 [siguiente]
--2018-03-30 14:22:39--  
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
Resolviendo git.alsa-project.org (git.alsa-project.org)... 77.48.224.243
Conectando con git.alsa-project.org (git.alsa-project.org)[77.48.224.243]:80... 
conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud: no especificado [application/x-sh]
Grabando a: “alsa-info.sh”

alsa-info.sh[   <=>  ]  28,03K  33,9KB/sin
0,8s

2018-03-30 14:22:41 (33,9 KB/s) - “alsa-info.sh” guardado [28707]

chmod: cambiando los permisos de './alsa-info.sh': Operación no
permitida

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

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

Title:
  the sound is broken

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  --2018-03-30 14:22:36--  http://www.alsa-project.org/alsa-info.sh
  Resolviendo www.alsa-project.org (www.alsa-project.org)... 77.48.224.243
  Conectando con www.alsa-project.org 
(www.alsa-project.org)[77.48.224.243]:80... conectado.
  Petición HTTP enviada, esperando respuesta... 302 Found
  Ubicación: 
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
 [siguiente]
  --2018-03-30 14:22:39--  
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
  Resolviendo git.alsa-project.org (git.alsa-project.org)... 77.48.224.243
  Conectando con git.alsa-project.org 
(git.alsa-project.org)[77.48.224.243]:80... conectado.
  Petición HTTP enviada, esperando respuesta... 200 OK
  Longitud: no especificado [application/x-sh]
  Grabando a: “alsa-info.sh”

  alsa-info.sh[   <=>  ]  28,03K  33,9KB/sin
  0,8s

  2018-03-30 14:22:41 (33,9 KB/s) - “alsa-info.sh” guardado [28707]

  chmod: cambiando los permisos de './alsa-info.sh': Operación no
  permitida

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

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

[Touch-packages] [Bug 1760190] [NEW] Useless icon themes

[Ahmet Aksoy]

Public bug reported:

Humanity-Dark
LoginIcons
Ubuntu-mono-dark
Ubuntu-mono-light
Hicolor

if i switch icons from these icons nothing happening.
I think these icons are no longer used in ubuntu.

And DMZ-Black, DMZ-White listing in icons

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1760190/+attachment/5096429/+files/Screenshot%20from%202018-03-30%2022-22-06.png

** Tags added: bionic

** Tags added: artful

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

Title:
  Useless icon themes

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

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

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

[Touch-packages] [Bug 1197395] Re: /run/user/$ID/pulse owned by root and not by the user

[Ccurtis0]

With the caveat that I haven't followed the entire thread, I had a
similar problem today on an older 14.04 release: the owner of
/run/user/$id/pulse would "spontaneously" become root. Comment #34 says
this is easily reproducible when running pkexec/synaptic. I believe I
can explain - broadly - what is happening by describing what I can
confirm.

First, here is one way to reproduce the problem:
*) PulseAudio (v4 in this case) starts as a normal user.
*) As root (via sudo su -), run 'aplay --list-devices'
*) /run/user/$id/pulse is now owned by root.

Tracing 'aplay' I can see that it is dlopen()ing a bunch of pulseaudio
support libraries. *Somehow* they (the pulseaudio support libraries, I
presume) determine that pusleaudio is running. They extract a cookie
from /root/.config/cookie and try to connect to the server via
/run/user/$id/pulse/native socket.

At this point, I don't know what the code is trying to do, but what it
_does_ do is this:

mkdir("/run/user/1000/pulse", 0700) = -1 EEXIST (File exists)
open("/run/user/1000/pulse", O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = 5
fchown(5, 0, 0) = 0
fchmod(5, 0700) = 0
[...]
getuid()= 0
socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC, 0) = 5
connect(5, {sa_family=AF_LOCAL, sun_path="/run/user/1000/pulse/native"}, 110) = 
-1 ENOENT (No such file or directory)
[...]

If my supposition is true that this is in the pulseaudio libraries, any
application running as root (like synaptic) is going to disable the
sound server when it tries to play audio through pulseaudio.

I scanned the pulseaudio changelogs and didn't see anything mentioning
this, but I can also confirm that Ubuntu 17.10 with pulseaudio version
10 and aplay version 1.1.3 does not do this. The older aplay version was
1.0.27.2.

In Ubuntu 17.10 pulseaudio is being run by 'gdm' but the same aplay
strace shows that it now looks for the socket in /var/run/pulse/native
instead of any particular UID in /run. It's unclear to me if the problem
is solved (in pulseaudio, if the culprit) or just band-aided by changing
the configuration (perhaps of ALSA integration with pulseaudio).

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

Title:
  /run/user/$ID/pulse owned by root and not by the user

Status in elementary OS:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Saucy:
  Invalid
Status in systemd source package in Saucy:
  Fix Released
Status in systemd package in Fedora:
  Won't Fix

Bug description:
  I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a 
media player (I use Musique), it freezes, as it finds that it cannot write into 
/run/user/$ID/pulse.
  If I change the owner of that directory to me, the media player starts as 
usual and is able to play music.
  I've never had this problem with previous versions of Ubuntu.
  Someone says that running PulseAudio with the -D argument changes the owner 
of that directory, but I didn't try.

  This is before manually changing the owner of that directory:
  $ musique
  Failed to create secure directory (/run/user/1000/pulse): Permission denied+

  ... # it doesn't crash, it keeps waiting

  If needed:
  (dmesg attached)
  lspci:
  00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
  00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 
(rev 03)
  00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 
(rev 03)
  00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 
(rev 03)
  00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 

[Touch-packages] [Bug 1760220] [NEW] ubuntu-bug with program path says as a snap does not belong to a package

[Brian Murray]

Public bug reported:

apport's ui.py file contains the following code:

 809 # executable?
 810 elif '/' in self.args[0]:
 811 pkg = apport.packaging.get_file_package(self.args[0])
 812 if not pkg:
 813 optparser.error('%s does not belong to a package.' % 
self.args[0])
 814 sys.exit(1)
 815 self.args = []
 816 self.options.filebug = True
 817 self.options.package = pkg

This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.

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


** Tags: bionic snaps

** Tags added: bionic snaps

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

Title:
  ubuntu-bug with program path says as a snap does not belong to a
  package

Status in apport package in Ubuntu:
  New

Bug description:
  apport's ui.py file contains the following code:

   809 # executable?
   810 elif '/' in self.args[0]:
   811 pkg = apport.packaging.get_file_package(self.args[0])
   812 if not pkg:
   813 optparser.error('%s does not belong to a package.' % 
self.args[0])
   814 sys.exit(1)
   815 self.args = []
   816 self.options.filebug = True
   817 self.options.package = pkg

  This will not provide any useful information about what to do if the
  'executable' is provided by a snap. Information similar to
  https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
  should be provided if the path is from a snap.

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

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

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Jeremy Bicha]

** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: vte2.91 (Ubuntu)
   Importance: Undecided => High

** Changed in: vte2.91 (Ubuntu)
   Status: New => Confirmed

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

[teo1978]

"not so well developed/maintained"? You mean worse than Nautilus??

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

[teo1978]

> Anyway I did, like yesterday, and it got closed
> (can't find it right now [...])

Here:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Touch-packages] [Bug 1649262] Re: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

[Simon Quigley]

Is this still a bug?

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

Status in Canonical System Image:
  Confirmed
Status in qtdeclarative-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  17.04 unity7

  ~$ webbrowser-app 
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
  UCUriHandler: Empty "APP_ID" environment variable, ignoring.
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information
  could not open containers config file  
"/home/pixel/.local/share/libertine/ContainersConfig.json"
  APP_ID isn't set, the handler can not be registered
  Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
  Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
  Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20)
  Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20)
  Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20)
  Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" 
QFlags(0x2)
  Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10)
  Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1)

  (webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not 
connect: Permission denied
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  APP_ID isn't set, the handler ignored
  qml: Loaded 13 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  ^CSegmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649262/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

[siddesh kadam]

i have tried the above link for Ubuntu 16.04 not working with nvidia
drivers (390) i have del 5558 and 920m graphics . (same flickering
screen ) , reverted back to nouveau drivers .

-- 
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 1759669] Re: Switch background uses gradients in backdrop mode

[Adolfo Jayme]

Fixed with ubuntu-themes 16.10+18.04.20180328-0ubuntu1

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Switch background uses gradients in backdrop mode

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  On non focused windows elements should have no gradients or colors, switch 
still uses it:
  https://i.imgur.com/uLQMLZu.png

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

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

[Touch-packages] [Bug 1435465] Re: Alt+F4 crashes app where WebView embedded in a Window

[Simon Quigley]

Seems like this is fixed now.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Alt+F4 crashes app where WebView embedded in a Window

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  was just watching something on Youtube Web App created by unity
  itself. when i pressed alt-f4 Ubuntu said it had an error and if i
  want to submit it.

  that is all folks.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webapp-container 0.23+15.04.20150320.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 19:56:16 2015
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2015-03-22 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  ProcCmdline: webapp-container --app-id=YouTubeyoutubecom 
--webapp=WW91VHViZQ== --enable-back-forward
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? ()
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
  Title: webapp-container crashed with SIGSEGV in QMetaObject::activate()
  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/qtbase-opensource-src/+bug/1435465/+subscriptions

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