[Touch-packages] [Bug 1763262] Re: systemd-journald crashed with SIGABRT in pthread_sigmask()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in pthread_sigmask()

Status in systemd package in Ubuntu:
  New

Bug description:
  I unfortunately cannot provide any more detail, as this message
  indicating the error was found pre existing on my screen. I hope it at
  least helps.

  Requested Info:
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu7
Candidate: 237-3ubuntu7
Version table:
   *** 237-3ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  8 20:27:32 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-03-05 (37 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  MachineType: Dell Inc. MM061
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   LC_TIME=en_NZ.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=6793acad-c3a5-48b0-83cc-8f52de815229 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   pthread_sigmask (how=2, newmask=, oldmask=0x0) at 
../sysdeps/unix/sysv/linux/pthread_sigmask.c:50
   journal_file_set_offline () from /lib/systemd/libsystemd-shared-237.so
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-237.so
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in pthread_sigmask()
  UpgradeStatus: Upgraded to bionic on 2018-03-13 (30 days ago)
  UserGroups:
   
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

[Launchpad Bug Tracker]

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

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

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Expired
Status in mesa package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  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.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

[Launchpad Bug Tracker]

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

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

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Expired
Status in mesa package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  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.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 372588] Re: sudo crontab -e uses wrong vi version

[Lucas Sandery]

In this case, when update-alternatives does not work, try select-editor
instead.

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

Title:
   sudo crontab -e uses wrong vi version

