date:20151219

@xtrchessreal, yes, alt+SysRq+ REISUB didn't work. It did help me out in
some other strange glitches. I think in this case, the USB drivers were
already shut off, and since I have a USB keyborad, it was unresponsive.
Maybe an analog / laptop keyboard would have worked.

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 483086] Re: Incorrect per-target ?= variable affectations

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

** Changed in: make-dfsg (Ubuntu)
   Status: New => Confirmed

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

Title:
  Incorrect per-target ?= variable affectations

Status in make-dfsg package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: make

  I am running 9.10 on x86_64 (updated yesterday), make 3.81-6.

  The following Makefile:
  -
  target1: OPTVAR?=/usr/local
  target1:
echo "Value for $@ '$(OPTVAR)'."

  target2:
echo "Value for $@ is '$(OPTVAR)'."
  -

  Make seems to behave badly with such a Makefile:

  shell> make OPTVAR=x target1 target2
  echo "Value for target1 '�!M'."
  Value for target1 '�!M'.
  echo "Value for target2 is '�!M'."
  Value for target2 is '�!M'.

  Whereas it has the expected behavior when passing OPTVAR through the
  environment:

  shell> env OPTVAR=x make target1 target2
  echo "Value for target1 'x'."
  Value for target1 'x'.
  echo "Value for target2 is 'x'."
  Value for target2 is 'x'.

  It also behaves as expected when OPTVAR is left undefined:

  shell> make target1 target2
  echo "Value for target1 '/usr/local'."
  Value for target1 '/usr/local'.
  echo "Value for target2 is ''."
  Value for target2 is ''.

  I believe this is a regression from jaunty.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Nov 15 14:57:25 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: make 3.81-6
  ProcEnviron:
   SHELL=/bin/zsh
   PATH=(custom, user)
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: make-dfsg
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

@xtrchessreal, if Chromium background processes are the culprit on your
platform, this would mean we are suffering from different issues.
Indeed, my symptoms are actually a bit different from what's described
in the original bug report -- I'm seeing the "Reached target Shutdown"
when I actually try to shut down, not reboot, and the system doesn't
fully shut down. My reboot works fine.

You can try to disable Chromium background processes from running in the
background when Chromium is shut down (settings --> Show advanced
settings --> uncheck "Continue running ... "), and close chromium before
you reboot.

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1527854] Re: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Installing for testing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jari   2054 F pulseaudio
   /dev/snd/controlC1:  jari   2054 F pulseaudio
   /dev/snd/controlC0:  jari   2054 F pulseaudio
  Date: Sat Dec 19 12:46:13 2015
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=1c0fb703-2b9d-4d9c-a5b8-ee59a3371e47
  InstallationDate: Installed on 2013-09-29 (811 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUSTeK Computer INC. V-P7H55E
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=0e8139a5-d931-44dc-b301-550b79ed3369 ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2015-12-19 (0 days ago)
  dmi.bios.date: 07/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P7H55E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/16/2010:svnASUSTeKComputerINC.:pnV-P7H55E:pvrX.0x:rvnASUSTeKComputerINC.:rnV-P7H55E:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P7H55E
  dmi.product.version: X.0x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1527854] Re: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2015-12-19 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1527854

** Tags added: iso-testing

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

Title:
  package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Installing for testing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jari   2054 F pulseaudio
   /dev/snd/controlC1:  jari   2054 F pulseaudio
   /dev/snd/controlC0:  jari   2054 F pulseaudio
  Date: Sat Dec 19 12:46:13 2015
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=1c0fb703-2b9d-4d9c-a5b8-ee59a3371e47
  InstallationDate: Installed on 2013-09-29 (811 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUSTeK Computer INC. V-P7H55E
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=0e8139a5-d931-44dc-b301-550b79ed3369 ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2015-12-19 (0 days ago)
  dmi.bios.date: 07/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P7H55E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/16/2010:svnASUSTeKComputerINC.:pnV-P7H55E:pvrX.0x:rvnASUSTeKComputerINC.:rnV-P7H55E:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P7H55E
  dmi.product.version: X.0x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 207135] Re: pulseaudio uses too much CPU

2015-12-19 Thread Susan Cragin

This is still a problem for me. I open a wine application with sound and
it starts okay but within a minute or two pulseaudio usage goes up to
about 30% of CPU.

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

Title:
  pulseaudio uses too much CPU

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Pulseaudio uses between 6 and 8% of my CPU (AMD Athlon(tm) 64
  Processor 3500+) when I'm just listening music using Rhythmbox. Seems
  too much IMHO.

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

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

[Touch-packages] [Bug 483086] Re: Incorrect per-target ?= variable affectations

2015-12-19 Thread Gary Bishop

I should have added that I'm on 14.04 LTS and the make version is 3.81.

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

Title:
  Incorrect per-target ?= variable affectations

Status in make-dfsg package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: make

  I am running 9.10 on x86_64 (updated yesterday), make 3.81-6.

  The following Makefile:
  -
  target1: OPTVAR?=/usr/local
  target1:
echo "Value for $@ '$(OPTVAR)'."

  target2:
echo "Value for $@ is '$(OPTVAR)'."
  -

  Make seems to behave badly with such a Makefile:

  shell> make OPTVAR=x target1 target2
  echo "Value for target1 '�!M'."
  Value for target1 '�!M'.
  echo "Value for target2 is '�!M'."
  Value for target2 is '�!M'.

  Whereas it has the expected behavior when passing OPTVAR through the
  environment:

  shell> env OPTVAR=x make target1 target2
  echo "Value for target1 'x'."
  Value for target1 'x'.
  echo "Value for target2 is 'x'."
  Value for target2 is 'x'.

  It also behaves as expected when OPTVAR is left undefined:

  shell> make target1 target2
  echo "Value for target1 '/usr/local'."
  Value for target1 '/usr/local'.
  echo "Value for target2 is ''."
  Value for target2 is ''.

  I believe this is a regression from jaunty.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Nov 15 14:57:25 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: make 3.81-6
  ProcEnviron:
   SHELL=/bin/zsh
   PATH=(custom, user)
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: make-dfsg
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Touch-packages] [Bug 1527938] Re: Upstream fonts-droid -> fonts-droid-fallback

2015-12-19 Thread Gunnar Hjalmarsson

@Vasudev: It struck me that the package name change isn't quite
uncomplicated, since fonts-droid is shipped by default on all Ubuntu
installs. However, I suggest that we await Aron Xu's comments before
doing anything.

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

Title:
  Upstream fonts-droid -> fonts-droid-fallback

Status in fonts-android package in Ubuntu:
  New

Bug description:
  Upstream has moved the Droid Sans Fallback font from the fonts-droid
  package to a new fonts-droid-fallback package.

  http://anonscm.debian.org/cgit/pkg-fonts/fonts-android.git/

  It means that we'll need to change the package name in a bunch of
  seeds, and in pkg_depends.

  This will not be a problem as regards new installs, as far as I can
  tell, but I fear a problem when people upgrade from 14.04 or 15.10 to
  16.04, since there is no dummy package with the old name which depends
  on the new one.

  @Aron: How should we deal with this issue? One way, if Droid Sans
  Fallback will keep being the default Chinese font in 16.04, is to ask
  upstream to create a transitional dummy package.

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

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

[Touch-packages] [Bug 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)

2015-12-19 Thread Luke

This may also affect libreoffice. See:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1527053
https://bugs.launchpad.net/ubuntu-themes/+bug/1527910

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

Title:
  Ambiance & Radiance themes are missing a "background-color" for
  tooltip elements (needed for GTK3-enabled Firefox Nightly)

Status in One Hundred Papercuts:
  Confirmed
Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Firefox Nightlies recently became GTK3-enabled, and that uncovered an
  issue with Ubuntu's Ambiance & Radiance GTK3 themes.

  They're missing a "background-color" for the .tooltip {...} CSS rule
  in their config files. They have a "tooltip_bg_color" variable, which
  they use to set up a background-image (really a gradient), but there's
  no background-color.

  This causes problems for GTK3-enabled Firefox, because it reads back some 
