[Touch-packages] [Bug 1787495] Re: no explanation for the events in the networkd-dispatcher manpage

[Julian Andres Klode]

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

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

Title:
  no explanation for the events in the networkd-dispatcher manpage

Status in networkd-dispatcher package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  networkd-dispatcher supports four hook directories:

  $ ls /usr/lib/networkd-dispatcher/
  dormant.d  no-carrier.d  off.d  routable.d
  $

  The manpage does not define what these hooks mean.  'routable' and
  'no-carrier' are self-explanatory, but it's not at all clear what
  'dormant' vs 'off' mean.  It's not at all clear what events one should
  expect to see as part of device bring-up.

  This needs to be better documented.

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

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[Mario Vukelic]

Michael, I am not Alex but I had the same on a completely fresh Cosmic
install from the Desktop image to a new latop (Asus ZenBook Flip
UX561UD). No special polkit/pam configs, after the install was finished
I ran an update and there it was

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[Mario Vukelic]

Unfortunately the machine is a friend's and not in my hands anymore, but
I can probably check next weekend if necessary

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[corrado venturini]

the ps output I addet to my bug
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791087 is from a
laptop install

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[Daniel van Vugt]

I think I've hit this with most/all cosmic desktop installs for the past
few months.

My uncertainty only comes from the fact that you won't hit the bug
until/unless the system needs to update snapd after that. So maybe a
good test is to start with a cosmic image that is older than the last
snapd update (2018-09-06). If you can't find such an image then install
the current cosmic image (2018-09-08) and wait till the next snapd
update in order to reproduce the bug.

Not sure if it's any different for automatic updates but I always
manually update:

  sudo apt update
  sudo apt full-upgrade

which is why the cause of the bug was immediately obvious to me.

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1786195] Re: broken audio/muffled, no system audio

[Dominic Anderson]

The bug was not gone when using kernel 4.4

there was also an additional kernel between 4.4 and 4.15 that was
available. I tried that as well. same result.no fix.

Since then I backed up my system and did a completely fresh install of
18.04LTS and the issue is still not fixed.

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

Title:
  broken audio/muffled, no system audio

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

Bug description:
  Ubuntu 18.04.1 LTS
  pulseaudio:
Installed: 1:11.1-1ubuntu7.1
Candidate: 1:11.1-1ubuntu7.1
Version table:
   *** 1:11.1-1ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  expected sound to return to normal/crisp throughout system and media 
applications.

  sound became muffled/distorted throughout all media applications,
  while other system sounds failed altogether. volume up/down failed.
  Chime on reboot also distorted. system and application sounds appear
  normal when used via bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  novgorod   1787 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  9 01:40:50 2018
  InstallationDate: Installed on 2018-08-01 (7 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB61.88Z.00CC.B00.1802021826
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22C8AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C8AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1786195] Re: broken audio/muffled, no system audio

[Dominic Anderson]

The bug was not gone when using kernel 4.4

there was also an additional kernel between 4.4 and 4.15 that was
available. I tried that as well. same result.no fix.

Since then I backed up my system and did a completely fresh install of
18.04LTS and the issue is still not fixed.

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

Title:
  broken audio/muffled, no system audio

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

Bug description:
  Ubuntu 18.04.1 LTS
  pulseaudio:
Installed: 1:11.1-1ubuntu7.1
Candidate: 1:11.1-1ubuntu7.1
Version table:
   *** 1:11.1-1ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  expected sound to return to normal/crisp throughout system and media 
applications.

  sound became muffled/distorted throughout all media applications,
  while other system sounds failed altogether. volume up/down failed.
  Chime on reboot also distorted. system and application sounds appear
  normal when used via bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  novgorod   1787 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  9 01:40:50 2018
  InstallationDate: Installed on 2018-08-01 (7 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB61.88Z.00CC.B00.1802021826
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22C8AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C8AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1786195] Re: broken audio/muffled, no system audio

[Daniel van Vugt]

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

** No longer affects: linux (Ubuntu)

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

Title:
  broken audio/muffled, no system audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.1 LTS
  pulseaudio:
Installed: 1:11.1-1ubuntu7.1
Candidate: 1:11.1-1ubuntu7.1
Version table:
   *** 1:11.1-1ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  expected sound to return to normal/crisp throughout system and media 
applications.

  sound became muffled/distorted throughout all media applications,
  while other system sounds failed altogether. volume up/down failed.
  Chime on reboot also distorted. system and application sounds appear
  normal when used via bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  novgorod   1787 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  9 01:40:50 2018
  InstallationDate: Installed on 2018-08-01 (7 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB61.88Z.00CC.B00.1802021826
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22C8AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C8AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1691678] Re: Overlay scrollbars escape the bottom of the Terminal window during resizing

[Daniel van Vugt]

** Tags added: cosmic

** Summary changed:

- Overlay scrollbars escape the bottom of the Terminal window during resizing
+ Scrollbars escape the bottom and right side of the Terminal window

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750889] Re: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1720651
   gnome-terminal: Extra pixel line to right of scrollbar with wayland sesssion
** This bug has been marked a duplicate of bug 1691678
   Scrollbars escape the bottom and right side of the Terminal window

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

Title:
  GNOME Terminal scrollbar looks weird on clean GNOME session under
  Wayland

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When using a clean GNOME session (with Adwaita theme) in combination
  with Wayland, the scrollbar in GNOME Terminal looks weird (see
  screenshot 1). The window also looks like it does not have a focus,
  but it does. Clicking anywhere on the menu bar fixes the focus issue,
  but the scrollbar still looks weird (see screenshot 2).

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

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

[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window

[Launchpad Bug Tracker]

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window

[Launchpad Bug Tracker]

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

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

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window

[Daniel van Vugt]

Still a problem in Ubuntu 18.10 cosmic.

** Tags added: bionic

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

[Daniel van Vugt]

** Summary changed:

- Scrollbars escape the bottom and right side of the Terminal window
+ Scrollbars escape the bottom and right side of the Terminal window by 1px

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[Michael Vogt]

We found the root cause now and work on a fix. sorry for the trouble -
Note that this is a "cosmic" specific issue. I'm exploring workarounds
now to unblock you.

** Changed in: snapd (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791220] Re: increased crash rate since 10.3 upgrade is available

[ Christian Ehrhardt ]

I tried backporting the upstream fix that came up in our discussion.
It fixes the crash back to how it was in Xenial (no segfault).
There still won't be much reason to run in non-VMWare envoronments, but this 
isn't what this was about.

It is working just fine.

Preparing a MP to review and a cosmic SRU template for Bionic later on
...

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

Title:
  increased crash rate since 10.3 upgrade is available

Status in VMWare tools:
  Unknown
Status in open-vm-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  Crash reports like:
  vmtoolsd (11) /usr/lib/libvmtools.so.0.0.0+2839c → [stack]+1ecfc → 
/usr/lib/libvmtools.so.0.0.0+4eb05 → 
/usr/lib/open-vm-tools/plugins/common/libhgfsServer.so+ccf → 
/usr/bin/vmtoolsd+5e98 → /usr/bin/vmtoolsd+4ce3 → /usr/bin/vmtoolsd+3ea8

  The cmdline of the failing process had:
  /usr/bin/vmtoolsd -n vmusr --blockFd 3

  I have a disassembly thou which looks like:

  => 0x7fedb35b739c :in (%dx),%eax
  0x7fedb35b739d :   xchg %rax,(%rsp)
  0x7fedb35b73a1 :   mov %rdi,0x28(%rax)
  0x7fedb35b73a5 :   mov %rsi,0x20(%rax)
  0x7fedb35b73a9 :   mov %rdx,0x18(%rax)
  0x7fedb35b73ad :   mov %rcx,0x10(%rax)
  0x7fedb35b73b1 :   mov %rbx,0x8(%rax)
  0x7fedb35b73b5 :   popq (%rax)
  0x7fedb35b73b7 :   pop %rbx
  0x7fedb35b73b8 :   retq 
  0x7fedb35b73b9:   nopl 0x0(%rax)
  0x7fedb35b73c0 :push %rbx
  0x7fedb35b73c1 :  mov %rdi,%rax
  0x7fedb35b73c4 :  push %rbp
  0x7fedb35b73c5 :  push %rax
  0x7fedb35b73c6 :  mov 0x30(%rax),%rbp

  We don't have much more yet.
  I filed an issue upstream [2] last week in case this showed up somewhere else 
as well, but haven't seen any response yet.

  Crash reports overview (might need ubuntu signin) are at [3] and one
  example is [4]

  [1]: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1784638
  [2]: https://github.com/vmware/open-vm-tools/issues/284
  [3]: 
https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=open-vm-tools&period=week&version=2%3A10.3.0-0ubuntu1~18.04.1
  [4]: 
https://errors.ubuntu.com/problem/bff98ff07d389a1a92b6cd538a823c1e2ce1a193

To manage notifications about this bug go to:
https://bugs.launchpad.net/open-vm-tools/+bug/1791220/+subscriptions

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[Daniel van Vugt]

Bug 1781513 is on bionic, so that's not the same issue as this?

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791220] Re: increased crash rate since 10.3 upgrade is available

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/354555

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

Title:
  increased crash rate since 10.3 upgrade is available

Status in VMWare tools:
  Unknown
Status in open-vm-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * The new version of open-vm-tools we recently SRUed had an issue
 that if started in non-VMWare environments (protected by systemd 
 condition-virtualization, but people fake VMware envs) would segfault.

   * It is fine to "not work there" but segfaulting is too hard

   * Upstream realized the issue, this is backporting the fix

  [Test Case]

   * Use a non-VMWare guest (e.g. a test system lxd container) and run
  $ vmtoolsd

   * This will segfault, with the fix it will have a clean exit.

  [Regression Potential]

   * All of this only affects non-VMWare environments in a tool only needed 
 in those environments - so the risk should be low. It is closing a 
 corner case of faked environments to keep bug reports and crashes down.
 I can think of a regression if the detection of the VMContext would be 
 wrong and therefore the service not properly initializing anymore in 
 systems it should do so - so far such an issue was not seen, btu that 
 would be the most likely potential regression.

  [Other Info]
   
   * n/a

  
  ---

  Hi,

  Crash reports like:
  vmtoolsd (11) /usr/lib/libvmtools.so.0.0.0+2839c → [stack]+1ecfc → 
/usr/lib/libvmtools.so.0.0.0+4eb05 → 
/usr/lib/open-vm-tools/plugins/common/libhgfsServer.so+ccf → 
/usr/bin/vmtoolsd+5e98 → /usr/bin/vmtoolsd+4ce3 → /usr/bin/vmtoolsd+3ea8

  The cmdline of the failing process had:
  /usr/bin/vmtoolsd -n vmusr --blockFd 3

  I have a disassembly thou which looks like:

  => 0x7fedb35b739c :in (%dx),%eax
  0x7fedb35b739d :   xchg %rax,(%rsp)
  0x7fedb35b73a1 :   mov %rdi,0x28(%rax)
  0x7fedb35b73a5 :   mov %rsi,0x20(%rax)
  0x7fedb35b73a9 :   mov %rdx,0x18(%rax)
  0x7fedb35b73ad :   mov %rcx,0x10(%rax)
  0x7fedb35b73b1 :   mov %rbx,0x8(%rax)
  0x7fedb35b73b5 :   popq (%rax)
  0x7fedb35b73b7 :   pop %rbx
  0x7fedb35b73b8 :   retq
  0x7fedb35b73b9:   nopl 0x0(%rax)
  0x7fedb35b73c0 :push %rbx
  0x7fedb35b73c1 :  mov %rdi,%rax
  0x7fedb35b73c4 :  push %rbp
  0x7fedb35b73c5 :  push %rax
  0x7fedb35b73c6 :  mov 0x30(%rax),%rbp

  We don't have much more yet.
  I filed an issue upstream [2] last week in case this showed up somewhere else 
as well, but haven't seen any response yet.

  Crash reports overview (might need ubuntu signin) are at [3] and one
  example is [4]

  [1]: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1784638
  [2]: https://github.com/vmware/open-vm-tools/issues/284
  [3]: 
https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=open-vm-tools&period=week&version=2%3A10.3.0-0ubuntu1~18.04.1
  [4]: 
https://errors.ubuntu.com/problem/bff98ff07d389a1a92b6cd538a823c1e2ce1a193

To manage notifications about this bug go to:
https://bugs.launchpad.net/open-vm-tools/+bug/1791220/+subscriptions

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

[Touch-packages] [Bug 1791220] Re: increased crash rate since 10.3 upgrade is available

[ Christian Ehrhardt ]

** Description changed:

+ [Impact]
+ 
+  * The new version of open-vm-tools we recently SRUed had an issue
+that if started in non-VMWare environments (protected by systemd 
+condition-virtualization, but people fake VMware envs) would segfault.
+ 
+  * It is fine to "not work there" but segfaulting is too hard
+ 
+  * Upstream realized the issue, this is backporting the fix
+ 
+ [Test Case]
+ 
+  * Use a non-VMWare guest (e.g. a test system lxd container) and run
+ $ vmtoolsd
+ 
+  * This will segfault, with the fix it will have a clean exit.
+ 
+ [Regression Potential]
+ 
+  * All of this only affects non-VMWare environments in a tool only needed 
+in those environments - so the risk should be low. It is closing a 
+corner case of faked environments to keep bug reports and crashes down.
+I can think of a regression if the detection of the VMContext would be 
+wrong and therefore the service not properly initializing anymore in 
+systems it should do so - so far such an issue was not seen, btu that 
+would be the most likely potential regression.
+ 
+ [Other Info]
+  
+  * n/a
+ 
+ 
+ ---
+ 
  Hi,
  
  Crash reports like:
  vmtoolsd (11) /usr/lib/libvmtools.so.0.0.0+2839c → [stack]+1ecfc → 
/usr/lib/libvmtools.so.0.0.0+4eb05 → 
/usr/lib/open-vm-tools/plugins/common/libhgfsServer.so+ccf → 
/usr/bin/vmtoolsd+5e98 → /usr/bin/vmtoolsd+4ce3 → /usr/bin/vmtoolsd+3ea8
  
  The cmdline of the failing process had:
  /usr/bin/vmtoolsd -n vmusr --blockFd 3
  
  I have a disassembly thou which looks like:
  
  => 0x7fedb35b739c :in (%dx),%eax
  0x7fedb35b739d :   xchg %rax,(%rsp)
  0x7fedb35b73a1 :   mov %rdi,0x28(%rax)
  0x7fedb35b73a5 :   mov %rsi,0x20(%rax)
  0x7fedb35b73a9 :   mov %rdx,0x18(%rax)
  0x7fedb35b73ad :   mov %rcx,0x10(%rax)
  0x7fedb35b73b1 :   mov %rbx,0x8(%rax)
  0x7fedb35b73b5 :   popq (%rax)
  0x7fedb35b73b7 :   pop %rbx
- 0x7fedb35b73b8 :   retq 
+ 0x7fedb35b73b8 :   retq
  0x7fedb35b73b9:   nopl 0x0(%rax)
  0x7fedb35b73c0 :push %rbx
  0x7fedb35b73c1 :  mov %rdi,%rax
  0x7fedb35b73c4 :  push %rbp
  0x7fedb35b73c5 :  push %rax
  0x7fedb35b73c6 :  mov 0x30(%rax),%rbp
  
  We don't have much more yet.
  I filed an issue upstream [2] last week in case this showed up somewhere else 
as well, but haven't seen any response yet.
  
  Crash reports overview (might need ubuntu signin) are at [3] and one
  example is [4]
  
  [1]: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1784638
  [2]: https://github.com/vmware/open-vm-tools/issues/284
  [3]: 
https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=open-vm-tools&period=week&version=2%3A10.3.0-0ubuntu1~18.04.1
  [4]: 
https://errors.ubuntu.com/problem/bff98ff07d389a1a92b6cd538a823c1e2ce1a193

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

Title:
  increased crash rate since 10.3 upgrade is available

Status in VMWare tools:
  Unknown
Status in open-vm-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * The new version of open-vm-tools we recently SRUed had an issue
 that if started in non-VMWare environments (protected by systemd 
 condition-virtualization, but people fake VMware envs) would segfault.

   * It is fine to "not work there" but segfaulting is too hard

   * Upstream realized the issue, this is backporting the fix

  [Test Case]

   * Use a non-VMWare guest (e.g. a test system lxd container) and run
  $ vmtoolsd

   * This will segfault, with the fix it will have a clean exit.

  [Regression Potential]

   * All of this only affects non-VMWare environments in a tool only needed 
 in those environments - so the risk should be low. It is closing a 
 corner case of faked environments to keep bug reports and crashes down.
 I can think of a regression if the detection of the VMContext would be 
 wrong and therefore the service not properly initializing anymore in 
 systems it should do so - so far such an issue was not seen, btu that 
 would be the most likely potential regression.

  [Other Info]
   
   * n/a

  
  ---

  Hi,

  Crash reports like:
  vmtoolsd (11) /usr/lib/libvmtools.so.0.0.0+2839c → [stack]+1ecfc → 
/usr/lib/libvmtools.so.0.0.0+4eb05 → 
/usr/lib/open-vm-tools/plugins/common/libhgfsServer.so+ccf → 
/usr/bin/vmtoolsd+5e98 → /usr/bin/vmtoolsd+4ce3 → /usr/bin/vmtoolsd+3ea8

  The cmdline of the failing process had:
  /usr/bin/vmtoolsd -n vmusr --blockFd 3

  I have a disassembly thou which looks like:

  => 0x7fedb35b739c :in (%dx),%eax
  0x7fedb35b739d :   xchg %rax,(%rsp)
  0x7fedb35b73a1 :   mov %rdi,0x28(%rax)
  0x7fedb35b73a5 :   mov %rsi,0x20(%rax)
  0x7fedb35b73a9 :   mov %rdx,0x18(%rax)
  0x7fedb35b73ad :   mov %rcx,0x10(%rax)
  0x7fedb35b73b1 :   mov %rbx,0x8(%rax)
  0x7fedb35b73b5 :   popq (%rax)
  0x7f

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

[bugproxy]

--- Comment From abhir...@in.ibm.com 2018-09-10 05:16 EDT---
Vorlon,

In the detailed steps , the commands have been simplified.
Let me put simple use case for ease to avoid confusion.

1)Create bond using nmcli utility with below attributes set:
one slave (eth0) , mode = active_backup ,  ipv4 is assigned to bond say 
30.1.2.100/24

2)Create VLAN on top of bond created in above step 1. ipv4 is assigned
to vlan say 30.1.3.100/24

3)Ping operation under test works for 30.1.2.1 and 30.1.3.1

4)Deactivate bond. Vlan also gets deactivated. Both 30.1.2.1 and 30.1.3.1 are 
not reachable.
Because ip routes no more exists on deactivation of bond. #This is expected as 
per my understanding

5)Activate bond. VLAN DOES NOT GET ACTIVATED AUTOMATICALLY. Only 30.1.2.1 is 
reachable.
Route for VLAN is not created. #This was working in combination with nmcli + 
other distros automatically, and as a end user need not do any operation with 
respect to VLAN.

6)For nmcli + Ubuntu, we are forced to Manually Activate VLAN, route is
then created for VLAN. 30.1.3.1 is now reachable.

Above steps can be repeated
1)Without assiging ip to bond as well
2)For some reasons if we want to add a new slave or delete a slave from bond OR 
change any attributes of bond say primary, primary_reselect etc, bond is 
deactivated, attributes of bond are modified and activated. In this process 
VLAN gets deactivated autmatically but not gets auto - activated resulting in 
loss of traffic

So either i suspect one of the two issues here
1)nmcli was internally handling this in case of other distros. i.e deactivated 
the vlan, when bond is deactivated and activate the vlan , when bond is 
activated.
OR
2)network kernel underlying module takes care of these notifications between 
bond and vlan. I suspected this because, as i did not see any log updates with 
respect to nmcli tool for automatically deactivating and activating VLAN

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

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond

[Touch-packages] [Bug 1791301] Re: Update to 2.38.0

[Iain Lane]

This bug was fixed in the package gdk-pixbuf - 2.38.0+dfsg-4

---
gdk-pixbuf (2.38.0+dfsg-4) unstable; urgency=medium

  [ Jeremy Bicha ]
  * Update debian/gbp.conf
  * debian/libgdk-pixbuf2.0-0.install: Use ${DEB_HOST_MULTIARCH} less.
Thanks lintian.

  [ John Paul Adrian Glaubitz ]
  * debian/rules: Have dh_auto_test override honor nocheck (Closes: #908373)

  [ Chris Lamb ]
  * Add Use-basename-instead-of-filename.patch:
- Proposed patch for reproducible builds and multi-arch co-installability
  (Closes: #908309)

 -- Jeremy Bicha   Sun, 09 Sep 2018 08:12:01 -0400

gdk-pixbuf (2.38.0+dfsg-3) unstable; urgency=medium

  [ Sven Joachim ]
  * Fix FTBFS on any-i386 (Closes: #908298)

 -- Andreas Henriksson   Sat, 08 Sep 2018 10:54:08
+0200

gdk-pixbuf (2.38.0+dfsg-2) unstable; urgency=medium

  * Allow 5× as much time for the tests, to hopefully allow gdk-pixbuf to pass
tests on all of our slower arches.

 -- Iain Lane   Fri, 07 Sep 2018 17:43:33 +0100

gdk-pixbuf (2.38.0+dfsg-1) unstable; urgency=medium

  * New upstream release (LP: #1791301)
- Add test case for buffer overflow in pixdata loader
- Avoid a deprecation warning with recent libjasper
- Deprecate GDK_INTERP_HYPER
- Drop Autotools build and move to Meson
- Drop the MMX assembly optimizations for pixops
- Ensure that GdkPixbuf's storage is safely handled
- Expose the dimensions of the original image from GdkPixbufLoader
- Fix documentation building with X11 disabled
- Fix introspection annotations
- Fix OOB error when dithering
- Generate separate introspection data for GdkPixdata API
- Improve compatibility for the post-install script
- Improve thumbnailer implementation
- Make X11 a dependency if the `x11` build option is enabled
- Plug a memory leak when using GBytes
- Properly install test data
  * debian/copyright: Exclude tests/bug753605-atsize.jpg, which is non-free.
This was added for a testcase, but we can't distribute it. The testcase
itself is disabled in debian/patches/Remove-test-for-GNOME-753605.patch
already.
  * Remove-test-for-GNOME-753605.patch:
+ Remove "wasn't included in the tarball" It now is in the tarball, but we
+ Don't try to install bug753605-atsize.jpg
are repacking to exclude it.
  * Build with meson.
  * Don't build the installed tests for this upload. It'd require a trip
through binNEW
  * docs: Drop AUTHORS, rename README to README.md
  * libgdk-pixbuf2.0-0.symbols: Drop two private symbols. These are in a
private header and weren't meant to be exported. codesearch.d.n shows no
external users.
  * Bump Standards-Version to 4.2.1 (no changes required)
  * Add Lintian overrides for warnings about GdkPixdata introspection data.
It's intentional that this is in gir1.2-gdkpixbuf-2.0

 -- Iain Lane   Fri, 07 Sep 2018 14:45:00 +0100

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update to 2.38.0

Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  that's the badger 🦡

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

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[corrado venturini]

workaround is easy: modify /var/lib/snapd/seed/seed.yaml and restart snapd
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1785388

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762314] Re: Sound output too low

[Pierre-Alexis Ciavaldini]

Same issue here on T570 running Manjaro, this is the only bug report talking 
about the problem which seems not related to Ubuntu but to alsa. All sliders 
are up in alsamixer, sound is around half-volume compared to the Windows 
install. ALSA Driver Version: k4.14.67-1-MANJARO.
these did not help: 
https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Volume_is_too_low

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

Title:
  Sound output too low

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound output on lenovo p51s is too low. No option to go above 100% in volume 
settings. Download pulse audio volume control to raise application and output 
volume to 153%, which helps to some extent, but then leads to distortion. 
  Was running windows 10 on same system and audio was loud enough!
  Also after this morning
  s update, the volume keys no longer work, even after re-mapping them in 
shortcuts.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jatin  2098 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  8 22:50:04 2018
  InstallationDate: Installed on 2018-03-23 (17 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or 
low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET36W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HCS06601
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51s
  dmi.product.name: 20HCS06601
  dmi.product.version: ThinkPad P51s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1791484] Re: [FFe] Update tracker and tracker-miners to 2.1.4

[Łukasz Zemczak]

Hello! This should be fine since as you said, these are not installed by
default - but since they're in 'supported', let's make sure these aren't
broken. Could you provide some test-build logs on Ubuntu cosmic (either
local of on a PPA)? Did you tests these packages on a cosmic system
already (I assume yes?). Thanks!

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

Title:
  [FFe] Update tracker and tracker-miners to 2.1.4

Status in tracker package in Ubuntu:
  New

Bug description:
  To go along with the rest of GNOME 3.30
  Both tracker and tracker-miners 2.1.4 will be synced from Debian. 

  tracker is not installed by default on any Ubuntu Flavours, but does
  provide an important part of the GNOME-Shell experience.

  These releases bring lots of fixes and a few new features.

  Tracker NEW in 2.1.4 - 2018-09-04
  =

* Fix build with format-security flag

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Fix resource refcounting issues in database. Reset is advised.
* Drop cardinality from nie:copyright, nie:license, nie:legal and dc:rights
* Fix superfluous ontology checks on second tracker-store run
* Use more SPARQL1.1 correct syntax.
* Allow use of domain rules outside prefix
* Compatibility fixes with C++

  Translations: gl, id, ko

  NEW in 2.1.2 - 2018-08-15
  =

* libtracker-sparql: Delete TrackerResource elements one by one
* libtracker-sparql: Fix compilation with C++
* build: Fixes for FreeBSD
* build: Fixes on meson

  Translations: cs, el, fr, fur, hu, sl, tr, zh_TW

  NEW in 2.1.1 - 2018-08-01
  =

* libtracker-direct: Plug leaks
* libtracker-sparql-backend: Fix fallback from direct to bus
  connection for queries.

  Translations: es, lt, ro

  NEW in 2.1.0 - 2018-07.22
  =

* Brown paper bag release
* All features from unreleased 2.0.5 apply
* One feature was missed: TrackerResource is now able to output
  JSON-LD. This is a new API call, so a minor bump should happen
  as per Semantic Versioning.

From 2.0.5 NEWS:
* build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
* build: Various meson build fixes
* tests: Many fixes to functional tests
* libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
* libtracker-direct: Majorly rewritten
* tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  Tracker-miners NEW in 2.1.4 - 2018-09-04
  =

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Unbreak watch on domain ontology owner. Fixes miners spuriously
  exiting.

  NEW in 2.1.2 - 2018-08-30
  =

* Allow use of domain rules outside prefix
* Add core-as-subproject as explicit meson option
* Ensure utf8ness in TrackerResource helpers
* Fix multiple cardinality issues in different extractors/properties
* Other minor SPARQL correctness fixes

  Translations: gl, id, ko

  NEW in 2.1.1 - 2018-08-15
  =

* tracker-miner-fs: Ignore mercurial repositories
* build: Fix build with -Werror=format-security
* tracker-extract: Ensure metadata strings are UTF-8 in JPEG/PNG extractors
* tracker-extract: Do not add named destinations to PDF TOCs
* tracker-extract: Ignore XMP image metadata on PDFs
* tracker-extract: Fix ISO 8601 date string generation on gstreamer 
extractor

  Translations: cs, el, fr, fur, hu, lt, sl, tr, zh_TW

  NEW in 2.1.0 - 2018-07-23
  =

* tests: Many updates and fixes to functional tests
* tracker-extract: Better infrastructure for tests, based on JSON-LD
* tracker-miner-fs: Restart tracker extract from the right domain
* tracker-extract: Persistently avoid files that trigger recoverable
  errors, to avoid log spamming on restarts.

  Translations: de, es, it, pl, pt_BR, ro, sv

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

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

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[Mario Vukelic]

Note that according to Oliver in the above linked bug #1785388 this is
currently intentional in Cosmic

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791484] Re: [FFe] Update tracker and tracker-miners to 2.1.4

[Tim Lunn]

Yes have been testing on cosmic.

they are both on gnome3-team/gnome3-staging ppa. Tracker is at 2.1.3
there, but has already my patch that was the only change in 2.1.4.

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+sourcepub/9389719/+listing-archive-extra
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+sourcepub/9389722/+listing-archive-extra

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

Title:
  [FFe] Update tracker and tracker-miners to 2.1.4

Status in tracker package in Ubuntu:
  New

Bug description:
  To go along with the rest of GNOME 3.30
  Both tracker and tracker-miners 2.1.4 will be synced from Debian. 

  tracker is not installed by default on any Ubuntu Flavours, but does
  provide an important part of the GNOME-Shell experience.

  These releases bring lots of fixes and a few new features.

  Tracker NEW in 2.1.4 - 2018-09-04
  =

* Fix build with format-security flag

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Fix resource refcounting issues in database. Reset is advised.
* Drop cardinality from nie:copyright, nie:license, nie:legal and dc:rights
* Fix superfluous ontology checks on second tracker-store run
* Use more SPARQL1.1 correct syntax.
* Allow use of domain rules outside prefix
* Compatibility fixes with C++

  Translations: gl, id, ko

  NEW in 2.1.2 - 2018-08-15
  =

* libtracker-sparql: Delete TrackerResource elements one by one
* libtracker-sparql: Fix compilation with C++
* build: Fixes for FreeBSD
* build: Fixes on meson

  Translations: cs, el, fr, fur, hu, sl, tr, zh_TW

  NEW in 2.1.1 - 2018-08-01
  =

* libtracker-direct: Plug leaks
* libtracker-sparql-backend: Fix fallback from direct to bus
  connection for queries.

  Translations: es, lt, ro

  NEW in 2.1.0 - 2018-07.22
  =

* Brown paper bag release
* All features from unreleased 2.0.5 apply
* One feature was missed: TrackerResource is now able to output
  JSON-LD. This is a new API call, so a minor bump should happen
  as per Semantic Versioning.

From 2.0.5 NEWS:
* build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
* build: Various meson build fixes
* tests: Many fixes to functional tests
* libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
* libtracker-direct: Majorly rewritten
* tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  Tracker-miners NEW in 2.1.4 - 2018-09-04
  =

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Unbreak watch on domain ontology owner. Fixes miners spuriously
  exiting.

  NEW in 2.1.2 - 2018-08-30
  =

* Allow use of domain rules outside prefix
* Add core-as-subproject as explicit meson option
* Ensure utf8ness in TrackerResource helpers
* Fix multiple cardinality issues in different extractors/properties
* Other minor SPARQL correctness fixes

  Translations: gl, id, ko

  NEW in 2.1.1 - 2018-08-15
  =

* tracker-miner-fs: Ignore mercurial repositories
* build: Fix build with -Werror=format-security
* tracker-extract: Ensure metadata strings are UTF-8 in JPEG/PNG extractors
* tracker-extract: Do not add named destinations to PDF TOCs
* tracker-extract: Ignore XMP image metadata on PDFs
* tracker-extract: Fix ISO 8601 date string generation on gstreamer 
extractor

  Translations: cs, el, fr, fur, hu, lt, sl, tr, zh_TW

  NEW in 2.1.0 - 2018-07-23
  =

* tests: Many updates and fixes to functional tests
* tracker-extract: Better infrastructure for tests, based on JSON-LD
* tracker-miner-fs: Restart tracker extract from the right domain
* tracker-extract: Persistently avoid files that trigger recoverable
  errors, to avoid log spamming on restarts.

  Translations: de, es, it, pl, pt_BR, ro, sv

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

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

[Touch-packages] [Bug 1789472] Re: SRU 2.56.2 to bionic

[Łukasz Zemczak]

Yeah, I confirmed that the glib2.0 armhf network-monitor-race test also
fails on release. udisks2 is broken and I hinted it in. Others passed
after some retried. Thanks for looking into that! Releasing!

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

Title:
  SRU 2.56.2 to bionic

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  The second stable release in the 2.56 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Various fixes in multiple places (see
  https://gitlab.gnome.org/GNOME/glib/blob/d4b603/NEWS) so various apps
  could be affected.

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

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

[Touch-packages] [Bug 1764779] Re: Nautilus crashed open Windows-partition [assertion failed: (location != NULL)]

[Launchpad Bug Tracker]

This bug was fixed in the package glib2.0 - 2.56.2-0ubuntu0.18.04.1

---
glib2.0 (2.56.2-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1789472, LP: #1764779)
  * Refreshed patches
  * d/p/tests-network-monitor-Always-use-the-dummy-proxy-res.patch:
- Removed (aplied upstream)

 -- Marco Trevisan (Treviño)   Tue, 28 Aug 2018
13:25:36 -0500

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Nautilus crashed open Windows-partition [assertion failed: (location
  != NULL)]

Status in glib2.0 package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  if I open a new partition from the Hard-drive (Windows in this case)
  Nautilus crash, report him self and after reopen it, the partition is
  normal available as nothing would be

  https://errors.ubuntu.com/problem/f49deb51a98d691e3e040d7f7334ad08d1e0e54c
  https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938
  https://errors.ubuntu.com/problem/00db9958203affb0a98a2842bb2bd91547e6bd5a
  https://errors.ubuntu.com/problem/818d3ad2d9fe9f9f64f32fcb5f10da4126d3827d

  [ Test case ]

  * Open nautilus and select an external hd that is not mounted from the sidebar
  * Nautilus sould not crash (in case showing an error message)

  [ Regression potential ]

  Partitions that have been actually mounted, are not shown or an error
  is prompted.

  -

  Issue from the log:

  Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount 
point cleanup: Process reported exit code 5: Failed to start 
clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit 
media-username-12F6CC77F6CC5D1B.mount not found.
  Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: 
assertion 'G_IS_MOUNT (mount)' failed
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: **
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: 
ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: 
(location != NULL)

  -

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 16:45:30 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' 
b'show-move-to-trash-shortcut-changed-dialog' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'"
  InstallationDate: Installed on 2018-03-16 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Touch-packages] [Bug 1764779] Update Released

[Łukasz Zemczak]

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

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

Title:
  Nautilus crashed open Windows-partition [assertion failed: (location
  != NULL)]

Status in glib2.0 package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  if I open a new partition from the Hard-drive (Windows in this case)
  Nautilus crash, report him self and after reopen it, the partition is
  normal available as nothing would be

  https://errors.ubuntu.com/problem/f49deb51a98d691e3e040d7f7334ad08d1e0e54c
  https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938
  https://errors.ubuntu.com/problem/00db9958203affb0a98a2842bb2bd91547e6bd5a
  https://errors.ubuntu.com/problem/818d3ad2d9fe9f9f64f32fcb5f10da4126d3827d

  [ Test case ]

  * Open nautilus and select an external hd that is not mounted from the sidebar
  * Nautilus sould not crash (in case showing an error message)

  [ Regression potential ]

  Partitions that have been actually mounted, are not shown or an error
  is prompted.

  -

  Issue from the log:

  Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount 
point cleanup: Process reported exit code 5: Failed to start 
clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit 
media-username-12F6CC77F6CC5D1B.mount not found.
  Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: 
assertion 'G_IS_MOUNT (mount)' failed
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: **
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: 
ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: 
(location != NULL)

  -

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 16:45:30 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' 
b'show-move-to-trash-shortcut-changed-dialog' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'"
  InstallationDate: Installed on 2018-03-16 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Touch-packages] [Bug 1789472] Re: SRU 2.56.2 to bionic

[Launchpad Bug Tracker]

This bug was fixed in the package glib2.0 - 2.56.2-0ubuntu0.18.04.1

---
glib2.0 (2.56.2-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1789472, LP: #1764779)
  * Refreshed patches
  * d/p/tests-network-monitor-Always-use-the-dummy-proxy-res.patch:
- Removed (aplied upstream)

 -- Marco Trevisan (Treviño)   Tue, 28 Aug 2018
13:25:36 -0500

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  SRU 2.56.2 to bionic

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  The second stable release in the 2.56 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Various fixes in multiple places (see
  https://gitlab.gnome.org/GNOME/glib/blob/d4b603/NEWS) so various apps
  could be affected.

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

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

[Touch-packages] [Bug 1789472] Update Released

[Łukasz Zemczak]

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

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

Title:
  SRU 2.56.2 to bionic

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  The second stable release in the 2.56 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Various fixes in multiple places (see
  https://gitlab.gnome.org/GNOME/glib/blob/d4b603/NEWS) so various apps
  could be affected.

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

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

[Touch-packages] [Bug 1789472] Re: SRU 2.56.2 to bionic

[Iain Lane]

I did keep on looking at the armhf failure. I think that the netlink
network monitor is a bit buggy and I filed
https://gitlab.gnome.org/GNOME/glib/merge_requests/313 with some fixes
to it.

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

Title:
  SRU 2.56.2 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  The second stable release in the 2.56 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Various fixes in multiple places (see
  https://gitlab.gnome.org/GNOME/glib/blob/d4b603/NEWS) so various apps
  could be affected.

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

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

[Touch-packages] [Bug 1767801] Re: Wrong group name "admin" instead of "adm" in default sudoers file of sudo 1.8.21p2-3ubuntu1

[Marc Deslauriers]

Do not change the line from "admin" to "adm".

The "admin" group was renamed to "sudo". The "adm" group is used for
something else and should not be part of the sudoers file.

The "admin" group needs to stay in that file to properly handle people
who upgraded systems from earlier releases. Upgrading to newer releases
doesn't automatically migrate users to the new "sudo" group, so removing
it will cause someone who just upgraded to lose sudo privileges, and
rendering them unable to fix the issue.

I am closing this bug as there is no change needed to that file.

** Changed in: sudo (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Wrong group name "admin" instead of "adm" in default sudoers file of
  sudo 1.8.21p2-3ubuntu1

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  This is just to inform you, that the file /etc/sudoers, that comes
  with sudo 1.8.21p2-3ubuntu1 during a fresh install of Xubuntu 18.04,
  contains

  # Members of the admin group may gain root privileges
  %adminALL=(ALL) ALL

  but the admin group is now named "adm" instead of "admin".
  This is easy to correct, but it might confuse people, that are not familiar 
with the sudoers file. So, I suggest to change this line to

  %adm ...

  
  Additional information:
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  apt-cache policy sudo
  sudo:
Installiert:   1.8.21p2-3ubuntu1
Installationskandidat: 1.8.21p2-3ubuntu1
Versionstabelle:
   *** 1.8.21p2-3ubuntu1 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Marcos]

This problem still exists in a fresh (minimal) installation of Ubuntu
18.04. To reproduce, just install from mini.iso without selecting any
packages at tasksel. I've discovered that if you install ebtables it
works as expected. That's why it works if you select  an Desktop or
Server option at tasksel, because both end up installing ebtables (idk
why, but whatever).

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:f

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Marcos]

Can't edit, so I'm writing another message. I was wrong about ubuntu-
desktop, it does not install ebtables by default, but server does.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

[Touch-packages] [Bug 1791673] [NEW] Sound - no output device

[Marco]

Public bug reported:

I don't understand if this is a problem of pulseaudio or what.
I don't get any sound output and the GUI Sound doesn't show any output device. 
However, the sound card module is installed:

$ lsmod | grep snd_hda_intel
snd_hda_intel  40960  6
snd_hda_codec 126976  3 
snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core   81920  4 
snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek
snd_pcm98304  4 
snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core
snd81920  33 
snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,thinkpad_acpi,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm

The audio device is detected:

$ lspci -nnk | grep -A2 Audio
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio 
[8086:a170] (rev 31)
 Subsystem: Lenovo Sunrise Point-H HD Audio [17aa:222e]
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel

For reference, I am running Ubuntu 18.04.1 LTS, with pulseaudio
1:11.1-1ubuntu7.1, and this is my alsa-base.conf:

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet 
--use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet 
--use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
options snd-hda-intel model=generic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 14:03:05 2018
InstallationDate: Installed on 2018-08-20 (21 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET78W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS6H100
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.versi

[Touch-packages] [Bug 1791688] [NEW] package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 1

[Wayne McRae]

Public bug reported:

Upgrading from 16.0 LTS to 18.04 LTS using apt dist-upgrade.  Kernel
panic booting to 4.15.0-33-generic.  Had to revert to 4.4.0-134 to get
to desktop.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: avahi-daemon 0.7-3.1ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
AptOrdering:
 xscreensaver:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Sep 10 14:28:26 2018
DpkgHistoryLog:
 Start-Date: 2018-09-10  14:28:18
 Remove: xscreensaver:amd64 (5.36-1ubuntu1)
ErrorMessage: installed avahi-daemon package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-04-27 (500 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: avahi
Title: package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: 
installed avahi-daemon package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic 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/1791688

Title:
  package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade:
  installed avahi-daemon package post-installation script subprocess
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Upgrading from 16.0 LTS to 18.04 LTS using apt dist-upgrade.  Kernel
  panic booting to 4.15.0-33-generic.  Had to revert to 4.4.0-134 to get
  to desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  AptOrdering:
   xscreensaver:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Sep 10 14:28:26 2018
  DpkgHistoryLog:
   Start-Date: 2018-09-10  14:28:18
   Remove: xscreensaver:amd64 (5.36-1ubuntu1)
  ErrorMessage: installed avahi-daemon package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-27 (500 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: 
installed avahi-daemon package post-installation script subprocess 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/1791688/+subscriptions

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

[Touch-packages] [Bug 1783571] Re: Set Yaru as default

[Didier Roche]

** Changed in: ubuntu-meta (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/1783571

Title:
  Set Yaru as default

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-sounds package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Set Yaru as default ubuntu 18.10 theme.

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

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

[Touch-packages] [Bug 1791706] [NEW] /lib/systemd/systemd-journald:6:journal_file_append_data:journal_file_append_entry:write_to_journal:dispatch_message_real:server_dispatch_message

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10.3, the problem page at 
https://errors.ubuntu.com/problem/82f6ccb214b5973176f89848a8f79045e422806c 
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: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic cosmic kylin-15.04 vivid wily xenial yakkety zesty

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

Title:
  /lib/systemd/systemd-
  
journald:6:journal_file_append_data:journal_file_append_entry:write_to_journal:dispatch_message_real:server_dispatch_message

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10.3, the problem page at 
https://errors.ubuntu.com/problem/82f6ccb214b5973176f89848a8f79045e422806c 
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/systemd/+bug/1791706/+subscriptions

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

[Touch-packages] [Bug 1609900] [NEW] Unplugging and re-plugging keyboard forgets xmodmap

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[I'm not sure against which package I can report this, so I've
preliminary done it against `qemu`]

Since I have a non-standard keyboard (a Kinesis, without Super key), I remapped 
a key on my system (XUbuntu 16.04).
This is accomplished via:

~$ cat ~/.Xmodmap
keycode 108 = Super_L

This works fine, but after any qemu execution, with passthrough of my
USB keyboard, the mapping is lost - more precisely, the system it starts
behaving like the key is not mapped.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: qemu 1:2.5+dfsg-5ubuntu10.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Aug  4 19:11:24 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-11 (24 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
KvmCmdLine:
 COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
 kvm-irqfd-clean S<   0 0  1261 2  0.0 [kvm-irqfd-clean]
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=7f35da3f-4f3a-40e1-8af0-3f02cfbf9884 ro
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XN-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug xenial
-- 
Unplugging and re-plugging keyboard forgets xmodmap
https://bugs.launchpad.net/bugs/1609900
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1609900] Re: Unplugging and re-plugging keyboard forgets xmodmap

[Phillip Susi]

** Summary changed:

- After QEMU execution with keyboard passthrough, key mappings are lost
+ Unplugging and re-plugging keyboard forgets xmodmap

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

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

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

Title:
  Unplugging and re-plugging keyboard forgets xmodmap

Status in xorg package in Ubuntu:
  New

Bug description:
  [I'm not sure against which package I can report this, so I've
  preliminary done it against `qemu`]

  Since I have a non-standard keyboard (a Kinesis, without Super key), I 
remapped a key on my system (XUbuntu 16.04).
  This is accomplished via:

  ~$ cat ~/.Xmodmap
  keycode 108 = Super_L

  This works fine, but after any qemu execution, with passthrough of my
  USB keyboard, the mapping is lost - more precisely, the system it
  starts behaving like the key is not mapped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu 1:2.5+dfsg-5ubuntu10.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug  4 19:11:24 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-11 (24 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1261 2  0.0 [kvm-irqfd-clean]
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=7f35da3f-4f3a-40e1-8af0-3f02cfbf9884 ro
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1791710] [NEW] tar 1.29b-2 breaks pristine-tar

[Saverio Proto]

Public bug reported:

Steps to reproduce:

docker run -ti ubuntu:18.04 /bin/bash

apt-get update
apt-get install git build-essential tar pristine-tar
git clone git://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron
cd neutron/
for i in `git branch -a | grep remote | grep -v HEAD | grep -v master`; do git 
branch --track ${i#remotes/origin/} $i; done
# this command will fail
pristine-tar -v checkout neutron_10.0.7.orig.tar.gz
# to fix it update tar
apt-get install wget && wget 
http://mirrors.kernel.org/ubuntu/pool/main/t/tar/tar_1.30+dfsg-2_amd64.deb
apt-get install ./tar_1.30+dfsg-2_amd64.deb
# now it works
pristine-tar -v checkout neutron_10.0.7.orig.tar.gz

** Affects: pristine-tar (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  tar 1.29b-2 breaks pristine-tar

Status in pristine-tar package in Ubuntu:
  New
Status in tar package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  docker run -ti ubuntu:18.04 /bin/bash

  apt-get update
  apt-get install git build-essential tar pristine-tar
  git clone git://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron
  cd neutron/
  for i in `git branch -a | grep remote | grep -v HEAD | grep -v master`; do 
git branch --track ${i#remotes/origin/} $i; done
  # this command will fail
  pristine-tar -v checkout neutron_10.0.7.orig.tar.gz
  # to fix it update tar
  apt-get install wget && wget 
http://mirrors.kernel.org/ubuntu/pool/main/t/tar/tar_1.30+dfsg-2_amd64.deb
  apt-get install ./tar_1.30+dfsg-2_amd64.deb
  # now it works
  pristine-tar -v checkout neutron_10.0.7.orig.tar.gz

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

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

[Touch-packages] [Bug 1791710] Re: tar 1.29b-2 breaks pristine-tar

[James Page]

** Also affects: pristine-tar (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  tar 1.29b-2 breaks pristine-tar

Status in pristine-tar package in Ubuntu:
  New
Status in tar package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  docker run -ti ubuntu:18.04 /bin/bash

  apt-get update
  apt-get install git build-essential tar pristine-tar
  git clone git://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron
  cd neutron/
  for i in `git branch -a | grep remote | grep -v HEAD | grep -v master`; do 
git branch --track ${i#remotes/origin/} $i; done
  # this command will fail
  pristine-tar -v checkout neutron_10.0.7.orig.tar.gz
  # to fix it update tar
  apt-get install wget && wget 
http://mirrors.kernel.org/ubuntu/pool/main/t/tar/tar_1.30+dfsg-2_amd64.deb
  apt-get install ./tar_1.30+dfsg-2_amd64.deb
  # now it works
  pristine-tar -v checkout neutron_10.0.7.orig.tar.gz

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

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

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

[Joe Cronin]

Public bug reported:

Failed during upgrade.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Mon Sep 10 09:18:00 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2015-06-19 (1179 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package systemd-sysv 237-3ubuntu10.3 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:
  Failed during upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 10 09:18:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2015-06-19 (1179 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791688] Re: package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess 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/1791688

Title:
  package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade:
  installed avahi-daemon package post-installation script subprocess
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Upgrading from 16.0 LTS to 18.04 LTS using apt dist-upgrade.  Kernel
  panic booting to 4.15.0-33-generic.  Had to revert to 4.4.0-134 to get
  to desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  AptOrdering:
   xscreensaver:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Sep 10 14:28:26 2018
  DpkgHistoryLog:
   Start-Date: 2018-09-10  14:28:18
   Remove: xscreensaver:amd64 (5.36-1ubuntu1)
  ErrorMessage: installed avahi-daemon package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-27 (500 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: 
installed avahi-daemon package post-installation script subprocess 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/1791688/+subscriptions

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

[Touch-packages] [Bug 1791576] Re: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1791576

Title:
  package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  bug report while I was partial-updating the 18.04 version of Ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 10 10:32:42 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-10-19 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess 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/initramfs-tools/+bug/1791576/+subscriptions

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

Note to self, I wonder if:
https://github.com/systemd/systemd/commit/c68867da320de296917820e5a76e902a8a86be5a
https://github.com/systemd/systemd/commit/7f96539d45028650f2ba9452095473a9c455d84b

are related.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1791770] [NEW] not able to change my brightness

[Neetish Borkar]

Public bug reported:

i am not able to change my brightness wint my keybord buttons or in the
settings.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 22:38:24 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c60] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP106M [GeForce GTX 1060 Mobile 6GB] 
[1043:1800]
InstallationDate: Installed on 2018-09-08 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUSTeK COMPUTER INC. GL502VMK
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=edde470d-ddb4-42e8-9a61-62c31bf664ed ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL502VMK.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL502VMK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: neetishborkar
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.203:bd11/23/2016:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL502VMK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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 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/1791770

Title:
  not able to change my brightness

Status in xorg package in Ubuntu:
  New

Bug description:
  i am not able to change my brightness wint my keybord buttons or in
  the settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 22:38:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c60] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106M [GeForce GTX 1060 Mobile 6GB] 
[1043:1800]
  InstallationDate: Installed on 2018-09-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=edde470d-ddb4-42e8-9a61-62c31bf664ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: neetishborkar
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.203:bd11/23/2016:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: li

[Touch-packages] [Bug 1786195] Re: broken audio/muffled, no system audio

[Chorca]

My issue seems to be localized to only the right speaker on a Thinkpad
x270, and the issue happens in Windows as well, so it may be due to a
blown speaker on my laptop.

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

Title:
  broken audio/muffled, no system audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.1 LTS
  pulseaudio:
Installed: 1:11.1-1ubuntu7.1
Candidate: 1:11.1-1ubuntu7.1
Version table:
   *** 1:11.1-1ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  expected sound to return to normal/crisp throughout system and media 
applications.

  sound became muffled/distorted throughout all media applications,
  while other system sounds failed altogether. volume up/down failed.
  Chime on reboot also distorted. system and application sounds appear
  normal when used via bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  novgorod   1787 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  9 01:40:50 2018
  InstallationDate: Installed on 2018-08-01 (7 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB61.88Z.00CC.B00.1802021826
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22C8AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C8AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1767453] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[miguelquiros]

I also tried to install version 20180409 after Ubuntu 18 was already
working and the error is still there. It is not a problem of the upgrade
procedure but a problem of the package itself.

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

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

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

[Touch-packages] [Bug 1767453] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[miguelquiros]

The bug appeared while upgrading from Ubuntu 16 to Ubuntu 18. It is a very 
serious bug, since many other packages depend on ca-certificates and were left 
unconfigured. Lots of error messages in the screen.
When the upgrade finished, the system was left in a very bad situation with so 
many non-configured packages. No workable reboot-shutdown button, not 
functioning menus ... If moving to a virtual terminal (Alt-F1) the virtual 
console did not work either, so the configuration error of ca-certificates is a 
really serious bug.
I did not dare to perform a hard poweroff and poweron because I was not 
confident that the system was going to be able to boot at all.
Fortunately enough, right clicking in the screen worked and I was able to open 
a terminal. From that terminal, I keyed firefox (not accesible through 
non-working menus) and downloaded from ubuntu archive the version 20170717 of 
ca-certificates and install it replacing the buggy 20180409 using dpkg -i.
After this, I performed
dpkg --configure -a
and all not-fully installed packages got correctly configured.
I had to poweroff via the button (no other choice) and when powering on again, 
Ubuntu 18 appeared with no other issue so far.

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

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

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L8548

I wonder if fake systemd-services logind shim is on the dbus, accepts
ScheduleShutdown and then does nothing.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

Reading modern systemctl code, if the scheduling fails, the intention is
to immediately shutdown.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Angel D. Segarra]

I would just remove ureadahead using apt. It's just another canonical
project that nobody has looked at in years and not a priority. I see no
difference whatsoever without it and maybe you won't either.

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

Yeah, this is all still broken upstream. If dbus call to schedule
shutdown, fails, immediate shutdown is not actually in fact attempted.

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

** Changed in: systemd (Ubuntu)
Milestone: ubuntu-17.06 => ubuntu-18.09

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Confirmed
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Walter Lapchynski]

bodhi, having the Technical Board review Phillip's posts might be
completely reasonable so as to finally end this conversation once and
for all. That has no bearing on the moderation, though.

The entire Ubuntu Community is bound by the terms of the Code of
Conduct, which, in short, means being nice to one another, regardless of
our points of view. So, I'm sorry, you don't just get to treat people
however you want just because you disagree with them. There is no
moderation as it concerns your attempts to correct a confusing technical
situation. Where the moderation exists is where it no longer remains
technical and especially where it becomes a personal attack.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

Heh, I believe there are historical options re -H -h. As a wild guess, i
looked at the sysvinit implementation in Debian (we have removed the
package in Ubuntu) it has this:

-h Halt or power off after shutdown.
-H Modifier  to the -h flag.  Halt action is to halt or drop into boot 
monitor on sys‐
   tems that support it.  Must be used with the -h flag.

So clear as mud, and i guess the "portable" way is to call "shutdown -h
-H" or something.

RE: scheduling

I guess you could inspect the system from landscape as follows:
- check system has re-execed into systemd init ( [ -d /run/systemd/system ] )
- check that upstart is gone ( UPSTART_SESSION= initctl version )
- poke the dbus interface to see if logind is there and has support for timing 
things (probably using busctl 
http://manpages.ubuntu.com/manpages/xenial/en/man1/busctl.1.html)
- realise the scheduling will not work
- request shutdown now

Imho, failing to schedule thing to shutdown, should shut the machine
down instantly. Or i should upgrade machine from trusty to xenial; and
like snapshot it; and figure out why scheduling does not work / logind
is not there.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Till Kamppeter]

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

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-34.37

---
linux (4.15.0-34.37) bionic; urgency=medium

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)

  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin SQ and RQ memory if QP create fails
- RDMA/bnxt_re: Fix system crash during load/unload
- net/mlx5e: Return error if prio is specified when offloading eswitch vlan
  push
- locking/xchg/al

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

** Also affects: landscape-client (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: systemd (Ubuntu Xenial)
Milestone: ubuntu-16.04.3 => xenial-updates

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

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

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Confirmed
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in landscape-client source package in Bionic:
  New
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1791783] [NEW] cupsd denied

[Lee]

Public bug reported:

Sep 10 12:15:44 server1 kernel: [  645.335635] audit: type=1400 
audit(1536603344.350:58): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"
Sep 10 12:15:44 server1 kernel: [  645.338733] audit: type=1400 
audit(1536603344.354:59): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"
Sep 10 12:15:44 server1 kernel: [  645.339664] audit: type=1400 
audit(1536603344.354:60): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"

apparmor-2.12-4ubuntu5, ubuntu 18.04.1

sudo aa-complain /usr/sbin/cupsd allows me to print.

Sep 10 12:19:04 server1 kernel: [  845.532951] audit: type=1400 
audit(1536603544.545:61): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16673 comm="apparmor_parser"
Sep 10 12:19:04 server1 kernel: [  845.533182] audit: type=1400 
audit(1536603544.545:62): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=16673 comm="apparmor_parser"
Sep 10 12:19:04 server1 kernel: [  845.546603] audit: type=1400 
audit(1536603544.561:63): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16673 comm="apparmor_parser"

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

** Description changed:

  Sep 10 12:15:44 server1 kernel: [  645.335635] audit: type=1400 
audit(1536603344.350:58): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"
  Sep 10 12:15:44 server1 kernel: [  645.338733] audit: type=1400 
audit(1536603344.354:59): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"
  Sep 10 12:15:44 server1 kernel: [  645.339664] audit: type=1400 
audit(1536603344.354:60): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"
  
  apparmor-2.12-4ubuntu5, ubuntu 18.04.1
  
  sudo aa-complain /usr/sbin/cupsd allows me to print.
+ 
+ Sep 10 12:19:04 server1 kernel: [  845.532951] audit: type=1400 
audit(1536603544.545:61): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16673 comm="apparmor_parser"
+ Sep 10 12:19:04 server1 kernel: [  845.533182] audit: type=1400 
audit(1536603544.545:62): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=16673 comm="apparmor_parser"
+ Sep 10 12:19:04 server1 kernel: [  845.546603] audit: type=1400 
audit(1536603544.561:63): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16673 comm="apparmor_parser"

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

Title:
  cupsd denied

Status in apparmor package in Ubuntu:
  New

Bug description:
  Sep 10 12:15:44 server1 kernel: [  645.335635] audit: type=1400 
audit(1536603344.350:58): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"
  Sep 10 12:15:44 server1 kernel: [  645.338733] audit: type=1400 
audit(1536603344.354:59): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"
  Sep 10 12:15:44 server1 kernel: [  645.339664] audit: type=1400 
audit(1536603344.354:60): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=11561 comm="cupsd" capability=12  
capname="net_admin"

  apparmor-2.12-4ubuntu5, ubuntu 18.04.1

  sudo aa-complain /usr/sbin/cupsd allows me to print.

  Sep 10 12:19:04 server1 kernel: [  845.532951] audit: type=1400 
audit(1536603544.545:61): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16673 comm="apparmor_parser"
  Sep 10 12:19:04 server1 kernel: [  845.533182] audit: type=1400 
audit(1536603544.545:62): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=16673 comm="apparmor_parser"
  Sep 10 12:19:04 server1 kernel: [  845.546603] audit: type=1400 
audit(1536603544.561:63): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16673 comm="apparmor_parser"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ub

[Touch-packages] [Bug 1788457] Re: SRU of LXC 3.0.2 (upstream bugfix release)

[Stéphane Graber]

Upload to bionic-updates

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

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

Title:
  SRU of LXC 3.0.2 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Bionic:
  In Progress
Status in lxc source package in Cosmic:
  Fix Released

Bug description:
  LXC upstream released LXC 3.0.2 as a bugfix release with following changelog:
  - CVE 2018-6556: verify netns fd in lxc-user-nic
  - fixed a range of bugs found by Coverity
  - lxc-usernsexec: cleanup and bugfixes
  - log: add CMD_SYSINFO()
  - log: add CMD_SYSERROR()
  - state: s/sleep()/nanosleep()/
  - lxclock: improve file locking
  - lxccontainer: improve file locking
  - lxccontainer: fix F_OFD_GETLK checks
  - netlink: add __netlink_{send,recv,transaction}
  - netns: allocate network namespace id
  - MAINTAINERS: add Wolfgang Bumiller
  - pam_cgfs: cleanups
  - log: add default log priority
  - tree-wide: pass unsigned long to prctl()
  - macro: add new macro header
  - conf: mount devpts without “max” on EINVAL
  - tree-wide: handle EINTR in read() and write()
  - tree-wide: replace pipe() with pipe2()
  - confile: split mount options into flags and data
  - conf: improve rootfs setup
  - autotools: default to -Wvla -std=gnu11
  - tree-wide: remove VLAs
  - tree-wide: replace strtok_r() with lxc_iterate_parts()
  - utils: add lxc_iterate_parts()
  - apparmor: allow start-container to change to lxc-**
  - apparmor: update current profiles
  - apparmor: Allow /usr/lib* paths for mount and pivot_root
  - conf: the atime flags are locked in userns
  - conf: handle partially functional device nodes
  - conf: create /dev directory
  - autotools: build both a shared and static liblxc
  - namespace: add api to convert namespaces to standard identifiers
  - tree-wide: set MSG_NOSIGNAL
  - tree-wide: use mknod() to create dummy files
  - cgfsng: respect lxc.cgroup.use
  - cgroups: remove is_crucial_cgroup_subsystem()
  - tree-wide: remove unneeded log prefixes
  - tests: cleanup all tests
  - terminal: set FD_CLOEXEC on pty file descriptors
  - conf: simplify lxc_setup_dev_console()
  - tools: rework tools
  - autodev: adapt to changes in Linux 4.18
  - log: change DEBUG, INFO, TRACE, NOTICE macro using strerror to SYS* 
macro
  - log: add lxc_log_strerror_r macro
  - network: unpriv lxc will run lxc.net.[i].script.up now
  - conf: only use newuidmap and newgidmap when necessary
  - autotools: support tls in cross-compile

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 3.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to xenial-
  backports as well, making sure we have the same version everywhere.

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

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

[Touch-packages] [Bug 1791166] Re: Programs using the libqt5gui5 library do not start.

[aroon]

OK.
Regards.

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

Title:
  Programs using the libqt5gui5 library do not start.

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Programs using the libqt5gui5 library do not start.
  Running in the terminal displays the message:
  "VirtualBox: supR3HardenedMainGetTrustedMain: 
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5Gui.so.5: cannot 
open shared object file: No such file or directory"
  or
  "smplayer: error while loading shared libraries: libQt5Widgets.so.5: cannot 
open shared object file: No such file or directory"
  My distribution is Ubuntu 18.04.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1791166/+subscriptions

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Stuart Gillies]

You may think you fixed it but I'm sitting in a hotel in The Netherlands
with a connected phone and tablet but not the laptop. Grrr! I have 18.04
up to date yesterday. Wifi says it is connected but hotel logon page
won't appear. Is there a usable workaround?

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1791808] [NEW] package gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Bhavya Singhal]

Public bug reported:

the application qtiplot won't install.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Sep 11 01:11:50 2018
DuplicateSignature:
 package:gir1.2-soup-2.4:amd64:2.62.1-1ubuntu0.1
 Setting up libmng2:amd64 (2.0.2-0ubuntu3) ...
 dpkg: error processing package gir1.2-soup-2.4:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-06-20 (81 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: libsoup2.4
Title: package gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  the application qtiplot won't install.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Sep 11 01:11:50 2018
  DuplicateSignature:
   package:gir1.2-soup-2.4:amd64:2.62.1-1ubuntu0.1
   Setting up libmng2:amd64 (2.0.2-0ubuntu3) ...
   dpkg: error processing package gir1.2-soup-2.4:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-06-20 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libsoup2.4
  Title: package gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1791808/+subscriptions

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

[Touch-packages] [Bug 1791808] Re: package gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

[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 libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1791808

Title:
  package gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  the application qtiplot won't install.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Sep 11 01:11:50 2018
  DuplicateSignature:
   package:gir1.2-soup-2.4:amd64:2.62.1-1ubuntu0.1
   Setting up libmng2:amd64 (2.0.2-0ubuntu3) ...
   dpkg: error processing package gir1.2-soup-2.4:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-06-20 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libsoup2.4
  Title: package gir1.2-soup-2.4:amd64 2.62.1-1ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1791808/+subscriptions

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

[Touch-packages] [Bug 1791811] [NEW] emacs ispell can't find german (deutsch) dictionary

[Axel G. Rossberg]

Public bug reported:

The ispell function of emacs expects to find a file such as
/usr/lib/aspell/deutsch.alias, just as there is a file british.alias in
the English aspell version. The file should probably simply contain the
lines:

# File added to make emacs ispell work
add de_DE.multi

Of course, as a simple workaround, you can add this file by hand.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: aspell-de 20151222-1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 10 21:00:17 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-08-31 (9 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
SourcePackage: igerman98
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  emacs ispell can't find german (deutsch) dictionary

Status in igerman98 package in Ubuntu:
  New

Bug description:
  The ispell function of emacs expects to find a file such as
  /usr/lib/aspell/deutsch.alias, just as there is a file british.alias
  in the English aspell version. The file should probably simply contain
  the lines:

  # File added to make emacs ispell work
  add de_DE.multi

  Of course, as a simple workaround, you can add this file by hand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: aspell-de 20151222-1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 10 21:00:17 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-31 (9 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: igerman98
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791817] [NEW] /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:run_crash

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.9-0ubuntu7.3, the problem page at 
https://errors.ubuntu.com/problem/2ad77366eaa9a36f8b12c33d55220b1c0ab7ad81 
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: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

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

Title:
  /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes:run_crash

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.9-0ubuntu7.3, the problem page at 
https://errors.ubuntu.com/problem/2ad77366eaa9a36f8b12c33d55220b1c0ab7ad81 
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/apport/+bug/1791817/+subscriptions

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

[Touch-packages] [Bug 1791817] Re: /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:run_crash

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1791324
   
/usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-gtk@598:run_argv:run_crashes:run_crash

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

Title:
  /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes:run_crash

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.9-0ubuntu7.3, the problem page at 
https://errors.ubuntu.com/problem/2ad77366eaa9a36f8b12c33d55220b1c0ab7ad81 
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/apport/+bug/1791817/+subscriptions

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

[Touch-packages] [Bug 1791822] [NEW] Internal display is blank

[Larry Reaves]

Public bug reported:

After upgrading all packages and rebooting today, the internal display
is blank.  An external display works fine.  I believe I also ran
upgrades on Friday, so it was a fairly recent package.  This is a
MacBookPro14,3.  I believe there was a kernel upgrade, not sure if there
was an Xorg upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 16:34:45 2018
DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 applespi, 0.1, 4.17.0-9-generic, x86_64: installed
 applespi, 0.1, 4.18.0-7-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Radeon Pro 555 [106b:017a]
InstallationDate: Installed on 2018-09-05 (5 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Apple Inc. MacBookPro14,3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=666e74b4-e3a0-4a21-ac25-36b7daa2d230 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to cosmic on 2018-09-05 (5 days ago)
dmi.bios.date: 06/26/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP143.88Z.0178.B00.1806261159
dmi.board.name: Mac-551B86E5744E2388
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,3
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-551B86E5744E2388
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP143.88Z.0178.B00.1806261159:bd06/26/2018:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.94-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic regression 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/1791822

Title:
  Internal display is blank

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading all packages and rebooting today, the internal display
  is blank.  An external display works fine.  I believe I also ran
  upgrades on Friday, so it was a fairly recent package.  This is a
  MacBookPro14,3.  I believe there was a kernel upgrade, not sure if
  there was an Xorg upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 16:34:45 2018
  DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   applespi, 0.1, 4.17.0-9-generic, x86_64: installed
   applespi, 0.1, 4.18.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon Pro 555 [106b:017a]
  InstallationDate: Installed on 2018-09-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. MacBookPro14,3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/

[Touch-packages] [Bug 1791820] [NEW] /usr/share/apport/apport-gtk:http.client.IncompleteRead:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:search_bug_patte

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.9-0ubuntu7.3, the problem page at 
https://errors.ubuntu.com/problem/9178257a55266131973fa3bc7462837640f82d44 
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: apport (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: bionic kylin-18.04 rls-cc-incoming xenial yakkety

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

Title:
  /usr/share/apport/apport-
  gtk:http.client.IncompleteRead:/usr/share/apport/apport-
  
gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:search_bug_patterns:read:_safe_read

Status in apport package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.9-0ubuntu7.3, the problem page at 
https://errors.ubuntu.com/problem/9178257a55266131973fa3bc7462837640f82d44 
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/apport/+bug/1791820/+subscriptions

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

[Touch-packages] [Bug 1791820] Re: /usr/share/apport/apport-gtk:http.client.IncompleteRead:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:search_bug_pattern

[Brian Murray]

Here's the Traceback:

Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 597, in 
app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 688, in run_argv
return self.run_crashes()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 245, in run_crashes
self.run_crash(f)
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 289, in run_crash
self.collect_info()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 1077, in collect_info
bpthread.exc_raise()
  File "/usr/lib/python3/dist-packages/apport/REThread.py", line 63, in 
exc_raise
raise self._exception[1].with_traceback(self._exception[2])
  File "/usr/lib/python3/dist-packages/apport/REThread.py", line 33, in run
self._retval = self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python3/dist-packages/apport/report.py", line 917, in 
search_bug_patterns
patterns = f.read().decode('UTF-8', errors='replace')
  File "/usr/lib/python3.5/http/client.py", line 461, in read
s = self._safe_read(self.length)
  File "/usr/lib/python3.5/http/client.py", line 609, in _safe_read
raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(29118 bytes read, 74729 more 
expected)

It looks like the try / except block for loading the bugpattern should
also pass on an IncompleteRead.

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

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

** Tags added: rls-cc-incoming

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

Title:
  /usr/share/apport/apport-
  gtk:http.client.IncompleteRead:/usr/share/apport/apport-
  
gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:search_bug_patterns:read:_safe_read

Status in apport package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.9-0ubuntu7.3, the problem page at 
https://errors.ubuntu.com/problem/9178257a55266131973fa3bc7462837640f82d44 
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/apport/+bug/1791820/+subscriptions

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

[Touch-packages] [Bug 1791822] Re: Internal display is blank

[Larry Reaves]

I can confirm that this is caused by the kernel update.  When booting
4.17.0-9-generic the screen works correctly.

** Package changed: xorg (Ubuntu) => linux (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/1791822

Title:
  Internal display is blank

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading all packages and rebooting today, the internal display
  is blank.  An external display works fine.  I believe I also ran
  upgrades on Friday, so it was a fairly recent package.  This is a
  MacBookPro14,3.  I believe there was a kernel upgrade, not sure if
  there was an Xorg upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 16:34:45 2018
  DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   applespi, 0.1, 4.17.0-9-generic, x86_64: installed
   applespi, 0.1, 4.18.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon Pro 555 [106b:017a]
  InstallationDate: Installed on 2018-09-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. MacBookPro14,3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=666e74b4-e3a0-4a21-ac25-36b7daa2d230 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-09-05 (5 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP143.88Z.0178.B00.1806261159
  dmi.board.name: Mac-551B86E5744E2388
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,3
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-551B86E5744E2388
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP143.88Z.0178.B00.1806261159:bd06/26/2018:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Ole]

Yes - Catch a flight to the US and go to a starbucks :).  Perhaps you can use 
the Starbucks approach I documented here:
https://askubuntu.com/questions/1023429/cant-connect-to-google-starbucks-wifi-on-ubuntu-17-10

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1063055] Re: colord-sane crashed with SIGABRT in raise()

[Chris Halse Rogers]

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

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

Title:
  colord-sane crashed with SIGABRT in raise()

Status in colord package in Ubuntu:
  Fix Released

Bug description:
  Occurred on quantal-desktop-armhf+omap4.img of 20121006 desktop when
  terminal application was closed

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: colord 0.1.21-1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-212.19-omap4 3.5.4
  Uname: Linux 3.5.0-212-omap4 armv7l
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: armhf
  Date: Sat Oct  6 19:17:57 2012
  ExecutablePath: /usr/lib/arm-linux-gnueabihf/colord/colord-sane
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta armhf+omap4 
(20121006)
  ProcCmdline: /usr/lib/arm-linux-gnueabihf/colord/colord-sane
  ProcEnviron:

  Signal: 6
  SourcePackage: colord
  StacktraceTop:
   ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   raise () from /lib/arm-linux-gnueabihf/libc.so.6
   abort () from /lib/arm-linux-gnueabihf/libc.so.6
   ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Title: colord-sane crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

Re: [Touch-packages] [Bug 1790098] Comment bridged from LTC Bugzilla

[Steve Langasek]

On Mon, Sep 10, 2018 at 09:19:41AM -, bugproxy wrote:
> So either i suspect one of the two issues here

> 1)nmcli was internally handling this in case of other distros.  i.e
> deactivated the vlan, when bond is deactivated and activate the vlan ,
> when bond is activated.

> OR

> 2)network kernel underlying module takes care of these notifications
> between bond and vlan.  I suspected this because, as i did not see any log
> updates with respect to nmcli tool for automatically deactivating and
> activating VLAN

It would be good for us to be able to isolate which of these two cases it
is, since if there is a bug with the kernel driver, that is definitely in
scope for us to ensure we fix.

To establish that this is a kernel bug, we would need to see a reproducer
for it in your existing environment that does not depend on nmcli, but is
instead reproducible using low-level iproute2 commands.

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

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MAND

[Touch-packages] [Bug 1791862] [NEW] Says 2 errors

[Nancy Wilson]

Public bug reported:

Tried to submit and now says 1 error.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Sep 10 08:57:47 2018
DistUpgraded: 2018-08-15 22:02:18,353 DEBUG Start checking for obsolete pkgs
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:167c]
InstallationDate: Installed on 2017-09-30 (344 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
MachineType: Hewlett-Packard HP ProBook 4530s
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=ee9d2869-7a7e-41c2-86ef-d8264ef4037f ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-16 (25 days ago)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SRR Ver. F.28
dmi.board.name: 167C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 22.23
dmi.chassis.asset.tag: CNU2133Q3R
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.28:bd06/26/2012:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.23:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP ProBook 4530s
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Aug 15 19:54:13 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


** Tags: apport-bug bionic i386 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/1791862

Title:
  Says 2 errors

Status in xorg package in Ubuntu:
  New

Bug description:
  Tried to submit and now says 1 error.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Sep 10 08:57:47 2018
  DistUpgraded: 2018-08-15 22:02:18,353 DEBUG Start checking for obsolete pkgs
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:167c]
  InstallationDate: Installed on 2017-09-30 (344 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=ee9d2869-7a7e-41c2-86ef-d8264ef4037f ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (25 days ago)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.28
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.23
  dmi.chassis.asset.tag: CNU2133Q3R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.28:bd06/26/2012:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion2

[Touch-packages] [Bug 1609900] Re: Unplugging and re-plugging keyboard forgets xmodmap

[Daniel van Vugt]

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Unplugging and re-plugging keyboard forgets xmodmap

Status in xorg package in Ubuntu:
  New

Bug description:
  [I'm not sure against which package I can report this, so I've
  preliminary done it against `qemu`]

  Since I have a non-standard keyboard (a Kinesis, without Super key), I 
remapped a key on my system (XUbuntu 16.04).
  This is accomplished via:

  ~$ cat ~/.Xmodmap
  keycode 108 = Super_L

  This works fine, but after any qemu execution, with passthrough of my
  USB keyboard, the mapping is lost - more precisely, the system it
  starts behaving like the key is not mapped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu 1:2.5+dfsg-5ubuntu10.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug  4 19:11:24 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-11 (24 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1261 2  0.0 [kvm-irqfd-clean]
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=7f35da3f-4f3a-40e1-8af0-3f02cfbf9884 ro
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1791770] Re: not able to change my brightness

[Daniel van Vugt]

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

** Summary changed:

- not able to change my brightness
+ not able to change my brightness [Asus GL502VMK]

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

Title:
  not able to change my brightness [Asus GL502VMK]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i am not able to change my brightness wint my keybord buttons or in
  the settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 22:38:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c60] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106M [GeForce GTX 1060 Mobile 6GB] 
[1043:1800]
  InstallationDate: Installed on 2018-09-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=edde470d-ddb4-42e8-9a61-62c31bf664ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: neetishborkar
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.203:bd11/23/2016:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

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

[Touch-packages] [Bug 1791862] Re: Says 2 errors

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Says 2 errors

Status in Ubuntu:
  Incomplete

Bug description:
  Tried to submit and now says 1 error.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Sep 10 08:57:47 2018
  DistUpgraded: 2018-08-15 22:02:18,353 DEBUG Start checking for obsolete pkgs
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:167c]
  InstallationDate: Installed on 2017-09-30 (344 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=ee9d2869-7a7e-41c2-86ef-d8264ef4037f ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (25 days ago)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.28
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.23
  dmi.chassis.asset.tag: CNU2133Q3R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.28:bd06/26/2012:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4530s
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Aug 15 19:54:13 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1790960] Re: I ve installed ubuntu and upgraded it + some apps.

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  I ve installed ubuntu and upgraded it + some apps.

Status in Ubuntu:
  Incomplete

Bug description:
  I don't know from where I catch that bug.
  Can U help me terminate it ?
  Thanks .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Sep  5 22:22:09 2018
  DistUpgraded: 2018-09-02 10:47:36,007 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 7340] [103c:188b]
  InstallationDate: Installed on 2018-09-01 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP 255 G1 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=41406866-69b5-46b7-b891-b3c847e2be2b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (3 days ago)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 188B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 69.18
  dmi.chassis.asset.tag: 5CG33351SV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.37:bd06/26/2013:svnHewlett-Packard:pnHP255G1NotebookPC:pvr08881330591620110:rvnHewlett-Packard:rn188B:rvrKBCVersion69.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP 255 G1 Notebook PC
  dmi.product.version: 08881330591620110
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Sep  2 03:55:29 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1791872] [NEW] [HDA-Intel - HDA Intel PCH, playback] Headphones not detected

[MeMo]

Public bug reported:

After 18.04 upgrade headphones (simple earphones with microphone via the
audio jack) are no longer detected. ACPI detects the microphone but not
the headphones:

$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

$ acpi_listen 
jack/microphone MICROPHONE unplug
jack/microphone MICROPHONE plug

Headphones do not appear in the list of audio devices when plugged in.

No physical problems with the headphones or the Jack otherwise (dual-
boot, tested with Windows).

I tried resetting alsa and pulseaudio to no avail. Not sure if "re-
install" preserves existing configuration files tough, so I'd appreciate
some pointers for a complete reset if necessary.

Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  memo   2270 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 23:23:05 2018
InstallationDate: Installed on 2016-06-24 (808 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
UpgradeStatus: Upgraded to bionic on 2018-04-27 (136 days ago)
dmi.bios.date: 07/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0WJF7F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd07/23/2018:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0WJF7F:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 13-7359
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-09-10T23:19:29.946335

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Headphones not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After 18.04 upgrade headphones (simple earphones with microphone via
  the audio jack) are no longer detected. ACPI detects the microphone
  but not the headphones:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ acpi_listen 
  jack/microphone MICROPHONE unplug
  jack/microphone MICROPHONE plug

  Headphones do not appear in the list of audio devices when plugged in.

  No physical problems with the headphones or the Jack otherwise (dual-
  boot, tested with Windows).

  I tried resetting alsa and pulseaudio to no avail. Not sure if "re-
  install" preserves existing configuration files tough, so I'd
  appreciate some pointers for a complete reset if necessary.

  Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  memo   2270 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 23:23:05 2018
  InstallationDate: Installed on 2016-06-24 (808 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (136 days ago)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.21.0
  dmi.board.name: 0WJF7F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd07/23/2018:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0WJF7F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-09-10T23:19:29.946335

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

-- 
Mailing list: https:/

[Touch-packages] [Bug 1790951] Re: Black vertical line on Right Side of the Screen

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (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/1790951

Title:
  Black vertical line on Right Side of the Screen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The OS appears to not recognize the monitors size and no mater if I
  select the native resolution, the black line still there. I've notice
  also that there are 2 display options, LVDS and VGA, but the problem
  is that the VGA doesn't exist, only the LVDS. I've already done the
  xrandr commands, and added the resolutions witch fitted better to the
  machine, but my guess is that it is not the resolution, it is a
  miscommunication between the OS and the hardware.

  Please help, I'm a linux user with less experience, but I like it a
  lot and I wish to stay in Ubuntu(even with that black line, but it
  would be better to not).

  Thanks for your awesome work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  5 14:57:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics 
Controller [104d:9044]
 Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics 
Controller [104d:9044]
  InstallationDate: Installed on 2018-08-31 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Sony Corporation VGC-JS160J
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=d74eae8d-b73a-4fd9-ac75-8f3ea6bed617 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0201T4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 13
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0201T4:bd08/29/2008:svnSonyCorporation:pnVGC-JS160J:pvrC6U09RL6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct13:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGC-JS160J
  dmi.product.version: C6U09RL6
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

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

[Touch-packages] [Bug 1785531] Re: i dont know what to write here.

[Daniel van Vugt]

Yes it sounds like the USB stick is faulty/corrupt, if not the USB port.

You might want to consider downloading a fresh copy of Ubuntu from here:
https://www.ubuntu.com/download/desktop/thank-you?version=18.04.1&architecture=amd64

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

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  i dont know what to write here.

Status in Ubuntu:
  Invalid

Bug description:
  I have had problem with 3 of my computers, Windows all of them ofcourse. 
Hoever i boght 3 usb stick from ubuntu to try and istall on all of the 3 
machines, and they all have the same problem! So i suspect that i have got 
severe virus from somewere. And i have tried to use all tre of the usb sticks i 
bought, but ther is the same problem with the installation anyhow. I am not an 
ace on computers neither so i do not understand what happening here. Maybe you 
guys can explain it to me. 
  Best of regards. Robert Johansson.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Aug  5 22:40:26 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Core Processor Integrated Graphics 
Controller [1179:fd3c]
  JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', 
'--lines=1000'] failed with exit code -7:
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: TOSHIBA Satellite C660
  ProcEnviron:
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/12
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 2.00
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PWWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 9
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr2.00:bd05/09/12:svnTOSHIBA:pnSatelliteC660:pvrPSC0QE-03M00RN5:rvnTOSHIBA:rnPWWAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A:
  dmi.product.name: Satellite C660
  dmi.product.version: PSC0QE-03M00RN5
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Aug  5 20:39:07 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12624 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1787365] Re: Nautilus hangs when using the location bar

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => nautilus (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/1787365

Title:
  Nautilus hangs when using the location bar

Status in nautilus package in Ubuntu:
  New

Bug description:
  After updating to 18.04 from 16.04, every time I try to type a
  character that's not a letter or a number in the nautilus location
  bar, like "/" or "~", it hangs.

  Something related to this happens with the calculator. The attachment
  is after opening it over the window where I'm typing this.

  Firefox also just crashed while typing this, so maybe it's also related.
  
https://crash-stats.mozilla.com/report/index/7dd510f7-fbaa-4554-8ccc-0b2530180816

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.2
  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:Unity7:ubuntu
  Date: Thu Aug 16 11:27:37 2018
  DistUpgraded: 2018-08-06 11:31:08,622 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1497]
  InstallationDate: Installed on 2016-05-30 (808 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Compaq 6200 Pro SFF PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=06ad5aeb-7d23-4cb7-8bda-fc035ae54b4b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-06 (9 days ago)
  dmi.bios.date: 09/20/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.24
  dmi.board.asset.tag: MXL2401SD8
  dmi.board.name: 1497
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL2401SD8
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.24:bd09/20/2013:svnHewlett-Packard:pnHPCompaq6200ProSFFPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 6200 Pro SFF PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Aug 16 10:39:21 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1774652] Re: xorg stopped responding to keyboard. Killing xorg "fixed" it

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (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/1774652

Title:
  xorg stopped responding to keyboard. Killing xorg "fixed" it

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I booted Ubuntu, and when I started using it, nothing would respond to the 
keyboard. Everything was responding normally to the mouse.
  It looked like the keystrokes were being "buffered" extremely slowly, I'll 
explain:

  For example, I opened Chrome and I started typing "facebook" in the
  address bar, but no character showed up, as if the keyboard wasn't
  even connected (however, I had used the same keyboard to type my
  password to log in and that had worked).

  So I opened a terminal, and then the characters "fa" showed up on the
  command line: that is two of the several characters that I had typed
  almost a minute before into another application.

  Then I started hitting keys randomly on my keyboard, like "lksjdbljb",
  and opening several applications (e.g. open Thunderbird, click "new
  message" - remember, the mouse was responding - and type random
  characters into the "to" address). With several seconds of delay, some
  other random characters that I had typed minutes before in another app
  would show up.

  That is, keyboard totally unusable, as if the keystroke buffer was
  slow. And this would happen with both the laptop's builtin keyboard
  and the external one connected via USB.

  
  I hit Ctrl+Alt+F1 (which responded immediately) to open a virtual terminal. I 
logged in on the virtual terminal, where the keyboard(s) would respond 
perfectly.
  I ran "top", and there was no process consuming an abnormal amount of CPU.

  I tried killing the "at-spi2-registr" process which was second in the
  list with like 2% CPU consumption and had caused me problems before
  (see #1772109), but that didn't help (I switched back to my xorg
  session via ctrl+alt+f7 and the keyboard was still berserk there).

  So finally I killed xorg, which obviously logged me out, and after I
  logged back in everything was working normally.

  
  About half of the fucking times I boot or reboot, the system is unusable due 
to some bug like this. Now this is a new one. Fucking pathetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  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: Fri Jun  1 15:59:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (1693 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  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

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

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

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

Status in linux package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1771331] Re: boot error, low resolution graphic mode

[Daniel van Vugt]

** Tags added: radeon

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

-  boot error, low resolution graphic mode
+ [radeon] boot error, low resolution graphic mode

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

Title:
  [radeon] boot error, low resolution graphic mode

Status in xorg-server package in Ubuntu:
  New

Bug description:
  This error only takes a short time, I suppose it must be due to some
  update of the Kernel or due to a change in Xorg. It does not always
  happen, only on some occasions when (re) starting the system the error
  "graphic mode in low resolution" appears but the appearance of the
  desktop is the same. I do not use high resolution graphics or 3D
  games. Only typical desktop applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
   
  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 May 15 12:45:53 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Trinity [Radeon HD 7540D] [1849:9991]
  InstallationDate: Installed on 2017-01-17 (482 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e48303dd-74b7-4cd9-b061-53998eeb96fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: FM2A75M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd11/20/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-HD+: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.
  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 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 15 12:24:45 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1770831] Re: Screen probles

[Daniel van Vugt]

Can you please take a photo of the problem and attach it here?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Screen probles 
+ [i915] Screen problems

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

Title:
  [i915] Screen problems

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When I sart I have a screen black and white pixels I put in stand by
  when I leave standby then screen is normal

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 12 12:42:38 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated 
Graphics Controller [1025:015b]
 Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [1025:015b]
  InstallationDate: Installed on 2018-04-09 (33 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Acer AOA150
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic 
root=UUID=f11f3698-678f-4e8e-8a2d-27ef88b479a0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3309
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3309:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  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: Sat May 12 12:20:25 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4546 
   vendor AUO
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

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

[Touch-packages] [Bug 1771235] Re: ext4 failed

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  ext4 failed

Status in Ubuntu:
  Incomplete

Bug description:
  Instable system with frozen and necessary reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon May 14 21:25:26 2018
  DistUpgraded: 2018-05-12 04:48:36,552 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd Skylake GT2 [HD Graphics 520] 
[144d:c136]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3L
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (2 days ago)
  dmi.bios.date: 06/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09AFN.043.170601.KS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP900X3L-KW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8830A0A-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09AFN.043.170601.KS:bd06/01/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3L:pvrP09AFN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3L-KW1BR:rvrSGL8830A0A-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 900X3L
  dmi.product.version: P09AFN
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat May 12 04:17:44 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/+bug/1771235/+subscriptions

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

[Touch-packages] [Bug 1771839] Re: keyboard

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  keyboard

Status in Ubuntu:
  Incomplete

Bug description:
  The keyboard is desconfigurated for spanish.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu May 17 10:03:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06fb]
  InstallationDate: Installed on 2017-04-21 (390 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Vostro 3250
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.5.2
  dmi.board.name: 0J4NFV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3250
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.
  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: Thu May 17 08:46:00 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputDP-1  
HDMI-1
  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/+bug/1771839/+subscriptions

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

[Touch-packages] [Bug 1771205] Re: This error cause fail of system

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  This error cause fail of system

Status in Ubuntu:
  Incomplete

Bug description:
  Sorry, I cannot write about it right now.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon May 14 21:51:11 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0725]
  InstallationDate: Installed on 2018-04-19 (24 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c00 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 11-3162
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=4d2bbd82-2c08-4d05-b7b1-f90a3e290e20 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0FCNP5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd04/19/2016:svnDellInc.:pnInspiron11-3162:pvr1.0.8:rvnDellInc.:rn0FCNP5:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.version: 1.0.8
  dmi.sys.vendor: Dell Inc.
  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

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

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

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

[mostafa]

Public bug reported:

plz help me!

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-34-generic 4.15.0-34.37
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
AptOrdering:
 ubuntu-desktop:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm3791 F pulseaudio
  mostafa6155 F pulseaudio
 /dev/snd/controlC1:  gdm3791 F pulseaudio
  mostafa6155 F pulseaudio
Date: Tue Sep 11 08:11:02 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=e5ce10c3-4a95-4ddb-82b3-57c1f449995b
InstallationDate: Installed on 2018-01-23 (230 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 20C600ABAD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=d784502d-edb2-4e1e-b9e4-a226c210abac ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET9EWW (2.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C600ABAD
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET9EWW(2.24):bd09/23/2016:svnLENOVO:pn20C600ABAD:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600ABAD:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad Edge E540
dmi.product.name: 20C600ABAD
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package bionic

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  plz help me!

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  AptOrdering:
   ubuntu-desktop:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3791 F pulseaudio
mostafa6155 F pulseaudio
   /dev/snd/controlC1:  gdm3791 F pulseaudio
mostafa6155 F pulseaudio
  Date: Tue Sep 11 08:11:02 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=e5ce10c3-4a95-4ddb-82b3-57c1f449995b
  InstallationDate: Installed on 2018-01-23 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 20C600ABAD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=d784502d-edb2-4e1e-b9e4-a226c210abac ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET9EWW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600ABAD
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chas

[Touch-packages] [Bug 796588] Re: Fine-grained network mediation

[Nicholas Zatkovich]

I suppose it's time for the bi-annual nudge on this.

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

Title:
  Fine-grained network mediation

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  This is a wishlist item / feature request.

  Increase the granularity of network restrictions to allow
  specification of which ports or ranges of ports can or can't be used
  by an application.  This functionality is available in systrace if
  either the example or code would be of help:

  http://en.wikipedia.org/wiki/Systrace

  http://www.systrace.org/

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

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

[Touch-packages] [Bug 796588] Re: Fine-grained network mediation

[Nicholas Zatkovich]

More to the point, implementing this would give snaps the ability to add
fine-grained network permissions for plugs, and this would suddenly make
snaps a very attractive alternative to Docker images for server apps. I
think this should be considered for priority.

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

Title:
  Fine-grained network mediation

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  This is a wishlist item / feature request.

  Increase the granularity of network restrictions to allow
  specification of which ports or ranges of ports can or can't be used
  by an application.  This functionality is available in systrace if
  either the example or code would be of help:

  http://en.wikipedia.org/wiki/Systrace

  http://www.systrace.org/

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

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

[Touch-packages] [Bug 1774049] Re: df incorrectly reports available space left

[Launchpad Bug Tracker]

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

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

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

Title:
  df incorrectly reports available space left

Status in coreutils package in Ubuntu:
  Expired

Bug description:
  When using df command, it reports 19GB available on /home, however
  trying to write anything to that gives a no space left error.

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

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

[Touch-packages] [Bug 796588] Re: Fine-grained network mediation

[John Johansen]

No disagreement that this is a high priority item. There is some work
around fine grained mediation happening but I am unsure when it will
land.

The problem is that this is not the only high priority item that needs
to be addressed. Changing priority of these items can certainly be
discussed again.

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

Title:
  Fine-grained network mediation

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  This is a wishlist item / feature request.

  Increase the granularity of network restrictions to allow
  specification of which ports or ranges of ports can or can't be used
  by an application.  This functionality is available in systrace if
  either the example or code would be of help:

  http://en.wikipedia.org/wiki/Systrace

  http://www.systrace.org/

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

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