[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-24 Thread Michael Biebl
Turns out, the missing fsck progress bar is a regression:
https://github.com/systemd/systemd/issues/17157

** Bug watch added: github.com/systemd/systemd/issues #17157
   https://github.com/systemd/systemd/issues/17157

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [Impact]

   * fsck messages is shown by plymouth, despite all fscks already
  completed.

  [Test Case]

   * Install Ubuntu Desktop with full disk encryption

   * Observe that fsck messages (press ctrl+c) is shown, and remains
  there on screen for a little while as plymouth transitions to gdm

   * After installing the update, observe that when fsck completes the
  messages are cleared and the transition to gdm is done without
  fsck/ctrl+c message present.

   * After this change lands in -updates, and daily desktop images are
  built with this, double check that casper-md5sum transition is also
  smooth.

  
  [Regression Potential] 

   * plymouth spinner theme is adjusted to clear the footer, at the end
  of fsck, even if systemd-fsckd didn't do that. At the moment there are
  two consumers of the fsck apis systemd-fsckd & casper-md5sum used on
  installed systems and live-isos respectively. If something else pushes
  messages to the footer, they might get cleared at the end of fsck.

  [Other Info]
   
   * Original bug report

  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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

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


[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-24 Thread Michael Biebl
>From my personal POV, I consider the progress bar more important then the 
>ability to interrupt fsck with CTRL+C.
Nowadays, SSDs are much more common and enable_periodic_fsck = 0 has been the 
default for many years now. So this is much less of an issue today then it was 
back in 2015, I think.

I think text-only boot (without plymouth and without quiet) has a
reasonable enough progress report from fsck. Without fsckd, we'd have no
progress report in plymouth and quiet text-only boots.

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [Impact]

   * fsck messages is shown by plymouth, despite all fscks already
  completed.

  [Test Case]

   * Install Ubuntu Desktop with full disk encryption

   * Observe that fsck messages (press ctrl+c) is shown, and remains
  there on screen for a little while as plymouth transitions to gdm

   * After installing the update, observe that when fsck completes the
  messages are cleared and the transition to gdm is done without
  fsck/ctrl+c message present.

   * After this change lands in -updates, and daily desktop images are
  built with this, double check that casper-md5sum transition is also
  smooth.

  
  [Regression Potential] 

   * plymouth spinner theme is adjusted to clear the footer, at the end
  of fsck, even if systemd-fsckd didn't do that. At the moment there are
  two consumers of the fsck apis systemd-fsckd & casper-md5sum used on
  installed systems and live-isos respectively. If something else pushes
  messages to the footer, they might get cleared at the end of fsck.

  [Other Info]
   
   * Original bug report

  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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

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


[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-24 Thread Michael Biebl
As for text-only boot: Maybe we could convince upstream to enable
verbose mode once an fsck takes longer then say 30s (similar to how the
eye-of-cyclon animation kicks in when services take a long time to
start). With something like that implemented, dropping fsckd might be an
option, I think.

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [Impact]

   * fsck messages is shown by plymouth, despite all fscks already
  completed.

  [Test Case]

   * Install Ubuntu Desktop with full disk encryption

   * Observe that fsck messages (press ctrl+c) is shown, and remains
  there on screen for a little while as plymouth transitions to gdm

   * After installing the update, observe that when fsck completes the
  messages are cleared and the transition to gdm is done without
  fsck/ctrl+c message present.

   * After this change lands in -updates, and daily desktop images are
  built with this, double check that casper-md5sum transition is also
  smooth.

  
  [Regression Potential] 

   * plymouth spinner theme is adjusted to clear the footer, at the end
  of fsck, even if systemd-fsckd didn't do that. At the moment there are
  two consumers of the fsck apis systemd-fsckd & casper-md5sum used on
  installed systems and live-isos respectively. If something else pushes
  messages to the footer, they might get cleared at the end of fsck.

  [Other Info]
   
   * Original bug report

  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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

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


[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-23 Thread Michael Biebl
I would be happy to see this patch merged upstream.
There was an attempt a few years ago:
https://lists.freedesktop.org/archives/systemd-devel/2015-March/029186.html

Eventually it was removed again: 
https://github.com/systemd/systemd/commit/96d9117ad2db7d8c13f7898127eee8939e88daf1
https://lists.freedesktop.org/archives/systemd-devel/2015-April/030175.html

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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

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


[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2019-09-05 Thread Michael Biebl
It would be good adding this information to the upstream bug tracker.

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * The keyboard on the graphical login screen started on VT1 may stop
  working and or keypresses including passwords are leaked to the
  terminal console running 'behind' the graphical login screen or
  environment.

  [Test Case]

   * Reboot after installing the fixed systemd package.
   * Install sysdig
   * Start sysdig on a remote connection or on a terminal console:
$ sudo sysdig evt.type=ioctl | grep  request=4B4
   * While sysdig is running log in and out 3 times in GDM and press a few keys 
in the graphical session to see if keyboard still works
   * Log in and out on an other terminal console, too, running a few commands 
while being logged in to ensure that keyboard is working.
   * Observe that on terminal consoles the monitored keyboard setter ioctl is 
called with argument=3, but where the graphical screen is active only 
argument=4 is used, unlike with the buggy version observed in 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14

  [Regression Potential]

   * The fix checks the current keyboard mode of the VT and allows only
  safe mode switches. The potential regression could be not allowing a
  valid mode switch keeping a keyboard in a non-operational mode.
  Testing covers that by typing the keyboard.

  
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2019-09-05 Thread Michael Biebl
Looking at the discussion at
https://gitlab.freedesktop.org/xorg/xserver/issues/857#note_201402 this
might be a bug in plymouth which is supposedly fixed in plymouth 0.9.4.

Could users who can reliably reproduce the issue post if they have
plymouth installed and if so, which version?

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #857
   https://gitlab.freedesktop.org/xorg/xserver/issues/857

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * The keyboard on the graphical login screen started on VT1 may stop
  working and or keypresses including passwords are leaked to the
  terminal console running 'behind' the graphical login screen or
  environment.

  [Test Case]

   * Reboot after installing the fixed systemd package.
   * Install sysdig
   * Start sysdig on a remote connection or on a terminal console:
$ sudo sysdig evt.type=ioctl | grep  request=4B4
   * While sysdig is running log in and out 3 times in GDM and press a few keys 
in the graphical session to see if keyboard still works
   * Log in and out on an other terminal console, too, running a few commands 
while being logged in to ensure that keyboard is working.
   * Observe that on terminal consoles the monitored keyboard setter ioctl is 
called with argument=3, but where the graphical screen is active only 
argument=4 is used, unlike with the buggy version observed in 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14

  [Regression Potential]

   * The fix checks the current keyboard mode of the VT and allows only
  safe mode switches. The potential regression could be not allowing a
  valid mode switch keeping a keyboard in a non-operational mode.
  Testing covers that by typing the keyboard.

  
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2019-09-05 Thread Michael Biebl
@rbalint if you can reliably reproduce the issue, it would probably be a
good idea if you follow up on that upstream bug tracker

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * The keyboard on the graphical login screen started on VT1 may stop
  working and or keypresses including passwords are leaked to the
  terminal console running 'behind' the graphical login screen or
  environment.

  [Test Case]

   * Reboot after installing the fixed systemd package.
   * Install sysdig
   * Start sysdig on a remote connection or on a terminal console:
$ sudo sysdig evt.type=ioctl | grep  request=4B4
   * While sysdig is running log in and out 3 times in GDM and press a few keys 
in the graphical session to see if keyboard still works
   * Log in and out on an other terminal console, too, running a few commands 
while being logged in to ensure that keyboard is working.
   * Observe that on terminal consoles the monitored keyboard setter ioctl is 
called with argument=3, but where the graphical screen is active only 
argument=4 is used, unlike with the buggy version observed in 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14

  [Regression Potential]

   * The fix checks the current keyboard mode of the VT and allows only
  safe mode switches. The potential regression could be not allowing a
  valid mode switch keeping a keyboard in a non-operational mode.
  Testing covers that by typing the keyboard.

  
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1639050] Re: Wrong package section, should be in "introspection"

2016-11-16 Thread Michael Biebl
In Debian, the values in debian/control are only used when the package is 
uploaded intially to the archive. The override entry is created from that.
Changing the contents of the archive override is done by the ftp-masters. If 
you later change the contents of debian/control does not have an influence on 
the override file.

So, this needs to be assigned to your ftp masters, they need to fix the
overrides and should be able to do that in one go.

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

Title:
  Wrong package section, should be in "introspection"

Status in webapps-sprint:
  New
Status in libsignon-glib package in Ubuntu:
  Confirmed

Bug description:
  Packages shipping gobject introspection should be in the dedicated
  section "introspection". This archive section was added a while ago,
  see also the corresponding entry in the debian policy 3.9.3.0:

  2.6. Version 3.9.3.0
  

   Released February, 2012.

   2.4
New archive sections _education_, _introspection_, and
_metapackages_ added.

  
  Packages shipping gobject introspection should be named 
gir1.2-NAMESPACE-VERSION.

  Based on the output of apt-cache, the following packages are in the
  wrong section. I didn't file a separate bug for all of them. I would
  appreciate if you can adjust the archive section for all the following
  packages in one go.

  #!/bin/bash

  while read pkg ; do
 apt-cache show $pkg | grep Section | grep -v introspection -q && echo 
$pkg
  done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' )

  
  gir1.2-accounts-1.0
  gir1.2-accountsservice-1.0
  gir1.2-appindicator-0.1
  gir1.2-appindicator3-0.1
  gir1.2-atk-1.0
  gir1.2-atspi-2.0
  gir1.2-bamf-3
  gir1.2-cheese-3.0
  gir1.2-clutter-1.0
  gir1.2-cogl-1.0
  gir1.2-coglpango-1.0
  gir1.2-colord-1.0
  gir1.2-dbusmenu-glib-0.4
  gir1.2-dbusmenu-gtk-0.4
  gir1.2-dbusmenu-gtk3-0.4
  gir1.2-dee-1.0
  gir1.2-ebook-1.2
  gir1.2-edataserver-1.2
  gir1.2-fcitx-1.0
  gir1.2-freedesktop
  gir1.2-gconf-2.0
  gir1.2-gdata-0.0
  gir1.2-gdesktopenums-3.0
  gir1.2-gdkpixbuf-2.0
  gir1.2-gkbd-3.0
  gir1.2-glib-2.0
  gir1.2-gmenu-3.0
  gir1.2-gnomebluetooth-1.0
  gir1.2-gnomedesktop-3.0
  gir1.2-goa-1.0
  gir1.2-gtk-2.0
  gir1.2-gtk-3.0
  gir1.2-gtkclutter-1.0
  gir1.2-gtksource-3.0
  gir1.2-gtop-2.0
  gir1.2-gucharmap-2.90
  gir1.2-gudev-1.0
  gir1.2-gweather-3.0
  gir1.2-hud-2
  gir1.2-hud-client-2
  gir1.2-ido3-0.1
  gir1.2-json-1.0
  gir1.2-lightdm-1
  gir1.2-messagingmenu-1.0
  gir1.2-nautilus-3.0
  gir1.2-networkmanager-1.0
  gir1.2-notify-0.7
  gir1.2-packagekitglib-1.0
  gir1.2-pango-1.0
  gir1.2-peas-1.0
  gir1.2-polkit-1.0
  gir1.2-rb-3.0
  gir1.2-rest-0.7
  gir1.2-rest-extras-0.7
  gir1.2-rsvg-2.0
  gir1.2-signon-1.0
  gir1.2-soup-2.4
  gir1.2-telepathyglib-0.12
  gir1.2-timezonemap-1.0
  gir1.2-totem-1.0
  gir1.2-totem-plparser-1.0
  gir1.2-unity-5.0
  gir1.2-upowerglib-1.0
  gir1.2-wnck-3.0
  gir1.2-evince-3.0
  gir1.2-geocodeglib-1.0
  gir1.2-libertine
  gir1.2-nmgtk-1.0
  gir1.2-ubuntu-app-launch-2
  gir1.2-anjuta-3.0
  gir1.2-atril
  gir1.2-caja
  gir1.2-caribou-1.0
  gir1.2-champlain-0.12
  gir1.2-cryptui-0.0
  gir1.2-diodon-1.0
  gir1.2-eom
  gir1.2-evd-0.1
  gir1.2-folks-0.6
  gir1.2-gdl-3
  gir1.2-gssdp-1.0
  gir1.2-gtk-vnc-2.0
  gir1.2-gtkchamplain-0.12
  gir1.2-gupnp-1.0
  gir1.2-gupnp-av-1.0
  gir1.2-gupnpigd-1.0
  gir1.2-indicate-0.7
  gir1.2-itl-1.0
  gir1.2-keybinder-3.0
  gir1.2-maliit-1.0
  gir1.2-mate-menu
  gir1.2-mate-panel
  gir1.2-mate-polkit
  gir1.2-matekbd
  gir1.2-mutter-3.0
  gir1.2-spice-client-glib-2.0
  gir1.2-spice-client-gtk-3.0
  gir1.2-telepathylogger-0.2
  gir1.2-urfkill-glib0
  gir1.2-v-sim-1.0
  gir1.2-gladeui-2.0
  gir1.2-grip
  gir1.2-javascriptcoregtk-3.0
  gir1.2-libvirt-glib-1.0
  gir1.2-nemo-3.0
  gir1.2-snapd-1
  gir1.2-webkit-3.0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gir1.2-accounts-1.0 1.22+16.10.20160520.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  3 22:02:42 2016
  InstallationDate: Installed on 2011-11-10 (1819 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: libaccounts-glib
  UpgradeStatus: Upgraded to yakkety on 2016-11-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1639050/+subscriptions

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


[Touch-packages] [Bug 1639050] [NEW] Wrong package section, should be in "introspection"

2016-11-03 Thread Michael Biebl
Public bug reported:

Packages shipping gobject introspection should be in the dedicated
section "introspection". This archive section was added a while ago, see
also the corresponding entry in the debian policy 3.9.3.0:

2.6. Version 3.9.3.0


 Released February, 2012.

 2.4
  New archive sections _education_, _introspection_, and
  _metapackages_ added.


Packages shipping gobject introspection should be named 
gir1.2-NAMESPACE-VERSION.

Based on the output of apt-cache, the following packages are in the
wrong section. I didn't file a separate bug for all of them. I would
appreciate if you can adjust the archive section for all the following
packages in one go.

#!/bin/bash

while read pkg ; do
   apt-cache show $pkg | grep Section | grep -v introspection -q && echo 
$pkg
done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' )


gir1.2-accounts-1.0
gir1.2-accountsservice-1.0
gir1.2-appindicator-0.1
gir1.2-appindicator3-0.1
gir1.2-atk-1.0
gir1.2-atspi-2.0
gir1.2-bamf-3
gir1.2-cheese-3.0
gir1.2-clutter-1.0
gir1.2-cogl-1.0
gir1.2-coglpango-1.0
gir1.2-colord-1.0
gir1.2-dbusmenu-glib-0.4
gir1.2-dbusmenu-gtk-0.4
gir1.2-dbusmenu-gtk3-0.4
gir1.2-dee-1.0
gir1.2-ebook-1.2
gir1.2-edataserver-1.2
gir1.2-fcitx-1.0
gir1.2-freedesktop
gir1.2-gconf-2.0
gir1.2-gdata-0.0
gir1.2-gdesktopenums-3.0
gir1.2-gdkpixbuf-2.0
gir1.2-gkbd-3.0
gir1.2-glib-2.0
gir1.2-gmenu-3.0
gir1.2-gnomebluetooth-1.0
gir1.2-gnomedesktop-3.0
gir1.2-goa-1.0
gir1.2-gtk-2.0
gir1.2-gtk-3.0
gir1.2-gtkclutter-1.0
gir1.2-gtksource-3.0
gir1.2-gtop-2.0
gir1.2-gucharmap-2.90
gir1.2-gudev-1.0
gir1.2-gweather-3.0
gir1.2-hud-2
gir1.2-hud-client-2
gir1.2-ido3-0.1
gir1.2-json-1.0
gir1.2-lightdm-1
gir1.2-messagingmenu-1.0
gir1.2-nautilus-3.0
gir1.2-networkmanager-1.0
gir1.2-notify-0.7
gir1.2-packagekitglib-1.0
gir1.2-pango-1.0
gir1.2-peas-1.0
gir1.2-polkit-1.0
gir1.2-rb-3.0
gir1.2-rest-0.7
gir1.2-rest-extras-0.7
gir1.2-rsvg-2.0
gir1.2-signon-1.0
gir1.2-soup-2.4
gir1.2-telepathyglib-0.12
gir1.2-timezonemap-1.0
gir1.2-totem-1.0
gir1.2-totem-plparser-1.0
gir1.2-unity-5.0
gir1.2-upowerglib-1.0
gir1.2-wnck-3.0
gir1.2-evince-3.0
gir1.2-geocodeglib-1.0
gir1.2-libertine
gir1.2-nmgtk-1.0
gir1.2-ubuntu-app-launch-2
gir1.2-anjuta-3.0
gir1.2-atril
gir1.2-caja
gir1.2-caribou-1.0
gir1.2-champlain-0.12
gir1.2-cryptui-0.0
gir1.2-diodon-1.0
gir1.2-eom
gir1.2-evd-0.1
gir1.2-folks-0.6
gir1.2-gdl-3
gir1.2-gssdp-1.0
gir1.2-gtk-vnc-2.0
gir1.2-gtkchamplain-0.12
gir1.2-gupnp-1.0
gir1.2-gupnp-av-1.0
gir1.2-gupnpigd-1.0
gir1.2-indicate-0.7
gir1.2-itl-1.0
gir1.2-keybinder-3.0
gir1.2-maliit-1.0
gir1.2-mate-menu
gir1.2-mate-panel
gir1.2-mate-polkit
gir1.2-matekbd
gir1.2-mutter-3.0
gir1.2-spice-client-glib-2.0
gir1.2-spice-client-gtk-3.0
gir1.2-telepathylogger-0.2
gir1.2-urfkill-glib0
gir1.2-v-sim-1.0
gir1.2-gladeui-2.0
gir1.2-grip
gir1.2-javascriptcoregtk-3.0
gir1.2-libvirt-glib-1.0
gir1.2-nemo-3.0
gir1.2-snapd-1
gir1.2-webkit-3.0

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gir1.2-accounts-1.0 1.22+16.10.20160520.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Nov  3 22:02:42 2016
InstallationDate: Installed on 2011-11-10 (1819 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: libaccounts-glib
UpgradeStatus: Upgraded to yakkety on 2016-11-03 (0 days ago)

** Affects: libaccounts-glib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  Wrong package section, should be in "introspection"

Status in libaccounts-glib package in Ubuntu:
  New

Bug description:
  Packages shipping gobject introspection should be in the dedicated
  section "introspection". This archive section was added a while ago,
  see also the corresponding entry in the debian policy 3.9.3.0:

  2.6. Version 3.9.3.0
  

   Released February, 2012.

   2.4
New archive sections _education_, _introspection_, and
_metapackages_ added.

  
  Packages shipping gobject introspection should be named 
gir1.2-NAMESPACE-VERSION.

  Based on the output of apt-cache, the following packages are in the
  wrong section. I didn't file a separate bug for all of them. I would
  appreciate if you can adjust the archive section for all the following
  packages in one go.

  #!/bin/bash

  while read pkg ; do
 apt-cache show $pkg | grep Section | grep -v introspection -q && echo 
$pkg
  done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' )

  
  gir1.2-accounts-1.0
  gir1.2-accountsservice-1.0
  gir1.2-appindicator-0.1
  gir1.2-appindicator3-0.1
  gir1.2-atk-1.0
  gir1.2-atspi-2.0
  gir1.2-bamf-3
  

[Touch-packages] [Bug 1602834] [NEW] obsolete conffiles not cleaned up on upgrade

2016-07-13 Thread Michael Biebl
Public bug reported:

Hi,

the following conffile is marked as obsolete in my dpkg status db

 /etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete

Ufw now ships /usr/share/bash-completion/completions/ufw, so the
conffile should be removed on upgrades.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ufw 0.35-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jul 13 22:19:52 2016
InstallationDate: Installed on 2011-11-10 (1706 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: ufw
UpgradeStatus: Upgraded to xenial on 2016-04-21 (82 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in ufw package in Ubuntu:
  New

Bug description:
  Hi,

  the following conffile is marked as obsolete in my dpkg status db

   /etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete

  Ufw now ships /usr/share/bash-completion/completions/ufw, so the
  conffile should be removed on upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 13 22:19:52 2016
  InstallationDate: Installed on 2011-11-10 (1706 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (82 days ago)

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

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


[Touch-packages] [Bug 1573296] [NEW] obsolete conffiles not cleaned up on upgrade

2016-04-21 Thread Michael Biebl
Public bug reported:

The following files are marked obsolete after the upgrade to 16.04:

 /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
 /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
 /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
 /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete


Those files should be cleaned up and the sysv init script properly deregistered.

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

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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


[Touch-packages] [Bug 1573299] [NEW] obsolete conffiles not cleaned up on upgrade

2016-04-21 Thread Michael Biebl
Public bug reported:

The following conffiles were not cleaned up after the upgrade to 16.04:

 /etc/bash_completion.d/gdbus 3c6022ac0bf85f2f374358a52456e803 obsolete
 /etc/bash_completion.d/gsettings ed6dbd29972bb65275e46f1cb1ac5062 obsolete
 /etc/bash_completion.d/gresource 305f04df5006e28bbee350d1f9f7f973 obsolete

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

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  The following conffiles were not cleaned up after the upgrade to
  16.04:

   /etc/bash_completion.d/gdbus 3c6022ac0bf85f2f374358a52456e803 obsolete
   /etc/bash_completion.d/gsettings ed6dbd29972bb65275e46f1cb1ac5062 obsolete
   /etc/bash_completion.d/gresource 305f04df5006e28bbee350d1f9f7f973 obsolete

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

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


[Touch-packages] [Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

2016-02-17 Thread Michael Biebl
@pitti: will /etc/systemd/system/tmp.mount override a /tmp mount point
from /etc/fstab (/run vs /etc)?

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

Title:
  Error message "Operation failed: No such file or directory" on
  installing/reconfiguring systemd

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
  installing/reconfiguring it I'm getting this output (the first error
  has already its own bug report here:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):

  root@ubuntu:~# dpkg-reconfigure systemd
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Operation failed: No such file or directory

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

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


[Touch-packages] [Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

2016-02-16 Thread Michael Biebl
An explicit reload should not be necessary for "enable". 
I also can't reproduce the problem:


$  cp /usr/share/systemd/tmp.mount /etc/systemd/system/tmp2.mount
$ systemctl enable tmp2.mount
Created symlink from /etc/systemd/system/local-fs.target.wants/tmp2.mount to 
/etc/systemd/system/tmp2.mount.

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

Title:
  Error message "Operation failed: No such file or directory" on
  installing/reconfiguring systemd

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
  installing/reconfiguring it I'm getting this output (the first error
  has already its own bug report here:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):

  root@ubuntu:~# dpkg-reconfigure systemd
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Operation failed: No such file or directory

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

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


[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
man bootup(7)

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

Title:
  /etc/halt.local has become /usr/sbin/halt.local

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 15.10, amd64
  systemd-225-1ubuntu9

  /etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO
  is bad for a couple of reasons.

  1) This is not where it's supposed to be
  2) Locally modified (non-dpkg managed) scripts under /usr is bad

  I have not been able to find anywhere documenting this as a decided
  change, so it seems like a bug to me.

  Please let me know if you need more info from me

  /Thomas

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

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


[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
fwiw, halt-local.service was hooked up in final.target and contains the
following:

[Unit]
Description=/usr/sbin/halt.local Compatibility
ConditionFileIsExecutable=/usr/sbin/halt.local
DefaultDependencies=no
After=shutdown.target
Before=final.target

To apply that to my /etc/systemd/system/foo.service example:


[Unit]
Description=Run service on shutdown
DefaultDependencies=no
After=shutdown.target
Before=final.target

[Service]
ExecStart=/bin/true

[Install]
WantedBy=final.target

Then run "systemctl enable foo.service" and you should be set.

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

Title:
  /etc/halt.local has become /usr/sbin/halt.local

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 15.10, amd64
  systemd-225-1ubuntu9

  /etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO
  is bad for a couple of reasons.

  1) This is not where it's supposed to be
  2) Locally modified (non-dpkg managed) scripts under /usr is bad

  I have not been able to find anywhere documenting this as a decided
  change, so it seems like a bug to me.

  Please let me know if you need more info from me

  /Thomas

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

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


[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
Or make that
WantedBy=final.target, if you want to execute it during late shutdown.

See man systemd.special(7)

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

Title:
  /etc/halt.local has become /usr/sbin/halt.local

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 15.10, amd64
  systemd-225-1ubuntu9

  /etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO
  is bad for a couple of reasons.

  1) This is not where it's supposed to be
  2) Locally modified (non-dpkg managed) scripts under /usr is bad

  I have not been able to find anywhere documenting this as a decided
  change, so it seems like a bug to me.

  Please let me know if you need more info from me

  /Thomas

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

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


[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
Add a native service file and hook it up in the shutdown.target. That's
the cleanest solution.

/etc/systemd/system/foo.service
[Unit]
Description=Run service on shutdown

[Service]
ExecStart=/bin/true

[Install]
WantedBy=shutdown.target

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

Title:
  /etc/halt.local has become /usr/sbin/halt.local

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 15.10, amd64
  systemd-225-1ubuntu9

  /etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO
  is bad for a couple of reasons.

  1) This is not where it's supposed to be
  2) Locally modified (non-dpkg managed) scripts under /usr is bad

  I have not been able to find anywhere documenting this as a decided
  change, so it seems like a bug to me.

  Please let me know if you need more info from me

  /Thomas

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

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


[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
Before the introduction of systemd in Debian and Ubuntu, /etc/halt.local was 
not supported at all.
Neither sysvinit nor upstart executed that file/script. So I'm mildly suprised, 
when you say "it always worked".

We decided to not introduce support for this legacy, sysv specific
service, which after a bit of research seems to be Redhat
(/sbin/halt.local) and SuSE (/etc/init.d/halt.local) specific.

Adding /etc/halt.local to the mix would only confuse things.
It's much better to create a native service file with systemd, and it's much 
easier.

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

Title:
  /etc/halt.local has become /usr/sbin/halt.local

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 15.10, amd64
  systemd-225-1ubuntu9

  /etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO
  is bad for a couple of reasons.

  1) This is not where it's supposed to be
  2) Locally modified (non-dpkg managed) scripts under /usr is bad

  I have not been able to find anywhere documenting this as a decided
  change, so it seems like a bug to me.

  Please let me know if you need more info from me

  /Thomas

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

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


[Touch-packages] [Bug 1518507] [NEW] Drop dependency on systemd-shim (and replace system-services)

2015-11-20 Thread Michael Biebl
Public bug reported:

The package declares a dependency on systemd-shim.
With systemd being the default init, this dependency is no longer required and 
actually wanted.

The dependency on systemd-services should also either be replaced with a
dependency on systemd (or libpam-systemd, depending on whether it needs
logind) or simply dropped.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Drop dependency on systemd-shim (and replace system-services)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The package declares a dependency on systemd-shim.
  With systemd being the default init, this dependency is no longer required 
and actually wanted.

  The dependency on systemd-services should also either be replaced with
  a dependency on systemd (or libpam-systemd, depending on whether it
  needs logind) or simply dropped.

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

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


[Touch-packages] [Bug 1438612]

2015-04-02 Thread Michael Biebl
ExecStop=/bin/true was my first idea, but Martin rightfully pointed out, that 
this doesn't influence KillMode, i.e. we need KillMode=none.
With that KillMode setting, I think we can actually drop ExecStop=/bin/true, so 
what remains is

KillMode=none

systemd has a final killing spree, before it unmounts the file systems
and I don't think dbus needs to do something special on stop?

We might have a problem, if /usr is on NFS and (at least on Debian)
dbus-daemon being installed in /usr/bin, which would keep the FS busy.

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

Title:
  remote file systems hang on shutdown, D-BUS stops too early

Status in D-Bus:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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


[Touch-packages] [Bug 1438612]

2015-04-02 Thread Michael Biebl
(In reply to Simon McVittie from comment #7)
 (In reply to Simon McVittie from comment #6)
  Perhaps it would be better to make the stop command exit
  nonzero?
 
 Straw man:
 
 ExecStop=/bin/sh -c echo Stopping the system dbus-daemon is not supported.
 Reboot the system instead.; exit 1
 
 ... which does work, but logs Unit dbus.service entered failed state
 during shutdown. It seems better to avoid crying wolf if possible, because
 it can hide real issues.


Spawning a shell (which will burn more cpu cycles then a simple /bin/true), 
this will also trigger a failure on every shutdown/reboot.
Do we really want this?

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

Title:
  remote file systems hang on shutdown, D-BUS stops too early

Status in D-Bus:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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


[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early

2015-03-31 Thread Michael Biebl
dbus would be stopped by the final killing spree.

This usually looks like this

stop individual services in reverse order

Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All loop devices detached.
Detaching DM devices.
All DM devices detached.
system-shutd[   51.216341] reboot: Power down
own succeeded.
Powering off.


I don't think, there is anything special that dbus needs to do on stop.

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

Title:
  remote file systems hang on shutdown, D-BUS stops too early

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

-- 
Mailing list: https://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 1437821] [NEW] no proper foreground mode

2015-03-29 Thread Michael Biebl
This is what -n is for.
Incidentally, this is also used in rsyslog.service file for systemd.

2015-03-29 14:25 GMT+02:00 Hadmut Danisch had...@danisch.de:
 Public bug reported:

 Hi,

 it's rather a feature request than a bug report:

 I had to package several network services in docker images (and to start
 them with supervisor as common practice). While almost all services like
 webservers, ldap,... have a running mode without daemonizing, i.e. can
 stay in foreground without forking, rsyslog does not seem to have this
 (just a debugging mode with setting an environment variable, which,
 however, did not run as expected).

 Would be nice to have this in rsyslog as well to be able to start it
 from supervisord.

 regards

 ProblemType: Bug
 DistroRelease: Ubuntu 14.04
 Package: rsyslog 7.4.4-1ubuntu2.5
 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
 Uname: Linux 3.13.0-48-generic x86_64
 ApportVersion: 2.14.1-0ubuntu3.7
 Architecture: amd64
 CurrentDesktop: XFCE
 Date: Sun Mar 29 14:19:56 2015
 InstallationDate: Installed on 2014-08-06 (234 days ago)
 InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
 (20140722.3)
 SourcePackage: rsyslog
 UpgradeStatus: No upgrade log present (probably fresh install)

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


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

 --
 You received this bug notification because you are subscribed to rsyslog
 in Ubuntu.
 Matching subscriptions: rsyslog-bugs
 https://bugs.launchpad.net/bugs/1437821

 Title:
   no proper foreground mode

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


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

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

Title:
  no proper foreground mode

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Hi,

  it's rather a feature request than a bug report:

  I had to package several network services in docker images (and to
  start them with supervisor as common practice). While almost all
  services like webservers, ldap,... have a running mode without
  daemonizing, i.e. can stay in foreground without forking, rsyslog does
  not seem to have this (just a debugging mode with setting an
  environment variable, which, however, did not run as expected).

  Would be nice to have this in rsyslog as well to be able to start it
  from supervisord.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Mar 29 14:19:56 2015
  InstallationDate: Installed on 2014-08-06 (234 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

2015-03-14 Thread Michael Biebl
Let me chime in here as maintainer of NM in Debian: The reason why we
ship the patch, which removes Wants/Before=network.target is, that this
lead to dependency cycles if services/sysv init scripts in rcS
(sysinit.target) had Should-Start/Required-Start: $network, like for
example /etc/init.d/rpcbind in Debian.

If there is no such sysv init script Ubuntu, this patch can be dropped
indeed.

As for Colin's remark in #25, sounds sensible, to add
After=network.target to wpa_supplicant.service as well.

Have you tried adding that and see if that fixes the problem on shutdown
with WiFi?

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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


[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

2015-03-14 Thread Michael Biebl
Sorry, meant Before=network.target, of course...

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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