Status in vim package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: vim

  When editing sudo's crontab using 'sudo crontab -e' ubuntu does not
  use vim which is set as the default $EDITOR

  What was tried:
  --
  Method-1:
  /home//.bashrc has export EDITOR=/usr/bin/vim

  This works when I do crontab -e but not when sudo crontab -e

  Method-2:
  1. Removed EDITOR environment variable from /home//.bashrc
  2. And tried
  sudo update-alternatives --config editor

  There are 5 alternatives which provide `editor'.

SelectionAlternative
  ---
1/usr/bin/vim.tiny
2/bin/ed
3/bin/nano
4/usr/bin/vim.basic
  *+5/usr/bin/vim.gnome

  Again, this works when I do crontab -e but not when sudo crontab -e. I
  tried 1, 4 and 5. No dice.

  Method-3:
  sudo EDITOR=vim crontab -e works. But why should I prefix the command with 
the environment variable everytime I run it. It should pick the editor as set 
in Method-1 and Method-2.

  What is expected to happen: 'sudo crontab -e' should open the crontab
  using the default system $EDITOR without much fuss.

  
  More info: http://ubuntuforums.org/showthread.php?t=1075667

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

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

[Touch-packages] [Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens

[Adolfo Jayme]

** No longer affects: ubuntu-font-family-sources (Ubuntu)

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

Title:
  Font/text rendering is irregular and not pixel-aligned on low DPI
  screens

Status in Canonical System Image:
  Confirmed
Status in fontconfig package in Ubuntu:
  Incomplete
Status in freetype package in Ubuntu:
  Incomplete
Status in harfbuzz package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and
  unity8 Mir session

  the version of qtdeclarative5-qtmir-plugin is
  0.4.7+16.04.20160104-0ubuntu1

  As you can see from the screenshots the text has low details and, in
  the case of indicators descriptions at the top, almost disappears.

  The text could be fixed by using Text.NativeRendering instead of 
Text.QtRendering for the QML labels on low dpi screens, although text doesn't 
seem to be the only issue here. The icons are definitely lacking detail as well 
(QML Image's smoothing is enabled maybe?).
  Also the dots of the infographic don't look like circles at all, they're 
missing pixels and many of them look like a C more than an O.

  It looks to me like something is setting the wrong resolution, because
  it looks quite bad. But the screenshots are 1366x768 so I think that's
  not the case.

  NOTE: Unity7 looks perfectly fine and detailed

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

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

[Touch-packages] [Bug 823348] Re: [nc] No guidance for contributors on how to design new characters

[Adolfo Jayme]

** No longer affects: ubuntu-font-family-sources (Ubuntu)

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

Title:
  [nc] No guidance for contributors on how to design new characters

Status in Ubuntu Font Family:
  New

Bug description:
  Can you please provide a "Styleguide" for the ubuntu font family?
  I tried to add a character on my own, matching the style of the rest of the 
ubuntu font, discovering that I would need a bit more "artistic guidance". 
Tried to copy the style from the given characters, but haven't been 100% 
certain when a line should be straight or curved for example. It would be nice 
to have the "rules" documented that if people start adding characters for other 
languages from scatch they have something to rely on.

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

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

[Touch-packages] [Bug 820034] Re: [742 new] Miscellaneous Symbols and Pictographs (Emoji)

[Adolfo Jayme]

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

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

Title:
  [742 new] Miscellaneous Symbols and Pictographs (Emoji)

Status in Ubuntu Font Family:
  Triaged
Status in fonts-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  This is a wishlist item.

  Please introduce Unicode character 'PILE OF POO' (U+1F4A9) in future versions 
of the Ubuntu font.
  It could be quite useful for changelogs, or for certain email communications.

  Ref.:
  http://www.fileformat.info/info/unicode/char/1f4a9/index.htm
  http://babelstone.blogspot.com/2009/11/whats-new-in-unicode-60.html

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

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

[Touch-packages] [Bug 1763156] Re: Bluetooth doesn't reconnect to my headsetup post resume from sleep

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1759628
bluez regression: Bluetooth audio fails to reconnect after resume

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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

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

[Touch-packages] [Bug 1746949] Re: Terminal lags (low FPS) the whole desktop when fast output

[Daniel van Vugt]

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=778926
   Importance: Unknown
   Status: Unknown

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

Title:
  Terminal lags (low FPS) the whole desktop when fast output

Status in GTK+:
  Unknown
Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Hi,

  When using Wayland and gnome-terminal, the performance/fps of the
  whole desktop is real low when gnome-terminal outputs alot of data.

  This happens when you cat some logfile for example, or do a tail -f on a 
quickly growing file.
  The whole desktop feels sluggish then.

  This is only the case on Wayland. on X-Server it goes perfectly!

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

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

[Touch-packages] [Bug 1763182] Re: remove landscape-common from minimal image

[David Britton]

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: Canonical Server Team (canonical-server) => ChristianEhrhardt 
(paelzer)

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

Title:
  remove landscape-common from minimal image

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The stated goal of minimal image is to strip out packages useful only
  to humans so that a smaller base can be used to build smaller
  applications running in clouds and in containers.

  To this end, please remove landscape-common as it pulls in a few
  python3 deps, and its goal is only to provide an entry in the dynamic
  MOTD that shows system statistics (disk usage, memory usage, etc) that
  a human would look at when logging in interactively.

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

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

[Touch-packages] [Bug 1748095] Re: Non-root user can reboot machine from the command line

[Rocko]

I sometimes need to reboot a server that I'm logged into. In this case,
I got the wrong gnome-terminal tab by mistake and rebooted my laptop
instead, losing all my current work, which was an extremely suboptimal
outcome.

I checked rebooting from another user when my first user logged in, and
it didn't let me do it - it told me the command to try, however, which
did require authentication. (Rebooting from the system menu didn't work
at all, it just silently failed, but that's another matter.)

I agree typing reboot into a terminal is not something that desktop
users typically do - in which case, why support it? Or at least why not
make the user confirm it's what they actually want before rebooting?

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

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

Status in systemd package in Ubuntu:
  Opinion

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1763203] [NEW] package console-setup-hostname 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package

[vickie71]

Public bug reported:

i upgraded my system.but it said an error

ProblemType: Package
DistroRelease: Kali 2018.2
Package: console-setup-linux 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Apr 12 04:52:24 2018
ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', 
which is also in package keyboard-configuration 1.108ubuntu15.3
InstallationDate: Installed on 2018-04-11 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.19.0.5kali1
 apt  1.2.25
SourcePackage: console-setup
Title: package console-setup-hostname 1.108ubuntu15.3 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package console-setup-hostname 1.108ubuntu15.3 failed to
  install/upgrade: trying to overwrite '/lib/systemd/system/console-
  setup.service', which is also in package keyboard-configuration
  1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  New

Bug description:
  i upgraded my system.but it said an error

  ProblemType: Package
  DistroRelease: Kali 2018.2
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Apr 12 04:52:24 2018
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2018-04-11 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.19.0.5kali1
   apt  1.2.25
  SourcePackage: console-setup
  Title: package console-setup-hostname 1.108ubuntu15.3 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752639] Re: Sound Indicator disappears on vertical MATE panel

[Alexander Browne]

** Also affects: indicator-power (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Sound Indicator disappears on vertical MATE panel

Status in indicator-power package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  If you use the sound indicator with a vertical panel, it will
  disappear when an app like Rhythmbox that adds itself to the
  indicator's menu is opened (or closed).

  You can see this by adjusting the properties of the default Ubuntu
  MATE top panel by changing the orientation to left. The sound
  indicator is there, but if you open Rhythmbox it disappears. If you
  change the panel back to top orientation, the indicator shows up
  again. (If you then change it back to left, the sound indicator does
  show up, but will disappear again if you quit Rhythmbox.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: indicator-sound 12.10.2+17.10.20170829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ActionStates: ({'mute': (true, signature '', []), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [<0.31622314453125>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 'desktop-settings': 
(true, '', []), 'volume-sync': (true, 't', []), 'rhythmbox.desktop': 
(true, '', [<{'running': , 'state': <'Paused'>}>]), 
'rhythmbox.desktop.greeter': (true, '', [<{'running': , 'state': 
<'Paused'>}>]), 'volume': (true, 'i', [<0.24173394559660655>]), 
'previous.rhythmbox.desktop': (true, '', []), 'indicator-shown': (true, '', 
[]), 'root': (true, '', [<{'title': <'Sound'>, 'accessible-desc': 
<'Volume (36%)'>, 'icon': <('themed', <['audio-volume-medium-panel', 
'audio-volume-medium', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'silent-mode': (true, '', []), 'play.rhythmbox.desktop': (true, '', 
[<'Paused'>]), 'next.rhythmbox.desktop': (true, '', []), 
'play-playlist.rhythmbox.desktop': (true, 's', [])},)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Mar  1 10:12:40 2018
  InstallationDate: Installed on 2018-03-01 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180301)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1488620] Re: Add LZ4 support

[Balint Reczey]

Initramfs-tools-core should also suggest liblz4-tool package.

** Patch added: "initramfs-tools_0.130ubuntu4.patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+attachment/5111337/+files/initramfs-tools_0.130ubuntu4.patch

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

Title:
  Add LZ4 support

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  I found that I could enable LZ4 compression for initramfs on my vivid
  machine by installing liblz4-tool package, adding one line to
  mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y.

  Please include support for (legacy) LZ4.

  Attached patch includes changes made to the latest version (initramfs-
  tools_0.120ubuntu3).

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

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

[Touch-packages] [Bug 1763182] Re: remove landscape-common from minimal image

[Launchpad Bug Tracker]

** Branch linked: lp:~vorlon/livecd-rootfs/lp.1763182

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

Title:
  remove landscape-common from minimal image

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The stated goal of minimal image is to strip out packages useful only
  to humans so that a smaller base can be used to build smaller
  applications running in clouds and in containers.

  To this end, please remove landscape-common as it pulls in a few
  python3 deps, and its goal is only to provide an entry in the dynamic
  MOTD that shows system statistics (disk usage, memory usage, etc) that
  a human would look at when logging in interactively.

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

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

[Touch-packages] [Bug 1763186] [NEW] apt-get install --reinstall --install-recommends ... doesn't install Recommends

[TJ]

Public bug reported:

apt-cache policy apt
apt:
  Installed: 1.6~beta1
  Candidate: 1.6~beta1
  Version table:
 *** 1.6~beta1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


Whilst trying to use virt-manager it reported requiring additional packages to 
run the SpiceClientGTK, which are Recommends of virt-manager.

System is configured with:

/etc/apt/apt.conf.d/05-no-install-recommends:APT::Install-Recommends
"false";

I did:

apt-get install --reinstall --install-recommends

but the Recommends are not installed. It seems that "--install-
recommends" is silently ignored.

apt-get remove virt-manager && apt-get install --install-recommends
virt-manager

works.

There's one of two bugs here, either:

1. should not ignore --install-recommends
2. should report it is ignoring --install-recommends

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

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

Title:
  apt-get install --reinstall --install-recommends ... doesn't install
  Recommends

Status in apt package in Ubuntu:
  New

Bug description:
  apt-cache policy apt
  apt:
Installed: 1.6~beta1
Candidate: 1.6~beta1
Version table:
   *** 1.6~beta1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Whilst trying to use virt-manager it reported requiring additional packages 
to run the SpiceClientGTK, which are Recommends of virt-manager.

  System is configured with:

  /etc/apt/apt.conf.d/05-no-install-recommends:APT::Install-Recommends
  "false";

  I did:

  apt-get install --reinstall --install-recommends

  but the Recommends are not installed. It seems that "--install-
  recommends" is silently ignored.

  apt-get remove virt-manager && apt-get install --install-recommends
  virt-manager

  works.

  There's one of two bugs here, either:

  1. should not ignore --install-recommends
  2. should report it is ignoring --install-recommends

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

-- 
Mailing list: https://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 1730242] Re: My system will not recover from suspend

[Robert McCarter]

Thank you for the advice. Apparently, there must have been a prior email
that I did not see. I apologize for that and plan to try the steps
outlined in the “Debugging Kernel Suspend” this weekend. If a still
cannot solve the problem can I still come back for help.

Sincerely,

Bob McCarter

> On Apr 9, 2018, at 12:17 AM, Launchpad Bug Tracker 
> <1730...@bugs.launchpad.net> wrote:
> 
> [Expired for xorg (Ubuntu) because there has been no activity for 60
> days.]
> 
> ** Changed in: xorg (Ubuntu)
>   Status: Incomplete => Expired
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1730242
> 
> Title:
>  My system will not recover from suspend
> 
> Status in xorg package in Ubuntu:
>  Expired
> 
> Bug description:
>  I have ubuntu installed on a dell vostro 200 desktop. I think this
>  problem began with version 12 upgrade. Prior to that it would recover
>  from auto suspends.
> 
>  Thanks in advance for any advice to correct the problem.
> 
>  Best,
> 
>  Bob
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.04
>  Package: xorg 1:7.7+13ubuntu3
>  Uname: Linux 4.13.11-041311-generic i686
>  .tmp.unity_support_test.1:
> 
>  ApportVersion: 2.20.1-0ubuntu2.10
>  Architecture: i386
>  CompizPlugins: No value set for 
> `/apps/compiz-1/general/screen0/options/active_plugins'
>  CompositorRunning: compiz
>  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>  CompositorUnredirectFSW: true
>  Date: Sun Nov  5 16:57:10 2017
>  DistUpgraded: Fresh install
>  DistroCodename: xenial
>  DistroVariant: ubuntu
>  DkmsStatus:
>   bbswitch, 0.8, 4.13.11-041311-generic, i686: installed
>   bbswitch, 0.8, 4.4.0-100-generic, i686: installed
>   nvidia-304, 304.135, 4.4.0-100-generic, i686: installed
>  ExtraDebuggingInterest: Yes, if not too technical
>  GraphicsCard:
>   NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 
> 00 [VGA controller])
> Subsystem: NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:0977]
>  InstallationDate: Installed on 2012-08-05 (1917 days ago)
>  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
> (20120423)
>  ProcEnviron:
>   LANGUAGE=en_US
>   PATH=(custom, no user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.11-041311-generic 
> root=UUID=c8f2cac1-e3af-4e51-8a89-726ef2282d44 ro drm.debug=0xe plymouth:debug
>  Renderer: Software
>  SourcePackage: xorg
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.vendor: Dell Inc.
>  dmi.board.vendor: Dell Inc.
>  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
>  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
>  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
>  version.xserver-xorg-core: xserver-xorg-core 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: Sun Nov  5 16:53:35 2017
>  xserver.configfile: default
>  xserver.devices:
>   inputPower Button KEYBOARD, id 6
>   inputPower Button KEYBOARD, id 7
>   inputDell Dell KM632 Wireless Keyboard and Mouse KEYBOARD, id 8
>   inputDell Dell KM632 Wireless Keyboard and Mouse KEYBOARD, id 9
>   inputDell Dell KM632 Wireless Keyboard and Mouse MOUSE, id 10
>  xserver.logfile: /var/log/Xorg.0.log
>  xserver.version: 2:1.18.4-0ubuntu0.7
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730242/+subscriptions

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

Title:
  My system will not recover from suspend

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have ubuntu installed on a dell vostro 200 desktop. I think this
  problem began with version 12 upgrade. Prior to that it would recover
  from auto suspends.

  Thanks in advance for any advice to correct the problem.

  Best,

  Bob

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.13.11-041311-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov  5 16:57:10 2017
  DistUpgraded: 

[Touch-packages] [Bug 1763182] Re: remove landscape-common from minimal image

[Steve Langasek]

currently, landscape-common is a dependency of the ubuntu-server
metapackage, which means removing landscape-common from the image will
also remove ubuntu-server.  I think we want landscape-common dropped to
a recommends via the seed first.

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

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

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

Title:
  remove landscape-common from minimal image

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The stated goal of minimal image is to strip out packages useful only
  to humans so that a smaller base can be used to build smaller
  applications running in clouds and in containers.

  To this end, please remove landscape-common as it pulls in a few
  python3 deps, and its goal is only to provide an entry in the dynamic
  MOTD that shows system statistics (disk usage, memory usage, etc) that
  a human would look at when logging in interactively.

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

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

[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction

[Etienne URBAH]

With 'systemd' version 237-3ubuntu7 from Ubuntu 18.04 Bionic Beta2 :

-  The 'pm-utils' package is NOT installed by default, and 'systemd'
does NOT systematically suspend my computer 2mn after the last opened
user session has been closed.

-  After manual installation of the 'pm-utils' package, 'systemd' DID
suspend my computer 2mn after the last opened user session has been
closed.

I have to perform further tests to check if the good behavior of
'systemd' systematically comes from the presence of the 'pm-utils'
package.

** Tags added: artful bionic

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

Title:
  IdleAction=suspend specified in logind.conf must systematically be
  inhibited during user interaction

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

Bug description:
  I want my computer to suspend when there is NO opened user session.

  So, I have activated following lines inside '/etc/systemd/logind.conf' :
  IdleAction=suspend
  IdleActionSec=15min

  -  Systematically , under Ubuntu Vivid (15.04), this works correctly :
 During user interaction, the computer does NOT automatically suspend, but 
stays continuously alive.
 Once all users have closed their session, the computer automatically 
suspends after 15 min.

  -  But systematically , under Ubuntu Wily (15.10 beta2), the computer 
automatically suspends after 15 min EVEN during user interaction.
 Hitting the keyboard makes the computer resume without data loss, but this 
is still annoying.
 In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must 
systematically be inhibited during user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z_admin1665 F pulseaudio
   /dev/snd/controlC1:  z_admin1665 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  8 19:26:59 2015
  HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140
  InstallationDate: Installed on 2015-09-27 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1763171] [NEW] graphic card driver packages cant be installed

[luka rogava]

Public bug reported:

i used intel graphics update tool for linux, couldnt install packages,
i also tried lots of command lines from various guides but still the
problem cant be solved. What i could understand is that maybe intel
doesnt support this old drivers for linux? because i had windows on this
laptop (Lenovo Thinkpad T410)earlier and everything was fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Apr 12 00:29:35 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
InstallationDate: Installed on 2018-03-19 (23 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: LENOVO 25184HU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=566b3489-a039-4407-a87c-e4ee4bbb0565 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET65WW (1.25 )
dmi.board.name: 25184HU
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:bvr6IET65WW(1.25):bd06/07/2010:svnLENOVO:pn25184HU:pvrThinkPadT410:rvnLENOVO:rn25184HU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T410
dmi.product.name: 25184HU
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91+git1804061830.cb850c~oibaf~x
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1804111930.bd9539~oibaf~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1804111930.bd9539~oibaf~x
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 Apr 12 00:23:23 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

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  graphic card driver packages cant be installed

Status in xorg package in Ubuntu:
  New

Bug description:
  i used intel graphics update tool for linux, couldnt install packages,
  i also tried lots of command lines from various guides but still the
  problem cant be solved. What i could understand is that maybe intel
  doesnt support this old drivers for linux? because i had windows on
  this laptop (Lenovo Thinkpad T410)earlier and everything was fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 12 00:29:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2018-03-19 (23 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 25184HU
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt

[AsciiWolf]

** Summary changed:

- [RFE] Automatically update the Ubuntu version strings
+ [RFE] Automatically update the Ubuntu version strings in python-apt

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

Title:
  [RFE] Automatically update the Ubuntu version strings in python-apt

Status in Ubuntu Translations:
  New
Status in python-apt package in Ubuntu:
  New

Bug description:
  Every time there is a new Ubuntu release, some strings need to be
  manually translated although the only thing that is changing is the
  Ubuntu version and code name. Please, consider updating these strings
  automatically based on a translated template. It would help many
  translators.

  These strings are:
  Ubuntu xx.yy 'Code Name'
  Cdrom with Ubuntu xx.yy 'Code Name'

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

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

[Touch-packages] [Bug 1763156] Re: Bluetooth doesn't reconnect to my headsetup post resume from sleep

[Anmar Oueja]

The following patches were added to the 5.48 version in Fedora and they
did fix the problem. Perhaps worth you adding them as well. Please see
https://koji.fedoraproject.org/koji/buildinfo?buildID=1040106 and the
bug https://bugzilla.redhat.com/show_bug.cgi?id=1534857

** Attachment added: "bluez-5.48-patches.zip"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1763156/+attachment/5111219/+files/bluez-5.48-patches.zip

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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

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

[Touch-packages] [Bug 1763156] Re: Bluetooth doesn't reconnect to my headsetup post resume from sleep

[Anmar Oueja]

Problem seems resolved with bluez 5.48.2 as outlined in this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1534857#c30

** Bug watch added: Red Hat Bugzilla #1534857
   https://bugzilla.redhat.com/show_bug.cgi?id=1534857

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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

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

[Touch-packages] [Bug 1763156] [NEW] Bluetooth doesn't reconnect to my headsetup post resume from sleep

[Anmar Oueja]

Public bug reported:

Steps to repro:

* Cold boot the laptop
* Pair it with bluetooth headset
* Listen to music
* Turn off the headset or turn off the bluetooth on the laptop
* Play music, sound comes out of the laptop speakers
* Turn on the headset back on or the bluetooth on the laptop
* Headset reconnects with the laptop and audio plays from the headset

-- all the above is expected --

* Suspend the laptop
* wait a minute or two for the headset to power down
* Resume the laptop
* Turn on the bluetooth headeset
* It doesn't automatically reconnect to the laptop (not expected behaviour)
* Launch Gnome Settings and select Bluetooth and force the headset to connect
* It connects for 2 seconds then disconnects (not expected behaviour)

The only to get the headset to reconnect again is by restarting the
bluetooth.service using systemctl.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 11 15:28:28 2018
InstallationDate: Installed on 2018-04-03 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 0JHP5H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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


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

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Juha Sahakangas]

The DISPLAY checks were not yet in place in 16.04 console-setup so the
bug probably happens a lot more frequently on it... would be nice if
they could be backported since it still has long period of support left
and this is extremely annoying. I'm starting to think there is some
other cause too because it seems to be much too common, why would
console-setup's packaging scripts be ran all the time since the package
itself updates hardly ever. Or does some trigger force that?

Note to everyone who suffers from it that this can be temporarily fixed
by running "sudo kbd_mode -s", which should be much less disruptive way
of solving it for a time than rebooting.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1538284] Re: [SRU] Unescaped left brace in regex is deprecated

[Eric Desrochers]

@Seyeong Kim (xtrusia)

I just notice a few DEP-8 failures. 
Please look here: https://people.canonical.com/~ubuntu-archive/pending-sru.html
and try to identify what's going on and take appropriate 
actions/justifications/... for each.

- Eric

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

Title:
  [SRU] Unescaped left brace in regex is deprecated

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Trusty:
  Won't Fix
Status in pam source package in Xenial:
  Fix Committed
Status in pam source package in Artful:
  Fix Committed
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

  When installing postgresql, many warning msgs are raised
  Please refer to Original Description

  ## Corrections
  In trusty, escaping is missing but not the same symptom. NOT AFFECTED TO 
TRUSTY

  [Test Case]

  1. create ubuntu instance
  2. apt install postgresql

  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.

  [Other info]

  Debian Bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810873
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815595

  [Original Description]

  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+subscriptions

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[granjerox]

Hello I've notice this strange behabiour a few days ago.

Here my setup:
- Dell XPS 13 first gen
- Ubuntu Gnome 16.04 up to date

Every alt+Fx changes to virtual terminals, win+left or right also. But
its not like control is pressed.

By the way alt+f2 brings back to GUI. And alt+f4 changes to virtual 4
and same time closes active window ... a real nightmare.

I havent narrow down the trigger but if I restart it gets solved and
returns from time to time.

I, like most linux users, love keyboard shortcut and there ara a few
with alt+fx.

Is this bug being tracked somewhere else?

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

[GeekSmith]

To distill this down to its most basic form, let's try this.

When resolvconf or resolved is installed but disabled, its DHCP hook
script still executes and potentially interferes with the proper
operation of other hook scripts.

My patch ensures that these hook scripts only run when the corresponding
service is enabled.

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

[GeekSmith]

What I'm trying to achieve is this: use resolvconf instead of resolved
in Ubuntu 17.10. There is a bug when one tries to do so.

This is a fresh install on a laptop using the desktop installation DVD.

resolv.conf points to /run/resolvconf/resolv.conf and is managed by
resolvconf.

I have NetworkManager and resolvconf enabled for interfaces not managed
by ifupdown, as shown in NetworkManager.conf in the initial report. I'm
using ifupdown for ethernet interfaces, NetworkManager for Wi-Fi.

The steps to reproduce are:
1. Install and enable resolvconf
2. Stop and mask resolved
3. Configure NetworkManager for resolvconf and ifupdown
4. Configure an interface in ifupdown for dhcp
5. Connect to the network

I agree that overriding make_resolv_conf() is good and necessary.
However, the scripts that do so currently do it blindly, even when the
service they support is disabled. My patch adds a simple sanity check to
ensure that disabled services don't run a script that will break DHCP
for enabled services.

I've described what was done to my system. If you have further
questions, please let me know. My goal is to use resolvconf in the place
of resolved. In doing so, I uncovered a bug in the dhcp hook scripts for
both resolved and resolvconf and I've provided a working patch for those
bugs. The patches have been running successfully on my systems for
months.

All I ask is for consideration of the patches I've provided, not a
criticism of choosing resolvconf over resolved.

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

[Touch-packages] [Bug 1763108] [NEW] xenial2bionic release upgrade loses DNS: empty resolv.conf

[Andreas Hasenack]

Public bug reported:

Note: I'm not sure which package better represents this bug, so I used
systemd, because /etc/resolv.conf had no "nameserver 127.0.0.53" entry
after the upgrade.


I did a plain standard lxd deploy of xenial, using the default images. Upgraded 
it to the latest xenial packages, and then issued a release upgrade to bionic.

At the end of the upgrade process, rebooted, and when the system came
back up, /etc/resolv.conf had no nameserver entries:

root@xenial2bionic:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

That was its whole content. Before the upgrade, in xenial, it had:
root@xenial2bionic:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.0.100.1
search lxd

systemd-resolve in the system after the upgrade to bionic was working just fine:
root@xenial2bionic:~# systemd-resolve --status
Global
 DNS Servers: 10.0.100.1
  DNS Domain: lxd
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 34 (eth0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Wed Apr 11 17:31:08 2018
MachineType: LENOVO 20HRCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=ZFS=nsnx/ROOT/ubuntu ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)
dmi.bios.date: 11/09/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET41W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
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.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET41W(1.26):bd11/09/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HRCTO1WW
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO

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


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

** Description changed:

- I did a plain standard lxd deploy of xenial, using the default images.
- Upgraded it to the latest xenial packages, and then issued a release
- upgrade to bionic.
+ Note: I'm not sure which package better represents this bug, so I used
+ systemd, because /etc/resolv.conf had no "nameserver 127.0.0.53" entry
+ after the upgrade.
+ 
+ 
+ I did a plain standard lxd deploy of xenial, using the default images. 
Upgraded it to the latest xenial packages, and then issued a release upgrade to 
bionic.
  
  At the end of the upgrade process, rebooted, and when the system came
  back up, /etc/resolv.conf had no nameserver entries:
  
  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
- 
  
  That was its whole content. Before the upgrade, in xenial, it had:
  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT 

[Touch-packages] [Bug 1763111] [NEW] autokey starting maximized (not in system tray)

[Duns]

Public bug reported:

It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window,
not, as expected (and as in Kubuntu 17.10) as system tray icon.

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


** Tags: autotey start system-tray window

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

Title:
  autokey starting maximized (not in system tray)

Status in xorg package in Ubuntu:
  New

Bug description:
  It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window,
  not, as expected (and as in Kubuntu 17.10) as system tray icon.

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

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

[Touch-packages] [Bug 1763108] Re: xenial2bionic release upgrade loses DNS: empty resolv.conf

[Andreas Hasenack]

Contents of /var/log of the upgraded container.

** Attachment added: "logs.tar.bz2"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1763108/+attachment/5111052/+files/logs.tar.bz2

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

Title:
  xenial2bionic release upgrade loses DNS: empty resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Note: I'm not sure which package better represents this bug, so I used
  systemd, because /etc/resolv.conf had no "nameserver 127.0.0.53" entry
  after the upgrade.

  
  I did a plain standard lxd deploy of xenial, using the default images. 
Upgraded it to the latest xenial packages, and then issued a release upgrade to 
bionic.

  At the end of the upgrade process, rebooted, and when the system came
  back up, /etc/resolv.conf had no nameserver entries:

  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  That was its whole content. Before the upgrade, in xenial, it had:
  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.0.100.1
  search lxd

  systemd-resolve in the system after the upgrade to bionic was working just 
fine:
  root@xenial2bionic:~# systemd-resolve --status
  Global
   DNS Servers: 10.0.100.1
    DNS Domain: lxd
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 34 (eth0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: no
  DNSSEC supported: no

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 11 17:31:08 2018
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=ZFS=nsnx/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)
  dmi.bios.date: 11/09/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET41W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  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.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET41W(1.26):bd11/09/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

@sil2100 please find attached an updated debdiff for protobuf. I just replaced 
this line:
TestGetAndDeserialize('optional_uint32', 1 << 31, long)

with:
TestGetAndDeserialize('optional_uint32', 1 << 31, integer_64)

as upstream already did:
https://github.com/google/protobuf/blob/master/python/google/protobuf/internal/reflection_test.py



** Patch added: "protobuf.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+attachment/5111000/+files/protobuf.debdiff

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  Fix Committed
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  Fix Committed
Status in httmock source package in Artful:
  Invalid
Status in protobuf source package in Artful:
  Invalid
Status in py-macaroon-bakery source package in Artful:
  In Progress
Status in pymacaroons source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

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

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

[Touch-packages] [Bug 1763100] [NEW] FONT="x/y/z" is not applied due to setupcon script bug

[TJ]

Public bug reported:

apt-cache policy console-setup
console-setup:
  Installed: 1.178ubuntu1
  Candidate: 1.178ubuntu1
  Version table:
 *** 1.178ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status

On 18.04 I wanted to set the TTY font to use a Powerline font. Despite
being able to set the font manually it wasn't being set at boot-time.

/etc/default/console-setup contains:

FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz"

"setupcon -v -f" reported an error:

putfont: KDFONTOP: Invalid argument

due to passing the font filename twice:

executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline-
v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz.

The problem is in /bin/setupcon where the collecting variable FONTFILES
has the font added twice, once at the top of the for loop

FONTFILES="$FONTFILES `findfile $fontdir $f`"

and again at the bottom

FONTFILES="$FONTFILES $RES"

Removing the first assignment fixes it.

FONTFILES=''
echo "DEBUG: FONT=$FONT"
if [ "$FONT" ]; then
for f in $FONT; do
  echo "DEBUG: for loop"
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi
FONTFILES=`echo $FONTFILES` # remove extra spaces

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  FONT="x/y/z" is not applied due to setupcon script bug

Status in console-setup package in Ubuntu:
  New

Bug description:
  apt-cache policy console-setup
  console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
   *** 1.178ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  On 18.04 I wanted to set the TTY font to use a Powerline font. Despite
  being able to set the font manually it wasn't being set at boot-time.

  /etc/default/console-setup contains:

  FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz"

  "setupcon -v -f" reported an error:

  putfont: KDFONTOP: Invalid argument

  due to passing the font filename twice:

  executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline-
  v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz.

  The problem is in /bin/setupcon where the collecting variable
  FONTFILES has the font added twice, once at the top of the for loop

  FONTFILES="$FONTFILES `findfile $fontdir $f`"

  and again at the bottom

  FONTFILES="$FONTFILES $RES"

  Removing the first assignment fixes it.

  FONTFILES=''
  echo "DEBUG: FONT=$FONT"
  if [ "$FONT" ]; then
  for f in $FONT; do
echo "DEBUG: for loop"
  FONTFILES="$FONTFILES `findfile $fontdir $f`"
  RES=`findfile $fontdir $f`
  if [ -z "$RES" ]; then
  fdec="${f%.gz}"
  RES=`findfile $fontdir $fdec`
  fi
  FONTFILES="$FONTFILES $RES"
  done
  fi
  FONTFILES=`echo $FONTFILES` # remove extra spaces

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

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

[Touch-packages] [Bug 1203718] Re: hud-service is consuming too much recources

[Stephen A. Goss]

This appears to be a problem in Ubuntu 16.04, where hud-service is
taking up 2.4 GB of RAM after 27 days on my system.

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

Title:
  hud-service is consuming too much recources

Status in Unity HUD:
  New
Status in hud package in Ubuntu:
  Confirmed

Bug description:
  For a couple of days now (I assume since recent Unity updates), my Laptop is 
performing more an more poor throughout the day. First 2-3 hours Unity is 
running smoothly (Dash, HUD, etc.) Afterwards, opening Dash or HUD and even 
switching workspaces and starting applications becomes very slow. Sometimes I 
have to restart lightdm from a tty-console or reboot.
  Running "top" in a terminal shows that a process called "hud-service" is 
consuming up to 60% of CPU and RAM resources.

  My hardware should be perfectly able to cope with 13.04 (Dell Latitude
  E5420, quad-core, 8GB RAM) and was until about two weeks before.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Jul 22 13:49:15 2013
  InstallationDate: Installed on 2013-04-25 (87 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713149] Re: resolv.conf symlink is broken after clean debootstrap

[Frank Burkhardt]

Hi,

(installing Bionic here)

a possible solution is to make sure, /target/run is already mounted
(bind-mount to /run) when debootstrap is running which will make systemd
create its resolv.conf copy in the correct /run-filesystem. Otherwise,
it would write to the /target-partition and in-target would hide the
stuff in there when doint its bind-mounts.

For now I create (and make executable) the script /usr/lib/base-
installer.d/41init-run via early_command:

#!/bin/sh
mkdir -p /target/run
mount --bind /run /target/run

IMHO this should be done by the base-installer.

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

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to 
"../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that 
points to /run/run/systemd/resolve/stub-resolv.conf" rather than 
"/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

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

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

[Touch-packages] [Bug 1748095] Re: Non-root user can reboot machine from the command line

[Dimitri John Ledkov]

reboot command is SysV-init compatibility command and is specified as
non-interactive.

Why are you typing reboot? seriously this is not something desktop users
typically do, at all =)

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

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

