[Touch-packages] [Bug 1650719] [NEW] I can not install any program

[Filippo Maggio]

Public bug reported:

I can't install a new program from the ubuntu software

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
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: Sat Dec 17 08:38:41 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3905]
InstallationDate: Installed on 2016-02-26 (294 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 80G0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed 
root=UUID=888b3a56-9c68-4590-ac7e-e48432faabb5 ro quiet nopat drm.debug=0xe 
splash plymouth:debug vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: A7CN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lancer 5A6
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-30
dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
dmi.product.name: 80G0
dmi.product.version: Lenovo G50-30
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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: Sat Dec 17 07:49:15 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1565 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 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/1650719

Title:
  I can not install any program

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't install a new program from the ubuntu software

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Sat Dec 17 08:38:41 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3905]
  InstallationDate: Installed on 2016-02-26 (294 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80G0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed 
root=UUID=888b3a56-9c68-4590-ac7e-e48432faabb5 ro quiet nopat drm.debug=0xe 
splash plymouth:debug vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 

[Touch-packages] [Bug 1650718] [NEW] I can not install any program

[Filippo Maggio]

Public bug reported:

I can't install a new program from the ubuntu software

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
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: Sat Dec 17 08:38:41 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3905]
InstallationDate: Installed on 2016-02-26 (294 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 80G0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed 
root=UUID=888b3a56-9c68-4590-ac7e-e48432faabb5 ro quiet nopat drm.debug=0xe 
splash plymouth:debug vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: A7CN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lancer 5A6
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-30
dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
dmi.product.name: 80G0
dmi.product.version: Lenovo G50-30
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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: Sat Dec 17 07:49:15 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1565 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 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/1650718

Title:
  I can not install any program

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't install a new program from the ubuntu software

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Sat Dec 17 08:38:41 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3905]
  InstallationDate: Installed on 2016-02-26 (294 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80G0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed 
root=UUID=888b3a56-9c68-4590-ac7e-e48432faabb5 ro quiet nopat drm.debug=0xe 
splash plymouth:debug vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 

[Touch-packages] [Bug 1561467] Re: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'

[Behzad Khandzad]

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

I have same bug during upgrade from ubuntu 15.10 to 16.4

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

Title:
  /var/lib/dpkg/info/udev.prerm called with unknown argument
  'deconfigure'

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Wily:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  Notification during upgrade:

  The upgrade will continue but the
  '/var/cache/apt/archives/systemd_229-3ubuntu1_amd64.deb' package may
  not be in a working state. Please consider submitting a bug report
  about it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 225-1ubuntu9.1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Mar 24 11:56:03 2016
  DuplicateSignature: package:systemd:225-1ubuntu9.1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess 
installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2015-01-24 (424 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: MEDION H81H3-EM2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=5875860d-f233-4082-93b8-7ee2fcdbacc4 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.7
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu9.1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 2
  UpgradeStatus: Upgraded to xenial on 2016-03-24 (0 days ago)
  dmi.bios.date: 06/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H81EM2W08.304
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81H3-EM2
  dmi.board.vendor: MEDION
  dmi.board.version: H81EM2W08.304
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH81EM2W08.304:bd06/30/2014:svnMEDION:pnH81H3-EM2:pvrH81EM2W08.304:rvnMEDION:rnH81H3-EM2:rvrH81EM2W08.304:cvnMEDION:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H81H3-EM2
  dmi.product.version: H81EM2W08.304
  dmi.sys.vendor: MEDION

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

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

[Touch-packages] [Bug 1650707] [NEW] mplayer segfaults in ff_draw_horiz_band

[Matt Mullins]

Public bug reported:

After the 6:9.20-0ubuntu0.14.04.1 security update, playing an XVID
stream in an AVI container segfaults decoding video frames.  Reverting
to 6:9.11-2ubuntu2 works -- I can't find a .deb for the previous 9.18
release, but this system was playing videos without issue until
recently.

In GDB:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

libavformat version 54.20.4 (external)
Mismatching header version 54.20.3
AVI file format detected.
[aviheader] Video stream found, -vid 0
[aviheader] Audio stream found, -aid 1
VIDEO:  [XVID]  624x352  12bpp  23.976 fps  989.1 kbps (120.7 kbyte/s)
Clip info:
 Software: VirtualDubMod 1.5.10.2 (build 2540/release)
Load subtitles in ./
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: 
No such file or directory
[vdpau] Error when calling vdp_device_create_x11: 1
==
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 54.35.1 (external)
Mismatching header version 54.35.0
Unsupported AVPixelFormat 53
Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
==
==
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 2 ch, floatle, 134.6 kbit/4.38% (ratio: 16819->384000)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==
[New Thread 0x7fffe363c700 (LWP 20856)]
AO: [pulse] 48000Hz 2ch floatle (4 bytes per sample)
Starting playback...
Movie-Aspect is 1.77:1 - prescaling to correct movie aspect.
VO: [xv] 624x352 => 624x352 Planar YV12 

Program received signal SIGSEGV, Segmentation fault.
0x0056edf7 in fast_memcpy ()
(gdb) bt
#0  0x0056edf7 in fast_memcpy ()
#1  0x00498119 in ?? ()
#2  0x00571c7c in ?? ()
#3  0x73ca0a83 in ff_draw_horiz_band (avctx=0xbc68c0, 
dsp=dsp@entry=0xbc8428, cur=cur@entry=0xbc7e50, last=last@entry=0xbc70d0, y=0, 
h=, picture_structure=3, first_field=0, draw_edges=1, 
low_delay=0, 
v_edge_pos=352, h_edge_pos=624) at 
/build/libav-dVKvK5/libav-9.20/libavcodec/mpegvideo.c:2529
#4  0x73ca0d22 in ff_mpeg_draw_horiz_band (s=s@entry=0xbc6ce0, 
y=, h=h@entry=16) at 
/build/libav-dVKvK5/libav-9.20/libavcodec/mpegvideo.c:2537
#5  0x73b89f86 in decode_slice (s=s@entry=0xbc6ce0) at 
/build/libav-dVKvK5/libav-9.20/libavcodec/h263dec.c:259
#6  0x73b8ab78 in ff_h263_decode_frame (avctx=0xbc68c0, data=0xbc66e0, 
got_frame=0x7fffd024, avpkt=) at 
/build/libav-dVKvK5/libav-9.20/libavcodec/h263dec.c:651
#7  0x73d47433 in avcodec_decode_video2 (avctx=0xbc68c0, 
picture=0xbc66e0, got_picture_ptr=0x7fffd024, avpkt=0x7fffd030) at 
/build/libav-dVKvK5/libav-9.20/libavcodec/utils.c:1288
#8  0x00572342 in ?? ()
#9  0x004c35a1 in decode_video ()
#10 0x0043f4a4 in ?? ()
#11 0x004337d6 in main ()

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

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

Title:
  mplayer segfaults in ff_draw_horiz_band

Status in libav package in Ubuntu:
  New

Bug description:
  After the 6:9.20-0ubuntu0.14.04.1 security update, playing an XVID
  stream in an AVI container segfaults decoding video frames.  Reverting
  to 6:9.11-2ubuntu2 works -- I can't find a .deb for the previous 9.18
  release, but this system was playing videos without issue until
  recently.

  In GDB:
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team
  mplayer: could not connect to socket
  mplayer: No such file or directory
  Failed to open LIRC support. You will not be able to use your remote control.

  libavformat version 54.20.4 (external)
  Mismatching header version 54.20.3
  AVI file format detected.
  [aviheader] Video stream found, -vid 0
  [aviheader] Audio stream found, -aid 1
  VIDEO:  [XVID]  624x352  12bpp  23.976 fps  989.1 kbps (120.7 kbyte/s)
  Clip info:
   Software: VirtualDubMod 1.5.10.2 (build 2540/release)
  Load subtitles in ./
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  [vdpau] Error when calling vdp_device_create_x11: 1
  

[Touch-packages] [Bug 28487] Re: ssh should not try to verify hostkey when only gssapi is used

[Quomoow]

seems to be fixed (dead)

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

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

Title:
  ssh should not try to verify hostkey when only gssapi is used

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  If I only have gssapi-keyx and gssapi-with-mic enabled (everything
  else is disabled) and I am missing a valid kerberos ticket, openssh
  asks me if i want to accept the hostkey (unless I already have
  accepted it). If I have a valid ticket I am not asked to verify the
  hostkey. When using gssapi/kerberos the hostkeys are pretty useless as
  the the validity of the host are verified through kerberos/gssapi.

  /torkel

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

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

[Touch-packages] [Bug 40017] Re: libapt progress reporting on remove/purge needs improvment

[Quomoow]

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

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

Title:
  libapt progress reporting on remove/purge needs improvment

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The current progress reporting on purge/remove write the status after
  the action had happend. This results in bad looking guis.

  Attached is a log from purging language-pack-bn-base as a example for
  such a action. Note that no feedback is send to the parent application
  over the status-fd until "generating locales..." has finished (and
  that can take a long time).

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

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

[Touch-packages] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid

[Quomoow]

