date:20160906

[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/1512634

Title:
  Mouse pointer gets distorted / broken on dual screen setup

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The mouse pointer is fine at boot, but after working a couple of
  minutes it gets distorted. I move my mouse pointer back and forth
  between my two screens all the time. The actual distortion happens
  randomly on the "screen switch" and when I move my pointer on one of
  my screens. Sometimes I can see a slight distortion and if I move my
  mouse pointer on top of a scrollbar its back to normal. But just for a
  little while, then its permanently distorted. And it happens only on
  one of the screens, never on both at the same time.

  WORKAROUND: disabled the fglrx drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov  3 10:39:02 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.13.0-62-generic, x86_64: installed
   fglrx-core, 15.200, 3.13.0-63-generic, x86_64: installed
   fglrx-core, 15.200, 3.13.0-65-generic, x86_64: installed
   fglrx-core, 15.200, 3.13.0-66-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] 
[1002:67b1] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:9295]
  InstallationDate: Installed on 2014-12-19 (318 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=f0b5450d-3c23-49f1-b3e8-4544b9af89d7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/22/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Nov  3 08:41:57 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: fglrx

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

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

[Touch-packages] [Bug 1596464] Re: unity greeter stays in desktop mode if a bluetooth HID is connected

[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/1596464

Title:
  unity greeter stays in desktop mode if a bluetooth HID is connected

Status in aethercast:
  Invalid
Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Reproduce steps
  1. Connect with Microsoft Wireless Display Adapter V2.0.8350
  2. Force disconnected by removing Microsoft Wireless Display Adapter.
  3. Ubuntu Phone returns back to Unity greeter but does not restore to phone 
mode, user is not able to use on screen keyboard to login.

  Expected behavior:
  The unity greeter should return back to Staged usage mode.

  VERSION
  current build number: 10
  device name: turbo
  channel: ubuntu-touch/rc-proposed/meizu-pd.zh-proposed
  last update: 2016-06-27 16:25:25
  version version: 10
  version ubuntu: 20160624
  version device: 20160617-82a5c0d
  version custom: 20160626-981-7-3

  aethercast0.1+15.04.20160607-0ubuntu1
  aethercast-tools  0.1+15.04.20160607-0ubuntu1

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

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

[Touch-packages] [Bug 1598597] Re: Screen does not turn off automatically

[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/1598597

Title:
  Screen does not turn off automatically

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Mako
  Rc-propsed
  R477

  After leaving the device idle for any time the screen does not turn off or 
blank automatically.
  Power button must be pressed to turn off the screen.

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

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

[Touch-packages] [Bug 1289094] Re: Could not find module FindOpenCV.cmake when compiling

2016-09-06 Thread linas

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

** This bug has been marked a duplicate of bug 1167014
   MIssing cmake files

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

Title:
  Could not find module FindOpenCV.cmake when compiling

Status in opencv package in Ubuntu:
  New

Bug description:
  Quoted from here: http://stackoverflow.com/questions/8711109/could-
  not-find-module-findopencv-cmake-error-in-configuration-
  process/22239942

  I had installed opencv from ubuntu 12.10 repository (libopencv-)* and
  had this problem:

  I wrote a CMakeLists.txt for a project in C++ (using ROS), which uses OpenCV 
libraries. When I try to create the project using cmake, I get the next 
configuration problem:
  "
  CMake Error at CMakeLists.txt:15 (find_package):
Could not find module FindOpenCV.cmake or a configuration file for package
OpenCV.

Adjust CMAKE_MODULE_PATH to find FindOpenCV.cmake or set OpenCV_DIR to the
directory containing a CMake configuration file for OpenCV.  The file will
have one of the following names:

  OpenCVConfig.cmake
  opencv-config.cmake
  "

  Couldn't solve it with export OpenCV_DIR=/usr/share/OpenCV/ (since my
  OpenCVConfig.cmake whas there). It was solved when I also changed some
  lines on the OpenCVConfig.cmake file:

  # ==
  # Include directories to add to the user project:
  # ==

  # Provide the include directories to the caller

  #SET(OpenCV_INCLUDE_DIRS
  "${OpenCV_INSTALL_PATH}/include/opencv;${OpenCV_INSTALL_PATH}/include")

  SET(OpenCV_INCLUDE_DIRS "/usr/include/opencv;/usr/include/opencv2")
  INCLUDE_DIRECTORIES(${OpenCV_INCLUDE_DIRS})

  # ==
  # Link directories to add to the user project:
  # ==

  # Provide the libs directory anyway, it may be needed in some cases.

  #SET(OpenCV_LIB_DIR "${OpenCV_INSTALL_PATH}/lib")

  SET(OpenCV_LIB_DIR "/usr/lib")

  LINK_DIRECTORIES(${OpenCV_LIB_DIR})

  And that worked on my Ubuntu 12.10. Remember to add the
  target_link_libraries(yourprojectname ${OpenCV_LIBS}) in your
  CMakeLists.txt.

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

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

[Touch-packages] [Bug 1167014] Re: MIssing cmake files

2016-09-06 Thread linas

Hitting this in xenial, too.

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

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

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

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

[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it should be 1.0)

** Summary changed:

- Unity8 default mouse wheel speed seen by Mir clients is 7.0 (it should be 1.0)
+ Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it should be 
1.0)

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

Title:
  Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it
  should be 1.0)

Status in Canonical System Image:
  Fix Committed
Status in QtMir:
  Fix Released
Status in qtubuntu:
  Fix Released
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4

  wheel mouse scrolling is too fast, tried with firefox and geany.

  run firefox on mir scroll up/down some random long page using the
  mouse wheel

  TEST CASE:

1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
2. Roll your mouse wheel over it and watch the log

  Expected: vscroll values of +1/-1
  Observed: vscroll values of +7/-7

  WORKAROUND:

  System Settings > Mouse & Touchpad >
  Slide the second (unlabelled) slider all the way left, and then one notch 
right.

  Turns out that unlabelled slider is the wheel scroll speed. Setting it
  one notch from the left correctly reduces the wheel speed from 7.0 to
  1.0 as Mir clients expect.

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

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

[Touch-packages] [Bug 1620870] Re: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start

2016-09-06 Thread Michael Marley

VLC crashes every time you try to start it too.

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

Title:
  After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel
  crashes every time on start

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

Bug description:
  Reverting to the previous version fixes the problem.  Here is the
  stacktrace from the crash:

  #0  0x in ?? ()
  #1  0x73896c5e in copyActionToPlatformItem 
(action=action@entry=0x55d65820, 
  item=item@entry=0x55e24380, itemsMenu=0x55ede310) at 
widgets/qmenu.cpp:3228
  #2  0x73896861 in QMenuPrivate::syncPlatformMenu 
(this=0x55e0a680) at widgets/qmenu.cpp:202
  #3  0x73896977 in QMenu::setPlatformMenu 
(this=this@entry=0x55f40df0, platformMenu=)
  at widgets/qmenu.cpp:3425
  #4  0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu 
(this=0x55ef0260, menu=0x55f40df0)
  at util/qsystemtrayicon.cpp:761
  #5  0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa 
(this=0x55ef0260)
  at util/qsystemtrayicon.cpp:710
  #6  0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys 
(this=)
  at util/qsystemtrayicon_x11.cpp:312
  #7  0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=)
  at util/qsystemtrayicon.cpp:171
  #8  0x556b6d22 in LegacySystemTray::init 
(this=this@entry=0x5603ba30)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62
  #9  0x556dea93 in StatusNotifierItem::init (this=0x5603ba30)
  at 
/build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110
  #10 0x556c0db3 in MainWin::setupSystray 
(this=this@entry=0x55d40e40)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014
  #11 0x556c10a2 in MainWin::init (this=0x55d40e40)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221
  #12 0x556c52f4 in QtUi::init (this=0x55cc4340)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81
  #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162
  #14 0x5566aa4c in main (argc=1, argv=0x7fffde88)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210

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

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

[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-06 Thread Mathieu Desnoyers

It seems odd that touching a shared object TLS (which triggers a TLS
fixup) from a constructor would deadlock. Which version of glibc are you
using ?

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

Title:
  deadlock in lttng_ust_init

Status in QtMir:
  Triaged
Status in lttng-ust package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Triaged
Status in ust package in Ubuntu:
  New

Bug description:
  Happens when running tests for
  https://code.launchpad.net/~dandrader/qtmir/content-hub-
  clipboard/+merge/303863 by CI.

  This is the backtrace of where it gets stuck:
  #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 
<_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51
  #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, 
the_map=) at dl-tls.c:778
  #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158
  #3 0x in lttng_ust_init () at lttng-ust-comm.c:369
  #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481
  #5 0x in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72
  #6 0x in _dl_init (env=, argv=, 
argc=, l=) at dl-init.c:30
  #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, 
env=0xbefff3dc) at dl-init.c:120
  #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3

  It gets stuck during initialization, more specifically, inside
  lttng_fixup_urcu_bp_tls()

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

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

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

Just tidying up. It's usually better to keep the bug title describing
what users see. Especially if your diagnosis is wrong... that title then
remains correct.

** Summary changed:

- Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, 
although gestures are not. Keyboard is thus unusable"
+ Haptics engine uses sync dbus calls. OSK becomes unusable as taps are delayed 
by 1-2 seconds and vibration doesn't occur any more (although gestures continue 
to work)

** Changed in: platform-api (Ubuntu)
   Status: Confirmed => In Progress

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

** Summary changed:

- Haptics engine uses sync dbus calls. OSK becomes unusable as taps are delayed 
by 1-2 seconds and vibration doesn't occur any more (although gestures continue 
to work)
+ OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't 
occur any more (although gestures continue to work)

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

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

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

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1556795] Re: Mouse wheel scrolling keeps going inertially (past the location I want to scroll to)

** Also affects: qtdeclarative-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Mouse wheel scrolling keeps going inertially (past the location I want
  to scroll to)

Status in Canonical System Image:
  Confirmed
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using a mouse wheel in Unity 8 > System Settings > Background works
  for scrolling. But it keeps scrolling inertially even after I've
  stopped rolling the wheel.

  This doesn't seem like a major issue, but it feels like the same kind
  of usability problem I have seen in Pocket Desktop where the web
  browser scrolls too far using two fingers on the phone (which I
  suspect is another simulated mouse wheel scroll :P). And in the web
  browser, not being able to scroll to the location you want is very
  frustrating.

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

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