Status in systemd package in Ubuntu:
  Opinion

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

[Dimitri John Ledkov]

May I backtrack a bit, and ask how is this system configured? And is it
a desktop or a server configuration? Is it a fresh install or an
upgrade?

Specifically, what I am confused about is how the networking is
configured and where /etc/resolv.conf is pointing at.

I see that NetworkManager and ifupdown were mentioned. Do you have both
of these configured and try to manage a) networking b) /etc/resolv.conf?

And what are the steps to reproduce this? Ideally with something simple
and reproducible like a lxd container launched with $ lxd launch ubuntu-
daily:artful test-container

Note that overriding make_resolv_conf() is a good thing, and it should
not at all be used. None of our network configuration tools rely on
make_resolv_conf() which is an extremely bad interface that writes out a
static file and looses information, as it assumes that there is only
ever one interface and one dhcp. Hence you will notice that everything
(networkd+resolved, ifupdown+resolvconf, networkmanager) overridee
make_resolv_conf.

I'm not quite sure what was done to your system, but resolvconf can be
used to managed the /etc/resolv.conf and that is integrated with
resolved. You will notice that resolved stub nameserver is pulled into
resolvconf config, and thus resolvconf can own /etc/resolv.conf which is
what happens on upgrades.

Please update the bug description on how to reproduce the problem you
are seeing, without ranting or jumping to conclusions, or trying to make
any unnecessary changes, because it is hard to understand what you are
trying to achieve, which may have been made worse with unnecessary
workarounds.

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

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

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

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

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

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

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1762304
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

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