system-colors by setting up a dummy tooltip and reading the 
(currently-not-useful) background-color and the foreground-color. Right now, 
this produces unreadable output (for the user) with 
white-text-on-a-white-background, as shown in this screenshot:
   https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351

  The solution is simple -- just add this one line to the ".tooltip" CSS rule 
in gtk-widgets.css:
 background-color: @tooltip_bg_color;

  For more details, see bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1187203

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: light-themes 14.04+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 24 17:35:25 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (67 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

2015-12-19 Thread xtrchessreal

My Ubuntu 15.04 is fresh installed using the frugal install method. Its a Sony
Vaio VGN-FW250j and the bios is locked out, which is why I had to use the
Frugal method. Its a dual boot system with Windows 7. The two share a Data
drive for storage only. I wish I knew how to capture the shutdown data.
I have not upgraded to 15.10 since someone confirmed its still doing it on that
as well. The one odd thing for me is I tried to use a different browser than
Chromium. I started using Firefox and the Target Reached Shutdown hang only
hangs for a few seconds and then shutsdown on its own. But every time I bring
up Chromium it hangs on shutdown or reboot and I have to use SYSRQ+alt+REISUB
to reboot then wait until its up again just so I can shutdown properly. So I
don't understand that and so far no one has been able to explain or repeat that
to confirm it. It is very repeatable for me.
My hunch is some background google app that is embedded with Chromium is the
culprit, at least in my case. It may just be the beginning of a chain of
events that happen to cause the hang but I don't know that because I can't
capture the shutdown data. I need a forensics tool.

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

Title:
reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
Confirmed

Bug description:
I rebooted my 15.04 system, and found it hanging indefinitely at the
plymouth shutdown screen. Hitting esc to reveal the console showed a
normal set of shutdown messages, ending with 'Reached target Shutdown'
(paraphrased from memory).

The system never rebooted on its own. I had to use SysRq to finish
the shutdown.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 13 11:53:10 2015
InstallationDate: Installed on 2010-09-24 (1723 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
MachineType: LENOVO 2306CTO
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET97WW (2.57 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

2015-12-19 Thread John Center

My Dell workstation is a fresh install of 15.04, also.  I'm having the
same problem.  I've attached some screen shots that show the last
messages typically seen after I try REISUB.

** Attachment added: "IMG_0765.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4537644/+files/IMG_0765.JPG

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

I have a hunch that this bug only occurs on systems upgraded from a previous 
Ubuntu version, perhaps with replacement of upstart with systemd, but not on 
fresh Ubuntu 15.04 or 15.10 installations.
Everyone who is affected: is there anyone who started having this problem on a 
fresh 15.04 or later installation? Please let us know within a week. This may 
shed insight onto how this bug may be reproduced.

I've changed status to 'Confirmed' since it looks like all the
information that could be provided has been provided. Developers and
enthusiasts: if there is anything else we can do to help diagnose this,
please let us know.

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 513168] Re: Printer options and other strings are not translatable

2015-12-19 Thread Pascal De Vuyst

system-config-printer has support for internationalized PPDs in 14.04
LTS

** Changed in: system-config-printer (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Printer options and other strings are not translatable

Status in Ubuntu Translations:
  Triaged
Status in foomatic-db package in Ubuntu:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in qt4-x11 package in Ubuntu:
  Triaged
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: system-config-printer

  1) Go to System->Administration->Print
  2) Select an already configured printer.
  3) Right click on it and select "Properties".
  4) Select "Policies" and you see that dropdown items are in English.
  5) Select "Printer options" and you see that all the items are in English.

  Affected releases:
  All supported releases are affected by this bug, even Lucid Lynx.

  Firefox printing support is affected too (it probably picks up from the same 
source)
  1) Open Firefox
  2) Go to File->Print...
  3) "Image Quality" and "Advanced" tabs content is in English.

  Many KDE apps are also affected
  1) Open any KDE application which can print anything, e.g. open an image in 
Gwenview.
  2) Go to File → Print.
  3) Click »Properties« ans select the »Advanced« tab. All printer options 
there are untranslated.

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

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

[Touch-packages] [Bug 1455916] Re: Xorg unexpectedly crashed

2015-12-19 Thread Stephane Lapie

Maybe a duplicate of
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764 (or at
least related ?)

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

Title:
  Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core:

[Touch-packages] [Bug 1527854] Re: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2015-12-19 Thread Jackson Doak

I believe i got the same or similar error trying to upgrade ubuntu 15.10
to 16.04 today. linux-image-4.3.0-2-generic fails to install, error 2. I
also have the nvidia drivers

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

Title:
  package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Installing for testing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jari   2054 F pulseaudio
   /dev/snd/controlC1:  jari   2054 F pulseaudio
   /dev/snd/controlC0:  jari   2054 F pulseaudio
  Date: Sat Dec 19 12:46:13 2015
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=1c0fb703-2b9d-4d9c-a5b8-ee59a3371e47
  InstallationDate: Installed on 2013-09-29 (811 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUSTeK Computer INC. V-P7H55E
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=0e8139a5-d931-44dc-b301-550b79ed3369 ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2015-12-19 (0 days ago)
  dmi.bios.date: 07/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P7H55E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/16/2010:svnASUSTeKComputerINC.:pnV-P7H55E:pvrX.0x:rvnASUSTeKComputerINC.:rnV-P7H55E:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P7H55E
  dmi.product.version: X.0x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1527938] [NEW] Upstream fonts-droid -> fonts-droid-fallback

2015-12-19 Thread Gunnar Hjalmarsson

Public bug reported:

Upstream has moved the Droid Sans Fallback font from the fonts-droid
package to a new fonts-droid-fallback package.

http://anonscm.debian.org/cgit/pkg-fonts/fonts-android.git/

It means that we'll need to change the package name in a bunch of seeds,
and in pkg_depends.

This will not be a problem as regards new installs, as far as I can
tell, but I fear a problem when people upgrade from 14.04 or 15.10 to
16.04, since there is no dummy package with the old name which depends
on the new one.

@Aron: How should we deal with this issue? One way, if Droid Sans
Fallback will keep being the default Chinese font in 16.04, is to ask
upstream to create a transitional dummy package.

** Affects: fonts-android (Ubuntu)
 Importance: High
 Status: New

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

Title:
  Upstream fonts-droid -> fonts-droid-fallback

Status in fonts-android package in Ubuntu:
  New

Bug description:
  Upstream has moved the Droid Sans Fallback font from the fonts-droid
  package to a new fonts-droid-fallback package.

  http://anonscm.debian.org/cgit/pkg-fonts/fonts-android.git/

  It means that we'll need to change the package name in a bunch of
  seeds, and in pkg_depends.

  This will not be a problem as regards new installs, as far as I can
  tell, but I fear a problem when people upgrade from 14.04 or 15.10 to
  16.04, since there is no dummy package with the old name which depends
  on the new one.

  @Aron: How should we deal with this issue? One way, if Droid Sans
  Fallback will keep being the default Chinese font in 16.04, is to ask
  upstream to create a transitional dummy package.

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

2015-12-19 Thread John Center

** Attachment added: "IMG_0766.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4537645/+files/IMG_0766.JPG

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 483086] Re: Incorrect per-target ?= variable affectations

2015-12-19 Thread Gary Bishop

We just spent an hour tracking down a problem only to find the bug has
been around since 2009.

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

Title:
  Incorrect per-target ?= variable affectations

Status in make-dfsg package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: make

  I am running 9.10 on x86_64 (updated yesterday), make 3.81-6.

  The following Makefile:
  -
  target1: OPTVAR?=/usr/local
  target1:
echo "Value for $@ '$(OPTVAR)'."

  target2:
