[Touch-packages] [Bug 1462596] Re: apt-get autoremove takes quadratically long

[Jarno Suni]

The aforementioned `sudo chmod -x` command has the side-effect that
update-grub will be left non-executable in case of power cut.

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

Title:
  apt-get autoremove takes quadratically long

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

Bug description:
  apt-get autoremove regenerates the initrd after removing each kernel.
  Since you generally call this command only when your boot volume is
  full of old kernels, it seems sub-optimal to regenerate the initrd
  eight times when removing eight kernels.  Could something be done with
  triggers to do a single regeneration of the initrd at the end?

  This is in 14.04

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

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

[Touch-packages] [Bug 1618988] Re: unity8 goes to black screen 'n freeze after logout attempt

[Daniel van Vugt]

** Tags added: black-screen

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

Title:
  unity8 goes to black screen 'n freeze after logout attempt

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  as in subject header ... when logging out of unity8 it will go to
  blackspace and freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160826-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 31 13:09:15 2016
  InstallationDate: Installed on 2016-08-31 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160616)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1506358] Re: unity8/libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

[Daniel van Vugt]

The correct milestone for this bug is 13 (OTA-13) in canonical-devices-
system-image.

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

Title:
  unity8/libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  ---
  Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

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

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

[Touch-packages] [Bug 1621746] Re: Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0)

[Daniel van Vugt]

This is a critical bug, but possibly also not valid.

The offending version of protobuf is not released. It's still in proposed:
https://launchpad.net/ubuntu/+source/protobuf

So I guess this should just serve as a reminder to rebuild users of
protobuf before v3 hits yakkety.

** Tags added: black-screen

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: protobuf (Ubuntu)
   Importance: Undecided => Critical

** Tags added: unity8-desktop

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

Title:
  Black Screen, libprotobuf FATAL program was compiled against version
  2.6.1  which is not compatible with the installed version (3.0.0)

Status in Canonical System Image:
  New
Status in protobuf package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 + proposed x86 install

  Black Screen, libprotobuf FATAL program was compiled against version
  2.6.1  which is not compatible with the installed version (3.0.0)

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

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

[Touch-packages] [Bug 1621746] Re: Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0)

[dinamic]

libprotobuf 3.0.0-7ubuntu3 amd64

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

Title:
  Black Screen, libprotobuf FATAL program was compiled against version
  2.6.1  which is not compatible with the installed version (3.0.0)

Status in Canonical System Image:
  New
Status in protobuf package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 + proposed x86 install

  Black Screen, libprotobuf FATAL program was compiled against version
  2.6.1  which is not compatible with the installed version (3.0.0)

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

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

[Touch-packages] [Bug 1621746] [NEW] Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0)

[dinamic]

Public bug reported:

Ubuntu 16.10 + proposed x86 install

Black Screen, libprotobuf FATAL program was compiled against version
2.6.1  which is not compatible with the installed version (3.0.0)

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

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

** Attachment added: "unity8.log"
   https://bugs.launchpad.net/bugs/1621746/+attachment/4737343/+files/unity8.log

** Also affects: protobuf (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/1621746

Title:
  Black Screen, libprotobuf FATAL program was compiled against version
  2.6.1  which is not compatible with the installed version (3.0.0)

Status in protobuf package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 + proposed x86 install

  Black Screen, libprotobuf FATAL program was compiled against version
  2.6.1  which is not compatible with the installed version (3.0.0)

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

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

[Touch-packages] [Bug 1539614] Re: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

[Launchpad Bug Tracker]

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

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

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

Title:
  unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  No idea what happened. Tried to log into the unity8 desktop session.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Fri Jan 29 14:50:28 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2015-04-30 (273 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   QGuiApplicationPrivate::createPlatformIntegration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1539614] Re: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

** Tags added: yakkety

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

Title:
  unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  No idea what happened. Tried to log into the unity8 desktop session.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Fri Jan 29 14:50:28 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2015-04-30 (273 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   QGuiApplicationPrivate::createPlatformIntegration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1621739] Re: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1539614
   unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

Status in unity8 package in Ubuntu:
  New

Bug description:
  unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Sep  9 08:11:18 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-06-05 (95 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   QGuiApplicationPrivate::createPlatformIntegration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1621215] Re: Sidebar: Other Locations fails to open

[Bug Watch Updater]

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

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  Sidebar: Other Locations fails to open

Status in GTK+:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Fresh daily image from today, also seen on recent install, updated.

  Open nautilus, click on Other Locations
  Nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity
  Date: Wed Sep  7 19:13:51 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+24'"
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621215] Re: Sidebar: Other Locations fails to open

[Jeremy Bicha]

See https://bugzilla.gnome.org/show_bug.cgi?id=769076#c13

The fix in gtk for the glib change is
https://git.gnome.org/browse/gtk+/commit/?id=0c1cc9

** Bug watch added: GNOME Bug Tracker #770550
   https://bugzilla.gnome.org/show_bug.cgi?id=770550

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=770550
   Importance: Unknown
   Status: Unknown

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Low => High

** Bug watch added: GNOME Bug Tracker #769076
   https://bugzilla.gnome.org/show_bug.cgi?id=769076

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

Title:
  Sidebar: Other Locations fails to open

Status in GTK+:
  Unknown
Status in glib2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Fresh daily image from today, also seen on recent install, updated.

  Open nautilus, click on Other Locations
  Nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity
  Date: Wed Sep  7 19:13:51 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+24'"
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621733] Re: windows shows random pattern around edges.

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340
(Ubuntu)

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

Title:
  windows shows random pattern around edges.

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  See the attached image.  This happens after suspend/resume.  I put
  about a minute delay in suspend hook.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.16 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Thu Sep  8 23:35:39 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
   bbswitch, 0.8, 4.4.16, x86_64: installed
   megaraid_sas, 06.810.09.00-rc1, 4.4.16, x86_64: built
   nvidia-340, 340.96, 4.4.16, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848e]
  InstallationDate: Installed on 2016-05-11 (121 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.16 
root=UUID=1e3cfb77-cf43-4ab5-8797-b2c6be8c0805 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: H170M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH170MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  8 22:38:28 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1621215] Re: Sidebar: Other Locations fails to open

[Jeremy Bicha]

I get this error on the command line when I click "Other Locations":

sys:1: Warning: g_cclosure_marshal_VOID__VOID: assertion 'n_param_values
== 1' failed

A no-change rebuild of gtk+3.0 in my PPA didn't help.

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

Title:
  Sidebar: Other Locations fails to open

Status in glib2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Fresh daily image from today, also seen on recent install, updated.

  Open nautilus, click on Other Locations
  Nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity
  Date: Wed Sep  7 19:13:51 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+24'"
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

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

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

[Touch-packages] [Bug 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

[mir-ci-bot]

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

** Changed in: mir
   Status: Fix Released => Fix Committed

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

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

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

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

[Touch-packages] [Bug 1621733] [NEW] windows shows random pattern around edges.

[Yuan Song]

Public bug reported:

See the attached image.  This happens after suspend/resume.  I put about
a minute delay in suspend hook.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.16 x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Thu Sep  8 23:35:39 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
 bbswitch, 0.8, 4.4.16, x86_64: installed
 megaraid_sas, 06.810.09.00-rc1, 4.4.16, x86_64: built
 nvidia-340, 340.96, 4.4.16, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848e]
InstallationDate: Installed on 2016-05-11 (121 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.16 
root=UUID=1e3cfb77-cf43-4ab5-8797-b2c6be8c0805 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: H170M Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH170MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Sep  8 22:38:28 2016
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Attachment added: "screenshot.jpg"
   
https://bugs.launchpad.net/bugs/1621733/+attachment/4737256/+files/screenshot.jpg

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

Title:
  windows shows random pattern around edges.

Status in xorg package in Ubuntu:
  New

Bug description:
  See the attached image.  This happens after suspend/resume.  I put
  about a minute delay in suspend hook.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.16 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRun

[Touch-packages] [Bug 1621733] Re: windows shows random pattern around edges.

[Yuan Song]

the problem disappeared after i did logout/login

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

Title:
  windows shows random pattern around edges.

Status in xorg package in Ubuntu:
  New

Bug description:
  See the attached image.  This happens after suspend/resume.  I put
  about a minute delay in suspend hook.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.16 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Thu Sep  8 23:35:39 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
   bbswitch, 0.8, 4.4.16, x86_64: installed
   megaraid_sas, 06.810.09.00-rc1, 4.4.16, x86_64: built
   nvidia-340, 340.96, 4.4.16, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848e]
  InstallationDate: Installed on 2016-05-11 (121 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.16 
root=UUID=1e3cfb77-cf43-4ab5-8797-b2c6be8c0805 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: H170M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH170MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  8 22:38:28 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Timo Aaltonen]

xmir could probably reuse some of pointer confinement and warping
support posted for xwayland this week

https://patchwork.freedesktop.org/series/12169/

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

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in MirAL:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

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

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

[Touch-packages] [Bug 1621724] [NEW] Blueman disconnected icon is too emphasized

[Dan Dascalescu]

Public bug reported:

I've just installed Blueman and noticed that when BT is off, the icon is
REALLY HIGHLIGHTED.

This may or may not be desired, but I find the convention adopted by the
default Bluetooth system indicator in Ubuntu Unity to make more sense.
In the screenshot, Bluetooth is off, and the default icon is disabled,
while Blueman is BLUE. Turning Bluetooth on makes both icons look grey
on black.

(Side note: it would be nice of Blueman offered an option to replace the
default Bluetooth manager's icon, so we wouldn't see two icons.)

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

** Attachment added: "Blueman disconnected icon is too highlighted.png"
   
https://bugs.launchpad.net/bugs/1621724/+attachment/4737223/+files/Blueman%20disconnected%20icon%20is%20too%20highlighted.png

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

Title:
  Blueman disconnected icon is too emphasized

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've just installed Blueman and noticed that when BT is off, the icon
  is REALLY HIGHLIGHTED.

  This may or may not be desired, but I find the convention adopted by
  the default Bluetooth system indicator in Ubuntu Unity to make more
  sense. In the screenshot, Bluetooth is off, and the default icon is
  disabled, while Blueman is BLUE. Turning Bluetooth on makes both icons
  look grey on black.

  (Side note: it would be nice of Blueman offered an option to replace
  the default Bluetooth manager's icon, so we wouldn't see two icons.)

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

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

[Touch-packages] [Bug 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[Dan Dascalescu]

Or, more annoyingly, bug 1621246

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1299282] Re: need to restart network-manager after resume from suspend

[Dan Dascalescu]

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

