date:20170712

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can no longer play wma files with Ubuntu 16.04

Status in gstreamer1.0 package in Ubuntu:
  Expired

Bug description:
  Multiple (7) computers were working just fine until a recent update
  apparently removed the plug-in.

  Perhaps you could provide us with an update to put the plug-in back in
  place.(?)

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

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

[Touch-packages] [Bug 1703415] Re: Disable Bluetooth sink in GDM to allow A2DP in the user session

But see also:
https://bugs.freedesktop.org/show_bug.cgi?id=90490

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

Title:
  Disable Bluetooth sink in GDM to allow A2DP in the user session

Status in gdm:
  Unknown
Status in PulseAudio:
  Confirmed
Status in gdm3 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in gdm3 package in Debian:
  New

Bug description:
  This is actually a PulseAudio bug, but the workaround is to disable
  Bluetooth audio in GDM.

  Further discussion (and the source of my understanding about this
  issue) upstream are here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414

  To summarise:

  GDM opens the A2DP profile for a11y purposes to allow screenreaders to
  output over BT audio devices. However Pulse doesn't release those
  devices when no audio is being played and the upshot is that once in
  the users session A2DP is not available for any Bluetooth audio
  devices, this means that you can only use the low quality profile
  HSP/HFP.

  There is a proposed workaround, but this means that a11y tools which
  need to output audio won't be able to use Bluetooth devices within
  GDM.

  I think that for 17.10 shipping this work-around is acceptable, and we
  should revisit in the 18.04 cycle to try and get a proper fix in PA.
  The suggested PA bug is:

  https://bugs.freedesktop.org/show_bug.cgi?id=57167

  but that hasn't seen movement since 2012.

  = The work around =

  From the Debian wiki:  https://wiki.debian.org/BluetoothUser/a2dp

  Disable the Bluetooth sink in the GDM PA daemon.

  Add this to /var/lib/gdm3/.config/pulse/default.pa

  #!/usr/bin/pulseaudio -nF
  #

  # load system wide configuration
  .include /etc/pulse/default.pa

  ### unload driver modules for Bluetooth hardware
  .ifexists module-bluetooth-policy.so
unload-module module-bluetooth-policy
  .endif

  .ifexists module-bluetooth-discover.so
unload-module module-bluetooth-discover
  .endif


  I have tested this, and I can confirm that it allows access to A2DP
  again in the user session.

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

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

[Touch-packages] [Bug 1703415] Re: Disable Bluetooth sink in GDM to allow A2DP in the user session

A better upstream bug report for PulseAudio might be:
https://bugs.freedesktop.org/show_bug.cgi?id=98144

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

** Bug watch added: freedesktop.org Bugzilla #98144
   https://bugs.freedesktop.org/show_bug.cgi?id=98144

** Bug watch added: freedesktop.org Bugzilla #90490
   https://bugs.freedesktop.org/show_bug.cgi?id=90490

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

Title:
  Disable Bluetooth sink in GDM to allow A2DP in the user session

Status in gdm:
  Unknown
Status in PulseAudio:
  Confirmed
Status in gdm3 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in gdm3 package in Debian:
  New

Bug description:
  This is actually a PulseAudio bug, but the workaround is to disable
  Bluetooth audio in GDM.

  Further discussion (and the source of my understanding about this
  issue) upstream are here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414

  To summarise:

  GDM opens the A2DP profile for a11y purposes to allow screenreaders to
  output over BT audio devices. However Pulse doesn't release those
  devices when no audio is being played and the upshot is that once in
  the users session A2DP is not available for any Bluetooth audio
  devices, this means that you can only use the low quality profile
  HSP/HFP.

  There is a proposed workaround, but this means that a11y tools which
  need to output audio won't be able to use Bluetooth devices within
  GDM.

  I think that for 17.10 shipping this work-around is acceptable, and we
  should revisit in the 18.04 cycle to try and get a proper fix in PA.
  The suggested PA bug is:

  https://bugs.freedesktop.org/show_bug.cgi?id=57167

  but that hasn't seen movement since 2012.

  = The work around =

  From the Debian wiki:  https://wiki.debian.org/BluetoothUser/a2dp

  Disable the Bluetooth sink in the GDM PA daemon.

  Add this to /var/lib/gdm3/.config/pulse/default.pa

  #!/usr/bin/pulseaudio -nF
  #

  # load system wide configuration
  .include /etc/pulse/default.pa

  ### unload driver modules for Bluetooth hardware
  .ifexists module-bluetooth-policy.so
unload-module module-bluetooth-policy
  .endif

  .ifexists module-bluetooth-discover.so
unload-module module-bluetooth-discover
  .endif


  I have tested this, and I can confirm that it allows access to A2DP
  again in the user session.

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

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

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693609] Re: Please make window control buttons larger

** Tags added: gnome-17.10

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

Title:
  Please make window control buttons larger

Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

[Touch-packages] [Bug 1704041] [NEW] Screen resolution

2017-07-12 Thread Shahzaib

Public bug reported:

I having graphics problem with ubuntu 16.04not able to add screen
resolution...everthing is too bigit gives option only to select one
resolution in setting and display

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39
Uname: Linux 3.13.0-108-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jul 12 20:24:26 2017
DistUpgraded: 2017-02-15 16:10:12,331 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: open-vm-tools, 10.0.7: added
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
InstallationDate: Installed on 2017-02-15 (147 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 002: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-108-generic 
root=UUID=4f931ec7-b9ca-4a3b-82bc-5fc68306ba69 ro nomdmonddf nomdmonisw
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-02-16 (147 days ago)
dmi.bios.date: 11/08/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0316
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B250M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0316:bd11/08/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-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: Wed Jul 12 20:22:45 2017
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install ubuntu 
xenial

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

Title:
  Screen resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  I having graphics problem with ubuntu 16.04not able to add screen
  resolution...everthing is too bigit gives option only to select
  one resolution in setting and display

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-108-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist:

[Touch-packages] [Bug 1704038] Re: upgrade problem when remove the python in a wrong way.

** Tags removed: need-duplicate-check

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

Title:
  upgrade problem when remove the python in a wrong way.

Status in apport package in Ubuntu:
  New

Bug description:
  when I uninstall the python unexpectedly, my ubuntu 17.04 got so many
  mistake when using

   sudo apt-get upgrade

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libgdf-dev libgdf0 liblua5.1-0-dev libreadline-dev libtinfo-dev libtool-bin
linux-headers-4.10.0-19 linux-headers-4.10.0-19-generic
linux-headers-4.10.0-21 linux-headers-4.10.0-21-generic
linux-headers-4.10.0-22 linux-headers-4.10.0-22-generic lua-any lua-sec
lua-socket lua5.1
  Use 'sudo apt autoremove' to remove them.
  The following packages will be upgraded:
apport apport-gtk bsdutils chromium-codecs-ffmpeg-extra
flashplugin-installer gnome-software gnome-software-common
gnome-software-plugin-snap intel-microcode libblkid1 libepoxy0 libfdisk1
libgcrypt20 libgweather-3-6 libgweather-common libmount1 libpoppler-glib8
libpoppler64 libsmartcols1 libuuid1 libwbclient0 mount nplan poppler-utils
python-problem-report python3-apport python3-problem-report thunderbird
thunderbird-gnome-support thunderbird-locale-zh-cn
thunderbird-locale-zh-hans ubuntu-software util-linux uuid-runtime
  34 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  51 not fully installed or removed.
  Need to get 51.1 MB of archives.
  After this operation, 753 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
python-problem-report all 2.20.4-0ubuntu4.4 [9,864 B]
  Get:2 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 bsdutils 
amd64 1:2.29-1ubuntu2.1 [55.4 kB]
  Get:3 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 util-linux 
amd64 2.29-1ubuntu2.1 [913 kB]
  Get:4 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 mount amd64 
2.29-1ubuntu2.1 [130 kB]
  Get:5 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 uuid-runtime 
amd64 2.29-1ubuntu2.1 [26.5 kB]
  Get:6 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/universe amd64 
chromium-codecs-ffmpeg-extra amd64 59.0.3071.109-0ubuntu0.17.04.1360 [1,036 kB]
  Get:7 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libwbclient0 
amd64 2:4.5.8+dfsg-0ubuntu0.17.04.3 [32.4 kB]
  Get:8 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libuuid1 
amd64 2.29-1ubuntu2.1 [14.8 kB]
  Get:9 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libblkid1 
amd64 2.29-1ubuntu2.1 [110 kB]
  Get:10 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libfdisk1 
amd64 2.29-1ubuntu2.1 [145 kB]
  Get:11 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libgcrypt20 
amd64 1.7.6-1ubuntu0.1 [400 kB]
  Get:12 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libmount1 
amd64 2.29-1ubuntu2.1 [119 kB]
  Get:13 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
libsmartcols1 amd64 2.29-1ubuntu2.1 [69.4 kB]
  Get:14 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 nplan amd64 
0.23~17.04.1 [38.1 kB]
  Get:15 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
python3-problem-report all 2.20.4-0ubuntu4.4 [9,944 B]
  Get:16 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
python3-apport all 2.20.4-0ubuntu4.4 [79.4 kB]
  Get:17 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 apport all 
2.20.4-0ubuntu4.4 [121 kB]
  Get:18 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 apport-gtk 
all 2.20.4-0ubuntu4.4 [9,516 B]
  Get:19 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/multiverse amd64 
flashplugin-installer amd64 26.0.0.137ubuntu0.17.04.1 [6,818 B]
  Get:20 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
gnome-software-plugin-snap amd64 3.22.7-0ubuntu3.17.04.5 [26.0 kB]
  Get:21 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
gnome-software amd64 3.22.7-0ubuntu3.17.04.5 [305 kB]
  Get:22 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
gnome-software-common all 3.22.7-0ubuntu3.17.04.5 [2,480 kB]
  Get:23 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libepoxy0 
amd64 1.3.1-1ubuntu1.17.04.1 [174 kB]
  Get:24 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
libgweather-common all 3.24.1-0ubuntu0.1 [146 kB]
  Get:25 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
libgweather-3-6 amd64 3.24.1-0ubuntu0.1 [50.9 kB]
  Get:26 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
poppler-utils amd64 0.48.0-2ubuntu2.1 [136 kB]
  Get:27 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64

[Touch-packages] [Bug 1704038] [NEW] upgrade problem when remove the python in a wrong way.

2017-07-12 Thread tom85

Public bug reported:

when I uninstall the python unexpectedly, my ubuntu 17.04 got so many
mistake when using

 sudo apt-get upgrade

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libgdf-dev libgdf0 liblua5.1-0-dev libreadline-dev libtinfo-dev libtool-bin
  linux-headers-4.10.0-19 linux-headers-4.10.0-19-generic
  linux-headers-4.10.0-21 linux-headers-4.10.0-21-generic
  linux-headers-4.10.0-22 linux-headers-4.10.0-22-generic lua-any lua-sec
  lua-socket lua5.1
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  apport apport-gtk bsdutils chromium-codecs-ffmpeg-extra
  flashplugin-installer gnome-software gnome-software-common
  gnome-software-plugin-snap intel-microcode libblkid1 libepoxy0 libfdisk1
  libgcrypt20 libgweather-3-6 libgweather-common libmount1 libpoppler-glib8
  libpoppler64 libsmartcols1 libuuid1 libwbclient0 mount nplan poppler-utils
  python-problem-report python3-apport python3-problem-report thunderbird
  thunderbird-gnome-support thunderbird-locale-zh-cn
  thunderbird-locale-zh-hans ubuntu-software util-linux uuid-runtime
34 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
51 not fully installed or removed.
Need to get 51.1 MB of archives.
After this operation, 753 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
python-problem-report all 2.20.4-0ubuntu4.4 [9,864 B]
Get:2 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 bsdutils amd64 
1:2.29-1ubuntu2.1 [55.4 kB]
Get:3 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 util-linux 
amd64 2.29-1ubuntu2.1 [913 kB]
Get:4 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 mount amd64 
2.29-1ubuntu2.1 [130 kB]
Get:5 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 uuid-runtime 
amd64 2.29-1ubuntu2.1 [26.5 kB]
Get:6 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/universe amd64 
chromium-codecs-ffmpeg-extra amd64 59.0.3071.109-0ubuntu0.17.04.1360 [1,036 kB]
Get:7 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libwbclient0 
amd64 2:4.5.8+dfsg-0ubuntu0.17.04.3 [32.4 kB]
Get:8 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libuuid1 amd64 
2.29-1ubuntu2.1 [14.8 kB]
Get:9 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libblkid1 
amd64 2.29-1ubuntu2.1 [110 kB]
Get:10 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libfdisk1 
amd64 2.29-1ubuntu2.1 [145 kB]
Get:11 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libgcrypt20 
amd64 1.7.6-1ubuntu0.1 [400 kB]
Get:12 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libmount1 
amd64 2.29-1ubuntu2.1 [119 kB]
Get:13 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libsmartcols1 
amd64 2.29-1ubuntu2.1 [69.4 kB]
Get:14 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 nplan amd64 
0.23~17.04.1 [38.1 kB]
Get:15 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
python3-problem-report all 2.20.4-0ubuntu4.4 [9,944 B]
Get:16 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
python3-apport all 2.20.4-0ubuntu4.4 [79.4 kB]
Get:17 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 apport all 
2.20.4-0ubuntu4.4 [121 kB]
Get:18 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 apport-gtk 
all 2.20.4-0ubuntu4.4 [9,516 B]
Get:19 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/multiverse amd64 
flashplugin-installer amd64 26.0.0.137ubuntu0.17.04.1 [6,818 B]
Get:20 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
gnome-software-plugin-snap amd64 3.22.7-0ubuntu3.17.04.5 [26.0 kB]
Get:21 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
gnome-software amd64 3.22.7-0ubuntu3.17.04.5 [305 kB]
Get:22 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
gnome-software-common all 3.22.7-0ubuntu3.17.04.5 [2,480 kB]
Get:23 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libepoxy0 
amd64 1.3.1-1ubuntu1.17.04.1 [174 kB]
Get:24 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
libgweather-common all 3.24.1-0ubuntu0.1 [146 kB]
Get:25 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
libgweather-3-6 amd64 3.24.1-0ubuntu0.1 [50.9 kB]
Get:26 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 poppler-utils 
amd64 0.48.0-2ubuntu2.1 [136 kB]
Get:27 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
libpoppler-glib8 amd64 0.48.0-2ubuntu2.1 [105 kB]
Get:28 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 libpoppler64 
amd64 0.48.0-2ubuntu2.1 [777 kB]
Get:29 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 
thunderbird-locale-zh-hans amd64 1:52.2.1+build1-0ubuntu0.17.04.1 [533 kB]
Get:30 http://mirrors.ustc.edu.cn/ubuntu zesty-updates/main amd64 thunderbird 
amd64 1:52.2.1+build1-0ubuntu0.17.04.1 [42.3 MB]
Get:31

[Touch-packages] [Bug 1401474] Re: [Dell Inspiron 7737] The power indicator won't be available until the adapter connected / disconnected

2017-07-12 Thread Po-Hsu Lin

** Changed in: indicator-power (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  [Dell Inspiron 7737] The power indicator won't be available until the
  adapter connected / disconnected

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  CID: 201306-13869 Dell Inspiron 7737

  The power indicator on this system only appears after you connect or
  disconnect it from the adapter.

  After it appears, reboot it will make the indicator disappear again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec 11 05:06:39 2014
  InstallationDate: Installed on 2014-12-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)

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

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

Title:
Volume notification keeps popping up constantly (the notify-OSD bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1636901] Re: Seamless mouse integration does not work with Mir in a VM

Fair point, but Mir is still an active project so I'll reopen that task.

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

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

Title:
  Seamless mouse integration does not work with Mir in a VM

Status in Mir:
  Confirmed
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Mouse integration is off using virt-manager/viewer/QVC/Spice with
  Unity8/mir as the guest.

  Steps to reproduce;
  1. Install in a virt-manager VM with QVC and Spice enabled.
  2. Login to Unity7, notice how mouse flows seamlessly between Host and Guest 
machine.
  3. Login to Unity8. Note how you can't bring the mouse to the top of the 
screen (or the far left usually).  Specifically it goes back to the host too 
quickly.

  The box that you can move in does change a bit (AFAICT).  Try
  fullscreen to see.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  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
  Date: Wed Oct 26 11:32:57 2016
  InstallationDate: Installed on 2016-08-23 (64 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160823)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689033] Re: A few missing icons in version 2.4.3