echo "Value for $@ is '$(OPTVAR)'."
  -

  Make seems to behave badly with such a Makefile:

  shell> make OPTVAR=x target1 target2
  echo "Value for target1 '�!M'."
  Value for target1 '�!M'.
  echo "Value for target2 is '�!M'."
  Value for target2 is '�!M'.

  Whereas it has the expected behavior when passing OPTVAR through the
  environment:

  shell> env OPTVAR=x make target1 target2
  echo "Value for target1 'x'."
  Value for target1 'x'.
  echo "Value for target2 is 'x'."
  Value for target2 is 'x'.

  It also behaves as expected when OPTVAR is left undefined:

  shell> make target1 target2
  echo "Value for target1 '/usr/local'."
  Value for target1 '/usr/local'.
  echo "Value for target2 is ''."
  Value for target2 is ''.

  I believe this is a regression from jaunty.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Nov 15 14:57:25 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: make 3.81-6
  ProcEnviron:
   SHELL=/bin/zsh
   PATH=(custom, user)
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: make-dfsg
  Uname: Linux 2.6.31-14-generic x86_64

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

-- 
Mailing list: https://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 1464917] Re: reboot hangs at 'Reached target Shutdown'

2015-12-19 Thread xtrchessreal

@Gregory Kramida, I'll run a test with disabled background apps and reply
with results...Thanks for the info

On Sat, Dec 19, 2015 at 2:44 PM, Gregory Kramida 
wrote:

> @xtrchessreal, if Chromium background processes are the culprit on your
> platform, this would mean we are suffering from different issues.
> Indeed, my symptoms are actually a bit different from what's described
> in the original bug report -- I'm seeing the "Reached target Shutdown"
> when I actually try to shut down, not reboot, and the system doesn't
> fully shut down. My reboot works fine.
>
> You can try to disable Chromium background processes from running in the
> background when Chromium is shut down (settings --> Show advanced
> settings --> uncheck "Continue running ... "), and close chromium before
> you reboot.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1464917
>
> Title:
>   reboot hangs at 'Reached target Shutdown'
>
> Status in systemd package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I rebooted my 15.04 system, and found it hanging indefinitely at the
>   plymouth shutdown screen.  Hitting esc to reveal the console showed a
>   normal set of shutdown messages, ending with 'Reached target Shutdown'
>   (paraphrased from memory).
>
>   The system never rebooted on its own.  I had to use SysRq to finish
>   the shutdown.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: systemd 219-7ubuntu6
>   ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
>   Uname: Linux 3.19.0-20-generic x86_64
>   ApportVersion: 2.17.2-0ubuntu1.1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sat Jun 13 11:53:10 2015
>   InstallationDate: Installed on 2010-09-24 (1723 days ago)
>   InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
> (20100816.1)
>   MachineType: LENOVO 2306CTO
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic
> root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
>   SourcePackage: systemd
>   UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
>   dmi.bios.date: 10/25/2013
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ET97WW (2.57 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 2306CTO
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 2306CTO
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions
>

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list:

[Touch-packages] [Bug 1523922] [NEW] cursor disappears frequently

You have been subscribed to a public bug:

A few times a week, my cursor just disappears.

It is still there, reacting to mouse events, I can see hover events,
clicking works too. But the cursor image just disappears which makes it
unusable.

Rebooting is the only solution. Restarting unity doesn't recover it.

** Affects: unity
 Importance: Critical
 Status: New

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

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1527901] [NEW] crash

2015-12-19 Thread Reacher

Public bug reported:

i was working on libre office calc and the display tured to a mass of
coloured lines.and the laptop shut down.ok on reboot.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Dec 19 16:15:53 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, i686: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-19-generic, i686: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-21-generic, i686: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-22-generic, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:308f]
   Subsystem: Hewlett-Packard Company Device [103c:308f]
InstallationDate: Installed on 2015-12-11 (7 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
MachineType: Hewlett-Packard Compaq Mini 110c-1000
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=401473e2-a47e-4101-a985-7cbe4b9a9292 ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 308F0 Ver. F.07
dmi.board.name: 308F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.0B
dmi.chassis.asset.tag: CNU9335J75
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr308F0Ver.F.07:bd06/18/2009:svnHewlett-Packard:pnCompaqMini110c-1000:pvr03A8100010030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.0B:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: Compaq Mini 110c-1000
dmi.product.version: 03A8100010030
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sat Dec 19 16:09:56 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4817 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: apport-bug compiz-0.9 i386 ubuntu wily

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

Title:
  crash

Status in xorg package in Ubuntu:
  New

Bug description:
  i was working on libre office calc and the display tured to a mass of
  coloured lines.and the laptop shut down.ok on reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Dec 19 16:15:53 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, i686: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-19-generic, i686: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-21-generic, i686: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-22-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])

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

2015-12-19 Thread Jeroen

Like #84, I ran into this issue after only a few weeks of running a
standard Ubuntu installation with full disk encryption.

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

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

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

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

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

[Touch-packages] [Bug 1527942] [NEW] pdfimprt crash libreoffice 5.0.3 when import a pdf in libreoffice

2015-12-19 Thread Battant

Public bug reported:

Hello,

I have installed libreoffice 5.0.3 on  ubuntu 14.04 LTS 64 bit throw the
libreoffice official ppa.

It seems that libreoffice crach when I try to use pdfimport like this

Open libreoffice 5.03
chose file open
chose a pdf on my disk and try to open a file
Actual result

Libreoffice crach, show an error message and reovery documents

Could you help me please ?

Best regards

mparchet


My configuration

Description:Ubuntu 14.04.3 LTS
Release:14.04

libreoffice-pdfimport
libreoffice:
  Installed: 1:5.0.3~rc2-0ubuntu1~trusty2
  Candidate: 1:5.0.3~rc2-0ubuntu1~trusty2
  Version table:
 *** 1:5.0.3~rc2-0ubuntu1~trusty2 0
500 http://ppa.launchpad.net/libreoffice/libreoffice-5-0/ubuntu/ 
trusty/main amd64 Packages
500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main amd64 
Packages
100 /var/lib/dpkg/status
 1:4.2.8-0ubuntu3 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
 1:4.2.3~rc3-0ubuntu2 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

apt-cache policy libreoffice-pdfimport
libreoffice-pdfimport:
  Installed: 1:5.0.3~rc2-0ubuntu1~trusty2
  Candidate: 1:5.0.3~rc2-0ubuntu1~trusty2
  Version table:
 *** 1:5.0.3~rc2-0ubuntu1~trusty2 0
500 http://ppa.launchpad.net/libreoffice/libreoffice-5-0/ubuntu/ 
trusty/main amd64 Packages
500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main amd64 
Packages
100 /var/lib/dpkg/status
 1:4.2.8-0ubuntu3 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1:4.2.3~rc3-0ubuntu2 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

Title:
  pdfimprt crash libreoffice 5.0.3 when import a pdf in libreoffice

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Hello,

  I have installed libreoffice 5.0.3 on  ubuntu 14.04 LTS 64 bit throw the
  libreoffice official ppa.

  It seems that libreoffice crach when I try to use pdfimport like this

  Open libreoffice 5.03
  chose file open
  chose a pdf on my disk and try to open a file
  Actual result

  Libreoffice crach, show an error message and reovery documents

  Could you help me please ?

  Best regards

  mparchet

  
  My configuration

  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  libreoffice-pdfimport
  libreoffice:
Installed: 1:5.0.3~rc2-0ubuntu1~trusty2
Candidate: 1:5.0.3~rc2-0ubuntu1~trusty2
Version table:
   *** 1:5.0.3~rc2-0ubuntu1~trusty2 0
  500 http://ppa.launchpad.net/libreoffice/libreoffice-5-0/ubuntu/ 
trusty/main amd64 Packages
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:4.2.8-0ubuntu3 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
   1:4.2.3~rc3-0ubuntu2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  apt-cache policy libreoffice-pdfimport
  libreoffice-pdfimport:
Installed: 1:5.0.3~rc2-0ubuntu1~trusty2
Candidate: 1:5.0.3~rc2-0ubuntu1~trusty2
Version table:
   *** 1:5.0.3~rc2-0ubuntu1~trusty2 0
  500 http://ppa.launchpad.net/libreoffice/libreoffice-5-0/ubuntu/ 
trusty/main amd64 Packages
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:4.2.8-0ubuntu3 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:4.2.3~rc3-0ubuntu2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

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

2015-12-19 Thread Hobson Lane

Like #86, but for me it took 3 weeks. Depends on number of kernel
patches released after initial install. The OS should `sudo apt-get
autoclean` instead of crash. Fine to "notify" user of the inadequate
default boot partition size, but definitely not OK to scare them with a
"Crash" notice every time that boot partition is found to be too small
for the pace of kernel patches and the default kernel retention policy.

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

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

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

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

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

[Touch-packages] [Bug 1527854] Re: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2015-12-19 Thread Jackson Doak

After the error, and the resultant failure of the upgrader to revert
things, the system runs 16.04 and will work fine after apt-get dist-
upgrade.

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

Title:
  package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Installing for testing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jari   2054 F pulseaudio
   /dev/snd/controlC1:  jari   2054 F pulseaudio
   /dev/snd/controlC0:  jari   2054 F pulseaudio
  Date: Sat Dec 19 12:46:13 2015
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=1c0fb703-2b9d-4d9c-a5b8-ee59a3371e47
  InstallationDate: Installed on 2013-09-29 (811 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUSTeK Computer INC. V-P7H55E
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=0e8139a5-d931-44dc-b301-550b79ed3369 ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2015-12-19 (0 days ago)
  dmi.bios.date: 07/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P7H55E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/16/2010:svnASUSTeKComputerINC.:pnV-P7H55E:pvrX.0x:rvnASUSTeKComputerINC.:rnV-P7H55E:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P7H55E
  dmi.product.version: X.0x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1527848] [NEW] Indicator-Datetime always shows UTC time for any online calendar added to evolution

2015-12-19 Thread Khurshid Alam

Public bug reported:

My timezone is set to GMT+5:30 (Kolkata, India) from indicator datetime
settings. But when I add a online google calendar in Evolution, events
(which has start time and end time) are appearing as UTC  time. However
in evolution, its all nice and evolution does respect my timezone.

How to reproduce:

1. Set google calendar timezone to match your timezone from google
calendar settings (web).

2. From web interface, add a event with time into that calendar. Then
copy its private ical address.

3. Open evolution. Add that calendar from new->calendar->on the web.

4. reboot.

What should happen?

If a event starts from 5 PM, indicator-datetime should reflect that.

What is happening?

indicator-datetime shows every event starting at UTC time; i.e, in my
case 5.30 hours behind!

Screenshot: http://i.imgur.com/gPisVnl.png

Note: It seems it only happens for online calendars. Locally created
events are ok.

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


** Tags: xenial

** Description changed:

  My timezone is set to GMT+5:30 (Kolkata, India) from indicator datetime
  settings. But when I add a online google calendar in Evolution, events
  (which has start time and end time) are appearing as UTC  time. However
  in evolution, its all nice and evolution does respect my timezone.
  
  How to reproduce:
  
  1. Set google calendar timezone to match your timezone from google
  calendar settings (web).
  
  2. From web interface, add a event with time into that calendar. Then
  copy its private ical address.
  
  3. Open evolution. Add that calendar from new->calendar->on the web.
  
  4. reboot.
  
  What should happen?
  
  If a event starts from 5 PM, indicator-datetime should reflect that.
  
  What is happening?
  
  indicator-datetime shows every event starting at UTC time; i.e, in my
  case 5.30 hours behind!
  
- Screenshot: http://i.imgur.com/916LeIC.png
- 
+ Screenshot: http://i.imgur.com/gPisVnl.png
  
  Note: It seems it only happens for online calendars. Locally created
  events are ok.

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

Title:
  Indicator-Datetime always shows UTC time for any online calendar added
  to evolution

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  My timezone is set to GMT+5:30 (Kolkata, India) from indicator
  datetime settings. But when I add a online google calendar in
  Evolution, events (which has start time and end time) are appearing as
  UTC  time. However in evolution, its all nice and evolution does
  respect my timezone.

  How to reproduce:

  1. Set google calendar timezone to match your timezone from google
  calendar settings (web).

  2. From web interface, add a event with time into that calendar. Then
  copy its private ical address.

  3. Open evolution. Add that calendar from new->calendar->on the web.

  4. reboot.

  What should happen?

  If a event starts from 5 PM, indicator-datetime should reflect that.

  What is happening?

  indicator-datetime shows every event starting at UTC time; i.e, in my
  case 5.30 hours behind!

  Screenshot: http://i.imgur.com/gPisVnl.png

  Note: It seems it only happens for online calendars. Locally created
  events are ok.

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

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

[Touch-packages] [Bug 1527374] Re: privilege escalation on attach through ptrace

This bug was fixed in the package linux-lts-wily - 4.2.0-22.27~14.04.1