** Changed in: xorg (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xorg

  /etc/init.d/x11-common in package x11-common, version 1:7.5+5ubuntu1
  from 10.04 includes

  $ awk 'BEGIN {RS = ""; ORS = "\n\n"} /chmod/' /etc/init.d/x11-common
  set_up_socket_dir () {
if [ "$VERBOSE" != no ]; then
  log_begin_msg "Setting up X server socket directory $SOCKET_DIR..."
fi
if [ -e $SOCKET_DIR ] && [ ! -d $SOCKET_DIR ]; then
  mv $SOCKET_DIR $SOCKET_DIR.$$
fi
mkdir -p $SOCKET_DIR
chown root:root $SOCKET_DIR
chmod 1777 $SOCKET_DIR
do_restorecon $SOCKET_DIR
[ "$VERBOSE" != no ] && log_end_msg 0 || return 0
  }

  set_up_ice_dir () {
if [ "$VERBOSE" != no ]; then
  log_begin_msg "Setting up ICE socket directory $ICE_DIR..."
fi
if [ -e $ICE_DIR ] && [ ! -d $ICE_DIR ]; then
  mv $ICE_DIR $ICE_DIR.$$
fi
mkdir -p $ICE_DIR
chown root:root $ICE_DIR
chmod 1777 $ICE_DIR
do_restorecon $ICE_DIR
[ "$VERBOSE" != no ] && log_end_msg 0 || return 0
  }
  $

  Both functions allow for the directory, /tmp/.X11-unix or
  /tmp/.ICE-unix, to already exist.  They then attempt to ensure it has
  the correct owner, group, and permissions.  But the

  chmod 1777 ...

  fails to do this.  chmod(1) says

  chmod preserves a directory's set-user-ID and set-group-ID bits
  unless you explicitly specify otherwise.  You can set or clear the
  bits with symbolic modes like u+s and g-s, and you can set (but not
  clear) the bits with a numeric mode.

  This is allowed by chmod(1posix).

  For an octal integer mode operand, the file mode bits shall be set
  absolutely.  [Sounds good so far.]

  For each bit set in the octal number, the corresponding file
  permission bit [meaning rwx] shown in the following table shall be
  set;  all other file permission bits shall be cleared.  For regular
  files, for each bit set in the octal number corresponding to the
  set-user-ID-on-execution or the set-group-ID-on-execution, bits
  shown in the following table shall be set; if these bits are not set
  in the octal number, they are cleared.  [Good.]  For other file
  types [e.g. directories], it is implementation-defined whether or
  not requests to set or clear the set-user-ID-on-execution or
  set-group-ID-on-execution bits are honored.

  IOW, the numeric mode 1777 will *never* clear the setuid and setgid
  bits.  A symbolic mode must be used to do this.

  $ mkdir foo
  $ l -d foo
  drwxr-xr-x 2 ralph ralph 4096 2010-08-24 11:07 foo
  $ chmod 1777 foo
  $ l -d foo
  drwxrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo

  Correct.  x11-common's chmod works in this case.

  $ chmod u+s foo
  $ l -d foo
  drwsrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
  $ chmod 1777 foo
  $ l -d foo
  drwsrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo

  Wrong.  It fails to clear setuid.

  $ chmod u-s,g+s foo
  $ l -d foo
  drwxrwsrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
  $ chmod 1777 foo
  $ l -d foo
  drwxrwsrwt 2 ralph ralph 4096 2010-08-24 11:07 foo

  Wrong.  Nor does it clear setgid.

  $ chmod a-s=rwxt foo
  $ l -d foo
  drwxrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
  $ 

  The symbolic `a-s=rwxt' should be used for both of x11-common's chmods
  in order to have the desired effect.

  Because of the incorrect 1777, users are seeing errors from xorg's
  xserver-wrapper.c,

  X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a
  directory, aborting.

  see bug #622179.  Perhaps this is being caused by the parent directory,
  /tmp, being setgid and this is inherited by the mkdir(1), see mkdir(2),
  and not cleared by the chmod.

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

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

[Touch-packages] [Bug 907312] Re: Add .xsessionrc file to /etc/skel

[Quomoow]

** Changed in: xorg (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Add .xsessionrc file to /etc/skel

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  A simple .xsessionrc placeholder ought to be added t o /etc/skel when
  X is installed.  It could be something approximately like this:


  # ~/.xsessionrc: sourced ?? by Xsession(5) ??, not executed
  # By default this file does nothing.

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

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

[Touch-packages] [Bug 1650701] Re: bug

[Quomoow]

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

** This bug has been marked a duplicate of bug 1650702
   bug

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

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  this bug will be

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Sat Dec 17 10:23:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 6470M [1043:1cb2]
  InstallationDate: Installed on 2016-08-11 (127 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer Inc. K42JZ
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=3bce069b-6e26-43ce-865e-75e6d8b3ea78 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K42JZ
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr209:bd12/29/2010:svnASUSTeKComputerInc.:pnK42JZ:pvr1.0:rvnASUSTeKComputerInc.:rnK42JZ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K42JZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Dec 17 08:43:48 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-0
LVDS   VGA-0
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1650702] [NEW] bug

[XiaoJuntao]

Public bug reported:

this bug will be

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
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: Sat Dec 17 10:23:42 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Radeon HD 6470M [1043:1cb2]
InstallationDate: Installed on 2016-08-11 (127 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK Computer Inc. K42JZ
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=3bce069b-6e26-43ce-865e-75e6d8b3ea78 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K42JZ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr209:bd12/29/2010:svnASUSTeKComputerInc.:pnK42JZ:pvr1.0:rvnASUSTeKComputerInc.:rnK42JZ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K42JZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Dec 17 08:43:48 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output  HDMI-0LVDS 
  VGA-0
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 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/1650702

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  this bug will be

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Sat Dec 17 10:23:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 6470M [1043:1cb2]
  InstallationDate: Installed on 2016-08-11 (127 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer Inc. K42JZ
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=3bce069b-6e26-43ce-865e-75e6d8b3ea78 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K42JZ
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 1650701] [NEW] bug

[XiaoJuntao]

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

Public bug reported:

this bug will be

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
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: Sat Dec 17 10:23:42 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Radeon HD 6470M [1043:1cb2]
InstallationDate: Installed on 2016-08-11 (127 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK Computer Inc. K42JZ
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=3bce069b-6e26-43ce-865e-75e6d8b3ea78 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K42JZ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr209:bd12/29/2010:svnASUSTeKComputerInc.:pnK42JZ:pvr1.0:rvnASUSTeKComputerInc.:rnK42JZ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K42JZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Dec 17 08:43:48 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output  HDMI-0LVDS 
  VGA-0
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 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/1650701

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  this bug will be

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Sat Dec 17 10:23:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 6470M [1043:1cb2]
  InstallationDate: Installed on 2016-08-11 (127 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer Inc. K42JZ
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=3bce069b-6e26-43ce-865e-75e6d8b3ea78 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K42JZ
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK 

[Touch-packages] [Bug 1650695] [NEW] Firefox

[Doug]

Public bug reported:

Firefox constantly reports error on opening

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic i686
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Dec 17 00:59:20 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Technology Solutions Mobile GM965/GL960 Integrated 
Graphics Controller (primary) [1734:1108]
   Subsystem: Fujitsu Technology Solutions Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) [1734:1108]
InstallationDate: Installed on 2016-11-17 (29 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release i386 (20161012.1)
MachineType: FUJITSU SIEMENS AMILO Pi 2515
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=bf39455e-cded-4388-8187-df770499a6ad ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.05C
dmi.board.name: F43
dmi.board.vendor: FUJITSU SIEMENS
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.05C:bd10/01/2007:svnFUJITSUSIEMENS:pnAMILOPi2515:pvr20:rvnFUJITSUSIEMENS:rnF43:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
dmi.product.name: AMILO Pi 2515
dmi.product.version: 20
dmi.sys.vendor: FUJITSU SIEMENS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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


** Tags: apport-bug i386 ubuntu yakkety

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

Title:
  Firefox

Status in xorg package in Ubuntu:
  New

Bug description:
  Firefox constantly reports error on opening

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Dec 17 00:59:20 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions Mobile GM965/GL960 Integrated 
Graphics Controller (primary) [1734:1108]
 Subsystem: Fujitsu Technology Solutions Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) [1734:1108]
  InstallationDate: Installed on 2016-11-17 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  MachineType: FUJITSU SIEMENS AMILO Pi 2515
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=bf39455e-cded-4388-8187-df770499a6ad ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.05C
  dmi.board.name: F43
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.05C:bd10/01/2007:svnFUJITSUSIEMENS:pnAMILOPi2515:pvr20:rvnFUJITSUSIEMENS:rnF43:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
  dmi.product.name: AMILO Pi 2515
  dmi.product.version: 20
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 

[Touch-packages] [Bug 1648901] Re: SPNEGO crash on mechanism failure

[Eric Desrochers]

Hi andrew, dwmw2 et al,

If I build a test package on Monday, will you be amenable to
install/test it and then provide feedbacks before I start the SRU ?

Addtionnaly, can you provide the detailed steps on how to reproduce the
problem ?

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

Title:
  SPNEGO crash on mechanism failure

Status in krb5 package in Ubuntu:
  In Progress

Bug description:
  Chrome (and other things) crash when Kerberos fails to authenticate:
  https://bugs.chromium.org/p/chromium/issues/detail?id=554905

  This was fixed in MIT krb5 in January:
  https://github.com/krb5/krb5/pull/385

  Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffdd687700 (LWP 14851)]
  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  2315  ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
  (gdb) bt
  #0  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  #1  0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788, 
  targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730, 
  opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

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

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

[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

[Nish Aravamudan]

Fixed in Debian with 2.1.26.dfsg1-8, per the other bug.

@duke-l, can you confirm this still occurs with Xenial? Given that
Xenial shipped with 2.1.26.dfsg1-14build1, which should have the
corresponding fix.

@hackel, it seems like you are possibly not using entirely Ubuntu
packages (given no php7.0 in 14.04), so it's not entirely clear if your
use-case is justification for the 14.04 backport, but I'll open tasks to
consider it at least, given the underlying issue is in the Ubuntu
package.

** Also affects: cyrus-sasl2 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cyrus-sasl2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cyrus-sasl2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: cyrus-sasl2 (Ubuntu Yakkety)
   Status: New => Fix Released

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

** Changed in: cyrus-sasl2 (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: cyrus-sasl2 (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: cyrus-sasl2 (Ubuntu Xenial)
   Importance: Undecided => Low

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Trusty:
  Triaged
Status in cyrus-sasl2 source package in Xenial:
  Incomplete
Status in cyrus-sasl2 source package in Yakkety:
  Fix Released
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

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

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

[Touch-packages] [Bug 1645002] Re: ssh sessions are not cleanly terminated on shutdown/restart with systemd

[Bug Watch Updater]

** Changed in: openssh (Debian)
   Status: Unknown => Fix Released

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

Title:
  ssh sessions are not cleanly terminated on shutdown/restart with
  systemd

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Triaged
Status in openssh source package in Yakkety:
  Fix Released
Status in openssh package in Debian:
  Fix Released

Bug description:
  In Ubuntu 16.04, a "reboot" command does not terminate the ssh
  session. This results in clients hanging, until timing out (sometimes
  as much as 120 seconds).

  This also introduces bugs to all  orchestration / automation tools which work 
over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 
hosts. For example, have a look at this issue for Fabric:
  https://github.com/fabric/fabric/issues/1488

  The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6. 
  There is a very detailed discussion in their bug tracker:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636

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

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

[Touch-packages] [Bug 1611363] Re: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

[David Barnett]

Where can I see the fix? What package was it in?

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

Title:
  vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

Status in vim:
  Fix Released
Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Xenial:
  Confirmed

Bug description:
  Hi, vim-gtk3 crashes so often on my system that it's borderline unusable.
  My system is a clean install of Ubuntu 16.04. I also (temporarily) renamed my 
customized ~/.vimrc and ~/.vim. My system is up-to-date as of today 
(2016-08-09); installed vim-gtk3 is 2:7.4.1689-3ubuntu1.1.

  The crash happens only (but very frequently, not always) when I launch
  gvim, either by calling it from a shell or by double-clicking a file
  in Nautilus. Note that the crash is independent of whether I'm opening
  a file or not. (At least I tried both variations from the terminal.)

  There's also a report on vim's bugtracker, but since unity appears in
  the backtrace, the consensus is that it's probably Ubuntu-specific.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: vim-gtk3 2:7.4.1689-3ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  9 14:34:31 2016
  ExecutablePath: /usr/bin/vim.gtk3
  InstallationDate: Installed on 2016-07-10 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: gvim -f 
/home/username/Documents/schoul/2016/1G-TODO/01-systemes-equations-TODO/chap01_systemes-equations-NOTES.tex
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: vim.gtk3 crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1645002] Re: ssh sessions are not cleanly terminated on shutdown/restart with systemd

[Nish Aravamudan]

As noted, this was fixed in Debian in 1:7.2p2-6. Both 16.10 and 17.04
have later versions, so this just needs an SRU to 16.04.

** Bug watch added: Debian Bug tracker #751636
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636

** Also affects: openssh (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636
   Importance: Unknown
   Status: Unknown

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

** Also affects: openssh (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: openssh (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: openssh (Ubuntu)
   Status: New => Fix Released

** Changed in: openssh (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  ssh sessions are not cleanly terminated on shutdown/restart with
  systemd

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Triaged
Status in openssh source package in Yakkety:
  Fix Released
Status in openssh package in Debian:
  Unknown

Bug description:
  In Ubuntu 16.04, a "reboot" command does not terminate the ssh
  session. This results in clients hanging, until timing out (sometimes
  as much as 120 seconds).

  This also introduces bugs to all  orchestration / automation tools which work 
over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 
hosts. For example, have a look at this issue for Fabric:
  https://github.com/fabric/fabric/issues/1488

  The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6. 
  There is a very detailed discussion in their bug tracker:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636

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

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

[Touch-packages] [Bug 1436558] Re: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of pa

[Nish Aravamudan]

If we were to merge to the latest release in Debian (2.4.44+dfsg-2),
zesty will get the Debian fix for this issue. We could then consider
backporting the fix from Helmut Grohne.

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

Title:
  package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade:
  trying to overwrite shared '/etc/ldap/ldap.conf', which is different
  from other instances of package libldap-2.4-2:amd64

Status in openldap package in Ubuntu:
  Triaged
Status in openldap package in Debian:
  Fix Released

Bug description:
  package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade:
  Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben,
  welches verschieden von anderen Instanzen des Paketes
  libldap-2.4-2:amd64 ist

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libldap-2.4-2 2.4.31-1+nmu2ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Wed Mar 25 16:48:52 2015
  DuplicateSignature: package:libldap-2.4-2:2.4.31-1+nmu2ubuntu8:Versuch, 
gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches verschieden 
von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libldap-2.4-2:amd64 ist
  InstallationDate: Installed on 2014-11-23 (122 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  SourcePackage: openldap
  Title: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: 
Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ldap.ldap.conf: [deleted]

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

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

[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

[Brian Murray]

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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

[Touch-packages] [Bug 1650683] [NEW] tracker runs despite search being set to off

[Paul]

Public bug reported:

The master switch in the Search control panel is set to OFF (see
attached screenshot). Yet the tracker daemon runs (poorly, cf. bug
#1650681).

This could under some circumstances lead to privacy violations.

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

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

Title:
  tracker runs despite search being set to off

Status in tracker package in Ubuntu:
  New

Bug description:
  The master switch in the Search control panel is set to OFF (see
  attached screenshot). Yet the tracker daemon runs (poorly, cf. bug
  #1650681).

  This could under some circumstances lead to privacy violations.

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

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

[Touch-packages] [Bug 1650681] Re: tracker-extract uses 1GB of RAM at idle

[Paul]

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1650681/+attachment/4792486/+files/JournalErrors.txt

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

Title:
  tracker-extract uses 1GB of RAM at idle

Status in tracker package in Ubuntu:
  New

Bug description:
  After two weeks, tracker-extract had an RSS of 0.5GB. I rebooted the
  system and logged back in. tracker-extract started working, and had
  soon consumed 1GB. It stopped extracting after a few minutes ("tracker
  daemon -w" shows no further activity) but keeps sitting at around 1GB
  resident.

  Initial:
   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  2425  0.0  1.5 2979100 517124 tty3   SNl+ Dec03   1:54 
/usr/lib/tracker/tracker-extract

  After reboot:
   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  1850  9.4  3.1 4236644 1048948 tty2  SNl+ 08:36   2:35 
/usr/lib/tracker/tracker-extract

  ~/.cache/tracker/meta.db was 46MB before the reboot, and is now 110MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: tracker-extract 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 17 08:52:33 2016
  InstallationDate: Installed on 2016-12-02 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1650681] [NEW] tracker-extract uses 1GB of RAM at idle

[Paul]

Public bug reported:

After two weeks, tracker-extract had an RSS of 0.5GB. I rebooted the
system and logged back in. tracker-extract started working, and had soon
consumed 1GB. It stopped extracting after a few minutes ("tracker daemon
-w" shows no further activity) but keeps sitting at around 1GB resident.

Initial:
 PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
2425  0.0  1.5 2979100 517124 tty3   SNl+ Dec03   1:54 
/usr/lib/tracker/tracker-extract

After reboot:
 PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
1850  9.4  3.1 4236644 1048948 tty2  SNl+ 08:36   2:35 
/usr/lib/tracker/tracker-extract

~/.cache/tracker/meta.db was 46MB before the reboot, and is now 110MB.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: tracker-extract 1.10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Dec 17 08:52:33 2016
InstallationDate: Installed on 2016-12-02 (13 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: tracker
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1650681/+attachment/4792484/+files/JournalErrors.txt

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

Title:
  tracker-extract uses 1GB of RAM at idle

Status in tracker package in Ubuntu:
  New

Bug description:
  After two weeks, tracker-extract had an RSS of 0.5GB. I rebooted the
  system and logged back in. tracker-extract started working, and had
  soon consumed 1GB. It stopped extracting after a few minutes ("tracker
  daemon -w" shows no further activity) but keeps sitting at around 1GB
  resident.

  Initial:
   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  2425  0.0  1.5 2979100 517124 tty3   SNl+ Dec03   1:54 
/usr/lib/tracker/tracker-extract

  After reboot:
   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  1850  9.4  3.1 4236644 1048948 tty2  SNl+ 08:36   2:35 
/usr/lib/tracker/tracker-extract

  ~/.cache/tracker/meta.db was 46MB before the reboot, and is now 110MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: tracker-extract 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 17 08:52:33 2016
  InstallationDate: Installed on 2016-12-02 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648901] Re: SPNEGO crash on mechanism failure

[Eric Desrochers]

** Changed in: krb5 (Ubuntu)
   Importance: Undecided => Low

** Changed in: krb5 (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

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

Title:
  SPNEGO crash on mechanism failure

Status in krb5 package in Ubuntu:
  In Progress

Bug description:
  Chrome (and other things) crash when Kerberos fails to authenticate:
  https://bugs.chromium.org/p/chromium/issues/detail?id=554905

  This was fixed in MIT krb5 in January:
  https://github.com/krb5/krb5/pull/385

  Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffdd687700 (LWP 14851)]
  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  2315  ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
  (gdb) bt
  #0  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668, 
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  #1  0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788, 
  targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730, 
  opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

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

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

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

[Stéphane Graber]

Autopkgtest found a regression related to unprivileged container
execution when combined with overlayfs and the trusty kernel (3.13).

Marking this as verification-failed and will be tracking this done,
fixing upstream and cherry-picking a fix (once we know exactly what's
going on).


This failure didn't occur upstream when testing on a 4.4 kernel, so it suggests 
it's only happening when going down the old overlayfs codepath which the 3.13 
kernel uses.

http://paste.ubuntu.com/23639928/

** Tags removed: verification-needed
** Tags added: verification-failed

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

Title:
  SRU of LXC 1.0.9 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Invalid
Status in lxc source package in Precise:
  In Progress
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  LXC upstream released LXC 1.0.9 as a bugfix release with following
  changelog:

   - Security fix for CVE-2016-8649
   - utils: make detect_ramfs_rootfs() return bool
   - tests: add test for detect_ramfs_rootfs()
   - add Documentation entries to lxc and lxc@ units
   - mark the python examples as having utf-8 encoding
   - log: sanity check the returned value from snprintf()
   - lxc-alpine: mount /dev/shm as tmpfs
   - archlinux: Do DHCP on eth0
   - archlinux: Fix resolving
   - Drop leftover references to lxc_strerror()
   - tests: fix image download for s390x
   - tools: fix coding style in lxc_attach
   - tools: make overlay valid backend
   - tools: better error reporting for lxc-start
   - alpine: Fix installing extra packages
   - lxc-alpine: do not drop setfcap
   - s390x: Fix seccomp handling of personalities
   - tools: correct the argument typo in lxc_copy
   - Use libtool for liblxc.so
   - c/r: use --external instead of --veth-pair
   - c/r: remember to increment netnr
   - c/r: add checkpoint/restore support for macvlan interfaces
   - ubuntu: Fix package upgrades requiring proc
   - c/r: drop duplicate hunk from macvlan case
   - c/r: use snprintf to compute device name
   - Tweak libtool handling to work with Android
   - tests: add lxc_error() and lxc_debug()
   - container start: clone newcgroup immediately
   - use python3_sitearch for including the python code
   - fix rpm build, include all built files, but only once
   - cgfs: fix invalid free()
   - find OpenSUSE's build also as obs-build
   - improve help text for --fancy and --fancy-format
   - improve wording of the help page for lxc-ls
   - cgfs: add print_cgfs_init_debuginfo()
   - cgfs: skip empty entries under /proc/self/cgroup
   - cgfs: explicitly check for NULL
   - tools: use correct exit code for lxc-stop
   - c/r: explicitly emit bind mounts as criu arguments
   - log: bump LXC_LOG_BUFFER_SIZE to 4096
   - conf: merge network namespace move & rename on shutdown
   - c/r: save criu's stdout during dump too
   - c/r: remove extra \ns from logs
   - c/r: fix off-by-one error
   - c/r: check state before doing a checkpoint/restore
   - start: CLONE_NEWCGROUP after we have setup cgroups
   - create symlink for /var/run
   - utils: add lxc_append_string()
   - cgroups: remove isolated cpus from cpuset.cpus
   - Update Ubuntu release name: add zesty and remove wily
   - templates: add squashfs support to lxc-ubuntu-cloud.in
   - cgroups: skip v2 hierarchy entry
   - also stop lxc-net in runlevels 0 and 6
   - add lxc.egg-info to gitignore
   - install bash completion where pkg-config tells us to
   - conf: do not use %m format specifier
   - debian: Don't depend on libui-dialog-perl
   - cgroups: use %zu format specifier to print size_t
   - lxc-checkpoint: automatically detect if --external or --veth-pair
   - cgroups: prevent segfault in cgfsng
   - utils: add lxc_preserve_ns()
   - start: add netnsfd to lxc_handler
   - conf: use lxc_preserve_ns()
   - attach: use lxc_preserve_ns()
   - lxc_user_nic: use lxc_preserve_ns()
   - conf, start: improve log output
   - conf: explicitly remove veth device from host
   - conf, start: be smarter when deleting networks
   - start, utils: improve preserve_ns()
   - start, error: improve log + non-functional changes
   - start, namespace: move ns_info to namespace.{c,h}
   - attach, utils: bugfixes
   - attach: use ns_info[LXC_NS_MAX] struct
   - namespace: always attach to user namespace first
   - cgroup: improve isolcpus handling
   - cgroups: handle non-existent isolcpus file
   - utils: add lxc_safe_uint()
   - tests: add unit tests for lxc_safe_uint()
   - utils: add lxc_safe_int()
   - tests: add unit tests for lxc_safe_int()
   - conf/ile: get ip prefix via lxc_safe_uint()
   - confile: use lxc_safe_u/int in config_init_{u,g}id
   - conf/ile: use lxc_safe_uint() in config_pts()
   - conf/ile: use lxc_safe_u/int() in config_start()
   - conf/ile: use lxc_safe_uint() in config_monitor()
   - conf/ile: use lxc_safe_uint() in 

[Touch-packages] [Bug 1650634] Re: when installing systemd, it creates /run/nologin preventing all users from logging in.

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => 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/1650634

Title:
  when installing systemd, it creates /run/nologin preventing all users
  from logging in.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd package in Suse:
  Unknown

Bug description:
  How to replicate:

  sudo apt-get install systemd

  wait for 5 minutes

  check to see if /run/nologin appears. If it does the bug is present.
  See https://ubuntuforums.org/showthread.php?t=2327330

  I ran this command via ansible on all of my servers. Then I could no
  longer log into any of them. Pretty big bug in my opinion. Please fix.

  -Tim

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd 204-5ubuntu20.20
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Dec 16 12:03:55 2016
  InstallationDate: Installed on 2014-04-21 (970 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

[Patrick Kilgore]

@benjaoming Looks like commit notes mixed up between 3114 and 3112.

The eval fix (CVE-2016-9949) is in 3112:

https://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/3112/

The patch in 3114 fixes CVE-2016-9951 (Relaunch code execution).

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Released

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

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

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

[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'

[Brian Murray]

There are a couple of instances of this occurring with 1.2.18, but I
think that is just noise as apport doesn't add package version
information until the data collection is done which can be a bit after
the crash.

 $ tools/pycassa-db-query.py 
'/usr/share/gdebi/gdebi-gtk%3AValueError%3A/usr/bin/gdebi-gtk%40100%3Aon_button_install_clicked%3Adpkg_action%3Acommit%3Ainstall_archives%3Arun%3Await_child%3Aupdate_interface%3Aupdate_interface'
5888 examined.
{u'1.2.18': 2, u'1.2.15ubuntu0.2': 859, u'1.3.1': 0, u'1.2.14': 2, u'1.2.15': 
5005}

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

Title:
  gdebi-gtk crashed with ValueError in update_interface(): could not
  convert string to float: '0,'

Status in apt package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Fix Committed
Status in gdebi source package in Xenial:
  Confirmed

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
  and
  https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a

  [Impact]
  Crashes of gdebi (and possibly other tools) in non-English locales which use 
1,0 or similar instead of 1.0

  [Test case]
  Install a deb package with gdebi, like Google Chrome, in such a locale.

  Original: Gdebi crashed while installing Google Chrome .deb-fil bur
  the error didn't appear until I logged out and back in again

  [Regression potential]
  Same as bug 1611010 - very low.

  
  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

[Pat McGowan]

Agree, marking this won't fix, we can re-open if we see other symptoms

** Changed in: canonical-devices-system-image
   Status: Confirmed => Won't Fix

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Won't Fix
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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

[Touch-packages] [Bug 1592427] Re: I can't disable proposed updates

[ajgreeny]

Just as a trial I have a few minutes ago restored the proposed.list file
to /etc/apt/sources.list.d/ which is where I originally found it, and
once again I am not able to disable the proposed repos from software-
sources GUI.  Whatever I do, the tick in the selection box of the
Developer Options tab stays firmly selected.

Removing that proposed.list file once again as I did before has once
more disabled the proposed repos.

So it looks as if something has added those proposed.list files to
/etc/apt/sources.list.d/ with no reference to me, and I am completely
baffled about what has been done, by what process, and why it happened.

I do have several ppa repos enabled, but I always have done so without
this ever occurring in the past, so I believe that is unconnected.

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

Title:
  I can't disable proposed updates

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Hi!!

  Accidentally I've enabled proposed updates in development section but
  now I can't disable it. I've rebooted the laptop but the issue isn't
  fixed.

  
  Regards!!

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

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

[Touch-packages] [Bug 1649477] Re: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: EOF on stdin at conffile prompt

[Tyler Hicks]

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

Title:
  package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: EOF on stdin at conffile prompt

Status in ntp package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Tue Dec 13 11:43:50 2016
  DpkgTerminalLog: Log started: 2016-12-13  11:25:42
  ErrorMessage: EOF on stdin at conffile prompt
  InstallationDate: Installed on 2013-11-26 (1112 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: ntp
  Title: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to 
install/upgrade: EOF on stdin at conffile prompt
  UpgradeStatus: Upgraded to trusty on 2014-11-23 (750 days ago)

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

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

[Touch-packages] [Bug 1650359] Re: g compiz error

[Tyler Hicks]

** 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/1650359

Title:
  g compiz error

Status in xorg package in Ubuntu:
  New

Bug description:
  sorry but ubuntu has experienced ann internal error.
  that's all i get recently.
  I will not allow source code, even from canonical as it can be manipulated 
apparently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.98  Mon Sep 19 17:31:03 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Dec 15 19:14:33 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-28-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848f]
  InstallationDate: Installed on 2016-09-18 (88 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug splash quiet drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd01/06/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Dec 15 18:35:01 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputEee PC WMI hotkeys   KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu6.1

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

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

[Touch-packages] [Bug 1649959] Re: unattended upgrade of apt kills running apt-daily job

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.3.3

---
apt (1.3.3) yakkety; urgency=medium

  [ Michael Vogt ]
  * Do not (re)start "apt-daily.system"
Thanks to Alexandre Detiste (Closes: #841763) (LP: #1649959)

 -- Julian Andres Klode   Wed, 14 Dec 2016 20:25:22
+0100

** Changed in: apt (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  unattended upgrade of apt kills running apt-daily job

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Causes automatic upgrades by unattended-upgrades to be interrupted if apt is 
configured, leaving the system in a partially configured state.

  [Test case]
  Install apt - make sure the apt-daily.service is not restarted (this systemd 
service runs unattended-upgrades)

  [Regression Potential] 
  It's only overriding dh_systemd_start to not be called for the service, so I 
don't see any possibility for regressions.

  [Original Bug report]
  This morning, I discovered that my new xenial system had attempted an 
unattended upgrade overnight but the upgrade was incomplete. It attempted to 
upgrade
  apt apt-transport-https apt-utils firefox firefox-locale-en 
flashplugin-installer libapt-inst2.0 libapt-pkg5.0 libgme0

  but the unattended-upgrades-dpkg.log log terminates after apt is
  configured.

  I had to dpkg --configure --pending and apt-get -f install to get apt back 
into working order.
  There were no errors, crashes or cores logged.

  The journal indicates that apt-daily.service stopped and restarted around the 
time of the upgrade, so I am assuming that is the problem (that systemd killed 
the update session as the result of an update to the unit files)
  ---
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-12-06 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NonfreeKernelModules: openafs
  Package: apt 1.3.2ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Tags:  yakkety
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1650667] Re: Dapper Contents files are empty at old-releases.ubuntu.com

[mpb]

I have no idea why Launchpad classified this bug as belonging to
systemd.  I thought I told launchpad that I did not know which package
should be associated with this bug.  Sorry!


** Package changed: systemd (Ubuntu) => dapper-backports

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

Title:
  Dapper Contents files are empty at old-releases.ubuntu.com

Status in Dapper Backports:
  New

Bug description:
  Is there some reason that the Contents-.gz files are empty for
  Dapper at old-releases.ubuntu.com?

  http://old-releases.ubuntu.com/ubuntu/dists/dapper/

  Contents-amd64.gz   29-Apr-2011 05:39  677   
  Contents-hppa.gz16-Dec-2008 05:56  9.1M  
  Contents-i386.gz29-Apr-2011 05:39  677   
  Contents-ia64.gz29-Apr-2011 05:39  677   
  Contents-powerpc.gz 29-Apr-2011 05:39  677   
  Contents-sparc.gz   29-Apr-2011 05:39  677

  Contents-hppa.gz is 9.1M, but all the others are only 677 bytes long.

  Is this fixable?

To manage notifications about this bug go to:
https://bugs.launchpad.net/dapper-backports/+bug/1650667/+subscriptions

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

[Touch-packages] [Bug 1640290] Re: Update Qt to 5.7.1

[Flames_in_Paradise]

Well, he got a nice & sensible reply. 
Made a new LP-bug 1650662 out of it (upgrade SW-version–Qt-Creator) x-refd this 
bug there. 

btw Debian was pretty fast to incorporate new Qt -lightspeed- Big
thanks!

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

Title:
  Update Qt to 5.7.1

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

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

  Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
  More information: https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1650667] [NEW] Dapper Contents files are empty at old-releases.ubuntu.com

[mpb]

Public bug reported:

Is there some reason that the Contents-.gz files are empty for
Dapper at old-releases.ubuntu.com?

http://old-releases.ubuntu.com/ubuntu/dists/dapper/

Contents-amd64.gz   29-Apr-2011 05:39  677   
Contents-hppa.gz16-Dec-2008 05:56  9.1M  
Contents-i386.gz29-Apr-2011 05:39  677   
Contents-ia64.gz29-Apr-2011 05:39  677   
Contents-powerpc.gz 29-Apr-2011 05:39  677   
Contents-sparc.gz   29-Apr-2011 05:39  677

Contents-hppa.gz is 9.1M, but all the others are only 677 bytes long.

Is this fixable?

** Affects: dapper-backports
 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/1650667

Title:
  Dapper Contents files are empty at old-releases.ubuntu.com

Status in Dapper Backports:
  New

Bug description:
  Is there some reason that the Contents-.gz files are empty for
  Dapper at old-releases.ubuntu.com?

  http://old-releases.ubuntu.com/ubuntu/dists/dapper/

  Contents-amd64.gz   29-Apr-2011 05:39  677   
  Contents-hppa.gz16-Dec-2008 05:56  9.1M  
  Contents-i386.gz29-Apr-2011 05:39  677   
  Contents-ia64.gz29-Apr-2011 05:39  677   
  Contents-powerpc.gz 29-Apr-2011 05:39  677   
  Contents-sparc.gz   29-Apr-2011 05:39  677

  Contents-hppa.gz is 9.1M, but all the others are only 677 bytes long.

  Is this fixable?

To manage notifications about this bug go to:
https://bugs.launchpad.net/dapper-backports/+bug/1650667/+subscriptions

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

[Touch-packages] [Bug 1592427] Re: I can't disable proposed updates

[ajgreeny]

I found the two files, proposed.list and proposed.list.save in
/etc/apt/sources.list.d folder and both of them had the same content:-

deb http://gb.archive.ubuntu.com/ubuntu/ xenial-proposed universe main
multiverse restricted

Neither file had that one line commented out with a # as I would expect.
I removed those files and now I can enable and disable the proposed
repos and if enabled the /etc/apt/sources.list file contains a line as
shown above as I expected.

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

Title:
  I can't disable proposed updates

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Hi!!

  Accidentally I've enabled proposed updates in development section but
  now I can't disable it. I've rebooted the laptop but the issue isn't
  fixed.

  
  Regards!!

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

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

[Touch-packages] [Bug 1650666] [NEW] GVim crashes when opening new tab

[Гурьев Николай]

Public bug reported:

When I open new tab using :tabnew command, GVim crashes in
unity_gtk_menu_section_get_item_attributes function of libunity-
gtk3-parser0 package.


Steps to reproduce:
1. Run gvim from vim-gtk3 package
2. Type `:tabnew`
3. GVim exits, the window closes


Stack trace obtained via gdb:

mymedia@comp2:~$ gdb -silent --args gvim -f -u /dev/null -U /dev/null --noplugin
Reading symbols from gvim...(no debugging symbols found)...done.
gdb$ run
Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe986d700 (LWP 11042)]
[New Thread 0x7fffe906c700 (LWP 11043)]
[New Thread 0x7fffe886b700 (LWP 11044)]

(gvim:11038): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <=
(gint)rarray->len' failed

** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
'0 <= index && index < items->len' failed

** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_child_shell:
assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed

** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
'0 <= index && index < items->len' failed

** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_label: assertion
'UNITY_GTK_IS_MENU_ITEM (item)' failed

** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_icon: assertion
'UNITY_GTK_IS_MENU_ITEM (item)' failed

Thread 1 "gvim" received signal SIGSEGV, Segmentation fault.
unity_gtk_menu_section_get_item_attributes (model=, 
item_index=, 
attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130
130 ../../../lib/unity-gtk-menu-section.c: Нет такого файла или каталога.
gdb$ backtrace 
#0  0x7fffe9a82083 in unity_gtk_menu_section_get_item_attributes 
(model=, item_index=, attributes=0x7fff8b90) 
at ../../../lib/unity-gtk-menu-section.c:130
#1  0x7653f23c in g_menu_model_real_iterate_item_attributes 
(model=0x56016160 [UnityGtkMenuSection], item_index=) at 
././gio/gmenumodel.c:299
#2  0x76541070 in g_menu_exporter_menu_describe_item 
(position=position@entry=1, menu=, menu=) at 
././gio/gmenuexporter.c:212
#3  0x765414be in g_menu_exporter_menu_items_changed (model=, position=1, removed=0, added=, user_data=0x55ffd4c0) 
at ././gio/gmenuexporter.c:276
#4  0x7fffee607e18 in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#5  0x7fffee60787a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#10 0x7626efaf in  (instance=, signal_id=, 
detail=)
at ././gobject/gsignal.c:3447
#6  0x762547ae in g_cclosure_marshal_generic 
(closure=0x5607fd10, return_gvalue=0x0, n_param_values=, 
param_values=, invocation_hint=, 
marshal_data=) at ././gobject/gclosure.c:1490
#7  0x76253f75 in g_closure_invoke (closure=0x5607fd10, 
return_value=return_value@entry=0x0, n_param_values=4, 
param_values=param_values@entry=0x7fff9250, 
invocation_hint=invocation_hint@entry=0x7fff91d0) at 
././gobject/gclosure.c:804
#8  0x76265f82 in signal_emit_unlocked_R 
(node=node@entry=0x55f38af0, detail=detail@entry=0, 
instance=instance@entry=0x56016160, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fff9250) at 
././gobject/gsignal.c:3635
#9  0x7626ebcc in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fff9440)
at ././gobject/gsignal.c:3391
#14 0x7626efaf in  (instance=, signal_id=, 
detail=) at ././gobject/gsignal.c:3447
#11 0x76253f75 in g_closure_invoke (closure=0x56054e20, 
return_value=return_value@entry=0x0, n_param_values=3, 
param_values=param_values@entry=0x7fff96d0, 
invocation_hint=invocation_hint@entry=0x7fff9650) at 
././gobject/gclosure.c:804
#12 0x76265f82 in signal_emit_unlocked_R 
(node=node@entry=0x55aee490, detail=detai---Type  to continue, or q 
 to quit---
l@entry=0, instance=instance@entry=0x55e7b9c0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fff96d0) at 
././gobject/gsignal.c:3635
#13 0x7626ebcc in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fff98b0)
at ././gobject/gsignal.c:3391
#15 0x5575edef in gui_mch_add_menu_item ()
#16 0x5566c0e0 in  ()
#17 0x5566c976 in ex_menu ()
#18 0x5561e4cf in do_cmdline ()
#19 0x555e7afe in ex_execute ()
#20 0x5561e4cf in do_cmdline ()
#21 0x55746879 in call_func ()
#22 0x557472d5 in get_func_tv ()
#23 0x55749d0f in ex_call ()
#24 0x5561e4cf in do_cmdline ()
#25 0x55746879 in call_func ()
#26 0x557472d5 in get_func_tv ()
#27 0x55749d0f in ex_call ()
#28 0x5561e4cf in do_cmdline ()
#29 0x55639d76 in  ()
#30 0x5563a5e4 in apply_autocmds ()

[Touch-packages] [Bug 1650591] Re: package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již nainstalován a zkonfigurován

[Julian Andres Klode]

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

Just to add: I marked this as a duplicate of  bug #1649959 a few hours
ago, but I was on the go, so I did not have time to write a comment. See
the other bug for more information.

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

Title:
  package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již
  nainstalován a zkonfigurován

Status in apt package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   apt:amd64: Configure
   apt-utils:amd64: Install
   linux-tools-4.8.0-30-lowlatency:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Dec 14 21:19:25 2016
  DpkgTerminalLog:
   dpkg: chyba při zpracovávání balíku apt (--configure):
balík apt je již nainstalován a zkonfigurován
  ErrorMessage: balík apt je již nainstalován a zkonfigurován
  InstallationDate: Installed on 2016-10-08 (69 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.2ubuntu0.1
  SourcePackage: apt
  Title: package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již 
nainstalován a zkonfigurován
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (57 days ago)

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

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

[Touch-packages] [Bug 1650634] Re: when installing systemd, it creates /run/nologin preventing all users from logging in.

[tim.tadh]

** Bug watch added: bugzilla.opensuse.org/ #980324
   http://bugzilla.opensuse.org/show_bug.cgi?id=980324

** Also affects: systemd via
   http://bugzilla.opensuse.org/show_bug.cgi?id=980324
   Importance: Unknown
   Status: Unknown

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

** Changed in: systemd
 Remote watch: bugzilla.opensuse.org/ #980324 => 
github.com/systemd/systemd/issues #3436

** Also affects: systemd (Suse) via
   http://bugzilla.opensuse.org/show_bug.cgi?id=980324
   Importance: Unknown
   Status: Unknown

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

Title:
  when installing systemd, it creates /run/nologin preventing all users
  from logging in.

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New
Status in systemd package in Suse:
  Unknown

Bug description:
  How to replicate:

  sudo apt-get install systemd

  wait for 5 minutes

  check to see if /run/nologin appears. If it does the bug is present.
  See https://ubuntuforums.org/showthread.php?t=2327330

  I ran this command via ansible on all of my servers. Then I could no
  longer log into any of them. Pretty big bug in my opinion. Please fix.

  -Tim

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd 204-5ubuntu20.20
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Dec 16 12:03:55 2016
  InstallationDate: Installed on 2014-04-21 (970 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1647638] Re: W: APT had planned for dpkg to do more than it reported back

[Adolfo Jayme]

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

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

Title:
  W: APT had planned for dpkg to do more than it reported back

Status in apt package in Ubuntu:
  New

Bug description:
  I noticed that base-files was not completely installed and meant to
  fix it with "sudo apt-get install --reinstall base-files". This
  resulted in the following output.

  $ LANG=C sudo apt-get install --reinstall base-files
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-4.9.0-4 linux-headers-4.9.0-4-generic 
linux-image-4.9.0-4-generic linux-image-extra-4.9.0-4-generic
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 13 not upgraded.
  Need to get 0 B/56,9 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 598721 files and directories currently installed.)
  Preparing to unpack .../base-files_9.6ubuntu8_amd64.deb ...
  Unpacking base-files (9.6ubuntu8) over (9.6ubuntu8) ...
  Setting up base-files (9.6ubuntu8) ...
  Processing triggers for install-info (6.3.0.dfsg.1-1) ...
  Processing triggers for cracklib-runtime (2.9.2-3) ...
  Processing triggers for plymouth-theme-ubuntu-gnome-text (16.10.5) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-2) ...
  Processing triggers for initramfs-tools (0.125ubuntu8) ...
  update-initramfs: Generating /boot/initrd.img-4.9.0-8-generic
  W: APT had planned for dpkg to do more than it reported back (4 vs 6).
 Affected packages: base-files:amd64

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty

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

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

[Touch-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

** Tags added: zesty

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

[Rodney Dawes]

Actually, since the app drawer has landed now, can we just remove unity-
scope-click from the snap?

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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

[Touch-packages] [Bug 1592427] Re: I can't disable proposed updates

[Brian Murray]

Were in /etc/apt/sources.list.d/ did you find proposed enabled?  What
was the name of the file and what were its contents?

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  I can't disable proposed updates

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Hi!!

  Accidentally I've enabled proposed updates in development section but
  now I can't disable it. I've rebooted the laptop but the issue isn't
  fixed.

  
  Regards!!

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

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

[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

[Christian Brauner]

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

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1649662] Re: [regression] resizing a some apps in Unity8 makes them distorted and freeze (usually software clients)

[Lukáš Tinkl]

It resumes working when you shrink the window to its very minimal size
but breaks again when enlarging it.

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

Title:
  [regression] resizing a some apps in Unity8 makes them distorted and
  freeze (usually software clients)

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]

  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"

  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)

  see attached screenshot

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

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

[Touch-packages] [Bug 1648938] Re: Update tracker to 1.10.2

[Jeremy Bicha]

We'll need to update this to 1.10.3 which whitelists a few more system
calls.

** Tags removed: verification-needed
** Tags added: verification-failed

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

Title:
  Update tracker to 1.10.2

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  =
  This update includes the new bugfix releases 1.10.1 and 1.10.2
  https://git.gnome.org/browse/tracker/tree/NEWS?h=tracker-1.10
  https://git.gnome.org/browse/tracker/log?h=tracker-1.10

  The major change is that the tracker extractor is now confined by
  libseccomp for better security (LP: #1648921)

  Test Case
  =
  I recommend testing with Ubuntu GNOME 16.10 since it includes tracker.
  1. After installing the update, log out and log back in just to make sure 
you're running the updated tracker
  2. Download some pictures or music files to an indexed folder (~/Downloads, 
~/Music, ~/Pictures are good)
  3. Wait a few moments and see if the files show up in the GNOME Music app, 
the GNOME Photos app, and/or the GNOME Shell Activities Overview when searching 
for that filename.
  4. You can also look for any tracker errors to show up in the GNOME Logs app 
(gnome-logs is a frontend to the systemd journal)

  Regression Potential
  
  Low. Ensure that tracker still works.

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

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

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

[Norbert]

Get this issue on Ubuntu 12.04.5 amd64 host using VirtualBox 5.1.10 with Ubuntu 
16.04.1 x86 guest.
The screen shows rainbow of pixels, not the desktop. Turning off 3D 
acceleration does not solve the problem.
Pressing right Ctrl+F1, then Ctrl+F7 solved the problem.

Dear Ubuntu developers, please fix this problem or contact VirtualBox
developers. VirtualBox-way is the easiest to get first impression of
Ubuntu. So it is expected that Ubuntu will work on VirtualBox without
special actions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[LaMont Jones]

Reconfirmed yakkety today.

Also tested "ip6= without ip=": which yakkety currently hates, but we've
decided to handle separately after this SRU lands, partially because
it's a trivial workaround ("for ipv6-only, specify "ip6=dhcp ip=off")
and also not a case that anything needing the SRU actually does.  (MAAS
always specifies both, with one of them set to "off".)

Marking this verification-done.

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
   X / Y
- [+]/[ ] MAAS on IPv6-only network
- [+]/[ ] MAAS on IPv4-only network
- [+]/[ ] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
- [+]/[ ] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
+ [+]/[+] MAAS on IPv6-only network
+ [+]/[+] MAAS on IPv4-only network
+ [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
+ [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source 

[Touch-packages] [Bug 1622041] Re: Mobile network denied

[jessesmith]

I have this bug  still, though much less frequently. I have updated the
linked bug report. I'm in Canada on the Telus network so it is an issue
that affects people outside the USA.

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

Title:
  Mobile network denied

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  Device: Running Ubuntu 15.04 (OTA-13-rc) on the Meizu Pro 5.

  Description of problem: When I power on the phone, it connects to my
  mobile network for a brief period of time. I can send/receive SMS
  texts and make phone calls. After a few minutes though the mobile
  connection drops and the mobile status in the pull-down panel shows
  "Denied". It is then no longer possible to place calls or send/receive
  SMS texts.

  This issue started happening immediately following the upgrade from
  Ubuntu 15.04 (r-14) to the new OTA-13-rc upgrade which became
  available at the start of September.

  I have another phone running Android on the same network which is
  running smoothly, no connection issues.

  I suspect this is more than an indication issue, from what I've read
  the dropped mobile connection may be a software/firmware problem, but
  I haven't been able to find a location/project more suitable where
  this bug can be filed. My apologies.

  My phone's syslog file is downloadable from the link below. The
  problem occurs on September 9th between 19:00 and 20:00.
  http://resonatingmedia.com/logs/syslog.txt

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

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

[Touch-packages] [Bug 1543185] Re: Malformed query causing timeouts due to ignored upstream queries

[Joshua Powers]

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

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

Title:
  Malformed query causing timeouts due to ignored upstream queries

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  In some situations dnsmasq makes malformed upstream queries resulting
  in servfail being returned after the 5s timeout built in to dnsmask.

  For example asking for

  foo

  with athing.bar.com and bar.com in the search path and two servers
  dns1.bar.com and dns1.bar.com results in

  System asks both dns1 and dns2 about: 
 foo.athing.bar.com => immediate NXDomain from both;
  asks  dns1 about:
foo.  => Servfail;
  asks both about:
   foo. with what tcpdump transcribes as '[b2&3=0x182] A?  => no 
response from either [5 sec timeout];
  retries:
   simple "A? foo." query to both, immediate Servfail from both

  The query giving the time out appear to be malformed and the upstream
  servers are completely ignoring it leading to the time out.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dnsmasq-base 2.68-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb  8 15:38:26 2016
  InstallationDate: Installed on 2014-05-07 (642 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 822041] Re: software-properties-kde Other Software list jumps on de-selection

[Flames_in_Paradise]

Probably this needs to be ported to QT5 ?

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

Title:
  software-properties-kde Other Software list jumps on de-selection

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  unticking a box in Other Software causes the scrollbar to jump up to
  the top of the list

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

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

[Touch-packages] [Bug 1595607] Re: /bin/nano:*** Error in `nano': free(): invalid next size (normal): ADDR ***

[Brian Murray]

** Description changed:

+ [Test Case]
+ Using the provided Error Tracker bucket confirm that there are no instances 
of the crash with the version of the package from -proposed.  Given that we 
don't have a reproducer we should let the package age for longer than 7 days to 
ensure many users are testing it.
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/d609e39daa79867af99f7c1c75f3db7b998971d9
  contains more details.

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

Title:
  /bin/nano:*** Error in `nano': free(): invalid next size (normal):
  ADDR ***

Status in nano package in Ubuntu:
  Fix Released
Status in nano source package in Xenial:
  Fix Committed

Bug description:
  [Test Case]
  Using the provided Error Tracker bucket confirm that there are no instances 
of the crash with the version of the package from -proposed.  Given that we 
don't have a reproducer we should let the package age for longer than 7 days to 
ensure many users are testing it.

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/d609e39daa79867af99f7c1c75f3db7b998971d9
  contains more details.

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

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

[Touch-packages] [Bug 1592427] Re: I can't disable proposed updates

[ajgreeny]

OK, that worked as expected, and now when I go to Software Sources from the 
Xubuntu menu I can enable and disable the proposed repos without a problem as I 
expect to be able to do.
This is baffling!

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

Title:
  I can't disable proposed updates

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Hi!!

  Accidentally I've enabled proposed updates in development section but
  now I can't disable it. I've rebooted the laptop but the issue isn't
  fixed.

  
  Regards!!

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

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

[Touch-packages] [Bug 1611363] Re: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

[Bug Watch Updater]

** Changed in: vim
   Status: Unknown => Fix Released

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

Title:
  vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

Status in vim:
  Fix Released
Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Xenial:
  Confirmed

Bug description:
  Hi, vim-gtk3 crashes so often on my system that it's borderline unusable.
  My system is a clean install of Ubuntu 16.04. I also (temporarily) renamed my 
customized ~/.vimrc and ~/.vim. My system is up-to-date as of today 
(2016-08-09); installed vim-gtk3 is 2:7.4.1689-3ubuntu1.1.

  The crash happens only (but very frequently, not always) when I launch
  gvim, either by calling it from a shell or by double-clicking a file
  in Nautilus. Note that the crash is independent of whether I'm opening
  a file or not. (At least I tried both variations from the terminal.)

  There's also a report on vim's bugtracker, but since unity appears in
  the backtrace, the consensus is that it's probably Ubuntu-specific.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: vim-gtk3 2:7.4.1689-3ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  9 14:34:31 2016
  ExecutablePath: /usr/bin/vim.gtk3
  InstallationDate: Installed on 2016-07-10 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: gvim -f 
/home/username/Documents/schoul/2016/1G-TODO/01-systemes-equations-TODO/chap01_systemes-equations-NOTES.tex
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: vim.gtk3 crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1650631] Re: ip6=dhcp turns on ip=dhcp

[LaMont Jones]

Based on a conversation with Scott, we are both of the opinion that this
bug should not delay the landing of the fixes for bug 1621507 and bug
1621615 into xenial and yakkety.

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

Title:
  ip6=dhcp turns on ip=dhcp

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  When testing bug 1639930 I found that booting a system with:
   ip6=dhcp 
  will enable ip=dhcp.  ip= does not enable ip6=dhcp, so this is odd behavior.

  Thus, if you had an ip6 only network, in order to do this you have to do:
   ip6=dhcp ip=off

  This is really just a matter of a very strange behavior, but behavior that 
can be fixed by just explicitly passing ip=off.


  Related bugs:
   * bug 1639930: initramfs network configuration ignored if only ip6= on 
kernel command line 
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.7
  ProcVersionSignature: User Name 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Dec 16 17:06:23 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1650634] [NEW] when installing systemd, it creates /run/nologin preventing all users from logging in.

[tim.tadh]

Public bug reported:

How to replicate:

sudo apt-get install systemd

wait for 5 minutes

check to see if /run/nologin appears. If it does the bug is present. See
https://ubuntuforums.org/showthread.php?t=2327330

I ran this command via ansible on all of my servers. Then I could no
longer log into any of them. Pretty big bug in my opinion. Please fix.

-Tim

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: systemd 204-5ubuntu20.20
ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
Uname: Linux 3.13.0-105-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Dec 16 12:03:55 2016
InstallationDate: Installed on 2014-04-21 (970 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  when installing systemd, it creates /run/nologin preventing all users
  from logging in.

Status in systemd package in Ubuntu:
  New

Bug description:
  How to replicate:

  sudo apt-get install systemd

  wait for 5 minutes

  check to see if /run/nologin appears. If it does the bug is present.
  See https://ubuntuforums.org/showthread.php?t=2327330

  I ran this command via ansible on all of my servers. Then I could no
  longer log into any of them. Pretty big bug in my opinion. Please fix.

  -Tim

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd 204-5ubuntu20.20
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Dec 16 12:03:55 2016
  InstallationDate: Installed on 2014-04-21 (970 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1496163] Re: i915 firmware is not copied to initrd

[Brian Murray]

I've uploaded this to Trusty queue for review by the SRU team.

** Changed in: initramfs-tools (Ubuntu Trusty)
 Assignee: Andy Whitcroft (apw) => Brian Murray (brian-murray)

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

Title:
  i915 firmware is not copied to initrd

Status in Skylinux:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Vivid:
  Won't Fix
Status in initramfs-tools source package in Wily:
  Fix Released

Bug description:
  [ Impact ]

  On Skylake, skl_dmc firmware is not incorporated into the initramfs.
  This is because it is a symlink to a versioned blob and the initramfs-
  tools hook does not dereference symlinks. As the driver is actually
  loaded from the initramfs, the firmware is missing for the lifetime of
  the boot, which means that the GPU cannot enter its lowest available
  power states plus some hotplugging scenarios are broken. This all
  manifests itself as such in dmesg:

  [0.728803] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1.bin failed with error -2
  [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to 
load firmware i915/skl_dmc_ver1.bin (0)

  [ Test Case ]

  After the fix has been applied and the initrd regenerates, the
  firmware should load successfully after a reboot.

  [ Regression Potential ]

  Unlikely, as the fix is part of Ubuntu since Wily.

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

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

[Touch-packages] [Bug 1650631] [NEW] ip6=dhcp turns on ip=dhcp

[Scott Moser]

Public bug reported:

When testing bug 1639930 I found that booting a system with:
 ip6=dhcp 
will enable ip=dhcp.  ip= does not enable ip6=dhcp, so this is odd behavior.

Thus, if you had an ip6 only network, in order to do this you have to do:
 ip6=dhcp ip=off

This is really just a matter of a very strange behavior, but behavior that can 
be fixed by just explicitly passing ip=off.
  

Related bugs:
 * bug 1639930: initramfs network configuration ignored if only ip6= on kernel 
command line 
 * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.7
ProcVersionSignature: User Name 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Fri Dec 16 17:06:23 2016
PackageArchitecture: all
ProcEnviron:
 TERM=vt220
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed uec-images xenial

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

Title:
  ip6=dhcp turns on ip=dhcp

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  When testing bug 1639930 I found that booting a system with:
   ip6=dhcp 
  will enable ip=dhcp.  ip= does not enable ip6=dhcp, so this is odd behavior.

  Thus, if you had an ip6 only network, in order to do this you have to do:
   ip6=dhcp ip=off

  This is really just a matter of a very strange behavior, but behavior that 
can be fixed by just explicitly passing ip=off.


  Related bugs:
   * bug 1639930: initramfs network configuration ignored if only ip6= on 
kernel command line 
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.7
  ProcVersionSignature: User Name 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Dec 16 17:06:23 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649352] Re: http direct to terminals?

[Dustin Kirkland ]

** Changed in: base-files (Ubuntu)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

** Changed in: base-files (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  http direct to terminals?

Status in base-files package in Ubuntu:
  In Progress

Bug description:
  Hi Dustin,

  Some recent changes introduced what looks to be a serious problem:

  http://launchpadlibrarian.net/296647523/base-
  files_9.6ubuntu7_9.6ubuntu8.diff.gz

  -SERVER="https://motd.ubuntu.com;
  +# White space separated list of 0 to many news services
  +SERVER="http://motd.ubuntu.com;
  [...]
  + if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" 
-o- "$s" >"$NEWS" 2>"$ERR"; then
  + echo
  + # At most, 2 lines of at most 80 characters
  + cat "$NEWS" | tail -n 2 | cut -c -80

  This allows any network man-in-the-middle attacker, DNS response
  forger, or BGP forger, to write 160 raw bytes directly to terminals.

  The previous version wasn't good (open for abuse by anyone who could
  trick one of the myriad x.509 Certificate Authorities to mis-issue a
  certificate) but this version is open for abuse by significantly more
  attackers.

  While most terminals are reasonably safe against outright
  maliciousness this has been a recurring exploitation theme for twenty
  years, and even what is "safe" for them to display could be wildly
  confusing to users unfamiliar with maliciously controlled terminals.
  (And users have wide tastes in terminals, some are fairly brittle.)

  cat(1) does not do any filtering for 'safe' display of arbitrary
  inputs. less(1) does, assuming -r is not in LESS environment variable
  or the less(1) command line. If you wish to keep the pipeline, perhaps
  tr(1)'s -d flag could be useful.

  On a related note, is there a reason why the motd.ubuntu.com server
  can't do HTTPS?

  Thanks

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

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

[Touch-packages] [Bug 1496163] Re: i915 firmware is not copied to initrd

[Brian Murray]

** Changed in: initramfs-tools (Ubuntu Vivid)
   Status: In Progress => Won't Fix

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

Title:
  i915 firmware is not copied to initrd

Status in Skylinux:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Vivid:
  Won't Fix
Status in initramfs-tools source package in Wily:
  Fix Released

Bug description:
  [ Impact ]

  On Skylake, skl_dmc firmware is not incorporated into the initramfs.
  This is because it is a symlink to a versioned blob and the initramfs-
  tools hook does not dereference symlinks. As the driver is actually
  loaded from the initramfs, the firmware is missing for the lifetime of
  the boot, which means that the GPU cannot enter its lowest available
  power states plus some hotplugging scenarios are broken. This all
  manifests itself as such in dmesg:

  [0.728803] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1.bin failed with error -2
  [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to 
load firmware i915/skl_dmc_ver1.bin (0)

  [ Test Case ]

  After the fix has been applied and the initrd regenerates, the
  firmware should load successfully after a reboot.

  [ Regression Potential ]

  Unlikely, as the fix is part of Ubuntu since Wily.

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

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

[Touch-packages] [Bug 1622041] Re: Mobile network denied

[Seth]

Are you guys still having this problem? If you are, please check out
this bug and comment:

https://bugs.launchpad.net/turbo/+bug/1592232

I originally thought that this was a USA only bug because of the
Cellular Band differences, but it looks like it affects people
everywhere.

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

Title:
  Mobile network denied

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  Device: Running Ubuntu 15.04 (OTA-13-rc) on the Meizu Pro 5.

  Description of problem: When I power on the phone, it connects to my
  mobile network for a brief period of time. I can send/receive SMS
  texts and make phone calls. After a few minutes though the mobile
  connection drops and the mobile status in the pull-down panel shows
  "Denied". It is then no longer possible to place calls or send/receive
  SMS texts.

  This issue started happening immediately following the upgrade from
  Ubuntu 15.04 (r-14) to the new OTA-13-rc upgrade which became
  available at the start of September.

  I have another phone running Android on the same network which is
  running smoothly, no connection issues.

  I suspect this is more than an indication issue, from what I've read
  the dropped mobile connection may be a software/firmware problem, but
  I haven't been able to find a location/project more suitable where
  this bug can be filed. My apologies.

  My phone's syslog file is downloadable from the link below. The
  problem occurs on September 9th between 19:00 and 20:00.
  http://resonatingmedia.com/logs/syslog.txt

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

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

[Touch-packages] [Bug 1622041] Re: Mobile network denied

[Launchpad Bug Tracker]

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

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

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

Title:
  Mobile network denied

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  Device: Running Ubuntu 15.04 (OTA-13-rc) on the Meizu Pro 5.

  Description of problem: When I power on the phone, it connects to my
  mobile network for a brief period of time. I can send/receive SMS
  texts and make phone calls. After a few minutes though the mobile
  connection drops and the mobile status in the pull-down panel shows
  "Denied". It is then no longer possible to place calls or send/receive
  SMS texts.

  This issue started happening immediately following the upgrade from
  Ubuntu 15.04 (r-14) to the new OTA-13-rc upgrade which became
  available at the start of September.

  I have another phone running Android on the same network which is
  running smoothly, no connection issues.

  I suspect this is more than an indication issue, from what I've read
  the dropped mobile connection may be a software/firmware problem, but
  I haven't been able to find a location/project more suitable where
  this bug can be filed. My apologies.

  My phone's syslog file is downloadable from the link below. The
  problem occurs on September 9th between 19:00 and 20:00.
  http://resonatingmedia.com/logs/syslog.txt

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

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

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

[LocutusOfBorg]

Hi Michael, I mean this change
https://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?id=17ee2def5d1b193f63fc378eda32d1bc9ead73cb

but you are right, I commented on the wrong bug report. silly me

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1650574] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess instaliran post-installation skripta returned error exit status 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: fontconfig (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  subprocess instaliran post-installation skripta returned error exit
  status 1

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  N/A

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Fri Dec 16 15:39:38 2016
  ErrorMessage: subprocess instaliran post-installation skripta returned error 
exit status 1
  InstallationDate: Installed on 2016-11-26 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
subprocess instaliran post-installation skripta returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Jason Gerard DeRose]

Mathieu,

Okay, just finished testing with xenial-proposed, no issues found.

Things are working as expected for my use-case (with no adjustments on
my end), so at least for the corners that my particular use-cases
covers, this proposed package seems regression free.

I tested PXE booting into a "diskless" read-only Ubuntu server
environment (using syslinux as the bootloader). Tested in both BIOS and
UEFI mode.

Sorry it took me a bit to do this follow-up testing!

Thanks!

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
   X / Y
  [+]/[ ] MAAS on IPv6-only network
  [+]/[ ] MAAS on IPv4-only network
  [+]/[ ] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[ ] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

To 

[Touch-packages] [Bug 1527843] Re: systemd-logind failed to enable subscription: launch helper exited with unknown return code 1

[Sergey Kruglov]

I deleted Bluеman, but the system will not boot normally. At boot time,
offers to enter into emergency mod! When loading upstart mode, the
system boots in console mode tty1.

my syslog


** Attachment added: "syslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1527843/+attachment/4792395/+files/syslog.txt

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

Title:
  systemd-logind failed to enable subscription: launch helper exited
  with unknown return code 1

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Wily:
  Expired

Bug description:
  Started my machine succesfully at night and the next morning the screen is 
blank/black and no GUI available.
  Switching to TTY1 i got after the login these messages:

  [31989] systemd-logind[4272]: Failed to enable subscription: Launch helper 
exited with unknown return code 1
  [31989] systemd-logind[4272]: Failed to fully start up daemon: Input/output 
error

  The much bigger problem is:
  PC does *not* start with normal boot options, i have to choose manually the 
upstart option in GRUB2.
  #1527806

  It is a fresh installed Xubuntu 15.10, all packages installed via
  Synaptic or CLI.

  
  Xubuntu 15.10

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[LaMont Jones]

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
   X / Y
- [+]/[+] MAAS on IPv6-only network
- [+]/[+] MAAS on IPv4-only network
- [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
- [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
+ [+]/[ ] MAAS on IPv6-only network
+ [+]/[ ] MAAS on IPv4-only network
+ [+]/[ ] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
+ [+]/[ ] MAAS booting IPv6 on dual-stack network (with and without dhcp4)
  
  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related 

[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

[Sneetsher]

Almost forget, Thank you very much for you help.

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  New

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

[Sneetsher]

Yeah, it does work as expected now. After:

chmod +x /home/sneetsher/.local
chmod +x /home/sneetsher/.local/share

I was working in real machine. I just checked 3 fresh installed
VirtualBox machines

14.04 0755
16.04 0700
16.10 0755

Anyway, this seems only for 16.04.

It is better to get that package back-ported, or may be more convenient
putting a note about those stable PPA's as alternative way to install
the edge release. To save users from falling in same pit.

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  New

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1650591] Re: package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již nainstalován a zkonfigurován

[Julian Andres Klode]

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

** This bug has been marked a duplicate of bug 1649959
   unattended upgrade of apt kills running apt-daily job

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

Title:
  package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již
  nainstalován a zkonfigurován

Status in apt package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   apt:amd64: Configure
   apt-utils:amd64: Install
   linux-tools-4.8.0-30-lowlatency:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Dec 14 21:19:25 2016
  DpkgTerminalLog:
   dpkg: chyba při zpracovávání balíku apt (--configure):
balík apt je již nainstalován a zkonfigurován
  ErrorMessage: balík apt je již nainstalován a zkonfigurován
  InstallationDate: Installed on 2016-10-08 (69 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.2ubuntu0.1
  SourcePackage: apt
  Title: package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již 
nainstalován a zkonfigurován
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (57 days ago)

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

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

[Touch-packages] [Bug 1479054] Re: Shuffle and repeat buttons pressed state does not visually differ from unpressed state

[Amr Ibrahim]

I'm also affected.

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

Title:
  Shuffle and repeat buttons pressed state does not visually differ from
  unpressed state

Status in rhythmbox package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in rhythmbox source package in Xenial:
  Invalid
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  In the default Ubuntu theme, the pressed/activated and deactivated
  button states are very similar and hard to differ. It is therefore
  hard to tell from the first look, if the shuffle is enabled or not. I
  am attaching the screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: rhythmbox 3.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic i686
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Jul 28 18:47:08 2015
  InstallationDate: Installed on 2013-08-17 (710 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to vivid on 2015-05-02 (87 days ago)

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

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

[Touch-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Committed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

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

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

[Touch-packages] [Bug 1650591] [NEW] package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již nainstalován a zkonfigurován

[Jan Urbánek]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: apt 1.3.2ubuntu0.1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering:
 apt:amd64: Configure
 apt-utils:amd64: Install
 linux-tools-4.8.0-30-lowlatency:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Dec 14 21:19:25 2016
DpkgTerminalLog:
 dpkg: chyba při zpracovávání balíku apt (--configure):
  balík apt je již nainstalován a zkonfigurován
ErrorMessage: balík apt je již nainstalován a zkonfigurován
InstallationDate: Installed on 2016-10-08 (69 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.2ubuntu0.1
SourcePackage: apt
Title: package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již 
nainstalován a zkonfigurován
UpgradeStatus: Upgraded to yakkety on 2016-10-20 (57 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již
  nainstalován a zkonfigurován

Status in apt package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   apt:amd64: Configure
   apt-utils:amd64: Install
   linux-tools-4.8.0-30-lowlatency:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Dec 14 21:19:25 2016
  DpkgTerminalLog:
   dpkg: chyba při zpracovávání balíku apt (--configure):
balík apt je již nainstalován a zkonfigurován
  ErrorMessage: balík apt je již nainstalován a zkonfigurován
  InstallationDate: Installed on 2016-10-08 (69 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.2ubuntu0.1
  SourcePackage: apt
  Title: package apt 1.3.2ubuntu0.1 failed to install/upgrade: balík apt je již 
nainstalován a zkonfigurován
  UpgradeStatus: Upgraded to yakkety on 2016-10-20 (57 days ago)

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

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

[Touch-packages] [Bug 1592427] Re: I can't disable proposed updates

[ajgreeny]

Just noticed the same thing in my Xubuntu 16.04.
I do not recall enabling proposed at all, so I'm baffled.

I have now removed the proposed.list and proposed.list.save from
/etc/apt/sources.list.d folder by commenting the files with a # and will
see what that does.

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

Title:
  I can't disable proposed updates

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Hi!!

  Accidentally I've enabled proposed updates in development section but
  now I can't disable it. I've rebooted the laptop but the issue isn't
  fixed.

  
  Regards!!

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

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

[Touch-packages] [Bug 1592427] Re: I can't disable proposed updates

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  I can't disable proposed updates

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Hi!!

  Accidentally I've enabled proposed updates in development section but
  now I can't disable it. I've rebooted the laptop but the issue isn't
  fixed.

  
  Regards!!

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

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

[Touch-packages] [Bug 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

[Benjamin Bach]

Question:

The release notes state: "Use ast.literal_eval() instead of the generic
eval(), to prevent arbitrary code execution from malicious .crash files"

The change should be in ui.py in this revision:

http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/3114

Just to be clear: How does "self.offer_restart = True" avoid generic
"eval()" and use "ast.literal_eval()" instead?

Does this also mean that there are still situations where "eval()" is
called? And why? This always leads to security issues, it's just a
matter of time.

Thanks for fixing it quickly.

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Released

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

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

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

[Touch-packages] [Bug 1650574] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess instaliran post-installation skripta returned error exit status 1

[Nvtv15]

Public bug reported:

N/A

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
Date: Fri Dec 16 15:39:38 2016
ErrorMessage: subprocess instaliran post-installation skripta returned error 
exit status 1
InstallationDate: Installed on 2016-11-26 (19 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
subprocess instaliran post-installation skripta returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  subprocess instaliran post-installation skripta returned error exit
  status 1

Status in fontconfig package in Ubuntu:
  New

Bug description:
  N/A

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Fri Dec 16 15:39:38 2016
  ErrorMessage: subprocess instaliran post-installation skripta returned error 
exit status 1
  InstallationDate: Installed on 2016-11-26 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
subprocess instaliran post-installation skripta returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)

[Geokimbo]

Yes. On a Dell t610. Same symptoms as above. Soundcard works fine on
CentOS 6 live so hardware is OK

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

Title:
  No sound on ASUS Xonar DGX Soundcard (16.04)

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Hello,
  On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), 
Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. 
Tested with the app to test speakers, Firefox, VLC, and checked with 
pavucontrol, the progress bar indicate that a sound is played on the card, but 
no sound on the speakers.

  I report this bug because it works on the same version with the
  integrated card of my motherboard. (ASUS H87-PLUS)

  On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all
  defaults params)

  The speakers connected are the Logitech Z9600 (by 3 jacks), and I
  precise that they are correctly plugged in, etc..., it works when I
  connect it to the integrated sound card of my motherboard (and if I
  use Ubuntu 14.04 LTS)

  I don't know if it's a normal development bug, but in doubt I report it.
  Thank you,
  Valentin Crône

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

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

[Touch-packages] [Bug 1650570] [NEW] package python3-problem-report 2.20.1-0ubuntu2.4 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Augusto César]

Public bug reported:

I don't know about this, but i would like to help the commmunity.
Thanks.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-problem-report 2.20.1-0ubuntu2.4
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Fri Dec 16 12:29:57 2016
Dependencies:
 
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: apport
Title: package python3-problem-report 2.20.1-0ubuntu2.4 failed to 
install/upgrade: sub-processo script post-installation instalado retornou 
estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python3-problem-report 2.20.1-0ubuntu2.4 failed to
  install/upgrade: sub-processo script post-installation instalado
  retornou estado de saída de erro 1

Status in apport package in Ubuntu:
  New

Bug description:
  I don't know about this, but i would like to help the commmunity.
  Thanks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-problem-report 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Dec 16 12:29:57 2016
  Dependencies:
   
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apport
  Title: package python3-problem-report 2.20.1-0ubuntu2.4 failed to 
install/upgrade: sub-processo script post-installation instalado retornou 
estado de saída de erro 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/1650570/+subscriptions

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Laurent Perrin]

Hello,

I just tested the package from Xenial proposed repository and it solved
the issue for us.

Here is the version of the package dbus: 1.10.6-1ubuntu3.2

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  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
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

-- 

[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

[Dimitri John Ledkov]

** Changed in: util-linux (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  In Progress
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  Triaged
Status in glibc source package in Yakkety:
  Fix Released
Status in util-linux source package in Yakkety:
  Triaged

Bug description:
  [Testcase]
  * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- 
--help
  Expected result:
/usr/sbin/mkinitramfs: unrecognized option '--help'
 --
Exit code 1
  Current result:
Segmentation fault
Exit code 139.

  There are two bugs in play here. glibc bug was fixed, and util-linux
  bug needs an upload still.

  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d ,
  s1@entry=0x2e6575634a500a6a ,
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40,
  optstring=0x20030 , longopts=,
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=,
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=,
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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

[Touch-packages] [Bug 1650555] [NEW] nsswitch.conf configuration doesn't work with mdns hosts

[Alberto Donato]

Public bug reported:

On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts
doesn't work anymore (it used to in xenial)

I can resolve names with avahi-resolve but ssh,ping,etc. fail to
resolve.

After some digging I found out that what's causing it is the "resolve"
option in /etc/nsswitch.conf:

hosts:  files resolve [!UNAVAIL=return] mdns4_minimal
[NOTFOUND=return] dns

Changing it to

hosts:  files mdns4_minimal [NOTFOUND=return] dns

(as it was on xenial) makes mDNS work again.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libnss-resolve 231-9ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Dec 16 15:16:38 2016
InstallationDate: Installed on 2016-10-22 (54 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  nsswitch.conf configuration doesn't work with mdns hosts

Status in systemd package in Ubuntu:
  New

Bug description:
  On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts
  doesn't work anymore (it used to in xenial)

  I can resolve names with avahi-resolve but ssh,ping,etc. fail to
  resolve.

  After some digging I found out that what's causing it is the "resolve"
  option in /etc/nsswitch.conf:

  hosts:  files resolve [!UNAVAIL=return] mdns4_minimal
  [NOTFOUND=return] dns

  Changing it to

  hosts:  files mdns4_minimal [NOTFOUND=return] dns

  (as it was on xenial) makes mDNS work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec 16 15:16:38 2016
  InstallationDate: Installed on 2016-10-22 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

[Christian Brauner]

Right, the cpuset bug is gone which was your main problem. Now the
only thing left to do should be:

chmod +x /home/sneetsher/.local

Please try again and report back. :)

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  New

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Pat McGowan]

Tested with version 1.10.6-1ubuntu3.2 of the packages dbus dbus-x11
libdbus-1-3 libdbus-1-3:i386 libdbus-1-dev dbus-user-session from
xenial-proposed


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  In Progress
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

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

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

[Touch-packages] [Bug 1650523] Re: Plugin "SNES-SPC700 Sound File Data decoder" in gstreamer1.0-plugins-bad may have security vulnerability

[Tyler Hicks]

We've released security updates to address this issue for all supported
Ubuntu releases:

https://launchpad.net/ubuntu/+source/game-music-emu/0.6.0-3ubuntu0.16.10.1
https://launchpad.net/ubuntu/+source/game-music-emu/0.6.0-3ubuntu0.16.04.1
https://launchpad.net/ubuntu/+source/game-music-emu/0.5.5-2ubuntu0.14.04.1
https://launchpad.net/ubuntu/+source/game-music-emu/0.5.5-2ubuntu0.12.04.1

Please make sure that you've applied all security updates. Thanks!

** Information type changed from Private Security to Public Security

** Also affects: game-music-emu (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Invalid

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

** Changed in: game-music-emu (Ubuntu)
   Status: New => Fix Released

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

Title:
  Plugin "SNES-SPC700 Sound File Data decoder" in gstreamer1.0-plugins-
  bad may have security vulnerability

Status in game-music-emu package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Steps:
  1. Ubuntu 16.04.1 LTS
  2. Trying to play xcalc_ubuntu_16.04_libc_2.23-0ubuntu3.spc file from this 
blog post ( 
https://scarybeastsecurity.blogspot.ru/2016/12/redux-compromising-linux-using-snes.html
 ) and this video ( https://www.youtube.com/watch?v=wrCLoem6ggM ).
  3. Totem found required plugin for playing "SNES-SPC700 Sound File Data 
decoder" which is in gstreamer1.0-plugins-bad.
  4. xcalc does not launched on music play or by Nautilus launch.

  Ubuntu security team, please read blog post (see above link) and
  confirm (and fix) or refute zero-day vulnerability.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-plugins-bad 1.8.2-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Fri Dec 16 12:03:27 2016
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-bad1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/game-music-emu/+bug/1650523/+subscriptions

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

[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions

[Sneetsher]

It couldn't start but got a different error messages. Please, here is
the attached log & commands output.

** Attachment added: "lxc_debug_info_after_installing_lxcfs2.0.5.zip"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+attachment/4792357/+files/lxc_debug_info_after_installing_lxcfs2.0.5.zip

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

Title:
  lxc-start fails to start a unprivileged container  - cgroup
  permissions

Status in lxc package in Ubuntu:
  New

Bug description:
  I was following this simple getting start tutorial:

  https://linuxcontainers.org/lxc/getting-started/

  Created using:

  lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64

  But it always fails at:

  lxc-start -n ci -d

  I even tried another Ubuntu 14.04 but didn't work too for same
  problem.

  Below the debug log got from running `lxc-start`

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 13 14:05:44 2016
  InstallationDate: Installed on 2016-07-09 (156 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1650546] [NEW] package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[jcpradilla]

Public bug reported:



ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
Uname: Linux 4.8.0-30-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Fri Dec 16 01:00:55 2016
DuplicateSignature:
 package:url-dispatcher:amd64:0.1+16.10.20160816.1-0ubuntu1
 Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package click (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-05-23 (206 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.2ubuntu0.1
SourcePackage: url-dispatcher
Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: url-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri Dec 16 01:00:55 2016
  DuplicateSignature:
   package:url-dispatcher:amd64:0.1+16.10.20160816.1-0ubuntu1
   Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package click (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-23 (206 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.2ubuntu0.1
  SourcePackage: url-dispatcher
  Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1618900] Please test proposed package

[Timo Aaltonen]

Hello Guillaume, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.90ubuntu0.3 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1618900

Title:
  [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  There are some race conditions in unattended-upgrades when it is used in 
shutdown mode. It is possible that the network has already been brought down or 
for a local file system, like /var/, to be unmounted before the 
unattended-upgrades script is run.  This then causes the updates not to be 
installed thereby making systems less secure - if security updates are enabled.

  [Test Case]
  Because this is a race condition, I haven't actually been able to recreate 
the bug.  However, the fix is straightforward and testing for regressions 
should be sufficient.

  1) On a freshly installed system.
  2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that 
  Unattended-Upgrade::InstallOnShutdown "true"; is not commented out.
  3) Reboot and watch updates being installed
  4) Verify updates were installed by reviewing 
/var/log/unattended-upgrades/unattended-upgrades.log
  5) Uncomment -updates in 50unattended-upgrades

  Repeats steps 3 and 4 again. There isn't any need to run unattended-
  upgrades in *not* shutdown mode because we have only modified the
  systemd service file.

  [Regression Potential]
  There is little chance of a regression, but because of the change (and this 
feature now working better) its possible the shutdown process will take longer 
and surprise users.

  Original Description
  

  Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we 
encounter the following systemd dependencies issues :
  - The network is often down when unattended-upgrades is running, so packages 
can not be downloaded (can be mitigated by using 
APT::Periodic::Download-Upgradeable-Packages "1";) :
  => ERROR An error occurred: 'Could not resolve host: .fr'
  => ERROR The URI 
'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb'
 failed to download, aborting
  - Important mountpoints like /boot are unmounted before unattended-upgrades 
is running, so newer kernels can not be installed properly (ramdisk and grub 
configuration can not be generated)

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

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

[Touch-packages] [Bug 1618900] Re: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

[Timo Aaltonen]

Hello Guillaume, or anyone else affected,

Accepted unattended-upgrades into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.92ubuntu1.2 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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: unattended-upgrades (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  There are some race conditions in unattended-upgrades when it is used in 
shutdown mode. It is possible that the network has already been brought down or 
for a local file system, like /var/, to be unmounted before the 
unattended-upgrades script is run.  This then causes the updates not to be 
installed thereby making systems less secure - if security updates are enabled.

  [Test Case]
  Because this is a race condition, I haven't actually been able to recreate 
the bug.  However, the fix is straightforward and testing for regressions 
should be sufficient.

  1) On a freshly installed system.
  2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that 
  Unattended-Upgrade::InstallOnShutdown "true"; is not commented out.
  3) Reboot and watch updates being installed
  4) Verify updates were installed by reviewing 
/var/log/unattended-upgrades/unattended-upgrades.log
  5) Uncomment -updates in 50unattended-upgrades

  Repeats steps 3 and 4 again. There isn't any need to run unattended-
  upgrades in *not* shutdown mode because we have only modified the
  systemd service file.

  [Regression Potential]
  There is little chance of a regression, but because of the change (and this 
feature now working better) its possible the shutdown process will take longer 
and surprise users.

  Original Description
  

  Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we 
encounter the following systemd dependencies issues :
  - The network is often down when unattended-upgrades is running, so packages 
can not be downloaded (can be mitigated by using 
APT::Periodic::Download-Upgradeable-Packages "1";) :
  => ERROR An error occurred: 'Could not resolve host: .fr'
  => ERROR The URI 
'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb'
 failed to download, aborting
  - Important mountpoints like /boot are unmounted before unattended-upgrades 
is running, so newer kernels can not be installed properly (ramdisk and grub 
configuration can not be generated)

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

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

[Touch-packages] [Bug 1648938] Re: Update tracker to 1.10.2

[Timo Aaltonen]

Hello Jeremy, or anyone else affected,

Accepted tracker into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/tracker/1.10.2-0ubuntu0.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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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: tracker (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Update tracker to 1.10.2

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  =
  This update includes the new bugfix releases 1.10.1 and 1.10.2
  https://git.gnome.org/browse/tracker/tree/NEWS?h=tracker-1.10
  https://git.gnome.org/browse/tracker/log?h=tracker-1.10

  The major change is that the tracker extractor is now confined by
  libseccomp for better security (LP: #1648921)

  Test Case
  =
  I recommend testing with Ubuntu GNOME 16.10 since it includes tracker.
  1. After installing the update, log out and log back in just to make sure 
you're running the updated tracker
  2. Download some pictures or music files to an indexed folder (~/Downloads, 
~/Music, ~/Pictures are good)
  3. Wait a few moments and see if the files show up in the GNOME Music app, 
the GNOME Photos app, and/or the GNOME Shell Activities Overview when searching 
for that filename.
  4. You can also look for any tracker errors to show up in the GNOME Logs app 
(gnome-logs is a frontend to the systemd journal)

  Regression Potential
  
  Low. Ensure that tracker still works.

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

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

[Touch-packages] [Bug 1648921] Re: Sandbox the tracker extractor

[Timo Aaltonen]

Hello Jeremy, or anyone else affected,

Accepted tracker into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/tracker/1.10.2-0ubuntu0.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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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: tracker (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Sandbox the tracker extractor

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Xenial:
  New
Status in tracker source package in Yakkety:
  Fix Committed

Bug description:
  * SECURITY UPDATE: extractor now runs in a sandbox confined by libseccomp
  - extractor's filesystem and network access is limited to being read and
    local only (LP: #1648921)
  - No CVE number

  The tracker developers have recently confined their extractor to
  attempt to make tracker more resilient to attacks, especially
  involving flaws in gstreamer parsers.

  There is no CVE number assigned to this issue.

  https://lwn.net/Articles/708196/
  
https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html

  The gstreamer security fixes are being handled separately. See bug
  1619600

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

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

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

[Michael Thayer]

Gianfranco, now I am interested - could you point me to the change you
mean?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

[Peter Würtz]

Still not fixed after almost 5 years. Problem and solution are well
known.

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

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

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

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

[Alexander Stohr]

PS:
based on x11 log data (/var/log/Xorg.0.log) i tried out this:

sudo cat /dev/input/event6 | od -x

when moving the mouse new data arrived.
but no data arrived when hitting any button or when turning the mouse wheel.

checking other such input devices did not provide any
(useable/related/promising) result.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  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: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

[Alexandre Payet]

** Summary changed:

- Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
+ Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

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

Title:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

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

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

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

[Alexander Stohr]

i am running a fresh install of Ubunutu 16.04.1 i386 on top of Virtual Box 
5.1.6 using Win7 i386 as host.
(with FreeDos as a VB-client on the same system i have the mouse just working.)
the hosting machine is accessed via RDP.

tests with console switching did not show any improvement.
checks with mouse or touchpad alternating did not show any improvement.

the mouse moves nice and tooltips or button highlights do appear.
just none of the buttons shows any reaction to my presses, neither from the 
touch pad nor from the wired red-light based wheel mouse.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  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: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1650536] [NEW] wrong behaviour of interface - audio specific

[jacopo.tolja]

Public bug reported:

report
1 no audio on audio jack
2 in trying to fix after testing sound with the audio test Right and Left i 
changed the stereo to 5-1 surround option available in the test windows
3 this caused to remove from the audio setting windows all output devices ( now 
is empty) 
Audio stopped working completely and the volume in the top bar had the x and I 
cannot activate.
is gray

4 I just update the system with regular updates and the sound now work
on the browser but the volume still have an x and is greyed but the
Audio is  active!! I can hear sound on video on  youtube and and play
music but I cannot adjust volume.

5 try to activate pavucontrol but get message " establishing connection
with pulseaudio please wait " but no responce

system information:
Linux jaki-XPS-13-9350 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
 suppose to be one of the certified laptop

Regarding the jack still do not work and when inserted the jack the
audio from internal speaker stop but there is no output. Dell changed
the motherboard but the problem persisted, tried windows 10 on a live
usb memory and sound worked out of the jack.

willing to let someone to log on the system and check remotely

jaki@jaki-XPS-13-9350:~$ xprop WM_CLASS
WM_CLASS(STRING) = "unity-control-center", "Unity-control-center"

unity-control-center:
  Installato: 15.04.0+16.04.20160705-0ubuntu1
  Candidato:  15.04.0+16.04.20160705-0ubuntu1
  Tabella versione:
 *** 15.04.0+16.04.20160705-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 15.04.0+16.04.20160413-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
jaki@jaki-XPS-13-9350:~$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Fri Dec 16 13:29:44 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2016-06-25 (174 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to xenial on 2016-09-07 (99 days ago)
dmi.bios.date: 06/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.4
dmi.board.name: 0H67KH
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  wrong behaviour of interface - audio specific

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  report
  1 no audio on audio jack
  2 in trying to fix after testing sound with the audio test Right and Left i 
changed the stereo to 5-1 surround option available in the test windows
  3 this caused to remove from the audio setting windows all output devices ( 
now is empty) 
  Audio stopped working completely and the volume in the top bar had the x and 
I cannot activate.
  is gray

  4 I just update the system with regular updates and the sound now work
  on the browser but the volume still have an x and is greyed but the
  Audio is  active!! I can hear sound on video on  youtube and and play
  music but I cannot adjust volume.

  5 try to activate pavucontrol but get message " establishing
  connection with pulseaudio please wait " but no responce

  system information:
  Linux jaki-XPS-13-9350 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
   suppose to be one of the certified laptop

  Regarding the jack still do not work and when inserted the jack the
  audio from internal speaker stop but there is no output. Dell changed
  the motherboard but the problem persisted, tried windows 10 on a live
  usb memory and sound worked out of the jack.

  willing to let 

[Touch-packages] [Bug 1649729] Re: ntpd startup failures under xenial

[Robie Basak]

Please see: https://lists.ubuntu.com/archives/ubuntu-
devel/2016-August/039484.html

Summary: in Ubuntu, we don't expect to use ntpdate any more. We're
leaving bugs in ntpdate packaging behind, on the basis that ntpdate no
longer needs to be installed by default.

Can you fix the problem by removing the ntpdate package?

Is there anything unique about your configuration that means that you're
hitting this bug "by default"? How is it that you have ntpdate installed
in the first place? If you installed it yourself, why did you install
it?

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

Title:
  ntpd startup failures under xenial

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  I have a system running 16.04.1 with multiple interfaces configured
  via /etc/network/interfaces.  Following a restart, ntpd will often be
  found not running, despite being installed and configured.

  syslog suggests ntpd is being repeatedly stopped and restarted within
  seconds.

  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING

  My current assumption is that this is the work of /etc/network/if-
  up.d/ntpdate being run on several interfaces nearly simultaneously.
  The rapid stop/start cycle of the daemon appears to trip up the port
  binding, and eventually cause ntpd to become unhappy and wind up
  stopped.

  Manually restarting ntpd (or even running /etc/network/if-
  up.d/ntpdate) outside of interface up/down time properly brings up
  ntpd.  It doesn't appear to be a configuration issue as such.

  Further, running  /etc/network/if-up.d/ntpdate from bash several times
  in rapid succession also produces the 'missing ntpd' behavior, outside
  of the context of any interface activity.

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

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

[Touch-packages] [Bug 1575354] Re: Connecting to VPN times out after 25 seconds if login credentials not entered

[Jeremy Hoyland]

I have also hit this bug in latest version of Linux Mint 18. I can
confirm that the timeout has somehow reverted to 25 seconds, while
previous versions of network manager allowed much longer.

Note that the timeout is overall from the moment of the first POST to
the VPN address.

Our corporate VPN gateway redirects to the nearest VPN available.
Assigning this new redirect takes almost all of the 25 seconds.
Occasionally one can type in username/password and get in under the 25
sec bar. If the 25 seconds started from the actual VPN negotiation it
would work just fine.

Using the command:
sudo openconnect -u myusername mycorporate.accessaddress.com

..allows me to launch my vpn session manually. It also prints out the
redirect address, and I can then create a new network-manager vpn
connection with this address, which connects much faster. I am using
this as a workaround for the time being.

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

Title:
  Connecting to VPN times out after 25 seconds if login credentials not
  entered

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connecting to OpenConnect VPN through the Gnome GUI fails because
  NetworkManager times out while requesting credentials through the GUI
  form in Ubuntu 16.04.

  It worked (is working on other computers I'm working on) fine from
  Ubuntu 12.04-15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openconnect 1.0.2-1build1
  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: GNOME
  Date: Tue Apr 26 22:06:41 2016
  SourcePackage: network-manager-openconnect
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

[Dimitri John Ledkov]

glibc (2.24-3ubuntu1) yakkety; urgency=medium

  * Merge with 2.24 from Debian sid, bringing in minor packaging changes and
upstream updates, including the security fix for CVE-2016-6323 on ARMv7.
  * debian/patches/ubuntu/local-altlocaledir.diff: Updated to latest version
from Martin that limits scope to LC_MESSAGES, fixing segv (LP: #1577460)
  * debian/testsuite-xfail-debian.mk: Allow nptl/tst-signal6 to fail on ARM.

 -- Adam Conrad   Wed, 05 Oct 2016 14:25:57 -0600

** Description changed:

+ [Testcase]
+ * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- 
--help
+ Expected result:
+   /usr/sbin/mkinitramfs: unrecognized option '--help'
+--
+   Exit code 1
+ Current result:
+   Segmentation fault
+   Exit code 139.
+ 
+ There are two bugs in play here. glibc bug was fixed, and util-linux bug
+ needs an upload still.
+ 
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#
  
  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:
  
  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'
  
  Following call-stack occured (creates coredump):
  
- #0  __strncmp_c (s1=0x2e6575634a500a6d , 
- s1@entry=0x2e6575634a500a6a , 
- s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
- #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
- optstring=0x20030 , longopts=, 
- longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
- #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
- optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
- at getopt.c:1175
- #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
- long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
+ #0  __strncmp_c (s1=0x2e6575634a500a6d ,
+ s1@entry=0x2e6575634a500a6a ,
+ s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
+ #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40,
+ optstring=0x20030 , longopts=,
+ longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
+ #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=,
+ optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
+ at getopt.c:1175
+ #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=,
+ long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

** Changed in: util-linux (Ubuntu)
   Status: New => Triaged

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => High

** Changed in: util-linux (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: util-linux (Ubuntu)
Milestone: None => ubuntu-17.01

** Changed in: util-linux (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: util-linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: util-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: util-linux (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.2

** Also affects: util-linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: glibc (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: util-linux (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: util-linux (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: util-linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: util-linux (Ubuntu Yakkety)
Milestone: None => yakkety-updates

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  In Progress
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Triaged
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  Triaged
Status in glibc source package in Yakkety:
  Fix Released
Status in util-linux source package in Yakkety:
  Triaged

Bug description:
  [Testcase]
  * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- 
--help
  Expected result:
/usr/sbin/mkinitramfs: unrecognized option '--help'
 --
Exit code 1
  Current result:
Segmentation fault
Exit code 139.

  There are two bugs in play here. glibc bug was fixed, and util-linux
  bug needs an upload still.

  Problem Description
  ==