Status in avahi package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr 11 12:00:23 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-06-06 (673 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2.1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[Łukasz Zemczak]

Hello bugproxy, or anyone else affected,

Accepted kmod into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/kmod/15-0ubuntu7 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed verification-needed-trusty

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Trusty:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+subscriptions

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

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

[Jolexin]

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

Public bug reported:

none

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Apr 11 12:00:23 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-06-06 (673 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2.1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

Status in avahi package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr 11 12:00:23 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-06-06 (673 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2.1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762386] Re: [FFe] Add networkd-dispatcher

[Dimitri John Ledkov]

** Package changed: ubuntu => networkd-dispatcher (Ubuntu)

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

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

** Changed in: networkd-dispatcher (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFe] Add networkd-dispatcher

Status in networkd-dispatcher package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  In order to be able to have hooks for systems running systemd-networkd
  (see bug 1718227), we need to add networkd-dispatcher. The package is
  ready at

  https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/networkd-
  dispatcher

  Once it's in we can change systemd to pull it in on systems as
  specified in the other bug.

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

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

[Touch-packages] [Bug 1635804] Re: short cut keys always showing

[Sebastien Bacher]

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

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

Title:
  short cut keys always showing

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

Bug description:
  as of 16.10 the shortcut keys are always showing in the right click
  menu. This is ugly and un-needed as there is a list of shortcut keys
  already available from the menu bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 22 19:17:35 2016
  InstallationDate: Installed on 2016-10-14 (8 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1762911] Re: crontab -l return 1 in absence of /var/spool/cron/crontabs/user

[Brian Murray]

** Project changed: apport => cron (Ubuntu)

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

Title:
  crontab -l return 1 in absence of /var/spool/cron/crontabs/user

Status in cron package in Ubuntu:
  New

Bug description:
  i guess it is rather a feature than a bug
  but it doesnot feel right
  $ crontab -l
  got "no crontab for $user" from stderr and a return code of 1
  if the file /var/spool/cron/crontabs/$user does not exist
  but if the file exists and is empty code 0 is returned
  by default that file does not exist so i think the error code doesn't make 
sense
  if "1" means error, the system should have that file created while creating 
user
  if "1" means not found, 1 should be returned when no jobs are found in the 
file

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

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

[Touch-packages] [Bug 1762911] [NEW] crontab -l return 1 in absence of /var/spool/cron/crontabs/user

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

i guess it is rather a feature than a bug
but it doesnot feel right
$ crontab -l
got "no crontab for $user" from stderr and a return code of 1
if the file /var/spool/cron/crontabs/$user does not exist
but if the file exists and is empty code 0 is returned
by default that file does not exist so i think the error code doesn't make sense
if "1" means error, the system should have that file created while creating user
if "1" means not found, 1 should be returned when no jobs are found in the file

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

-- 
crontab -l return 1 in absence of /var/spool/cron/crontabs/user
https://bugs.launchpad.net/bugs/1762911
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cron 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 1635804] Re: short cut keys always showing

[Ads20000]

Upstream said in the upstream bug that it's a bug in GTK.

'there is a list of shortcut keys already available from the menu bar'
this is not true because Files (in GNOME, at least) uses CSD? Perhaps
this should be closed here and upstream as Won't Fix?

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=773929
   Importance: Unknown
   Status: Unknown

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

Title:
  short cut keys always showing

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

Bug description:
  as of 16.10 the shortcut keys are always showing in the right click
  menu. This is ugly and un-needed as there is a list of shortcut keys
  already available from the menu bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 22 19:17:35 2016
  InstallationDate: Installed on 2016-10-14 (8 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

-- 
Mailing list: https://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 1761763] Re: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gary Caine]

I replied on launchpad but in answer to your 2 questions.

I did the fix broken pages from advanced options from grub, and I'm 
pretty sure that this is what caused it.

 From dbus status

  dbus.service - D-Bus System Message Bus
    Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor 
preset: enab
    Active: active (running) since Wed 2018-04-11 07:53:20 CST; 5min ago
  Docs: man:dbus-daemon(1)
  Main PID: 733 (dbus-daemon)
     Tasks: 1 (limit: 4915)
    CGroup: /system.slice/dbus.service
    └─733 /usr/bin/dbus-daemon --system --address=systemd: 
--nofork --nop

Apr 11 07:53:52 gary-System-Product-Name dbus[733]: [system] 
Successfully activa
Apr 11 07:53:55 gary-System-Product-Name dbus[733]: [system] Failed to 
activate
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system] Activating 
via syst
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system] 
Successfully activa
Apr 11 07:54:09 gary-System-Product-Name dbus[733]: [system] Activating 
via syst
Apr 11 07:54:34 gary-System-Product-Name dbus[733]: [system] Failed to 
activate
Apr 11 07:57:18 gary-System-Product-Name dbus[733]: [system] Activating 
via syst
Apr 11 07:57:43 gary-System-Product-Name dbus[733]: [system] Failed to 
activate
Apr 11 07:58:23 gary-System-Product-Name dbus[733]: [system] Activating 
via syst
Apr 11 07:58:48 gary-System-Product-Name dbus[733]: [system] Failed to 
activate