Is this a duplicate of bug 1380480 ?

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

Title:
  need to restart network-manager after resume from suspend

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  possibly related to bug #1289884 , but when i resume from suspend none
  of my interfaces (wireless, wired usb, bluetooth connection) are
  visibile to network-manager until i restart it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 28 15:56:30 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-02-24 (32 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  IpRoute:
   default via 10.9.0.1 dev eth0  proto static 
   10.9.0.0/24 dev eth0  proto kernel  scope link  src 10.9.0.38  metric 1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   B0:79:94:D7:0E:0E bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
disabled   enabled disabled

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

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

[Touch-packages] [Bug 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[Dan Dascalescu]

Happy to report that with oem-audio-hda-daily-lts-xenial-dkms -
0.201608190750~ubuntu16.04.1, the problem seems gone so far.

Now if only there was a workaround like this (installing newer drivers)
for another suspend-resume issue, bug 1380480.

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1620934] Re: QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, apps don't render

[Daniel van Vugt]

Sorry for the noise. I don't know which project to target but it's not
Mir, Mesa or Unity8...

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

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

** Changed in: qtubuntu (Ubuntu)
   Importance: Undecided => Critical

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

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

** Changed in: qtmir
   Importance: Undecided => Critical

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

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => Critical

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

** Summary changed:

- QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, apps don't 
render
+ Qt/QML apps don't render any more (logs say "QEGLPlatformContext: 
eglMakeCurrent failed: 3001")

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1621215] Re: Sidebar: Other Locations fails to open

[Jeremy Bicha]

I'm reassigning this from (nautilus and glib2.0) to (gtk+3.0 and
glib2.0) because upgrading gtk+3.0 to 3.21.5 also fixes this and
downgrading back to yakkety's gtk+3.0 brings the bug back.

Therefore, I believe this bug can be fixed in either GTK or glib.

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  Sidebar: Other Locations fails to open

Status in glib2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Fresh daily image from today, also seen on recent install, updated.

  Open nautilus, click on Other Locations
  Nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity
  Date: Wed Sep  7 19:13:51 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+24'"
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Daniel van Vugt]

protobuf (3.0.0-7ubuntu3) yakkety; urgency=medium

  [ Alan Griffiths ]
  * Fix reloading of the shared libraries with dlopen. LP: #1619616.

 -- Matthias Klose   Thu, 08 Sep 2016 14:19:44 +0200

** Changed in: protobuf (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Committed

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

  ~

  The reason this matters:

  The principle downstream from Mir (Unity8) loads Mir as one of a
  number of plugins, several of which use protobuf. That means that
  we're prone to being loaded, unloaded and reloaded and don't have
  control of this.

  We've encountered problems in this scenario before that have been
  traced to protobuf so we have a specific test. But other Unity8
  plugins may encounter the same issue.

  As seen in comment #25 the problem here is entirely down to a change
  in the behavior of libmirprotobuf-lite - it no longer unloads on
  dlclose().

  This is only a problem because there is code (see patch in comment
  #20) that assumes that the library will not be used after a call to
  google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.

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

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

[Touch-packages] [Bug 1620934] Re: QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, all apps, dash are just black windows

[Daniel van Vugt]

Native Mir demos still render correctly. So the problem is specific to
the Ubuntu/Qt toolkit side.

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

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

** Changed in: qtmir
   Status: Incomplete => Confirmed

** Changed in: qtubuntu
   Status: Incomplete => Confirmed

** Summary changed:

- QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, all apps, 
dash are just black windows
+ QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, apps don't 
render

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: qtubuntu
   Importance: Undecided => Critical

** Changed in: unity8 (Ubuntu)
   Importance: High => Critical

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

Title:
  QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, apps
  don't render

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Invalid
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1620934] Re: QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, all apps, dash are just black windows

[Daniel van Vugt]

And after updating now me too (Intel graphics).

unity8-dash.log:
[2016-09-09:10:15:04.738] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.738] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.754] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.754] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.770] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.770] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.786] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.786] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.802] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.802] QEGLPlatformContext: eglMakeCurrent failed: 3001
[2016-09-09:10:15:04.819] QEGLPlatformContext: eglMakeCurrent failed: 3001


** Tags added: black-screen

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

Title:
  QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, apps
  don't render

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Invalid
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1620934] Re: QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, all apps, dash are just black windows

[Daniel van Vugt]

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

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

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

Title:
  QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, all
  apps, dash are just black windows

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in QtMir:
  Incomplete
Status in qtubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1582813] Re: service --status-all always reports upstart managed daemons as running

[Mathew Hodson]

** Description changed:

- [SRU Justification]
- SRU regression.  The change to lsb-base that landed into -updates on the 12th 
of May:
+ [Impact]
+ 
+ This is a regression caused by the change to lsb-base that landed in
+ -updates on the 12th of May:
  
  lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium
  
    * Add 01-upstart-lsb from the upstart package and make
  executing rc.d scripts no-op if there is an upstart
  job for that script. (LP: #1273462)
  
   -- Zhang Hua  Thu, 06 Aug 2015 11:11:16
  -0500
  
- changed the behaviour of init.d scripts to pass through to the
+ This changed the behaviour of init.d scripts to pass through to the
  associated upstart configuration for process management, where packages
  ship both an upstart configuration and an init.d configuration.
  
  This has a rather nasty side effect on 'service --status-all', which
  calls the 'status' method on all installed init.d scripts - this gets
  translated into:
  
    status 
  
  for upstart scripts, which correctly identifies the process as not
  running, but always returns a 0 return code. As a result, --status-all
  incorrectly identifies upstart processes as running even when they are
  not.
  
- [Regression potential]
- Minimal.  This SRU updates the behavior of the lsb init script upstart 
diversion to implement LSB-compliant return values for the 'status' subcommand. 
 It is possible this behavior change will differ from the original behavior of 
some init scripts, but that behavior was undefined.
+ [Test Case]
  
- [Test case]
  1. On an installed trusty system, run this command to get a list of affected 
upstart jobs:
- for job in $(initctl list | awk '/stop\/waiting/ { print $1 }'); do if [ -x 
"/etc/init.d/$job" ]; then echo $job; done
+ for job in $(initctl --system list | awk '/stop\/waiting/ {print $1}'); do if 
[ -x "/etc/init.d/$job" ]; then echo $job; fi; done
+ 
  2. Check the status of this service in the output of service --status-all:
  service --status-all 2>&1 | grep procps
+ 
  3. Confirm that the service is shown as running, despite us knowing above 
that it is not:
-  [ + ]  procps
+  [ + ]  procps
+ 
  4. Install the lsb-base package from trusty-proposed.
+ 
  5. Check the status of this service again in the output of service 
--status-all:
  service --status-all 2>&1 | grep procps
+ 
  6. Confirm that the service is no longer shown as running:
-  [ - ]  procps
+  [ - ]  procps
+ 
+ [Regression Potential]
+ 
+ Minimal. This SRU updates the behavior of the lsb init script upstart
+ diversion to implement LSB-compliant return values for the 'status'
+ subcommand. It is possible this behavior change will differ from the
+ original behavior of some init scripts, but that behavior was undefined.

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

Title:
  service --status-all always reports upstart managed daemons as running

Status in lsb package in Ubuntu:
  Fix Released
Status in lsb source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  This is a regression caused by the change to lsb-base that landed in
  -updates on the 12th of May:

  lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium

    * Add 01-upstart-lsb from the upstart package and make
  executing rc.d scripts no-op if there is an upstart
  job for that script. (LP: #1273462)

   -- Zhang Hua  Thu, 06 Aug 2015 11:11:16
  -0500

  This changed the behaviour of init.d scripts to pass through to the
  associated upstart configuration for process management, where
  packages ship both an upstart configuration and an init.d
  configuration.

  This has a rather nasty side effect on 'service --status-all', which
  calls the 'status' method on all installed init.d scripts - this gets
  translated into:

    status 

  for upstart scripts, which correctly identifies the process as not
  running, but always returns a 0 return code. As a result, --status-all
  incorrectly identifies upstart processes as running even when they are
  not.

  [Test Case]

  1. On an installed trusty system, run this command to get a list of affected 
upstart jobs:
  for job in $(initctl --system list | awk '/stop\/waiting/ {print $1}'); do if 
[ -x "/etc/init.d/$job" ]; then echo $job; fi; done

  2. Check the status of this service in the output of service --status-all:
  service --status-all 2>&1 | grep procps

  3. Confirm that the service is shown as running, despite us knowing above 
that it is not:
   [ + ]  procps

  4. Install the lsb-base package from trusty-proposed.

  5. Check the status of this service again in the output of service 
--status-all:
  service --status-all 2>&1 | grep procps

  6. Confirm that the service is no longer shown as running:
   [ - ]  procps

  [Regression Potential]

  Minimal. This SRU updates the behavior of the lsb init script upstart
  diversion to implement LSB-com

[Touch-packages] [Bug 1621686] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621687] Re: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-gi 3.12.0-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject package in Ubuntu:
  New

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gi 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject
  Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621686] [NEW] package python-gobject-2 2.28.6-12build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Yang]

Public bug reported:

When I install sudo apt-get install im-switch and sudo apt-get install
ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

I've received these errors below:

Errors were encountered while processing:
 python-gi
 python-cairo
 python-gobject-2
 python-gtk2
 python-notify
 ibus
 python-configparser
 python-django
 python-pkg-resources
 python-setuptools
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-gobject-2 2.28.6-12build1
ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Sep  9 09:24:21 2016
DuplicateSignature: package:python-gobject-2:2.28.6-12build1:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-08-18 (21 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: pygobject-2
Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pygobject-2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621687] [NEW] package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Yang]

Public bug reported:

When I install sudo apt-get install im-switch and sudo apt-get install
ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

I've received these errors below:

Errors were encountered while processing:
 python-gi
 python-cairo
 python-gobject-2
 python-gtk2
 python-notify
 ibus
 python-configparser
 python-django
 python-pkg-resources
 python-setuptools
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-gi 3.12.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Sep  9 09:24:21 2016
DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-08-18 (21 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: pygobject
Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package python-gi 3.12.0-1ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in pygobject package in Ubuntu:
  New

Bug description:
  When I install sudo apt-get install im-switch and sudo apt-get install
  ibus ibus-clutter ibus-gtk ibus-gtk3 ibus-qt4.

  I've received these errors below:

  Errors were encountered while processing:
   python-gi
   python-cairo
   python-gobject-2
   python-gtk2
   python-notify
   ibus
   python-configparser
   python-django
   python-pkg-resources
   python-setuptools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gi 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Sep  9 09:24:21 2016
  DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: pygobject
  Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1582813] Re: service --status-all always reports upstart managed daemons as running