[Touch-packages] [Bug 1543344] Re: QML Flickables scrolling with mouse wheel insanely fast

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

I'm going to say duplicate of bug 1556795. But please also see bug
1605513.

** This bug is no longer a duplicate of bug 1607240
   Unity8 default mouse wheel speed seen by Mir clients is 7.0 (it should be 
1.0)

** This bug has been marked a duplicate of bug 1556795
   Mouse wheel scrolling keeps going inertially (past the location I want to 
scroll to)

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

Title:
  QML Flickables scrolling with mouse wheel insanely fast

Status in Canonical System Image:
  Incomplete
Status in Canonical Pocket Desktop:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Scrolling QML Flickables with mouse wheel is way too fast.

  Steps:
  * connect a mouse to your device
  * scroll the wheel over the dash

  Expected:
  * scrolling sane

  Current:
  * scrolling insane

  The same can be observed with two-finger scrolling when using the
  virtual touchpad when you connect your device to an external screen.

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

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

[Touch-packages] [Bug 1543344] Re: QML Flickables scrolling with mouse wheel insanely fast

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

I'm not completely sure this is a duplicate of bug 1607240 because that
one technically never existed in a form that users of non-X11 apps would
notice. Because Unity8 was also defaulting to slowing down scrolling by
a similar amount, which was a guestimate hack that kept most apps
scrolling at the right speed.

We only had to fix the whole stack (bug 1607240) in order to get high
precision touchpad scrolling implemented recently.

Maybe bug 1556795 is a better description?

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

Title:
  QML Flickables scrolling with mouse wheel insanely fast

Status in Canonical System Image:
  Incomplete
Status in Canonical Pocket Desktop:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Scrolling QML Flickables with mouse wheel is way too fast.

  Steps:
  * connect a mouse to your device
  * scroll the wheel over the dash

  Expected:
  * scrolling sane

  Current:
  * scrolling insane

  The same can be observed with two-finger scrolling when using the
  virtual touchpad when you connect your device to an external screen.

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

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

[Touch-packages] [Bug 1607223] Re: Two-finger touchpad scrolling is not accurate in apps under Unity8 (but is in Mir demo servers)

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

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

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

Title:
  Two-finger touchpad scrolling is not accurate in apps under Unity8
  (but is in Mir demo servers)

Status in Canonical System Image:
  Fix Committed
Status in QtMir:
  Fix Released
Status in qtubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  Smooth two-finger touchpad scrolling is not accurate in apps under
  Unity8 (but is in Mir demo servers).

  The reason appears to be because QtMir drops the nice float vscroll
  precision that Mir gives it and converts that into an int with very
  limited resolution:

  void handleWheelEvent(ulong timestamp, QPoint angleDelta,
  Qt::KeyboardModifiers mods) override

  QPoint is a pair of integers, but touchpad v/hscroll values are
  floats.

  I have only just discovered that although my new smooth scrolling
  support about to land in Xmir works in Mir's demo servers, it doesn't
  work when I run the same binaries under Unity8.

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

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