On 2018-04-11 06:39 AM, Trent Lloyd wrote:
> Looking at your logs, generally it seems like dbus is broken for some
> reason.
>
> Would also be great to check it's status:
> # systemctl status dbus
>

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

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

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  This is using 17.10 so I believe it is different than the 1633217 bug
  report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 08:18:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-06  08:18:02
   Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-07 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Mario Limonciello]

@xnox in order to coordinate the systemd upload in case you have
anything in flight, here's a debdiff:

** Patch added: "backported fix from upstream"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1760106/+attachment/5110809/+files/systemd-offsets.debdiff

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

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

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

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

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

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

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

[Touch-packages] [Bug 1761763] Re: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gary Caine]

This happened when I did fix broken packages after going into advanced
option from grub

here's the output of dbus

 dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enab
   Active: active (running) since Wed 2018-04-11 07:53:20 CST; 5min ago
 Docs: man:dbus-daemon(1)
 Main PID: 733 (dbus-daemon)
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/dbus.service
   └─733 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nop

Apr 11 07:53:52 gary-System-Product-Name dbus[733]: [system] Successfully activa
Apr 11 07:53:55 gary-System-Product-Name dbus[733]: [system] Failed to activate 
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system] Successfully activa
Apr 11 07:54:09 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:54:34 gary-System-Product-Name dbus[733]: [system] Failed to activate 
Apr 11 07:57:18 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:57:43 gary-System-Product-Name dbus[733]: [system] Failed to activate 
Apr 11 07:58:23 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:58:48 gary-System-Product-Name dbus[733]: [system] Failed to activate

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

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

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  This is using 17.10 so I believe it is different than the 1633217 bug
  report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 08:18:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-06  08:18:02
   Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-07 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1635804] [NEW] short cut keys always showing

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