[Mathew Hodson]

I verified that this bug affects procps on my Trusty system and the new
lsb-base package fixes it.

$ ls -l /etc/init.d/procps 
-rwxr-xr-x 1 root root 1192 May 27  2013 /etc/init.d/procps
$ initctl --system list | grep procps
procps stop/waiting
$ service --status-all 2>&1 | grep procps
 [ + ]  procps

After installing lsb-base (4.1+Debian11ubuntu6.2), service --status-all
correctly shows that procps is not running.

$ sudo dpkg -i lsb-base_4.1+Debian11ubuntu6.2_all.deb
(Reading database ... 197667 files and directories currently installed.)
Preparing to unpack lsb-base_4.1+Debian11ubuntu6.2_all.deb ...
Unpacking lsb-base (4.1+Debian11ubuntu6.2) over (4.1+Debian11ubuntu6.1) ...
Setting up lsb-base (4.1+Debian11ubuntu6.2) ...
$ initctl --system list | grep procps
procps stop/waiting
$ service --status-all 2>&1 | grep procps
 [ - ]  procps

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

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

Title:
  service --status-all always reports upstart managed daemons as running

Status in lsb package in Ubuntu:
  Fix Released
Status in lsb source package in Trusty:
  Fix Committed

Bug description:
  [SRU Justification]
  SRU regression.  The change to lsb-base that landed into -updates on the 12th 
of May:

  lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium

    * Add 01-upstart-lsb from the upstart package and make
  executing rc.d scripts no-op if there is an upstart
  job for that script. (LP: #1273462)

   -- Zhang Hua  Thu, 06 Aug 2015 11:11:16
  -0500

  changed the behaviour of init.d scripts to pass through to the
  associated upstart configuration for process management, where
  packages ship both an upstart configuration and an init.d
  configuration.

  This has a rather nasty side effect on 'service --status-all', which
  calls the 'status' method on all installed init.d scripts - this gets
  translated into:

    status 

  for upstart scripts, which correctly identifies the process as not
  running, but always returns a 0 return code. As a result, --status-all
  incorrectly identifies upstart processes as running even when they are
  not.

  [Regression potential]
  Minimal.  This SRU updates the behavior of the lsb init script upstart 
diversion to implement LSB-compliant return values for the 'status' subcommand. 
 It is possible this behavior change will differ from the original behavior of 
some init scripts, but that behavior was undefined.

  [Test case]
  1. On an installed trusty system, run this command to get a list of affected 
upstart jobs:
  for job in $(initctl list | awk '/stop\/waiting/ { print $1 }'); do if [ -x 
"/etc/init.d/$job" ]; then echo $job; done
  2. Check the status of this service in the output of service --status-all:
  service --status-all 2>&1 | grep procps
  3. Confirm that the service is shown as running, despite us knowing above 
that it is not:
   [ + ]  procps
  4. Install the lsb-base package from trusty-proposed.
  5. Check the status of this service again in the output of service 
--status-all:
  service --status-all 2>&1 | grep procps
  6. Confirm that the service is no longer shown as running:
   [ - ]  procps

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[pcjason]

Hello,
I am just chiming in to confirm that rebuilding the PulseAudio package without 
the 05XX and 06XX series of patches included resolves this issue on my 
Plantronics BackBeat Go 2 (PLT_BBTGO2) bluetooth headphones.  If there is 
anything that I can do to help debug the issue, please let me know.

-Jason

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1621413] Re: 16.10 default wallpapers

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-wallpapers - 16.10.0-0ubuntu1