---
linux-lts-wily (4.2.0-22.27~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1527538

  [ Jann Horn ]

  * ptrace: being capable wrt a process requires mapped uids/gids
- LP: #1527374

linux (4.2.0-22.26) wily; urgency=low

  [ Upstream Kernel Changes ]

  * xen: Add RING_COPY_REQUEST()
- CVE-2015-8550
  * xen-netback: don't use last request to determine minimum Tx credit
- CVE-2015-8550
  * xen-netback: use RING_COPY_REQUEST() throughout
- CVE-2015-8550
  * xen-blkback: only read request operation from shared ring once
- CVE-2015-8550
  * xen-blkback: read from indirect descriptors only once
- CVE-2015-8550
  * xen-scsiback: safely copy requests
- CVE-2015-8550
  * xen/pciback: Save xen_pci_op commands before processing it
- CVE-2015-8550
  * xen/pciback: Return error on XEN_PCI_OP_enable_msi when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Return error on XEN_PCI_OP_enable_msix when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Do not install an IRQ handler for MSI interrupts.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: For XEN_PCI_OP_disable_msi[|x] only disable if device has
MSI(X) enabled.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Don't allow MSI-X ops if PCI_COMMAND_MEMORY is not set.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553

 -- Luis Henriques   Fri, 18 Dec 2015
10:27:07 +

** Changed in: linux-lts-wily (Ubuntu)
   Status: New => Fix Released

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

Title:
  privilege escalation on attach through ptrace

Status in linux package in Ubuntu:
  Incomplete
Status in linux-armadaxp package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  New
Status in linux-lts-raring package in Ubuntu:
  New
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Released
Status in linux-lts-wily package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Incomplete

Bug description:
  A kernel bug in user namespaces allows root in a container to ptrace
  host-root-owned tasks during a window of opportunity during lxc-attach
  / 'lxc exec', before they drop privilege by doing setuid to the
  container root uid.

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

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

[Touch-packages] [Bug 1527374] Re: privilege escalation on attach through ptrace

This bug was fixed in the package linux-lts-wily - 4.2.0-22.27~14.04.1

---
linux-lts-wily (4.2.0-22.27~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1527538

  [ Jann Horn ]

  * ptrace: being capable wrt a process requires mapped uids/gids
- LP: #1527374

linux (4.2.0-22.26) wily; urgency=low

  [ Upstream Kernel Changes ]

  * xen: Add RING_COPY_REQUEST()
- CVE-2015-8550
  * xen-netback: don't use last request to determine minimum Tx credit
- CVE-2015-8550
  * xen-netback: use RING_COPY_REQUEST() throughout
- CVE-2015-8550
  * xen-blkback: only read request operation from shared ring once
- CVE-2015-8550
  * xen-blkback: read from indirect descriptors only once
- CVE-2015-8550
  * xen-scsiback: safely copy requests
- CVE-2015-8550
  * xen/pciback: Save xen_pci_op commands before processing it
- CVE-2015-8550
  * xen/pciback: Return error on XEN_PCI_OP_enable_msi when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Return error on XEN_PCI_OP_enable_msix when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Do not install an IRQ handler for MSI interrupts.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: For XEN_PCI_OP_disable_msi[|x] only disable if device has
MSI(X) enabled.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Don't allow MSI-X ops if PCI_COMMAND_MEMORY is not set.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553

 -- Luis Henriques   Fri, 18 Dec 2015
10:27:07 +

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

Title:
  privilege escalation on attach through ptrace

Status in linux package in Ubuntu:
  Incomplete
Status in linux-armadaxp package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  New
Status in linux-lts-raring package in Ubuntu:
  New
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Released
Status in linux-lts-wily package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Incomplete

Bug description:
  A kernel bug in user namespaces allows root in a container to ptrace
  host-root-owned tasks during a window of opportunity during lxc-attach
  / 'lxc exec', before they drop privilege by doing setuid to the
  container root uid.

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

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

[Touch-packages] [Bug 1527374] Re: privilege escalation on attach through ptrace

This bug was fixed in the package linux-lts-vivid - 3.19.0-42.48~14.04.1

---
linux-lts-vivid (3.19.0-42.48~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1527519

  [ Jann Horn ]

  * ptrace: being capable wrt a process requires mapped uids/gids
- LP: #1527374

linux (3.19.0-42.47) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * xen: Add RING_COPY_REQUEST()
- CVE-2015-8550
  * xen-netback: don't use last request to determine minimum Tx credit
- CVE-2015-8550
  * xen-netback: use RING_COPY_REQUEST() throughout
- CVE-2015-8550
  * xen-blkback: only read request operation from shared ring once
- CVE-2015-8550
  * xen-blkback: read from indirect descriptors only once
- CVE-2015-8550
  * xen-scsiback: safely copy requests
- CVE-2015-8550
  * xen/pciback: Save xen_pci_op commands before processing it
- CVE-2015-8550
  * xen/pciback: Return error on XEN_PCI_OP_enable_msi when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Return error on XEN_PCI_OP_enable_msix when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Do not install an IRQ handler for MSI interrupts.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: For XEN_PCI_OP_disable_msi[|x] only disable if device has
MSI(X) enabled.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Don't allow MSI-X ops if PCI_COMMAND_MEMORY is not set.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553

 -- Luis Henriques   Fri, 18 Dec 2015
09:59:09 +

** Changed in: linux-lts-vivid (Ubuntu)
   Status: New => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8550

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8551

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8552

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8553

** Changed in: linux-lts-vivid (Ubuntu)
   Status: New => Fix Released

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

Title:
  privilege escalation on attach through ptrace

Status in linux package in Ubuntu:
  Incomplete
Status in linux-armadaxp package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  New
Status in linux-lts-raring package in Ubuntu:
  New
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Released
Status in linux-lts-wily package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Incomplete

Bug description:
  A kernel bug in user namespaces allows root in a container to ptrace
  host-root-owned tasks during a window of opportunity during lxc-attach
  / 'lxc exec', before they drop privilege by doing setuid to the
  container root uid.

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

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

[Touch-packages] [Bug 1527374] Re: privilege escalation on attach through ptrace

This bug was fixed in the package linux-lts-vivid - 3.19.0-42.48~14.04.1

---
linux-lts-vivid (3.19.0-42.48~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1527519

  [ Jann Horn ]

  * ptrace: being capable wrt a process requires mapped uids/gids
- LP: #1527374

linux (3.19.0-42.47) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * xen: Add RING_COPY_REQUEST()
- CVE-2015-8550
  * xen-netback: don't use last request to determine minimum Tx credit
- CVE-2015-8550
  * xen-netback: use RING_COPY_REQUEST() throughout
- CVE-2015-8550
  * xen-blkback: only read request operation from shared ring once
- CVE-2015-8550
  * xen-blkback: read from indirect descriptors only once
- CVE-2015-8550
  * xen-scsiback: safely copy requests
- CVE-2015-8550
  * xen/pciback: Save xen_pci_op commands before processing it
- CVE-2015-8550
  * xen/pciback: Return error on XEN_PCI_OP_enable_msi when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Return error on XEN_PCI_OP_enable_msix when device has MSI
or MSI-X enabled
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Do not install an IRQ handler for MSI interrupts.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: For XEN_PCI_OP_disable_msi[|x] only disable if device has
MSI(X) enabled.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553
  * xen/pciback: Don't allow MSI-X ops if PCI_COMMAND_MEMORY is not set.
- CVE-2015-8551, CVE-2015-8552, CVE-2015-8553

 -- Luis Henriques   Fri, 18 Dec 2015
09:59:09 +

** Changed in: linux-lts-wily (Ubuntu)
   Status: New => Fix Released

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

Title:
  privilege escalation on attach through ptrace

Status in linux package in Ubuntu:
  Incomplete
Status in linux-armadaxp package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  New
Status in linux-lts-raring package in Ubuntu:
  New
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Released
Status in linux-lts-wily package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Incomplete

Bug description:
  A kernel bug in user namespaces allows root in a container to ptrace
  host-root-owned tasks during a window of opportunity during lxc-attach
  / 'lxc exec', before they drop privilege by doing setuid to the
  container root uid.

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

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

[Touch-packages] [Bug 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-12-19 Thread RaphaëlPLE

I have the same issue.

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

Title:
  package initramfs-tools 0.120ubuntu6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Error occured during UBUNTU Mate upgrade to 15.10 on Raspberry PI2 and
  once trying perform manual update getting:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.120ubuntu6) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.120ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-3.18.0-25-rpi2
  Unsupported platform.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 
1
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.120ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: armhf
  Date: Sun Oct 25 08:19:08 2015
  DuplicateSignature: package:initramfs-tools:0.120ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago)

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

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

[Touch-packages] [Bug 1527862] [NEW] Ubuntu 16.04 Unity8 black screen

Public bug reported:

just installed a fresh 16.04 daily build, updated and installed unity8
desktop session mir.

expected: unity8
actual result: black screen

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

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

Title:
  Ubuntu 16.04 Unity8 black screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  just installed a fresh 16.04 daily build, updated and installed unity8
  desktop session mir.

  expected: unity8
  actual result: black screen

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

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

[Touch-packages] [Bug 1527863] [NEW] screen display

Public bug reported:

on eeepc 901, lost in 3/4 of screen , boot on systemd

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+12ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.3-0ubuntu2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Dec 19 12:02:02 2015
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
   Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
InstallationDate: Installed on 2015-12-19 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209)
MachineType: ASUSTeK Computer INC. 901
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash init=/sbin/upstart
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1
version.libdrm2: libdrm2 2.4.65-3
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sat Dec 19 12:00:39 2015
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 1612 does not belong 
to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 805 
 vendor HSD
xserver.version: 2:1.17.3-2ubuntu2

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


** Tags: apport-bug compiz-0.9 corruption i386 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/1527863

Title:
  screen display

Status in xorg package in Ubuntu:
  New

Bug description:
  on eeepc 901, lost in 3/4 of screen , boot on systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+12ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Dec 19 12:02:02 2015
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
  InstallationDate: Installed on 2015-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209)
  MachineType: ASUSTeK Computer INC. 901
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash init=/sbin/upstart
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 901
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx

[Touch-packages] [Bug 1527862] Re: Ubuntu 16.04 Unity8 black screen

mir-0.17.1+16.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168): 
Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe

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

Title:
  Ubuntu 16.04 Unity8 black screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  just installed a fresh 16.04 daily build, updated and installed unity8
  desktop session mir.

  expected: unity8
  actual result: black screen

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

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

[Touch-packages] [Bug 1527862] Re: Ubuntu 16.04 Unity8 black screen

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1527862/+attachment/4537374/+files/unity8.log

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

Title:
  Ubuntu 16.04 Unity8 black screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  just installed a fresh 16.04 daily build, updated and installed unity8
  desktop session mir.

  expected: unity8
  actual result: black screen

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

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

[Touch-packages] [Bug 1527862] Re: Ubuntu 16.04 Unity8 black screen

Failed to connect to Mir: Failed to connect: not accepted by server
[1450528330.893660]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-sTjxjQ/mir-0.17.1+16.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"
Unable to init server: Could not connect: Connection refused

(gst-plugin-scanner:2013): Clutter-CRITICAL **: Unable to initialize
Clutter: Could not initialize Gdk

(gst-plugin-scanner:2013): Clutter-Gst-CRITICAL **: Unable to initialize Clutter
()
qtmir.screens: ScreenController::ScreenController
[1450528331.562308] mirplatform: Found graphics driver: mesa-kms
[1450528331.562423] mirplatform: Found graphics driver: mesa-x11
qtmir.mir: MirServer created
[1450528331.564144] mirserver: Starting
[1450528331.564389] mircommon: Loading modules from: 
/usr/lib/x86_64-linux-gnu/mir/server-platform
[1450528331.564498] mircommon: Loading module: 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.6
[1450528331.564563] mircommon: Loading module: 
/usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.6
[1450528331.565985] mirplatform: Found graphics driver: mesa-kms
[1450528331.566061] mirplatform: Found graphics driver: mesa-x11
[1450528331.566183] mirserver: Selected driver: mesa-kms (version 0.17.1)
ERROR: 
/build/mir-sTjxjQ/mir-0.17.1+16.04.20151105.1/src/server/graphics/nested/mir_client_host_connection.cpp(192):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: No such file or directory

ERROR: QMirServer - Mir failed to start

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

Title:
  Ubuntu 16.04 Unity8 black screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  just installed a fresh 16.04 daily build, updated and installed unity8
  desktop session mir.

  expected: unity8
  actual result: black screen

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

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

[Touch-packages] [Bug 1527862] Re: Ubuntu 16.04 Unity8 black screen

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1527862/+attachment/4537403/+files/unity8.log

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

Title:
  Ubuntu 16.04 Unity8 black screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  just installed a fresh 16.04 daily build, updated and installed unity8
  desktop session mir.

  expected: unity8
  actual result: black screen

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

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

[Touch-packages] [Bug 1527862] Re: Ubuntu 16.04 Unity8 black screen

** Attachment added: 
"update-notifier-crash-_var_crash__usr_bin_unity8-dash.1000.crash.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1527862/+attachment/4537405/+files/update-notifier-crash-_var_crash__usr_bin_unity8-dash.1000.crash.log

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

Title:
  Ubuntu 16.04 Unity8 black screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  just installed a fresh 16.04 daily build, updated and installed unity8
  desktop session mir.

  expected: unity8
  actual result: black screen

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

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

[Touch-packages] [Bug 1527862] Re: Ubuntu 16.04 Unity8 black screen

** Attachment added: "unity8-dash.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1527862/+attachment/4537404/+files/unity8-dash.log

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

Title:
  Ubuntu 16.04 Unity8 black screen

Status in unity8 package in Ubuntu:
  New

Bug description:
  just installed a fresh 16.04 daily build, updated and installed unity8
  desktop session mir.

  expected: unity8
  actual result: black screen

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

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

[Touch-packages] [Bug 1527870] [NEW] no clue,

2015-12-19 Thread Marc Wagner

Public bug reported:

Get a message that there is a system problem, what I do not know.

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

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

Title:
  no clue,

Status in apparmor package in Ubuntu:
  New

Bug description:
  Get a message that there is a system problem, what I do not know.

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

2015-12-19 Thread GTriderXC

I have the same problem in my Scania. Pairing "works". Phone sees the BT of a 
radio correctly then I'm starting pairing, I give the code, radio gives me a 
message that pairing was correct and my Aquaris 4.5 is on the list of known 
trusted devices but never connects to the phone. After few seconds I get a 
message that the connection with the phone failed.
>From the phone side the problem looks this way: my bq shows me that it is 
>connected to the radio. It is always connected even if I turn the radio off or 
>click the "disconnect" button. Funny thing is that though the phone is telling 
>me that it is connected with the radio of the car (I think it shows it as a 
>headset) when I'm making a phone call the phone isn't trying to send and 
>receive the voice via bluetooth. I can talk through the phone though it shows 
>it is connected with the radio/headset.

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

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

2015-12-19 Thread LAZA

Public bug reported:

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

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


** Tags: wily

-- 
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:
  New

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 1495781] Re: Can't move to trash in data partition

2015-12-19 Thread CzBiX

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

@Rik Shaw, do you meaning the logic of patch?

I was dis-asm the file of glib, find the position of 'if condition' on line 44
in
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/glib2.0/vivid-proposed/revision/227#debian/patches/0001-Fix-trashing-on-overlayfs.patch
change the machine instruction to jump(0xeb), then this if block will be
skipped.

It's just a simple hack to fix it. Compile source code without that
patch is correct and more safer way.

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

Title:
Can't move to trash in data partition

Status in glib2.0 package in Ubuntu:
Confirmed

Bug description:
I have a clean install of Ubuntu 15.04.

I partitioned my disk into root and data partitions.
I then created ~/Data folder, and mount data partition on it.
I then created symlinks for ~/Downloads, ~/Music, etc... to ~/Data/Downloads,
~/Data/Music, etc...

Whenever I delete files directly inside ~/ they seem to go to the
Trash (in ~/.local/share/Trash), but when I try to delete files in
other folders that are linked to ~/Data (for example ~/Downloads, or
~/Data/Downloads) Nautilus says: "File can't be put in the trash. Do
you want to delete it immediately?".

I compile glib without patch at
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1445622/comments/25,
then it works well.

report from https://bugs.launchpad.net/nautilus/+bug/1406376

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

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

[Touch-packages] [Bug 1527315] Re: Attached gif downloaded from telegram takes out the phone as thumbnailer hogs the memory and cpu

2015-12-19 Thread Michi Henning

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michi Henning (michihenning)

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

Title:
  Attached gif downloaded from telegram takes out the phone as
  thumbnailer hogs the memory and cpu

Status in Canonical System Image:
  Confirmed
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  STEPS:
  1. drop the attached gif into the Photo's  folder
  2. Open gallery
  3. Refresh the photo's scope

  ISSUE:
  The gif I think causes thumbnailer to loop, Memory usage jump 4% each loop 
until oom takes out the app but thumbnailer is still stuck in it's loop so 
eventually the scopes are all taken out, At that point thumbnailer is stopped 
and the system returns to normal with the exception that there is now a black 
space where the scopes used to be.

  IMAGE:
  Krillin ota 8.5

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

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

[Touch-packages] [Bug 1527854] [NEW] package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2015-12-19 Thread (J)Aloittelija

Public bug reported:

Installing for testing

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-2-generic 4.3.0-2.11
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jari   2054 F pulseaudio
 /dev/snd/controlC1:  jari   2054 F pulseaudio
 /dev/snd/controlC0:  jari   2054 F pulseaudio