[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed seen by Mir clients is 7.0 (it should be 1.0)

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

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

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

Title:
  Unity8 default mouse wheel speed seen by Mir clients is 7.0 (it should
  be 1.0)

Status in Canonical System Image:
  Fix Committed
Status in QtMir:
  Fix Released
Status in qtubuntu:
  Fix Released
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4

  wheel mouse scrolling is too fast, tried with firefox and geany.

  run firefox on mir scroll up/down some random long page using the
  mouse wheel

  TEST CASE:

1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
2. Roll your mouse wheel over it and watch the log

  Expected: vscroll values of +1/-1
  Observed: vscroll values of +7/-7

  WORKAROUND:

  System Settings > Mouse & Touchpad >
  Slide the second (unlabelled) slider all the way left, and then one notch 
right.

  Turns out that unlabelled slider is the wheel scroll speed. Setting it
  one notch from the left correctly reduces the wheel speed from 7.0 to
  1.0 as Mir clients expect.

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

-- 
Mailing list: https://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 1620854] [NEW] Audio playback works in slow motion after resume from suspension

2016-09-06 Thread Luke Yelavich

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

 duplicate 1580882


** This bug has been marked a duplicate of bug 1580882
   [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

** This bug has been marked a duplicate of bug 1580882
   [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

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

Title:
  Audio playback works in slow motion after resume from suspension

Status in alsa-driver package in Ubuntu:
  New
Status in linux-lts-xenial package in Ubuntu:
  New

Bug description:
  The audio playback through HDMI works in slow motion after a resume
  from suspension.

  Before the suspension the audio works as expected on both the "internal 
speaker" and "HDMI" output cards.
  When you suspend (and then resume) the system the audio playback starts 
acting weird through the HDMI output card.
  The audio is played in slow motion and you can also see that the time of 
playback is going on slower than the time in real life.

  Let me describe one of the tests I've performed.
   I've booted the system and started playing a song in vlc.
   I've opened the Ubuntu sound settings.
   I've selected the "HDMI" output card and the playback worked as expected.
   I've selected the "Internal speakers" output card and the playback worked as 
expected.
   
   Then I've closed vlc, suspended and then resumed the system.
   
   I've started playing a song in vlc again.
   I've opened the Ubuntu sound settings.
   I've selected the "HDMI" output card and the playback started working in 
slow motion: the audio was extremely slow and also the time indicator was 
working slowly (5 seconds of the song were played in about 10 seconds "in real 
life").
   I've selected the "Internal speakers" output card and the playback started 
working as expected again.

  Please note that after a resume from suspension when you select the "Internal 
speakers" card the bug disappears and when you select the "HDMI" card the bug 
appears again.
  I've tested this bug also with videos in vlc, in a browser and in totem. The 
bug appears (or disappears) in the same way.
  The bug affects every kind of audio, including system sounds.

  Everything works fine before a suspension.
  The only way I found to restore the before-suspension behavior is a reboot.

  
  Steps to reproduce:
   * Make sure this is a fresh boot (never suspended since the last boot).
   * Play something with audio
 (tested with: video in browser, song in vlc and Ubuntu speaker tests).
   * Select "Speakers - Internal audio" as output device (Audio works as 
expected).
   * Select "HDMI - Internal audio" as output device (Audio works as expected).
   * Stop the audio playback.
   * Suspend and resume the system.
   * Play something again.
   * Select "Speakers - Internal audio" as output device (Audio works as 
expected).
   * Select "HDMI - Internal audio" as output device (The bug appears).

  Expected behavior:
   * Audio playback should work well through "Speakers - Internal audio" as 
output device.
   * Audio playback should work well through "HDMI - Internal audio" as output 
device.

  Actual behavior:
   * Audio playback is working well through "Speakers - Internal audio" as 
output device.
   * Audio playback is working in slow motion through "HDMI - Internal audio" 
as output device.

  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:  riccardo   3492 F pulseaudio
   /dev/snd/controlC1:  riccardo   3492 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep  6 23:36:10 2016
  InstallationDate: Installed on 2016-04-22 (136 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_Type: Sound works for a while, then breaks
  Title: [HDA-Intel - HDA Intel HDMI, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

** Tags added: performance

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

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

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620870] Re: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start

2016-09-06 Thread Michael Marley

Specifically, the "libqt5widgets5" package seems to be at fault.  If I
revert only this package to the previous version Quassel works properly.

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

Title:
  After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel
  crashes every time on start

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

Bug description:
  Reverting to the previous version fixes the problem.  Here is the
  stacktrace from the crash:

  #0  0x in ?? ()
  #1  0x73896c5e in copyActionToPlatformItem 
(action=action@entry=0x55d65820, 
  item=item@entry=0x55e24380, itemsMenu=0x55ede310) at 
widgets/qmenu.cpp:3228
  #2  0x73896861 in QMenuPrivate::syncPlatformMenu 
(this=0x55e0a680) at widgets/qmenu.cpp:202
  #3  0x73896977 in QMenu::setPlatformMenu 
(this=this@entry=0x55f40df0, platformMenu=)
  at widgets/qmenu.cpp:3425
  #4  0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu 
(this=0x55ef0260, menu=0x55f40df0)
  at util/qsystemtrayicon.cpp:761
  #5  0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa 
(this=0x55ef0260)
  at util/qsystemtrayicon.cpp:710
  #6  0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys 
(this=)
  at util/qsystemtrayicon_x11.cpp:312
  #7  0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=)
  at util/qsystemtrayicon.cpp:171
  #8  0x556b6d22 in LegacySystemTray::init 
(this=this@entry=0x5603ba30)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62
  #9  0x556dea93 in StatusNotifierItem::init (this=0x5603ba30)
  at 
/build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110
  #10 0x556c0db3 in MainWin::setupSystray 
(this=this@entry=0x55d40e40)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014
  #11 0x556c10a2 in MainWin::init (this=0x55d40e40)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221
  #12 0x556c52f4 in QtUi::init (this=0x55cc4340)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81
  #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162
  #14 0x5566aa4c in main (argc=1, argv=0x7fffde88)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210

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

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

[Touch-packages] [Bug 1620870] [NEW] After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start

2016-09-06 Thread Michael Marley

Public bug reported:

Reverting to the previous version fixes the problem.  Here is the
stacktrace from the crash:

#0  0x in ?? ()
#1  0x73896c5e in copyActionToPlatformItem 
(action=action@entry=0x55d65820, 
item=item@entry=0x55e24380, itemsMenu=0x55ede310) at 
widgets/qmenu.cpp:3228
#2  0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) 
at widgets/qmenu.cpp:202
#3  0x73896977 in QMenu::setPlatformMenu 
(this=this@entry=0x55f40df0, platformMenu=)
at widgets/qmenu.cpp:3425
#4  0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu 
(this=0x55ef0260, menu=0x55f40df0)
at util/qsystemtrayicon.cpp:761
#5  0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa 
(this=0x55ef0260)
at util/qsystemtrayicon.cpp:710
#6  0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys 
(this=)
at util/qsystemtrayicon_x11.cpp:312
#7  0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=)
at util/qsystemtrayicon.cpp:171
#8  0x556b6d22 in LegacySystemTray::init 
(this=this@entry=0x5603ba30)
at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62
#9  0x556dea93 in StatusNotifierItem::init (this=0x5603ba30)
at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110
#10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40)
at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014
#11 0x556c10a2 in MainWin::init (this=0x55d40e40)
at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221
#12 0x556c52f4 in QtUi::init (this=0x55cc4340)
at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81
#13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20)
at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162
#14 0x5566aa4c in main (argc=1, argv=0x7fffde88)
at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel
  crashes every time on start

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

Bug description:
  Reverting to the previous version fixes the problem.  Here is the
  stacktrace from the crash:

  #0  0x in ?? ()
  #1  0x73896c5e in copyActionToPlatformItem 
(action=action@entry=0x55d65820, 
  item=item@entry=0x55e24380, itemsMenu=0x55ede310) at 
widgets/qmenu.cpp:3228
  #2  0x73896861 in QMenuPrivate::syncPlatformMenu 
(this=0x55e0a680) at widgets/qmenu.cpp:202
  #3  0x73896977 in QMenu::setPlatformMenu 
(this=this@entry=0x55f40df0, platformMenu=)
  at widgets/qmenu.cpp:3425
  #4  0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu 
(this=0x55ef0260, menu=0x55f40df0)
  at util/qsystemtrayicon.cpp:761
  #5  0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa 
(this=0x55ef0260)
  at util/qsystemtrayicon.cpp:710
  #6  0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys 
(this=)
  at util/qsystemtrayicon_x11.cpp:312
  #7  0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=)
  at util/qsystemtrayicon.cpp:171
  #8  0x556b6d22 in LegacySystemTray::init 
(this=this@entry=0x5603ba30)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62
  #9  0x556dea93 in StatusNotifierItem::init (this=0x5603ba30)
  at 
/build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110
  #10 0x556c0db3 in MainWin::setupSystray 
(this=this@entry=0x55d40e40)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014
  #11 0x556c10a2 in MainWin::init (this=0x55d40e40)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221
  #12 0x556c52f4 in QtUi::init (this=0x55cc4340)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81
  #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162
  #14 0x5566aa4c in main (argc=1, argv=0x7fffde88)
  at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210

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

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

[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-06 Thread Simon Marchi

Which version of liblttng-ust is that?

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

Title:
  deadlock in lttng_ust_init

Status in QtMir:
  Triaged
Status in lttng-ust package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Triaged
Status in ust package in Ubuntu:
  New

Bug description:
  Happens when running tests for
  https://code.launchpad.net/~dandrader/qtmir/content-hub-
  clipboard/+merge/303863 by CI.

  This is the backtrace of where it gets stuck:
  #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 
<_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51
  #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, 
the_map=) at dl-tls.c:778
  #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158
  #3 0x in lttng_ust_init () at lttng-ust-comm.c:369
  #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481
  #5 0x in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72
  #6 0x in _dl_init (env=, argv=, 
argc=, l=) at dl-init.c:30
  #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, 
env=0xbefff3dc) at dl-init.c:120
  #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3

  It gets stuck during initialization, more specifically, inside
  lttng_fixup_urcu_bp_tls()

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

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

[Touch-packages] [Bug 1620855] Re: /usr/bin/signon-ui:11:QXcbConnection::QXcbConnection:QXcbIntegration::QXcbIntegration:QXcbIntegrationPlugin::create:loadIntegration:QPlatformIntegrationFactory::crea

2016-09-06 Thread Brian Murray

There are in excess of 150,000 crashes about this for Trusty and it
seems to be an on-going issue.

** Changed in: signon-ui (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/bin/signon-
  
ui:11:QXcbConnection::QXcbConnection:QXcbIntegration::QXcbIntegration:QXcbIntegrationPlugin::create:loadIntegration:QPlatformIntegrationFactory::create

Status in signon-ui package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding signon-ui.  This problem was most recently seen with version
  0.16+14.04.20140304.is.0.15+14.04.20140313-0ubuntu2, the problem page
  at
  https://errors.ubuntu.com/problem/58786f7a2c0e1cad8ecb7b677393bc7ebf390262
  contains more details.

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

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

[Touch-packages] [Bug 1620855] [NEW] /usr/bin/signon-ui:11:QXcbConnection::QXcbConnection:QXcbIntegration::QXcbIntegration:QXcbIntegrationPlugin::create:loadIntegration:QPlatformIntegrationFactory::cr

2016-09-06 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding signon-ui.  This problem was most recently seen with version
0.16+14.04.20140304.is.0.15+14.04.20140313-0ubuntu2, the problem page at
https://errors.ubuntu.com/problem/58786f7a2c0e1cad8ecb7b677393bc7ebf390262
contains more details.

** Affects: signon-ui (Ubuntu)
 Importance: High
 Status: New


** Tags: trusty utopic vivid

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

Title:
  /usr/bin/signon-
  
ui:11:QXcbConnection::QXcbConnection:QXcbIntegration::QXcbIntegration:QXcbIntegrationPlugin::create:loadIntegration:QPlatformIntegrationFactory::create

Status in signon-ui package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding signon-ui.  This problem was most recently seen with version
  0.16+14.04.20140304.is.0.15+14.04.20140313-0ubuntu2, the problem page
  at
  https://errors.ubuntu.com/problem/58786f7a2c0e1cad8ecb7b677393bc7ebf390262
  contains more details.

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

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

[Touch-packages] [Bug 1620854] Re: Audio playback works in slow motion after resume from suspension

2016-09-06 Thread Riccardo Maffei

** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New

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

Title:
Audio playback works in slow motion after resume from suspension

Status in alsa-driver package in Ubuntu:
New
Status in linux-lts-xenial package in Ubuntu:
New

Bug description:
The audio playback through HDMI works in slow motion after a resume
from suspension.

Before the suspension the audio works as expected on both the "internal
speaker" and "HDMI" output cards.
When you suspend (and then resume) the system the audio playback starts
acting weird through the HDMI output card.
The audio is played in slow motion and you can also see that the time of
playback is going on slower than the time in real life.

Let me describe one of the tests I've performed.
I've booted the system and started playing a song in vlc.
I've opened the Ubuntu sound settings.
I've selected the "HDMI" output card and the playback worked as expected.
I've selected the "Internal speakers" output card and the playback worked as
expected.

Then I've closed vlc, suspended and then resumed the system.

I've started playing a song in vlc again.
I've opened the Ubuntu sound settings.
I've selected the "HDMI" output card and the playback started working in
slow motion: the audio was extremely slow and also the time indicator was
working slowly (5 seconds of the song were played in about 10 seconds "in real
life").
I've selected the "Internal speakers" output card and the playback started
working as expected again.

Please note that after a resume from suspension when you select the "Internal
speakers" card the bug disappears and when you select the "HDMI" card the bug
appears again.
I've tested this bug also with videos in vlc, in a browser and in totem. The
bug appears (or disappears) in the same way.
The bug affects every kind of audio, including system sounds.

Everything works fine before a suspension.
The only way I found to restore the before-suspension behavior is a reboot.

Steps to reproduce:
* Make sure this is a fresh boot (never suspended since the last boot).
* Play something with audio
(tested with: video in browser, song in vlc and Ubuntu speaker tests).
* Select "Speakers - Internal audio" as output device (Audio works as
expected).
* Select "HDMI - Internal audio" as output device (Audio works as expected).
* Stop the audio playback.
* Suspend and resume the system.
* Play something again.
* Select "Speakers - Internal audio" as output device (Audio works as
expected).
* Select "HDMI - Internal audio" as output device (The bug appears).

Expected behavior:
* Audio playback should work well through "Speakers - Internal audio" as
output device.
* Audio playback should work well through "HDMI - Internal audio" as output
device.

Actual behavior:
* Audio playback is working well through "Speakers - Internal audio" as
output device.
* Audio playback is working in slow motion through "HDMI - Internal audio"
as output device.

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: riccardo 3492 F pulseaudio
/dev/snd/controlC1: riccardo 3492 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 6 23:36:10 2016
InstallationDate: Installed on 2016-04-22 (136 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64
(20160421)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Audio interno - HDA Intel PCH
Symptom_Type: Sound works for a while, then breaks
Title: [HDA-Intel - HDA Intel HDMI, playback] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 229D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.13
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.30:bd10/22/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY 17 Notebook PC
dmi.product.version: 097312405F1620180
dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:

[Touch-packages] [Bug 1620854] [NEW] Audio playback works in slow motion after resume from suspension

2016-09-06 Thread Riccardo Maffei

Public bug reported:

The audio playback through HDMI works in slow motion after a resume from
suspension.

Before the suspension the audio works as expected on both the "internal 
speaker" and "HDMI" output cards.
When you suspend (and then resume) the system the audio playback starts acting 
weird through the HDMI output card.
The audio is played in slow motion and you can also see that the time of 
playback is going on slower than the time in real life.

Let me describe one of the tests I've performed.
 I've booted the system and started playing a song in vlc.
 I've opened the Ubuntu sound settings.
 I've selected the "HDMI" output card and the playback worked as expected.
 I've selected the "Internal speakers" output card and the playback worked as 
expected.
 
 Then I've closed vlc, suspended and then resumed the system.
 
 I've started playing a song in vlc again.
 I've opened the Ubuntu sound settings.
 I've selected the "HDMI" output card and the playback started working in slow 
motion: the audio was extremely slow and also the time indicator was working 
slowly (5 seconds of the song were played in about 10 seconds "in real life").
 I've selected the "Internal speakers" output card and the playback started 
working as expected again.

Please note that after a resume from suspension when you select the "Internal 
speakers" card the bug disappears and when you select the "HDMI" card the bug 
appears again.
I've tested this bug also with videos in vlc, in a browser and in totem. The 
bug appears (or disappears) in the same way.
The bug affects every kind of audio, including system sounds.

Everything works fine before a suspension.
The only way I found to restore the before-suspension behavior is a reboot.


Steps to reproduce:
 * Make sure this is a fresh boot (never suspended since the last boot).
 * Play something with audio
   (tested with: video in browser, song in vlc and Ubuntu speaker tests).
 * Select "Speakers - Internal audio" as output device (Audio works as 
expected).
 * Select "HDMI - Internal audio" as output device (Audio works as expected).
 * Stop the audio playback.
 * Suspend and resume the system.
 * Play something again.
 * Select "Speakers - Internal audio" as output device (Audio works as 
expected).
 * Select "HDMI - Internal audio" as output device (The bug appears).

Expected behavior:
 * Audio playback should work well through "Speakers - Internal audio" as 
output device.
 * Audio playback should work well through "HDMI - Internal audio" as output 
device.

Actual behavior:
 * Audio playback is working well through "Speakers - Internal audio" as output 
device.
 * Audio playback is working in slow motion through "HDMI - Internal audio" as 
output device.

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:  riccardo   3492 F pulseaudio
 /dev/snd/controlC1:  riccardo   3492 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep  6 23:36:10 2016
InstallationDate: Installed on 2016-04-22 (136 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Audio interno - HDA Intel PCH
Symptom_Type: Sound works for a while, then breaks
Title: [HDA-Intel - HDA Intel HDMI, playback] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 229D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.13
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd10/22/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY 17 Notebook PC
dmi.product.version: 097312405F1620180
dmi.sys.vendor: Hewlett-Packard

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

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kernel-sound 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/1620854

Title:
  Audio playback works in slow motion after resume from suspension

Status in alsa-driver package in Ubuntu:
  New
Status in linux-lts-xenial package in Ubuntu:
  New

Bug description:
  The audio playback through HDMI works in slow motion after a

[Touch-packages] [Bug 1577247] Re: webbrowser-app

2016-09-06 Thread Anthony

** Changed in: webbrowser-app (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  webbrowser-app

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  (webbrowser-app:4034): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4034): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4034): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
  QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
  file:///usr/share/webbrowser-app/webbrowser/ContentPickerDialog.qml:22:1: 
module "Ubuntu.Content" is not installed
  file:///usr/share/webbrowser-app/webbrowser/ContentDownloadDialog.qml:22:1: 
module "Ubuntu.Content" is not installed
  file:///usr/share/webbrowser-app/ContentHandler.qml:20:1: module 
"Ubuntu.Content" is not installed
  file:///usr/share/webbrowser-app/webbrowser/DownloadHandler.qml:20:1: module 
"Ubuntu.DownloadManager" is not installed
  Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
  Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
  Input device added: "HDA Intel Front Mic" "/dev/input/event7" QFlags(0x20)
  Input device added: "HDA Intel Rear Mic" "/dev/input/event8" QFlags(0x20)
  Input device added: "HDA Intel Line" "/dev/input/event9" QFlags(0x20)
  Input device added: "HDA Intel Line Out" "/dev/input/event10" QFlags(0x20)
  Input device added: "HDA Intel Front Headphone" "/dev/input/event11" 
QFlags(0x20)
  Input device added: "Twin USB Joystick" "/dev/input/event5" QFlags()
  Input device added: "Twin USB Joystick" "/dev/input/event6" QFlags()
  Input device added: "BTC USB Multimedia Keyboard" "/dev/input/event2" 
QFlags(0x1|0x10)
  Input device added: "BTC USB Multimedia Keyboard" "/dev/input/event3" 
QFlags(0x1)
  Input device added: "Genius Optical Mouse" "/dev/input/event4" QFlags(0x2)
  Input device added: "UVC Camera (046d:0802)" "/dev/input/event12" QFlags(0x1)
  Failed to create OpenGL context for format QSurfaceFormat(version 2.0, 
options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, 
blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, 
swapBehavior 2, swapInterval 1, profile  0) 
  Aborted (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  2 02:18:38 2016
  InstallationDate: Installed on 2016-04-27 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1573762] Re: Ubuntu 16.04 LTS - webbrowser-app does not launch

2016-09-06 Thread Anthony

I get the above errors, and when I try to launch with sudo I get the
following:

$ sudo webbrowser-app 
[sudo] password for *: 
No protocol specified
QXcbConnection: Could not connect to display :0
Aborted (core dumped)

Good old Nvidia doing what it does best. I am using the Nvidia
proprietary driver instead of xorg because the latter kept giving me
black screens with cursor on system wakeup (I say this in case the video
driver is a cause of the webbrowser fail).

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

Title:
   Ubuntu 16.04 LTS - webbrowser-app does not launch

Status in Oxide:
  Confirmed
Status in webbrowser-app:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When trying to launch the webbrowser-app, it flashes for a second and
  then disappears, launching it from terminal shows this error :

  (webbrowser-app:9153): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied. dconf will not work properly. 
  file:///usr/share/webbrowser-app/webbrowser/ContentPickerDialog.qml:22:1: 
module "Ubuntu.Content" is not installed 
  file:///usr/share/webbrowser-app/webbrowser/ContentDownloadDialog.qml:22:1: 
module "Ubuntu.Content" is not installed 
  file:///usr/share/webbrowser-app/ContentHandler.qml:20:1: module 
"Ubuntu.Content" is not installed 
  file:///usr/share/webbrowser-app/webbrowser/DownloadHandler.qml:20:1: module 
"Ubuntu.DownloadManager" is not installed 
  [0422/170822:ERROR:oxide_qt_gl_context_dependent.cc(82)] Unable to create 
adopted GL context for platform: xcb - unexpected result from 
QPlatformNativeInterface::nativeResourceForContext 
  shm_open() failed: Permission denied 
  [0422/170822:ERROR:gl_context_glx.cc(59)] Failed to create GL context with 
glXCreateContextAttribsARB. 
  [0422/170822:ERROR:gpu_info_collector.cc(47)] gfx::GLContext::CreateGLContext 
failed 
  [0422/170822:ERROR:gpu_info_collector.cc(115)] Could not create context for 
info collection. 
  [0422/170822:ERROR:oxide_browser_main_parts.cc(299)] 
gpu::CollectContextGraphicsInfo failed 
  qml: Loaded 5 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-mobile.js 
  Failed to create OpenGL context for format QSurfaceFormat(version 2.0, 
options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, 
blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, 
swapBehavior 2, swapInterval 1, profile 0) 
  Aborted

  This issue occurs when using the NVIDIA graphics adapter, when
  switching to Intel graphics, webbrowser-app launches as expected.

  Ubuntu 16.04 LTS (installation date : 2016-04-21) | Intel i7-4710MQ +
  HD Graphics 4600 | NVIDIA GTX 860M (drivers version 361.42)

  webbrowser-app  : 0.23+16.04.20160413-0ubuntu1 500 | 500
  http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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

[Touch-packages] [Bug 1424263] Re: Broken dependencies

2016-09-06 Thread Brian Murray

This is not an issue with the version of steam in the Ubuntu archive
only with the .deb file provided by Valve.

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

** Summary changed:

- Broken dependencies
+ steam deb file isn't aware of HWE stacks

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

Title:
  steam deb file isn't aware of HWE stacks

Status in mesa package in Ubuntu:
  Invalid
Status in steam package in Ubuntu:
  Invalid

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 21 17:22:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1424263] Re: Broken dependencies

2016-09-06 Thread Brian Murray

If you installed steam from here, http://store.steampowered.com/about/,
then on first run it tries to install 'libgl1-mesa-dri:i386 libgl1-mesa-
glx:i386 libc6:i386'.  If you install the appropriate packages for your
HWE stack first, e.g. sudo apt-get install libgl1-mesa-dri-lts-wily:i386
libgl1-mesa-glx-lts-wily:i386, then you can successfully run steam.  To
find out what HWE stack you have installed you can use the following
command:

dpkg -l | grep ii.*-lts

Regardless, this (the steam application manually trying to install
packages) is not something we the developers of Ubuntu can fix so I'm
setting this to Invalid.


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

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

Title:
  steam deb file isn't aware of HWE stacks

Status in mesa package in Ubuntu:
  Invalid
Status in steam package in Ubuntu:
  Invalid

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 21 17:22:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

2016-09-06 Thread Dan Kortschak

When I started looking at this problem, the machine would not boot
without nomodeset. This is no longer the case - and removing that fixes
the problem.

Thank you for looking at this, Timo. Please mark as invalid.

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 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 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date:

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

2016-09-06 Thread Victor Gabillon

I have the same problem, and agree with Daniel. For the phone at least,
I think that when the left launcher is revealed, the first touch that is
outside of the left launcher should only hide the left launcher and not
activate whatever is outside of the launcher. It would be very practical
and intuitive.

-- 
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 1620844] [NEW] package keyboard-configuration 1.108ubuntu15.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück

2016-09-06 Thread yocu2016

Public bug reported:

This error occured after upgrading from ubuntu 14.04 to 16.04 a couple of days 
age.
It still exists.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Sep  7 00:25:46 2016
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 127 zurück
InstallationDate: Installed on 2013-09-18 (1084 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu15.2 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 127 zurück
UpgradeStatus: Upgraded to xenial on 2016-08-29 (8 days ago)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

** Attachment removed: "DpkgHistoryLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1620844/+attachment/4735801/+files/DpkgHistoryLog.txt

** Attachment removed: "Df.txt"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1620844/+attachment/4735799/+files/Df.txt

** Attachment removed: "Dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1620844/+attachment/4735800/+files/Dmesg.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1620844/+attachment/4735803/+files/JournalErrors.txt

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

Title:
  package keyboard-configuration 1.108ubuntu15.2 failed to
  install/upgrade: Unterprozess installiertes post-installation-Skript
  gab den Fehlerwert 127 zurück

Status in console-setup package in Ubuntu:
  New

Bug description:
  This error occured after upgrading from ubuntu 14.04 to 16.04 a couple of 
days age.
  It still exists.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Sep  7 00:25:46 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 127 zurück
  InstallationDate: Installed on 2013-09-18 (1084 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.108ubuntu15.2 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 127 zurück
  UpgradeStatus: Upgraded to xenial on 2016-08-29 (8 days ago)

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

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

[Touch-packages] [Bug 1471998] Re: [enhancement] Support copy-paste between X and Mir

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

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

  [ Daniel d'Andrada ]
  * DBusFocusInfo: added isSurfaceFocused(serializedId)
  * Use content-hub for clipboard services (LP: #1471998)
  * Don't link tests against LTTng

 -- Ken VanDine   Wed, 31 Aug 2016 01:52:12
+

** 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 content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1471998

Title:
  [enhancement] Support copy-paste between X and Mir

Status in Canonical System Image:
  Fix Committed
Status in Libertine:
  Fix Committed
Status in Libertine devel series:
  Fix Committed
Status in Libertine trunk series:
  Fix Committed
Status in Mir:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in libertine package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  X applications should be able to paste from Mir applications and vice
  versa.

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

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

[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init

2016-09-06 Thread Gerry Boland

This issue was worked around, but with a far-from-ideal solution

** Also affects: lttng-ust (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: qtmir
   Status: New => Triaged

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

** Branch linked: lp:~dandrader/qtmir/no-lttng-on-tests

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

Title:
  deadlock in lttng_ust_init

Status in QtMir:
  Triaged
Status in lttng-ust package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Triaged
Status in ust package in Ubuntu:
  New

Bug description:
  Happens when running tests for
  https://code.launchpad.net/~dandrader/qtmir/content-hub-
  clipboard/+merge/303863 by CI.

  This is the backtrace of where it gets stuck:
  #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 
<_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51
  #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, 
the_map=) at dl-tls.c:778
  #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158
  #3 0x in lttng_ust_init () at lttng-ust-comm.c:369
  #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481
  #5 0x in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72
  #6 0x in _dl_init (env=, argv=, 
argc=, l=) at dl-init.c:30
  #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, 
env=0xbefff3dc) at dl-init.c:120
  #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3

  It gets stuck during initialization, more specifically, inside
  lttng_fixup_urcu_bp_tls()

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

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

[Touch-packages] [Bug 1620345] Re: Slow startup due to FIPS selftest if openssl loaded

2016-09-06 Thread Seth Arnold

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

Nikita, thanks for the report; there's an openssl update currently in
the -proposed pocket that removes this fledgling FIPS support, including
the slow startup tests. Please see
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1614210 for full
details.

Thanks

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

Title:
  Slow startup due to FIPS selftest if openssl loaded

Status in openssl package in Ubuntu:
  New

Bug description:
  I recently noticed that the PHP testsuite runs significantly slower if
  openssl is enabled. E.g. running "make test TESTS=tests" takes 7
  seconds without openssl and 37 seconds with. This is a factor of five
  difference.

  After a quick check using callgrind, it turns out that the vast
  majority of the time is spent in performing a FIPS_selftest(). This
  was very surprising, and I was initially afraid that Ubuntu had
  enabled the OpenSSL FIPS mode, which is well known to degrade
  security. However, it seems that this is not the case, and Ubuntu has
  simply patched OpenSSL to always perform the FIPS_selftest(),
  independently of whether FIPS mode is used.

  I'm not entirely sure what should/can be done about this. I understand
  the motivation for always performing a self-test and that it is not a
  common workload to start a process many hundreds of times in a row to
  perform a small task. However, it should be noted that OpenSSL
  acknowledges [0] that the test is unnecessarily slow, because they
  cannot change the current implementation without invalidating the FIPS
  certification. This indicates that it should be possible to perform a
  cheaper self-test.

   [0]: https://www.openssl.org/docs/fipsnotes.html

  ---

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  libssl-dev:
Installed: 1.0.2g-1ubuntu4.2
Candidate: 1.0.2g-1ubuntu4.2

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

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

[Touch-packages] [Bug 1620345] Re: Slow startup due to FIPS selftest if openssl loaded

2016-09-06 Thread Seth Arnold

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

** This bug has been marked a duplicate of bug 1591797
   Only run FIPS self tests when FIPS is enabled

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

Title:
  Slow startup due to FIPS selftest if openssl loaded

Status in openssl package in Ubuntu:
  New

Bug description:
  I recently noticed that the PHP testsuite runs significantly slower if
  openssl is enabled. E.g. running "make test TESTS=tests" takes 7
  seconds without openssl and 37 seconds with. This is a factor of five
  difference.

  After a quick check using callgrind, it turns out that the vast
  majority of the time is spent in performing a FIPS_selftest(). This
  was very surprising, and I was initially afraid that Ubuntu had
  enabled the OpenSSL FIPS mode, which is well known to degrade
  security. However, it seems that this is not the case, and Ubuntu has
  simply patched OpenSSL to always perform the FIPS_selftest(),
  independently of whether FIPS mode is used.

  I'm not entirely sure what should/can be done about this. I understand
  the motivation for always performing a self-test and that it is not a
  common workload to start a process many hundreds of times in a row to
  perform a small task. However, it should be noted that OpenSSL
  acknowledges [0] that the test is unnecessarily slow, because they
  cannot change the current implementation without invalidating the FIPS
  certification. This indicates that it should be possible to perform a
  cheaper self-test.

   [0]: https://www.openssl.org/docs/fipsnotes.html

  ---

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  libssl-dev:
Installed: 1.0.2g-1ubuntu4.2
Candidate: 1.0.2g-1ubuntu4.2

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

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

[Touch-packages] [Bug 1471998] Re: [enhancement] Support copy-paste between X and Mir

This bug was fixed in the package libertine -
1.4+16.10.20160901.1-0ubuntu1

---
libertine (1.4+16.10.20160901.1-0ubuntu1) yakkety; urgency=medium

  [ Chris Townsend ]
  * Add a background process that allows copying & pasting between an X app,
another X app, and native Unity 8 apps. (LP: #1471998)

 -- Ken VanDine   Thu, 01 Sep 2016 20:06:21
+

** Changed in: libertine (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 content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1471998

Title:
  [enhancement] Support copy-paste between X and Mir

Status in Canonical System Image:
  Fix Committed
Status in Libertine:
  Fix Committed
Status in Libertine devel series:
  Fix Committed
Status in Libertine trunk series:
  Fix Committed
Status in Mir:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in libertine package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  X applications should be able to paste from Mir applications and vice
  versa.

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

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

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

2016-09-06 Thread GeeMac

Sorry I meant "Startup Applications" not system startup.

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

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

Status in xorg package in Ubuntu:
  New

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

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

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

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

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

To manage notifications about this bug go to:

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

2016-09-06 Thread GeeMac

Just for the heck of it I tried switching drivers again.

Nvidia (proprietary Tested) driver  No difference at reboot or relog.

Nvidia (proprietary) No difference at reboot or relog.

X.Org X Server Nouveau will boot at 1280x720 (720P) Will not save 1920x1080 
when changed.  Nouveau is unstable with this system.
Video tearing and flashing within a few minuets of any screen changes from a 
static desktop.

I hope the above information is answering your questions.
I would like to get this resolved soon since it is getting tiresome to have to 
type the xrander in terminal every time.
I would place it in system startup, but it won't save after added. See Bug 
#1617129

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

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

Status in xorg package in Ubuntu:
  New

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

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

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

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

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

[Touch-packages] [Bug 1008050] Re: After resume from suspend, power-indicator is unaware of battery changes

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

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

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

Title:
  After resume from suspend, power-indicator is unaware of battery
  changes

Status in indicator-power:
  Incomplete
Status in indicator-power package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When resuming from suspend, power-indicator seems to be frozen.
  Remaining time is not updated, even if I (un)plug AC.

  Only way to restore normal operation without reboot is to start gnome-
  power-manager...  the indicator becomes responsive again.

  Probably related to https://bugs.launchpad.net/indicator-
  power/+bug/983928 and/or https://bugs.launchpad.net/indicator-
  power/+bug/994745

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

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

[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-09-06 Thread Tim Gardner

Test kernel at http://people.canonical.com/~rtg/lsattr-lp1619918/

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-09-06 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2016-September/079897.html

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-09-06 Thread Tim Gardner

Commit 02da2d72174c61988eb4456b53f405e3ebdebce4 merged in v4.7

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

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

** Also affects: e2fsprogs (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: e2fsprogs (Ubuntu Yakkety)
   Importance: Undecided
   Status: Invalid

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: Incomplete

** Also affects: e2fsprogs (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => Fix Released

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Vivid)
   Status: New => In Progress

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Touch-packages] [Bug 1620799] [NEW] Desktop too big

2016-09-06 Thread William Hughes

Public bug reported:

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

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

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


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

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

Title:
  Desktop too big

Status in xorg package in Ubuntu:
  New

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep  6 14:32:33 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series

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

2016-09-06 Thread OpenSource

Similar results for me. Pops up every 40 seconds or so.

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

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

Status in pulseaudio package in Ubuntu:
Confirmed

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

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

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

Thanks.

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

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

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

[Touch-packages] [Bug 1406810] Re: screen is garbled with 14.10 (was fine with 14.04)

2016-09-06 Thread Nicolas Jungers

Christopher Penalver, I've now tested the 4.8-rc5. Unsurprisingly the
result is the same than for 4.8-rc4.

Do you think that testing each new kernel version one after the other is
a path to a solution? It feels more like a path to madness to me.

To recap, 14.04 with kernel 3.13 *was* working and both 14.10 (with
kernel 3.16) - 15.04 (with kernel 3.19) *were not* working. 15.10 wasn't
working either but Apple released in October a "bios" upgrade that you
make me apply to debug the situation. Since then 14.04 doesn't work
anymore.

Do you have any suggestion?

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

Title:
  screen is garbled with 14.10 (was fine with 14.04)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On a iMac Alu 2010, when upgrading from 14.04 desktop to 14.10 desktop
  or installing 10.10 server (SSH package only) the screen shows thin 
horizontal lines moving on a black background.

  /etc/X11/xorg.conf is absent (using default config),
  /var/log/Xorg.0.log doesn't show any error beside the lack of the
  fglrx module. But I doubt it's relevant with the symptoms appearing on
  the server install.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.19
  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
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850] 
[1002:944a] (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00b5]
  InstallationDate: Installed on 2015-01-01 (440 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: Apple Inc. iMac11,1
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic 
root=UUID=f19c8f84-1553-4a36-889a-acfb8a13da9a ro
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-79-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 03/17/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM111.88Z.0034.B02.1003171314
  dmi.board.name: Mac-F2268DAE
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268DAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM111.88Z.0034.B02.1003171314:bd03/17/10:svnAppleInc.:pniMac11,1:pvr1.0:rvnAppleInc.:rnMac-F2268DAE:rvr:cvnAppleInc.:ct13:cvrMac-F2268DAE:
  dmi.product.name: iMac11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Mar 16 19:43:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors

2016-09-06 Thread Cyrille37

Hi,
I've same errors:

on a fresh Ubuntu 16.04 LTS,
in /var/log/syslog :

Sep  6 21:20:56 cyrille-W740SU org.gnome.zeitgeist.Engine[4367]: ** 
(zeitgeist-datahub:4855): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
Sep  6 21:20:56 cyrille-W740SU gnome-session[4504]: ** 
(zeitgeist-datahub:4885): WARNING **: zeitgeist-datahub.vala:229: Unable to get 
name "org.gnome.zeitgeist.datahub" on the bus!

Cheers

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

Title:
  Lots of zeitgeist errors

Status in Zeitgeist Datahub:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt"
 was not found, exec: google-chrome-stable, mime_type: application/pkix-cert
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" 
was not found, exec: google-chrome-stable, mime_type: 
application/x-extension-html
  ...
  Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop
  Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 
2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop]
  ...
  Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop

  Any clues how to fix all that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

Triaging this bug lead me to discover bug #1620791. This bug will need
to be fixed before, or at the same time as, bug #1620791 is fixed.

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

Important is high as we'll need a fix soon in order for thumbnailer-
service to run as a snap.

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

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

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

** Changed in: apparmor (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

** Tags added: aa-feature aa-kernel

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1620774] Re: lxc container does not start: cgroupfs failed to detect cgroup metadata

2016-09-06 Thread Stéphane Graber

What init system are you using on this system?

systemd would automatically mount those cgroups which then wouldn't need
the help of cgroup-lite (preferred) or cgroupfs-mount (which you used).

But if you're using upstart on Ubuntu 16.04, then you indeed do need one
of those two packages installed.

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

Title:
  lxc container does not start: cgroupfs failed to detect cgroup
  metadata

Status in lxc package in Ubuntu:
  New

Bug description:
  lxc container failed to start until after I installed cgroupfs-mount

  After a recent upgrade, I received the following error messages when
  start an lxc container:

  kevin@awabi:~$ sudo lxc-start -F -n escale_build
  lxc-start: cgroups/cgfs.c: cgfs_init: 2288 cgroupfs failed to detect cgroup 
metadata
  lxc-start: start.c: lxc_spawn: 1094 failed initializing cgroup support

lxc-start: start.c: __lxc_start: 1354 failed to spawn 'escale_build'
lxc-start: 
tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  
  aptitude install cgroupfs-mount

  Then I could successful start my container.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.4-0ubuntu1~ubuntu16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 11:26:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (477 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (99 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1620780] [NEW] dev-sda2.device job running and times out

2016-09-06 Thread Scott Moser

Public bug reported:

$ lxc launch ubuntu-daily:yakkety y4
$ lxc exec y3 -- systemctl list-jobs
JOB UNITTYPE  STATE  
  5 dev-sda2.device start running

1 jobs listed.

$ lxc exec y3 -- cat /etc/cloud/build.info 
build_name: server
serial: 20160902

$ lxc exec y3 -- systemd-analyze
Startup finished in 1min 30.373s (userspace) = 6d 2h 27min 41.963s


$ lxc exec y3 -- journalctl > yakkety-lxd-journalctl.txt

$ lxc exec y3 -- systemctl status dev-sda2.device
● dev-sda2.device
   Loaded: loaded
   Active: activating (tentative) since Tue 2016-09-06 18:38:31 UTC; 4min 39s 
ago

Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start timed 
out.
Sep 06 18:40:01 y3 systemd[1]: Timed out waiting for device dev-sda2.device.
Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
failed with result 'timeout'.
Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-5
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Sep  6 18:38:48 2016
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug uec-images yakkety

** Attachment added: "journalctl for container"
   
https://bugs.launchpad.net/bugs/1620780/+attachment/4735665/+files/yakkety-lxd-journalctl.txt

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

Title:
  dev-sda2.device job running and times out

Status in systemd package in Ubuntu:
  New

Bug description:
  $ lxc launch ubuntu-daily:yakkety y4
  $ lxc exec y3 -- systemctl list-jobs
  JOB UNITTYPE  STATE  
5 dev-sda2.device start running

  1 jobs listed.

  $ lxc exec y3 -- cat /etc/cloud/build.info 
  build_name: server
  serial: 20160902

  $ lxc exec y3 -- systemd-analyze
  Startup finished in 1min 30.373s (userspace) = 6d 2h 27min 41.963s

  
  $ lxc exec y3 -- journalctl > yakkety-lxd-journalctl.txt

  $ lxc exec y3 -- systemctl status dev-sda2.device
  ● dev-sda2.device
 Loaded: loaded
 Active: activating (tentative) since Tue 2016-09-06 18:38:31 UTC; 4min 39s 
ago

  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
timed out.
  Sep 06 18:40:01 y3 systemd[1]: Timed out waiting for device dev-sda2.device.
  Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start 
failed with result 'timeout'.
  Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep  6 18:38:48 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620774] [NEW] lxc container does not start: cgroupfs failed to detect cgroup metadata

2016-09-06 Thread Kevin Dalley

Public bug reported:

lxc container failed to start until after I installed cgroupfs-mount

After a recent upgrade, I received the following error messages when
start an lxc container:

kevin@awabi:~$ sudo lxc-start -F -n escale_build
lxc-start: cgroups/cgfs.c: cgfs_init: 2288 cgroupfs failed to detect cgroup 
metadata
lxc-start: start.c: lxc_spawn: 1094 failed initializing cgroup support
  
lxc-start: start.c: __lxc_start: 1354 failed to spawn 'escale_build'
  lxc-start: 
tools/lxc_start.c: main: 344 The container failed to start.
lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained 
by setting the --logfile and --logpriority options.


aptitude install cgroupfs-mount

Then I could successful start my container.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc 2.0.4-0ubuntu1~ubuntu16.04.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep  6 11:26:12 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (477 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: lxc
UpgradeStatus: Upgraded to xenial on 2016-05-30 (99 days ago)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: amd64 apparmor apport-bug xenial

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

Title:
  lxc container does not start: cgroupfs failed to detect cgroup
  metadata

Status in lxc package in Ubuntu:
  New

Bug description:
  lxc container failed to start until after I installed cgroupfs-mount

  After a recent upgrade, I received the following error messages when
  start an lxc container:

  kevin@awabi:~$ sudo lxc-start -F -n escale_build
  lxc-start: cgroups/cgfs.c: cgfs_init: 2288 cgroupfs failed to detect cgroup 
metadata
  lxc-start: start.c: lxc_spawn: 1094 failed initializing cgroup support

lxc-start: start.c: __lxc_start: 1354 failed to spawn 'escale_build'
lxc-start: 
tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  
  aptitude install cgroupfs-mount

  Then I could successful start my container.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.4-0ubuntu1~ubuntu16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 11:26:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (477 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (99 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

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

2016-09-06 Thread eddy

** Attachment added: "pulseaudio log"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580882/+attachment/4735656/+files/pulseverbose.log

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

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

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

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

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

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

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

2016-09-06 Thread eddy

Luke, logs as requested. (This is from an Intel NUC if it makes any
difference).


** Attachment added: "pacmd list-sinks output"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580882/+attachment/4735655/+files/sinks.txt

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

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

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

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

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

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

[Touch-packages] [Bug 1620139] Re: factor buffers output when run interactively

2016-09-06 Thread Neil Turton

That seems like a good approach.  Thanks for looking at this.

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

Title:
  factor buffers output when run interactively

Status in coreutils package in Ubuntu:
  New

Bug description:
  When the "factor" utility is run without any arguments, it reads
  numbers from stdin and writes the factors to stdout.  One use case for
  this mode is to run factor in a terminal window and enter numbers
  manually.  This worked well in coreutils 8.23 and earlier.  However,
  in coreutils 8.25, the output of factor is buffered, making this mode
  of operation less useful.

  Notice that in the logs for version 8.25, all of the output occurs
  after end-of-file has been reached on stdin.

  I entered the following input:
factor --version
factor
5
7
9
^D

  bash$ factor --version
  factor (GNU coreutils) 8.23
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Paul Rubin, Torbjörn Granlund, and Niels Möller.
  bash$ factor
  5
  5: 5
  7
  7: 7
  9
  9: 3 3
  bash$ 

  bash$ factor --version
  factor (GNU coreutils) 8.25
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Paul Rubin, Torbjörn Granlund and Niels Möller.
  bash$ factor
  5
  7
  9
  5: 5
  7: 7
  9: 3 3
  bash$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Sep  4 23:32:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-13 (1118 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

After thinking this through some more and discussing with John Johansen,
the current query interface is not sufficient to support querying of
permissions granted by owner file rules. The reason is that, when
dealing with owner file rules, the decision to allow or not depends on
two objects. The first is the file itself and the second is the UID
associated with the process accessing the file. The current query
interface only knows about the file and the UID associated with the
process doing the *query*. The process doing the query is almost never
the same as the process attempting to access the file.


** Changed in: apparmor
   Status: Confirmed => Triaged

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked

** Branch linked: lp:~dandrader/qtmir/dontOccludeFreshSurfaces

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

Title:
  First scope not rendered until unlocked

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  The pre-populating of first scope on startup (before the screen is
  unlocked) doesn't seem to be fully working.

  My early investigation shows that the shell plugin correctly pre-
  populates scope model on startup when the screen is still locked, but
  after unlocking scope view is white for 1-2 seconds and only then the
  page is rendered and all the images are requested, so the perception
  is as if pre-population didn't work. The perceived performance depends
  on whether the 1st scope is a local scope (such as Apps) or a scope
  which needs remote images (and whether the images are already cached
  by the thumbnailer in the latter case).

  This might be caused by https://bugs.launchpad.net/qtmir/+bug/1475678

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

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

[Touch-packages] [Bug 1620759] Re: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

2016-09-06 Thread Apport retracing service

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

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 #1608560, 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/1620759/+attachment/4735638/+files/CoreDump.gz

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  apps from ubuntu apps store will not authenticate or install.
  "Install" button blinks but does nothing.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-system-settings-online-accounts 0.7+16.10.20160718-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Sep  6 11:12:28 2016
  ExecutablePath: /usr/bin/online-accounts-ui
  InstallationDate: Installed on 2016-08-31 (6 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160616)
  ProcCmdline: /usr/bin/online-accounts-ui --socket 
/run/user/1000/online-accounts-ui/ui-1-ubuntuone --profile unconfined
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  Signal: 6
  SourcePackage: ubuntu-system-settings-online-accounts
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1620759/+subscriptions

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

[Touch-packages] [Bug 1471998] Re: [enhancement] Support copy-paste between X and Mir

This bug was fixed in the package qtubuntu -
0.63+16.10.20160831-0ubuntu1

---
qtubuntu (0.63+16.10.20160831-0ubuntu1) yakkety; urgency=medium

  [ Daniel d'Andrada ]
  * Use content-hub for clipboard services (LP: #1471998)

 -- Ken VanDine   Wed, 31 Aug 2016 01:51:46
+

** Changed in: qtubuntu (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 content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1471998

Title:
  [enhancement] Support copy-paste between X and Mir

Status in Canonical System Image:
  Fix Committed
Status in Libertine:
  Fix Committed
Status in Libertine devel series:
  Fix Committed
Status in Libertine trunk series:
  Fix Committed
Status in Mir:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in libertine package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  X applications should be able to paste from Mir applications and vice
  versa.

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

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

[Touch-packages] [Bug 1620759] [NEW] online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

2016-09-06 Thread ventrical

Public bug reported:

apps from ubuntu apps store will not authenticate or install.  "Install"
button blinks but does nothing.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: ubuntu-system-settings-online-accounts 0.7+16.10.20160718-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Sep  6 11:12:28 2016
ExecutablePath: /usr/bin/online-accounts-ui
InstallationDate: Installed on 2016-08-31 (6 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160616)
ProcCmdline: /usr/bin/online-accounts-ui --socket 
/run/user/1000/online-accounts-ui/ui-1-ubuntuone --profile unconfined
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
Signal: 6
SourcePackage: ubuntu-system-settings-online-accounts
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char 
const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
 QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, 
char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace yakkety

** Information type changed from Private to Public

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

Title:
  online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  apps from ubuntu apps store will not authenticate or install.
  "Install" button blinks but does nothing.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-system-settings-online-accounts 0.7+16.10.20160718-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Sep  6 11:12:28 2016
  ExecutablePath: /usr/bin/online-accounts-ui
  InstallationDate: Installed on 2016-08-31 (6 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160616)
  ProcCmdline: /usr/bin/online-accounts-ui --socket 
/run/user/1000/online-accounts-ui/ui-1-ubuntuone --profile unconfined
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  Signal: 6
  SourcePackage: ubuntu-system-settings-online-accounts
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1620759/+subscriptions

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for snaps

Marking the Snappy task as "Wont't Fix" for now. This theoretically
could be fixed in snapd's home interface by dropping the "owner" prefix
but I don't think that's the correct fix for this bug. Either
libapparmor or the kernel need to handle the owner conditional better or
the calling application should do another query for owned files.

** Changed in: snappy
   Status: New => Won't Fix

** Summary changed:

- libapparmor's aa_query_label() always returns allowed = 0 for snaps
+ libapparmor's aa_query_label() always returns allowed = 0 for file rules 
containing the "owner" conditional

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Confirmed
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for snaps

I think that the problem here stems from the fact that the home interface's
rules use the "owner" prefix:

 # Allow read access to toplevel $HOME for the user
 owner @{HOME}/ r,
 
 # Allow read/write access to all non-hidden files that aren't in ~/snap/
 owner @{HOME}/[^s.]** rwk,
 owner @{HOME}/s[^n]** rwk,
 owner @{HOME}/sn[^a]**rwk,
 owner @{HOME}/sna[^p]**   rwk,
 # allow creating a few files not caught above
 owner @{HOME}/{s,sn,sna}{,/} rwk,

The kernel tracks these owner permissions differently than permissions that are
not tied to the owner. You can see that the allow vector is not 0x00 with 
strace:

 $ strace -s1024 ./query_file snap.demo-wget.wget /home/tyhicks/testfile 
 ...
 read(3, "allow 0x0200\ndeny 0x\naudit 0x\nquiet 
0x\n", 67) = 67
 ...

The allow vector is non-zero (0x0200) but it isn't AA_MAY_READ
(0x0011). Instead, I think AA_MAY_READ is being left shifted by the kernel
to indicate that the "owner" prefix was present on the rule. I'll need to
verify that and then discuss among the upstream developers what to do about
this in the libapparmor query interface.


Additionally, the query_file.c test program has a bug. It redefines
AA_MAY_READ, AA_MAY_WRITE, and AA_CLASS_FILE. It gets the definitions of
AA_MAY_READ and AA_MAY_WRITE wrong. Please just use the definitions provided by
.

After making that change, you can remove the "owner" prefix from the rules that
grant access to $HOME in the snap.demo-wget.wget profile, reload the profile,
and then test program will work as expected. This confirms that the "owner" 
prefix causes the unexpected test program results.


** Changed in: apparmor
   Status: New => Confirmed

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

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Confirmed
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1249349] Re: Progress bar hangs at 100% after download is finished, while installing

** Branch linked: lp:~unity-team/unity8/processing-indterminate

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

Title:
  Progress bar hangs at 100% after download is finished, while
  installing

Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  When a user installs a new click packages the following steps ocurr
  (internally)

  1. Download application.
  2. Check the click package checksum
  3. Launch click and install the application.

  Unfortunately the preview just shows the progress up to the end of
  step 1. Steps 2 and 3 might take some time and the user will be left
  with no feed back of what is going on. The u-d-m has bug 1248770 about
  to be fixed and will make fixing this issue easier. Ideally when the
  processing signal is raised the progress bar should be set to the
  indeterminate state
  (http://developer.ubuntu.com/api/devel/ubuntu-13.10/qml/ui-toolkit
  /qml-ubuntu-components0-progressbar.html#indeterminate-prop) and a
  string should show what is going on.

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

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

[Touch-packages] [Bug 1620172] Re: Diagnostic System

2016-09-06 Thread Timo Aaltonen

I don't see a bug

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

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

Title:
  Diagnostic System

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Xdiagnose run report

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep  4 22:18:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:14dd]
  InstallationDate: Installed on 2016-08-31 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=3a27a143-85d3-422b-855a-c012e1b3155a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.513
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  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.:bvrX551MA.513:bd09/09/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  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  4 10:43:50 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8428 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1620265] Re: System Startup

2016-09-06 Thread Timo Aaltonen

and why did you file it against xorg...

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

Title:
  System Startup

Status in Ubuntu:
  New

Bug description:
  Whenever i starts my system, its getting an error that "clean
  */***files, block **/files, and my system startup
  time is 5 to 10 minute. system gets very slow to boot pl help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-37.56-generic 4.4.19
  Uname: Linux 4.4.0-37-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  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: Mon Sep  5 06:10:02 2016
  DistUpgraded: 2016-09-05 05:07:05,798 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
  InstallationDate: Installed on 2015-09-13 (357 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20060
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-37-generic 
root=UUID=f6b2525b-b218-4421-80c3-47b01da8c9ca ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (0 days ago)
  dmi.bios.date: 04/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 29CN23WW(V2.01)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnLENOVO:bvr29CN23WW(V2.01):bd04/07/2010:svnLENOVO:pn20060:pvrIdeapadZ560:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: 20060
  dmi.product.version: Ideapad Z560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  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: Mon Sep  5 05:57:22 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8940 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1620743] [NEW] VPN connetion failed

2016-09-06 Thread Stephan Henningsen

Public bug reported:

When I deliberately disconnect from VPN using Network Indicator > VPN >
Disconnect VPN I see a notification saying "VPN connection failed".  But
nothing has failed.  Correct wording should be used e.g. "Disconnected
from VPN".

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


** Tags: vpn wording

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

Title:
  VPN connetion failed

Status in tracker package in Ubuntu:
  New

Bug description:
  When I deliberately disconnect from VPN using Network Indicator > VPN
  > Disconnect VPN I see a notification saying "VPN connection failed".
  But nothing has failed.  Correct wording should be used e.g.
  "Disconnected from VPN".

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

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

[Touch-packages] [Bug 1620570] Re: Setting scale for menu and title bars > 1 makes window titles disappear.

2016-09-06 Thread Timo Aaltonen

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

Title:
  Setting scale for menu and title bars > 1 makes window titles
  disappear.

Status in unity package in Ubuntu:
  New

Bug description:
  If the value of the menu and title bars scale is set to anything
  higher than 1 on any resolution then all window titles become
  invisible unless they are in the unity top bar. The bug takes
  immediate affect and is also applied to every login.

  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1332947 details
  some information about the text scaling being doubled, I'm unsure if
  it is related.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-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: Tue Sep  6 11:46:22 2016
  DistUpgraded: 2016-07-29 14:06:42,947 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
   virtualbox, 5.0.24, 4.6.0-040600-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Juniper XT [Radeon HD 5770] 
[1787:200b]
  InstallationDate: Installed on 2015-11-04 (306 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: MSI MS-7788
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.6.0-040600-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (38 days ago)
  dmi.bios.date: 09/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  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: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.6:bd09/29/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7788
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep  6 11:39:47 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1511047] Re: packages FTBFS if gir libraries don't contain a GObject

2016-09-06 Thread Iain Lane

any chance you can pick this back up upstream?

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

Title:
  packages FTBFS if gir libraries don't contain a GObject

Status in GObject Introspection:
  In Progress
Status in gobject-introspection package in Ubuntu:
  Fix Released

Bug description:
  Changes in gobject-introspection 1.46.0 to support Microsoft
  toolchains have eliminated the fix for
  https://bugzilla.gnome.org/show_bug.cgi?id=699442 causing FTBFS on a
  number of packages in Ubuntu "xenial."

  Running g-ir-scanner results in an error "ERROR: can't resolve
  libraries to shared libraries: X" where X is the argument
  passed to --library= on the command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1511047/+subscriptions

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

[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

2016-09-06 Thread Matthias Klose

of course, you have to conditionalize the rules file too

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

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  New
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New
Status in hardening-wrapper package in Debian:
  New

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

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

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

[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

2016-09-06 Thread Matthias Klose

postgresql-9.5 uses a b-d: dpkg-dev (>= 1.16.1~) | hardening-wrapper

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

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  New
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New
Status in hardening-wrapper package in Debian:
  New

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

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

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

[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue

2016-09-06 Thread Dimitri John Ledkov

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: libica (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: openssl-ibmca (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  openssl engine error if trying to exploit hw crypto on z due to
  library issue

Status in libica package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New
Status in openssl-ibmca package in Ubuntu:
  New

Bug description:
  openssl-ibmca usually requires libica2 and libica-utils for proper
  functioning and all required tooling (like icainfo, icastats, etc.)

  But after the installation of these packages and the configuration, with is 
like this:
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo vi /etc/ssl/openssl.cnf
  adding the following line as the first active one:
  openssl_conf = openssl_def
  and removing or commenting all other occurrences of that line in the config 
file
  and saving and closing the openssl.cnf file
  this output of the openssl engine command is expected:

  $ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support

  or even more precise these chiphers should be listed in case of "-c":

  $ openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
   [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, 
DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, 
AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, 
AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512]

  But instead openssl is giving this error, due to a missing "libica.so":
  $ openssl engine
  Error configuring OpenSSL
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine 
configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1
  4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module 
initialization error:conf_mod.c:223:module=engines, value=engine_section, 
retcode=-1  
  $

  There is no libica.so that is shipped with any of the above packages 
(verified with dpkg -l) or otherwise available in the filesystem:
  $ sudo find / -name "libica.so" 2>/dev/null
  ubuntu@HWE0001:~$ 

  But there is a different verison of that libica:
  $ sudo find / -name "*libica.so*" 2>/dev/null
  /usr/lib/s390x-linux-gnu/libica.so.2
  /usr/lib/s390x-linux-gnu/libica.so.2.6.1
  $ 

  So there are right now two workarounds:
  1)
  creating a (symbolic) link from libica.so.2 to libica.so, like
  $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 
/usr/lib/s390x-linux-gnu/libica.so 
  that allows openssl to find a library named 'libica.so':
  18:15:00: frank.hei...@canonical.com: ubuntu@HWE0001:~$ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  But this could lead to issues in case of any potential functions or interface 
changes there we introduced with libica.so.2
  2)
  installation of the "libica-dev" package that provides a (development) 
version of libica.so:
  $ dpkg -L libica-dev | grep libica.so
  /usr/lib/s390x-linux-gnu/libica.so
  $

  But the hardware crypto exploitation should work out of the box w/o
  the link or the libica-dev package.

  Either libica.so should be shipped (in addition to libica.so.2) with
  the proper dependency to openssl-ibmca - openssh-ibmca should make use
  of libica2 instead of libica.so.2...

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

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

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

2016-09-06 Thread Rafael David Tinoco

Okay, bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496942

Is avoiding me to verify this. 
The lab I was able to get was a ConnectX-4 HCA lab (I was planning to use 
SR-IOV). 
I'll check if I can have two ConnectX-3 servers to verify this.

Be back soon.

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Wily:
  Won't Fix
Status in isc-dhcp source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves.
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for snaps

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

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

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for snaps

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

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

2016-09-06 Thread Pat McGowan

@andrea I am not experiencing anything close to a 1 sec delay, not really 
noticing any delay at all
In the description you mention I had Mir touchspots visualization enabled, can 
you test without that

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

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

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1573547] Re: Apt's bash completion is incomplete

2016-09-06 Thread Mathew Hodson

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

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

Title:
  Apt's bash completion is incomplete

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  New

Bug description:
  *** Original bug report ***

  "build-dep" and "clean" apt options are missing in /usr/share/bash-
  completion/completions/apt file.  Patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 14:25:54 2016
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

  *** SRU part ***

  [Test case]
  Check that options like build-dep and clean work.

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

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

[Touch-packages] [Bug 1620356] Re: 12.0.2 released with lot of fixes

2016-09-06 Thread Boaz Dodin

Is it possible to backport this version to Xenial?

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

Title:
  12.0.2 released with lot of fixes

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 12.0.2 brings many stability improvements to the Mesa 12.0
  release

  Mesa 12.0.2 takes care of addressing crashes in GLX, EGL, and Wayland
  EGL. There are also numerous memory leak fixes for video decoding
  drivers.

  https://lists.freedesktop.org/archives/mesa-
  dev/2016-September/127937.html

  This is hardly requested to get it pushed to the archives asap.

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

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

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

2016-09-06 Thread Pat McGowan

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

** Tags removed: regression-proposed

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

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

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

@Pat this is a bug I accidentally managed to reproduce, not a constant
behaviour.

I don't have a way to reproduce it yet. We "just" have a to find a way
for the haptics engine dbus call to block, in my case I'm not sure what
made that happen, the dbus call was blocking and then returning NoReply.

I tried killing usensord to reproduce the bug, but that didn't help,
dbus just errored instantly with a blabla was not provided by any
.service files".

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

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

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()

2016-09-06 Thread Lukáš Tinkl

You can already do this by querying Unity 8 GSettings (qml snippet
below):

import GSettings 1.0

GSettings {
   id: settings
   schema.id: "com.canonical.Unity8"
}

...

if (unity8Settings.usageMode === "Windowed") {
   // running in windowed mode
} else { // == "Staged"
   // running in staged mode
}

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

Title:
  Implement Screen::GetShellMode()

Status in Mir:
  New
Status in Oxide:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  This is currently just a stub that returns NonWindowed on mobile
  devices and Windowed everywhere else. It needs to be more intelligent
  than that (eg, Windowed on a tablet device) and needs to be dynamic,
  but I don't think there's a way for us to do that yet.

  Basically, we need to know whether the shell is in windowed or staged
  mode. The display's form factor isn't particularly relevant.

  This is needed to complete bug 1545088 and others.

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

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

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

2016-09-06 Thread Pat McGowan

This change to usensord now checks the app permissions to access the sensor on 
every tap.
http://bazaar.launchpad.net/~phablet-team/usensord/trunk/revision/26
This should use something like an lru cache with the dbus sender id

** Tags added: regression-proposed

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

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

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

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

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

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first

2016-09-06 Thread Numan Demirdöğen

You are wellcome:) I tried to push patch to branch but how-to in the
Ubuntu wiki ( as far as I remember ) was a bit complicated for someone
like me who is just an end user:) The answer in the Askubuntu is much
easier.

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

Title:
  Python warnings: modules imported without specifying a version first

Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  here is the problem:

  $ /usr/share/apport/apport-gtk
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without 
specifying a version first. Use gi.require_version('GdkX11', '3.0') before 
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport-gtk 2.19-0ubuntu1
  Uname: Linux 4.2.2-040202-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Oct  2 16:17:14 2015
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)

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

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

[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()

2016-09-06 Thread David Barth

Can mir and / or unity8 give us that information?

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

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

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

Title:
  Implement Screen::GetShellMode()

Status in Mir:
  New
Status in Oxide:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  This is currently just a stub that returns NonWindowed on mobile
  devices and Windowed everywhere else. It needs to be more intelligent
  than that (eg, Windowed on a tablet device) and needs to be dynamic,
  but I don't think there's a way for us to do that yet.

  Basically, we need to know whether the shell is in windowed or staged
  mode. The display's form factor isn't particularly relevant.

  This is needed to complete bug 1545088 and others.

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

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

[Touch-packages] [Bug 1620553] Re: [Krillin] Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

** Summary changed:

- [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard 
is thus unusable
+ [Krillin] Haptics engine uses sync dbus calls. Was: "Taps are delayed by 
1-2seconds, although gestures are not. Keyboard is thus unusable"

** Summary changed:

- [Krillin] Haptics engine uses sync dbus calls. Was: "Taps are delayed by 
1-2seconds, although gestures are not. Keyboard is thus unusable"
+ Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, 
although gestures are not. Keyboard is thus unusable"

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

Status in platform-api package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

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

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

Status in platform-api package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

2016-09-06 Thread Thomas Voß

** Changed in: platform-api (Ubuntu)
   Importance: Critical => High

** Changed in: platform-api (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

Status in platform-api package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620553] Re: Haptics engine uses sync dbus calls. Was: "Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable"

2016-09-06 Thread Thomas Voß

** Branch linked: lp:~thomas-voss/platform-api/fix-1620553

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

Title:
  Haptics engine uses sync dbus calls. Was: "Taps are delayed by
  1-2seconds, although gestures are not. Keyboard is thus unusable"

Status in platform-api package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

2016-09-06 Thread Dmitry Shachnev

The remaining issue looks like
https://bugreports.qt.io/browse/QTBUG-54793. It can be fixed by a simple
two-line patch (maybe I’ll propose it for review soon).

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

2016-09-06 Thread Chris Coulson

Ditto for firefox (but to precise)

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

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  New
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New
Status in hardening-wrapper package in Debian:
  New

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

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

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

[Touch-packages] [Bug 1620496] Re: Calendar widget gets confused with DST changes

2016-09-06 Thread Lukáš Tinkl

** Summary changed:

- Calendar widget gets confused with October
+ Calendar widget gets confused with DST changes

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

Title:
  Calendar widget gets confused with DST changes

Status in Canonical System Image:
  Confirmed
Status in ubuntu-settings-components package in Ubuntu:
  In Progress

Bug description:
  I can see two October 30ths on my phone, see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qml-module-ubuntu-settings-components 0.9+15.04.20160818.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Sep  6 09:24:34 2016
  InstallationDate: Installed on 2016-09-03 (3 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160903-020304)
  SourcePackage: ubuntu-settings-components
  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/1620496/+subscriptions

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

[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable

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

** Changed in: platform-api (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Krillin] Taps are delayed by 1-2seconds, although gestures are not.
  Keyboard is thus unusable

Status in platform-api package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable

2016-09-06 Thread Christian Dywan

The new plugin indeed seems to be synchronous - in the UI Toolkit we
merely use HapticsEffect.play(), so nothing to do on that side.

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

Title:
  [Krillin] Taps are delayed by 1-2seconds, although gestures are not.
  Keyboard is thus unusable

Status in platform-api package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable

2016-09-06 Thread Christian Dywan

** Changed in: platform-api (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  [Krillin] Taps are delayed by 1-2seconds, although gestures are not.
  Keyboard is thus unusable

Status in platform-api package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

2016-09-06 Thread Stéphane Graber

How far back is this supported? LXC is automatically backported all the
way back to trusty without any change to the packaging being required
right now.

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

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  New
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New
Status in hardening-wrapper package in Debian:
  New

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

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

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

2016-09-06 Thread Michael Thayer

Not sure if you want to include the double menu issue here or if you
prefer to treat the bug as fixed.  As a reminder, the double menu issue
seemed to happen with appmenu-qt because it simply hid the local menus
but did not intercept hide and show requests from the application.

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

2016-09-06 Thread Michael Thayer

I can confirm though that the global menu now works for the second
window.

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable