[Touch-packages] [Bug 1699637] Re: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

[Yovan Zhuo Jiawan]

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

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

Title:
  g_object_unref: assertion 'G_IS_OBJECT (object)' failed

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

Bug description:
  lightdm work fine with xfce4(arch linux),but when i check it's status
  by systemd,it show this message.

  Jun 21 15:55:38 archlinux systemd[1]: Starting Light Display Manager...
  Jun 21 15:55:38 archlinux systemd[1]: Started Light Display Manager.
  Jun 21 15:55:38 archlinux lightdm[417]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  Jun 21 15:55:38 archlinux lightdm[465]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid
  Jun 21 15:55:47 archlinux lightdm[417]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  Jun 21 15:55:47 archlinux lightdm[607]: pam_unix(lightdm:session): session 
opened for user jaken by (uid=0)
  Jun 21 17:58:33 archlinux lightdm[417]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Khurshid Alam]

There is also this bug 1683383, not sure if it is related. But lots key
shortcuts problems started to arrive after Ubuntu removed 6 year old
patch from xorg.

For me, Ctrl+Alt+T works fine though. Only Alt++Fn+Print-screen doesn't
work.

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

** Tags added: libvirt-18.04

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL

[Caleb Martin]

Where is this fixed? do-release-upgrade still fails with the same error
in WSL and breaks it.

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

Title:
  do-release-upgrade broke WSL

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  New

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2

[quakeglen]

I just installed Ubuntu Mate 16.04 and kernel 4.12, it gives me the best
results so far:

- Internal audio: no sound, detected as bytcht-nocodec 1 ouput/1 input
- HDMI audio: works fine, tested with chrome and rhythmbox
- HDMI video: works fine
- Touchscreen: simple touch only, for example: on web pages can scroll, but on 
text editors select text instead of scroll
- Card Reader: not mounted automatically on startup, unless lock session and 
session restarts, sd mounts automatically, sometimes gives error, but still 
mounts
- Battery icon: works fine
- Bluethooth: seems to work fine, detects devices
- Lock button: not working
- Start button: not working
- up/down volume: not working
- wifi: some times get stuck, but in general works great
- camera: tried webcamoid, but doesn't start. Cheese says device not found.

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[bodhi.zazen]

Phillip:

You were banned from the Ubuntu Forms not by me personally, but rather
by the Forums Council after repeated violations of the CoC and difficult
interactions with the Forums Staff including both moderators and Forums
Council Members.

You appealed your ban to the Community Council, and your ban was upheld.

This is not the appropriate place to protest you ban. I am no longer an
active staff member, please contact the current Forums Council if you
wish to discuss any potential future use of the Forums

https://wiki.ubuntu.com/ForumCouncil

As far as the technical discussion I am afraid we will have to agree to
disagree.

I can not always follow what you are saying, but I have the impression,
perhaps falsely, you do not understand or that you intermingle issues of
Wayland, X (XWayland, Xhost), and Weston, those are fairly diverse
features / functions.

At any rate, I also think you do not understand that Wayland is in rapid
development and not all the mechanisms of security have been agreed on
up stream or resolved.

I believe Upstream has made their security intentions very clear in
their mailing list and security blog, which I have provided for your
consideration.

The fedora experience makes this very clear in their bug reports as
well. The Fedora project has raised most if not all of your issues, and
as they are a bit further ahead, the Fedora Bug Reports are referenced
here.

This thread makes it clear that Ubuntu is working not on revamping
wayland security, but by rewriting applications and the way they obtain
elevated privileges.

I also see your bugs getting closed as "wont fix" here on Ubuntu.

My best suggestion would be that you engage into a technical discussion
with your LP mentor, the community council, perhaps Norbert, or one of
the Gnome Developers whom you respect rather than continue a discussion
with myself, here, on this bug report.

I suggest you conduct such a technical discussion outside this bug
report, perhaps on the gnome or wayland mailing list or IRC or whatever
channel you feel benefits you most. I have given you the Wayland mailing
list and links to security discussions and can send them again if you
would like.

I believe this bug report is not the best place to obtain the
clarification and answers to your questions and I have in good faith
provided you and others what I would hope would be helpful information
and sources of further information.


bodhi@daemon:~$sudo gedit
No protocol specified
Unable to init server: Could not connect: Connection refused

(gedit:7374): Gtk-WARNING **: cannot open display: :0
bodhi@daemon:~$sudo su -


root@daemon:~#gedit
Unable to init server: Could not connect: Connection refused

(gedit:7346): Gtk-WARNING **: cannot open display:

I believe once Upstream (Wayland) feels the wayland code has matured
their long term intentions will be to drop XWayland and support for
circumventing wayland security via the mechanisms you currently use /
exploit such as Xhost , su - , etc.

I believe Xwayland and Xhost are intended to give downstream projects
such a Fedora and Ubuntu time to transition from X to Wayland and time
for Wayland to mature. Obviously this is a large project, both for
Wayland and Ubuntu .

I do not believe that because mechanisms currently exist to run
applications as root on Wayland at this time that you should assume that
such mechanisms will either be maintained or expanded in the future.

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

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

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

[Touch-packages] [Bug 1597377] Re: Malformed 01autoremove-kernels apt file

[Launchpad Bug Tracker]

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

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

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

Title:
  Malformed 01autoremove-kernels apt file

Status in apt package in Ubuntu:
  Expired

Bug description:
  After updating my system earlier today, I wanted to perform an apt
  search and it failed with this error:

  E: Syntax error /etc/apt/apt.conf.d/01autoremove-kernels:20: Malformed
  tag

  Upon inspecting the file I saw this malformed line (2nd line):

 "^.*-modules-4\.4\.0-24-generic$";
   ^@h½N^H<88>ÿÿodules-4\.4\.0-28-generic$";
 "^.*-kernel-4\.4\.0-24-generic$";

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

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

[Touch-packages] [Bug 1723562] Re: Kernels get stuck in "manual" state and fail to autoremove after disk full condition

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernels get stuck in "manual" state and fail to autoremove after disk
  full condition

Status in apt package in Ubuntu:
  Expired

Bug description:
  I use unattended-upgrades to install new kernels (I think probably
  from the security pocket). I believe this is the default. I also don't
  run autoremove automatically, which I believe is also the default.

  I just recovered a system that had been stuck in a disk full state for
  a while without me noticing because, without an automated autoremove,
  unattended-upgrades had filled my system full of kernels.

  Expected: "apt-get --purge autoremove" will remove all unused kernels,
  perhaps with a bit of coaxing from me to provide enough free space for
  dpkg and apt to function.

  Actual: "apt-get --purge autoremove" left many extra kernels
  installed.

  It seems that the reason is that apt considered most of the
  automatically installed kernels as being marked for manual install. I
  suspect that this is because apt wasn't able to mark kernels as
  automatically installed because it didn't have enough space to do so
  at the time, and without such a mark, it assumes manual.

  Workaround: use "apt-mark" to mark all kernels as automatic once
  enough space is available. Then run "/etc/kernel/postinst.d/apt-auto-
  removal" manually. Then "apt-get --purge autoremove" works.

  I'm not sure how we might approach fixing this. But I think it's a
  poor UX that Ubuntu currently relies on autoremove to remove old
  kernels to prevent the disk filling up, but this fails to work in some
  cases when the disk does fill up.

  I'm tagging such bugs "kernel-autoremove" to help us identify what
  needs fixing to make kernel autoremovals work completely to fix this
  UX issue.

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

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

[Touch-packages] [Bug 1737867] Re: apport crashes with FileNotFoundError in is_same_ns

[Daniel van Vugt]

This is the top apport crasher by more than an order of magnitude. Over
34000 crashes in the past month alone.

** Summary changed:

- 
/usr/share/apport/apport:FileNotFoundError:/usr/share/apport/apport@380:is_same_ns
+ apport crashes with FileNotFoundError in is_same_ns

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

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

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

Title:
  apport crashes with FileNotFoundError in is_same_ns

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1737867] [NEW] apport crashes with FileNotFoundError in is_same_ns

[errors.ubuntu.com bug bridge]

Public bug reported:

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

** Affects: apport
 Importance: Undecided
 Status: New

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


** Tags: artful bionic kylin-17.10 xenial zesty

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

Title:
  apport crashes with FileNotFoundError in is_same_ns

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1737657] Re: Failure to be root is repored in a misleading message

[Paul Gear]

Hi @kogorman-pacbell,

Can you explain what you think should be happening here?  Running
ntpdate from sudo or a root shell gives exactly the same behaviour -
ntpdate requires a list of servers to be provided on the command line,
and it is simply indicating that this has not been provided.

In addition, it's completely legitimate to run ntpdate as a non-root
user in order to see the offset from a remote server without setting the
time (see the man page for details on the -d option).

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

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

Title:
  Failure to be root is repored in a misleading message

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  This is a feature request.

  When solving a problem or in a rush, I don't necessarily remember
  everything from a man page, or even think to read it.  This is what
  happened with ntpdate(8)

  $ ntpdate
  11 Dec 20:08:12 ntpdate[13930]: no servers can be used, exiting
  $

  Of course, I should have used sudo.  And it's documented.  But as I
  pointed out that doesn't help much when in a hurry or stressed.  My
  bad, so I usually wouldn't mention it.  But the fix is so simple I
  hope it appeals to you.

  -> test the permissions and if they are missing, make that message

  11 Dec 20:08:12 ntpdate[13930]: insufficient permissions (suggestion:
  use sudo)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntpdate 1:4.2.8p4+dfsg-3ubuntu5.7
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Dec 11 17:53:23 2017
  InstallationDate: Installed on 2016-08-08 (490 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)

[WinEunuchs2Unix]

Brand new install 16.04.3 on Skylake w/UEFI. Originally /EFI partition
was being checked so set it to 0 in /etc/fstab. But /dev/nvme0n1p5 kept
being checked no matter how long interval set using tune2fs. Finally
used grub's `fastboot` kernel command line to make "clean" message go
away.

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

Title:
  fsck runs on every boot (clean install, single ext4 filesystem)

Status in upstart package in Ubuntu:
  Invalid

Bug description:
  fsck runs early on *every* boot (and always says "/dev/sda1: clean ...")
  The system was always shut down using the regular Unity mechanism (Gear->Shut 
Down...)

  Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1"
  shows the date of installation and never changes.

  This system is a brand new, clean install from the 15.10 beta2 iso, with 
subsequent updates.
  I took all the installer defaults, which created a single ext4 file system.

  Please see attached:
bootscreen.png - screen shot of fsck output at start of bootup (from VM 
window)
dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: upstart 1.13.2-0ubuntu16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:10:05 2015
  InstallationDate: Installed on 2015-10-07 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemJobs:
   Error: command ['initctl', '--system', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Daniel van Vugt]

@popey, have a look at bug 1707828. It shows Ctrl+Alt+T not working due
to DBus timeouts and GSD problems. Quite possibly other key combos like
Alt+PrtScn could suffer a similar fate.

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1737855] [NEW] package linux-image-4.4.0-103-generic 4.4.0-103.126 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Jim Sheng]

Public bug reported:

After upgrading from 14.04 LTS to 16.04LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-103-generic 4.4.0-103.126
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jim2793 F pulseaudio
 /dev/snd/controlC0:  jim2793 F pulseaudio
Date: Wed Dec 13 00:03:34 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=0fc93c05-44f8-4618-beaa-bd141f4d9bd9
InstallationDate: Installed on 2017-12-02 (10 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. Inspiron 15-3552
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=39b6b1f0-402c-4658-97a9-b56b986f9262 ro locale=zh_CN quiet splash 
radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 
video.use_native_backlight=1 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-103-generic 4.4.0-103.126 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2017-12-13 (0 days ago)
dmi.bios.date: 12/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 4.0.13
dmi.board.name: 079W3P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 15-3552
dmi.product.version: 4.0.13
dmi.sys.vendor: Dell Inc.

** Affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737855

Title:
  package linux-image-4.4.0-103-generic 4.4.0-103.126 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After upgrading from 14.04 LTS to 16.04LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-103-generic 4.4.0-103.126
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim2793 F pulseaudio
   /dev/snd/controlC0:  jim2793 F pulseaudio
  Date: Wed Dec 13 00:03:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=0fc93c05-44f8-4618-beaa-bd141f4d9bd9
  InstallationDate: Installed on 2017-12-02 (10 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=39b6b1f0-402c-4658-97a9-b56b986f9262 ro locale=zh_CN quiet splash 
radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 
video.use_native_backlight=1 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-103-generic 4.4.0-103.126 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-12-13 (0 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.13
  dmi.board.name: 079W3P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: 

[Touch-packages] [Bug 1737853] Re: PCI/internal sound card not detected on Dell XPS 13 9343

[Daniel Garcia Sardina]

Fixed by adding the following line to /etc/modprobe.d/alsa-base.conf
options snd-hda-intel index=1,0 jackpoll_ms=500

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

Title:
  PCI/internal sound card not detected on Dell XPS 13 9343

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal sound card not recognized on fresh install of ubuntu 17.10 on
  Dell XPS 13 (9343)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dangar 1219 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 01:03:41 2017
  InstallationDate: Installed on 2017-12-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1737855] Re: package linux-image-4.4.0-103-generic 4.4.0-103.126 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-103-generic 4.4.0-103.126 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After upgrading from 14.04 LTS to 16.04LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-103-generic 4.4.0-103.126
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim2793 F pulseaudio
   /dev/snd/controlC0:  jim2793 F pulseaudio
  Date: Wed Dec 13 00:03:34 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=0fc93c05-44f8-4618-beaa-bd141f4d9bd9
  InstallationDate: Installed on 2017-12-02 (10 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=39b6b1f0-402c-4658-97a9-b56b986f9262 ro locale=zh_CN quiet splash 
radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 
video.use_native_backlight=1 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-103-generic 4.4.0-103.126 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-12-13 (0 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.13
  dmi.board.name: 079W3P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.13
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1737853] [NEW] PCI/internal sound card not detected on Dell XPS 13 9343

[Daniel Garcia Sardina]

Public bug reported:

Internal sound card not recognized on fresh install of ubuntu 17.10 on
Dell XPS 13 (9343)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dangar 1219 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 13 01:03:41 2017
InstallationDate: Installed on 2017-12-12 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  PCI/internal sound card not detected on Dell XPS 13 9343

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal sound card not recognized on fresh install of ubuntu 17.10 on
  Dell XPS 13 (9343)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dangar 1219 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 01:03:41 2017
  InstallationDate: Installed on 2017-12-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

[Coomy Ted]

Partial from logfile. Dell 5378 13 i7 KabyLake fresh re-install of
Artful


Priority 3dbus:

Failed to construct signal

dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) 
none
(src/devices/nm-device.c:1452)): assertion '' failed

It's a shame that this bug has been around so long without fixes.

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

Title:
  wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Wifi network can't connect after the wake up from suspend. Xubuntu
  15.04

  I'll post more useful details (journalctl log) as a comment to this
  bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 4.0.0-04rc5-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  2 18:18:56 2015
  InstallationDate: Installed on 2015-03-27 (5 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1737762] Re: i wont let me update and my terminal is going crazy

[Paul White]

** Changed in: xorg (Ubuntu)
 Assignee: brandon cunningham (brandonkilecunningham) => (unassigned)

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

Title:
  i wont let me update and my terminal is going crazy

Status in xorg package in Ubuntu:
  New

Bug description:
  it wont let me update and terminal is crazy

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Set the CPU Frequency Scaling 
governor to "ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec 12 06:57:52 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 
3450/3470] [103c:30dc]
  InstallationDate: Installed on 2017-03-14 (272 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCD Ver. F.17
  dmi.board.name: 30DC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.2A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCDVer.F.17:bd03/05/2010:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.17:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.2A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 6930p
  dmi.product.version: F.17
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Dec 12 02:50:18 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1728378] Re: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed

[Coomy Ted]

This bug affects my Dell 5378 13 i7 KabyLake. New re-install of Artful.

NetworkManager

(src/devices/nm-device.c:1452)): assertion '' failed

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

Title:
  NetworkManager: ((src/devices/nm-device.c:1452)): assertion
  '' failed

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This error shows up in boot logs:
  "NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' 
failed".
  Ubuntu 17.10

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Dave Chiluk]

** Tags added: indeed

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1737846] [NEW] bash fails to redirect standard output of a pipeline to the input file of the fist pipeline's command

[Arbiel Perlacremaz]

Public bug reported:

In a non-interactive bash session, redirecting the standard output to the file 
read by the pipeline's first command leads to random resuts : the redirection 
sometimes works, but generally the file is overwriten by an empty file.
In an interactive session, the redirection works, which leads the user to look 
somewhere else to find a bug.

However, when the last command is a user-writen function which simulates
"cat", the resulting file is correct, as in an interactive session.

Bash documentation does not prohibit such processing.

Arbiel

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: bash 4.3-7ubuntu1.5
ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
Uname: Linux 3.13.0-106-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 12 23:51:22 2017
InstallationDate: Installed on 2014-05-30 (1292 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: bash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Attachment added: "error-report"
   
https://bugs.launchpad.net/bugs/1737846/+attachment/5021868/+files/error-report

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

Title:
  bash fails to redirect standard output of a pipeline to the input file
  of the fist pipeline's command

Status in bash package in Ubuntu:
  New

Bug description:
  In a non-interactive bash session, redirecting the standard output to the 
file read by the pipeline's first command leads to random resuts : the 
redirection sometimes works, but generally the file is overwriten by an empty 
file.
  In an interactive session, the redirection works, which leads the user to 
look somewhere else to find a bug.

  However, when the last command is a user-writen function which
  simulates "cat", the resulting file is correct, as in an interactive
  session.

  Bash documentation does not prohibit such processing.

  Arbiel

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bash 4.3-7ubuntu1.5
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-106-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 12 23:51:22 2017
  InstallationDate: Installed on 2014-05-30 (1292 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1737843] [NEW] Consider demoting xchat-gnome to universe

[Jeremy Bicha]

Public bug reported:

xchat-gnome came up today in a discussion of main components that aren't
ready for openssl 1.1.

https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040087.html

See Steve's response
https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040089.html

"Ubuntu-only package (dropped in Debian, dropped subsequently in Ubuntu, then
brought back).  Did not ship in yakkety or zesty; when restored in artful it
went straight to main because it was still seeded, but it's unclear this was
ever reviewed by the Desktop Team or whether they want this package still in
main.  (The re-uploader is not a member of the Desktop Team.)"

xchat-gnome is seeded in the supported-desktop-extra seed.

Do we still need an IRC desktop client in main? (irssi is in main)

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

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

** Also affects: xchat-gnome (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Consider demoting xchat-gnome to universe

Status in ubuntu-meta package in Ubuntu:
  New
Status in xchat-gnome package in Ubuntu:
  New

Bug description:
  xchat-gnome came up today in a discussion of main components that
  aren't ready for openssl 1.1.

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-December/040087.html

  See Steve's response
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040089.html

  "Ubuntu-only package (dropped in Debian, dropped subsequently in Ubuntu, then
  brought back).  Did not ship in yakkety or zesty; when restored in artful it
  went straight to main because it was still seeded, but it's unclear this was
  ever reviewed by the Desktop Team or whether they want this package still in
  main.  (The re-uploader is not a member of the Desktop Team.)"

  xchat-gnome is seeded in the supported-desktop-extra seed.

  Do we still need an IRC desktop client in main? (irssi is in main)

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

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

[Touch-packages] [Bug 1322024] Re: Make Hexchat the default IRC client instead of XChat in Ubuntu 14.10 and later versions

[Jeremy Bicha]

hexchat currently uses gtk2 and I don't think we want any more gtk2
dependencies added to main.

hexchat is currently in main so it would need to complete the Main Inclusion 
Process.
https://wiki.ubuntu.com/MainInclusionProcess

But you'll need to talk to the Ubuntu Desktop team about whether they
want hexchat in main.

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

Title:
  Make Hexchat the default IRC client instead of XChat in Ubuntu 14.10
  and later versions

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in xchat package in Ubuntu:
  New

Bug description:
  Since XChat is no longer in development by it's main developer, I was
  thinking that maybe you guys should make HexChat the default IRC
  client for Ubuntu 14.10, if it isn't already the default IRC client in
  Ubuntu 14.04. It's a great IRC client, and it's much better than
  XChat. So I would really appreciate it if you guys could make HexChat
  the default IRC client in the next release of Ubuntu.

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

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

[Touch-packages] [Bug 498137] Re: Weather data for Coventry (UK) no longer available

[Bug Watch Updater]

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

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

Title:
  Weather data for Coventry (UK) no longer available

Status in libgweather:
  Fix Released
Status in libgweather package in Ubuntu:
  Invalid

Bug description:
  Since Coventry airport closed at the beginning of December 09
  (http://news.bbc.co.uk/1/hi/england/coventry_warwickshire/8401690.stm)
  no weather information has been available for Coventry (UK). The data
  currently being displayed originates from the 8th of December 09.

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

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

[Touch-packages] [Bug 1737835] [NEW] libunity fails to build, test failure

[Jeremy Bicha]

Public bug reported:

libunity fails to build from source in current bionic. Full build log at

https://launchpad.net/~jbicha/+archive/ubuntu/dev/+build/13847861

Build log excerpt
=
TEST: test-vala... (pid=18081)
  /Unit/ResultsSynchronizer:   OK
  /Unit/IO/AsyncDesktopFile:   OK
  /Unit/IO/AsyncOpenFromDataDirs:  OK
  /Unit/Utils/AsyncOnce:   OK
  /Unit/Utils/AsyncMutex:  OK
  /Unit/AppInfoManager/Allocation: OK
  /Unit/AppInfoManager/ClearEmpty: OK
  /Unit/AppInfoManager/SyncLookupMissing:  OK
  /Unit/AppInfoManager/AsyncLookupMissing: OK
  /Unit/AppInfoManager/SyncLookupOk:   OK
  /Unit/AppInfoManager/AsyncLookupOk:  OK
  /Unit/Launcher/EmptyEntry:   
(test-vala:18081): libunity-CRITICAL **: unity-launcher.vala:154: Unable to 
connect to session bus: Could not connect: Connection refused
FAIL

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


** Tags: bionic ftbfs

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

Title:
  libunity fails to build, test failure

Status in libunity package in Ubuntu:
  New

Bug description:
  libunity fails to build from source in current bionic. Full build log
  at

  https://launchpad.net/~jbicha/+archive/ubuntu/dev/+build/13847861

  Build log excerpt
  =
  TEST: test-vala... (pid=18081)
/Unit/ResultsSynchronizer:   OK
/Unit/IO/AsyncDesktopFile:   OK
/Unit/IO/AsyncOpenFromDataDirs:  OK
/Unit/Utils/AsyncOnce:   OK
/Unit/Utils/AsyncMutex:  OK
/Unit/AppInfoManager/Allocation: OK
/Unit/AppInfoManager/ClearEmpty: OK
/Unit/AppInfoManager/SyncLookupMissing:  OK
/Unit/AppInfoManager/AsyncLookupMissing: OK
/Unit/AppInfoManager/SyncLookupOk:   OK
/Unit/AppInfoManager/AsyncLookupOk:  OK
/Unit/Launcher/EmptyEntry:   
  (test-vala:18081): libunity-CRITICAL **: unity-launcher.vala:154: Unable to 
connect to session bus: Could not connect: Connection refused
  FAIL

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

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

[Touch-packages] [Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe

[Stéphane Graber]

Marking the lxc task as invalid since LXC does not drop any such
capabilities by default, so such failure isn't lxc's fault. It's either
the user's fault (by dropping capabilities that Ubuntu/Debian consider
as required) or the systemd's package fault (for not doing a capability
check).

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

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

Title:
  On upgrade, daemon-reexec should only be issued if safe

Status in lxc package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Dear all,

  Following up the bug report #1713674, when executing systemd in a
  hardened LXC context, it might not be suitable to reexec systemd
  daemon, that would not be able to perform.

  For instance, in our LXC, we drop several capabilities, including
  sys_admin and we set /sys to read-only (in which, systemd will find
  its cgroups). This means, systemd cannot be reexecuted, it will fail
  to restart and will freeze (properly) at restart making the LXC
  container in frozen state (still working, but no new services
  startable, no interaction with systemd possible anymore).

  When upgrading systemd the debian package, as postinst, will always
  attempt to reexecute systemd, possibly breaking every other upgrade
  where a daemon restart is made in postinst, and leaving the system in
  a degraded state.

  It would likely be appropriate the check whether the reexecute can
  work will before performing it: checking capabilities, sys mount point
  perms, etc. If not applicable, not performing a reexucte and possibly
  print a message to the user.

  Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.

  Cheers

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

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

[Touch-packages] [Bug 1737805] Re: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured

[dino99]

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

** Package changed: glib2.0 (Ubuntu) => dpkg (Ubuntu)

** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade:
  package libglib2.0-0:amd64 is already installed and configured

Status in dpkg package in Ubuntu:
  New

Bug description:
  the instalation failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:amd64 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.14
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Tue Dec 12 20:28:43 2017
  DuplicateSignature:
   package:libglib2.0-0:amd64:2.48.2-0ubuntu1
   Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ...
   dpkg: error processing package uuid-runtime (--configure):
package uuid-runtime is already installed and configured
  ErrorMessage: package libglib2.0-0:amd64 is already installed and configured
  InstallationDate: Installed on 2016-07-07 (523 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: glib2.0
  Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: 
package libglib2.0-0:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

[Vlad Orlov]

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

** Changed in: mate-terminal (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

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

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Jeremy Bicha]

Uploaded debdiffs to the SRU queue where they will need to be manually
approved by the SRU Team before being built as proposed updates.

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  In Progress
Status in libgweather source package in Zesty:
  In Progress
Status in libgweather source package in Artful:
  In Progress

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Touch-packages] [Bug 1737803] Re: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Leonidas S. Barbosa]

** Information type changed from Private Security to Public

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