Date: Sat Dec 19 12:46:13 2015
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=1c0fb703-2b9d-4d9c-a5b8-ee59a3371e47
InstallationDate: Installed on 2013-09-29 (811 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: ASUSTeK Computer INC. V-P7H55E
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=0e8139a5-d931-44dc-b301-550b79ed3369 ro drm.debug=0xe plymouth:debug
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to xenial on 2015-12-19 (0 days ago)
dmi.bios.date: 07/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0504
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: V-P7H55E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/16/2010:svnASUSTeKComputerINC.:pnV-P7H55E:pvrX.0x:rvnASUSTeKComputerINC.:rnV-P7H55E:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: V-P7H55E
dmi.product.version: X.0x
dmi.sys.vendor: ASUSTeK Computer INC.

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Installing for testing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jari   2054 F pulseaudio
   /dev/snd/controlC1:  jari   2054 F pulseaudio
   /dev/snd/controlC0:  jari   2054 F pulseaudio
  Date: Sat Dec 19 12:46:13 2015
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=1c0fb703-2b9d-4d9c-a5b8-ee59a3371e47
  InstallationDate: Installed on 2013-09-29 (811 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUSTeK Computer INC. V-P7H55E
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=0e8139a5-d931-44dc-b301-550b79ed3369 ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2015-12-19 (0 days ago)
  dmi.bios.date: 07/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P7H55E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/16/2010:svnASUSTeKComputerINC.:pnV-P7H55E:pvrX.0x:rvnASUSTeKComputerINC.:rnV-P7H55E:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name:

[Touch-packages] [Bug 1527854] Re: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2015-12-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Installing for testing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jari   2054 F pulseaudio
   /dev/snd/controlC1:  jari   2054 F pulseaudio
   /dev/snd/controlC0:  jari   2054 F pulseaudio
  Date: Sat Dec 19 12:46:13 2015
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=1c0fb703-2b9d-4d9c-a5b8-ee59a3371e47
  InstallationDate: Installed on 2013-09-29 (811 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUSTeK Computer INC. V-P7H55E
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=0e8139a5-d931-44dc-b301-550b79ed3369 ro drm.debug=0xe plymouth:debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-2-generic 4.3.0-2.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2015-12-19 (0 days ago)
  dmi.bios.date: 07/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P7H55E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/16/2010:svnASUSTeKComputerINC.:pnV-P7H55E:pvrX.0x:rvnASUSTeKComputerINC.:rnV-P7H55E:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P7H55E
  dmi.product.version: X.0x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install

2015-12-19 Thread Sebastian Nohn

Change summary, because /boot is always to small on "LVM or Encrypted
install". The former summary read like it was a user error, while it
isn't.

** Summary changed:

- Kernels not autoremoving, causing out of space error on LVM or Encrypted 
install with small /boot partition
+ Kernels not autoremoving, causing out of space error on LVM or Encrypted 
install

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted install

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

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

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

[Touch-packages] [Bug 1527806] Re: PC does not boot with "normal" options - need debug mode and upstart

2015-12-19 Thread LAZA

Added

journalctl -xb

output of a failed normal boot.

** Attachment added: "journalctl1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1527806/+attachment/4537265/+files/journalctl1.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/1527806

Title:
  PC does not boot with "normal" options - need debug mode and upstart

Status in systemd package in Ubuntu:
  New

Bug description:
  Fresh installation of Xubuntu 15.10 and does not boot at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Dec 19 00:44:46 2015
  InstallationDate: Installed on 2015-12-18 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Precision WorkStation T3500
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=db230f21-3dc1-4553-90ef-8aa0c66e2253 ro quiet splash 
init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 09KPNV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd05/28/2013:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3500
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1490212] Re: "Modaliases" field missing from debian control file

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

** Changed in: b43-fwcutter (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  "Modaliases" field missing from debian control file

Status in b43-fwcutter package in Ubuntu:
  Expired
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  The b43 module is not listed as an option by the "additional drivers"
  section of the software-properties-gtk utility.  This takes its
  information from the ubuntu-drivers-common package and a bug has been
  reported against that package
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1186779 ).

  However, if I'm reading things correctly, the firmware-b43-installer
  package could solve this by providing a modaliases field in the debian
  control file.  For example, the bcmwl-kernel-source package has the
  line:

  Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

  This would be scanned by the ubuntu-drivers-common package and
  consequently appear in software-properties-gtk.

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

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

[Touch-packages] [Bug 1523922] Re: cursor disappears frequently

2015-12-19 Thread knulp haller

It is not unity bug, it is a lightdm problem. try to restart lightdm
service

** Package changed: unity (Ubuntu) => lightdm (Ubuntu)

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

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

Title:
  cursor disappears frequently

Status in Unity:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  A few times a week, my cursor just disappears.

  It is still there, reacting to mouse events, I can see hover events,
  clicking works too. But the cursor image just disappears which makes
  it unusable.

  Rebooting is the only solution. Restarting unity doesn't recover it.

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

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

[Touch-packages] [Bug 1527874] Re: lost 3/4 screen

boot systemd

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

Title:
  lost 3/4 screen

Status in xorg package in Ubuntu:
  New

Bug description:
  lost 3/4 screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+12ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic i686
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Dec 19 12:17:42 2015
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
  InstallationDate: Installed on 2015-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209)
  MachineType: ASUSTeK Computer INC. 901
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 901
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 901
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Dec 19 12:15:15 2015
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 824 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 805 
   vendor HSD
  xserver.version: 2:1.17.3-2ubuntu2

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

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

[Touch-packages] [Bug 1527874] [NEW] lost 3/4 screen

Public bug reported:

lost 3/4 screen

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+12ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic i686
ApportVersion: 2.19.3-0ubuntu2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Dec 19 12:17:42 2015
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
   Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
InstallationDate: Installed on 2015-12-19 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209)
MachineType: ASUSTeK Computer INC. 901
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1
version.libdrm2: libdrm2 2.4.65-3
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sat Dec 19 12:15:15 2015
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 824 does not belong 
to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 805 
 vendor HSD
xserver.version: 2:1.17.3-2ubuntu2

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


** Tags: apport-bug corruption i386 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/1527874

Title:
  lost 3/4 screen

Status in xorg package in Ubuntu:
  New

Bug description:
  lost 3/4 screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+12ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic i686
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Dec 19 12:17:42 2015
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
  InstallationDate: Installed on 2015-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209)
  MachineType: ASUSTeK Computer INC. 901
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 901
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 901
  dmi.product.version: x.x
  dmi.sys.vendor:

[Touch-packages] [Bug 1527863] Re: screen display

boot upstart

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

Title:
  screen display

Status in xorg package in Ubuntu:
  New

Bug description:
  on eeepc 901, lost in 3/4 of screen , boot on systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+12ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Dec 19 12:02:02 2015
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
  InstallationDate: Installed on 2015-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209)
  MachineType: ASUSTeK Computer INC. 901
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash init=/sbin/upstart
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 901
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 901
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Dec 19 12:00:39 2015
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 1612 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 805 
   vendor HSD
  xserver.version: 2:1.17.3-2ubuntu2

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

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

[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255]

2015-12-19 Thread Barry Lagerweij

The Acer laptop has 2 seperate jacks: one for mic input, one for headset
output (combined with spdif output).

The Dell laptop has probably one jack for headset/mic combined? My guess
is that the mapping will be different. Also, looking at
https://github.com/torvalds/linux/commits/master/sound/pci/hda/patch_realtek.c,
it looks like there are many 'quirks' to get things working.

Does anyone know if it's possible to use one of the two ports as a
combined mic/headset jack?

Barry

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1527870] Re: no clue,

2015-12-19 Thread Christian Boltz

The crystal balls are out of stock, so maybe you can at least provide
the exact message?

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

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

Title:
  no clue,

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Get a message that there is a system problem, what I do not know.

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

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

[Touch-packages] [Bug 1511496] Re: Synaptics touchpad pastes when clicked in the top-right corner

** Tags added: vivid wily

** Description changed:

  When I tap the Synaptics touchpad of my laptop, the contents of the
  clipboard are pasted. It's exactly as if I typed "Ctrl-V" in the current
  window. I see no way in the touchpad settings to disable this behavior,
  so it seems like a bug.
  
  Action taken: tap the touchpad in the top right of the touchpad
  Expected result: the mouse is clicked at the current location
  Erroneous result: the clipboard is pasted into the current application.
+ 
+ WORKAROUND: Put in /etc/X11/xorg.conf :
+ Section "InputClass"
+ Identifier "touchpad"
+ Driver "synaptics"
+ MatchIsTouchpad "on"
+ 
+ Option "RTCornerButton" "0"
+ Option "RBCornerButton" "0"
+ EndSection
  
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.10, 3.19.0-32-generic, x86_64: installed
   vboxhost, 5.0.10, 3.19.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:062e]
  InstallationDate: Installed on 2015-10-16 (33 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1286): WARNING **: Failed to load user image: Failed 
