date:20160925

Maybe fixed? Not yet sure if that branch just landed is sufficient.

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

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

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

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

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

[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2016-09-25 Thread mir-ci-bot

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

** Changed in: mir
   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/1570698

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

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

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

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

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

[Touch-packages] [Bug 1574005] Re: HDMI connection not working on Ubuntu 16.04 and GeForce GTX 960M

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

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

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

Title:
  HDMI connection not working on Ubuntu 16.04 and GeForce GTX 960M

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The bug is described in question #291879 . After upgrading to Ubuntu
  16.04 the HDMI monitor is no longer detected.

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

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

[Touch-packages] [Bug 1582144] Re: Unity 8 scopes possible to get vertically squeezed with Qt 5.6

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

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

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

Title:
  Unity 8 scopes possible to get vertically squeezed with Qt 5.6

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  With bug #1565763 fixed the scopes display well by default. However,
  it's possible to get into situation where the icons are vertically
  squished instead, see attachment.

  A way to reproduct it is swiping from down to up (for scrolling) when
  the device / Unity 8 is busy like directly after boot. Instead of
  scrolling down after the Unity 8 is free to process events again (or
  for whatever reason it's temporarily stuck), all the icons are
  displayed as in the attachment instead. See video for how to reproduce
  (at times).

  Once it has happened, I've not found a way to untangle them again
  other than restarting Unity 8.

  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/unity8/+bug/1582144/+subscriptions

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

[Touch-packages] [Bug 1627582] Re: systemd-resolved crashed with SIGABRT in log_assert_failed()

2016-09-25 Thread Apport retracing service

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

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 #1607884, 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/1627582/+attachment/4748632/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-resolved crashed with SIGABRT in log_assert_failed()

Status in systemd package in Ubuntu:
  New

Bug description:
  I got this crach just after logged in after the last kernel upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6git1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Sep 25 18:53:47 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-11-28 (1032 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6530
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=409b2104-0062-403c-8b6b-f07948051f69 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGABRT in log_assert_failed()
  UpgradeStatus: Upgraded to yakkety on 2016-08-31 (25 days ago)
  UserGroups:
   
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd08/27/2013:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1626435] Re: Keyboard layout not applied on the shell

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

** Changed in: mir
   Status: New => In Progress

** Changed in: mir
   Importance: Undecided => High

** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

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

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

** Changed in: mir
Milestone: None => 0.25.0

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

Title:
  Keyboard layout not applied on the shell

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Split out from bug #1611859:

  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 in the wizard
  * and in snap decisions

  Current:
  * you can only use us layout in the shell

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-078]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:07:47 2016
  InstallationDate: Installed on 2016-05-06 (138 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/1626435/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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()

Still happening in Mir 0.24.0 using NBS. See: bug 1627311

-- 
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 Released
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 1627311] Re: Mir client crashes with SIGABRT in send_message() from release_buffer_stream

This appears to be a recurrence of bug 1506358, which we closed thinking
it was fixed by the introduction of NBS. Obviously not fixed, now the
same crash is happening in a slightly different way with NBS.

** Summary changed:

- Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
+ Mir client crashes with SIGABRT in send_message() from release_buffer_stream

** Changed in: xorg-server (Ubuntu)
   Importance: Medium => High

** Summary changed:

- Mir client crashes with SIGABRT in send_message() from release_buffer_stream
+ Xmir crashes with SIGABRT in send_message() from release_buffer_stream (on a 
cursor)

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

** Changed in: mir
   Importance: Undecided => High

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Tags added: cursor unity8-desktop

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

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

** Summary changed:

- Xmir crashes with SIGABRT in send_message() from release_buffer_stream (on a 
cursor)
+ Xmir crashes with SIGABRT in send_message() from release_buffer_stream() from 
FreeCursor()

** Summary changed:

- Xmir crashes with SIGABRT in send_message() from release_buffer_stream() from 
FreeCursor()
+ Xmir crashed with SIGABRT in send_message() from release_buffer_stream() from 
FreeCursor()

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

Title:
  Xmir crashed with SIGABRT in send_message() from
  release_buffer_stream() from FreeCursor()

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  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.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2

[Touch-packages] [Bug 1575614] Re: [SRU]Can't select secret key for TLS auth for 802.1X authentication

2016-09-25 Thread Fedor

As a workaround, you can drag and drop your private key directly from
Files (Nautilus)

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

Title:
  [SRU]Can't select secret key for TLS auth for 802.1X authentication

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Users cannot select TLS certificate when connecting to a network that
  requires TLS type 802.1X authentication

  [Test case]
  STR:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  For wifi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  [Regression Potential]
  The fix is quite straight forward and the possibility of causing regression 
is limited.

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

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

[Touch-packages] [Bug 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename

2016-09-25 Thread Michi Henning

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

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

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

Title:
  Recognize album artwork with "Album title.supported_extension"
  filename

Status in Ubuntu Music App:
  Invalid
Status in mediascanner2 package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  Invalid

Bug description:
  At this time, Music currently supports the following filenames for local 
album artwork (i.e. album artwork which is stored locally in the same folder as 
the music for which it should be associated):
  * cover
  * album
  * albumart
  * .folder
  * folder

  These filenames must have one of the following extensions:
  * jpeg
  * jpg
  * png

  However most applications and programs also support (provided it matches the 
folder name and metadata album title exactly):
  Album Title.supported_extension

  I propose that "Album Title.supported_extension" be added to the list
  of recognized filenames for album artwork, to bring Music into line
  with most other music players...

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1627252/+subscriptions

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (i.e. menus and tooltips)

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  Unity8 can't correctly display multi-surface apps (i.e. menus and
  tooltips)

Status in Canonical System Image:
  Triaged
Status in QtMir:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1627013] Re: Qt Drag and Drop across two windows of the same app is not detected

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

** Tags added: dnd

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

Title:
  Qt Drag and Drop across two windows of the same app is not detected

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  What happened:
  1) Installed multi-window silo for the webbrowser [0] and installed demo app 
[1]
  2) Launched the multi window drag and drop example app, note sometimes the 
windows are spawned on top of each other, so you may need to move one to see 
both
  3) Attempt to drag one of the red boxes into the centre of the other window
  4) Notice that on unity7 the centre of the window turns green whereas on 
unity8 nothing happens
  5) Notice on unity7 that when the mouse is released the red box is moved into 
that window

  What I expected to happen:
  On unity8 for it to act the same as unity7, for the drag handle to work 
correctly and for the window droparea detection to work.

  Note at step 3 while dragging the box that on unity7 a handle
  correctly appears near the mouse and follows it, whereas on unity8 it
  spawns a window with the image for the handle but it doesn't follow
  the mouse. I am assuming this is linked to other existing bugs within
  unity8/mir where showing menus appear in separate windows? But I'm not
  sure which bug that is?

  I am currently assuming that either the increased security of Mir
  between windows is preventing the Qt drag system from being to detect
  when the mouse is over another window? (even though they are the same
  app)  Or is the issue that this functionality has not been implemented
  yet?

  I have the a xenial desktop with the stable overlay and the multi-
  window silo for the webbrowser [0]. The demo mini-app I have linked to
  this bug and can be found at [1]. Let me know if you need help running
  it.

  The use case for this scenario, is moving tabs in the webbrowser
  between multiple windows and dragging a tab out of a window to spawn a
  new window.

  0 - 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-084/+packages
  1 - https://code.launchpad.net/~ahayzen/+junk/multi-window-dnd-cpp-001

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

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

[Touch-packages] [Bug 1607185] Re: It's difficult to close the launcher without tapping on something you didn't want to

That's just standard practice - mark all other tasks as Incomplete while
waiting to hear from the design team (the Ubuntu UX task).

Certainly the bug is valid with several of us complaining about it, but
if an issue is deemed at all contentious then the developers will
generally defer to the design team for input.

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

Title:
  It's difficult to close the launcher without tapping on something you
  didn't want to

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

Bug description:
  It's difficult to close the launcher without tapping on something you
  didn't want to.

  Test case:
1. Open an app.
2. Open the launcher swiping from the left.
3. Close the launcher without triggering any touches in the app.

  Expected: Tapping outside the launcher will close it without touches reaching 
the app.
  Observed: Tapping outside the launcher closes it but unwanted touches reach 
the app.

  You can close the launcher by swiping it back off the side, but it's
  too small to do that very easily without also accidentally touching
  the top-most app.

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

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

[Touch-packages] [Bug 1626344] Re: [enhancement] Add microseconds to unity8.log prefix

It appears you're right. Not possible to fix.

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

** Changed in: unity8 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [enhancement] Add microseconds to unity8.log prefix

Status in Canonical System Image:
  Won't Fix
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Please add microseconds to the logging prefix used in unity8.log (and
  more?). They are often useful for debugging and would make things look
  more consistent with Mir. For example, I just saw this in a user's bug
  report:

  [2016-09-22:02:30:46.345] qtmir.mir: SessionListener::SessionListener - this= 
SessionListener(0xf17ece3c)
  [2016-09-22:02:30:46.345] qtmir.mir: 
PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0xf17ecffc)
  [2016-09-22 02:30:46.345807] mirserver: Using nested cursor
  [2016-09-22:02:30:46.346] qtmir.mir: 
MirWindowManagerImpl::MirWindowManagerImpl
  [2016-09-22 02:30:46.346617] mirserver: Initial display configuration:
  [2016-09-22 02:30:46.349255] mirserver:   0.1: LVDS 10,0" 135x216mm
  [2016-09-22 02:30:46.349405] mirserver:Current mode 1200x1920 56,90Hz
  [2016-09-22 02:30:46.349470] mirserver:Preferred mode 1200x1920 
56,90Hz
  [2016-09-22 02:30:46.349526] mirserver:Logical position +0+0
  [2016-09-22 02:30:46.349588] mirserver:   0.2: unused DisplayPort
  [2016-09-22 02:30:46.349644] mirserver:   0.3: unused (null)
  [2016-09-22 02:30:46.350821] mirserver: Mir version 0.24.0
  [2016-09-22:02:30:46.350] qtmir.screens: QtCompositor::start
  [2016-09-22:02:30:46.413] qtmir.screens: ScreensModel::update

  We could certainly make the date/time formats the same...

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

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

[Touch-packages] [Bug 1627281] Re: Double tapping the title bar in desktop mode does not maximize the app window

Double clicking still works on desktop using a mouse.

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

Title:
  Double tapping the title bar in desktop mode does not maximize the app
  window

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

Bug description:
  bq M10 rc-proposed r196
  I've noticed the double tapping the title bar of an app does no longer works 
to maximize the app window. It works though if the window is maximized to 
return it to the previous size.

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

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

[Touch-packages] [Bug 1569227] Re: Mouse & Touchpad second slider is not labelled

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Mouse & Touchpad second slider is not labelled

Status in Canonical System Image:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid

Bug description:
  Mouse & Touchpad second slider is not labelled

  It seems to control the mouse wheel speed though.

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

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

[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

There is a setting for this in Unity8 now. It's the second (unnamed) scrollbar 
under:
System Settings > Mouse & Touchpad > Mouse

However there are two bugs related to that scroll bar:
  1. It's not yet labelled (bug 1569227)
  2. It doesn't go high enough (missing fix: 
https://code.launchpad.net/~vanvugt/ubuntu-system-settings/fix-1607240/+merge/301606)

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions

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

[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-25 Thread Michi Henning

Changes are in silo 1991.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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

[Touch-packages] [Bug 1613561] Re: [MIR] thumbnailer

2016-09-25 Thread Michi Henning

Tests are disabled for on arm64, ppc64, and ppc64le for yakkety and
xenial. That's where we've seen failures, and we don't particularly care
about these arches at the moment.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (i.e. menus and tooltips)

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

** Changed in: canonical-devices-system-image
Milestone: None => 14

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

Title:
  Unity8 can't correctly display multi-surface apps (i.e. menus and
  tooltips)

Status in Canonical System Image:
  Triaged
Status in QtMir:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

-- 
Mailing list: https://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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-25 Thread Luke Yelavich

affects ubuntu/pulseaudio
 assignee themuso


** Changed in: pulseaudio (Ubuntu)
 Assignee: Simon Fels (morphis) => Luke Yelavich (themuso)

-- 
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 1627562] [NEW] PulseaudioSound[2537]: segfault at 0 ip 000000000143a244 sp 00007fafacff72e0 error 4 in spotify[400000+2134000]

2016-09-25 Thread Cristian Aravena Romero

Public bug reported:

[ 6081.211245] PulseaudioSound[2537]: segfault at 0 ip 0143a244
sp 7fafacff72e0 error 4 in spotify[40+2134000]

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-16.17-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-16-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   9271 F...m pulseaudio
 /dev/snd/controlC0:  caravena   9271 F pulseaudio
CurrentDesktop: GNOME
Date: Sun Sep 25 22:02:48 2016
InstallationDate: Installed on 2015-07-26 (427 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  PulseaudioSound[2537]: segfault at 0 ip 0143a244 sp
  7fafacff72e0 error 4 in spotify[40+2134000]

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [ 6081.211245] PulseaudioSound[2537]: segfault at 0 ip
  0143a244 sp 7fafacff72e0 error 4 in
  spotify[40+2134000]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-16.17-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-16-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   9271 F...m pulseaudio
   /dev/snd/controlC0:  caravena   9271 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 25 22:02:48 2016
  InstallationDate: Installed on 2015-07-26 (427 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: https://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 1616413] Re: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all

2016-09-25 Thread Luke Yelavich

So there is no 3.5mm connectinos at the rear?

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

Title:
  [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I am not getting any sound at all from my Dell Optiplex 7040 (running
  Ubuntu 16.04).

  The volume control icon is showing up next to the clock, and I am able
  to change the volume levels: but this has no effect. There is
  absolutely NO sound at all.

  In Settings -> Output, no devices are listed. Strangely enough, aplay
  -l results in:

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3234 Analog [ALC3234 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0

  which indicates that the sound card is getting detected. I tried

  sudo alsa force-reload

  following which I rebooted. That doesn't fix the problem. I opened
  alsamixer: it is detecting the sound card perfectly and nothing is
  muted. Still, there is no audio. I then tried the following:

  sudo apt-get remove --purge alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio
  sudo alsa force-reload

  And still there is no audio. I'd be really grateful if you could look
  into this. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  suvam  4522 F pulseaudio
suvam  5594 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Aug 24 15:59:21 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-02-12 (193 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  suvam  4522 F pulseaudio
suvam  5594 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-08-11 (13 days ago)
  dmi.bios.date: 12/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0HD5W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/04/2015:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7040
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1627511] Re: package libqtcore4 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches verschieden von andere

2016-09-25 Thread Steve Langasek

This shows an upgrade failure in the libqtcore4 package, not in skype.

** Package changed: skype (Ubuntu) => qt4-x11 (Ubuntu)

** Changed in: qt4-x11 (Ubuntu)
   Status: Incomplete => New

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade: Versuch,
  gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben,
  welches verschieden von anderen Instanzen des Paketes libqtcore4:i386
  ist

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  I don't know whether/why there's a problem at all. After booting the
  system, it showed that there was an error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 25 11:05:03 2016
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libqtcore4:i386 ist
  InstallationDate: Installed on 2015-10-16 (345 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libqtcore4:i386 ist
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (20 days ago)

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

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

[Touch-packages] [Bug 1025973] Re: ureadahead appears to violate Apple patent 7607000

2016-09-25 Thread Ken Sharp

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

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

Title:
  ureadahead appears to violate Apple patent 7607000

Status in ureadahead package in Ubuntu:
  Invalid

Bug description:
  It appears that ureadahead violates Apple patent 7607000.

  See http://www.google.com/patents/US7607000

  Is there prior art? The patent in question was filed September 25,
  2009.

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

-- 
Mailing list: https://launchpad.net/~touch-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?)

2016-09-25 Thread Kathy Reid

@vooze: This worked PERFECTLY. The PLT_BBTGO2 is now paired and
connected successfully and I can adjust controls in the Sound settings
panel. I had to run

sudo pactl load-module module-bluetooth-discover

after I'd added the PPA, updated pulseaudio and rebooted.

A huge thank you for all your help.

Do you need specifics on the hardware I'm using?

Kind regards,
Kathy

-- 
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 1627511] [NEW] package libqtcore4 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches verschieden von ande

You have been subscribed to a public bug:

I don't know whether/why there's a problem at all. After booting the
system, it showed that there was an error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqtcore4 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Sep 25 11:05:03 2016
ErrorMessage: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libqtcore4:i386 ist
InstallationDate: Installed on 2015-10-16 (345 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: qt4-x11
Title: package libqtcore4 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libqtcore4:i386 ist
UpgradeStatus: Upgraded to xenial on 2016-09-04 (20 days ago)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial
-- 
package libqtcore4 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libqtcore4:i386 ist
https://bugs.launchpad.net/bugs/1627511
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qt4-x11 in Ubuntu.

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

[Touch-packages] [Bug 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group

2016-09-25 Thread Dongdong88

To xin (pursue) :

  you also can download procps-3.3.10 source code and compile it in
ubuntu16.04, then you could replace /bin/kill with the binary you
compile . in this way you dont need copy the libprocps.so.3 .

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

Title:
  /bin/kill in ubuntu16.04 has bug in killing process group

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

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

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

[Touch-packages] [Bug 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

jap1968, it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  dmesg output :

  [ 8815.416923] [drm] stuck on render ring
  [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8815.419462] drm/i915: Resetting chip after gpu hang
  [ 8821.417592] [drm] stuck on render ring
  [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8821.420108] drm/i915: Resetting chip after gpu hang
  [ 8827.430254] [drm] stuck on render ring
  [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8827.432786] drm/i915: Resetting chip after gpu hang
  [ 8833.418862] [drm] stuck on render ring
  [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8833.421551] drm/i915: Resetting chip after gpu hang
  [ 8839.419503] [drm] stuck on render ring
  [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8839.422060] drm/i915: Resetting chip after gpu hang
  [ 8845.432118] [drm] stuck on render ring
  [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8845.434799] drm/i915: Resetting chip after gpu hang
  [ 8851.432751] [drm] stuck on render ring
  [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8851.435224] drm/i915: Resetting chip after gpu hang
  [ 8857.457381] [drm] stuck on render ring
  [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8857.459883] drm/i915: Resetting chip after gpu hang
  [ 8863.458003] [drm] stuck on render ring
  [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8863.460640] drm/i915: Resetting chip after gpu hang
  [ 8869.458654] [drm] stuck on render ring
  [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too 
fast, banning!
  [ 8869.461116] drm/i915: Resetting chip after gpu hang
  [ 8875.435238] [drm] stuck on render ring
  [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8875.437697] drm/i915: Resetting chip after gpu hang
  [ 8881.447863] [drm] stuck on render ring
  [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8881.450331] drm/i915: Resetting chip after gpu hang
  [ 8887.436497] [drm] stuck on render ring
  [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8887.438961] drm/i915: Resetting chip after gpu hang
  [ 8893.437078] [drm] stuck on render ring
  [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8893.439562] drm/i915: Resetting chip after gpu hang

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-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: Sun Apr 24 15:57:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2002]
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine:

[Touch-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2016-09-25 Thread David Cesarino de Sousa

I can confirm that what I said before isn't valid anymore. What appeared
to be fixed in 15.10 has resurfaced in 16.04, and now I can't fix it
even by myself.

Oh well... I just gave up on suspending.

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in blueman package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in blueman source package in Precise:
  Confirmed
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in blueman source package in Quantal:
  Invalid
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in blueman source package in Raring:
  Invalid
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2)
  ~ % apt-cache policy bluez
  bluez:
    Installed: 4.98-2ubuntu7
    Candidate: 4.98-2ubuntu7
    Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions

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

[Touch-packages] [Bug 1627546] [NEW] use safe mount for usb devices

2016-09-25 Thread god

Public bug reported:

For years ubuntu has been plagued by horrible user experience when dealing with 
usb drives:
- user forget to unmount device
- fs is corrupted
- user insert device back and is overwritten/lost

Luckily solution is finally available: ubuntu should use systemd-mount for all 
usb devices so they are
- mount only when it's really necessary
- aggressively unmounted to prevent data loss
- fscked before mounting

This will lead to much nicer situation where new users will not blame
ubuntu anymore for data loss.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: 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/1627546

Title:
  use safe mount for usb devices

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  For years ubuntu has been plagued by horrible user experience when dealing 
with usb drives:
  - user forget to unmount device
  - fs is corrupted
  - user insert device back and is overwritten/lost

  Luckily solution is finally available: ubuntu should use systemd-mount for 
all usb devices so they are
  - mount only when it's really necessary
  - aggressively unmounted to prevent data loss
  - fscked before mounting

  This will lead to much nicer situation where new users will not blame
  ubuntu anymore for data loss.

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

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

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

2016-09-25 Thread Peter Bittner

@Pat @Victor Alright, so it's a hardware issue: I've installed Android
and there are the same issues with the screen turning black. Then I'm
done with this bug report.

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

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in vegetahd:
  New
Status in powerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

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

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

[Touch-packages] [Bug 1557761] Re: rc-sysinit run twice due to failsafe race condition

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

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

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

Title:
  rc-sysinit run twice due to failsafe race condition

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We have noticed that after the upgrade from 12.04 to 14.04, daemons
  that are started from rc.d scripts are sometimes being run twice.

  We've tracked this down to a race condition in the failsafe script.
  Here is the normal sequence of events:

  Mar 16 10:39:37 failsafe: Failsafe of 120 seconds reached.
  Mar 16 10:39:37 failsafe: net-device-up start event emitted
  Mar 16 10:39:37 failsafe: starting failsafe script
  Mar 16 10:39:37 failsafe: sleeping in failsafe script
  Mar 16 10:39:37 failsafe: static-network-up start event emitted
  Mar 16 10:39:37 failsafe: rc-sysinit starting event emitted
  Mar 16 10:39:37 kernel: [2.056689] init: failsafe main process (642) 
killed by TERM signal

  (Note the inaccurate message about the 120 seconds being reached which
  is actually logged immediately on boot - best just to ignore that.
  The TERM warning is also harmless - that is the normal result.)

  Here is what we see on a bad boot, where the rc.d scripts are started
  twice:

  Mar 16 10:24:47 failsafe: static-network-up start event emitted
  Mar 16 10:24:47 failsafe: rc-sysinit starting event emitted
  Mar 16 10:24:47 failsafe: Failsafe of 120 seconds reached.
  Mar 16 10:24:47 failsafe: net-device-up start event emitted
  Mar 16 10:24:47 failsafe: starting failsafe script
  Mar 16 10:24:47 failsafe: sleeping in failsafe script
  Mar 16 10:26:47 failsafe: emitting from failsafe script
  Mar 16 10:26:47 failsafe: rc-sysinit starting event emitted
  Mar 16 10:26:47 kernel: [  122.229597] init: failsafe main process (797) 
killed by TERM signal

  rc-sysinit has been emitted twice.

  Note that the rc-sysinit event has been emitted before the failsafe
  script has been emitted, because in this boot it happens that the
  static-network-up event was emitted before the net-device-up event.

  As a result, the normal stop on "starting rc-sysinit" rule in the
  failsafe job definition doesn't work because the failsafe job is not
  yet running.

  Another way to look at the issue is that the rc-sysinit job
  definition's "start on (filesystem and static-network-up) or failsafe-
  boot" means that it will always start twice if it finishes before the
  failsafe handler fires.

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

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

[Touch-packages] [Bug 1595177] Re: [SRU] Update apt/xenial to 1.2.14

2016-09-25 Thread Bruno Nova

I've updated apt to 1.2.14 and it seems to be working OK.
I ran a dist-upgrade after several days without updating, and all is well.

Bash autocompletion is also more complete now (LP: #1598384 and LP:
#1573547).

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

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

Title:
  [SRU] Update apt/xenial to 1.2.14

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  (This is a template for now, so I can close the bug in the 1.2.14
  upload)

  [Impact]
  We intend to upload APT 1.2.14 to xenial under the new "micro upstream 
release" policy.

  Apart from fixing bug 1573547, it also updates translations fixes the
  following other bugs:

  [[1.2.13]]

  Segmentation fault fixes:
  * fail instead of segfault on unreadable config files (Closes: 824503)

  Fixes for 3rd party programs using libapt and C++ locale API:
  * prevent C++ locale number formatting in text APIs (Closes: #825396)

  Fix for hurd (not really affecting us here, but upstream):
  * apt-key: change to / before find to satisfy its CWD needs.
    Thanks to Samuel Thibault for 'finding' the culprit! (Closes: 826043)

  Leak fixes:
  * do not hang on piped input in PipedFileFdPrivate
  * don't leak an FD in lz4 (de)compression
  * don't leak FD in AutoProxyDetect command return parsing

  [[1.2.14]]
  Regression fix from 1.2.13:
    * do not error if auto-detect-proxy cmd has no output (Closes: 827713)
  Huge apt-ftparchive performance regression fix from 1.1:
    * Reinstate caching of file hashes in apt-ftparchive (Closes: #806924)
  Tiny bug fixes, about 2 lines each:
    * source: if download is skipped, don't try to unpack
    * ensure filesize of deb is included in the hashes list

  [Test case]
  The releases follow new upstream micro release rule and thus are assumed to 
be tested by our integration test suite. There are two exceptions which cannot 
be tested:

  * prevent C++ locale number formatting in text APIs
  * apt-key: change to / before find to satisfy its CWD needs

  The first has no affected code in the archive (but maybe 3rd party
  code), the second only affects hurd.

  [Regression Potential]
  Very low. The release has been tested by a thorough integration test suite on 
Travis CI, Debian autopkgtests, and has been in Debian unstable since 
2016-06-22.

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

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

[Touch-packages] [Bug 1627365] Re: Screen frezes, only mouse pointer can move

2016-09-25 Thread Jose Barakat

Hi Christopher.

I'll remove
  http://ppa.launchpad.net/canonical-x/vulkan/ubuntu
  http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu
  http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu

and report back.

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

Title:
  Screen frezes, only mouse pointer can move

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This issue only occurs when I use certain gaming software like
  Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode.

  As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my
  symptoms are:

  - X stops responding to input (sometimes mouse cursor can still move, but 
clicking has no effect)
  - The screen displays but does not update. Sometimes there is screen 
corruption too, sometimes the screen goes black.
  - Often, X cannot be killed from the console or if it can, it won't restart 
properly; only a reboot clears the state 

  I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to
  frozen desktop/application with Ctrl+Alt+F7.

  I would like to reproduce this issue and collect the necessary data
  over ethernet, but I don't how to do it.

  - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony
  PlayStation Portable Emulator), Emulation Station (Frontend for
  Emulators) and a couple of minutes pass, so I can't go back to
  Windowed mode. I've tried with VLC fullscreen mode without issues.
  I'll make a more detailed report of apps later on comments.

  - I first noticed it aprox. after installing this repos:
http://ppa.launchpad.net/canonical-x/vulkan/ubuntu
http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu

  - I'm using Unity, so I can't be sure if this is happening in other
  DE's

  - Like I said before, this happens when switching from fullscreen mode
  to windowed mode, in some applications. I haven't had problems with
  streaming video (youtube player, jwplayer, vimeo player, etc...) in
  fullscreen mode.

  
  Thanks!

  
  Technical Info.
  
  Machine: Lenovo G400s (Laptop)

  
  ~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04


  ~$ apt-cache policy xorg
  xorg:
Instalados: 1:7.7+13ubuntu3
Candidato:  1:7.7+13ubuntu3
Tabla de versión:
   *** 1:7.7+13ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status


  Phoronix Test Suite v6.4.0
  Interactive Benchmarking

  System Software / Hardware Information

  Hardware:
  Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, 
Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate 
ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, 
Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless

  Software:
  OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 
7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 
3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen 
Resolution: 1366x768

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.2-040702-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: Sat Sep 24 10:11:14 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: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2015-07-08 (444 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20244
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic 
root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash 
pciehp.pciehp_force=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BCN36WW(V2.02)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G400s
  dmi.modalias:

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Peter S

Thanks for the input about 16.10, Christian. I was considering an
upgrade to get rid of the problem, but now I will think twice before
doing so.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-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

This bug was fixed in the package qtmir - 0.4.8+16.10.20160909-0ubuntu1

---
qtmir (0.4.8+16.10.20160909-0ubuntu1) yakkety; urgency=medium

  [ Daniel d'Andrada ]
  * Send relative pointer movement to Mir clients (LP: #1597205)
  * Implement cursor confinement (LP: #1590099)

  [ Gerry Boland ]
  * Deliver mouse event manually if no cursor exists to deliver it
  * [tests] refactor ScreensModel test to use mocks from mirtest-dev

 -- Michał Sawicz   Fri, 09 Sep 2016
14:40:56 +

** Changed in: qtmir (Ubuntu)
   Status: In Progress => 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/1590099

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

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
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 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

2016-09-25 Thread Stephen

Same issue, since upgrade to 16.04 the system has hung during reboot.
The network isn't fully shutdown and responds to pings but sshd is
stopped, the system reboots successfully if swap is disabled. Attempted
to add reboot=force to grub, to no avail; only disabling swap fixed the
issue.

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

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This bug has been affecting me since 15.04
  Prior to shutdown I activate debug-shell 'systemctl start debug-shell'
  I have followed bug #1464917 and installed Xenial-proposed with systemd 
229-4ubuntu5 package.  
  I have finally collected shutdown info using vt9.  
  Issues collecting info due to what I believe is a timeout where vt9 is not 
activated when ctl+alt+F9 is pressed.  I was able to collect info in vt9 to 
file "shutdown.text" I appended outputs to file "shutdown.text" the following 
commands in this order:
  systemctl list-jobs >>shutdown.text
  systemctl --failed >>shutdown.text
  uname -a >>shutdown.text
  systemd --version >>shutdown.text
  lsblk >>shutdown.text
  blkid >>shutdown.text
  journalctl -b >>shutdown.text
  systemctl -all >>shutdown.text
  journalctl -xe >>shutdown.text

  After gaining these data I was only able to finish the reboot with the 
alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown
  Each output I separated upon next boot by hand with a line 
# for easier perusing.

  As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a
  && systemctl poweroff' or 'sudo swapoff -a && reboot'  which
  occasionally fails if SWAP has more data than available RAM.  In that
  latter case I am left waiting for the hang and then using
  alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot
  before SWAP has a chance to gain data, then I can use any form of
  halt, poweroff or menu to shutdown.

  I have been unable to get answers from AskUbuntu or the above listed
  bug #1464917 "Reached target Shutdown"  I am filing this bug per
  instructions requested in that bug.  Other systemd bugs I have
  researched #788303 Debian bug reports, #2930 Github and #3087 Github.

  Thanks for your time and efforts to help with this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  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
  Date: Sun May 15 12:08:34 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2015-06-29 (321 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Sony Corporation VGN-FW250J
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro 
resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago)
  dmi.bios.date: 07/25/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1090Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1090Y0:bd07/25/2008:svnSonyCorporation:pnVGN-FW250J:pvrC6011MLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-FW250J
  dmi.product.version: C6011MLK
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1627511] Re: package libqtcore4 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches verschieden von andere

2016-09-25 Thread Flames_in_Paradise

The error seems to be caused by the last installation candidate (skype-
bin), i386-package on 64-Bit installation.

** Package changed: qt4-x11 (Ubuntu) => skype (Ubuntu)

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade: Versuch,
  gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben,
  welches verschieden von anderen Instanzen des Paketes libqtcore4:i386
  ist

Status in skype package in Ubuntu:
  Incomplete

Bug description:
  I don't know whether/why there's a problem at all. After booting the
  system, it showed that there was an error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 25 11:05:03 2016
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libqtcore4:i386 ist
  InstallationDate: Installed on 2015-10-16 (345 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libqtcore4:i386 ist
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (20 days ago)

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

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

[Touch-packages] [Bug 1627511] Re: package libqtcore4 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches verschieden von andere

2016-09-25 Thread Flames_in_Paradise

Bugs against SKYPE should be reported against their bugbase.

Ubuntu can't do anything about this, as it is proprietrary third-party-
software.

Reading from the logs that the installation language is german I would
highly recommend for you to seek help at the german ubuntuusers-forum
[1].

Beforehand I can let you have the link to their Community-Wiki regards
to Skype [2]


[1] https:/www.ubuntuusers.de
[2] https://wiki.ubuntuusers.de/Skype/

** Changed in: qt4-x11 (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade: Versuch,
  gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben,
  welches verschieden von anderen Instanzen des Paketes libqtcore4:i386
  ist

Status in skype package in Ubuntu:
  Incomplete

Bug description:
  I don't know whether/why there's a problem at all. After booting the
  system, it showed that there was an error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 25 11:05:03 2016
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libqtcore4:i386 ist
  InstallationDate: Installed on 2015-10-16 (345 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libqtcore4:i386 ist
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (20 days ago)

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Joakim Koed

Christian: Sounds like maybe it could be a problem with network-manager
+ lightdm, as gnome use GDM it makes sense there is no issue there.

In the meantime, you could always use this script:
http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
after-16-04-upgrade/761220#761220

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Christian Dysthe

I am having the same problem in Ubuntu 16.10 Beta 1. The main reason I
went for it so early was hoping these issues were resolved. They are
not. There's always problems when I come home after work and resume my
laptop. I'm either stuck on the now non existing work network or I do
not have any networks at all. I have tried "everything". I have two of
these Yoga Pro laptops, one with vanilla Ubuntu 16.10 beta and one with
UbuntuGNOME. On UbuntuGNOME no such problems.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Joakim Koed

Peter S: Just tried, same result.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1561759] Re: Not able to "Filing a general bug against no particular package"

2016-09-25 Thread Hans Joachim Desserud

Thanks for taking your time to report this issue and help making Ubuntu
better.

I am not able to trigger this issue here. When I run `ubuntu-bug`
without any package name or other options, I get the small dialog window
to select type of issue I want to report. I didn't click through all of
them, but the options seemed to be working too.

I notice that I'm running apport-gtk 2.20.1-0ubuntu2.1 (on Ubuntu 16.04)
which is a newer version than the one where this was originally
reported. Could you please check whether you still have this problem
with the latest version of apport?

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

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

Title:
  Not able to "Filing a general bug against no particular package"

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Unlike described in 
  
https://help.ubuntu.com/community/ReportingBugs#Filing_a_general_bug_against_no_particular_package
  ubuntu-bug fails  if not given a package name or using the -w option to 
retrieve package from executeable contrary to the descibed procedure to file a 
/general/ bug against /no particular/ package

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportLog:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashReports: 640:1000:117:1220382:2016-03-23 10:25:40.878120899 
+0100:2016-03-23 10:27:02.488061850 
+0100:/var/crash/_usr_bin_xfce4-power-manager.1000.crash
  CurrentDesktop: LXDE
  Date: Thu Mar 24 23:32:22 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-19 (34 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160217)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1525976] Re: fix broken homepage link

2016-09-25 Thread Hans Joachim Desserud

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The homepage link has been updated in procps 2:3.3.12-1ubuntu2 which is
available in Ubuntu Yakkety. Therefore I am closing this as Fix
Released.

 If you need a fix for the bug in previous versions of Ubuntu, please
perform as much as possible of the SRU Procedure [1] to bring the need
to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

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

Title:
  fix broken homepage link

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  Gitorious is not around anymore, so http://gitorious.org/procps
  doesn't go anywhere.

  It looks like procps has moved to gitlab: https://gitlab.com/procps-
  ng/procps

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

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

[Touch-packages] [Bug 1525976] Re: fix broken homepage link

2016-09-25 Thread Hans Joachim Desserud

See the homepage link on http://packages.ubuntu.com/yakkety/procps

** Tags added: packaging string-fix

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

Title:
  fix broken homepage link

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  Gitorious is not around anymore, so http://gitorious.org/procps
  doesn't go anywhere.

  It looks like procps has moved to gitlab: https://gitlab.com/procps-
  ng/procps

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-09-25 Thread Peter S

Have any of you tried using static IP adressess for your system?

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-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?)

2016-09-25 Thread Joakim Koed

Kathy: sounds like you have the exact same problem as the rest of us. I
would recommend just using the PPA, until Luke and Simon have an chance
to take a further look at it.. Hope it works for your hardware.

-- 
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 1627526] [NEW] package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед попыткой удаления его следует

2016-09-25 Thread nurik_K

Public bug reported:

The error appeared after installation attempts unity 8

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Sep 25 16:03:25 2016
DpkgTerminalLog:
 dpkg: ошибка при обработке пакета libunity-scopes1.0:amd64 (--remove):
  пакет абсолютно неработоспособен; перед попыткой удаления
  его следует переустановить
ErrorMessage: пакет абсолютно неработоспособен; перед попыткой удаления  его 
следует переустановить
InstallationDate: Installed on 2016-09-25 (0 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: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 failed 
to install/upgrade: пакет абсолютно неработоспособен; перед попыткой удаления  
его следует переустановить
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1627526

Title:
  package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
  failed to install/upgrade: пакет абсолютно неработоспособен; перед
  попыткой удаления  его следует переустановить

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  The error appeared after installation attempts unity 8

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 25 16:03:25 2016
  DpkgTerminalLog:
   dpkg: ошибка при обработке пакета libunity-scopes1.0:amd64 (--remove):
пакет абсолютно неработоспособен; перед попыткой удаления
его следует переустановить
  ErrorMessage: пакет абсолютно неработоспособен; перед попыткой удаления  его 
следует переустановить
  InstallationDate: Installed on 2016-09-25 (0 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: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 
failed to install/upgrade: пакет абсолютно неработоспособен; перед попыткой 
удаления  его следует переустановить
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1627526/+subscriptions

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

[Touch-packages] [Bug 859102] Re: pam_unix should not always complain about failed authentication

2016-09-25 Thread John Python

This problem also exists for sssd:

Sep 25 13:11:10 myserver sshd[15919]: pam_unix(sshd:auth): authentication 
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=127.0.0.1  user=bob
Sep 25 13:11:10 myserver sshd[15919]: pam_sss(sshd:auth): authentication 
success; logname= uid=0 euid=0 tty=ssh ruser= rhost=127.0.0.1 user=bob

It's possible to fix this ourselves, but it would be much better to see
a more permanent solution.

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

Title:
  pam_unix should not always complain about failed authentication

Status in pam package in Ubuntu:
  Confirmed

Bug description:
  I run a server with ubuntu lucid, pam et al 1.1.1-2ubuntu5.3.
  I used pam-auth-update to enable unix-style and ldap style authentication.
  For accounts that exist in my LDAP only, i get on every (successful!) 
authentication attempt the following message in auth.log:

  dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname=
  uid=0 euid=0 tty=dovecot ruser=xyz rhost=127.0.0.1  user=xyz

  This appears to happen because of any of the following problems:
  1. the unix module has a higher priority than the ldap module
  2. the unix module itself logs errors even if its "control" settings (ie. the 
second field in common-auth) ask it to ignore such a problem
  3. the unix module is not supposed to be configured at the same time as the 
ldap module.

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

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

[Touch-packages] [Bug 1627053] Re: Need visual indication that video recording isn't capturing sound

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

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Need visual indication that video recording isn't capturing sound

Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  When recording a video and the camera-app doesn't have permission to
  access the microphone, no audio will be recorded. This is expected of
  course, but it would be useful to have a visual indication that this
  is happening, perhaps somewhere on the camera HUD. Without this visual
  indication the users has no way of knowing that the video won't have
  any sound, until they try to play back the video, and then it's too
  late. I have a few important videos without sound for this reason :/.

  Also, taking a step back, a more fundamental solution would be to
  follow Matthew's suggestion from bug 1554142: the camera-app shouldn't
  ask for a special microphone permission, "the ability to record video
  includes the ability to use the microphone".

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

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

[Touch-packages] [Bug 682662] Re: pam-auth-update ignores debconf settings

2016-09-25 Thread John Python

Came by to report this same issue. /usr/share/pam-config/mkhomedir is
being ignored on Ubuntu 16.04 with this configuration:

Name: Create home directory during login
Default: yes
Priority: 900

Session-Type: Additional
Session:
requiredpam_mkhomedir.so umask=0077 skel=/etc/skel


It was working perfectly fine on Ubuntu 14.04.

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

Title:
  pam-auth-update ignores debconf settings

Status in pam package in Ubuntu:
  Triaged
Status in pam package in Debian:
  Won't Fix

Bug description:
  pam-auth-update ignores the current debconf-settings. This makes it
  impossible to do automatically configure pam in noninteractive
  installations.

  Demonstration:

  ~ # debconf-get-selections | grep libpam-runtime
  libpam-runtimelibpam-runtime/override boolean true
  libpam-runtimelibpam-runtime/conflictserror   
  libpam-runtimelibpam-runtime/no_profiles_chosen   error   
  libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, 
ldap, tmpdir, gnome-keyring, consolekit
  libpam-runtimelibpam-runtime/you-had-no-auth  error   

  ~ # DEBIAN_FRONTEND=noninteractive pam-auth-update

  ~ # debconf-get-selections | grep libpam-runtime
  libpam-runtimelibpam-runtime/override boolean false
  libpam-runtimelibpam-runtime/conflictserror   
  libpam-runtimelibpam-runtime/no_profiles_chosen   error   
  libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, 
winbind, ldap
  libpam-runtimelibpam-runtime/you-had-no-auth  error

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

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

[Touch-packages] [Bug 1627522] [NEW] send reduced (image)

2016-09-25 Thread mikahdh

Public bug reported:

Wish I could send minimized pictures.
Usually I take 'regular sized' pictures but when I send them via mail I don't 
wanna send dozens of MB.

For instance there's an android app called 'send reduced' which is very handy..
https://f-droid.org/repository/browse/?fdfilter=send+reduced=mobi.omegacentauri.SendReduced

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


** Tags: feature minimize

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

Title:
  send reduced (image)

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Wish I could send minimized pictures.
  Usually I take 'regular sized' pictures but when I send them via mail I don't 
wanna send dozens of MB.

  For instance there's an android app called 'send reduced' which is very 
handy..
  
https://f-droid.org/repository/browse/?fdfilter=send+reduced=mobi.omegacentauri.SendReduced

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

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

[Touch-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi

2016-09-25 Thread Mateo Salta

This also hppens on the intellect compute stick, and makes it rather
unusable using only the wifi and bluetooth built in, I would say this is
a critical #1 bug for using this comercialLy avaible product.

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

Title:
  Bluetooth does not coexist with WiFi

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On my system bluetooth and wifi are unusable together. I have a built-
  in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi
  transfers slow to a halt whenever there is BT traffic.

  For example, if I play a music file from another machine through the
  network using a BT headset, only the first few seconds of the file
  will play until the player runs out of buffered data. No further data
  is downloaded. Web pages also do not download, and I even lose
  connection to AP from time to time.

  At the same time, it looks like AFH is trying to work. If I monitor
  the value returned by 'hcitool afh', it changes. But this seems to
  have little effect on connection quality.

  Is this a problem with my hardware, or the AFH implementation? Is
  there a way to force bluetooth to not use the channels in use by WiFi?

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

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

[Touch-packages] [Bug 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

2016-09-25 Thread David DIDIER

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

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

Title:
  [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   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
  BootLog:
   
  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 13 21:49:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.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: Tue Sep 13 21:14:29 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

2016-09-25 Thread jap1968

Same problem here. I rarely had this problem previously with Ubuntu
14.04, but since updated to Ubuntu 16.04 I am suffering this issue very
often.

The problem mainly appears when trying to resume the laptop from
suspend. Mine has already installed xserver-xorg-video-intel. The laptop
has an intel HD Graphics 4400 video adapter, the one integrated within
the Core i7-4510U CPU

$ lspci
...
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)

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

Title:
  Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  dmesg output :

  [ 8815.416923] [drm] stuck on render ring
  [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8815.419462] drm/i915: Resetting chip after gpu hang
  [ 8821.417592] [drm] stuck on render ring
  [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8821.420108] drm/i915: Resetting chip after gpu hang
  [ 8827.430254] [drm] stuck on render ring
  [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8827.432786] drm/i915: Resetting chip after gpu hang
  [ 8833.418862] [drm] stuck on render ring
  [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], 
reason: Ring hung, action: reset
  [ 8833.421551] drm/i915: Resetting chip after gpu hang
  [ 8839.419503] [drm] stuck on render ring
  [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8839.422060] drm/i915: Resetting chip after gpu hang
  [ 8845.432118] [drm] stuck on render ring
  [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8845.434799] drm/i915: Resetting chip after gpu hang
  [ 8851.432751] [drm] stuck on render ring
  [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8851.435224] drm/i915: Resetting chip after gpu hang
  [ 8857.457381] [drm] stuck on render ring
  [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], 
reason: Ring hung, action: reset
  [ 8857.459883] drm/i915: Resetting chip after gpu hang
  [ 8863.458003] [drm] stuck on render ring
  [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8863.460640] drm/i915: Resetting chip after gpu hang
  [ 8869.458654] [drm] stuck on render ring
  [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: 
Ring hung, action: reset
  [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too 
fast, banning!
  [ 8869.461116] drm/i915: Resetting chip after gpu hang
  [ 8875.435238] [drm] stuck on render ring
  [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8875.437697] drm/i915: Resetting chip after gpu hang
  [ 8881.447863] [drm] stuck on render ring
  [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], 
reason: Ring hung, action: reset
  [ 8881.450331] drm/i915: Resetting chip after gpu hang
  [ 8887.436497] [drm] stuck on render ring
  [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8887.438961] drm/i915: Resetting chip after gpu hang
  [ 8893.437078] [drm] stuck on render ring
  [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], 
reason: Ring hung, action: reset
  [ 8893.439562] drm/i915: Resetting chip after gpu hang

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-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: Sun Apr 24 15:57:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2002]
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)

[Touch-packages] [Bug 1627511] [NEW] package libqtcore4 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches verschieden von ande

2016-09-25 Thread tu

Public bug reported:

I don't know whether/why there's a problem at all. After booting the
system, it showed that there was an error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqtcore4 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Sep 25 11:05:03 2016
ErrorMessage: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libqtcore4:i386 ist
InstallationDate: Installed on 2015-10-16 (345 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: qt4-x11
Title: package libqtcore4 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libqtcore4:i386 ist
UpgradeStatus: Upgraded to xenial on 2016-09-04 (20 days ago)

** Affects: qt4-x11 (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 qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1627511

Title:
  package libqtcore4 (not installed) failed to install/upgrade: Versuch,
  gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben,
  welches verschieden von anderen Instanzen des Paketes libqtcore4:i386
  ist

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  I don't know whether/why there's a problem at all. After booting the
  system, it showed that there was an error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 25 11:05:03 2016
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libqtcore4:i386 ist
  InstallationDate: Installed on 2015-10-16 (345 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/xdg/Trolltech.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libqtcore4:i386 ist
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (20 days ago)

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

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

[Touch-packages] [Bug 1627504] [NEW] [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or crackling sound. Test tones work but sound immediatly returns to poor quality after comple

2016-09-25 Thread Nyall

Public bug reported:

Using digital audio output on Intel driver.
Sound from games is barely decipherable over the distortion/crackle. Playing 
test tones (left/right test and on bug report) work fine but the noise returns 
when the clips are completed.

Tried tsched=0, hda fix 1 and hda fix 2. no luck yet
When first added tsched command, it blurs the screen and no audio devices are 
available. remove, restart, re-add and screen and audio back but problem still 
present (maybe just spelt wrong first time?).

Help appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nytonial   1759 F pulseaudio
 /dev/snd/controlC0:  nytonial   1759 F pulseaudio
CurrentDesktop: Unity
Date: Sun Sep 25 15:28:53 2016
InstallationDate: Installed on 2016-09-07 (17 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black SPDIF Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or 
crackling sound
UpgradeStatus: Upgraded to xenial on 2016-09-08 (16 days ago)
dmi.bios.date: 02/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.60
dmi.board.asset.tag: Default string
dmi.board.name: Z170A XPOWER GAMING TITANIUM EDITION(MS-7968)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 3.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd02/23/2016:svnMSI:pnMS-7968:pvr3.0:rvnMSI:rnZ170AXPOWERGAMINGTITANIUMEDITION(MS-7968):rvr3.0:cvnMSI:ct3:cvr3.0:
dmi.product.name: MS-7968
dmi.product.version: 3.0
dmi.sys.vendor: MSI
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-25T14:21:58.691691

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1627504

Title:
  [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts
  or crackling sound. Test tones work but sound immediatly returns to
  poor quality after completion.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Using digital audio output on Intel driver.
  Sound from games is barely decipherable over the distortion/crackle. Playing 
test tones (left/right test and on bug report) work fine but the noise returns 
when the clips are completed.

  Tried tsched=0, hda fix 1 and hda fix 2. no luck yet
  When first added tsched command, it blurs the screen and no audio devices are 
available. remove, restart, re-add and screen and audio back but problem still 
present (maybe just spelt wrong first time?).

  Help appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nytonial   1759 F pulseaudio
   /dev/snd/controlC0:  nytonial   1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 25 15:28:53 2016
  InstallationDate: Installed on 2016-09-07 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts 
or crackling sound
  UpgradeStatus: Upgraded to xenial on 2016-09-08 (16 days ago)
  dmi.bios.date: 02/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A XPOWER GAMING TITANIUM EDITION(MS-7968)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0

[Touch-packages] [Bug 1627502] Re: Black screen, cursor shown, wifi connection popup shown

2016-09-25 Thread Timo Jyrinki

** Description changed:

My yakkety installation is now for some reason in shape that lightdm
only starts with a black screen, although mouse cursor is shown and
movable and "wifi networks available" popup is shown at the top right
corner.
+
+ After some while this disappears and the system goes to some sort of tty
+ switching loop where sometimes text cursor is shown and sometimes just
+ blank screen. If I want to recover text console control of machine I
+ need to quickly after booting switch to tty1 and stop lightdm.
+
+ This started happening last week after some upgrades and a reboot.

I've tried reinstalling and everything I can think of, but I can't fix
it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't
start at all.

I couldn't also use ubuntu-bug since I can't use the browser interface
from command line (otherwise it works fine until that point) and it
segfaults under Plasma environment while collecting information.

** Attachment added: "lightdm logs"

https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627502/+attachment/4748365/+files/lightdm.tar

** Description changed:

After some while this disappears and the system goes to some sort of tty
switching loop where sometimes text cursor is shown and sometimes just
blank screen. If I want to recover text console control of machine I
need to quickly after booting switch to tty1 and stop lightdm.

This started happening last week after some upgrades and a reboot.

I've tried reinstalling and everything I can think of, but I can't fix
it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't
- start at all.
+ start at all. So I'm using sddm + Plasma now but would like to be also
+ be able to run Unity 7 and Unity 8.

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

Title:
Black screen, cursor shown, wifi connection popup shown

Status in lightdm package in Ubuntu:
New

Bug description:
My yakkety installation is now for some reason in shape that lightdm
only starts with a black screen, although mouse cursor is shown and
movable and "wifi networks available" popup is shown at the top right
corner.

After some while this disappears and the system goes to some sort of
tty switching loop where sometimes text cursor is shown and sometimes
just blank screen. If I want to recover text console control of
machine I need to quickly after booting switch to tty1 and stop
lightdm.

This started happening last week after some upgrades and a reboot.

I've tried reinstalling and everything I can think of, but I can't fix
it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
doesn't start at all. So I'm using sddm + Plasma now but would like to
be also be able to run Unity 7 and Unity 8.

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

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

[Touch-packages] [Bug 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes

2016-09-25 Thread Jan Claeys

** Summary changed:

- nautilus trash doesn't include btrfs subvolumes
+ nautilus trash doesn't include btrfs and zfs subvolumes

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

Title:
  nautilus trash doesn't include btrfs and zfs subvolumes

Status in GLib:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global
  trash.

  Comment by bug triage team: comment 4 has a spot-on analysis of where
  this issue is coming from, an inconsistency between trash handling in
  gvfs and glib/gio.  The problem has been around for quite a while.

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

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

[Touch-packages] [Bug 1627502] [NEW] Black screen, cursor shown, wifi connection popup shown

2016-09-25 Thread Timo Jyrinki

Public bug reported:

My yakkety installation is now for some reason in shape that lightdm
only starts with a black screen, although mouse cursor is shown and
movable and "wifi networks available" popup is shown at the top right
corner.

I've tried reinstalling and everything I can think of, but I can't fix
it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't
start at all.

I couldn't also use ubuntu-bug since I can't use the browser interface
from command line (otherwise it works fine until that point) and it
segfaults under Plasma environment while collecting information.

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

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

Title:
  Black screen, cursor shown, wifi connection popup shown

Status in lightdm package in Ubuntu:
  New

Bug description:
  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.

  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
  doesn't start at all.

  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

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

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

[Touch-packages] [Bug 883138] Re: Dim file extensions

2016-09-25 Thread Fred

@ginggs, modify the Open File and Save File dialogs in Wine to dim the
file extension. See screenshot.

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

Title:
  Dim file extensions

Status in GTK+:
  Confirmed
Status in Nautilus:
  Confirmed
Status in Wine:
  New
Status in enlightenment package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in lesstif2 package in Ubuntu:
  New
Status in mono package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged
Status in qt4-x11 package in Ubuntu:
  Opinion
Status in tcltk-defaults package in Ubuntu:
  New
Status in wine package in Ubuntu:
  Incomplete

Bug description:
  Many web browsers have now began dimming less relevant parts of the URL, such 
as the protocol, subdomain, path, and query string.
  I propose we have an option/setting/feature that does the same Nautilus and 
Gtk file dialogs. Dim the the file extension.

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

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

[Touch-packages] [Bug 1627496] [NEW] AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.

2016-09-25 Thread Valentin Quequet

Public bug reported:

Hello Guys,

I'm currently running an up-to-date Xenial system on amd64 (PC)
platform.

Whenever I launch the OS with stock kernel (4.4.X) all seems good.

Whenever I launch the OS with let's say a mainline-PPA kernel whose
version is above 3.6.0 inclusive (3.5.X are functional), or stock
yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card,
whose description is appended in a few text files I joined to this
message.

In hope this helps,

Sincelely,
Vécu


P.S. : I very suspect this is a mainstream bug ; for any complimentary info. 
please don't hesitate to post and ask for more.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.8.0-16-generic x86_64
.tmp.unity_support_test.1:
 
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: Sun Sep 25 15:23:08 2016
DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41]
InstallationDate: Installed on 2015-05-01 (512 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: TOSHIBA SATELLITE L875-10G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic 
root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago)
dmi.bios.date: 3/25/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.50
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE L875-10G
dmi.product.version: PSKBLE-003006FR
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs 1.0
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: Sun Sep 25 15:10:31 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

** Attachment added: "Logs_Attachment.tar.gz"
   
https://bugs.launchpad.net/bugs/1627496/+attachment/4748335/+files/Logs_Attachment.tar.gz

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

Title:
  AMD Radeon hardware features or firmware looked over by Linux 3.6.0+
  kernel.

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello Guys,

  I'm currently running an up-to-date Xenial system on amd64 (PC)
  platform.

  Whenever I launch the OS with stock kernel (4.4.X) all seems good.

  Whenever I launch the OS with let's say a mainline-PPA kernel whose
  version is above 3.6.0 inclusive (3.5.X are functional), or stock
  yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics
  card, whose description is appended in a few text files I joined to
  this message.

  In hope this helps,

  Sincelely,
  Vécu

  
  P.S. : I very suspect this is a mainstream bug ; for any complimentary info. 
please don't hesitate to post and ask for more.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2016-09-25 Thread Yonsy

~  sudo ls /sys/devices/platform/dock.0
ls: cannot access '/sys/devices/platform/dock.0': No such file or directory
 ✘  ~ 

the file don't exists in my laptop described above (Spectre x360 core i7
6500u)

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1511074] Re: camera constantly refocuses when recording a video

2016-09-25 Thread dinamic

same with M10 https://www.youtube.com/watch?v=SjNcB_Oswgk

this not happen with most android phones, even low end phones

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

Title:
  camera constantly refocuses when recording a video

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Triaged

Bug description:
  camera is missing auto focus options ON/OFF

  i really need to turn OFF auto focus. i can't record the screen
  without turning OFF the auto focus, but there is no settings...

  Sample video showing the refocusing
  https://www.youtube.com/watch?v=8Zdpp7mZEQs

  Its a bit odd that its going out of focus at all, wonder if there is a
  way to improve the configuration.

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

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

[Touch-packages] [Bug 1623768] Re: Adapt to new Totem icon name

2016-09-25 Thread Rafael Laguna

** Changed in: lubuntu-artwork (Ubuntu)
 Assignee: (unassigned) => Rafael Laguna (rafaellaguna)

** Changed in: lubuntu-artwork (Ubuntu)
   Status: New => Incomplete

** Changed in: lubuntu-artwork (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  Adapt to new Totem icon name

Status in humanity-icon-theme package in Ubuntu:
  New
Status in lubuntu-artwork package in Ubuntu:
  Fix Committed
Status in ubuntukylin-theme package in Ubuntu:
  New
Status in xubuntu-artwork package in Ubuntu:
  Fix Committed

Bug description:
  Totem has changed its icon name for easier integration with flatpak

  -Icon=totem
  +Icon=org.gnome.Totem

  If your icon theme will be used in Ubuntu 16.04 LTS also, then I
  recommend making a symlink from the totem icon to the new
  org.gnome.Totem icon. Alternatively, you could drop the icon and let
  users use the high resolution icons shipped by Totem itself.

  See also bug 1618138 which lists some other app icon name changes but
  those icons aren't shipped in all themes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+subscriptions

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

[Touch-packages] [Bug 1574333] Re: LVM-based server does not boot with kernel 4.4 (but works with 4.2)

2016-09-25 Thread qwerty

I encounter the issue as u. Here is a summary of the problem and what I
tried: http://askubuntu.com/questions/797128/lvmetad-is-not-active-yet-
using-direct-activation-during-sysinit-on-boot

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

Title:
  LVM-based server does not boot with kernel 4.4 (but works with 4.2)

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I‘ve updated my home-made NAS from wily to xenial and it stopped
  booting.

  Selecting the 4.2 kernel on the grub menu makes it work again.

  The working kernel is 4.2.0-35-generic

  The failing kernel is 4.4.0-21-generic.

  When the booting sequence freezes, I can have a terminal with the
  following text :

   lvmetad is not active yet, using direct activation during sysinit
  Scannig for Btrfs flesystems
  _

  Actually my set-up is lvm based, and the correponding lines of the
  output of a mount command are

  /dev/mapper/clio-root on / type btrfs 
(rw,relatime,nospace_cache,subvolid=256,subvol=/@)
  /dev/mapper/clio-root on /mnt/clio-root type btrfs 
(rw,relatime,nospace_cache,subvolid=5,subvol=/)
  /dev/mapper/clio-root on /home type btrfs 
(rw,relatime,nospace_cache,subvolid=257,subvol=/@home)

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

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

[Touch-packages] [Bug 1606078] Re: No sound with Ubuntu 16.04

2016-09-25 Thread javier algilaga

Same issue in lg p1 express dual, using Ubuntu 16.04. This bug is repeated 
previously with Ubuntu 8.04
Luke Yelavich, I tried installing this package 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+files/oem-audio-hda-daily-dkms_0.201609250548~ubuntu16.04.1_all.deb
but doesn't work.
It works correctly changing files in /etc/modprobe.d 
It's the same solution that it worked in Ubuntu 8,04
Thaks

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

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

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

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

[Touch-packages] [Bug 1421718] Re: [Ubuntu Phone Store] No message when no applications found

2016-09-25 Thread Norbert

BQ M10, OTA-13. 
Ubuntu Store show empty window as search result.
Why? I do not know. Slow/broken internet connection? Timeout? Search term is 
not found in App/Scope database?

Please show verbose message for user for at least these variants:
* search term not found;
* timeout occured, please try again;
* unknown error occured.

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

Title:
  [Ubuntu Phone Store] No message when no applications found

Status in Ubuntu UX:
  Won't Fix
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Hi!

  Steps:
  1. Open Store.
  2. Search RRS (Not RSS).
  3. Bug: Nothing found, but you can't see a message for this.
  4. Search RSS.
  5. OK: You see 5 applications found message.

  Thanks in advance!

  --
  Desired resolution:

  This is part of a bigger redesign project (Scopes toolkit) and it
  can't be fixed as a single bug. The description and specs will be
  updated as soon as they are available.

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

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

[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

2016-09-25 Thread Vincas Dargis

I've noticed same issue on BQ E5 on OTA-12 and OTA-13. Sometimes
incomming call gets silent after a split second (I can hear a blip of
sound).

Attaching syslog and unity8.log of that exact minute it happened. There
are no lines in media-hub log.


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1612367/+attachment/4748323/+files/syslog

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

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

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

[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

2016-09-25 Thread Vincas Dargis

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1612367/+attachment/4748324/+files/unity8.log

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

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

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

[Touch-packages] [Bug 1358294] Re: App data and config files are not removed when an app is uninstalled

2016-09-25 Thread Norbert

Confirmed on BQ M10, OTA-13. Folder in ~/.local/share/... persists after
app remove.

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

Title:
  App data and config files are not removed when an app is uninstalled

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in click package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Triaged

Bug description:
  If an app uses ~/.config/foo (say, uses Qt.labs.settings), and the
  user uninstalls the app, ~/.config/foo is not removed. It should be
  deleted when the app is uninstalled.

  Using latest utopic on the phone.

  -
  Desired resolution:

  - When a user deletes an app, 100% of files associated with the app
  should be deleted.

  - A warning notification should be displayed when a user goes to
  delete an app informing them that this action will also delete any
  data they have stored inside the app.  This notification should give
  the options of cancelling or proceeding with the action.

  - Users should not be allowed to delete the key apps that ship with
  the phone.  These key apps are defined as: Dialler, Address book,
  Messaging, Browser, Camera, Music player

  The above will give the user a simple easy to understand mental model
  while simultaneously protecting the user from deleting important
  content within the default apps.

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

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

[Touch-packages] [Bug 1625877] Re: VLC screen always on top

2016-09-25 Thread Leo Lee

I test this on Yakkety Yak in VirtualBox, works normally.
Maybe it's resolved.

Last version of Ubuntu I used is 14.04.
I remembered vlc works normally, but not the same computer.

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

Title:
  VLC screen always on top

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After new installed VLC on 16.04
  The video screen always on top only while playing with VLC

  the interface disappeared while minimum VLC (video playing)
  video screen remains only

  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"

  in Preference > Video > Display

  Reference:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053

  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
  CurrentDesktop: Unity
  Date: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
  InstallationDate: Installed on 2016-09-01 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: SY Series
  dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: SY Series
  dmi.product.version: Not Applicable
  dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
  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: Tue Sep 20 22:21:24 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1191
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1626883] Re: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault

2016-09-25 Thread Olli Salli

Thank you. I can verify libssl1.0.0 1.0.2g-1ubuntu4.5 no longer exhibits
the crash:

jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$
 apt-cache policy libssl1.0.0
libssl1.0.0:
  Installed: 1.0.2g-1ubuntu4.5
  Candidate: 1.0.2g-1ubuntu4.5
  Version table:
 *** 1.0.2g-1ubuntu4.5 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.2g-1ubuntu4.2 500
500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 1.0.2g-1ubuntu4 500
500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$
 DATABASE_DATABASE=wordpressmastere2e wp plugin install --force --activate 
wp-cfm
Deprecated: Methods with the same name as their class will not be constructors 
in a future version of PHP; WP_Import has a deprecated constructor in 
/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php
 on line 38
Notice: Undefined offset: 4 in 
phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124
Installing WP-CFM (1.4.5)
Ladataan pakettia lähteestä https://downloads.wordpress.org/plugin/wp-cfm.zip...
Using cached file '/home/jenkins/.wp-cli/cache/plugin/wp-cfm-1.4.5.zip'...
Puretaan pakettia...
Asennetaan lisäosaa...
Poistetaan lisäosan vanhaa versiota...
Lisäosa päivitetty onnistuneesti.
Activating 'wp-cfm'...
Warning: Plugin 'wp-cfm' is already active.
jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$

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

Title:
  libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert
  validation to segfault

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Precise:
  Fix Released
Status in openssl source package in Trusty:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released

Bug description:
  Last night unattended-upgrades upgraded the openssl packages
  (libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to
  version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that
  used PHP to connect to a HTTPS site started crashing when verifying
  the server cert.

  Like this:

  ```
  
jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$
 DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force 
--activate wp-cfm
  Deprecated: Methods with the same name as their class will not be 
constructors in a future version of PHP; WP_Import has a deprecated constructor 
in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop
/vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php 
on line 38
  Notice: Undefined offset: 4 in 
phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124
  Segmentation fault (core dumped)
  *** Segmentation fault
  Register dump:

   RAX:    RBX: 0001   RCX: 
   RDX: 000c   RSI: 55665071af59   RDI: 
   RBP: 556650a49e4e   R8 : 556652364720   R9 : 
   R10:    R11: 7fdb3c081730   R12: 55665071af59
   R13: 000c   R14:    R15: 7fdb39418cf0
   RSP: 7ffc4bad7a08

   RIP: 7fdb3bf77d16   EFLAGS: 00010293

   CS: 0033   FS:    GS: 

   Trap: 000e   Error: 0004   OldMask:    CR2: 

   FPUCW: 027f   FPUSW:    TAG: 
   RIP:    RDP: 

   ST(0)     ST(1)  
   ST(2)     ST(3)  
   ST(4)     ST(5)  
   ST(6)     ST(7)  
   mxcsr: 1fa0
   XMM0:   XMM1:  

   XMM2:   XMM3:  

   XMM4:   XMM5:  

   XMM6:   XMM7:  

   XMM8:   XMM9:  

   XMM10:  XMM11: 

   XMM12:  XMM13: 

   XMM14:  XMM15: 


  Backtrace:
  /lib/x86_64-linux-gnu/libc.so.6(strlen+0x26)[0x7fdb3bf77d16]
  php(add_assoc_string_ex+0x32)[0x556650677b12]
  php(zif_openssl_x509_parse+0x17c)[0x5566505312ec]

[Touch-packages] [Bug 1622717] Re: "Quit" from quicklist doesn’t close all open windows, doesn’t actually quit the application

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

Title:
  "Quit" from quicklist doesn’t close all open windows, doesn’t actually
  quit the application

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I’m attaching a sample click application that contains a simple qml
  scene that opens several windows. This can be installed on a device
  with:

pkcon install-local --allow-untrusted fubar.osomon_0.4_all.click

  Initially, only one window is open, and tapping on any window opens
  one more window.

  If I reveal the launcher and long press on the app’s icon to select
  the "Quit" option, not all windows are closed:

   - if there is only one window open, it’s closed and the application 
successfully exits
   - if there are two windows open, only the second window is closed, the first 
one remains open (and consequently the application is still running)
   - if there are three windows open, only the first and third one are closed, 
the second one remains…

  Expected behaviour: when "Quit" is tapped, all open windows are
  closed, and the application exits.

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

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

[Touch-packages] [Bug 1627365] Re: Screen frezes, only mouse pointer can move

Jose Barakat, thank you for reporting this and helping make Ubuntu
better.

To clarify, if you remove all the unsupported PPAs is this still
reproducible?

** Tags added: bios-outdated-2.04

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

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

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

Title:
  Screen frezes, only mouse pointer can move

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This issue only occurs when I use certain gaming software like
  Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode.

  As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my
  symptoms are:

  - X stops responding to input (sometimes mouse cursor can still move, but 
clicking has no effect)
  - The screen displays but does not update. Sometimes there is screen 
corruption too, sometimes the screen goes black.
  - Often, X cannot be killed from the console or if it can, it won't restart 
properly; only a reboot clears the state 

  I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to
  frozen desktop/application with Ctrl+Alt+F7.

  I would like to reproduce this issue and collect the necessary data
  over ethernet, but I don't how to do it.

  - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony
  PlayStation Portable Emulator), Emulation Station (Frontend for
  Emulators) and a couple of minutes pass, so I can't go back to
  Windowed mode. I've tried with VLC fullscreen mode without issues.
  I'll make a more detailed report of apps later on comments.

  - I first noticed it aprox. after installing this repos:
http://ppa.launchpad.net/canonical-x/vulkan/ubuntu
http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu

  - I'm using Unity, so I can't be sure if this is happening in other
  DE's

  - Like I said before, this happens when switching from fullscreen mode
  to windowed mode, in some applications. I haven't had problems with
  streaming video (youtube player, jwplayer, vimeo player, etc...) in
  fullscreen mode.

  
  Thanks!

  
  Technical Info.
  
  Machine: Lenovo G400s (Laptop)

  
  ~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04


  ~$ apt-cache policy xorg
  xorg:
Instalados: 1:7.7+13ubuntu3
Candidato:  1:7.7+13ubuntu3
Tabla de versión:
   *** 1:7.7+13ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status


  Phoronix Test Suite v6.4.0
  Interactive Benchmarking

  System Software / Hardware Information

  Hardware:
  Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, 
Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate 
ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, 
Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless

  Software:
  OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 
7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 
3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen 
Resolution: 1366x768

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.2-040702-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: Sat Sep 24 10:11:14 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: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2015-07-08 (444 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20244
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic 
root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash 
pciehp.pciehp_force=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BCN36WW(V2.02)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G400s
  dmi.modalias:

[Touch-packages] [Bug 1615204] Re: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1

Aaron Marcuse-Kubitza, the justification you provided doesn't indicate
one way or the other the root cause is xorg.

Could you please provide a full technical discussion (not a couple
sentence opinion)?

** Package changed: xorg (Ubuntu) => linux (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/1615204

Title:
  select-by-word/double-click drag-select only works sporadically on
  Toshiba Chromebook 1

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (also on Linux kernel bug tracker at
  https://bugzilla.kernel.org/show_bug.cgi?id=153871)

  Detailed bug description:
  In Ubuntu 16.04.1 [1] on the Toshiba Chromebook 1, if you try to select text 
by word, by double-clicking/triple-touchpad-tapping and then dragging the 
mouse, this only works occasionally. However, selecting text by line with a 
triple-click/4-tap drag works fine. This bug does not appear when Ubuntu 
16.04.1 is run in a VM in VirtualBox.
  [1] and now Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 
4.4.0-34-generic (the same as for 16.04)

  Steps to reproduce:
  1) On a 1st-generation Toshiba Chromebook (and possibly other machines, too), 
run Ubuntu 16.04.1 from a boot disk 
(http://releases.ubuntu.com/16.04/ubuntu-16.04.1-desktop-i386.iso).
  2) Open a terminal window and type several words.
  3) Double-click/triple-touchpad-tap and then drag the mouse to attempt to 
select multiple words.
  4) Compare this to the same boot disk run in VirtualBox, where it works 
properly.
  5) Compare this to Ubuntu 14.04.5 with the hardware-specific update to Linux 
kernel 4.4.0-34-generic (see comment #23 & 
http://wiki.ubuntu.com/1404_HWE_EOL), where it doesn't work.
  6) Compare this to the hardware-specific update but with Linux kernel 
4.4.0-34-generic removed (downgraded to 3.16.0-77-generic), where it also 
doesn't work (and is therefore not a kernel problem, but rather relates to 
other files in the hardware-specific update).

  Expected results:
  Multiple words are selected.

  Actual result:
  Only the first word is selected.

  Reproducibility:
  Double-click drag-select will work occasionally, but most of the time it 
doesn't.

  Workaround:
  In applications other than Terminal, can use Ctrl+Shift+Right-Arrow to select 
by word (significantly slower for large text blocks). No known workaround for 
Terminal.

  Impact:
  Recommend not upgrading to 16.04 if you have a computer where double-click 
drag-select doesn't work in it.

  Description of the environment:
   Operation system: Ubuntu 16.04.1
   Versions of components: Linux kernel 4.4.0-34-generic (also on Ubuntu 
14.04.5)
   Reference architecture: 1st-generation Toshiba Chromebook (model name 
"Toshiba Leon")
   Network model: N/A
   Related projects installed: none (boot disk)

  Additional information:
  N/A
  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   1882 F pulseaudio
   /dev/snd/controlC1:  administrator   1882 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-04-05 (506 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Toshiba Leon
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=127e42a1-2015-0521--28e347c5f54d ro tpm_tis.force=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.127.22
  Tags:  trusty
  Uname: Linux 4.4.0-34-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: Toshiba
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr:
  dmi.product.name: Leon
  dmi.product.version: 1.0
  dmi.sys.vendor: Toshiba

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

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

[Touch-packages] [Bug 1578698] Re: Crash on waking from suspend after upgrading to 16.04

Csaba Miklos, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Crash on waking from suspend after upgrading to 16.04

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Since upgrading to Ubuntu 16.04 and compiz
  1:0.9.12.2+16.04.20160415-0ubuntu1 I have started to see frequent,
  apparently random crashes when resuming from suspend.  I don't have
  any definitive proof that it is compiz vs e.g. the Unity plugin, as I
  don't even get one of the usual crash dialogues when this happens.  I
  just see the screen freeze up, aside from the cursor, and then after
  10-15 seconds it seems to reload compiz and I am able to actually
  enter my password to login.  I'm sorry this report isn't of more help,
  I will continue investigating to see if I can narrow it down at all.

  Edit: I'm using the Intel graphics driver, and spotted the following
  in dmesg:

  [drm] stuck on render ring
  [drm] GPU HANG: ecode 7:0:0x85d8, in compiz [16077], reason: Ring hung, 
action: reset
  drm/i915: Resetting chip after gpu hang
  [drm] stuck on render ring
  [drm] GPU HANG: ecode 7:0:0x85d8, in compiz [16077], reason: Ring hung, 
action: reset
  [ cut here ]
  WARNING: CPU: 6 PID: 804 at 
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, 
false, NULL, _flip->i915->rps.mmioflips))
  Modules linked in:
   vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) hidp cmac drbg 
ansi_cprng ctr ccm pci_stub rfcomm bnep zram lz4_compress arc4 intel_rapl 
x86_pkg_temp_thermal uvcvideo intel_powerclamp iwlmvm snd_hda_codec_conexant 
snd_hda_codec_hdmi videobuf2_vmalloc crct10dif_pclmul snd_hda_codec_generic 
videobuf2_memops crc32_pclmul videobuf2_v4l2 mac80211 snd_hda_intel 
videobuf2_core aesni_intel snd_hda_codec v4l2_common snd_hda_core btusb 
videodev aes_x86_64 snd_hwdep btrtl lrw btbcm media gf128mul snd_pcm btintel 
glue_helper bluetooth ablk_helper cryptd snd_seq_midi snd_seq_midi_event 
iwlwifi snd_rawmidi joydev snd_seq input_leds rtsx_pci_ms serio_raw cfg80211 
memstick snd_seq_device snd_timer lpc_ich snd soundcore ie31200_edac mei_me 
toshiba_acpi mei toshiba_bluetooth toshiba_haps sparse_keymap
   edac_core shpchp mac_hid soc_button_array kvm_intel kvm irqbypass nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc coretemp autofs4 hid_generic usbhid hid 
rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt psmouse fb_sys_fops ahci drm alx libahci rtsx_pci mdio wmi video fjes 
[last unloaded: vboxdrv]
  CPU: 6 PID: 804 Comm: kworker/6:0 Tainted: GW  OE   4.4.0-21-generic 
#37-Ubuntu
  Hardware name: TOSHIBA Satellite P75-A/Type2 - Board Product Name1, BIOS 1.50 
04/18/2014
  Workqueue: events intel_mmio_flip_work_func [i915]
   0286 c262292d 88007aa2bd20 813e93c3
   88007aa2bd68 c0270a50 88007aa2bd58 81080f62
   88027609f780 88045f396500 88045f39ae00 0180
  Call Trace:
   [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? __switch_to+0x420/0x5a0
   [] intel_mmio_flip_work_func+0x38e/0x3d0 [i915]
   [] process_one_work+0x162/0x480
   [] worker_thread+0x4b/0x4c0
   [] ? process_one_work+0x480/0x480
   [] ? process_one_work+0x480/0x480
   [] kthread+0xd8/0xf0
   [] ? kthread_create_on_node+0x1e0/0x1e0
   [] ret_from_fork+0x3f/0x70
   [] ? kthread_create_on_node+0x1e0/0x1e0
  ---[ end trace d6a9268873c90b8e ]---
  [ cut here ]
  WARNING: CPU: 6 PID: 23478 at 
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, 
false, NULL, _flip->i915->rps.mmioflips))
  Modules linked in:
   vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) hidp cmac drbg 
ansi_cprng ctr ccm pci_stub rfcomm bnep zram lz4_compress arc4 intel_rapl 
x86_pkg_temp_thermal uvcvideo intel_powerclamp iwlmvm snd_hda_codec_conexant 
snd_hda_codec_hdmi videobuf2_vmalloc crct10dif_pclmul snd_hda_codec_generic 
videobuf2_memops crc32_pclmul videobuf2_v4l2 mac80211 snd_hda_intel 
videobuf2_core aesni_intel snd_hda_codec v4l2_common snd_hda_core btusb 
videodev aes_x86_64 snd_hwdep btrtl lrw btbcm media gf128mul snd_pcm btintel 
glue_helper bluetooth ablk_helper cryptd snd_seq_midi snd_seq_midi_event 
iwlwifi snd_rawmidi joydev snd_seq input_leds

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1626288] Re: X fonts and widgets disappear after suspend/resume cycle

Samuel Ballé, thank you for reporting this and helping make Ubuntu
better.

In order to allow additional upstream developers to examine the issue, at your 
earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** This bug is no longer a duplicate of bug 1434351
   X fonts and widgets disappear after suspend/resume cycle

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

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

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

Title:
   X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  not all the time, but at some suspend/resume operations fonts disapear from 
gnome terminal, nm-applet and soffice which then show spaces and underscore 
placeholders instead of characters.
  google chrome, thunderbird, firefox, virtualbox are not affected.
  As it happens not at each suspend resume I find it hard to diagnose what is 
going wrong.
  next time I will launch more apps to see wich ones are affected.

  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
  BootLog:
   /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks
   [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps.
   See 'systemctl status snapd.refresh.service' for details.
   [[0;32m  OK  [0m] Started Detect the available GPUs and deal with any 
system changes.
Starting Light Display Manager...
  CompizPlugins:
   (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Wed Sep 21 23:41:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
  InstallationDate: Installed on 2016-07-27 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook W65_67SZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05SB.02
  dmi.board.asset.tag:

[Touch-packages] [Bug 1625877] Re: VLC screen always on top