Title:
  package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  im not sure about the cause of the issue.. i upgraded from ubuntu 14
  to 16.. from the first launch im getting this issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.8
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Tue Dec 12 23:47:05 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-29 (44 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-12-12 (0 days ago)

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

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

[Touch-packages] [Bug 1737805] Re: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured

[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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1737805

Title:
  package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade:
  package libglib2.0-0:amd64 is already installed and configured

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  the instalation failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:amd64 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.14
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Tue Dec 12 20:28:43 2017
  DuplicateSignature:
   package:libglib2.0-0:amd64:2.48.2-0ubuntu1
   Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ...
   dpkg: error processing package uuid-runtime (--configure):
package uuid-runtime is already installed and configured
  ErrorMessage: package libglib2.0-0:amd64 is already installed and configured
  InstallationDate: Installed on 2016-07-07 (523 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: glib2.0
  Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: 
package libglib2.0-0:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1737805] [NEW] package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured

[Andrei]

Public bug reported:

the instalation failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0:amd64 2.48.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.14
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Tue Dec 12 20:28:43 2017
DuplicateSignature:
 package:libglib2.0-0:amd64:2.48.2-0ubuntu1
 Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ...
 dpkg: error processing package uuid-runtime (--configure):
  package uuid-runtime is already installed and configured
ErrorMessage: package libglib2.0-0:amd64 is already installed and configured
InstallationDate: Installed on 2016-07-07 (523 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: glib2.0
Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: 
package libglib2.0-0:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade:
  package libglib2.0-0:amd64 is already installed and configured

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  the instalation failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:amd64 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.14
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Tue Dec 12 20:28:43 2017
  DuplicateSignature:
   package:libglib2.0-0:amd64:2.48.2-0ubuntu1
   Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ...
   dpkg: error processing package uuid-runtime (--configure):
package uuid-runtime is already installed and configured
  ErrorMessage: package libglib2.0-0:amd64 is already installed and configured
  InstallationDate: Installed on 2016-07-07 (523 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: glib2.0
  Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: 
package libglib2.0-0:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 365094] Re: there isn't in the list a place (Falconara Ancona - Italia) in weather applet

[Bug Watch Updater]

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

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

Title:
  there isn't in the list a place (Falconara Ancona - Italia) in weather
  applet

Status in libgweather:
  Fix Released
Status in libgweather package in Ubuntu:
  Incomplete

Bug description:
  sorry for my bad english,

  In ubuntu 8.04 I've my place but in ubuntu 8.10 it missing.

  City name Ancona/Falconara Italy

  Latitude 43,616665
  Longitude 13,37
  Airport Ancona/Falconara
  Airport ICAO code LIPY
  Codice WMO16191

  tahnks

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

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

[Touch-packages] [Bug 1682102] Re: libseccomp should support GA and HWE kernels

[Tyler Hicks]

As for the failing Xenial snapd autopkgtests...

- amd64: The autopkgtest:ubuntu-16.04-amd64:tests/main/completion fails with 
and without the libseccomp in xenial-proposed
- s390x: No tests are ever ran due to the tests requiring "machine-level 
isolation" but that not being available on s390x. However, snapd s390x test 
runs have been hitting an error for about the last month.

Both are false positives and should not be something that keeps
libseccomp from migrating.

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

Title:
  libseccomp should support GA and HWE kernels

Status in libseccomp package in Ubuntu:
  Invalid
Status in libseccomp source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  out of date libseccomp w.r.t. custom and hwe kernels provides sub-par 
userspace protection, which is otherwise available on the running kernel and 
hardware combination.
  This results in subpar security of systems running new architectures (s390x & 
ppc64el) and newer hwe/custom kernels.

  * Version 2.3.1 - April 20, 2016
  - Fixed a problem with 32-bit x86 socket syscalls on some systems
  - Fixed problems with ipc syscalls on 32-bit x86
  - Fixed problems with socket and ipc syscalls on s390 and s390x

  * Version 2.3.0 - February 29, 2016
  - Added support for the s390 and s390x architectures
  - Added support for the ppc, ppc64, and ppc64le architectures
  - Update the internal syscall tables to match the Linux 4.5-rcX releases
  - Filter generation for both multiplexed and direct socket syscalls on x86
  - Support for the musl libc implementation
  - Additions to the API to enable runtime version checking of the library
  - Enable the use of seccomp() instead of prctl() on supported systems
  - Added additional tests to the regression test suite

  There is no ABI/API break

  There are no packaging changes, apart from dropping patches included
  in this upstream release and updating new symbols.

  Doing wholesome update is safer and carries less risk, than
  individually cherrypicking effectively all of the above.

  This is a backport to an LTS release under the banner of safe
  introduction of new features and new hardware support.

  It is expected that container technologies will take advantage of the
  newly available libseccomp.

  This may need to be uploaded as a security update.

  Currently, s390x support in xenial libssecomp is incomplete. And there
  are v4.5+ syscall tables missing as used by hwe kernels and some
  custom kernels.

  [Testcase]
  Validate that all main contianer technologies are operational and do not 
regress, e.g.:
   - lxc
   - lxd
   - docker
   - snapd

  [Regression Potential]
  Userspace components may detect at runtime newly available libseccomp, and 
thus restrict user-space processes more than previously done. This may lead to 
a change of restrictions applied on the user sapce processes, and result in 
previously unexpected denials / errors returned.

  
  [Proposed Update available in bileto PPA]
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2981

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

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

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

[bugproxy]

--- Comment From chngu...@us.ibm.com 2017-12-12 12:29 EDT---
We hit the same issue on BostonLC as well. We are blocked on this in order to 
go forward.
Breno, do you have any workaround to bypass this issue ?

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  

[Touch-packages] [Bug 192629] Re: "Cannot move file to trash, do you want to delete immediately?" on NTFS / VFAT partitions

[Aravind R]

ubuntu 17.10 same issue

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

Title:
  "Cannot move file to trash, do you want to delete immediately?" on
  NTFS / VFAT partitions

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Trying to delete files with nautilus from a vfat partition "fails".
  Well, the file can be deleted OK, but it seems gvfs can't send the
  file to the trashcan, so only permanent delete is available.
  Furthermore, the name of the file appears in little boxes, similar to
  viewing a chinese site using Latin-1 encoding (will attach
  screenshot).

  Distro: Hardy up to date (17-february 2008)

  Steps to reproduce: Copy a file to an vfat partition. Select it and delete 
using nautilus. A message error will appear: 
"Can't move file to trashcan. Do you want to delete it inmediately?"
"File <>cannot be moved to trashcan"

  Versions:
  Nautilus 1:2.21.91-0ubuntu2
  gvfs 0.1.7-0ubuntu4

  /etc/fstab for the vfat partition:
  UUID=9445-A956  /fat32  vfatdefaults,utf8,umask=007,gid=46 0  
 1

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

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

[Touch-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

[Aravind R]

My Current system is ubuntu 17.10. If I delete file under home it moves
to trash. But if I delete file in other location. It dont go to trash

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

Title:
  Files in the root of a folder on another partition symlinked to user's
  home cannot be moved to trash because of a patch in this package

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Released
Status in glib2.0 source package in Yakkety:
  Fix Released

Bug description:
  [ Description ]

  Can't trash files if the directory they are in is a symlink to another
  device

  [ QA ]

  Steps:
  1. Install system and partition disk into root and data partitions
  2. create ~/Data folder, and mount data partition on it
  3. create symlinks for ~/whatever/ to ~/Data/something/
  4. delete files directly inside ~/whatever/

  What happen:
  Then Nautilus says: "File can't be put in the trash. Do you want to delete it 
immediately?".

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

  The proposed fix uses g_stat instead of g_stat to follow symlinks, so
  we know where to place the trash (you can't rename() across
  filesystems). If that is wrong, then it could regress trashing other
  kinds of files.

  [ Original ]

  I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.

  I've reported this bug (or marked as "it affects me") in a couple of
  other places before I've finally discovered that this is the package
  that's causing this problem, which unfortunately has been around for a
  couple of years now.

  This bug has been reported upstream as well, but it's just taking very
  very long to arrive at a decision and take action it seems.

  Apparently one of the patches
  (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix-
  trashing-on-overlayfs.patch/) which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz)
  to the original package which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz)
  is the root cause of this annoying problem.

  As I prefer keeping one patition for the root filesystem (/), one
  partition for user settings (/home) and one partition for user data
  (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which
  are simply symlinked to my home folder for ease of use, I cannot move
  any file to the trash in the root of these folders when I access them
  from my home folder or nautilus sidebar.

  This problem doesn't affect folders at all, nor any other files in
  subfolders, etc.

  So I was wondering if Ubuntu devs can leave out that particular patch
  when building this package for Ubuntu - if it doesn't cause more harm,
  which I doubt.

  Otherwise, I would appreciate if I could learn how to do it myself:
  how can I (as an end-user) compile the contents of
  "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in
  "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on-
  overlayfs.patch"?

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

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

[Touch-packages] [Bug 1640180] Re: gnome-todo doesn't load CalDav task list from EDS

[Jeremy Bicha]

** Changed in: evolution-data-server (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  gnome-todo doesn't load CalDav task list from EDS

Status in GNOME To Do:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in gnome-todo package in Ubuntu:
  Triaged

Bug description:
  Since the upgrade to Yakkety Gnome-TODO doesn't show my remote CalDav
  task list that were set through evolution. The list are still
  available in working in Evolution.

  I tried to set them up again but they didn't appear. 
  I tried upgrading to version available in various gnome3-ppa (still 3.20.* 
though) and it didn't help.

  The bug seems to have been handled in Fedora :
  https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1363848
  and https://bodhi.fedoraproject.org/updates/FEDORA-2016-db729be3e1 (I
  found those while searching the web for a solution).

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

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

[Touch-packages] [Bug 1728653] Re: Update evolution-data-server to 3.26.3

[Jeremy Bicha]

** Summary changed:

- Update evolution-data-server to 3.26.2
+ Update evolution-data-server to 3.26.3

** Description changed:

  Impact
  ==
  evolution-data-server (e-d-s) has released a new stable bugfix release.
- (These will happen about once every month or two until 3.28 is released.)
+ (These will happen about once every month until 3.28 is released.)
  
- Updating e-d-s is required to update evolution to 3.26.2 (LP: #1728655)
+ Updating e-d-s is required to update evolution to 3.26.3 (LP: #1728655)
  
  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26
  
  Test Case
  =
  After installing the update, restart your computer.
  
  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.
  
  Regression Potential
  
  GNOME 3.26 distros will be shipping this update.
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

** Changed in: evolution-data-server (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  Update evolution-data-server to 3.26.3

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  evolution-data-server (e-d-s) has released a new stable bugfix release.
  (These will happen about once every month until 3.28 is released.)

  Updating e-d-s is required to update evolution to 3.26.3 (LP:
  #1728655)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.26 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1728653/+subscriptions

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

[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

[Mike Hardy]

I see the same thing on Ubuntu 16.04 / apport 2.20.1-0ubuntu2.14 - same
apport command line (except a different PID number), same error number
and everything.

Looks like 'is_same_ns' is blindly doing an os.readlink on a path that
it assumes must exist (because it does no defensive check) but the path
clearly is missing sometimes

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1551731] Re: free command not working with -s flag

[Brian Murray]

This is fixed in Zesty and later.

 procps | 2:3.3.12-1ubuntu2   | zesty   | source, amd64, arm64, armhf, 
i386, ppc64el, s390x
 procps | 2:3.3.12-1ubuntu2   | artful  | source, amd64, arm64, armhf, 
i386, ppc64el, s390x
 procps | 2:3.3.12-1ubuntu2   | bionic  | source, amd64, arm64, armhf, 
i386, ppc64el, s390x


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

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

Title:
  free command not working with -s flag

Status in procps-ng:
  Fix Released
Status in procps package in Ubuntu:
  Fix Released

Bug description:
  when i enter this command :
  free -s 3
  or and numbers for seconds , it returns me :
  free: seconds argument `3' failed
  but i have only this bug in version 3.3.10 and in 3.3.9 it worls normally and 
refresh free in entered seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  1 17:00:20 2016
  InstallationDate: Installed on 2016-01-24 (36 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160123)
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/procps-ng/+bug/1551731/+subscriptions

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

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

[bugproxy]

--- Comment From indira.pr...@in.ibm.com 2017-12-12 11:57 EDT---
Can i take whip system back for other testing.

Regards,
Indira

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  ?
?   ?   ?  ?

[Touch-packages] [Bug 1737790] Re: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Might have been caused by a full /boot

  Maybe same as https://bugs.launchpad.net/bugs/1737282

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  theo  14705 F pulseaudio
david 30317 F pulseaudio
gdm   30621 F pulseaudio
  Date: Mon Dec 11 22:34:49 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b82815c7-d577-421c-ae03-79a7aa4b080d
  InstallationDate: Installed on 2014-10-01 (1167 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 42404CG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET51WW (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42404CG
  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:bvr8AET51WW(1.31):bd08/08/2011:svnLENOVO:pn42404CG:pvrThinkPadT520:rvnLENOVO:rn42404CG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 42404CG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1737790] [NEW] package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[2GooD]

Public bug reported:

Might have been caused by a full /boot

Maybe same as https://bugs.launchpad.net/bugs/1737282

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-extra-4.13.0-19-generic 4.13.0-19.22
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  theo  14705 F pulseaudio
  david 30317 F pulseaudio
  gdm   30621 F pulseaudio
Date: Mon Dec 11 22:34:49 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=b82815c7-d577-421c-ae03-79a7aa4b080d
InstallationDate: Installed on 2014-10-01 (1167 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 42404CG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET51WW (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42404CG
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:bvr8AET51WW(1.31):bd08/08/2011:svnLENOVO:pn42404CG:pvrThinkPadT520:rvnLENOVO:rn42404CG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T520
dmi.product.name: 42404CG
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful need-duplicate-check

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

Title:
  package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Might have been caused by a full /boot

  Maybe same as https://bugs.launchpad.net/bugs/1737282

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  theo  14705 F pulseaudio
david 30317 F pulseaudio
gdm   30621 F pulseaudio
  Date: Mon Dec 11 22:34:49 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b82815c7-d577-421c-ae03-79a7aa4b080d
  InstallationDate: Installed on 2014-10-01 (1167 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 42404CG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET51WW (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42404CG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
 

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

Ok, so I will add this on the next libvirt merge to be safe on bionic.

** Changed in: libvirt (Ubuntu)
   Status: Confirmed => 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/1732030

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

@Tamas - your stack trace might help to identify another source of such
issues, let us know.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install

[Roger]

In ubuntu 17.10, this issue disappeared after I installed
gstreamer1.0-libav.

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

Title:
  Totem can't play H264 on fresh 16.04 beta install

Status in gstreamer1.0 package in Ubuntu:
  Fix Released

Bug description:
  Totem can't play neither find the correct codec to play H264 *.mp4
  video in last 16.04 beta.

  Terminal says :

  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile)
  decoder|decoder-video/x-h264, stream-format=(string)avc,
  alignment=(string)au, level=(string)4, profile=(string)main, max-
  input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile)
  decoder)

  
  Totem tries to find the correct codec but fails, see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 15:51:47 2016
  InstallationDate: Installed on 2016-03-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  ?
?   ?   ?  ?

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Yuan-Chen Cheng]

@Łukasz, Do you think it's easier for us to SRU: #1693756, #17 ?

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Yuan-Chen Cheng]

@Łukasz, Do you think it's easier for us to SRU LP: #1693756, #17 ?

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Julian Andres Klode]

1. This is appending. You could also write it
apt::sandbox::seccomp::allow:: "getdents" but the list notation is
documented.

2. Right. Others might have other issues, mostly depending on their NSS
modules. I don't think we'll fix all of them. But I don't think there
are many users with non-standard NSS modules, so this maybe affects
what, 1 to 5% of the users?

3. Exactly

We can eventually also enable getdents in apt itself, once the methods
do not need write access to partial/ anymore (because the main process
then opens the file and sends it via a socket). I only disabled it for
now so one method cannot find files used by other methods (except for
guessing).

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1610499] Re: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group

[Volker Mischo]

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

Hello, I 've got the same problem with DB2. When I'm leaving the system
as the DB instance owner, all procs are killed. I guess, it depends on
the new systemd in 1604. ( see /var/log/syslog "received SIGRTMIN+24
from PID  (kill) "  ) maybe some sysctl param like kernel.shmall ..
are involved too. It would be nice if a maintainer finally fixed that
problem.

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

Title:
  hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process
  group

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

Hi Julian,
I have broken down the testcase into reproducible steps:

Testcase - TL;DR get running guest with IP and enable libvirt nss:
$ apt install libnss-libvirt libvirt-dameon-system
$ apt update
$ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily 
arch=amd64 label=daily release=artful
$ uvt-kvm create --password=ubuntu testguest release=artful arch=amd64 
label=daily
$ vim /etc/nsswitch.conf
# add libvirt to the hosts line
$ apt download hello

So would the following be good then?
$ cat /etc/apt/apt.conf.d/90libnss-libvirt
apt::sandbox::seccomp::allow { "getdents" };

I wonder about a few things:
1. is there a format that does not "set" but append this to ensure if one 
placed other seccomp allows that they do not interfere?
2. I'm not sure everybody is hitting that through libnss-libvirt so I might 
only fix one of many incarnations of this.
3. this is only for newer apt needs this right - so only >=bionic ok?

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

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

-- 
Mailing list: https://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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Ryan Harper]

On Tue, Dec 12, 2017 at 5:52 AM, Dimitri John Ledkov  wrote:

> Once the kernel is fixed, are there any changes that are required to
> systemd/udev?
>

No changes needed.


>
> ** Changed in: systemd (Ubuntu Bionic)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  In Progress
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: 

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[manfreed]

Alan Pope:

I did have a similar issue where most of the usual hotkeys wouldn't
work, but that was caused me screwing around in gnome settings and it
was solved by resetting my profile.

I believe this issue is different than that.

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 559105] Re: Temperature in The Hague, The Netherlands is always the same

[Bug Watch Updater]

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

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

Title:
  Temperature in The Hague, The Netherlands is always the same

Status in libgweather:
  Fix Released
Status in libgweather package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-panel

  In gnome-panel under clock the weather an temperature is shown for The 
Netherland. The temperature is always shown as 5 degrees Centugrade (day and 
night), This is not the temperature in the netherlands right now.
  Changing the location pe Rotterdam for The Hague has no influence. The clock 
keeps showing 5 degrees centigrade

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-panel 1:2.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: wl fglrx
  Architecture: amd64
  Date: Fri Apr  9 12:20:39 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-panel

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

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Łukasz Zemczak]

Sadly the test results got wiped out from Bileto for unknown reasons, I
have re-run the tests. They should appear here
https://bileto.ubuntu.com/#/ticket/3054 under the Automated Test
Results.

What about my question about cherry-picking the new modem code to the
xenial version of modemmanager? As said, seeing how many packages this
SRU involves I'm starting to get worried about if this will get
accepted.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Jeremy Bicha]

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

** Also affects: gnome-weather (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: gnome-weather (Ubuntu Xenial)

** Also affects: libgweather (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: gnome-weather (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** No longer affects: gnome-weather (Ubuntu Zesty)

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

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

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

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

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  In Progress
Status in libgweather source package in Zesty:
  In Progress
Status in libgweather source package in Artful:
  In Progress

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Julian Andres Klode]

It would be nice if libvirt-nss could ship an /etc/apt/apt.conf.d
/libvirt-nss.conf, or a numbered file like the others, that allows
getdents. I don't think I want to turn it on in general because not
being able to list a directory is kind of useful.

** Also affects: libvirt (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/1732030

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  New

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1737762] [NEW] i wont let me update and my terminal is going crazy

[brandon cunningham]

Public bug reported:

it wont let me update and terminal is crazy

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog: [  OK  ] Started LSB: Set the CPU Frequency Scaling 
governor to "ondemand".
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Dec 12 06:57:52 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3450/3470] 
[103c:30dc]
InstallationDate: Installed on 2017-03-14 (272 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP EliteBook 6930p
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCD Ver. F.17
dmi.board.name: 30DC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.2A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCDVer.F.17:bd03/05/2010:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.17:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.2A:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 6930p
dmi.product.version: F.17
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Dec 12 02:50:18 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Assignee: brandon cunningham (brandonkilecunningham)
 Status: New


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

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => brandon cunningham (brandonkilecunningham)

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

Title:
  i wont let me update and my terminal is going crazy

Status in xorg package in Ubuntu:
  New

Bug description:
  it wont let me update and terminal is crazy

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Set the CPU Frequency Scaling 
governor to "ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec 12 06:57:52 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 
3450/3470] [103c:30dc]
  InstallationDate: Installed on 2017-03-14 (272 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  

[Touch-packages] [Bug 1737318] Re: dependency not met

[Bruce Miller]

Sorry for the poorly formatted reply. In future, I will not use a
webmail client tto send bugmail.

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

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

Title:
  dependency not met

Status in systemd package in Ubuntu:
  New

Bug description:
  The following packages have unmet dependencies:
   libnss-resolve : Depends: systemd (= 234-2ubuntu12.1) but 234-2ubuntu12.2 is 
to be installed
  open: 23; closed: 490; defer: 5; conflict: 5  

.The following actions will 
resolve these dependencies:

   Keep the following packages at their current version:
  1) libpam-systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]
  2) libsystemd0 [234-2ubuntu12.1 (artful-security, artful-updates, now)]   
  3) systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libnss-resolve 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Dec  9 07:40:09 2017
  InstallationDate: Installed on 2016-10-02 (432 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160512)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (46 days ago)

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Sebastien Bacher]

** Package changed: gnome-shell (Ubuntu) => unity (Ubuntu)

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

[Michael Thayer]

Ah, it is the old problem with lightdm not waiting for the udev
notification that the driver is loaded.

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

Title:
  Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

Status in Virtualbox:
  Invalid
Status in console-setup package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Fix Released

Bug description:
  (Content copied from "Ubuntu 14.10 ISO live boot ends up with a
  corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz)

  Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO 
ends up with a corrupted screen. See the screenshot:
  https://launchpadlibrarian.net/186864347/ubu.png

  Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7)
  fixes the display.

  I think that this might be a problem with resolution setting:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  ```

  After switching back and forth to the tty7 (what fixes the display)
  the log says:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
  00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=720x400
  00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1
  00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler..
  00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768
  00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use 
VGA device content..
  ```

  I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens
  on both of them.

  You can download the ISO images of these two systems here:

   https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10
  -desktop-amd64.iso

   http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-
  gnome-14.10-desktop-amd64.iso

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

Note: adding getdents as suggested was enough, there were no further
seccomp hits triggered later on.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

I hit this today in a Bionic container trying to use "apt-get download".
Found this bug and based on this trying to provide the debug data that was 
requested back then.

So I gathered the crash file with JulianK's hint and then used Tamas
workaround to get all apport tools as needed.

# apport-retrace --rebuild-package-info --stdout 
/var/crash/_usr_lib_apt_methods_http.0.crash 
dpkg-source: info: extracting apt in apt-1.6~alpha5
dpkg-source: info: unpacking apt_1.6~alpha5.tar.xz
W: Download is performed unsandboxed as root as file 'apt_1.6~alpha5.dsc' 
couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
--- stack trace ---
#0  0x7faff80f04eb in __getdents (fd=3, buf=0x561fff2a96d0 "\035g\233", 
, nbytes=32768) at 
../sysdeps/unix/sysv/linux/getdents.c:96
resultvar = 78
retval = 
#1  0x7faff80f00b5 in __readdir (dirp=0x561fff2a96a0) at 
../sysdeps/posix/readdir.c:65
maxread = 
bytes = 
reclen = 
dp = 
saved_errno = 0
#2  0x7faff55e826e in ?? () from /lib/x86_64-linux-gnu/libnss_libvirt.so.2
No symbol table info available.
#3  0x7faff55cebdf in ?? () from /lib/x86_64-linux-gnu/libnss_libvirt.so.2
No symbol table info available.
#4  0x7faff55cf657 in _nss_libvirt_gethostbyname4_r () from 
/lib/x86_64-linux-gnu/libnss_libvirt.so.2
No symbol table info available.
#5  0x7faff81155df in gaih_inet (name=name@entry=0x561fff26cba0 
"archive.ubuntu.com", service=, req=req@entry=0x7fffa2434860, 
pai=pai@entry=0x7fffa2434328, naddrs=naddrs@entry=0x7fffa2434324, 
tmpbuf=tmpbuf@entry=0x7fffa2434390) at ../sysdeps/posix/getaddrinfo.c:790
fct4 = 0x7faff55cf5f0 <_nss_libvirt_gethostbyname4_r>
pat = 0x7fffa2434118
no_inet6_data = 
nip = 0x561fff2a93d0
status = 
no_more = 0
no_data = 0
inet6_status = NSS_STATUS_UNAVAIL
res_ctx = 0x561fff295a00
res_enable_inet6 = false
tp = 
st = 0x7fffa2434040
at = 0x7fffa2434000
got_ipv6 = false
canon = 0x0
orig_name = 0x561fff26cba0 "archive.ubuntu.com"
alloca_used = 
port = 
malloc_name = false
addrmem = 0x0
canonbuf = 0x0
result = 0
#6  0x7faff81175c7 in __GI_getaddrinfo (name=, 
service=, hints=0x7fffa2434860, pai=0x561ffdb8b370) at 
../sysdeps/posix/getaddrinfo.c:2304
tmpbuf = {data = 0x7fffa24343a0, length = 1024, __space = "\377\002", 
'\000' , 
"\003\240CC\242\377\177\000\000\000\000\000\000\000\000\000\000ff02::3\000ip6-allhosts",
 '\000' , "able 
hosts\n\000\257\177\000\000\030\000\000\000\000\000\000\000\000<\360\251\300\071s\362\230|?\370\257\177\000\000\000\000\000\000\000\000\000\000\260\346(\377\037V\000\000\000\350(\377\037V\000\000\220m)\377\037V\000\000ps)\377\037V\000\000\000\000\000\000\000\000\000\000\376\263\n\370\257\177\000\000\240b+\377\037V\000\000\006\000\000\000\000\000\000\000\272\375\033\370\257\177\000\000"...}
i = 0
last_i = 0
nresults = 0
p = 0x0
gaih_service = {name = 0x7fffa2434aa0 "http", num = -1}
pservice = 
local_hints = {ai_flags = 1, ai_family = 0, ai_socktype = 0, 
ai_protocol = 0, ai_addrlen = 4280870576, ai_addr = 0x561fff28e800, 
ai_canonname = 0x561fff296d90 "@m)\377\037V", ai_next = 0x561fff297370}
in6ai = 0x561fff28e8f8
in6ailen = 6
seen_ipv4 = true
seen_ipv6 = true
check_pf_called = true
end = 0x7fffa2434328
naddrs = 0
__PRETTY_FUNCTION__ = "getaddrinfo"
#7  0x561ffd98218e in ?? ()
No symbol table info available.
#8  0x561ffd98359d in ?? ()
No symbol table info available.
#9  0x561ffd974652 in ?? ()
No symbol table info available.
#10 0x561ffd97c0c8 in ?? ()
No symbol table info available.
#11 0x561ffd96b73b in ?? ()
No symbol table info available.
#12 0x7faff803d1c1 in __libc_start_main (main=0x561ffd96b690, argc=1, 
argv=0x7fffa2435948, init=, fini=, 
rtld_fini=, stack_end=0x7fffa2435938) at ../csu/libc-start.c:308
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -9070595946702466195, 
94695398488480, 140735915710784, 0, 0, -3324084521362287763, 
-3351014314436619411}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 
0x7fffa2435958, 0x7faff953f150}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= -1572644520}}}
not_first_call = 
#13 0x561ffd96b9ca in ?? ()
No symbol table info available.
--- source code stack trace ---
#0  0x7faff80f04eb in __getdents (fd=3, buf=0x561fff2a96d0 "\035g\233", 
, nbytes=32768) at 
../sysdeps/unix/sysv/linux/getdents.c:96
  [Error: getdents.c was not found in source tree]
#1  0x7faff80f00b5 in __readdir (dirp=0x561fff2a96a0) at 
../sysdeps/posix/readdir.c:65
  [Error: readdir.c was not found in source tree]
#2  0x7faff55e826e in ?? () from /lib/x86_64-linux-gnu/libnss_libvirt.so.2
#3  0x7faff55cebdf in ?? () from 

[Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

[Dimitri John Ledkov]

I am wondering if this should be merged as a distro patch, or not.

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

Title:
  /dev/disk/by-path not properly populated for (e)SATA port multiplier
  disks

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  We have a just-installed Ubuntu 16.04 LTS machine with a number of
  disks behind port-multiplier eSATA ports, all of them driven by a SiI
  3124 controller (sata_sil24 kernel driver). Our machine sees all disks
  on all channels, however under 16.04 only one disk from each channel
  shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id
  and /dev/disk/by-uuid). For our usage this is a severe defect because
  we rotate disks in and out of the external enclosure and rely on
  mounting specific slots in the external enclosure through /dev/disk
  /by-path.

  This did not happen in Ubuntu 12.04 LTS, the release that this machine
  was previously running.

  According to 'udevadm info --export-db' and 'udevadm test-builtin
  path_id' and so on, systemd's udev stuff is assigning all drives
  behind the same port the same disk/by-path data (ID_PATH et al). In
  'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show
  a difference in the target portion of PCI path, eg:

P: 
/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
P: 
/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb

  However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH'
  portions do not. For both devices above, we see:

S: disk/by-path/pci-:02:00.0-ata-1
E: ID_PATH=pci-:02:00.0-ata-1

  Naturally only one device can have a /dev/disk/by-
  path/pci-:02:00.0-ata-1 symlink, so instead of four disks per
  channel in /dev/disk/by-path we see one.

  Ubuntu release: 16.04

  Package versions from 'apt-cache policy udev systemd':
  udev:
Installed: 229-4ubuntu7
  systemd:
Installed: 229-4ubuntu7

  'journalctl -b' reports that during boot systemd does report some
  'appeared twice with different sysfs paths' notes, eg:

  Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath-
  pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by
  \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared
  twice with different sysfs paths
  
/sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:3:0/0:3:0:0/block/sdd/sdd1
  and
  
/sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1

  However it doesn't seem to be reporting this for all port-multiplier
  drives and their partitions.

  If it would be useful I can attach full 'udevadm info --export-db'
  output or the like.

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

-- 
Mailing list: https://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 1737318] Re: dependency not met

[Bruce Miller]

Incorrect. I am *_not_* installing packages from artful-proposed. I do *_not_* 
upgrade packages individually.
Here is my sources.list:
deb http://ca.archive.ubuntu.com/ubuntu/ artful main restricteddeb 
http://ca.archive.ubuntu.com/ubuntu/ artful-updates main restricteddeb 
http://ca.archive.ubuntu.com/ubuntu/ artful universedeb 
http://ca.archive.ubuntu.com/ubuntu/ artful-updates universedeb 
http://ca.archive.ubuntu.com/ubuntu/ artful multiversedeb 
http://ca.archive.ubuntu.com/ubuntu/ artful-updates multiversedeb 
http://ca.archive.ubuntu.com/ubuntu/ artful-backports main restricted universe 
multiversedeb http://archive.canonical.com/ubuntu artful partnerdeb 
http://security.ubuntu.com/ubuntu artful-security main restricteddeb 
http://security.ubuntu.com/ubuntu artful-security universedeb 
http://security.ubuntu.com/ubuntu artful-security multiversedeb 
http://www.duinsoft.nl/pkg debs all
This is the update alias which I run daily (and which is throwing the errors 
which I have reported):
sudo apt-get update && sudo aptitude --with-recommends safe-upgrade && sudo 
aptitude --with-recommends full-upgrade && sudo apt-get upgrade && sudo apt-get 
dist-upgrade && sudo apt autoremove && sudo aptitude autoclean
 


  From: Dimitri John Ledkov 
 To: b...@brmiller.ca 
 Sent: Tuesday, December 12, 2017 5:50 AM
 Subject: [Bug 1737318] Re: dependency not met
   
You should upgrade all packages together, not individually. 
You appear to be trying to install packages from artful-proposed, which is not 
recommended for daily use, unless you are testing SRU fixes.
If you do not intend to validate pre-release test packages, please disable 
artful-proposed on your system.

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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1737318

Title:
  dependency not met

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The following packages have unmet dependencies:
  libnss-resolve : Depends: systemd (= 234-2ubuntu12.1) but 234-2ubuntu12.2 is 
to be installed
  open: 23; closed: 490; defer: 5; conflict: 5                                  
                                                                                
                                                    .The following actions will 
resolve these dependencies:

      Keep the following packages at their current version:                    
  1)    libpam-systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]
  2)    libsystemd0 [234-2ubuntu12.1 (artful-security, artful-updates, now)]  
  3)    systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libnss-resolve 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Dec  9 07:40:09 2017
  InstallationDate: Installed on 2016-10-02 (432 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160512)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (46 days ago)

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

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

Title:
  dependency not met

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The following packages have unmet dependencies:
   libnss-resolve : Depends: systemd (= 234-2ubuntu12.1) but 234-2ubuntu12.2 is 
to be installed
  open: 23; closed: 490; defer: 5; conflict: 5  

.The following actions will 
resolve these dependencies:

   Keep the following packages at their current version:
  1) libpam-systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]
  2) libsystemd0 [234-2ubuntu12.1 (artful-security, artful-updates, now)]   
  3) systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libnss-resolve 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Dec  9 07:40:09 2017
  InstallationDate: Installed on 2016-10-02 (432 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160512)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (46 days ago)

To manage notifications about this 

[Touch-packages] [Bug 1692353] Re: systemd-fsckd : useless CR displayed on console

[Dimitri John Ledkov]

Interesting.

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

Title:
  systemd-fsckd : useless CR displayed on console

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My system is "Ubuntu 16.04.2 LTS" (grep DISTRIB_DESCRIPTION /etc/lsb-
  release).

  The systemd package is installed:
$ dpkg -l | grep systemd
> systemd 229-4ubuntu17 

  I noticed that approximately 15 seconds after the boot, a useless
  Carriage Return ('\r') is displayed on the console (/dev/console).
  This character interacts with the display of the user currently logued in
  on the console. This screws the current line, when users is pressing keys.

  After monitoring system activity, I found the culprit:
/lib/systemd/system/systemd-fsckd.service

  To test, run:
service systemd-fsckd stop# In case, it is still running.
service systemd-fsckd start
  Go to the console, wait for approximately 15 seconds, and you see the cursor
  jumping from its current position to the beginning of the line. This is the 
BUG.
  Note: the console is not the X11 terminal (xterm, lxterminal, etc.) ; the
  console is the text tty reached with Control-Alt-F1.

  The systemd-fsckd.service starts the following daemon:
/lib/systemd/systemd-fsckd
  This is the daemon which displays two useless '\r' characters.

  I went to:
http://packages.ubuntu.com/xenial/systemd

  I downloaded:

http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu10.debian.tar.xz

  The file debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch
  contains:
  +static int manager_write_console(Manager *m, const char *message) {
  [...]
  +if (message) {
  +fprintf(console, "\r%s\r%n", message, );
  +if (m->clear  < (size_t)l)
  +m->clear = (size_t)l;
  +} else {
  +fputc('\r', console);
  +for (j = 0; j < m->clear; j++)
  +fputc(' ', console);
  +fputc('\r', console);
  +}

  So, when no message was previously displayed, "m->clear" is still set
  to 0.

  Then, when the program ends it calls:
  +/* clear last line */
  +manager_write_console(m, NULL);

  However, in the "else" above, two '\r' characters are displayed, surrounding
  no space characters.

  So, when no message was previously displayed, there is nothing to clear, so
  no '\r' character to display.

  A trivial patch is attached. It is untested.

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

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

[Touch-packages] [Bug 1692353] Re: systemd-fsckd : useless CR displayed on console

[Dimitri John Ledkov]

Didrocks, would you be able to review this patch?

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  systemd-fsckd : useless CR displayed on console

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My system is "Ubuntu 16.04.2 LTS" (grep DISTRIB_DESCRIPTION /etc/lsb-
  release).

  The systemd package is installed:
$ dpkg -l | grep systemd
> systemd 229-4ubuntu17 

  I noticed that approximately 15 seconds after the boot, a useless
  Carriage Return ('\r') is displayed on the console (/dev/console).
  This character interacts with the display of the user currently logued in
  on the console. This screws the current line, when users is pressing keys.

  After monitoring system activity, I found the culprit:
/lib/systemd/system/systemd-fsckd.service

  To test, run:
service systemd-fsckd stop# In case, it is still running.
service systemd-fsckd start
  Go to the console, wait for approximately 15 seconds, and you see the cursor
  jumping from its current position to the beginning of the line. This is the 
BUG.
  Note: the console is not the X11 terminal (xterm, lxterminal, etc.) ; the
  console is the text tty reached with Control-Alt-F1.

  The systemd-fsckd.service starts the following daemon:
/lib/systemd/systemd-fsckd
  This is the daemon which displays two useless '\r' characters.

  I went to:
http://packages.ubuntu.com/xenial/systemd

  I downloaded:

http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu10.debian.tar.xz

  The file debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch
  contains:
  +static int manager_write_console(Manager *m, const char *message) {
  [...]
  +if (message) {
  +fprintf(console, "\r%s\r%n", message, );
  +if (m->clear  < (size_t)l)
  +m->clear = (size_t)l;
  +} else {
  +fputc('\r', console);
  +for (j = 0; j < m->clear; j++)
  +fputc(' ', console);
  +fputc('\r', console);
  +}

  So, when no message was previously displayed, "m->clear" is still set
  to 0.

  Then, when the program ends it calls:
  +/* clear last line */
  +manager_write_console(m, NULL);

  However, in the "else" above, two '\r' characters are displayed, surrounding
  no space characters.

  So, when no message was previously displayed, there is nothing to clear, so
  no '\r' character to display.

  A trivial patch is attached. It is untested.

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

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

[Touch-packages] [Bug 1737732] [NEW] systemd-resolve default nameserver 127.0.0.53 disables resolution in guest systems

[shemgp]

Public bug reported:

When the default nameserver, which is set by systemd-resolve, is
127.0.0.53, guest systems (libvirtd, lxc, snaps, anbox, etc) won't work
unless there's a non 127.0.0.x nameserver (eg. 8.8.8.8) in
/etc/resolv.conf.  Because the dnsmasq in these guest machines try to
resolve to 127.0.0.53 and can't find the real nameserver.

The quick fix is of course to:

sudo rm /etc/resolv.conf
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

But that's not the default.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.2
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec 12 20:01:39 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (805 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 34361A0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash nomodset vga=792 
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GCETA3WW (2.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 34361A0
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA3WW(2.63):bd09/24/2015:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X220
dmi.product.name: 34361A0
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
mtime.conffile..etc.systemd.journald.conf: 2017-09-12T19:43:29.248459

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


** Tags: amd64 apport-bug artful package-from-proposed third-party-packages

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

Title:
  systemd-resolve default nameserver 127.0.0.53 disables resolution in
  guest systems

Status in systemd package in Ubuntu:
  New

Bug description:
  When the default nameserver, which is set by systemd-resolve, is
  127.0.0.53, guest systems (libvirtd, lxc, snaps, anbox, etc) won't
  work unless there's a non 127.0.0.x nameserver (eg. 8.8.8.8) in
  /etc/resolv.conf.  Because the dnsmasq in these guest machines try to
  resolve to 127.0.0.53 and can't find the real nameserver.

  The quick fix is of course to:

  sudo rm /etc/resolv.conf
  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  But that's not the default.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 20:01:39 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (805 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash nomodset vga=792 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA3WW(2.63):bd09/24/2015:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2017-09-12T19:43:29.248459

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

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

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

[Vlad Orlov]

** Tags added: bionic

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

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

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1730272] Re: package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

[Terence Cummins]

Thank you.


On 12/12/17 22:31, Dimitri John Ledkov wrote:
> Preparing to unpack .../systemd-sysv_234-2ubuntu12.1_amd64.deb ...
> Unpacking systemd-sysv (234-2ubuntu12.1) over (232-21ubuntu7.1) ...
> Removing 'diversion of 
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
> systemd-shim'
> dpkg-divert: error: rename involves overwriting 
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
>different file 
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
> not allowed
> dpkg: error processing archive 
> /var/cache/apt/archives/systemd-sysv_234-2ubuntu12.1_amd64.deb (--unpack):
>   subprocess installed post-removal script returned error exit status 2
>
>
> You should not have "systemd-shim" package installed, please try to remove it.
>

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

Title:
  package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-shim  also failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: systemd-sysv 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Mon Nov  6 10:19:01 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2014-02-21 (1354 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  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
  SourcePackage: systemd
  Title: package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: Upgraded to artful on 2017-11-05 (0 days ago)

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Launchpad Bug Tracker]

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

** Changed in: gnome-shell (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/1732612

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Dimitri John Ledkov]

Once the kernel is fixed, are there any changes that are required to
systemd/udev?

** Changed in: systemd (Ubuntu Bionic)
   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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  In Progress
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
 

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Alan Pope  濾]

On my Unity session on 17.10 printscreen doesn't work, neither does
ALT+Printscreen (it triggers HUD), nor CTRL+ALT+T to open terminal.
Seems a bunch of them don't work.

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[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/1732612

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1733468] Re: do-release-upgrade failed to update to systemd 229-4ubuntu21

[Dimitri John Ledkov]

This is very odd:

Initializing machine ID from D-Bus machine ID.
Adding group `systemd-journal' (GID 120) ...
Done.
You are required to change your password immediately (root enforced)
chfn: PAM: Authentication token is no longer valid; new one required
adduser: `/usr/bin/chfn -f systemd Time Synchronization systemd-timesync' 
returned error code 1. Exiting.
dpkg: error processing package systemd (--configure):
 subprocess installed post-installation script returned error exit status 1

I'm not sure if digitalocean images are customized, in a way that
prevent upgrades. Can you try creating system systemd-timesync user, and
re-attempting the upgrade?

$ sudo adduser --quiet --system --group --no-create-home --home /run/systemd \
--gecos "systemd Time Synchronization" systemd-timesync

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

Title:
  do-release-upgrade failed to update to systemd 229-4ubuntu21

Status in systemd package in Ubuntu:
  New

Bug description:
  This is going from Ubuntu 14 to 16 LTS via do-release-upgrade on
  DigitalOcean.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu21
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Mon Nov 20 22:08:04 2017
  DuplicateSignature: package:systemd:229-4ubuntu21:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-18 (1312 days ago)
  InstallationMedia:
   
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: root=LABEL=DOROOT ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.0.1ubuntu2.17
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-resolved.service → 
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-11-21 (0 days ago)
  dmi.bios.date: 11/03/2016
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20161103
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20161103:bd11/03/2016:svnDigitalOcean:pnDroplet:pvr20161103:cvnBochs:ct1:cvr:
  dmi.product.name: Droplet
  dmi.product.version: 20161103
  dmi.sys.vendor: DigitalOcean

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Dimitri John Ledkov]

Not sure how any of this helps, I would require somebody with
graphics/keyboard stack to understand what/where has regressed.

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1732489] Re: TMPTIME is not honoured

[Dimitri John Ledkov]

I fear, I agree with debian bug report, the ship has sailed to get this
migration right =/

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  TMPTIME is not honoured

Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  TMPTIME is incorrectly migrated on an upgrade from Trusty to Xenial.

  tmp.conf uses D where it should be d. This also has the effect of
  wiping /tmp no matter what.

  This is fixed in Debian.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795269

  This could result in data loss, although storing non-volatile files in
  /tmp is madness.

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

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

[Touch-packages] [Bug 1732769] Re: package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dimitri John Ledkov]

The system appears to have invalid init.d scripts, with invalid headers.

Please fix those, or find who/where/why have them shipped:

insserv: warning: script 'queues-torque.sh' missing LSB tags and overrides
insserv: There is a loop between service torque-scheduler and queues-torque.sh 
if stopped
insserv:  loop involving service queues-torque.sh at depth 2
insserv:  loop involving service torque-scheduler at depth 1
insserv: Stopping queues-torque.sh depends on torque-scheduler and therefore on 
system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package udev (--configure):
 subprocess installed post-installation 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1732769

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I cannot say more than the summary/title

  The number 21 is not in the list on display

  Thanks to help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Thu Nov 16 19:57:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-30 (474 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision M6500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0R1203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6500
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1736240] Re: package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Julian Andres Klode]

Well, it was an update-manager update. I'm not sure why the user
triggered one, but probably a high-level graphical tool should not allow
that. For APT, it does not make sense to prevent people from upgrading
itself. That said, livecd tools could create a pre-install hook that
fails with "This is a live system, it does not support upgrades"?

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

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

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in apt package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  I can't install updates, use my touchpad or open drop down menu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Mon Dec  4 19:56:22 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: 
file=/cdrom/multiboot/hostname-16.04.3-desktop-amd64/preseed/hostname.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/hostname-16.04.3-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/hostname-16.04.3-desktop-amd64/casper/ 
initrd=/multiboot/hostname-16.04.3-desktop-amd64/casper/initrd.lz quiet splash 
--- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AC
  dmi.board.vendor: HP
  dmi.board.version: 53.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd08/21/2017:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AC:rvr53.27:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe

[Dimitri John Ledkov]

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

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

Title:
  On upgrade, daemon-reexec should only be issued if safe

Status in lxc package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Dear all,

  Following up the bug report #1713674, when executing systemd in a
  hardened LXC context, it might not be suitable to reexec systemd
  daemon, that would not be able to perform.

  For instance, in our LXC, we drop several capabilities, including
  sys_admin and we set /sys to read-only (in which, systemd will find
  its cgroups). This means, systemd cannot be reexecuted, it will fail
  to restart and will freeze (properly) at restart making the LXC
  container in frozen state (still working, but no new services
  startable, no interaction with systemd possible anymore).

  When upgrading systemd the debian package, as postinst, will always
  attempt to reexecute systemd, possibly breaking every other upgrade
  where a daemon restart is made in postinst, and leaving the system in
  a degraded state.

  It would likely be appropriate the check whether the reexecute can
  work will before performing it: checking capabilities, sys mount point
  perms, etc. If not applicable, not performing a reexucte and possibly
  print a message to the user.

  Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.

  Cheers

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

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

[Touch-packages] [Bug 1730272] Re: package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

[Dimitri John Ledkov]

Preparing to unpack .../systemd-sysv_234-2ubuntu12.1_amd64.deb ...
Unpacking systemd-sysv (234-2ubuntu12.1) over (232-21ubuntu7.1) ...
Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
dpkg: error processing archive 
/var/cache/apt/archives/systemd-sysv_234-2ubuntu12.1_amd64.deb (--unpack):
 subprocess installed post-removal script returned error exit status 2


You should not have "systemd-shim" package installed, please try to remove it.

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

Title:
  package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-shim  also failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: systemd-sysv 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Mon Nov  6 10:19:01 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2014-02-21 (1354 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  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
  SourcePackage: systemd
  Title: package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: Upgraded to artful on 2017-11-05 (0 days ago)

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

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

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

For the record I'd like to mention that the key information to spot the
root cause of this bug was provided in Christophe's comment #10, even if
the solutions differ.

Thanks, Christophe, for your helpful contribution!

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Artful:
  In Progress

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Touch-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:

[Valentin Stauber]

Same issue here, Ubuntu 17.10

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

Title:
  Sorry something went wrong GDBus:

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After applying the latest update the Software-center now opens but
  still has a problem.

  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".

  Some of the links to the software doesn't work.
  Some of the buttons of categories doesn't work.
  Updates never show "software to be updated" anymore

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

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

[Touch-packages] [Bug 1736740] Re: package systemd-sysv (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Robert Udah]

This no longer applies to me

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

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

Title:
  package systemd-sysv (not installed) failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  package systemd-sysv (not installed) failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-135-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Dec  6 14:05:38 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-11-03 (1129 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package systemd-sysv (not installed) failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2017-12-06 (0 days ago)

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

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

[Touch-packages] [Bug 1736740] Re: package systemd-sysv (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Robert Udah]

I was trying to upgrade to Zesty Zapus 17.04 
I have performed a full install from scratch.

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

Title:
  package systemd-sysv (not installed) failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  package systemd-sysv (not installed) failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-135-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Dec  6 14:05:38 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-11-03 (1129 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package systemd-sysv (not installed) failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2017-12-06 (0 days ago)

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

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

[Touch-packages] [Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

[Michael Thayer]

Actually Lubuntu probably doesn't support Wayland at all.

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

Title:
  Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

Status in Virtualbox:
  Invalid
Status in console-setup package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Fix Released

Bug description:
  (Content copied from "Ubuntu 14.10 ISO live boot ends up with a
  corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz)

  Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO 
ends up with a corrupted screen. See the screenshot:
  https://launchpadlibrarian.net/186864347/ubu.png

  Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7)
  fixes the display.

  I think that this might be a problem with resolution setting:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  ```

  After switching back and forth to the tty7 (what fixes the display)
  the log says:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
  00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=720x400
  00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1
  00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler..
  00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768
  00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use 
VGA device content..
  ```

  I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens
  on both of them.

  You can download the ISO images of these two systems here:

   https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10
  -desktop-amd64.iso

   http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-
  gnome-14.10-desktop-amd64.iso

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

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

[Touch-packages] [Bug 1734344] Re: systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21

[Dimitri John Ledkov]

The systemd-fsckd test case got improved on s390x to handle zipl
bootloader.

However, it now only sometimes passes, as it seems to timeout and/or
being flakey.

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

Title:
  systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20171123_190248_4f60f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20171123_123920_4f60f@/log.gz

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

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

[Touch-packages] [Bug 1734344] Re: systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21

[Dimitri John Ledkov]

I shall SRU ssytemd-fsckd test case fixes back, however, I also think I
should mark it as expect-fail somehow on s390x only.

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

Title:
  systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20171123_190248_4f60f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20171123_123920_4f60f@/log.gz

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

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

[Touch-packages] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

[Dimitri John Ledkov]

These did not make v235, I guess you meant v236. Description updated.

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

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
   Status: New

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

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

** Description changed:

  Hey everyone,
  
  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified hierarchy
  or when running with a liblxc driver that doesn't yet know how to handle
  the unified cgroup hierarchy. I've pushed patches to systemd upstream
  that let systemd ingnore the non-delegated unified hierarchy. The
  relevant commits are:
  
  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0
  
- These patches will be in 235 but should be backported from xenial
+ These patches will be in 236 but should be backported from xenial
  upwards.
  
  Christian

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

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

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

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

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

[Touch-packages] [Bug 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS

[Dimitri John Ledkov]

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

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

Title:
  systemd-sysctl: exit gracefully on EPERM/EACCESS

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New

Bug description:
  Hi everyone,

  systemd-sysctl in systemd versions prior to 232 will exit with FAILED
  when not being able to apply kernel variables. In containers it should
  simply move on and exit with SUCCESS. Upstream systemd carries
  appropriate patches for this already. The relevant commits are:

  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa

  these should be backported to xenial's systemd.

  Christian

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

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

[Touch-packages] [Bug 1734344] Re: systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21

[Dimitri John Ledkov]

Not sure about amd64 failure.

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

Title:
  systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20171123_190248_4f60f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20171123_123920_4f60f@/log.gz

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

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

[Touch-packages] [Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

[Michael Thayer]

I would just point out that the problem with Lubuntu live which was
reported and which I reproduced would force a fall-back from Wayland to
X.Org.

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

Title:
  Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

Status in Virtualbox:
  Invalid
Status in console-setup package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Fix Released

Bug description:
  (Content copied from "Ubuntu 14.10 ISO live boot ends up with a
  corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz)

  Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO 
ends up with a corrupted screen. See the screenshot:
  https://launchpadlibrarian.net/186864347/ubu.png

  Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7)
  fixes the display.

  I think that this might be a problem with resolution setting:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  ```

  After switching back and forth to the tty7 (what fixes the display)
  the log says:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
  00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=720x400
  00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1
  00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler..
  00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768
  00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use 
VGA device content..
  ```

  I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens
  on both of them.

  You can download the ISO images of these two systems here:

   https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10
  -desktop-amd64.iso

   http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-
  gnome-14.10-desktop-amd64.iso

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

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

[Touch-packages] [Bug 1736240] Re: package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dimitri John Ledkov]

Hm, posibly an apt bug, we should not be upgrading livecd sessions.

** Also 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1736240

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in apt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I can't install updates, use my touchpad or open drop down menu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Mon Dec  4 19:56:22 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: 
file=/cdrom/multiboot/hostname-16.04.3-desktop-amd64/preseed/hostname.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/hostname-16.04.3-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/hostname-16.04.3-desktop-amd64/casper/ 
initrd=/multiboot/hostname-16.04.3-desktop-amd64/casper/initrd.lz quiet splash 
--- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AC
  dmi.board.vendor: HP
  dmi.board.version: 53.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd08/21/2017:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AC:rvr53.27:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1735296] Re: systemd-resolved.service

[Dimitri John Ledkov]

Correct, purging resolvconf is only supported "out of the box"/"just
works" in 17.10 and up, as resolvconf/libnss-resolve there have the
correct maintainer scripts to do the tansition.

I do not recommend using systemd-resolve in xenial, as it does not have
a stub resolver available, and software that does not use nss will not
be able to have any network resolution without bypassing resolved. Using
systemd-resolved without resolvconf is currently only best supported on
17.10+.

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

** Summary changed:

- systemd-resolved.service
+ systemd-resolved.service doesn't play nice if resolvconf is removed on 
xenial, works on artful+

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

Title:
  systemd-resolved.service doesn't play nice if resolvconf is removed on
  xenial, works on artful+

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  if you purge resolvconf on Xenial and want systemd-resolve the link is
  not update and its doesn't use systemd-resolce cache

  1) 
  Description:Ubuntu 16.04.3 LTS
  Release:16.04

  2) systemd  229-4ubuntu21  amd64  system and service manager

  3)
  ls -l /etc/resolv.conf
  lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  aptitude purge -y resolvconf

  

  ls -l /run/systemd/resolve
  total 4
  -rw-r--r-- 1 systemd-resolve systemd-resolve 381 Nov 29 22:42 resolv.conf

  ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf

  # on it's working
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04
  systemd --version
  235

  ls -l /run/systemd/resolve/
  total 8
  -rw-r--r-- 1 systemd-resolve systemd-resolve 608 Nov 29 16:36 resolv.conf
  -rw-r--r-- 1 systemd-resolve systemd-resolve 264 Nov 29 16:36 stub-resolv.conf

  ls -l /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 Oct 25 10:38 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  
  4)
  ## 
  ls -l /etc/resolv.conf
  lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  systemctl status/restart systemd-resolved.service

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

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

[Touch-packages] [Bug 1736240] Re: package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dimitri John Ledkov]

cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file or 
directory
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1

This looks odd... Are you inside a livecd session? Upgrades on livecd
are not supported.

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

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in apt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I can't install updates, use my touchpad or open drop down menu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Mon Dec  4 19:56:22 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: 
file=/cdrom/multiboot/hostname-16.04.3-desktop-amd64/preseed/hostname.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/hostname-16.04.3-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/hostname-16.04.3-desktop-amd64/casper/ 
initrd=/multiboot/hostname-16.04.3-desktop-amd64/casper/initrd.lz quiet splash 
--- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AC
  dmi.board.vendor: HP
  dmi.board.version: 53.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd08/21/2017:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AC:rvr53.27:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1735703] Re: package libnss-resolve:amd64 (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dimitri John Ledkov]

Note, on 17.10 defautl configuration libnss-resolve is not longer used
by default, so you may remove it.

Also note:
Failed to enable unit: Unit file /etc/systemd/system/systemd-resolved.service 
is masked.
dpkg: error processing package libnss-resolve:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1

This is not the default configuration, please do:
$ sudo systemctl unmask systemd-resolved

To return your system into the default configuration.

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

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

Title:
  package libnss-resolve:amd64 (not installed) failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Just after update from Ubuntu 16.04 LTS up-to-date

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libnss-resolve:amd64 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  AptOrdering:
   libnss-resolve:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Dec  1 11:48:22 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-06 (25 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  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: systemd
  Title: package libnss-resolve:amd64 (not installed) failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to artful on 2017-12-01 (0 days ago)

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

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

[Touch-packages] [Bug 1734943] Re: no internet access, from any wi-fi network or wired network

[Dimitri John Ledkov]

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

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

Title:
  no internet access, from any wi-fi network or wired network

Status in network-manager package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Today, when i started Ubuntu. In bar, on the network icon appear a "?"
  symbol. I tried to connect Ubuntu to internet with a wired cable and
  another wi-fi network. He's connect to wi-fi and wired cable network
  but appears a "?" symbol in the network icon and i don't have access
  on the internet. Sorry for my bad english  :))) Thank you!

  P.S. i use Ubuntu 17.10

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

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