---
ubuntu-wallpapers (16.10.0-0ubuntu1) yakkety; urgency=medium

  * New default wallpapers for 16.10 (LP: #1621413)
  * Add a symlink to the default greyscale wallpaper, called
ubuntu-default-greyscale-wallpaper.png (LP: #1592870).

 -- Iain Lane   Thu, 08 Sep 2016 18:56:57 +0100

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Fix Released

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

Title:
  16.10 default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  New

Bug description:
  Attached are the new wallpapers for 16.10.

  They are in PNG_8, PNG_24 and the same for greyscale, along with
  mobile formatted ones.

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

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

[Touch-packages] [Bug 1462596] Re: apt-get autoremove takes quadratically long

[Jarno Suni]

Oh, this is the script that is used for updating grub in conjunction with 
kernel removal: /etc/kernel/postrm.d/zz-update-grub
Anyway, OP meant regenerating the initrd, which is handled by initramfs-tools 
scripts.

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

Title:
  apt-get autoremove takes quadratically long

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

Bug description:
  apt-get autoremove regenerates the initrd after removing each kernel.
  Since you generally call this command only when your boot volume is
  full of old kernels, it seems sub-optimal to regenerate the initrd
  eight times when removing eight kernels.  Could something be done with
  triggers to do a single regeneration of the initrd at the end?

  This is in 14.04

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

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

[Touch-packages] [Bug 1615454] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

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

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 20:05:59 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-06-16 (66 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-22 (0 days ago)

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

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

[Touch-packages] [Bug 765390] Re: Include a weather indicator by default

[Mathew Hodson]

** Summary changed:

- (Regression) indicator-weather is not seeded; cannot be right-click  added 
under Unity
+ Include a weather indicator by default

** Project changed: weather-indicator => ubuntu

** No longer affects: ubuntu

** Project changed: unity => ubuntu

** No longer affects: ubuntu

** No longer affects: indicator-weather (Ubuntu)

** No longer affects: unity (Ubuntu)

** Changed in: ubuntu-meta (Ubuntu)
Milestone: ubuntu-11.10 => None

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-meta (Ubuntu)
   Status: Incomplete => New

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

Title:
  Include a weather indicator by default

Status in Ayatana Design:
  Incomplete
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Binary package hint: unity

  Gnome 2 contained a feature which allowed it to show the local weather
  conditions next to the clock. I personally find this feature extremely
  useful and I check it nearly every time I leave the house or my office
  at work. Arguably it's more to me than the date and time display since
  I wear a watch. This feature appears to be missing in Unity.

  Considering its usefulness, and the fact that Unity lacks the ability
  to add an alternate panel applet to replace it, this feature probably
  should be added to Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.8-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  Date: Mon Apr 18 21:58:52 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to natty on 2011-04-16 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/765390/+subscriptions

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

[Touch-packages] [Bug 1580537] Re: LibreOffice with ambiance theme and breeze icon style is unusable

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+16.10.20160908-0ubuntu1

---
ubuntu-themes (16.10+16.10.20160908-0ubuntu1) yakkety; urgency=medium

  [ Iain Lane ]
  * Fix combobox menus having a black line down the left hand side

 -- i...@orangesquash.org.uk (i...@orangesquash.org.uk)  Thu, 08 Sep
2016 14:43:10 +

** Changed in: ubuntu-themes (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  LibreOffice with ambiance theme and breeze icon style is unusable

Status in libreoffice package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Until today i didn't use LibreOffice on Ubuntu 16.04. I opened it
  today and i see menu/icon bar totally unusable with Ambiance theme and
  default Breeze style. (image attached)

  The version installed is 5.1.2-0ubuntu1.

  I did upgrade from 14.04 to 16.04 with some issues.

  Changing from Breeze to Human is usable but fugly.

  No issue with Radiance theme.

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

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

[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Matthew Exon]

Me too, this didn't allow me to check for updates:

phablet@ubuntu-phablet:~$ stop indicator-network
indicator-network stop/waiting

Here I went to System Settings.  It still said "Connect to the Internet
to check for updates".

phablet@ubuntu-phablet:~$ rm .cache/upstart/indicator-network*
phablet@ubuntu-phablet:~$ start indicator-network
indicator-network start/running, process 12648
phablet@ubuntu-phablet:~$ cat .cache/upstart/indicator-network.log 
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/0" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/1" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/2" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/3" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/4" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/5" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/6" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/7" ((null):0, 
(null))
phablet@ubuntu-phablet:~$

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

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

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

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

[Touch-packages] [Bug 1621215] Re: Sidebar: Other Locations fails to open

[Doug McMahon]

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

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

Title:
  Sidebar: Other Locations fails to open

Status in glib2.0 package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Fresh daily image from today, also seen on recent install, updated.

  Open nautilus, click on Other Locations
  Nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity
  Date: Wed Sep  7 19:13:51 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+24'"
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[Luke Yelavich]

As for backporting the commit, its certianly worth considering. However
yakkety should have a newer kernel when it is released, and that kernel
will be backported to xenial in time, and a new xenial image will be
released with that updated kernel.

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

[Andrea Bernabei]

I had a quick look at this (I have ZERO Go knowledge though), the code seems to 
hang at http://bazaar.launchpad.net/~go-dbus/go-dbus/v1/view/136/dbus.go#L303
i.e. waiting for a reply on replyChan

gdb showed that all threads had an infinite chain of futexsleep() except
one, that was waiting on epollwait(), and above epollwait() that had a
chain of runtime.netpoll().

Hope that helps

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  UPDATE: see comment #5, it turns out it's the haptics plugin doing
  SYNC dbus calls and blocking the UI thread when the dbus service does
  not reply or the replies come with a big delay

  
  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 188741] Re: missing localities in weather applet

[Mathew Hodson]

This should be fixed upstream. If you problems with the locations in
libgweather you can report them on the GNOME Bugzilla. See
https://wiki.gnome.org/Projects/LibGWeather/ImprovingLocations

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

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

Title:
  missing localities in weather applet

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

Bug description:
  Binary package hint: gnome-applets (weather applet in clock applet)

  i noticed that in italian cities Modena and Reggio Emilia are missing, and 
they are quite important cities in their area. i noticed also a typo error: 
there's "marino di massa" instead of the correct name of "marina di massa". can 
that be fixed?
  i need that cities because i live in Reggio Emilia and it is very near to 
Modena and i need a weather applet

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

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

[Touch-packages] [Bug 920749] Re: pam configuration for SSH prevents LANG override

[David Hess]

It seems that commenting out this line:

sessionrequired pam_env.so user_readenv=1
envfile=/etc/default/locale

in /etc/pam.d/sshd is the simplest resolution to this problem.

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

Title:
  pam configuration for SSH prevents LANG override

Status in portable OpenSSH:
  Confirmed
Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Confirmed

Bug description:
  The default /etc/pam.d/sshd configuration has:

  # Read environment variables from /etc/environment and
  # /etc/security/pam_env.conf.
  #auth   required pam_env.so # [1]
  # In Debian 4.0 (etch), locale-related environment variables were moved to
  # /etc/default/locale, so read that as well.
  auth   required pam_env.so envfile=/etc/default/locale

  The default SSH client configuration has "Send LC_*" and the default
  SSH server configuration has "Accept LC_*". The PAM configuration
  prevents any user-overrides for locale settings.

  For example, if /etc/default/locale has:
  LANG=en_US.UTF-8
  LC_COLLATE=C

  Then running "LANG=zh_SG.utf8 LC_COLLATE=en_US.UTF-8 ssh 
myspecialhost.foo.bar.com" yields:
  ubuntu@ip-10-12-15-243:~$ locale
  LANG=en_US.UTF-8
  LC_COLLATE=C
  (output truncated for clarity)

  While having a blank /etc/default/locale yeilds:
  ubuntu@ip-10-12-15-243:~$ locale
  locale: Cannot set LC_ALL to default locale: No such file or directory
  LANG=zh_SG.utf8
  LC_COLLATE=en_US.UTF-8
  (output truncated for clarity)

  I think, although I am not sure, that this is a bug with the default
  configuration. It means that in order for server to accept multple
  languages or LC_* bindings, the system locale default would have to be
  unset. Effectively this is forcing the system default on all users.

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

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

[Touch-packages] [Bug 1621654] Re: package click-apparmor 0.2ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 100

[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 click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1621654

Title:
  package click-apparmor 0.2ubuntu1 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 100

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  it started with broken-package issues re. bind9. i re-installed debian
  repositories but still have issues with apt update...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: click-apparmor 0.2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-95-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Sep  8 18:22:58 2016
  DpkgTerminalLog:
   Removing click-apparmor (0.2ubuntu1) ...
   invoke-rc.d: unknown initscript, /etc/init.d/click-apparmor not found.
   /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
   dpkg: error processing package click-apparmor (--remove):
subprocess installed pre-removal script returned error exit status 100
  DuplicateSignature: package:click-apparmor:0.2ubuntu1:subprocess installed 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 100
  InstallationDate: Installed on 2016-08-21 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.2ubuntu1 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 100
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621656] [NEW] GTK and possibly KDE were very upset with each other

[Aaron Lenentine]

Public bug reported:

I was trying to update the GUI to GTK but I think some KDE got in there
inadvertently. This happened to me a little bit ago as well  I was able
to recover with an install disk once, but there was one time that compiz
went so sideways I had to dump the whole image.

Any assistance would be greatly appreciated. Luckinly I haven't rebooted
yet.  I may still be able to dig these packages out by hand.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Sep  8 15:13:45 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:382a]
InstallationDate: Installed on 2016-08-18 (21 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 80QQ
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=9f188e65-5d07-469d-8393-280f3a754fbd ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN23WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN23WW:bd09/16/2015:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Sep  8 07:24:08 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   19026 
 vendor SDC
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  GTK and possibly KDE were very upset with each other

Status in xorg package in Ubuntu:
  New

Bug description:
  I was trying to update the GUI to GTK but I think some KDE got in
  there inadvertently. This happened to me a little bit ago as well  I
  was able to recover with an install disk once, but there was one time
  that compiz went so sideways I had to dump the whole image.

  Any assistance would be greatly appreciated. Luckinly I haven't
  rebooted yet.  I may still be able to dig these packages out by hand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep  8 15:13:45 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:382a]
  InstallationDate: Installed on 2016-08-18 (21 days ago)
  InstallationMedia: Ubu

[Touch-packages] [Bug 1621654] [NEW] package click-apparmor 0.2ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 100

[steve]

Public bug reported:

it started with broken-package issues re. bind9. i re-installed debian
repositories but still have issues with apt update...

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: click-apparmor 0.2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
Uname: Linux 3.13.0-95-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Thu Sep  8 18:22:58 2016
DpkgTerminalLog:
 Removing click-apparmor (0.2ubuntu1) ...
 invoke-rc.d: unknown initscript, /etc/init.d/click-apparmor not found.
 /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
 dpkg: error processing package click-apparmor (--remove):
  subprocess installed pre-removal script returned error exit status 100
DuplicateSignature: package:click-apparmor:0.2ubuntu1:subprocess installed 
pre-removal script returned error exit status 100
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 100
InstallationDate: Installed on 2016-08-21 (18 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: click-apparmor
Title: package click-apparmor 0.2ubuntu1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 100
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package click-apparmor 0.2ubuntu1 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 100

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  it started with broken-package issues re. bind9. i re-installed debian
  repositories but still have issues with apt update...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: click-apparmor 0.2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-95-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Sep  8 18:22:58 2016
  DpkgTerminalLog:
   Removing click-apparmor (0.2ubuntu1) ...
   invoke-rc.d: unknown initscript, /etc/init.d/click-apparmor not found.
   /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
   dpkg: error processing package click-apparmor (--remove):
subprocess installed pre-removal script returned error exit status 100
  DuplicateSignature: package:click-apparmor:0.2ubuntu1:subprocess installed 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 100
  InstallationDate: Installed on 2016-08-21 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.2ubuntu1 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 100
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 188741] Re: missing localities in weather applet

[Mathew Hodson]

** Bug watch removed: GNOME Bug Tracker #507371
   https://bugzilla.gnome.org/show_bug.cgi?id=507371

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

Title:
  missing localities in weather applet

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

Bug description:
  Binary package hint: gnome-applets (weather applet in clock applet)

  i noticed that in italian cities Modena and Reggio Emilia are missing, and 
they are quite important cities in their area. i noticed also a typo error: 
there's "marino di massa" instead of the correct name of "marina di massa". can 
that be fixed?
  i need that cities because i live in Reggio Emilia and it is very near to 
Modena and i need a weather applet

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

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

[Touch-packages] [Bug 397267] Re: No weather information in gnome panel

[Mathew Hodson]

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

** Bug watch removed: GNOME Bug Tracker #579434
   https://bugzilla.gnome.org/show_bug.cgi?id=579434

** This bug has been marked a duplicate of bug 447570
   Clock applet no longer shows weather in panel

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

Title:
  No weather information in gnome panel

Status in libgweather package in Ubuntu:
  Confirmed

Bug description:
  This bug is not new. But I opening it because when I tried to reopen the bug 
which which people thought was fixed (but which still persisted for me), 
someone advised that I rather open a new one. The bug I'm referring to is 
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/216197. 
  This bug relates to the world clock applet in the gnome-panel which also 
shows weather when configured to do so.
  Before 8.10 I could see the weather conditions of both manually added 
locations and locations which were already in the list (whether I was behind 
proxy or directly connected to internet). After upgrading to intripid only 
locations in the list worked I did nto get weather report for location which I 
manually added by inserting their name/longitude/latitude manually. Now in 
jaunty none works when I'm working behind a proxy- but this is a different 
upstream bug (http://bugzilla.gnome.org/show_bug.cgi?id=579434).
  The reason I am opening this bug is that the clock applet is unable to show 
whether of manually added locations even when one is directly connected to the 
internet. This used to work fine in hardy both when directly connected to the 
internet and when connected from behind a proxy (which doesn't work any more, 
even for locations in the list).

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

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

[Touch-packages] [Bug 1265588] Re: Please Use Another Weather Channel

[Mathew Hodson]

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

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

Title:
  Please Use Another Weather Channel

Status in libgweather package in Ubuntu:
  New

Bug description:
  Current channel doesn't offer wide city selection and it doesn't
  update regularly. (Sometimes the current weather stays same for days.)

  Accuweather, Yahoo Weather, Google Weather, The Weather Channel,
  Freemeteo

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

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

[Touch-packages] [Bug 1615864] Re: Screen resolution not saved after reboot or logout and back in

[GeeMac]

Hello Christopher,

Can you give me an idea why this is marked as "Low" Importance?
This issue was not in 14.04.  I have reinstalled 16.04 LTS twice now after the 
failed update from 14.04 and have the same issue. I feel that this issue is 
more important then leaving this as low grade issue.  There are others having 
the issue but have not posted it as a bug, but they have in some forums.  I 
have been that route and also have been in the IRC.
I can only guess at two things; my MB / graphics chipset is old and 16 is not 
backward compatible or there is a bug in 16.04. I'm thinking the latter.
I have tried all that I could think of along with your suggestions. Also I 
can't think of any other information that I can give you to help with this 
situation.  I would hate to have to go backwards to 14.04. 
I'm disabled here so I am available almost 24/7 if you want to investigate this 
further 
If you have the time I can set up a TeamViewer session so you can look around.

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

Title:
  Screen resolution not saved after reboot or logout and back in

Status in xorg package in Ubuntu:
  New

Bug description:
  The issue is that Ubuntu 16.04 does not save or read the saved screen
  resolution settings of 1920x1080 from my Vizio 42 inch TV HDMI
  connected to my computer. When booting into the desktop the mouse
  pointer is small as if in 1920x1080 but then changes to a larger
  pointer then the resolution is then 1280x720 which seems to what 16.04
  falls back to.

  The TV reports the proper information under xrandr.
  gee@HTPC:~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096
  VGA-0 disconnected (normal left inverted right x axis y axis)
  TV-0 disconnected (normal left inverted right x axis y axis)
  HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 980mm x 580mm
 1280x720  60.00 +  59.94
 1920x1080 59.9459.94*   60.0560.0050.04
 720x576   50.0050.08
 720x480   59.94
 640x480   59.93

  WORKAROUND: Type at the terminal:
  xrandr -s 1920x1080

  ---
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.131  Sun Nov  8 21:43:33 
PST 2015
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed
   nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / 
nForce 630a] [1462:349f]
  InstallationDate: Installed on 2016-08-20 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp.
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7349
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=377930d2-4053-4a10-96ef-8cac652e4c24 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 03/19/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CaptiveWorks CW-3000HD V2.37
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7349
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCaptiveWorksCW-3000HDV2.37:bd03/19/2008:svnMSI:pnMS-7349:pvr1.0:rvnMSI:rnMS-7349:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.na

[Touch-packages] [Bug 1355813] Re: Interface MTU management across MAAS/juju

[Richard Harding]

** Changed in: juju-core (Ubuntu)
   Status: Triaged => 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/1355813

Title:
  Interface MTU management across MAAS/juju

Status in juju-core:
  Fix Released
Status in MAAS:
  Triaged
Status in juju-core package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Context:

  juju + MAAS deployed OpenStack environment, misc services deployed
  under LXC on the bootstrap node, interfaces configured for jumbo
  frames - note that I had to manually set the LXC container interfaces
  to mtu 9000 before the bridge would do the same.

  Action:

  Reboot one of the containers; MTU on br0 resets from 9000 -> 1500.

  This feels like more of a 'we need a better way to orchestrate MTU
  configuration across different services' so raising tasks for MAAS and
  Juju as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.5-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Tue Aug 12 13:26:00 2014
  KernLog:

  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions

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

[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

[Pat McGowan]

It seems to be deadlocked after calling messagebus.Call
@enwei can you take a look, set two alarms in the clock app for the same minute 
to reproduce it

** Changed in: usensord (Ubuntu)
 Assignee: (unassigned) => Zhang Enwei (zhangew401)

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  UPDATE: see comment #5, it turns out it's the haptics plugin doing
  SYNC dbus calls and blocking the UI thread when the dbus service does
  not reply or the replies come with a big delay

  
  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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

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

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

    $KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

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

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

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

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

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

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

[Touch-packages] [Bug 1615455] Re: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Launchpad Bug Tracker]

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  sant-64@sant64-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy  libglib2.0-0:amd64
  libglib2.0-0:
Installed: 2.48.1-1~ubuntu16.04.1
Candidate: 2.48.1-1~ubuntu16.04.1
Version table:
   *** 2.48.1-1~ubuntu16.04.1 500
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.48.0-1ubuntu4 500
  500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  Installation/upgradation

  4) What happened instead
  Error as desibed above

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 20:19:49 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-09-19 (337 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: glib2.0
  Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

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

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

[Touch-packages] [Bug 1621413] Re: 16.10 default wallpapers

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu-wallpapers

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

Title:
  16.10 default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Attached are the new wallpapers for 16.10.

  They are in PNG_8, PNG_24 and the same for greyscale, along with
  mobile formatted ones.

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

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

[Touch-packages] [Bug 1595485] Re: packages to remove from yakkety

[LocutusOfBorg]

https://launchpad.net/ubuntu/+source/insighttoolkit4/4.10.0-dfsg1-3ubuntu1/+build/10712957
insightoolkit4 on ppc64el grow too much for buildd space.
Debian has no binary on ppc64el and maintaining them is difficult.
Please remove it and its reverse-dependencies, in case somebody increases the 
space, they will enter again the archive

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

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

Title:
  packages to remove from yakkety

Status in flightgear package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Fix Released
Status in fslview package in Ubuntu:
  Fix Released
Status in gnome-video-arcade package in Ubuntu:
  Fix Released
Status in insighttoolkit package in Ubuntu:
  Fix Released
Status in insighttoolkit4 package in Ubuntu:
  New
Status in iva package in Ubuntu:
  Fix Released
Status in ldc package in Ubuntu:
  New
Status in libpng package in Ubuntu:
  Fix Released
Status in mame package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in python-pysam package in Ubuntu:
  Fix Released
Status in runit package in Ubuntu:
  Fix Released
Status in samtools package in Ubuntu:
  Fix Released
Status in simgear package in Ubuntu:
  Invalid
Status in singular package in Ubuntu:
  Fix Released
Status in stacks package in Ubuntu:
  Fix Released
Status in vcmi package in Ubuntu:
  Fix Released
Status in vmtk package in Ubuntu:
  Fix Released
Status in vtk package in Ubuntu:
  Fix Released
Status in fpc package in Debian:
  Fix Released

Bug description:
  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16

  no reverse dependencies I can see
  2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)

  just removing vmtk/powerpc should allow its removal too

  3) vtk
  Superseded by vtk6

  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)

  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)

  removed in Debian too

  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore

  6) singular [armhf]
  removed in Debian too

  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480

  8) mame [ppc64el]
  sandness on that arch, removed in Debian

  9) flightgear [armhf]
  I don't care about simgear/armhf, because it is unlikely for such a game to 