as of 16.10 the shortcut keys are always showing in the right click
menu. This is ugly and un-needed as there is a list of shortcut keys
already available from the menu bar.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 22 19:17:35 2016
InstallationDate: Installed on 2016-10-14 (8 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug third-party-packages yakkety
-- 
short cut keys always showing
https://bugs.launchpad.net/bugs/1635804
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

[Tom Verdaat]

@ddstreet I opened a separate ticket as requested a while ago. Some eyes
on it would be very welcome. It's bug 1759573

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 26 06:32:57 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.networking.conf: [modified]
  mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927

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

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

[Touch-packages] [Bug 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[Andy Whitcroft]

** Changed in: kmod (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: kmod (Ubuntu Trusty)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Trusty:
  In Progress
Status in kmod source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+subscriptions

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

[Touch-packages] [Bug 1763019] Re: systemd-journald crashed with SIGABRT in fsync()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in fsync()

Status in systemd package in Ubuntu:
  New

Bug description:
  System was upgrading after beta install

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 11 14:51:25 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-04-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407)
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3e9f0606-7a57-4522-9f1f-cb143a1d61b1 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   fsync (fd=17) at ../sysdeps/unix/sysv/linux/fsync.c:27
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in fsync()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.vendor: LENOVO
  dmi.product.version: ThinkCentre M58

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

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

[Touch-packages] [Bug 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[Andy Whitcroft]

** Also affects: kmod (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Trusty:
  In Progress
Status in kmod source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+subscriptions

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

[Touch-packages] [Bug 1761763] Re: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Trent Lloyd]

Looking at your logs, generally it seems like dbus is broken for some
reason.

Would also be great to check it's status:
# systemctl status dbus

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

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

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  This is using 17.10 so I believe it is different than the 1633217 bug
  report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 08:18:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-06  08:18:02
   Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-07 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761763] Re: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Trent Lloyd]

Thanks for the report.

 How did this happen, was it during a package upgrade for a normal
installation or is this a new install, etc.  If a new install, describe
which install media download and options you used. Or were you
installing avahi-daemon or some other package using apt install, etc.

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

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

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  This is using 17.10 so I believe it is different than the 1633217 bug
  report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 08:18:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-06  08:18:02
   Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-07 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762983] Re: communitheme snap doesn't work with evince

[Launchpad Bug Tracker]

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

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

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

Title:
  communitheme snap doesn't work with evince

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  As mentioned on https://github.com/ubuntu/gtk-
  communitheme/issues/325#issuecomment-380383969, evince can't load the
  communitheme snap.

  Indeed, as the directory isn't a standard one (/snap/…), the protected
  applications by apparmor can't load it.

  As the snap is temporary, distro-patch (ubuntu only) common
  abstractions directory for theme and icons (similar than the flatpak
  patches).

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

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

[Touch-packages] [Bug 1763004] Re: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem

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

Title:
  package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libhybris package in Ubuntu:
  New

Bug description:
  error occur after loging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr 11 20:00:45 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7
  DpkgHistoryLog:
   Start-Date: 2018-04-11  20:00:37
   Commandline: apt-get install gparted
   Requested-By: lsl2017 (1000)
   Install: libparted-fs-resize0:amd64 (3.2-15ubuntu0.1, automatic), 