2017-07-12 Thread Bug Watch Updater

** Changed in: gtk
   Status: Confirmed => Fix Released

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

Title:
  A few missing icons in version 2.4.3

Status in gdk-pixbuf:
  Invalid
Status in GTK+:
  Fix Released
Status in easytag package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  A few icons are missing in version 2.4.3 for zesty (and probably
  artful), see https://i.imgur.com/Cl4o36Sr.png

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

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

[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable

Is UNRELEASED OK or do we want to change that to artful?

+sound-theme-freedesktop (0.8-1ubuntu1) UNRELEASED; urgency=medium

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

Title:
  Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
  New

Bug description:
  When testing stereo speakers you get the "Front left" and "Front
  right" samples, but no such sample exists for mono speakers e.g.
  HSP/HFP bluetooth devices.

  Instead you get played the "audio-test-signal" which is white noise.
  To begin with I thought this was a problem with Bluetooth or the
  speaker itself, but it's just the sample being used.

  There is a bug upstream to provide this sample, but in the meantime I
  think playing the "audio-channel-front-center.oga" is a suitable
  standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1704027] [NEW] package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package util-linux is not ready for configuration cannot configure (current status 'half-installed'

2017-07-12 Thread Paul J. Schneider

Public bug reported:

1. Ubuntu 16.04.2 LTS

2. 2.27.1-6ubuntu3.3

3. Nothing

4. An error message stating the package could not be installed popped
up.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jul 13 01:33:20 2017
DpkgTerminalLog:
 dpkg: error processing package util-linux (--configure):
  package util-linux is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-02-04 (158 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: util-linux
Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package 
util-linux is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704027

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  package util-linux is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  1. Ubuntu 16.04.2 LTS

  2. 2.27.1-6ubuntu3.3

  3. Nothing

  4. An error message stating the package could not be installed popped
  up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jul 13 01:33:20 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
package util-linux is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-04 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
package util-linux is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-07-12 Thread NJ

Corrections to the above post.

(i) '[I]t its original' should be 'in its original'.

(ii) 'Inference from the conjunction of 1, 2 and 3' should be,
'Inference from the conjunction of 1, 2, 3 and 4' - because I found
another reason.

A facility to edit posts would be welcome (but perhaps that exists and I
overlook it somehow).

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-07-12 Thread NJ

1. It has been four months since this bug - it its original incarnation
(https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606)
- was reported.

2. The bug is critical: it breaks security software.

3. The bug has been reported to Ubuntu, which has paid employees.

4. The bug is a regression and hence presumably not especially hard to
fix.

Inference from the conjunction of 1, 2 and 3: *this bug should have been
fixed by now*. Yet, it has not. Nor has any explanation been provided as
to why not, at least not here. Not has there been a shortage of people
asking, politely, for a fix.


Perhaps then a slightly more strident question is in order. To wit: **what 
gives?** This is the sort of unfixed major problem that drives people back to 
Windows and Mac OS. (I know that https://bugs.launchpad.net/ubuntu/+bug/1 is 
closed, but still.)

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  while restoring from a hard lockup after Firefox memory hogging.
  reboot threw up above warning

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jul 12 18:13:48 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2016-07-26 (351 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 1525
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=5e29d9d3-b772-4cdf-9496-1c2ddf07881e ro drm.debug=0xe plymouth:debug
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/liblzma.so.5
   ?? () from /lib/x86_64-linux-gnu/liblzma.so.5
   lzma_block_buffer_encode () from /lib/x86_64-linux-gnu/liblzma.so.5
   lzma_stream_buffer_encode () from /lib/x86_64-linux-gnu/liblzma.so.5
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.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: systemd-journald crashed with SIGABRT in lzma_block_buffer_encode()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1681493] Re: Ubuntu Zesty: Problem With Screen Brightness Settings

2017-07-12 Thread Maxim

I think this bug may be connected with display matrices: asus g752vs and
my laptop have b172han01. I made a display replacement and this problem
appeared after this.

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

Title:
  Ubuntu Zesty: Problem With Screen Brightness Settings

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS (Nvidia GTX1070)
  Ubuntu 17.04
  Xorg-Server-1.19.3
  Nvidia driver 375.39

  Situation on 2017-04-05:
  Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen 
brightness, but after restarting the screen brightness of my laptop resets to 
maximum.

  Situation on 2017-04-08:
  Today I received many Ubuntu updates (kernel included), and I also installed 
freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - 
Proprietary GPU Drivers PPA).
  Now brightness settings are correctly saved, but I have a new problem: 
changing brightness level doesn't produce any effect (both with or without 
Nvidia driver installed)

  Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and
  "acpi_video1"

  ~$ systemctl status systemd-backlight@backlight:acpi_video0.service
  ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 683 (code=exited, status=0/SUCCESS)

  ~$ systemctl status systemd-backlight@backlight:acpi_video1.service
  ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 684 (code=exited, status=0/SUCCESS)

  Situation on 2017-04-10:
  I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via 
additional drivers.
  Now the situation has returned to initial problem: I can again adjust the 
screen brightness, but after restarting the screen brightness of my laptop 
again resets to maximum.
  --- 
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-02 (98 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. G752VS
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: systemd 232-21ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VS.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G752VS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+subscriptions

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

[Touch-packages] [Bug 1681493] Re: Ubuntu Zesty: Problem With Screen Brightness Settings

2017-07-12 Thread Maxim

I have very similar problem, details are here:
https://askubuntu.com/q/935585/698509

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

Title:
  Ubuntu Zesty: Problem With Screen Brightness Settings

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS (Nvidia GTX1070)
  Ubuntu 17.04
  Xorg-Server-1.19.3
  Nvidia driver 375.39

  Situation on 2017-04-05:
  Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen 
brightness, but after restarting the screen brightness of my laptop resets to 
maximum.

  Situation on 2017-04-08:
  Today I received many Ubuntu updates (kernel included), and I also installed 
freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - 
Proprietary GPU Drivers PPA).
  Now brightness settings are correctly saved, but I have a new problem: 
changing brightness level doesn't produce any effect (both with or without 
Nvidia driver installed)

  Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and
  "acpi_video1"

  ~$ systemctl status systemd-backlight@backlight:acpi_video0.service
  ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 683 (code=exited, status=0/SUCCESS)

  ~$ systemctl status systemd-backlight@backlight:acpi_video1.service
  ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 684 (code=exited, status=0/SUCCESS)

  Situation on 2017-04-10:
  I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via 
additional drivers.
  Now the situation has returned to initial problem: I can again adjust the 