run on thar architecture.

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

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

[Touch-packages] [Bug 1621595] Re: package libqt5webkit5 5.5.1*dfsg-2ubuntu1 failed to install/upgrade: не удалось скопировать извлечённые данные «./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в «

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

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

** Tags added: corrupted-package

** Changed in: qtwebkit-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  package libqt5webkit5 5.5.1*dfsg-2ubuntu1 failed to install/upgrade:
  не удалось скопировать извлечённые данные «./usr/lib/x86_64-linux-
  gnu/libQt5WebKit.so.5.5.1» в «/usr/lib/x86_64-linux-
  gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец файла или
  потока

Status in qtwebkit-opensource-src package in Ubuntu:
  Invalid

Bug description:
  from app manager

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5webkit5 5.5.1*dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libqt5webkit5: Install
   libqt5webkit5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Sep  8 21:57:33 2016
  ErrorMessage: не удалось скопировать извлечённые данные 
«./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в 
«/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец 
файла или потока
  InstallationDate: Installed on 2016-08-24 (14 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qtwebkit-opensource-src
  Title: package libqt5webkit5 5.5.1*dfsg-2ubuntu1 failed to install/upgrade: 
не удалось скопировать извлечённые данные 
«./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в 
«/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец 
файла или потока
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621554] Re: package perl-modules 5.20.2-2 [modified: usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to install/upgrade: cannot copy extracted data for './usr/share

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

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

** Tags added: corrupted-package

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

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

Title:
  package perl-modules 5.20.2-2 [modified:
  usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to
  install/upgrade: cannot copy extracted data for
  './usr/share/perl/5.20.2/pod/perldiag.pod' to
  '/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of
  file or stream

Status in perl package in Ubuntu:
  Invalid

Bug description:
  update fails mentioning a problem with perl-modules 5.20.2-2ubuntu0.1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: perl-modules 5.20.2-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  Date: Thu Sep  8 17:37:14 2016
  DuplicateSignature: package:perl-modules:5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm]:cannot copy extracted 
data for './usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2016-09-08 (0 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4
  SourcePackage: perl
  Title: package perl-modules 5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[Joseph Salisbury]

Per comment #10, the bug was fixed somewhere between upstream 4.4 and
4.6.  To narrow it down further, so we can perform a reverse bisect can
you test the 4.5 final kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/


If 4.5 is good, maybe test 4.5-rc1:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-wily/


To perform the reverse bisect, we need to identify the last bad kernel version 
and the first good one.

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Au

[Touch-packages] [Bug 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[Dan Dascalescu]

Correct link for upgrading ALSA:
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1620799] Re: Desktop too big

[William Hughes]

This may be a Google Chrome problem. Third install (with whole disk
wipe) of 16.04.1 without google-chrome and the menu / launchpad have
returned. Installed chromium and so far still works OK. I have to try
this on my other computer to see if this is it.

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

Title:
  Desktop too big

Status in xorg package in Ubuntu:
  New

Bug description:
  When I first installe Ubuntu 16.04.01 64 bit Desktop was OK except for
  some screen flicker while using chrome. Tried updating the Intel Video
  Drivers then Desktop got way to big. Ended up reinstalling OS and
  fixed desktop, until computer went to sleep and the Desktop got too
  big agaain. Desktop is so large I can't see menus or launcher. All I
  can see is purple background. Able to right click to bring up terminal
  or screen adjustment. Nothing works so far. Lenovo LT 1952P Monitor.
  Lenovo M58 Computer Intel Q45 or Q43 video chip. Intel Duo Core
  Processor.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep  6 14:32:33 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller 
[17aa:3049]
 Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller 
[17aa:3049]
  InstallationDate: Installed on 2016-09-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=9c6de8f8-ff75-443e-8028-4c33848e883e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT77AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT77AUS:bd05/07/2012:svnLENOVO:pn7359AEU:pvrThinkCentreM58:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 7359AEU
  dmi.product.version: ThinkCentre M58
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep  6 14:30:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2448 
   vendor LEN
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1621611] [NEW] Network Error after OTA update

[Joe Borg]

Public bug reported:

This doubt a webbrowser-app issue, but there was no "Networking" option
on https://wiki.ubuntu.com/Avengers

After updating my BQ E4.5 to Ubuntu 15.04 OTA-12, I get intermittent
network errors.  This is most obvious when opening the "webbrowser-app".
I frequently get presented with "Network Error".

Is there anything I can do to debug where this is coming from?  I've
tried factory resetting, with no luck.

Please let me know if there is anything details I can get from the phone
that would help.

Thanks

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Network Error after OTA update

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  This doubt a webbrowser-app issue, but there was no "Networking"
  option on https://wiki.ubuntu.com/Avengers

  After updating my BQ E4.5 to Ubuntu 15.04 OTA-12, I get intermittent
  network errors.  This is most obvious when opening the "webbrowser-
  app".  I frequently get presented with "Network Error".

  Is there anything I can do to debug where this is coming from?  I've
  tried factory resetting, with no luck.

  Please let me know if there is anything details I can get from the
  phone that would help.

  Thanks

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

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

[Touch-packages] [Bug 1570478] Re: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Update: Qt 5.6.1 and UITK 20160716:

  13 failures which MUST be fixed:
    dpr2
    dpr3
    performance

  --- original report ---
  Considerably less than on amd64 (bug #1560004), but still some now seen with 
the new UITK 20160412 and the latest Qt builds:

  1 failures which MUST be fixed:
    tst_performance

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/performance/performance
  [...]
  #7  0x77c32034 in UCTheme::PaletteConfig::restorePalette() 
(this=0xeb8160) at ./src/Ubuntu/UbuntuToolkit/uctheme.cpp:278
  #8  0x77c2ebf3 in UCTheme::~UCTheme() (this=0xeb8160, 
__in_chrg=) at ./src/Ubuntu/UbuntuToolkit/uctheme_p.h:125

  https://launchpadlibrarian.net/253810125/buildlog_ubuntu-xenial-armhf
  .ubuntu-ui-
  toolkit_1.3.1938+16.04.20160412build1~xenial1~qt560~1_BUILDING.txt.gz

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

[Jonas G. Drange]

One of the threads deadlocks inside the haptic handler (which is 100
lines of go, called every time the user e.g. presses the OSK), on a call
to dbus (messageBus.Call()). However, dbus seems to function fine, this
looks like an internal failure in usensord.

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  UPDATE: see comment #5, it turns out it's the haptics plugin doing
  SYNC dbus calls and blocking the UI thread when the dbus service does
  not reply or the replies come with a big delay

  
  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

-- 
Mailing list: https://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 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Steven Wheeler]

Hi, I have done as you suggest but nothing has changed, screenshot of the
log file attached.

Regards,

[image: screenshot20160908_194824951.png]Steven

On Thu, 8 Sep 2016 at 17:15 Antti Kaijanmäki 
wrote:

> Now, to get past the "Connect to the Internet to check for updates" in
> system settings, could you try to issue the following command:
>
> $ stop indicator-network
>
> Then open system settings and see if it allows you to check for updates.
> Right now there should not be any, as OTA-13 has not been released yet,
> but this should let you at least receive updates in the future when we
> pinpoint and fix the underlying problem.
>
> Then next, please remove any old indicator-network logs:
>
> $ rm  .cache/upstart/indicator-network*
>
> And start indicator-network again:
>
> $ start indicator-network
>
> After this, please attach the latest indicator-network log to this bug
> report, and also check if the indicator appears. The log should be
> .cache/upstart/indicator-network.log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1615474
>
> Title:
>   Network Indicator / Connectivity-API is not accessible
>
> Status in Canonical System Image:
>   Incomplete
> Status in indicator-network package in Ubuntu:
>   In Progress
>
> Bug description:
>   Sometime in the last few days my phone lost the ability to connect to
>   wifi networks and the network indicator at the top has stopped
>   working.
>
>   Currently between "Bluetooth" and "Sound" I have a gear icon and the
>   caption "indicator-network".  When I select it, the rest of the screen
>   is blank.  There are no settings available and no way to connect to a
>   wifi network.
>
>   On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
>   "Previous networks".  But below that the page is just white, there is
>   no way to select a wifi network.
>
>   Rebooting the phone doesn't seem to fix the problem.
>
>   Given that this is an MX4 and therefore the USB port doesn't work, and
>   there's no SD card slot, there's vanishingly few ways to get data in
>   and out of this phone now.  If there's a solution to the problem, it's
>   going to have to involve something other than updating system
>   software.
>
>   Current system software is Ubuntu 15.05 (OTA-12).
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions
>


** Attachment added: "screenshot20160908_194824951.png"
   
https://bugs.launchpad.net/bugs/1615474/+attachment/4737004/+files/screenshot20160908_194824951.png

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

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

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

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

[Touch-packages] [Bug 1570478] Re: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6

[Launchpad Bug Tracker]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/propertyChangeFix

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

Title:
  Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Update: Qt 5.6.1 and UITK 20160716:

  13 failures which MUST be fixed:
    dpr2
    dpr3
    performance

  --- original report ---
  Considerably less than on amd64 (bug #1560004), but still some now seen with 
the new UITK 20160412 and the latest Qt builds:

  1 failures which MUST be fixed:
    tst_performance

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/performance/performance
  [...]
  #7  0x77c32034 in UCTheme::PaletteConfig::restorePalette() 
(this=0xeb8160) at ./src/Ubuntu/UbuntuToolkit/uctheme.cpp:278
  #8  0x77c2ebf3 in UCTheme::~UCTheme() (this=0xeb8160, 
__in_chrg=) at ./src/Ubuntu/UbuntuToolkit/uctheme_p.h:125

  https://launchpadlibrarian.net/253810125/buildlog_ubuntu-xenial-armhf
  .ubuntu-ui-
  toolkit_1.3.1938+16.04.20160412build1~xenial1~qt560~1_BUILDING.txt.gz

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1621595] [NEW] package libqt5webkit5 5.5.1*dfsg-2ubuntu1 failed to install/upgrade: не удалось скопировать извлечённые данные «./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в

[KKuznetsov]

Public bug reported:

from app manager

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5webkit5 5.5.1*dfsg-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 libqt5webkit5: Install
 libqt5webkit5: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Sep  8 21:57:33 2016