to open file '/home/trewhitte/.face': No such file or directory
   init: indicator-power main process (1321) killed by TERM signal
   init: indicator-application main process (1326) killed by TERM signal
  MachineType: Dell Inc. Latitude E7450
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic 
root=UUID=7d0dc4da-2a18-4838-b806-126cae6a56d3 ro quiet splash 
intel_pstate=enable vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Tags:  trusty ubuntu
  Uname: Linux 3.19.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Nov 18 16:26:50 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4925
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

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

Title:
  Synaptics touchpad pastes when clicked in the top-right corner

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I tap the Synaptics touchpad of my laptop, the contents of the
  clipboard are pasted. It's exactly as if I typed "Ctrl-V" in the
  current window. I see no way in the touchpad settings to disable this
  behavior, so it seems like a bug.

  Action taken: tap the touchpad in the top right of the touchpad
  Expected result: the mouse is clicked at the current location
  Erroneous result: the clipboard is pasted into the current application.

  WORKAROUND: Put in /etc/X11/xorg.conf :
  Section "InputClass"
  Identifier "touchpad"
  Driver "synaptics"
  MatchIsTouchpad "on"

  Option "RTCornerButton" "0"
  Option "RBCornerButton" "0"
  EndSection

  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for

[Touch-packages] [Bug 1519823] Re: regular crash of X. lightdm is shown after crash

Luca Frosini, thank you for reporting this and helping make Ubuntu
better.

As per https://www.asus.com/Motherboards/P8H77M_PRO/HelpDesk_Download/
an update to your computer's buggy and outdated BIOS is available
(1505). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status Confirmed. If it's not reproducible, please 
mark this as Invalid.

Thank you for your understanding.

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

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

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

Title:
  regular crash of X. lightdm is shown after crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The crash happen randomly, but always when the user perform an action 
(especially when a new windows or new tab on browser is created).
  I especially have this crash when I click on reply button on thunderbird

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Nov 25 14:18:45 2015
  DistUpgraded: 2015-10-29 11:09:19,997 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca]
  InstallationDate: Installed on 2015-01-05 (324 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=8d1438a5-df16-43eb-83f6-288e26294c57 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-29 (27 days ago)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Nov 25 12:42:54 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1511496] Re: Synaptics touchpad pastes when clicked in the top-right corner

Ethan Trewhitt, the issue you are reporting is an upstream one. Could
you please report this problem via
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg (Component:
input/synaptics)?

Please provide a direct URL to your bug report once you have made it so
that it may be tracked.

Thank you for your understanding.

** Package changed: xorg (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Synaptics touchpad pastes when clicked in the top-right corner

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Triaged

Bug description:
  When I tap the Synaptics touchpad of my laptop, the contents of the
  clipboard are pasted. It's exactly as if I typed "Ctrl-V" in the
  current window. I see no way in the touchpad settings to disable this
  behavior, so it seems like a bug.

  Action taken: tap the touchpad in the top right of the touchpad
  Expected result: the mouse is clicked at the current location
  Erroneous result: the clipboard is pasted into the current application.

  WORKAROUND: Put in /etc/X11/xorg.conf :
  Section "InputClass"
  Identifier "touchpad"
  Driver "synaptics"
  MatchIsTouchpad "on"

  Option "RTCornerButton" "0"
  Option "RBCornerButton" "0"
  EndSection

  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.10, 3.19.0-32-generic, x86_64: installed
   vboxhost, 5.0.10, 3.19.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:062e]
  InstallationDate: Installed on 2015-10-16 (33 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1286): WARNING **: Failed to load user image: Failed 
to open file '/home/trewhitte/.face': No such file or directory
   init: indicator-power main process (1321) killed by TERM signal
   init: indicator-application main process (1326) killed by TERM signal
  MachineType: Dell Inc. Latitude E7450
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic 
root=UUID=7d0dc4da-2a18-4838-b806-126cae6a56d3 ro quiet splash 
intel_pstate=enable vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Tags:  trusty ubuntu
  Uname: Linux 3.19.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Nov 18 16:26:50 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4925
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1511496/+subscriptions

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

[Touch-packages] [Bug 1509846] Re: lightdm crashes on window open in Ubuntu 15.10 intel

2015-12-19 Thread david

This bug has been affecting me for about 4 weeks now.  Lightdm crashes
on random window opening.  Usually a  thunderbird window.  VERY
frustrating.  I used to go 6 months between restarts.  Now it crashes
every day a few times.

** Package changed: xorg (Ubuntu) => lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  lightdm crashes on window open in Ubuntu 15.10 intel

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Symptom: xorg crashes on windows creation

  How to reproduce: No 100% reproducibility, however intensively using
  2D/3D acceleration triggers the bug (e.g. by opening several new
  windows and/or menus in a Unity desktop environment)

  Affected hardware: Intel HD Graphics 4400/5000 etc
  Affected software:
  - kernel 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64
  - Ubuntu 15.10 with Unity (because of compiz 2D/3D acceleration)
  - any other software using direct rendering (e.g. VLC)

  Workaround:
  - Disable window animations in Compiz reduces the frequency of the crashes.
  Use compizconfig-settings-manager for this tweak (sudo apt-get install 
compizconfig-settings-manager)

  
  [original description below]

  I get crashes, when I open a new window in an already started
  application. It happens irregularely, but I can force the crash if I
  open several new message windows in thunderbird. But it also happens
  in other applilcations, for example a new terminal window.

  This is the output during the crash in /var/log/Xorg.0.log
  [   253.500] (EE)
  [   253.500] (EE) Backtrace:
  [   253.500] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f09075b62e]
  [   253.500] (EE) 1: /usr/bin/X (0x55f0905a7000+0x1b8999) [0x55f09075f999]
  [   253.500] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f44130a8000+0x352f0) 
[0x7f44130dd2f0]
  [   253.500] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x24f18) [0x7f440f4a3f18]
  [   253.500] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x26157) [0x7f440f4a5157]
  [   253.500] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x2b4b1) [0x7f440f4aa4b1]
  [   253.500] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x804e4) [0x7f440f4ff4e4]
  [   253.501] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x80e2c) [0x7f440f4ffe2c]
  [   253.501] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x82e1a) [0x7f440f501e1a]
  [   253.501] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x4197c) [0x7f440f4c097c]
  [   253.501] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x59906) [0x7f440f4d8906]
  [   253.501] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55f090604654]
  [   253.501] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55f09075f274]
  [   253.501] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55f09060a502]
  [   253.501] (EE) 14: /usr/bin/X (0x55f0905a7000+0xf495a) [0x55f09069b95a]
  [   253.501] (EE) 15: /usr/bin/X (0x55f0905a7000+0xf5ef5) [0x55f09069cef5]
  [   253.501] (EE) 16: /usr/bin/X (0x55f0905a7000+0x5818f) [0x55f0905ff18f]
  [   253.501] (EE) 17: /usr/bin/X (0x55f0905a7000+0x5c34b) [0x55f09060334b]
  [   253.501] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f44130c8a40]
  [   253.501] (EE) 19: /usr/bin/X (_start+0x29) [0x55f0905ed6c9]
  [   253.501] (EE)
  [   253.501] (EE) Segmentation fault at address 0x0
  [   253.501] (EE)
  Fatal server error:
  [   253.501] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [   253.501] (EE)
  [   253.501] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  [   253.501] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [   253.502] (EE)
  [   253.502] (II) AIGLX: Suspending AIGLX clients for VT switch
  [   253.588] (EE) Server terminated with error (1). Closing log file.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.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
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-11-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2015-10-20

[Touch-packages] [Bug 1507233] Re: xorg