screen brightness, but after restarting the screen brightness of my laptop 
again resets to maximum.
  --- 
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-02 (98 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. G752VS
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: systemd 232-21ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VS.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G752VS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1681493/+subscriptions

-- 
Mailing list: https://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 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

2017-07-12 Thread Alister

Hi Seth

My problem with the half installed package appears to have been resolved 
with the "sudo apt-get install --reinstall" process. Updates are now 
installing correctly as far as I can see.

Alister Lee

On 13/07/17 04:52, Seth Arnold wrote:
> I'm curious how we can work around this bug. If you're affected please
> report the results of:
>
> dpkg -l | awk '/^iH/ { print $2 }'
>
> This shows which specific packages are half-installed on your systems.
>
> With the list of packages this returns, please also report success or
> failure of:
>
> sudo apt-get install --reinstall ALL PACKAGES FROM THE HALF-INSTALLED
> LIST
>
> Thanks
>

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

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   libssl1.0.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:47:55 2017
  DuplicateSignature:
   package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
   dpkg: error processing package libssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-15 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1703598] Re: [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your sources.list'

On Wed, Jul 12, 2017 at 09:46:37PM -, Amr Ibrahim wrote:
> It's attached here.
> 
> ** Attachment added: "sources.list"
>
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1703598/+attachment/4913799/+files/sources.list
> 
> ** Changed in: apport (Ubuntu)
>Status: Incomplete => New

All your deb-src entries are commented out so they are not enabled and
apport-retrace won't be usable.

--
Brian Murray

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

Title:
  [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your
  sources.list'

Status in apport package in Ubuntu:
  New

Bug description:
  I get that error when I do this:

  apport-retrace -g -R -S system -v crash-file.crash

  ERROR: E:You must put some 'source' URIs in your sources.list

  - But I think they are already there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport-retrace 2.20.1-0ubuntu2.9
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportLog:
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: called for pid 2837, 
signal 11, core limit 0
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: executable: 
/usr/bin/signon-ui (command line "/usr/bin/signon-ui")
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3064) Tue Jul 11 12:57:44 2017: wrote report 
/var/crash/_usr_bin_signon-ui.1000.crash
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 11 14:02:02 2017
  InstallationDate: Installed on 2017-06-21 (19 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703598] Re: [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your sources.list'

2017-07-12 Thread Amr Ibrahim

It's attached here.

** Attachment added: "sources.list"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1703598/+attachment/4913799/+files/sources.list

** Changed in: apport (Ubuntu)
   Status: Incomplete => 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/1703598

Title:
  [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your
  sources.list'

Status in apport package in Ubuntu:
  New

Bug description:
  I get that error when I do this:

  apport-retrace -g -R -S system -v crash-file.crash

  ERROR: E:You must put some 'source' URIs in your sources.list

  - But I think they are already there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport-retrace 2.20.1-0ubuntu2.9
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportLog:
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: called for pid 2837, 
signal 11, core limit 0
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: executable: 
/usr/bin/signon-ui (command line "/usr/bin/signon-ui")
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3064) Tue Jul 11 12:57:44 2017: wrote report 
/var/crash/_usr_bin_signon-ui.1000.crash
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 11 14:02:02 2017
  InstallationDate: Installed on 2017-06-21 (19 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1699850] Re: Reliable network connectivity for apt-daily

2017-07-12 Thread Julian Andres Klode

Also note that getaddrinfo() is blocking, so that's not really going to
work.

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

Title:
  Reliable network connectivity for apt-daily

Status in systemd:
  Unknown
Status in apt package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  apt-daily.service is launched by a timer that depends on network-
  online.target (after the fixes for bug 1686470 are in everywhere)

  At boot that is mostly sufficient for it to have network online, but
  it does not seem to work all the time, and we might be disagreeing
  with network-manager and friends what online state means.

  At resume time, network-online.target is still active, so the service
  is started as soon as possible when it tries to catch up. Depending on
  the timing, the network connectivity might not be there yet, and it
  will fail and only retry 12 hours later.

  [Proposed solution]
  Introduce a new apt-helper wait-online that tries to connect() to remote 
hosts specified in sources.list until one connection works or a TIMEOUT is 
reached. The proposed algorithm looks something like this:

  while (time elapsed < TIMEOUT):
    for each entry:
  host = getaddrinfo()
  if host failed:
    continue
  fd = connect to it
  if fd is invalid:
    continue

  all fds += fd

  if poll(all fds, 100 ms timeout) finds a connected one:
    exit(0)

  exit(42) # timeout

  There are two things to consider:
  * getaddrinfo() and connect() may fail if network is not up yet, so we need 
to retry (we might need to sleep somewhere)
  * If poll() fails, we likely sleep enough, so no extra sleep needed.

  I believe the time out should be something like 30s.

  On the systemd service side, we add:
    ExecStartPre=/usr/lib/apt/apt-helper wait-online
    RestartForceExitStatus=42
    RestartSec=15m

  To retry the service after 15 minutes.

  [Test case]
  * Start apt-daily.service after turning off network -> It should wait (in 
ExecStartPre)
  * Turn on network -> apt-daily.service should start

  [Regression potential]
  There might be increased I/O activity after resume, if that did not work 
before.

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

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

[Touch-packages] [Bug 1531622] Re: default config still using a legacy keyword: KLogPermitNonKernelFacility

The configuration change is correct, but I think it's not working in the
end. Upstream has a bug about it:

https://github.com/rsyslog/rsyslog/issues/477

And I filed
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1703987 for the
ubuntu packages.

** Bug watch added: github.com/rsyslog/rsyslog/issues #477
   https://github.com/rsyslog/rsyslog/issues/477

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  /etc/rsyslog.conf contains:

    $KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

   Jan  5 08:56:16 simon-laptop rsyslogd-: command
  'KLogPermitNonKernelFacility' is currently not permitted - did you
  already set it via a RainerScript command (v6+ config)? [v8.14.0 try
  http://www.rsyslog.com/e/ ]

  Error  is described as "legacy parameter no longer permitted".

  This legacy parameter causes config syntax checks (rsyslogd -N1) to
  fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.14.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan  6 15:47:15 2016
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

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

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

[Touch-packages] [Bug 1675515] Re: old KLogPermitNonKernel directive error in rsyslog.conf

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

I filed bug #1703987 for the problem I mentioned in comment #3

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

Title:
  old KLogPermitNonKernel directive error in rsyslog.conf

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  The rsyslog.conf provided in Xenial contains an error that is logged
  by rsyslog at startup with the short name. rsyslog ignores a
  '$PreserveFQDN on' when logging this error. This is an issue when
  using a log aggregation facility such as Splunk. A fix is to correct
  the error in the provided rsyslog.conf.

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

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

[Touch-packages] [Bug 1702793] Re: Merge changes from upstream

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  Merge changes from upstream

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Changes to support day-of-week patching and logging to syslog were
  added to upstream (https://github.com/mvo5/unattended-upgrades) over a
  year ago. These changes are not present in the latest Xenial nor
  Trusty packages (0.90 and 0.82.1) - requesting that these changes be
  pulled from upstream.

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

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

[Touch-packages] [Bug 1703987] [NEW] New style permitnonkernelfacility imklog option inside module() doesn't work

Public bug reported:

artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw)

There are two ways to load the imklog module and pass it an option
(PermitNonKernelFacility in this case).

a) legacy
$ModLoad imklog
$KLogPermitNonKernelFacility on


b) "new style", also referred to as "v6+":
module(load="imklog" permitnonkernelfacility="on")

For a while the ubuntu package was using a mix: loading the module with
the new style, but setting the option via the legacy method. In bug
#1531622 this was fixed for yakkety+.

Problem is, upstream isn't honouring the new style option setting due to
a bug of its own: https://github.com/rsyslog/rsyslog/issues/477

With the legacy config:
#module(load="imklog" permitnonkernelfacility="on")
$ModLoad imklog
$KLogPermitNonKernelFacility on

I get kernel messages in /var/log/syslog:
root@nsn7:~# grep andreas-was-here /var/log/syslog
root@nsn7:~# echo andreas-was-here > /dev/kmsg
root@nsn7:~# grep andreas-was-here /var/log/syslog
Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
root@nsn7:~#

But with this new v6 config style:
module(load="imklog" permitnonkernelfacility="on") # provides kernel logging 
support
#$ModLoad imklog
#$KLogPermitNonKernelFacility on

The text doesn't show up in /var/log/syslog. That's the upstream bug.

** Affects: rsyslog
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: github.com/rsyslog/rsyslog/issues #477
   https://github.com/rsyslog/rsyslog/issues/477

** Also affects: rsyslog via
   https://github.com/rsyslog/rsyslog/issues/477
   Importance: Unknown
   Status: Unknown

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

Title:
  New style permitnonkernelfacility imklog option inside module()
  doesn't work

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  New

Bug description:
  artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw)

  There are two ways to load the imklog module and pass it an option
  (PermitNonKernelFacility in this case).

  a) legacy
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  
  b) "new style", also referred to as "v6+":
  module(load="imklog" permitnonkernelfacility="on")

  For a while the ubuntu package was using a mix: loading the module
  with the new style, but setting the option via the legacy method. In
  bug #1531622 this was fixed for yakkety+.

  Problem is, upstream isn't honouring the new style option setting due
  to a bug of its own: https://github.com/rsyslog/rsyslog/issues/477

  With the legacy config:
  #module(load="imklog" permitnonkernelfacility="on")
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  I get kernel messages in /var/log/syslog:
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  root@nsn7:~# echo andreas-was-here > /dev/kmsg
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
  root@nsn7:~#

  But with this new v6 config style:
  module(load="imklog" permitnonkernelfacility="on") # provides kernel logging 
support
  #$ModLoad imklog
  #$KLogPermitNonKernelFacility on

  The text doesn't show up in /var/log/syslog. That's the upstream bug.

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

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

[Touch-packages] [Bug 1675515] Re: old KLogPermitNonKernel directive error in rsyslog.conf

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

I just saw that this was fixed in yakkety:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622

I will therefore repurpose this bug to be about my findings in comment
#3

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

Title:
  old KLogPermitNonKernel directive error in rsyslog.conf

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  The rsyslog.conf provided in Xenial contains an error that is logged
  by rsyslog at startup with the short name. rsyslog ignores a
  '$PreserveFQDN on' when logging this error. This is an issue when
  using a log aggregation facility such as Splunk. A fix is to correct
  the error in the provided rsyslog.conf.

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

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

[Touch-packages] [Bug 1675515] Re: old KLogPermitNonKernel directive error in rsyslog.conf

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

On second thought, it's better to open a new bug I believe. Sorry.

** This bug has been marked a duplicate of bug 1531622
   default config still using a legacy keyword: KLogPermitNonKernelFacility

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

Title:
  old KLogPermitNonKernel directive error in rsyslog.conf

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  The rsyslog.conf provided in Xenial contains an error that is logged
  by rsyslog at startup with the short name. rsyslog ignores a
  '$PreserveFQDN on' when logging this error. This is an issue when
  using a log aggregation facility such as Splunk. A fix is to correct
  the error in the provided rsyslog.conf.

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

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

[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable

2017-07-12 Thread Ubuntu Foundations Team Bug Bot

The attachment "sound-theme-freedesktop.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
New

Bug description:
When testing stereo speakers you get the "Front left" and "Front
right" samples, but no such sample exists for mono speakers e.g.
HSP/HFP bluetooth devices.

Instead you get played the "audio-test-signal" which is white noise.
To begin with I thought this was a problem with Bluetooth or the
speaker itself, but it's just the sample being used.

There is a bug upstream to provide this sample, but in the meantime I
think playing the "audio-channel-front-center.oga" is a suitable
standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1675515] Re: old KLogPermitNonKernel directive error in rsyslog.conf

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

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

Title:
  old KLogPermitNonKernel directive error in rsyslog.conf

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  The rsyslog.conf provided in Xenial contains an error that is logged
  by rsyslog at startup with the short name. rsyslog ignores a
  '$PreserveFQDN on' when logging this error. This is an issue when
  using a log aggregation facility such as Splunk. A fix is to correct
  the error in the provided rsyslog.conf.

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

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