ErrorMessage: не удалось скопировать извлечённые данные 
«./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в 
«/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец 
файла или потока
InstallationDate: Installed on 2016-08-24 (14 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: qtwebkit-opensource-src
Title: package libqt5webkit5 5.5.1*dfsg-2ubuntu1 failed to install/upgrade: не 
удалось скопировать извлечённые данные 
«./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в 
«/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец 
файла или потока
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtwebkit-opensource-src (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 qtwebkit-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1621595

Title:
  package libqt5webkit5 5.5.1*dfsg-2ubuntu1 failed to install/upgrade:
  не удалось скопировать извлечённые данные «./usr/lib/x86_64-linux-
  gnu/libQt5WebKit.so.5.5.1» в «/usr/lib/x86_64-linux-
  gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец файла или
  потока

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  from app manager

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5webkit5 5.5.1*dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libqt5webkit5: Install
   libqt5webkit5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Sep  8 21:57:33 2016
  ErrorMessage: не удалось скопировать извлечённые данные 
«./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в 
«/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец 
файла или потока
  InstallationDate: Installed on 2016-08-24 (14 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qtwebkit-opensource-src
  Title: package libqt5webkit5 5.5.1*dfsg-2ubuntu1 failed to install/upgrade: 
не удалось скопировать извлечённые данные 
«./usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1» в 
«/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.5.1.dpkg-new»: неожиданный конец 
файла или потока
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Mathieu Trudel-Lapierre]

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

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

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

Status in MAAS:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in klibc package in Ubuntu:
  New
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure
  the network.

  ipconfig does not support dhcpv6.  See: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=627164

  Anyone wanting to netboot in an ipv6-only environment is affected.

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

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

[Touch-packages] [Bug 1269175] Re: lvresize, lvextend, and fsadm attempt to fsck a mounted filesystem

[reem]

** Changed in: lvm2 (Ubuntu)
 Assignee: (unassigned) => reem (reemhassan333)

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

Title:
  lvresize,lvextend, and fsadm attempt to fsck a mounted filesystem

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Precise:
  Fix Released

Bug description:
  [Impact]

   * Potential filesystem corruption

   * The above is remedied by backporting a fix from upstream lvm2 that
  allows fsadm to return 3 on attempts to check a mounted filesystem.
  This allows lvextend and lvresize to proceed without a fsck when the
  filesystem is mounted.

  [Test Case]

  1. Run lvextend -L +...G -r 
  2. Obtain a message saying:
  WARNING!!! The filesystem is mounted. If you continue you ***WILL***
  cause ***SEVERE*** filesystem damage.

  Do you really want to continue?

  3. Reply no, and lvextend or lvresize proceed anyway, freaking out any user 
who does not recognize the above message as having come from fsck.
  4. Reply yes, and possibly corrupt your filesystem.

  [Regression Potential]

   * There is regression potential for scripts that depend on fsadm
  return values.  I did search for other references to "fsadm" within
  the lvm2 package, but found none.

   * Possible regressions may manifest themselves as other filesystem or
  lvm2 tools failing.

  [Other Info]

   * All 4 patches that were backported for this fix exist upstreams
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance


  


  
  Steps to Reproduce:
  1. Run lvextend -L +...G -r 
  2. Obtain a message saying:
  WARNING!!! The filesystem is mounted. If you continue you ***WILL***
  cause ***SEVERE*** filesystem damage.

  Do you really want to continue?

  3. Reply no, and lvextend or lvresize proceed anyway, freaking out any user 
who does not recognize the above message as having come from fsck.
  4. Reply yes, and possibly corrupt your filesystem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lvm2 2.02.66-4ubuntu7.3
  ProcVersionSignature: User Name 3.2.0-57.87-generic 3.2.52
  Uname: Linux 3.2.0-57-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Jan 14 22:33:52 2014
  Ec2AMI: ami-05c2
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: cpu1-ram1-disk50-ephemeral20
  Ec2Kernel: aki-0548
  Ec2Ramdisk: ari-0548
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[George Velimachitis]

I confirm the above findings on latest Linux Mint available kernel
4.4.0.36 however I also noticed

sudo DRI_PRIME=1 glxgears works

whereas

DRI_PRIME=1 glxgears gives a blank screen.

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubun

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Ian Weisser]

There seems a lot of confusion in this bug report about which pieces of
the system work together to cause this problem, and which pieces should
be responsible for fixing it.

Marking kernels as eligible for autoremoval is done by apt. The apt
package provides /etc/kernel/postinst.d/apt-auto-removal, which sets the
rules for marking kernel packages eligible for autoremoval. If you
discover a system that keeps more than three kernels (and isn't already
broken), run 'apt autoremove' manually. If the system still has more
than three kernels, then see if you can figure out why and then file a
bug against Apt.

But apt only marks. Apt doesn't actually pull the trigger and run an
autoremove.

Compounding the problem is another issue with apt: Apt in 16.04 and
earlier queues autoremoval instead of running it first (or last...or
scheduled). This is what makes broken systems harder to fix. Out-of-
space hits before autoremove.

Unattended-Upgrades prior to 16.04, if the option is enabled, merely
runs 'apt autoremove' via aptdaemon. U-U does not check nor care what
packages need to be removed. U-U does not check nor care if the system
is LVM/Encrypted or has a small separate /boot partition. None of that
is part of U-U's job.

U-U developers in 16.04 addressed this problem (even though it's
arguably not U-U's problem) by checking if packages are already marked
eligible-for-autoremove at the beginning of the run. If so, it
autoremoves them before doing anything else. Again, U-U doesn't care
about which packages happen to be marked, or wheter the system has a
small /boot partition.

In 16.04, the problem is undeniably fixed. The additional functionality
of U-U has prevented stale kernels from accumulating on all my test
systems. However, developers have understandably shown little interest
in backporting that particular fix.

And there are other options to integrate the fix better into apt itself
instead of U-U. For example, aptdaemon does seem to have queue
management tools - it should be possible to move an 'autoremove' to the
head of queue (incidentally making fixes much easier). Or we can add
another kernel hook file to /etc/kernel/postinst.d/ to trigger an
autoremove upon kernel installs (instead of U-U's daily check). Or we
can add a startup/cron.daily service that simply checks for existence of
a small /boot partition and runs autoremove before (or after) the daily
apt update. Or we can have aptdaemon catch out-of-space errors (instead
of simply passing them), run autoremove, and then try the install again.

Almost none of these possible solutions would be implemented in
Unattended Upgrades.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

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.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+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 1621571] [NEW] curl crashes due to "curl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libhogweed.so.4: undefined symbol: __gmpn_cnd_add_n"

[Karl-Philipp Richter]

Public bug reported:

For example `curl --insecure -O
https://gforge.inria.fr/frs/download.php/file/33524/CGAL-4.4.tar.bz2`
crashes 100 % of times with this error message and return code 127.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: curl 7.47.0-1ubuntu2.1
Uname: Linux 4.7.2-040702-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep  8 20:00:27 2016
InstallationDate: Installed on 2015-12-12 (271 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: curl
UpgradeStatus: Upgraded to xenial on 2016-03-14 (178 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  curl crashes due to "curl: symbol lookup error: /usr/lib/x86_64-linux-
  gnu/libhogweed.so.4: undefined symbol: __gmpn_cnd_add_n"

Status in curl package in Ubuntu:
  New

Bug description:
  For example `curl --insecure -O
  https://gforge.inria.fr/frs/download.php/file/33524/CGAL-4.4.tar.bz2`
  crashes 100 % of times with this error message and return code 127.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: curl 7.47.0-1ubuntu2.1
  Uname: Linux 4.7.2-040702-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  8 20:00:27 2016
  InstallationDate: Installed on 2015-12-12 (271 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: curl
  UpgradeStatus: Upgraded to xenial on 2016-03-14 (178 days ago)

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

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

[Touch-packages] [Bug 1621413] Re: 16.10 default wallpapers

[Iain Lane]

I uploaded the PNG-24 version; can replace it with a better quality one
once it arrives

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

Title:
  16.10 default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Attached are the new wallpapers for 16.10.

  They are in PNG_8, PNG_24 and the same for greyscale, along with
  mobile formatted ones.

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

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

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

[Simon Déziel]

** Description changed:

  /etc/rsyslog.conf contains:
  
-   $KLogPermitNonKernelFacility on
+   $KLogPermitNonKernelFacility on
  
  But this no longer supported and trigger this log message:
  
-  Jan  5 08:56:16 simon-laptop rsyslogd-: command
+  Jan  5 08:56:16 simon-laptop rsyslogd-: command
  'KLogPermitNonKernelFacility' is currently not permitted - did you
  already set it via a RainerScript command (v6+ config)? [v8.14.0 try
  http://www.rsyslog.com/e/ ]
  
  Error  is described as "legacy parameter no longer permitted".
+ 
+ This legacy parameter causes config syntax checks (rsyslogd -N1) to
+ fail.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.14.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan  6 15:47:15 2016
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

** Patch removed: "lp1531622-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736967/+files/lp1531622-yakkety.debdiff

** Patch removed: "lp1531622-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736968/+files/lp1531622-xenial.debdiff

** Patch added: "lp1531622-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736971/+files/lp1531622-yakkety.debdiff

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

    $KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

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

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

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

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

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

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

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

[Simon Déziel]

I updated the 2 debdiffs to remove useless space in the config file.

** Patch added: "lp1531622-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736972/+files/lp1531622-xenial.debdiff

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

    $KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

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

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

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

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

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

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

[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init

[Daniel d'Andrada]

libc6  2.21-0ubuntu4.0.1

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

Title:
  deadlock in lttng_ust_init

Status in QtMir:
  Triaged
Status in lttng-ust package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Triaged
Status in ust package in Ubuntu:
  New

Bug description:
  Happens when running tests for
  https://code.launchpad.net/~dandrader/qtmir/content-hub-
  clipboard/+merge/303863 by CI.

  This is the backtrace of where it gets stuck:
  #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 
<_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51
  #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, 
the_map=) at dl-tls.c:778
  #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158
  #3 0x in lttng_ust_init () at lttng-ust-comm.c:369
  #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481
  #5 0x in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72
  #6 0x in _dl_init (env=, argv=, 
argc=, l=) at dl-init.c:30
  #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, 
env=0xbefff3dc) at dl-init.c:120
  #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3

  It gets stuck during initialization, more specifically, inside
  lttng_fixup_urcu_bp_tls()

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

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

[Touch-packages] [Bug 1620634] Re: Hangs to build on ppc64el

[Ken VanDine]

I've been experiencing this on the PPA builders for more than just
content-hub.  I've seen it with qtmir as well.  I think there's a bigger
issue with the builders.

** Changed in: content-hub (Ubuntu)
   Status: New => Invalid

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

Title:
  Hangs to build on ppc64el

Status in content-hub package in Ubuntu:
  Invalid

Bug description:
  It seems impossible to get ppc64el build to finish on yakkety. The
  build seems to fail but hangs forever (until cancelling the build job)
  probably because there's a test related thread loose and not killed.

  --
  gdk_pixbuf-2.0 -lapparmor 
-Wl,-rpath,/<>/content-hub-0.2+16.10.20160830/build/src/com/ubuntu/content:
  make[3]: Leaving directory 
'/<>/content-hub-0.2+16.10.20160830/build'
  [100%] Built target content-hub-send
  make[2]: Leaving directory 
'/<>/content-hub-0.2+16.10.20160830/build'
  /usr/bin/cmake -E cmake_progress_start 
/<>/content-hub-0.2+16.10.20160830/build/CMakeFiles 0
  make[1]: Leaving directory 
'/<>/content-hub-0.2+16.10.20160830/build'
     debian/rules override_dh_auto_test
  make[1]: Entering directory '/<>/content-hub-0.2+16.10.20160830'
  dbus-test-runner -t make -p "-C" -p "build/tests/acceptance-tests" -p test
  DBus daemon: 
unix:abstract=/tmp/dbus-O9sC0cCtE9,guid=19a0b33017166ee2a4c9d4ff57cec6e9
  task-0: Started with PID: 11044
  task-0: make[2]: Entering directory 
'/<>/content-hub-0.2+16.10.20160830/build/tests/acceptance-tests'
  task-0: Running tests...
  task-0: /usr/bin/ctest --force-new-ctest-process
  task-0: Test project 
/<>/content-hub-0.2+16.10.20160830/build/tests/acceptance-tests
  task-0: Start 1: app_hub_communication_default_source
  task-0: 1/10 Test #1: app_hub_communication_default_source ... Passed 0.03 sec
  task-0: Start 2: app_hub_communication_known_sources
  task-0: 2/10 Test #2: app_hub_communication_known_sources  Passed 0.03 sec
  task-0: Start 3: app_hub_communication_stores

  ** (dbus-test-runner:11039): WARNING **: Timing out at maximum wait of
  30 seconds.

  (dbus-test-runner:11039): libdbustest-CRITICAL **: dbus_test_service_run: 
assertion 'all_tasks(service, all_tasks_finished_helper, NULL)' failed
  task-0: Shutting down
  DBus daemon: Shutdown
  debian/rules:15: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 255
  make[1]: Leaving directory '/<>/content-hub-0.2+16.10.20160830'
  debian/rules:7: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

  --

  This happens despite 5+ retries. Also i386 and armhf needed a retry
  but they did eventually finish.

  This prevents getting any content-hub landing to yakkety properly.

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

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

[Touch-packages] [Bug 1621546] Re: package click-apparmor 0.3.13.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Steve Beattie]

This seems to be the problem (from the dpkg terminal log):

Configurando click-apparmor (0.3.13.1) ...
Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
dpkg: erro ao processar o pacote click-apparmor (--configure):
 sub-processo script post-installation instalado retornou estado de saída de 
erro 1

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

Title:
  package click-apparmor 0.3.13.1 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  Packge is crached.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click-apparmor 0.3.13.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  8 13:31:57 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-07-17 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.13.1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init

[Mathieu Desnoyers]

What is your glibc version ? You provided your libglib version which is
unrelated to lttng-ust.

Or are you using Android bionic libc... ?

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

Title:
  deadlock in lttng_ust_init

Status in QtMir:
  Triaged
Status in lttng-ust package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Triaged
Status in ust package in Ubuntu:
  New

Bug description:
  Happens when running tests for
  https://code.launchpad.net/~dandrader/qtmir/content-hub-
  clipboard/+merge/303863 by CI.

  This is the backtrace of where it gets stuck:
  #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 
<_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51
  #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, 
the_map=) at dl-tls.c:778
  #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158
  #3 0x in lttng_ust_init () at lttng-ust-comm.c:369
  #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481
  #5 0x in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72
  #6 0x in _dl_init (env=, argv=, 
argc=, l=) at dl-init.c:30
  #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, 
env=0xbefff3dc) at dl-init.c:120
  #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3

  It gets stuck during initialization, more specifically, inside
  lttng_fixup_urcu_bp_tls()

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

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

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

[Simon Déziel]

I'm not sure if the version is good for the Xenial debdiff, let me know
if there is anything.

** Patch added: "lp1531622-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736968/+files/lp1531622-xenial.debdiff

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

$KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

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

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

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

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

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

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

[Simon Déziel]

** Patch added: "lp1531622-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736967/+files/lp1531622-yakkety.debdiff

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

$KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

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

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

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

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

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

[Touch-packages] [Bug 1611859] Re: Keyboard layout isn't applied within wizard or in dash after wizard

[Lukáš Tinkl]

** Branch unlinked: lp:~lukas-kde/unity8/moveWindowByAltLMB

** Branch linked: lp:~lukas-kde/unity8/edgeMaximize

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

Title:
  Keyboard layout isn't applied within wizard or in dash after wizard

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In https://requests.ci-train.ubuntu.com/#/ticket/1771

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout within the wizard
  * and in the dash after completing the wizard

  Current:
  * layout is only applied on first app focus change

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160810.2-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-001]
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 10 19:04:24 2016
  InstallationDate: Installed on 2016-05-06 (95 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621554] Re: package perl-modules 5.20.2-2 [modified: usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to install/upgrade: cannot copy extracted data for './usr/share

[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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1621554

Title:
  package perl-modules 5.20.2-2 [modified:
  usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to
  install/upgrade: cannot copy extracted data for
  './usr/share/perl/5.20.2/pod/perldiag.pod' to
  '/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of
  file or stream

Status in perl package in Ubuntu:
  New

Bug description:
  update fails mentioning a problem with perl-modules 5.20.2-2ubuntu0.1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: perl-modules 5.20.2-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  Date: Thu Sep  8 17:37:14 2016
  DuplicateSignature: package:perl-modules:5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm]:cannot copy extracted 
data for './usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2016-09-08 (0 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4
  SourcePackage: perl
  Title: package perl-modules 5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621555] [NEW] Brother HL-L2340DW not printing either USB or WiFi MATE 16.04.1 LTSE 16.04 LTS

[Fred Yates]

Public bug reported:

The system recognizes the printer, it prints the file, shows the job has
been sent, logs it to the spooler, shows it as completed, but nothing is
printed. This happens for both USB and WiFi

I have tried through launchpad to get help
https://answers.launchpad.net/ubuntu/+question/385656 and also have a
support request into Brother. The printer prints fine over WiFi through
Windows 7 Pro.

Also tried on Ubuntu MATE Community: -- https://ubuntu-mate.community/t
/help-installng-brother-hl-l2340dw/8734

I can access http://localhost:631 just fine.

Last, inside a VM running Windows 7 I can print to a different WiFi HP
printer.

Located in Oregon.
Desperately trying to leave MS.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Sep  8 09:37:24 2016
InstallationDate: Installed on 2016-08-01 (38 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Lpstat:
 device for HL-L2340D-USB: 
usb://Brother/HL-L2340D%20series?serial=U63879M5N386362
 device for HLL2340D: socket://10.0.0.9:9100
MachineType: LENOVO 20138
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HL-L2340D-USB.ppd', 
'/etc/cups/ppd/HLL2340D.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HL-L2340D-USB.ppd: Permission denied
 grep: /etc/cups/ppd/HLL2340D.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=6d56d615-bf89-4bdb-96cb-f48f4c294730 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 5ECN96WW(V9.01)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G780
dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN96WW(V9.01):bd03/14/2013:svnLENOVO:pn20138:pvrLenovoG780:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG780:
dmi.product.name: 20138
dmi.product.version: Lenovo G780
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  Brother HL-L2340DW not printing either USB or WiFi MATE 16.04.1 LTSE
  16.04 LTS

Status in cups package in Ubuntu:
  New

Bug description:
  The system recognizes the printer, it prints the file, shows the job
  has been sent, logs it to the spooler, shows it as completed, but
  nothing is printed. This happens for both USB and WiFi

  I have tried through launchpad to get help
  https://answers.launchpad.net/ubuntu/+question/385656 and also have a
  support request into Brother. The printer prints fine over WiFi
  through Windows 7 Pro.

  Also tried on Ubuntu MATE Community: -- https://ubuntu-
  mate.community/t/help-installng-brother-hl-l2340dw/8734

  I can access http://localhost:631 just fine.

  Last, inside a VM running Windows 7 I can print to a different WiFi HP
  printer.

  Located in Oregon.
  Desperately trying to leave MS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Sep  8 09:37:24 2016
  InstallationDate: Installed on 2016-08-01 (38 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat:
   device for HL-L2340D-USB: 
usb://Brother/HL-L2340D%20series?serial=U63879M5N386362
   device for HLL2340D: socket://10.0.0.9:9100
  MachineType: LENOVO 20138
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HL-L2340D-USB.ppd', '/etc/cups/ppd/HLL2340D.ppd'] failed with 
exit code 2: grep: /etc/cups/ppd/HL-L2340D-USB.ppd: Permission denied
   grep: /etc/cups/ppd/HLL2340D.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=6d56d615-bf89-4bdb-96cb-f48f4c294730 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN96WW(V9.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G780
  dmi.modalias: 
dmi:bvnLENOVO:

[Touch-packages] [Bug 1620557] Re: weather.noaa.gov was shut down

[Jeremy Bicha]

Don't worry about marking this a duplicate. We repurposed the other bug
to just track the libmateweather SRU instead.

Do you want to upload the fix for Trusty too?

gnome-applets in Precise is technically no longer supported which I
think was the only thing using this library for actual weather data
there so I'm not personally going to do a precise upload but someone
else could if they wanted to.

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

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

** Changed in: libgweather (Ubuntu Trusty)
   Status: New => Triaged

** Tags added: precise trusty yakkety

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

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Trusty:
  Triaged
Status in libgweather source package in Xenial:
  In Progress

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

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

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

[Touch-packages] [Bug 1621554] [NEW] package perl-modules 5.20.2-2 [modified: usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to install/upgrade: cannot copy extracted data for './usr/sha

[Will]

Public bug reported:

update fails mentioning a problem with perl-modules 5.20.2-2ubuntu0.1

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: perl-modules 5.20.2-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
Date: Thu Sep  8 17:37:14 2016
DuplicateSignature: package:perl-modules:5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm]:cannot copy extracted 
data for './usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
ErrorMessage: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
InstallationDate: Installed on 2016-09-08 (0 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1.1
 apt  1.0.9.7ubuntu4
SourcePackage: perl
Title: package perl-modules 5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 vivid

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

Title:
  package perl-modules 5.20.2-2 [modified:
  usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to
  install/upgrade: cannot copy extracted data for
  './usr/share/perl/5.20.2/pod/perldiag.pod' to
  '/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of
  file or stream

Status in perl package in Ubuntu:
  New

Bug description:
  update fails mentioning a problem with perl-modules 5.20.2-2ubuntu0.1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: perl-modules 5.20.2-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  Date: Thu Sep  8 17:37:14 2016
  DuplicateSignature: package:perl-modules:5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm]:cannot copy extracted 
data for './usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2016-09-08 (0 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4
  SourcePackage: perl
  Title: package perl-modules 5.20.2-2 [modified: 
usr/share/perl/5.20.2/Locale/Codes/Language_Codes.pm] failed to 
install/upgrade: cannot copy extracted data for 
'./usr/share/perl/5.20.2/pod/perldiag.pod' to 
'/usr/share/perl/5.20.2/pod/perldiag.pod.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621546] [NEW] package click-apparmor 0.3.13.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[mjanuario]

Public bug reported:

Packge is crached.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: click-apparmor 0.3.13.1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Sep  8 13:31:57 2016
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
InstallationDate: Installed on 2016-07-17 (52 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: click-apparmor
Title: package click-apparmor 0.3.13.1 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: click-apparmor (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 click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1621546

Title:
  package click-apparmor 0.3.13.1 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  Packge is crached.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click-apparmor 0.3.13.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  8 13:31:57 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-07-17 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.13.1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1590005] Re: activeFocusOnTab is ignored when Button is embedded inside ListItem in a horizontal ListView

[Zsombor Egri]

Input from UX: if a ListItem is used in a horizontal oriented ListView,
the horizontal navigation keys should focus the ListItems themselves,
and eventual active content focusing should be omitted no matter what is
the activeFocusOnTab setting is.

The https://code.launchpad.net/~zsombi/ubuntu-ui-
toolkit/dontFocusDisabledLi branch seem to fix this issue as well.

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/dontFocusDisabledLi

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  activeFocusOnTab is ignored when Button is embedded inside ListItem in
  a horizontal ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Run this code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  model: 10
  orientation: ListView.Horizontal
  delegate: ListItem {
  width: units.gu(5)
  height: units.gu(5)
  Button {
  activeFocusOnTab: false
  anchors {
  fill: parent
  margins: units.gu(1)
  }
  text: "Button #" + index
  }
  }
  }
  }

  Use TAB to select the first ListItem in the list. Pressing the LEFT
  arrow after that will put the focus on the Button in the first
  ListItem (you can see the focus outline changing).

  The same happens when using keyboard navigation to go to the last
  ListItem and then pressing the RIGHT cursor key.

  I could not reproduce the issue with a vertical ListView.

  This gives problems for the new Toolbar with scrolling icons inside
  it, because there I am wrapping an AbstractButton inside a ListItem in
  order to be able to get cursor key navigation until this bug is fixed:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1573616

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

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

[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

[Pat McGowan]

Verified it does not trigger a deadlock on stable using the approach of
two simultaneous alarms

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  UPDATE: see comment #5, it turns out it's the haptics plugin doing
  SYNC dbus calls and blocking the UI thread when the dbus service does
  not reply or the replies come with a big delay

  
  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1462596] Re: apt-get autoremove takes quadratically long

[Jarno Suni]

Oh, you can do something now: you can set update-grub executable (found
by command `which update-grub`) not executable by `sudo chmod -x`
temporarily, and then remove the kernels, and then restore the state of
the file by `sudo chmod +x` and finally run `sudo update-grub` manually.
This is because /etc/kernel/postinst.d/zz-update-grub exits, if the
executable is not found (at least in 14.04 and 16.04).

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

Title:
  apt-get autoremove takes quadratically long

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

Bug description:
  apt-get autoremove regenerates the initrd after removing each kernel.
  Since you generally call this command only when your boot volume is
  full of old kernels, it seems sub-optimal to regenerate the initrd
  eight times when removing eight kernels.  Could something be done with
  triggers to do a single regeneration of the initrd at the end?

  This is in 14.04

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

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

[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Antti Kaijanmäki]

Now, to get past the "Connect to the Internet to check for updates" in
system settings, could you try to issue the following command:

$ stop indicator-network

Then open system settings and see if it allows you to check for updates.
Right now there should not be any, as OTA-13 has not been released yet,
but this should let you at least receive updates in the future when we
pinpoint and fix the underlying problem.

Then next, please remove any old indicator-network logs:

$ rm  .cache/upstart/indicator-network*

And start indicator-network again:

$ start indicator-network

After this, please attach the latest indicator-network log to this bug
report, and also check if the indicator appears. The log should be
.cache/upstart/indicator-network.log

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

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

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

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

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

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-09-08 11:53 EDT---
Hello Canonical.

May we please have a status update on this bug?

Thanks.

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file: /lib/udev/rules.d/60-evdev.rules
  Reading rules file: /lib/udev/rules.d/60-gnupg.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-input.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-sto

[Touch-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 0.6.40-2ubuntu11.2

---
accountsservice (0.6.40-2ubuntu11.2) xenial; urgency=medium

  * debian/patches/0014-libsystemd.patch:
- Backport patch to adapt to systemd 209, fixes missing "Switch User"
  functionality in GNOME Shell (LP: #1577049)
  * debian/control:
- Bump minimum systemd for above patch

 -- Jeremy Bicha   Thu, 25 Aug 2016 21:27:44 -0400

** Changed in: accountsservice (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Committed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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

[Touch-packages] [Bug 1577049] Update Released

[Brian Murray]

The verification of the Stable Release Update for accountsservice has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Committed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.6

---
isc-dhcp (4.2.4-7ubuntu12.6) trusty; urgency=medium

  * Fixed missing broadcast flag for Infiniband interfaces (LP: #1529815)
- added:
  + d/p/dhcp-4.2.4-dhclient-options-changed.patch

 -- Rafael David Tinoco   Tue, 07 Jun 2016
15:29:50 +0200

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in isc-dhcp source package in Wily:
  Won't Fix
Status in isc-dhcp source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves.
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

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

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

[Touch-packages] [Bug 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[Ekimia]

Have updated my 16.04 ( upgraded from 15.10 if that matters) with

oem-audio-hda-daily-dkms_0.201609080501~ubuntu16.04.1_all.deb

After after Reboot + suspend, the problem is gone.

A bit ashamed I did not try this before.

We now need to isolate the exact commit in alsa that fixes this and
backport it ?

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

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

[Steve Langasek]

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

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

Status in MAAS:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in klibc package in Ubuntu:
  New
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure
  the network.

  ipconfig does not support dhcpv6.  See: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=627164

  Anyone wanting to netboot in an ipv6-only environment is affected.

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

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