libgtkmm-2.4-1v5:amd64 (1:2.24.4-2, automatic), gparted:amd64 (0.25.0-1)
   Upgrade: libparted2:amd64 (3.2-15, 3.2-15ubuntu0.1), parted:amd64 (3.2-15, 
3.2-15ubuntu0.1)
  DuplicateSignature:
   package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libhardware2 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-26 (75 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: libhybris
  Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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/libhybris/+bug/1763004/+subscriptions

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

[Touch-packages] [Bug 1763004] [NEW] package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

[LSL2014]

Public bug reported:

error occur after loging in

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Apr 11 20:00:45 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7
DpkgHistoryLog:
 Start-Date: 2018-04-11  20:00:37
 Commandline: apt-get install gparted
 Requested-By: lsl2017 (1000)
 Install: libparted-fs-resize0:amd64 (3.2-15ubuntu0.1, automatic), 
libgtkmm-2.4-1v5:amd64 (1:2.24.4-2, automatic), gparted:amd64 (0.25.0-1)
 Upgrade: libparted2:amd64 (3.2-15, 3.2-15ubuntu0.1), parted:amd64 (3.2-15, 
3.2-15ubuntu0.1)
DuplicateSignature:
 package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package libhardware2 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-01-26 (75 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: libhybris
Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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: libhybris (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libhybris package in Ubuntu:
  New

Bug description:
  error occur after loging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr 11 20:00:45 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7
  DpkgHistoryLog:
   Start-Date: 2018-04-11  20:00:37
   Commandline: apt-get install gparted
   Requested-By: lsl2017 (1000)
   Install: libparted-fs-resize0:amd64 (3.2-15ubuntu0.1, automatic), 
libgtkmm-2.4-1v5:amd64 (1:2.24.4-2, automatic), gparted:amd64 (0.25.0-1)
   Upgrade: libparted2:amd64 (3.2-15, 3.2-15ubuntu0.1), parted:amd64 (3.2-15, 
3.2-15ubuntu0.1)
  DuplicateSignature:
   package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libhardware2 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-26 (75 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: libhybris
  Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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/libhybris/+bug/1763004/+subscriptions

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

[Amr Ibrahim]

I am also having stutter videos in Totem in Bionic. I am using old
hardware from 2011. I am ready to give more debugging info when needed.

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761763] Re: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

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

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  This is using 17.10 so I believe it is different than the 1633217 bug
  report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 08:18:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-06  08:18:02
   Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-07 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762996] [NEW] network-manager sets proprietary driver as default, which breaks wifi

[patslap]

Public bug reported:

Fresh install of 18.04 Beta final on HP Pavilion G6 laptop.


Selected 'install proprietary drivers and codecs' during installation.

Wifi worked on first boot.

Performed apt update && apt upgrade.

On second boot after updates, wifi will not connect. Tried three
separate access points, to no avail.

Workaround was to disable proprietary driver.

Submitted as bug, as new user would struggle. network-manager should not
set a non-working wifi driver as default.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 11 11:45:44 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-04-11 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
IpRoute:
 default via 192.168.0.1 dev wlp1s0b1 proto dhcp metric 600 
 192.168.0.0/24 dev wlp1s0b1 proto kernel scope link src 192.168.0.31 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICETYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp1s0b1  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
VM7710976   178e1867-9364-4de8-a595-91f81268dbc7  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 eno1  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
 loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  network-manager sets proprietary driver as default, which breaks wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  Fresh install of 18.04 Beta final on HP Pavilion G6 laptop.

  
  Selected 'install proprietary drivers and codecs' during installation.

  Wifi worked on first boot.

  Performed apt update && apt upgrade.

  On second boot after updates, wifi will not connect. Tried three
  separate access points, to no avail.

  Workaround was to disable proprietary driver.

  Submitted as bug, as new user would struggle. network-manager should
  not set a non-working wifi driver as default.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 11:45:44 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 192.168.0.1 dev wlp1s0b1 proto dhcp metric 600 
   192.168.0.0/24 dev wlp1s0b1 proto kernel scope link src 192.168.0.31 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp1s0b1  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
VM7710976   178e1867-9364-4de8-a595-91f81268dbc7  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   eno1  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  --   

[Touch-packages] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed

[Graham Leggett]

In our case it burned a number of days of dev time, so this is
definitely causing pain.

We've never seen this before because until docker, we have not
encountered a system where apt-transport-https wasn't installed by
default.

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

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

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

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

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

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

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

  Key notes:

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

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

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

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

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

[Touch-packages] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed

[Julian Andres Klode]

Or rather, I'm not sure it's worth it. I plan to look at other fixes in
1.6 soon, and see which of these we need for stable series.

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

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

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

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

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

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

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

  Key notes:

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

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

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

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

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

[Touch-packages] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed

[Julian Andres Klode]

I think so, but I don't think it's worth pushing out an update just for
that change. It's been broken since forever, so it's not like it's
fixing a regression or something; so I'd probably wait for something
else to attach it to.

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

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

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

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

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

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

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

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

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

  Key notes:

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

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

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

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

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

[Daniel van Vugt]

I'm really not sure what changed to make 4K video so stuttery now in
totem. The CPU is fairly low and goes through the roof only if I
uninstall VAAPI. So VAAPI is working, and it works smoothly in mpv too.

Since I could last play 4K smoothly in totem there has been:
  * A mesa update 17.2 -> 18.0
  * A Xorg update 1.19.5 -> 1.19.6
  * Kernel updates
  * Hardware changes (I changed from a Haswell to Kaby Lake desktop)

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed

[Graham Leggett]

Is it possible to backport this to trusty too? This bit us hard, and
there are a lot of people out there posting this problem but with no
solution.

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

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

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

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

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

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

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

  Key notes:

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

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

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

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

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

[Touch-packages] [Bug 1762983] Re: communitheme snap doesn't work with evince

[Didier Roche]

Submitted as https://salsa.debian.org/apparmor-
team/apparmor/merge_requests/5.

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

Title:
  communitheme snap doesn't work with evince

Status in apparmor package in Ubuntu:
  New

Bug description:
  As mentioned on https://github.com/ubuntu/gtk-
  communitheme/issues/325#issuecomment-380383969, evince can't load the
  communitheme snap.

  Indeed, as the directory isn't a standard one (/snap/…), the protected
  applications by apparmor can't load it.

  As the snap is temporary, distro-patch (ubuntu only) common
  abstractions directory for theme and icons (similar than the flatpak
  patches).

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[Launchpad Bug Tracker]

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

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

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 1762983] [NEW] communitheme snap doesn't work with evince

[Didier Roche]

Public bug reported:

As mentioned on https://github.com/ubuntu/gtk-
communitheme/issues/325#issuecomment-380383969, evince can't load the
communitheme snap.

Indeed, as the directory isn't a standard one (/snap/…), the protected
applications by apparmor can't load it.

As the snap is temporary, distro-patch (ubuntu only) common abstractions
directory for theme and icons (similar than the flatpak patches).

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

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

Title:
  communitheme snap doesn't work with evince

Status in apparmor package in Ubuntu:
  New

Bug description:
  As mentioned on https://github.com/ubuntu/gtk-
  communitheme/issues/325#issuecomment-380383969, evince can't load the
  communitheme snap.

  Indeed, as the directory isn't a standard one (/snap/…), the protected
  applications by apparmor can't load it.

  As the snap is temporary, distro-patch (ubuntu only) common
  abstractions directory for theme and icons (similar than the flatpak
  patches).

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

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

[Touch-packages] [Bug 1762984] [NEW] DNS resolving not working due to wrong entry in resolv.conf

[thet]

Public bug reported:

In my ``/etc/resolv.conf`` I have the entry:

```
nameserver 127.0.0.53
```

I'm connected to the network via WIFI.
My IP is ``192.168.0.31``

The network-manager applet shows me automatic DNS configuration and a DNS 
server of 192.0.0.1, which is correct.
Changing DNS configuration in the network-manager applet to manual and editing 
it there doesn't work either.

I have to edit the resolv.conf file in order to get DNS resolving work.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 11 11:51:58 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-04-09 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
IpRoute:
 default via 192.168.0.1 dev wlp1s0 proto dhcp metric 20600 
 169.254.0.0/16 dev wlp1s0 scope link metric 1000 
 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.31 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  wifi  1523440039  Mi 11 Apr 
2018 11:47:19 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp1s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
 welanseppaf2f9fd1-2a81-4e2c-95e5-3f4e9a9997b9  wifi  1523402504  Mi 11 Apr 
2018 01:21:44 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
 running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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


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

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

Title:
  DNS resolving not working due to wrong entry in resolv.conf

Status in network-manager package in Ubuntu:
  New

Bug description:
  In my ``/etc/resolv.conf`` I have the entry:

  ```
  nameserver 127.0.0.53
  ```

  I'm connected to the network via WIFI.
  My IP is ``192.168.0.31``

  The network-manager applet shows me automatic DNS configuration and a DNS 
server of 192.0.0.1, which is correct.
  Changing DNS configuration in the network-manager applet to manual and 
editing it there doesn't work either.

  I have to edit the resolv.conf file in order to get DNS resolving
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 11:51:58 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 192.168.0.1 dev wlp1s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.31 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  

[Touch-packages] [Bug 1762212] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: el subproceso script pre-removal nuevo devolvió el
  código de salida de error 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Error ocurred while upgrading system.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sun Apr  8 17:57:54 2018
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2017-12-31 (98 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 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/1762212/+subscriptions

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

[Touch-packages] [Bug 1762978] [NEW] ksmserver-logout-greeter crashes on logout preventing me from logging out

[Hamish Farrant]

Public bug reported:

Running on the live-usb version of kubuntu 17.10.1 on a dell precision
5520


Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: 
Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3ac23d1000 (LWP 11971))]

Thread 3 (Thread 0x7f3aa35e1700 (LWP 11974)):
#0  0x7f3abdc8706d in __GI___libc_read (fd=7, buf=0x7f3aa35e0a20, 
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f3ab3ae7073 in ?? () from 
/usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111
#2  0x7f3ab6b04280 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3ab6abfc4b in g_main_context_check () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3ab6ac0110 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f3ab6ac027c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f3abe5cb49b in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3abe570e3a in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3abe3903ca in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f3abf1aee45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7f3abe39529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f3ab88457fc in start_thread (arg=0x7f3aa35e1700) at 
pthread_create.c:465
#12 0x7f3abdc97b5f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3aa8c79700 (LWP 11973)):
#0  0x7f3abdc8b951 in __GI___poll (fds=0x7f3a9c004e60, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3ab6ac0169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3ab6ac027c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3abe5cb49b in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3abe570e3a in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3abe3903ca in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3ac05ebf45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f3abe39529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3ab88457fc in start_thread (arg=0x7f3aa8c79700) at 
pthread_create.c:465
#9  0x7f3abdc97b5f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3ac23d1000 (LWP 11971)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#5  0x7f3abdbbbf5d in __GI_abort () at abort.c:90
#6  0x7f3abe380107 in QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3ac0cb8787 in 
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f3ac0cb9755 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7f3ac0cba37a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7f3abeb3dd35 in QWindow::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x7f3ac0d2dd05 in QQuickWindow::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x55c454797fd1 in ?? ()
#13 0x7f3abf77b46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f3abf782d34 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f3abe572de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f3abeb32e5f in 
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
 () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x7f3abeb33a9d in 
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
 () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x7f3abeb0bcab in 
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
 () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x7f3aaccbb5a0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#20 0x7f3ab6abffb7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f3ab6ac01f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f3ab6ac027c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f3abe5cb47f in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f3abe570e3a in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f3abe579da4 in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x55c454795122 in ?? ()
#27 

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Horst Schirmeier]

Additional side effect: Bionic sometimes fails to come back from S3 and
stays frozen with a black screen.

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

[John Johansen]

So I have been looking at this again, and have found a couple issues.

1. Where prlimit is concerned. AppArmor adds an addition restriction on
when cap sys_resource is required. The CAP_SYS_RESOURCE capability is
required if the target processes label does not match that of the
caller.

Hence why libvirtd requires
  capability sys_resource,

in its profile.


The apparmor check should be broken down further as other ipc checks, but that 
should not have an effect here based on the peer= field. For the 
cap_sys_resource check the profile does not need an rlimit rule.


2. if stacking is used the denial message could be misleading as a denied 
message will be generated for each profile in the stack even if it was not a 
profile causing the denial.

In this case we should see duplicates of the above denial except with
the profile= field changing. So one with libvurtd and another with some
other process. With the currently available information this does not
seem to be the problem.


3. The rawdata for the libvirtd profile does show the profile has 
CAP_SYS_RESOURCE permissions


4. It is the CAP_SYS_RESOURCE check that is failing. This check will only be 
triggered when using prlimit with a target having a different confinement than 
the setting task.  Which is exactly what we see in the audit message.

There is a logic inversion bug in this path.

I have a test kernel building and will update when its ready

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in The Ubuntu-power-systems project:
  In Progress
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1679704/+subscriptions

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

[Touch-packages] [Bug 1762961] Re: Screen corruption

[Hamish Farrant]

When I switched it to XRender the corruption completely stopped

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

Title:
  Screen corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  By default, kubuntu uses the OpenGL for the rendering backend (2.0 or
  3.1) when it was in these modes, it'd show forms of screen corruption

  for example a loading bar might flicker between a longer and a shorter bar
  or a combo box would seemingly not respond, and then suddenly do something 