[Touch-packages] [Bug 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

2017-07-12 Thread Matyáš Koc

I applied the fix and it looks like it's all working now. I wan't aware
of the anonymous sockets, so I was trying wrong things.

Thank you!

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in dovecot package in Ubuntu:
  New

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

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

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

[Touch-packages] [Bug 1675515] Re: old KLogPermitNonKernel directive error in rsyslog.conf

The new option doesn't seem to be working correctly:
https://github.com/rsyslog/rsyslog/issues/477

With the old style config:
#module(load="imklog" permitnonkernelfacility="on")   # provides kernel logging 
support
$ModLoad imklog
#KLogPermitNonKernelFacility on

I get kernel messages in /var/log/syslog:
root@nsn7:~# grep andreas-was-here /var/log/syslog
root@nsn7:~# echo andreas-was-here > /dev/kmsg 
root@nsn7:~# grep andreas-was-here /var/log/syslog
Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
root@nsn7:~# 

But with this new v6 config style:
module(load="imklog" permitnonkernelfacility="on")   # provides kernel logging 
support
#$ModLoad imklog
#$KLogPermitNonKernelFacility on

I don't. Which is the github issue I mentioned.

Still, the ubuntu package is using a mix of old style vs new style when
loading the imklog module, and that won't work anyway. We either go with
v6 for both (loading and setting the option). or with legacy.

** Bug watch added: github.com/rsyslog/rsyslog/issues #477
   https://github.com/rsyslog/rsyslog/issues/477

** Also affects: rsyslog via
   https://github.com/rsyslog/rsyslog/issues/477
   Importance: Unknown
   Status: Unknown

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

Title:
  old KLogPermitNonKernel directive error in rsyslog.conf

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  The rsyslog.conf provided in Xenial contains an error that is logged
  by rsyslog at startup with the short name. rsyslog ignores a
  '$PreserveFQDN on' when logging this error. This is an issue when
  using a log aggregation facility such as Splunk. A fix is to correct
  the error in the provided rsyslog.conf.

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

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

[Touch-packages] [Bug 1703866] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2017-07-12 Thread Damien Levac

Of course and I've installed them on my main machine but that was an
upgrade over SSH and the term info were not on that remote host. All in
all, I think it was more my fault than anything else...

Maybe, to avoid this pitfall for other users, 'xterm' could be assumed
if the TERM variable is not recognized? Otherwise I think this is a non-
issue...

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in debconf package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  Was just trying to upgrade from 14.04 to 16.04 and the installer
  reported that issue and asked me to fill this...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Tue Jul 11 17:05:23 2017
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-09-06 (1404 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

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

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

[Touch-packages] [Bug 1703866] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

Damien, interesting; did st provide terminfo pieces to install too?

Thanks

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in debconf package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  Was just trying to upgrade from 14.04 to 16.04 and the installer
  reported that issue and asked me to fill this...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Tue Jul 11 17:05:23 2017
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-09-06 (1404 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

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

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

[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable

** Description changed:

When testing stereo speakers you get the "Front left" and "Front right"
samples, but no such sample exists for mono speakers e.g. HSP/HFP
bluetooth devices.

Instead you get played the "audio-test-signal" which is white noise. To
- being with I thought this was a problem with Bluetooth or the speaker
+ begin with I thought this was a problem with Bluetooth or the speaker
itself, but it's just the sample being used.

There is a bug upstream to provide this sample, but in the meantime I
think playing the "audio-channel-front-center.oga" is a suitable
standin.

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

Title:
Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
New

Bug description:
When testing stereo speakers you get the "Front left" and "Front
right" samples, but no such sample exists for mono speakers e.g.
HSP/HFP bluetooth devices.

Instead you get played the "audio-test-signal" which is white noise.
To begin with I thought this was a problem with Bluetooth or the
speaker itself, but it's just the sample being used.

There is a bug upstream to provide this sample, but in the meantime I
think playing the "audio-channel-front-center.oga" is a suitable
standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

2017-07-12 Thread Jeremy Gabriel

When I run the dpkg command, it doesn't list anything.just brings up
the prompt again.

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

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   libssl1.0.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:47:55 2017
  DuplicateSignature:
   package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
   dpkg: error processing package libssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-15 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

Oh, I always forget that unix has _anonymous_ sockets too. Silly
complicated things. Thanks John.

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in dovecot package in Ubuntu:
  New

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

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

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

[Touch-packages] [Bug 1703946] Automatically added comment

Added to Trello: https://trello.com/c/n6MT5npU/193-bug1703946-dedicated-
mono-test-sound-is-unavailable

** Tags removed: desktop-trello-import

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

Title:
  Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
  New

Bug description:
  When testing stereo speakers you get the "Front left" and "Front
  right" samples, but no such sample exists for mono speakers e.g.
  HSP/HFP bluetooth devices.

  Instead you get played the "audio-test-signal" which is white noise.
  To being with I thought this was a problem with Bluetooth or the
  speaker itself, but it's just the sample being used.

  There is a bug upstream to provide this sample, but in the meantime I
  think playing the "audio-channel-front-center.oga" is a suitable
  standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable

As per: 
http://packaging.ubuntu.com/html/traditional-packaging.html#creating-a-debdiff
this patch includes an updated maintainers section in the debian/control file.


** Patch added: "sound-theme-freedesktop.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+attachment/4913559/+files/sound-theme-freedesktop.debdiff

** Tags added: desktop-trello-import

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

Title:
  Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
  New

Bug description:
  When testing stereo speakers you get the "Front left" and "Front
  right" samples, but no such sample exists for mono speakers e.g.
  HSP/HFP bluetooth devices.

  Instead you get played the "audio-test-signal" which is white noise.
  To being with I thought this was a problem with Bluetooth or the
  speaker itself, but it's just the sample being used.

  There is a bug upstream to provide this sample, but in the meantime I
  think playing the "audio-channel-front-center.oga" is a suitable
  standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1432871] Re: `df` shows bind mounts instead of real mounts.

2017-07-12 Thread Eric Jensen

Actually I was wrong, on some boxes with coreutils_8.21-1ubuntu5.4 it
was working fine. This is really an initramfs-tools bug:
https://bugs.launchpad.net/ubuntu/trusty/+source/coreutils/+bug/1535349

I had the version with the fix, but needed to reboot again to get it to
take effect I guess. Rebooting after initramfs-tools - 0.103ubuntu4.3
fixed the issue everywhere for me even on coreutils_8.21-1ubuntu5.4

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

Title:
`df` shows bind mounts instead of real mounts.

Status in coreutils package in Ubuntu:
Fix Released
Status in coreutils source package in Trusty:
Fix Released
Status in coreutils source package in Vivid:
Fix Released
Status in coreutils source package in Wily:
Fix Released

Bug description:
[Impact]

* df displays bind mounts instead of "real" mounts if the bind mount
is mounted to a shorter directory.

* justification - When trusty moved to using /proc/mounts this
changed behavior from precise. Additionally it doesn't make sense
that a bind mount should show up in df over a real root mount.

* Explanation - These patches change behavior of df to rely on
/proc/self/mountinfo which has more complete info than /proc/mounts.
Such as what directory of the filesystem was used as the source of the
mount. Additionally given this new information there is a patch on df
itself to make use of this new information.

[Test Case]

* $ mount

192.168.1.2:/raid on /raid type nfs
/dev/sdc5 on /data type ext4 (rw)

/data/a on /a type none (rw,bind)
/raid/temp on /b type none (rw,bind)

$df
Filesystem 1K-blocks Used Available Use% Mounted on

/data/a 449830616 229975284 196982196 54% /a
/raid/temp 7752072192 5581343744 1780023296 76% /b

I'd expect to see the real mount prioritized over the bind mount. Like so.
$df
Filesystem 1K-blocks Used Available Use% Mounted on

/dev/sdc5449830616 229975284 196982196 54% /data
192.168.1.2:/raid 7752072192 5581438976 1779929088 76% /raid

[Regression Potential]

* Patch is upstreamed.

* df command now relies on /proc/self/mountinfo

[Other Info]

* The behavior of df, mount and similar number of other commands has
changed going forward. Previously these commands all processed
/etc/mtab which was maintained by the mount command. Going forward
they still process /etc/mtab, but this is simply a symlink to
/proc/mounts now which is maintained by the kernel and slightly more
accurate. Unlike the mount command, the kernel makes no distinction
between bind mounts and normal mounts. This is evident by the fact
that you can mount a device, bind mount from that device, and then
unmount the original mount. The default behavior of df in this case
is to simply pick the mounted directory for a device that is the
shortest since it has no other information to go on from /proc/mounts.
Moving to using /proc/self/mountinfo resolves this issue, and is what
upstream is doing moving forward.

* In order to solve this issue, I have written patches and got them
integrated upstream.
gnulib commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=c6148bca89e9465fd6ba3a10d273ec4cb58c2dbe
and
coreutils commit:
http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=3babaf83875ceac896c8dd3a64248e955dfecef9
have been authored by me.

While attempting to push these patches into Ubuntu, it became apparent
that our version of coreutils does not contain the requisite patches
to correctly support /proc/self/mountinfo. /proc/self/mountinfo gives
more complete information than /proc/self/mounts which /etc/mtab now
points to. Using /proc/self/mountinfo is the upstream way of doing
things, and it allows us to resolve this specific bug.

Patches required in order to support /proc/self/mountinfo are.
Origin: upstream, gnulib - http://git.savannah.gnu.org/gitweb/?p=gnulib.git
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=3ea43e02541ece750ffc6cd1dfe34195421b4ef3
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=2768ceb7994506e2cfba88be3b6bd13ef5440a90
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=de1cbdd48244c66c51a3e2bc1594ac3ad32ce038
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=3fb6e360363744462ce15c381f0b116c6fc4ce82

Origin: upstream, coreutils -
http://git.savannah.gnu.org/gitweb/?p=coreutils.git
commit:
http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=1b1c40e1d6f8cf30b6c7c9d31bbddbc3d5cc72e6
Original bug.

Depending on mount path length df sometimes prioritizes showing bind mounts
over real

[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso

2017-07-12 Thread dann frazier

The MIR has been approved, so please go ahead and add numactl to the
server seed.

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

Title:
  please include numactl on the ubuntu-server iso

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Xenial:
  New

Bug description:
  I've submitted an MIR for the numactl binary package at: LP: #1700824.
  Assuming that is approved, please also include this on the server seed, which 
I believe is necessary for it to appear on the ubuntu-server ISOs.

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

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

[Touch-packages] [Bug 1703941] Re: bluetooth not work and wifi some time disable and enable

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1703941

Title:
  bluetooth not work and wifi some time disable and enable

Status in xorg package in Ubuntu:
  New

Bug description:
  my bluetooth and wifi hardware is belongs to Ralink and its detail is
  rt3290, It problem is that it sometime auto disable till the hareware
  which ih turn on and when trying to enable then it not enable its
  fail.My bluetooth is not work infact it doesn't show visibility enable
  option and not work in any ubuntu version.Please tell me what to do?to
  inform me please send me email at "abhirajp...@gmail.com"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 12 22:16:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2017-07-11 (1 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=6e79f8f5-ebf2-4c7a-a87e-a9f61697f325 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  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: Wed Jul 12 21:45:38 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   18769 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1703866] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2017-07-12 Thread Damien Levac

I eventually succeeded to finish upgrading the system. The only thing I
had to manually fix was to set TERM=xterm because the installer was not
able to pop-up the purple selection screen with my self-compiled st
terminal.

Do not know if this is related to this automatically generated bug
report though...

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in debconf package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  Was just trying to upgrade from 14.04 to 16.04 and the installer
  reported that issue and asked me to fill this...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Tue Jul 11 17:05:23 2017
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-09-06 (1404 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

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

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

[Touch-packages] [Bug 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

2017-07-12 Thread John Johansen

This is caused by an anonymous socket communication channel between
dovecot and anvil. If this problem is not happening in 16.04 (unless you
are using the release kernel) then it will be because o a change to
dovecot, newer versions of apparmor have been SRUed back to 16.04

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in dovecot package in Ubuntu:
  New

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

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

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

[Touch-packages] [Bug 1188475] Re: ldap group doesn't work

For some reason bug expiration isn't working for this bug. Given that
there were no updates for over two months, I'm marking it as invalid.

Feel free to reopen it if you have more information about the problem.

Thanks!


** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  ldap group doesn't work

Status in cyrus-sasl2 package in Ubuntu:
  Invalid

Bug description:
  Hello!

  I wrote almost the same mail to sasl mail list, but , I guess, it is
  good to fix in 12.04...

  This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04

  Problem is that after user is authentificated with ldap bind , ldap 
  connection for checking user in group ( lak_group_member function )
  is made with this user's bind, not bind parameters from config file.
  User can not ( and have not in our case- I don't know why , but this is 
  not real problem ) have access to ldap groups.
  And so, authentication is always fail.

  I added unbind and anonymous bind ( enough in our case):

  /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig 
  lak.c
  --- lak.c.orig2013-06-07 09:15:20.098788278 +0400
  +++ lak.c2013-06-07 09:22:31.504774185 +0400
  @@ -1342,6 +1342,10 @@
   if (rc != LAK_OK)
   goto done;

  +lak_unbind (lak );
  +rc  = lak_bind(lak, "");
  +
  +
   rc = ldap_search_st(lak->ld, group_search_base, 
  lak->conf->group_scope, group_filter, (char **) group_attrs, 0, 
  &(lak->conf->timeout), );
   switch (rc) {
   case LDAP_SUCCESS:

  
  but, it is obvoius that rebind should be done with credintials from 
  config, but this is over my head :-(

  Could you, please, fix this bug correctly?

  Thank you!

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

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

[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

I'm curious how we can work around this bug. If you're affected please
report the results of:

dpkg -l | awk '/^iH/ { print $2 }'

This shows which specific packages are half-installed on your systems.

With the list of packages this returns, please also report success or
failure of:

sudo apt-get install --reinstall ALL PACKAGES FROM THE HALF-INSTALLED
LIST

Thanks

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

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   libssl1.0.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:47:55 2017
  DuplicateSignature:
   package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
   dpkg: error processing package libssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-15 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

2017-07-12 Thread Matyáš Koc

It is suprising for me too, as I don't know about this problem on 16.04
LTS and I could not reproduce it. It was probably introduced in 17.04 or
around that.

I have done some experimenting now and I managed to find out that the
problem is caused only by profile for /usr/lib/dovecot/anvil (not
dovecot profile itself). Also, adding just "singal," to the profile
didn't work.

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in dovecot package in Ubuntu:
  New

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

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

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

[Touch-packages] [Bug 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

2017-07-12 Thread John Johansen

Its an anonymous socket. The best you can do is

to /usr/sbin/dovecot/anvil add
  unix (send, receive) peer=(label=/usr/sbin/dovecot),

to /usr/sbin/dovecot add
  unix (send, receive) peer=(label=/usr/sbin/dovecot/anvil),

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in dovecot package in Ubuntu:
  New

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

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

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

[Touch-packages] [Bug 1703866] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

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

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in debconf package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  Was just trying to upgrade from 14.04 to 16.04 and the installer
  reported that issue and asked me to fill this...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Tue Jul 11 17:05:23 2017
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-09-06 (1404 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

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

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

[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable

debdiff to do the symlink


** Patch added: "sound-theme-freedesktop.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+attachment/4913547/+files/sound-theme-freedesktop.debdiff

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

Title:
  Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
  New

Bug description:
  When testing stereo speakers you get the "Front left" and "Front
  right" samples, but no such sample exists for mono speakers e.g.
  HSP/HFP bluetooth devices.

  Instead you get played the "audio-test-signal" which is white noise.
  To being with I thought this was a problem with Bluetooth or the
  speaker itself, but it's just the sample being used.

  There is a bug upstream to provide this sample, but in the meantime I
  think playing the "audio-channel-front-center.oga" is a suitable
  standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1703828] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: package libssl1.0.0:amd64 is not ready for configuration cannot configure (current status 'hal

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package libssl1.0.0:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  I tried to install 'electrum' application by copy and pasting sudo
  apt-get install python-qt4 python-pip  (in the Terminal Emulator) from
  website https://electrum.org/#download.


  I had problems with updating ubuntu studio last week. OS will not
  update now. I think it was because I auto-installed a bitcoin wallet
  called exodus which is partly non-open-source. I have v1.28.2
  installed. It works but doesn't seen fully installed.

  https://www.exodus.io/releases/

  When I try to update exodus a problem occurs with mozilla.

  Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-lowlatency 4.4.70
  Uname: Linux 4.4.0-83-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jul 12 13:09:13 2017
  DuplicateSignature:
   package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.6
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
package libssl1.0.0:amd64 is not ready for configuration
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-08-04 (341 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package libssl1.0.0:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1432871] Re: `df` shows bind mounts instead of real mounts.

2017-07-12 Thread Eric Jensen

Perhaps it was reverted?  This actually works fine for me on trusty in
the older 8.21-1ubuntu5.1 but not the newer 8.21-1ubuntu5.3 or
8.21-1ubuntu5.4  I ran into the problem with it outputting UUID because
amazon's aws ec2 cloudwatch script mon-put-instance-data.pl uses it as
its Filesystem dimension and my alarms all of a sudden had insufficient
data after apt-get upgrade:

ubuntu@ip-10-0-1-100:~$ dpkg --list coreutils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  
Architecture Description
+++-===---===
ii  coreutils   8.21-1ubuntu5.4  amd64  
  GNU core utilities
ubuntu@ip-10-0-1-100:~$ /bin/df -k -l -P /
Filesystem 1024-blocksUsed 
Available Capacity Mounted on
/dev/disk/by-uuid/aef583e5-28c9-4161-ac41-bc0f2c3f6b61   103071868 6235644  
92542660   7% /
ubuntu@ip-10-0-1-100:~$ sudo dpkg -i coreutils_8.21-1ubuntu5.3_amd64.deb 
>/dev/null
ubuntu@ip-10-0-1-100:~$ /bin/df -k -l -P /
Filesystem 1024-blocksUsed 
Available Capacity Mounted on
/dev/disk/by-uuid/aef583e5-28c9-4161-ac41-bc0f2c3f6b61   103071868 6235632  
92542672   7% /
ubuntu@ip-10-0-1-100:~$ sudo dpkg -i coreutils_8.21-1ubuntu5.1_amd64.deb 
>/dev/null
ubuntu@ip-10-0-1-100:~$ /bin/df -k -l -P /
Filesystem 1024-blocksUsed Available Capacity Mounted on
/dev/xvda1   103071868 6235628  92542676   7% /

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

Title:
  `df` shows bind mounts instead of real mounts.

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Trusty:
  Fix Released
Status in coreutils source package in Vivid:
  Fix Released
Status in coreutils source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * df displays bind mounts instead of "real" mounts if the bind mount
  is mounted to a shorter directory.

   * justification - When trusty moved to using /proc/mounts this
  changed behavior from precise.  Additionally it doesn't make sense
  that a bind mount should show up in df over a real root mount.

   * Explanation - These patches change behavior of df to rely on
  /proc/self/mountinfo which has more complete info than /proc/mounts.
  Such as what directory of the filesystem was used as the source of the
  mount.  Additionally given this new information there is a patch on df
  itself to make use of this new information.

  [Test Case]

   * $ mount
  
  192.168.1.2:/raid on /raid type nfs
  /dev/sdc5 on /data type ext4 (rw)
  
  /data/a on /a type none (rw,bind)
  /raid/temp on /b type none (rw,bind)

  $df
  Filesystem   1K-blocks   Used  Available Use% Mounted on
  
  /data/a  449830616  229975284  196982196  54% /a
  /raid/temp  7752072192 5581343744 1780023296  76% /b
  

  I'd expect to see the real mount prioritized over the bind mount.  Like so.
  $df
  Filesystem   1K-blocks   Used  Available Use% Mounted on
  
  /dev/sdc5449830616  229975284  196982196  54% /data
  192.168.1.2:/raid   7752072192 5581438976 1779929088  76% /raid
  

  [Regression Potential]

   * Patch is upstreamed.

   * df command now relies on /proc/self/mountinfo

  [Other Info]

   * The behavior of df, mount and similar number of other commands has
  changed going forward.  Previously these commands all processed
  /etc/mtab which was maintained by the mount command.  Going forward
  they still process /etc/mtab, but this is simply a symlink to
  /proc/mounts now which is maintained by the kernel and slightly more
  accurate.  Unlike the mount command, the kernel makes no distinction
  between bind mounts and normal mounts.  This is evident by the fact
  that you can mount a device, bind mount from that device, and then
  unmount the original mount.  The default behavior of df in this case
  is to simply pick the mounted directory for a device that is the
  shortest since it has no other information to go on from /proc/mounts.
  Moving to using /proc/self/mountinfo resolves this issue, and is what
  upstream is doing moving forward.

   * In order to solve this issue, I have written patches and got them 
integrated upstream.
  gnulib commit: 
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=c6148bca89e9465fd6ba3a10d273ec4cb58c2dbe
 and
  coreutils commit: 
http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=3babaf83875ceac896c8dd3a64248e955dfecef9

[Touch-packages] [Bug 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

I'm surprised about the "addr=none peer_addr=none" -- any idea what's
going on here?

Thanks

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

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in dovecot package in Ubuntu:
  New

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

2017-07-12 Thread Jason Mast

While it is helpful for new users to have to google shell commands and
identify solutions to problems, this simply occurs too often. The
solution is the same every time. It is repetitive and annoying,

the script could store the new and old information in different
locations to avoid the lack of space, the boot could be made larger by
default, options could be presented to the user rather than simply
failing, backup information for old kernals could be stored elsewhere
(and only the most recent moved to boot for compatibility) ... etc.

a sample dialog would be 
"there is not enough space for the boot information, there are too many items 
being retained in /boot, but it is strongly suggested that you maintain some 
backup kernals as updates can cause issues with new or old hardware. Please 
choose the number of old backups to maintain and the frequency with which they 
should be replaced"
then have a dialog that lists options like (daily weekly monthly yearly and no 
backups) and an option to store them tarred in another location that does not 
fill up ... also it should list the size of the individual groups of files (by 
date) ... and it should explain that this is a kernal backup not a file backup

also boot should be bigger

and there should be a semipermanent configuration change listed on the
forum rather than the delete old kernals solution - which is just a
bandaid in that you will just have to repeatedly do it, because
sometimes i just want to turn the thing on and play minecraft (and my
timesink of choice is not system administration)

Anyway,the point of "automatic updates" is they happen automatically,
and you dont have to mess with them, this bug forces you to mess with
them

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable

Simply symlinking works:

ln - s audio-channel-front-center.oga audio-channel-mono.oga

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

Title:
  Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
  New

Bug description:
  When testing stereo speakers you get the "Front left" and "Front
  right" samples, but no such sample exists for mono speakers e.g.
  HSP/HFP bluetooth devices.

  Instead you get played the "audio-test-signal" which is white noise.
  To being with I thought this was a problem with Bluetooth or the
  speaker itself, but it's just the sample being used.

  There is a bug upstream to provide this sample, but in the meantime I
  think playing the "audio-channel-front-center.oga" is a suitable
  standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable

https://bugs.freedesktop.org/show_bug.cgi?id=100977

** Bug watch added: freedesktop.org Bugzilla #100977
   https://bugs.freedesktop.org/show_bug.cgi?id=100977

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

Title:
  Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
  New

Bug description:
  When testing stereo speakers you get the "Front left" and "Front
  right" samples, but no such sample exists for mono speakers e.g.
  HSP/HFP bluetooth devices.

  Instead you get played the "audio-test-signal" which is white noise.
  To being with I thought this was a problem with Bluetooth or the
  speaker itself, but it's just the sample being used.

  There is a bug upstream to provide this sample, but in the meantime I
  think playing the "audio-channel-front-center.oga" is a suitable
  standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1703946] [NEW] Dedicated mono test sound is unavailable

Public bug reported:

When testing stereo speakers you get the "Front left" and "Front right"
samples, but no such sample exists for mono speakers e.g. HSP/HFP
bluetooth devices.

Instead you get played the "audio-test-signal" which is white noise. To
being with I thought this was a problem with Bluetooth or the speaker
itself, but it's just the sample being used.

There is a bug upstream to provide this sample, but in the meantime I
think playing the "audio-channel-front-center.oga" is a suitable
standin.

** Affects: sound-theme-freedesktop (Ubuntu)
Importance: Undecided
Status: New

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

Title:
Dedicated mono test sound is unavailable

Status in sound-theme-freedesktop package in Ubuntu:
New

Bug description:
When testing stereo speakers you get the "Front left" and "Front
right" samples, but no such sample exists for mono speakers e.g.
HSP/HFP bluetooth devices.

Instead you get played the "audio-test-signal" which is white noise.
To being with I thought this was a problem with Bluetooth or the
speaker itself, but it's just the sample being used.

There is a bug upstream to provide this sample, but in the meantime I
think playing the "audio-channel-front-center.oga" is a suitable
standin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions

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

[Touch-packages] [Bug 1701198] Re: dialog displayed even if there's an unreportable reason

2017-07-12 Thread Karl-Philipp Richter

I've seen "truncated" report files being listed as `UnreportableReason`.
In that case showing the reporting dialog doesn't make sense. I doubt
that users who are not apport developers pay attention to that field
without any further feedback/interaction from the apport dialog, but
they should since if they're already willing to report bugs, they're
most likely willing to update outdated packages.

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

Title:
  dialog displayed even if there's an unreportable reason

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  A dialog about a crashing application is displayed even if there's an
  "UnreportableReason" property present (which one only find when
  scrolling down the dialog). Displaying the dialog in that case doesn't
  make too much sense because the issue can't be reported with useful
  information and the user should either not be annoyed or get the
  opportunity to deactivate the displaying of the `apport-gtk` dialog if
  the report is broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Jun 29 10:29:35 2017
  InstallationDate: Installed on 2015-12-12 (564 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (58 days ago)

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

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

[Touch-packages] [Bug 1703649] Re: Traceroute needs net_admin capability for unknown reason

2017-07-12 Thread Vincas Dargis

Added systemd because:
# apt-cache show libnss-resolve | fgrep Source
Source: systemd

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

Title:
  Traceroute needs net_admin capability for unknown reason

Status in systemd package in Ubuntu:
  New
Status in traceroute package in Ubuntu:
  New

Bug description:
  With help of AppArmor on 17.04 and 17.10 I've discovered that
  traceroute needs net_admin capabilities.

  My plan is to update [0] AppArmor profile to fix various DENIED
  messages in syslog/audit for traceroute, though I am not sure about
  allowing, or denying, net_admin capability.

  Looks like traceroute tries to set SO_RCVBUFFORCE and SO_SNDBUFFORCE:

  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)

  What is interesting, that traceroute developer does not recall
  changing these values [1]. On Debian Sid and OpenSuse Tumbleweed this
  issue does not reproduce either.

  Could it be some Ubuntu-specific patch in the works? It seems that
  traceroute works OK without net_admin...

  Thanks!

  [0] 
https://code.launchpad.net/~talkless/apparmor/fix_traceroute_tcp/+merge/326260
  [1] https://sourceforge.net/p/traceroute/mailman/message/35927818/

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

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

[Touch-packages] [Bug 1703649] Re: Traceroute needs net_admin capability for unknown reason

2017-07-12 Thread Vincas Dargis

Looks like culprit is libnss_resonve.so.

First of all, to reproduce, I have to use hostname like google.com. If I
give traceroute an IP address, there are no setsockopt calls that needs
net_admin cap.

Here's gdb log, breakpointed on setsockopt, dumped registers (you can
see rdx set to "33" so that's one of SO_RCVBUFFORCE/SO_SNDBUFFORCE), and
backtrace, that leads to /lib/x86_64-linux-gnu/libnss_resolve.so.2:

Breakpoint 1 (setsockopt) pending.
Starting program: /usr/sbin/traceroute -T google.com
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Breakpoint 1, setsockopt () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
rax0x34000  212992
rbx0x55ad9953abe0   94204090100704
rcx0x7ffc27aac6d0   140720973989584
rdx0x21 33
rsi0x1  1
rdi0x3  3
rbp0x7ffc27aac6d0   0x7ffc27aac6d0
rsp0x7ffc27aac6c8   0x7ffc27aac6c8
r8 0x4  4
r9 0x0  0
r100x7ffc27aac6d0   140720973989584
r110x202514
r120x3  3
r130x7ffc27aac6d4   140720973989588
r140x7ffc27aac760   140720973989728
r150x55ad9953abe0   94204090100704
rip0x7f057a78a320   0x7f057a78a320 
eflags 0x293[ CF AF SF IF ]
cs 0x33 51
ss 0x2b 43
ds 0x0  0
es 0x0  0
fs 0x0  0
gs 0x0  0
#0  setsockopt () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f057af2cd43 in ?? () from /lib/x86_64-linux-gnu/libnss_resolve.so.2
#2  0x7f057af1ccd5 in ?? () from /lib/x86_64-linux-gnu/libnss_resolve.so.2
#3  0x7f057af46f02 in ?? () from /lib/x86_64-linux-gnu/libnss_resolve.so.2
#4  0x7f057af2287d in _nss_resolve_gethostbyname4_r () from 
/lib/x86_64-linux-gnu/libnss_resolve.so.2
#5  0x7f057a76e16f in gaih_inet (name=name@entry=0x7ffc27aae76e 
"google.com", service=, req=req@entry=0x7ffc27aad400, 
pai=pai@entry=0x7ffc27aacf28, naddrs=naddrs@entry=0x7ffc27aacf24, 
tmpbuf=tmpbuf@entry=0x7ffc27aacf90) at ../sysdeps/posix/getaddrinfo.c:848
#6  0x7f057a770448 in __GI_getaddrinfo (name=, 
service=, hints=0x7ffc27aad400, pai=0x7ffc27aad3f8) at 
../sysdeps/posix/getaddrinfo.c:2391
#7  0x55ad9791e326 in ?? ()
#8  0x55ad9791e4b3 in ?? ()
#9  0x55ad97921cae in ?? ()
#10 0x55ad9791a7d1 in ?? ()
#11 0x7f057a6a13f1 in __libc_start_main (main=0x55ad9791a700, argc=3, 
argv=0x7ffc27aad888, init=, fini=, 
rtld_fini=, stack_end=0x7ffc27aad878)
at ../csu/libc-start.c:291
#12 0x55ad9791b3fa in ?? ()


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

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

Title:
  Traceroute needs net_admin capability for unknown reason

Status in systemd package in Ubuntu:
  New
Status in traceroute package in Ubuntu:
  New

Bug description:
  With help of AppArmor on 17.04 and 17.10 I've discovered that
  traceroute needs net_admin capabilities.

  My plan is to update [0] AppArmor profile to fix various DENIED
  messages in syslog/audit for traceroute, though I am not sure about
  allowing, or denying, net_admin capability.

  Looks like traceroute tries to set SO_RCVBUFFORCE and SO_SNDBUFFORCE:

  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)
  setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
  setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation 
not permitted)

  What is interesting, that traceroute developer does not recall
  changing these values [1]. On Debian Sid and OpenSuse Tumbleweed this
  issue does not reproduce either.

  Could it be some Ubuntu-specific patch in the works? It seems that
  traceroute works OK

[Touch-packages] [Bug 1573786] Re: gdb Process record does not support instruction 0xc5

2017-07-12 Thread silvio

Just a pointer to a thread with a good explanation about this problem:
https://sourceware.org/ml/gdb/2016-08/msg00025.html

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

Title:
  gdb Process record does not support instruction 0xc5

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  the 'process record' feature of gdb allows reverse debugging.  neato.
  but on Ubuntu-16.04 it fails to work, complaining about an unhandled
  instruction.

  % gdb simple 
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from simple...done.
  (gdb) b main
  Breakpoint 1 at 0x400db7: file 
/home/robl/work/mpich/src/mpi/romio/test/simple.c, line 26.
  (gdb) run
  Starting program: /home/robl/work/build/mpich-logfs/src/mpi/romio/test/simple 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  Breakpoint 1, main (argc=1, argv=0x7fffd698)
  at /home/robl/work/mpich/src/mpi/romio/test/simple.c:26
  26  {
  (gdb) record
  (gdb) continue
  Continuing.
  Process record does not support instruction 0xc5 at address 0x77dee6e7.
  Process record: failed to record execution log.

  Program stopped.
  _dl_runtime_resolve_avx () at ../sysdeps/x86_64/dl-trampoline.h:81
  81  ../sysdeps/x86_64/dl-trampoline.h: No such file or directory.

  
  If we examine the address we see this:

  (gdb) x/i 0x77dee6e7
  => 0x77dee6e7 <_dl_runtime_resolve_avx+71>: vmovdqa %ymm0,(%rsp)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdb 7.11-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 15:34:03 2016
  InstallationDate: Installed on 2015-09-10 (225 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1701198] Re: dialog displayed even if there's an unreportable reason

The UnreportableReason field does contain information about packages
being out of date on your system. If I saw that message I'd update my
system and try the operation again, so I think it is useful.

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

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

Title:
  dialog displayed even if there's an unreportable reason

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  A dialog about a crashing application is displayed even if there's an
  "UnreportableReason" property present (which one only find when
  scrolling down the dialog). Displaying the dialog in that case doesn't
  make too much sense because the issue can't be reported with useful
  information and the user should either not be annoyed or get the
  opportunity to deactivate the displaying of the `apport-gtk` dialog if
  the report is broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Jun 29 10:29:35 2017
  InstallationDate: Installed on 2015-12-12 (564 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (58 days ago)

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

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

[Touch-packages] [Bug 1702601] Re: package winbind (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1

Remember that if you update or reinstall this printer driver again in
the future, it will undo this fix and you will have to apply it again.

Cheers! :)


** Changed in: samba (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package winbind (not installed) failed to install/upgrade: подпроцесс
  установлен сценарий post-removal возвратил код ошибки 1

Status in apport package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Invalid

Bug description:
  Ошибка произошла после обновления пакетов Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: winbind (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   winbind: Purge
   samba: Configure
   system-config-samba: Configure
   NULL: ConfigurePending
  Architecture: amd64
  BothFailedConnect: Yes
  Date: Thu Jul  6 11:05:35 2017
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-05-12 (54 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  NmbdLog:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package winbind (not installed) failed to install/upgrade: подпроцесс 
установлен сценарий post-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)

2017-07-12 Thread Andy Pomfret

Just upgraded to 16.04 and have the same issue. My pulseaudio version
is also 1:8.0-0ubuntu3.3. I also can't apply the workaround in comment
#20 because all audio sockets are in use.

In case it helps: if the sound settings window (unity-control-centre
sound) is open and has focus, then 'Digital Output (S/PDIF)' becomes
selected at exactly the time that the indicator appears, regardless of
which output device was previously selected. I can't find a way to
disable (not simply mute) the S/PDIF output to see if that helps.

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

Title:
Volume notification keeps popping up constantly (the notify-OSD bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Fix Released

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

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

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

[Touch-packages] [Bug 1703195] Re: Unable to report VirtualBox bug because of apport bug - could find no obvious other way to report any bugs

The help for ubuntu-bug indicates that it can take the following
arguments:

 $ ubuntu-bug --help
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash 
file]

I think it'd be a bit of work to add in support to check whether or not
the argument is a program e.g. VirtualBox and not a package or symptom.

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

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

** Summary changed:

- Unable to report VirtualBox bug because of apport bug - could find no obvious 
other way to report any bugs
+ ubuntu-bug doesn't check if the argument is a program associated with a 
package

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

Title:
  ubuntu-bug doesn't check if the argument is a program associated with
  a package

Status in apport package in Ubuntu:
  Triaged

Bug description:
  I type
  Alt-F2 ubuntu-bugs VirtualBox
  apport says Application not installed !
  But when I just type
  ubuntu-bugs VirtualBox
  ubuntu starts VirtualBox (so it DOES know it's installed)

  Since upgarding from 12.04 to 14.04 to 16.04 LTS VirtualBox locks up
  on the machine completely, I can't kill any processes cleanly (even as
  root equivalent) so I have to log out (attempt repeatedly) or mostly I
  need to do a console shutdown - r 0

  I have reported this to Oracle VirtualBox, and have lots of info I can
  supply to help isolate the bug which I am well on way to isolating,
  but my question here is: Is there an alternate method (documented I
  may have missed) to report bug with VirtualBox (or any app) that
  crashes / fails to work with apport?

  Thanks for any help!

  Regards,
  Phil

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-docs 16.04.4
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul  9 21:23:35 2017
  InstallationDate: Installed on 2012-10-13 (1730 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-docs
  UpgradeStatus: Upgraded to xenial on 2017-07-07 (2 days ago)

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

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

[Touch-packages] [Bug 1703326] Re: Lock screen wallpaper is a plain blue screen

Once the wallpaper is done, we also need to tweak the colours (and
layout if possible).

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

Title:
  Lock screen wallpaper is a plain blue screen

Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  The default lock screen wallpaper in Artful is currently a plain blue
  screen.

  This is probably because the default wallpaper file doesn't exist on
  Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg).

  This should be the default wallpaper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1703326/+subscriptions

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

[Touch-packages] [Bug 1703326] Re: Lock screen wallpaper is a plain blue screen

** Attachment added: "gnome-shell-theme.gresource"
   
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1703326/+attachment/4913508/+files/gnome-shell-theme.gresource

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

Title:
  Lock screen wallpaper is a plain blue screen

Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  The default lock screen wallpaper in Artful is currently a plain blue
  screen.

  This is probably because the default wallpaper file doesn't exist on
  Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg).

  This should be the default wallpaper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1703326/+subscriptions

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

[Touch-packages] [Bug 1703326] Re: Lock screen wallpaper is a plain blue screen

Method to "fix":

Extract /usr/share/gnome-shell/gnome-shell-theme.gresource
copy in the wallpaper.  It seems to need to be compiled in to the gresource 
file.
edit gnome-shell.theme.gresource.xml to add the local wallpaper
edit gnome-shell.css to set it
compile it back up with glib-compile-resources

Attached is a compiled resource with the wallpaper in it.  It's just a
hacky test.

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

Title:
  Lock screen wallpaper is a plain blue screen

Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  The default lock screen wallpaper in Artful is currently a plain blue
  screen.

  This is probably because the default wallpaper file doesn't exist on
  Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg).

  This should be the default wallpaper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1703326/+subscriptions

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

[Touch-packages] [Bug 1703598] Re: [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your sources.list'

Could you add your sources.list file?

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

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

Title:
  [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your
  sources.list'

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  I get that error when I do this:

  apport-retrace -g -R -S system -v crash-file.crash

  ERROR: E:You must put some 'source' URIs in your sources.list

  - But I think they are already there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport-retrace 2.20.1-0ubuntu2.9
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportLog:
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: called for pid 2837, 
signal 11, core limit 0
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: executable: 
/usr/bin/signon-ui (command line "/usr/bin/signon-ui")
   ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3064) Tue Jul 11 12:57:44 2017: wrote report 
/var/crash/_usr_bin_signon-ui.1000.crash
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 11 14:02:02 2017
  InstallationDate: Installed on 2017-06-21 (19 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703838] Re: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try

2017-07-12 Thread fargoth

More system information:

lspci -vn gives:

05:00.0 0280: 8086:24f3 (rev 3a)
Subsystem: 8086:1010
Flags: bus master, fast devsel, latency 0, IRQ 142
Memory at df10 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-a7-a0-ff-ff-a3-07-c8
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

Also attached wpa_supplicant log (although I set the log level to debug too 
late for this time).
Notice that wpa_supplicant stops doing group rekeying about 15 minutes before 
the network disconnected (around 11:25), and all the messages from 13:57 and on 
are from the 2 reconnection attempts. It seems there was no automatic attempt 
at reconnection that reached wpa_supplicant.

** Attachment added: "wpa_supplicant log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+attachment/4913485/+files/wpa_sup%20failure%20to%20reconnect2

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

Title:
  Failure to automatically reconnect after drop - requiring manual
  reconnect, only successful after second try

Status in network-manager package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04 (64 bit)
  Package version 1.4.4-1ubuntu3.1


  This happened to me 3 times today:

  The connection drops and is not automatically restored, even though
  the network is visible in the nm-applet.

  Manually clicking on the network to connect, results in an animation
  of the nm-applet showing it's trying, but it gives up after a while
  and changes the icon to up\down arrows instead of the wifi sign.

  Clicking on it again, and selecting my network again, results in an
  almost instant reconnection, which implies that the computer should
  have known to do it automatically instead of requiring me to tell it
  to connect again (let alone twice).

  Here is the journal from a system startup:

  https://pastebin.com/hGrFEWiU

  And here is the journal from one such unsuccessful reconnect.
  I've added (*** comments ***) to mark where I've manually tried to reconnect 
(twice, second time successfully):

  https://pastebin.com/TAyt6McQ

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

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

[Touch-packages] [Bug 1703882] Re: systemd-networkd does not pick up dns-search from DHCP

2017-07-12 Thread Dimitri John Ledkov

Correct this is an identified regression in systemd, we will be
switching the default to trust search domains by default.

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

Title:
  systemd-networkd does not pick up dns-search from DHCP

Status in systemd package in Ubuntu:
  New

Bug description:
  When using networkd as renderer for netplan the nameserver gets set
  via DHCP but the search list is not picked up. This did work with
  ifupdown:

  ubuntu@bar-zesty6401:~$ cat /etc/network/interfaces
  ...
  # The primary network interface
  auto eth0
  iface eth0 inet dhcp

  ubuntu@bar-zesty6401:~$ cat /etc/resolv.conf
  ...
  nameserver 192.168.2.1
  nameserver 127.0.0.53
  search smbhome.net

  
  ubuntu@bar-artful6401:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  eth0:
dhcp4: yes

  ubuntu@bar-artful6401:~$ networkctl status eth0
  ● 2: eth0
 Link File: /lib/systemd/network/99-default.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
 State: routable (configured)
  Path: xen-vif-0
Driver: vif
HW Address: 00:16:3e:71:31:57 (Xensource, Inc.)
   Address: 192.168.2.159
fe80::216:3eff:fe71:3157
   Gateway: 192.168.2.1 (PC Engines GmbH)
   DNS: 192.168.2.1

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

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

[Touch-packages] [Bug 1703898] [NEW] systemd-journald crashed with SIGABRT in journal_file_append_object()

2017-07-12 Thread Loren Pearson

Public bug reported:

Ubuntu 17.04 Desktop
On boot, I receive an error.

Sorry Ubuntu 17.04 has experienced an internal error.
ExecutablePath
  /lib/systemd/systemd-hournald
Package
  systemd 232-21ubuntu5
ProblemType
  Crash
Title
  systemd-journald crashed with SIGABRT in journal_file_append_object()
ApportVersion
  2.20.4-Oubuntu4.4
Architecture
  amd64
CoreDump
  (binary data)

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


** Tags: journal systemd-boot

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Desktop
  On boot, I receive an error.

  Sorry Ubuntu 17.04 has experienced an internal error.
  ExecutablePath
/lib/systemd/systemd-hournald
  Package
systemd 232-21ubuntu5
  ProblemType
Crash
  Title
systemd-journald crashed with SIGABRT in journal_file_append_object()
  ApportVersion
2.20.4-Oubuntu4.4
  Architecture
amd64
  CoreDump
(binary data)

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

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

[Touch-packages] [Bug 1703882] [NEW] systemd-networkd does not pick up dns-search from DHCP

2017-07-12 Thread Stefan Bader

Public bug reported:

When using networkd as renderer for netplan the nameserver gets set via
DHCP but the search list is not picked up. This did work with ifupdown:

ubuntu@bar-zesty6401:~$ cat /etc/network/interfaces
...
# The primary network interface
auto eth0
iface eth0 inet dhcp

ubuntu@bar-zesty6401:~$ cat /etc/resolv.conf
...
nameserver 192.168.2.1
nameserver 127.0.0.53
search smbhome.net


ubuntu@bar-artful6401:~$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
eth0:
  dhcp4: yes

ubuntu@bar-artful6401:~$ networkctl status eth0
● 2: eth0
   Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-eth0.network
Type: ether
   State: routable (configured)
Path: xen-vif-0
  Driver: vif
  HW Address: 00:16:3e:71:31:57 (Xensource, Inc.)
 Address: 192.168.2.159
  fe80::216:3eff:fe71:3157
 Gateway: 192.168.2.1 (PC Engines GmbH)
 DNS: 192.168.2.1

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

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

Title:
  systemd-networkd does not pick up dns-search from DHCP

Status in systemd package in Ubuntu:
  New

Bug description:
  When using networkd as renderer for netplan the nameserver gets set
  via DHCP but the search list is not picked up. This did work with
  ifupdown:

  ubuntu@bar-zesty6401:~$ cat /etc/network/interfaces
  ...
  # The primary network interface
  auto eth0
  iface eth0 inet dhcp

  ubuntu@bar-zesty6401:~$ cat /etc/resolv.conf
  ...
  nameserver 192.168.2.1
  nameserver 127.0.0.53
  search smbhome.net

  
  ubuntu@bar-artful6401:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  eth0:
dhcp4: yes

  ubuntu@bar-artful6401:~$ networkctl status eth0
  ● 2: eth0
 Link File: /lib/systemd/network/99-default.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
 State: routable (configured)
  Path: xen-vif-0
Driver: vif
HW Address: 00:16:3e:71:31:57 (Xensource, Inc.)
   Address: 192.168.2.159
fe80::216:3eff:fe71:3157
   Gateway: 192.168.2.1 (PC Engines GmbH)
   DNS: 192.168.2.1

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

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

[Touch-packages] [Bug 1703866] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

** Tags removed: need-duplicate-check

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in openssl package in Ubuntu:
  New

Bug description:
  Was just trying to upgrade from 14.04 to 16.04 and the installer
  reported that issue and asked me to fill this...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Tue Jul 11 17:05:23 2017
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-09-06 (1404 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

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

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

[Touch-packages] [Bug 1703866] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2017-07-12 Thread Damien Levac

Public bug reported:

Was just trying to upgrade from 14.04 to 16.04 and the installer
reported that issue and asked me to fill this...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
Date: Tue Jul 11 17:05:23 2017
DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess 
installed post-installation script returned error exit status 255
ErrorMessage: subprocess installed post-installation script returned error exit 
status 255
InstallationDate: Installed on 2013-09-06 (1404 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in openssl package in Ubuntu:
  New

Bug description:
  Was just trying to upgrade from 14.04 to 16.04 and the installer
  reported that issue and asked me to fill this...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Tue Jul 11 17:05:23 2017
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-09-06 (1404 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago)

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

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

[Touch-packages] [Bug 1703326] Automatically added comment

Added to Trello: https://trello.com/c/fX8lP0VF/189-bug1703326-lock-
screen-wallpaper-is-a-plain-blue-screen

** Tags removed: desktop-trello-import

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

Title:
  Lock screen wallpaper is a plain blue screen

Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  The default lock screen wallpaper in Artful is currently a plain blue
  screen.

  This is probably because the default wallpaper file doesn't exist on
  Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg).

  This should be the default wallpaper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1703326/+subscriptions

-- 
Mailing list: https://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 1702601] Re: package winbind (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1

2017-07-12 Thread Vladislav

Yes, it worked! Very much I thank you! The problem is removed.

---
С уважением, Владислав Пономарев

12.07.2017 20:23, Andreas Hasenack пишет:
> Correct, these lines do influence operation. These are the so called LSB
> headers and they influence service startup and shutdown ordering.
>
> -- You received this bug notification because you are subscribed to 
> the bug report. https://bugs.launchpad.net/bugs/1702601 Title: package 
> winbind (not installed) failed to install/upgrade: подпроцесс 
> установлен сценарий post-removal возвратил код ошибки 1 Status in 
> apport package in Ubuntu: New Status in samba package in Ubuntu: 
> Incomplete Bug description: Ошибка произошла после обновления пакетов 
> Ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: 
> winbind (not installed) ProcVersionSignature: Ubuntu 
> 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic 
> x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: winbind: Purge 
> samba: Configure system-config-samba: Configure NULL: ConfigurePending 
> Architecture: amd64 BothFailedConnect: Yes Date: Thu Jul 6 11:05:35 
> 2017 ErrorMessage: подпроцесс установлен сценарий post-removal 
> возвратил код ошибки 1 InstallationDate: Installed on 2017-05-12 (54 
> days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - 
> Release amd64 (20170215.2) NmbdLog: RelatedPackageVersions: dpkg 
> 1.18.4ubuntu1.2 apt 1.2.20 SambaServerRegression: Yes SmbConfIncluded: 
> Yes SmbLog: SourcePackage: samba Title: package winbind (not 
> installed) failed to install/upgrade: подпроцесс установлен сценарий 
> post-removal возвратил код ошибки 1 UpgradeStatus: No upgrade log 
> present (probably fresh install) To manage notifications about this 
> bug go to: 
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1702601/+subscriptions 
>

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

Title:
  package winbind (not installed) failed to install/upgrade: подпроцесс
  установлен сценарий post-removal возвратил код ошибки 1

Status in apport package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  Ошибка произошла после обновления пакетов Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: winbind (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   winbind: Purge
   samba: Configure
   system-config-samba: Configure
   NULL: ConfigurePending
  Architecture: amd64
  BothFailedConnect: Yes
  Date: Thu Jul  6 11:05:35 2017
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-05-12 (54 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  NmbdLog:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package winbind (not installed) failed to install/upgrade: подпроцесс 
установлен сценарий post-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703520] Re: DNS resolving doesn't work in complain mode with dnsmasq and apparmor

2017-07-12 Thread John Johansen

@Bjoern can you set a couple of apparmor flags and report back what is
reported in the logs?

Specifically as root can you do

echo -n "noquiet" > /sys/module/apparmor/parameters/audit
echo 1 >  /sys/module/apparmor/parameters/debug
echo 0 > /proc/sys/kernel/printk_ratelimit

and then restart dnsmasq

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

Title:
  DNS resolving doesn't work in complain mode with dnsmasq and apparmor

Status in apparmor package in Ubuntu:
  New

Bug description:
  After i have firefox, chromium-browser and dnsmasq profiled with sudo
  aa-autodep (complain-mode was used), i can not resolving websites.
  (Log is at the attachement)

  I have copied the profiles of the three programms from the top in 
/etc/apparmor.d/disable and after a reboot i can resolving websites.
  The network manager can connect with my router the whole time.

  I'm have Ubuntu 16.04.02 LTS with all updates. (11.07.2017 CEST)

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

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

[Touch-packages] [Bug 1703326] Re: Lock screen wallpaper is a plain blue screen

2017-07-12 Thread Didier Roche

** Tags added: desktop-trello-import

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

Title:
  Lock screen wallpaper is a plain blue screen

Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  The default lock screen wallpaper in Artful is currently a plain blue
  screen.

  This is probably because the default wallpaper file doesn't exist on
  Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg).

  This should be the default wallpaper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1703326/+subscriptions

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

[Touch-packages] [Bug 1594611] Re: /usr/bin/mate-panel:11:XGetWindowProperty:xembed_get_info:_gtk_socket_windowing_embed_get_info:_gtk_socket_add_window:on_proxy_appeared

** Package changed: mate-panel (Ubuntu) => gtk+2.0 (Ubuntu)

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

Title:
  /usr/bin/mate-
  
panel:11:XGetWindowProperty:xembed_get_info:_gtk_socket_windowing_embed_get_info:_gtk_socket_add_window:on_proxy_appeared

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.12.2-1, the problem page at
  https://errors.ubuntu.com/problem/f8d023bb182aea9e92cdcb85078392a5c4a51a52
  contains more details.

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

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

[Touch-packages] [Bug 1635802] Re: GStreamer: mp3s did not work in Yakkety Yak

2017-07-12 Thread Bug Watch Updater

** Changed in: gstreamer1.0
   Status: Confirmed => Expired

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

Title:
  GStreamer: mp3s did not work in Yakkety Yak

Status in Gstreamer1.0:
  Expired
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  gstreamer: mp3s did not work in Yakkety Yak. It has worked in before
  (i.e. in Xenial Xerus), hence it is a regression.

  To reproduct (old):

  * Add a podcast URL of your choice to rhythmbox (try 
http://www.deutschlandfunk.de/podcast-nachrichten.1257.de.podcast.xml if unsure)
  * Use the update button
  * Click on the episode, download it (right mouse button - context menu)
  * Try to hear (by double click or by adding it to the playback list)
  * The error occurs:
    * Expected behaviour: The podcast is played.
    * Current behaviour: Nothing happens. Rhythmbox is unable to play the 
podcast.

  To reproduce (new):

  * Use gst-play-1.0 and try to play an mp3 file. Compare with playing
  an flac file. Also see attachments.

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

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

[Touch-packages] [Bug 1594611] [NEW] /usr/bin/mate-panel:11:XGetWindowProperty:xembed_get_info:_gtk_socket_windowing_embed_get_info:_gtk_socket_add_window:on_proxy_appeared

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding mate-panel.  This problem was most recently seen with version
1.12.2-1, the problem page at
https://errors.ubuntu.com/problem/f8d023bb182aea9e92cdcb85078392a5c4a51a52
contains more details.

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


** Tags: xenial
-- 
/usr/bin/mate-panel:11:XGetWindowProperty:xembed_get_info:_gtk_socket_windowing_embed_get_info:_gtk_socket_add_window:on_proxy_appeared
https://bugs.launchpad.net/bugs/1594611
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+2.0 in Ubuntu.

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

[Touch-packages] [Bug 1636901] Re: Seamless mouse integration does not work with Mir in a VM

2017-07-12 Thread Bryan Quigley

I'm guessing this won't be fixed, but if someone does want to work on it
feel free to reopen.

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

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

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

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

Title:
  Seamless mouse integration does not work with Mir in a VM

Status in Mir:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Mouse integration is off using virt-manager/viewer/QVC/Spice with
  Unity8/mir as the guest.

  Steps to reproduce;
  1. Install in a virt-manager VM with QVC and Spice enabled.
  2. Login to Unity7, notice how mouse flows seamlessly between Host and Guest 
machine.
  3. Login to Unity8. Note how you can't bring the mouse to the top of the 
screen (or the far left usually).  Specifically it goes back to the host too 
quickly.

  The box that you can move in does change a bit (AFAICT).  Try
  fullscreen to see.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  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
  Date: Wed Oct 26 11:32:57 2016
  InstallationDate: Installed on 2016-08-23 (64 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160823)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1629137] Re: /usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:GI_libc_malloc:read_packet:_xcb_in_read

** Package changed: mate-settings-daemon (Ubuntu) => libxcb (Ubuntu)

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

Title:
  /usr/bin/mate-settings-
  
daemon:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read

Status in libxcb package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-settings-daemon.  This problem was most recently seen
  with version 1.12.1-2build1, the problem page at
  https://errors.ubuntu.com/problem/b93e825cd3349b4e29bf3760e512f60febd8c38b
  contains more details.

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

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

[Touch-packages] [Bug 1673286] Re: /usr/bin/mate-volume-control-applet:11:malloc_consolidate:_int_malloc:GI_libc_malloc:read_packet:_xcb_in_read

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

** This bug has been marked a duplicate of bug 1629137
   
/usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read

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

Title:
  /usr/bin/mate-volume-control-
  
applet:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read

Status in libxcb package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-media.  This problem was most recently seen with package version 1.12.1-1, 
the problem page at 
https://errors.ubuntu.com/problem/31206cc9f08f903a2d53a96328a56c00a5561c3a 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1681518] Re: /usr/bin/xfce4-panel:11:_int_malloc:GI_libc_malloc:read_packet:_xcb_in_read:_xcb_conn_wait

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

** Package changed: xfce4-panel (Ubuntu) => libxcb (Ubuntu)

** This bug has been marked a duplicate of bug 1598259
   
/usr/bin/marco:11:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read:_xcb_conn_wait

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

Title:
  
/usr/bin/xfce4-panel:11:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read:_xcb_conn_wait

Status in libxcb package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xfce4-panel.  This problem was most recently seen with package version 
4.12.0-4ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ebc9f6eecfa610db8bb88caa57bfb01159625668 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1629137] [NEW] /usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:GI_libc_malloc:read_packet:_xcb_in_read

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding mate-settings-daemon.  This problem was most recently seen
with version 1.12.1-2build1, the problem page at
https://errors.ubuntu.com/problem/b93e825cd3349b4e29bf3760e512f60febd8c38b
contains more details.

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


** Tags: xenial
-- 
/usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read
https://bugs.launchpad.net/bugs/1629137
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libxcb in Ubuntu.

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

[Touch-packages] [Bug 1681518] [NEW] /usr/bin/xfce4-panel:11:_int_malloc:GI_libc_malloc:read_packet:_xcb_in_read:_xcb_conn_wait

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xfce4-panel.  This problem was most recently seen with package version 
4.12.0-4ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ebc9f6eecfa610db8bb88caa57bfb01159625668 
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 you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: precise raring saucy trusty utopic vivid xenial yakkety
-- 
/usr/bin/xfce4-panel:11:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read:_xcb_conn_wait
https://bugs.launchpad.net/bugs/1681518
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libxcb in Ubuntu.

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

[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

2017-07-12 Thread Dimitri John Ledkov

Adjusted hard and soft nofile limits on the host to 10, launched
container and observed lower nofile limits in prlimit. Upgraded systemd
in the container from 229-4ubuntu17 to 229-4ubuntu18. Rebooted the
container and observed much higher nofile limits.

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

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

Title:
  systemd does not respect nofile ulimit when running in container

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets
  an arbitrary cap.

  [Test Case]

   * Start container with high RLIMIT_NOFILE (e.g. 100 000)
   * Check that RLIMIT_NOFILE on the container is more than 65536

  [Regression Potential]

   * This is a feature / change of behaviour. Some users may be relying
  on the lower RLIMIT_NOFILE cap, but it should not have a negative
  impact on the host (as in creating too many file descriptors/denial of
  service).

  [Original Bug Report]

  When systemd currently starts in a container that has RLIMIT_NOFILE set to 
e.g.
  10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
  I've pushed a patch to systemd upstream that will try to set
  the nofile limit to the allowed kernel maximum. If this fails, it will compute
  the minimum of the current set value (the limit that is set on the container)
  and the maximum value as soft limit and the currently set maximum value as the
  maximum value. This way it retains the limit set on the container.
  It would be great if we could backport this patch to have system adhere to
  nofile limits set for the container. This is especially important since user
  namespaces will allow you to lower the limit but not raise it back up 
afterwards.
  The upstream patch is appended.

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

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

[Touch-packages] [Bug 1703840] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Just said I needed to report a bug on reboot. I had just tried to run
  Synaptic to install Skype and it said that it coulldn't run because
  apt-get or apt something was already running. Of course no button to
  end the conflicting process, no help to find it, etc. Not a very
  helpful system.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jul 12 09:37:20 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-22 (19 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703840] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-07-12 Thread Wes Kussmaul

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

Public bug reported:

Just said I needed to report a bug on reboot. I had just tried to run
Synaptic to install Skype and it said that it coulldn't run because apt-
get or apt something was already running. Of course no button to end the
conflicting process, no help to find it, etc. Not a very helpful system.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
AptOrdering:
 gconf2-common:amd64: Install
 libgconf-2-4:amd64: Install
 gconf-service-backend:amd64: Install
 gconf-service:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Jul 12 09:37:20 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-22 (19 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Just said I needed to report a bug on reboot. I had just tried to run
  Synaptic to install Skype and it said that it coulldn't run because
  apt-get or apt something was already running. Of course no button to
  end the conflicting process, no help to find it, etc. Not a very
  helpful system.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jul 12 09:37:20 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-22 (19 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1703838] [NEW] Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try

2017-07-12 Thread fargoth

Public bug reported:

Using Ubuntu 17.04 (64 bit)
Package version 1.4.4-1ubuntu3.1


This happened to me 3 times today:

The connection drops and is not automatically restored, even though the
network is visible in the nm-applet.

Manually clicking on the network to connect, results in an animation of
the nm-applet showing it's trying, but it gives up after a while and
changes the icon to up\down arrows instead of the wifi sign.

Clicking on it again, and selecting my network again, results in an
almost instant reconnection, which implies that the computer should have
known to do it automatically instead of requiring me to tell it to
connect again (let alone twice).

Here is the journal from a system startup:

https://pastebin.com/hGrFEWiU

And here is the journal from one such unsuccessful reconnect.
I've added (*** comments ***) to mark where I've manually tried to reconnect 
(twice, second time successfully):

https://pastebin.com/TAyt6McQ

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

Title:
  Failure to automatically reconnect after drop - requiring manual
  reconnect, only successful after second try

Status in network-manager package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04 (64 bit)
  Package version 1.4.4-1ubuntu3.1


  This happened to me 3 times today:

  The connection drops and is not automatically restored, even though
  the network is visible in the nm-applet.

  Manually clicking on the network to connect, results in an animation
  of the nm-applet showing it's trying, but it gives up after a while
  and changes the icon to up\down arrows instead of the wifi sign.

  Clicking on it again, and selecting my network again, results in an
  almost instant reconnection, which implies that the computer should
  have known to do it automatically instead of requiring me to tell it
  to connect again (let alone twice).

  Here is the journal from a system startup:

  https://pastebin.com/hGrFEWiU

  And here is the journal from one such unsuccessful reconnect.
  I've added (*** comments ***) to mark where I've manually tried to reconnect 
(twice, second time successfully):

  https://pastebin.com/TAyt6McQ

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

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

[Touch-packages] [Bug 1693850] Please test proposed package

2017-07-12 Thread Robie Basak

Hello Chow, or anyone else affected,

Accepted libzen into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libzen/0.4.34-1ubuntu0.17.04.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

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

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

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Fix Committed
Status in libzen source package in Yakkety:
  Fix Committed
Status in libzen source package in Zesty:
  Fix Committed
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1693850] Please test proposed package

2017-07-12 Thread Robie Basak

Hello Chow, or anyone else affected,

Accepted libzen into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libzen/0.4.33-3ubuntu0.16.10.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-yakkety to verification-done-yakkety. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-yakkety. In either case, details of your
testing will help us make a better decision.

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

** Changed in: libzen (Ubuntu Zesty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-zesty

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

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Fix Committed
Status in libzen source package in Yakkety:
  Fix Committed
Status in libzen source package in Zesty:
  Fix Committed
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

2017-07-12 Thread Robie Basak

Hello Chow, or anyone else affected,

Accepted libzen into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libzen/0.4.32-1ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: libzen (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

** Changed in: libzen (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-yakkety

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

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Fix Committed
Status in libzen source package in Yakkety:
  Fix Committed
Status in libzen source package in Zesty:
  Fix Committed
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1702601] Re: package winbind (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1