unexpected
  text entered would vanish then reappear

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CompositorRunning: None
  Date: Wed Apr 11 18:40:36 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07bf]
 Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
  LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1762961] [NEW] Screen corruption

[Hamish Farrant]

Public bug reported:

By default, kubuntu uses the OpenGL for the rendering backend (2.0 or
3.1) when it was in these modes, it'd show forms of screen corruption

for example a loading bar might flicker between a longer and a shorter bar
or a combo box would seemingly not respond, and then suddenly do something 
unexpected
text entered would vanish then reappear

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CasperVersion: 1.387
CompositorRunning: None
Date: Wed Apr 11 18:40:36 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07bf]
   Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)
MachineType: Dell Inc. Precision 5520
ProcEnviron:
 LANGUAGE=
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Screen corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  By default, kubuntu uses the OpenGL for the rendering backend (2.0 or
  3.1) when it was in these modes, it'd show forms of screen corruption

  for example a loading bar might flicker between a longer and a shorter bar
  or a combo box would seemingly not respond, and then suddenly do something 
unexpected
  text entered would vanish then reappear

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CompositorRunning: None
  Date: Wed Apr 11 18:40:36 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07bf]
 Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
  LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  

[Touch-packages] [Bug 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

[Olivier Tilloy]

I successfully tested ibus 1.5.11-1ubuntu2.1 from xenial-proposed,
following the test case in the bug description:

I installed the chromium snap from the stable channel (version
65.0.3325.181, revision 274) and monitor the system journal for apparmor
denials while launching it:

journalctl -f | grep chmod

I observed a denial similar to that one:

audit[16919]: AVC apparmor="DENIED" operation="chmod"
profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
fsuid=1000 ouid=1000

I then rebuilt and installed the snap with libibus-1.0-5 and ibus-gtk3
from xenial-proposed (version 1.5.11-1ubuntu2.1):

cd /tmp
cp /var/lib/snapd/snaps/chromium_274.snap ./
unsquashfs chromium_274.snap
wget 
https://launchpadlibrarian.net/364009842/libibus-1.0-5_1.5.11-1ubuntu2.1_amd64.deb
wget 
https://launchpadlibrarian.net/364009838/ibus-gtk3_1.5.11-1ubuntu2.1_amd64.deb
dpkg -x ibus-gtk3_1.5.11-1ubuntu2.1_amd64.deb squashfs-root/
dpkg -x libibus-1.0-5_1.5.11-1ubuntu2.1_amd64.deb squashfs-root/
snapcraft pack squashfs-root
snap remove chromium
snap install --dangerous chromium_65.0.3325.181_amd64.snap
snap connect chromium:browser-sandbox


I launched it again while monitoring the system journal, and observed that the 
chmod denial was gone.

I also verified that ibus input still works in the snap (tested with
ibus-cangjie for traditional Chinese).

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

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Xenial:
  Fix Committed

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This is rather harmless, but it could be avoided by checking first the
  file mode bits on that directory, and do the g_chmod call only if ≠
  0700.

  
  [Impact]

  Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
  The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.

  
  [Test Case]

  Install the chromium snap from the stable channel (version
  65.0.3325.181, revision 274 as of this writing), and monitor the
  system journal for apparmor denials while launching it:

  journalctl -f | grep chmod

  Observe a denial similar to that one:

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  Now rebuild the chromium snap with the patched libibus (this can be
  done by downloading the .snap file, unpacking it with  unsquashfs,
  replacing the libibus files by unpacking the updated deb, then
  repacking the snap with `snapcraft pack`), install it and launch it
  while monitoring the system journal.

  Observe the denial on chmod is gone.

  
  [Regression Potential]

  This is a low-risk, self-contained change. It doesn't change the logic of 
ibus_bus_init.
  ibus input still working in apps (both debs and snaps) should be enough to 
prove that there are no regressions.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days 

[Touch-packages] [Bug 1697377] Re: Change TextBoxes Direction for RTL languages

[Reza-irdev]

Okay, Thank you for your response. I’ll submit the issue on that site.
But i cant find any member with the name you mentioned.

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

Title:
  Change TextBoxes  Direction for RTL languages

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  My and all RTL language users problem is that there us no option to
  change text direction in a text-box! for example in windows when i
  press left CTRL+SHIFT text direction sets to LTR and when press right
  CTRL+SHIFT direction changes to RTL. It is a really big problem for us
  and its a essential feature. Also automatic direction detection base
  on language direction is not good solution at all.

  From: https://support.microsoft.com/en-us/help/12445/windows-keyboard-
  shortcuts

  Ctrl + Shift = Switch the keyboard layout when multiple keyboard
  layouts are available.

  
  See: 
https://blogs.technet.microsoft.com/office_global_experience/2010/02/19/useful-tricks-and-shortcuts-for-users-around-the-world/

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

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

[Touch-packages] [Bug 1762923] Re: jackd2 required libreadline6 to install

[Julian Andres Klode]

The jackd we ship in Ubuntu is built against the correct libreadline
version. You have to contact your third party repository provider for
support with that.

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

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

Title:
  jackd2 required libreadline6 to install

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Tried to install jackd2 with kxstudio repository package but it
  depended on libreadline6 and wouldn't accept libreadline7 which was
  installed, so I installed libreadline6 from a debian deb i found
  online and it allowed me to install it correctly.

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

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

[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

[ChristianEhrhardt]

** Tags added: bionic

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

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

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

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

[Touch-packages] [Bug 1762945] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Status in systemd package in Ubuntu:
  New

Bug description:
  18.04 Beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Apr 10 22:31:17 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-02-07 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_ZM
   LANGUAGE=en_ZM:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=139819346732800, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1697377] Re: Change TextBoxes Direction for RTL languages

[Shlomil]

Hi Reza,
Issues regarding GTK should be reported in the upstream issue tracker. Which 
seems to be:
https://gitlab.gnome.org/GNOME/gtk/issues
Maybe you should first have a chat with Behdad Esfahbod regarding this issue.
Good luck!

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

Title:
  Change TextBoxes  Direction for RTL languages

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  My and all RTL language users problem is that there us no option to
  change text direction in a text-box! for example in windows when i
  press left CTRL+SHIFT text direction sets to LTR and when press right
  CTRL+SHIFT direction changes to RTL. It is a really big problem for us
  and its a essential feature. Also automatic direction detection base
  on language direction is not good solution at all.

  From: https://support.microsoft.com/en-us/help/12445/windows-keyboard-
  shortcuts

  Ctrl + Shift = Switch the keyboard layout when multiple keyboard
  layouts are available.

  
  See: 
https://blogs.technet.microsoft.com/office_global_experience/2010/02/19/useful-tricks-and-shortcuts-for-users-around-the-world/

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

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

[Touch-packages] [Bug 1762551] Re: Scroll bar in Firefox is very thin and does not widen when hovered

[Amr Ibrahim]

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

After more investigation, it turns out that there are two different
bugs.

One in FF 46 (bug #1575896) was about an invisible scroll bar, which got
fixed in a later version. The other newer bug started in FF 52, which is
currently about a very thin scroll bar that regressed in 52 and later
(see the screenshots in bug #1675496).

I have changed the duplicates accordingly.

** This bug is no longer a duplicate of bug 1575896
   Scrollbar thumb not drawn in Firefox 46 and later (gtk3?)
** This bug has been marked a duplicate of bug 1675496
   Scrollbars are tiny in Firefox (since FF 52)

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

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

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

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

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

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

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

[Touch-packages] [Bug 1647943] Re: guest session leaves cruft behind

[Gunnar Hjalmarsson]

Please see .

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

Title:
  guest session leaves cruft behind

Status in lightdm package in Ubuntu:
  New

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

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

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

  Other files seem to be affected as well.

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

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

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

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

[Touch-packages] [Bug 1762923] [NEW] jackd2 required libreadline6 to install

[Fred-bertram]

Public bug reported:

Tried to install jackd2 with kxstudio repository package but it depended
on libreadline6 and wouldn't accept libreadline7 which was installed, so
I installed libreadline6 from a debian deb i found online and it allowed
me to install it correctly.

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

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

Title:
  jackd2 required libreadline6 to install

Status in apt package in Ubuntu:
  New

Bug description:
  Tried to install jackd2 with kxstudio repository package but it
  depended on libreadline6 and wouldn't accept libreadline7 which was
  installed, so I installed libreadline6 from a debian deb i found
  online and it allowed me to install it correctly.

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

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

[Touch-packages] [Bug 1762921] [NEW] xorg

[Steve]

Public bug reported:

xorg failure at start up and crashes at times

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-35-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Wed Apr 11 02:13:59 2018
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2018-02-17 (52 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  xorg failure at start up and crashes at times

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Wed Apr 11 02:13:59 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (52 days ago)

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

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