date:20170206

Public bug reported:

There is too much (inappropriate) shadow rendered for non-rectangular
surfaces.

Test case:
  $ mir_demo_client_egltriangle -b0 -- --desktop_file_hint=unity8

Expected:
  Either a shaped shadow or none at all.

Observed:
  In Unity8 there is a constant shadow over the background.
  In mir_proving_server there is a line of shadow around the invisible border.
  Both are wrong.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: mir
 Importance: Medium
 Status: Triaged

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


** Tags: visual-quality

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

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

Title:
  Incorrect shadows for non-rectangular windows

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

Bug description:
  There is too much (inappropriate) shadow rendered for non-rectangular
  surfaces.

  Test case:
$ mir_demo_client_egltriangle -b0 -- --desktop_file_hint=unity8

  Expected:
Either a shaped shadow or none at all.

  Observed:
In Unity8 there is a constant shadow over the background.
In mir_proving_server there is a line of shadow around the invisible border.
Both are wrong.

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

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

[Touch-packages] [Bug 1662433] Re: Too much shadow for shaped surfaces

Actually I don't think we have a good solution for this yet.

When it was last discussed (Den Haag?) and some times before I suggested
we should just do shadow updates when the input area changes (or some
other client-initiated call). What we shouldn't do is try to generate a
new shaped shadow on every frame, unless there's reason to believe the
shape has changed.

** Summary changed:

- Too much shadow for shaped surfaces
+ Incorrect shadows for non-rectangular windows

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

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

Title:
  Incorrect shadows for non-rectangular windows

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

Bug description:
  There is too much (inappropriate) shadow rendered for non-rectangular
  surfaces.

  Test case:
$ mir_demo_client_egltriangle -b0 -- --desktop_file_hint=unity8

  Expected:
Either a shaped shadow or none at all.

  Observed:
In Unity8 there is a constant shadow over the background.
In mir_proving_server there is a line of shadow around the invisible border.
Both are wrong.

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

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

[Touch-packages] [Bug 1661523] Re: AppArmor profile for Firefox (51.0.1) after took in enforced mode falls back into unconfined

2017-02-06 Thread Sziráki Tamás

Today Firefox has been updated, but the the problem is still there.

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

Title:
  AppArmor profile for Firefox (51.0.1) after took in enforced mode
  falls back into unconfined

Status in apparmor package in Ubuntu:
  New

Bug description:
  The profile for Firefox after took in enforced mode falls back into
  unconfined mode, and download into any selected folders in my account,
  not only the allowed one.

  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  apt-cache policy apparmor
  apparmor:
Telepítve: 2.10.95-0ubuntu2.5
Jelölt:2.10.95-0ubuntu2.5
Verziótáblázat:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Feb  3 09:03:18 2017
  InstallationDate: Installed on 2015-09-19 (502 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=429aedd2-83c1-4b53-b23f-c8099109f278 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1608604] Re: Epson L210 multifunctional printer, scanner is not working.

2017-02-06 Thread Aravind Gopal

Please see the comments from #116 , #126 etc in bug 
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353

I thought that bug is for printers only and not MFD.

I am suffering from this issue for more than 10 MONTHS. 
Even after providing with the screenshots and log files .

Till now there isn't any technical guidance.. to solve a partial problem with 
an essential hardware.
AND PROBLEM PERSISTS.. I cannot scan from LINUX.(No problem with Win10) 

Even though I a like a Canon MFD(not supported by Linux), I opted Epson MFD 
because Linux supported it.
I am a fan of Linux. Now Its like Ubuntu is forcing me to Switch OS. 

PLease Help

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

Title:
  Epson L210 multifunctional printer, scanner is not working.

Status in lsb package in Ubuntu:
  Invalid

Bug description:
  Installed lsb package and installed epson's drivers. Not working.
  Printer setting identifies printer correctly(EPSON-L210-Series). but
  in Simple scan, an error"unable to connect to scanner" arise. when
  tried to change scanner there the scanner name is given as
  "Epson(unknown model)". It seems that there is something wrong with
  hardware detection/identification and/or communication gap between
  printer and scanner modules.

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

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

[Touch-packages] [Bug 1638611] Re: Rotating display to 90 and 270 degrees crashes shell

Oh! Good news: Gerry's fix hasn't landed yet so this bug may get fixed
by that very soon:

lp:~gerboland/qtmir/fix-glcontext-loss-on-reconfigure

(bug 1521403)

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

** Branch linked: lp:~gerboland/qtmir/fix-glcontext-loss-on-reconfigure

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Gerry Boland (gerboland)

** Changed in: canonical-devices-system-image
 Assignee: Gerry Boland (gerboland) => Michał Sawicz (saviq)

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

Title:
  Rotating display to 90 and 270 degrees crashes shell

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in qtmir package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Reproduce:
  rotate display to mir_orientation_left

  What happens:
  (The following is a log from the client, in this case System Settings)
  [2016-11-02 16:51:04.111664]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-S1BioZ/mir-0.24.1+16.04.20160928/src/client/no_tls_future-inl.h(73): 
Throw in function T mir::client::PromiseState::get_value() [with T = 
std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: broken_promise

  2016-11-02 16:51:04,111 - WARNING - QEGLPlatformContext:
  eglSwapBuffers failed: 3000

  What should happen:
  like with mir_orientation_inverted it should just work.

  USC log: http://pastebin.ubuntu.com/23416688/
  U8 log: http://pastebin.ubuntu.com/23451419/

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

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

[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

2017-02-06 Thread Cyrus Lien

** Changed in: oem-priority
   Status: New => Triaged

** Changed in: oem-priority
 Assignee: (unassigned) => Alex Tu (alextu)

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION 
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged-- 

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-06 Thread Yuan-Chen Cheng

** Tags added: somerville

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-06 Thread Cyrus Lien

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

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

[Touch-packages] [Bug 1630156] Re: No password needed to Log in after cancel the password and then reset again

2017-02-06 Thread Yuan-Chen Cheng

** Tags added: n+1

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  OS: 14.04 trusty

  Tested with 16.10
  lightdm version is 1.19.5
  issue still exist

  
  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password.
  3. Reboot and log to desktop without password.
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Reboot but still no password needed at Log in interface.

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

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-06 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

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

[Touch-packages] [Bug 1638611] Re: Rotating display to 90 and 270 degrees crashes shell

Thanks Bill. I can't see any Mir code in that stack trace. And Gerry is
indeed the best person to look at it since he recently fixed another
(related?) GL context crash that looked similar.

It's worth noting that Unity8 has historically (on phablet) done its own
screen rotation independently of Mir's. I'm actually not sure if Unity8
supports Mir's screen rotation settings (via display config).

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

Title:
  Rotating display to 90 and 270 degrees crashes shell

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  rotate display to mir_orientation_left

  What happens:
  (The following is a log from the client, in this case System Settings)
  [2016-11-02 16:51:04.111664]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-S1BioZ/mir-0.24.1+16.04.20160928/src/client/no_tls_future-inl.h(73): 
Throw in function T mir::client::PromiseState::get_value() [with T = 
std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: broken_promise

  2016-11-02 16:51:04,111 - WARNING - QEGLPlatformContext:
  eglSwapBuffers failed: 3000

  What should happen:
  like with mir_orientation_inverted it should just work.

  USC log: http://pastebin.ubuntu.com/23416688/
  U8 log: http://pastebin.ubuntu.com/23451419/

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

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

[Touch-packages] [Bug 1605478] Re: supertux2 segfaults on native Mir with SDL_VIDEODRIVER=mir trying to call glXQueryVersion

Thanks. Ubuntu appears to just copy and use Debian glew releases. So
yes, if you can get Debian to release 2.0.1 that would help us.

There's no huge demand for a fix but it's periodically confusing if we
try supertux as a Mir test once or twice a year and each time (I) forget
that it's this bug preventing it from working. Or preventing any glew
app from working on Mir, I guess.

** Also affects: glew via
   https://github.com/nigels-com/glew/issues/103
   Importance: Unknown
   Status: Unknown

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

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

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

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

Title:
  supertux2 segfaults on native Mir with SDL_VIDEODRIVER=mir trying to
  call glXQueryVersion

Status in Glew:
  Unknown
Status in glew package in Ubuntu:
  Triaged
Status in libsdl2 package in Ubuntu:
  Invalid
Status in supertux package in Ubuntu:
  Invalid

Bug description:
  supertux2 crashes on native Mir, trying to call GLX functions...

  Thread 1 "supertux2" received signal SIGSEGV, Segmentation fault.
  0x7519a95d in XQueryExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  (gdb) bt
  #0  0x7519a95d in XQueryExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #1  0x7518e4c2 in XInitExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #2  0x76f8269c in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  #3  0x76f7e041 in glXQueryVersion ()
 from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  #4  0x76d2eb34 in glxewInit ()
 from /usr/lib/x86_64-linux-gnu/libGLEW.so.1.13
  #5  0x00560eeb in GLRenderer::GLRenderer() ()
  #6  0x0055e153 in GLVideoSystem::GLVideoSystem() ()
  #7  0x004f4b85 in VideoSystem::create(VideoSystem::Enum) ()
  #8  0x004ad662 in Main::launch_game() ()
  #9  0x004af0ad in Main::run(int, char**) ()
  #10 0x004a9f13 in main ()

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

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

[Touch-packages] [Bug 1624738] Re: Firefox search and location boxes have black borders when unselected

2017-02-06 Thread Martin Wimpress

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Firefox search and location boxes have black borders when unselected

Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  [Impact]

  As seen in the attached screen shot the borders around Firefox
  location and search entry boxes are black when unselected, but they
  should be grey.

  The black borders are inconsistent with the rest of the Ubuntu theming
  and it looks jarring.

  The issue is resolved by styling the 'frame' selector, which Firefox
  uses to style the Search and Location entry boxes. Some overrides are
  then applied to prevent frames incorrectly rendering borders in other
  applications.

  [Test Case]

  To observe the issue simply open Firefox and look at the Search or
  Location entry boxes while they are unselected, the borders will be
  black.

  After installing the patched theme doing to same will result in the
  borders being rendered using an appropriate shade of grey.

  [Regression Potential]

  It is possible that some GTK3+ applications may now render frames with
  a border where they previously did not. That said, the default
  applications in Ubuntu have been checked for this regression and the
  appropriate overrides have been added.

  The default installed applications in Ubuntu have been tested to
  ensure they do not regress in the manner described above.

  [Other Info]
   
  Should Firefox style the Search and Location entry boxes with a discrete 
selector in the future then the styling added to work around the black border 
could be removed/updated.

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

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

[Touch-packages] [Bug 1662375] [NEW] package account-plugin-owncloud (not installed) failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in

2017-02-06 Thread harveygfl

Public bug reported:

package account-plugin-owncloud (not installed) failed to
install/upgrade: trying to overwrite
'/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in
package owncloud-client 2.2.2+dfsg-1ubuntu0.2

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: account-plugin-owncloud (not installed)
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Mon Feb  6 19:08:37 2017
DpkgTerminalLog:
 Preparing to unpack 
.../0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb ...
 Unpacking account-plugin-owncloud (0.13+16.10.20160929.1-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-zVoRo6/0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which 
is also in package owncloud-client 2.2.2+dfsg-1ubuntu0.2
DuplicateSignature:
 package:account-plugin-owncloud:(not installed)
 Unpacking account-plugin-owncloud (0.13+16.10.20160929.1-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-zVoRo6/0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which 
is also in package owncloud-client 2.2.2+dfsg-1ubuntu0.2
ErrorMessage: trying to overwrite 
'/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in package 
owncloud-client 2.2.2+dfsg-1ubuntu0.2
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: account-plugins
Title: package account-plugin-owncloud (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in package 
owncloud-client 2.2.2+dfsg-1ubuntu0.2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict yakkety

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

Title:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in
  package owncloud-client 2.2.2+dfsg-1ubuntu0.2

Status in account-plugins package in Ubuntu:
  New

Bug description:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in
  package owncloud-client 2.2.2+dfsg-1ubuntu0.2

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-owncloud (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 19:08:37 2017
  DpkgTerminalLog:
   Preparing to unpack 
.../0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb ...
   Unpacking account-plugin-owncloud (0.13+16.10.20160929.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-zVoRo6/0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', 
which is also in package owncloud-client 2.2.2+dfsg-1ubuntu0.2
  DuplicateSignature:
   package:account-plugin-owncloud:(not installed)
   Unpacking account-plugin-owncloud (0.13+16.10.20160929.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-zVoRo6/0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', 
which is also in package owncloud-client 2.2.2+dfsg-1ubuntu0.2
  ErrorMessage: trying to overwrite 
'/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in package 
owncloud-client 2.2.2+dfsg-1ubuntu0.2
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: account-plugins
  Title: package account-plugin-owncloud (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in package 
owncloud-client 2.2.2+dfsg-1ubuntu0.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1662375] Re: package account-plugin-owncloud (not installed) failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in p

2017-02-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in
  package owncloud-client 2.2.2+dfsg-1ubuntu0.2

Status in account-plugins package in Ubuntu:
  New

Bug description:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in
  package owncloud-client 2.2.2+dfsg-1ubuntu0.2

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-owncloud (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 19:08:37 2017
  DpkgTerminalLog:
   Preparing to unpack 
.../0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb ...
   Unpacking account-plugin-owncloud (0.13+16.10.20160929.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-zVoRo6/0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', 
which is also in package owncloud-client 2.2.2+dfsg-1ubuntu0.2
  DuplicateSignature:
   package:account-plugin-owncloud:(not installed)
   Unpacking account-plugin-owncloud (0.13+16.10.20160929.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-zVoRo6/0-account-plugin-owncloud_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/icons/hicolor/32x32/apps/owncloud.png', 
which is also in package owncloud-client 2.2.2+dfsg-1ubuntu0.2
  ErrorMessage: trying to overwrite 
'/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in package 
owncloud-client 2.2.2+dfsg-1ubuntu0.2
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: account-plugins
  Title: package account-plugin-owncloud (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/icons/hicolor/32x32/apps/owncloud.png', which is also in package 
owncloud-client 2.2.2+dfsg-1ubuntu0.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1411867] Re: [USB-Audio - Plantronics .Audio 478 USB, recording] Microphone Stops Working After Pressing Hardware Mute

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [USB-Audio - Plantronics .Audio 478 USB, recording] Microphone Stops
  Working After Pressing Hardware Mute

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu, when the hardware "mute" button is pressed, the headset
  microphone becomes muted, but the mute indicator light fails to light
  up. On pressing the mute button again to hardware unmute the mic, the
  mic is never unmuted. I have to physically unplug and replug the
  microphone to unmute the mic.

  On OS X, when the hardware mute button is pressed, the mic is muted
  and a red mute indicator light lights up. When I press the button
  again, the light goes away and the mic is unmuted.

  
  I believe the issue is related to the USB HID (for volume up, volume down, 
and call accept) not being properly interfaced with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jchan  2924 F pulseaudio
   /dev/snd/pcmC1D0c:   jchan  2924 F...m pulseaudio
   /dev/snd/pcmC1D0p:   jchan  2924 F...m pulseaudio
   /dev/snd/controlC0:  jchan  2924 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 16 17:32:58 2015
  InstallationDate: Installed on 2014-04-22 (269 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:USB failed
  Symptom_Card: Plantronics .Audio 478 USB - Plantronics .Audio 478 USB
  Symptom_Type: None of the above
  Title: [USB-Audio - Plantronics .Audio 478 USB, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCH7710H.86A.0106.2012.1227.1251
  dmi.board.name: DH77DF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG40293-300
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCH7710H.86A.0106.2012.1227.1251:bd12/27/2012:svn:pn:pvr:rvnIntelCorporation:rnDH77DF:rvrAAG40293-300:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1662368] Re: webbrowser-app crashed in qmlscene call

2017-02-06 Thread stinger

i dont think so.

this is on zesty with new QT 5.7.1

** This bug is no longer a duplicate of private bug 1560994

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

Title:
  webbrowser-app crashed in qmlscene call

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  looks like a QT 5.7.1 bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webbrowser-app 0.23+17.04.20170110-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Feb  7 00:46:36 2017
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-11-06 (92 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f6508fa95d8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:83
   __GI_exit (status=) at exit.c:105
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: Upgraded to zesty on 2016-11-19 (79 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1662368] Re: webbrowser-app crashed in qmlscene call

2017-02-06 Thread Apport retracing service

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

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 #1560994, 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/1662368/+attachment/4814409/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  webbrowser-app crashed in qmlscene call

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  looks like a QT 5.7.1 bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webbrowser-app 0.23+17.04.20170110-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Feb  7 00:46:36 2017
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-11-06 (92 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f6508fa95d8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:83
   __GI_exit (status=) at exit.c:105
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: Upgraded to zesty on 2016-11-19 (79 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1661406] Re: apparmor failing to be purged on trusty

2017-02-06 Thread Tyler Hicks

** Changed in: apparmor (Ubuntu Trusty)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: apparmor (Ubuntu Trusty)
   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/1661406

Title:
  apparmor failing to be purged on trusty

Status in apparmor package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  Triaged

Bug description:
  Version: 2.10.95-0ubuntu2.5~14.04.1

  When executing apt -y purge apparmor.

  The purge run but has errors as files do not exist and the rmdir fails
  to execute.

  rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or
  directory

  Steps to reproduce:
  apt-get update
  apt-get -y install apparmor
  apt -y purge apparmor

  I will put workarounds in place for now in puppet but this is making
  puppet not like it..

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

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

[Touch-packages] [Bug 1662357] Re: Can't use lsb_release on Ubuntu Core 16

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

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

Title:
  Can't use lsb_release on Ubuntu Core 16

Status in Snappy:
  New
Status in Snappy Ubuntu Core:
  New
Status in lsb package in Ubuntu:
  New

Bug description:
  brian-murray@localhost:~$ snap list   

  
  Name Version Rev  Developer  Notes
  core 16.04.1 888  canonical  -

  
  brian-murray@localhost:~$ lsb_release
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '16.04 LTS'

  brian-murray@localhost:~$ lsb_release -a
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '6.06 LTS'

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

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

[Touch-packages] [Bug 1608604] Re: Epson L210 multifunctional printer, scanner is not working.

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We appreciate the difficulties you
are facing, but it would make more sense to raise problems you are
having in the support tracker at https://answers.launchpad.net/ubuntu if
you are uncertain if they are bugs. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs#When%20not%20to%20file%20a%20bug.

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/lsb/+question/452000

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

Title:
  Epson L210 multifunctional printer, scanner is not working.

Status in lsb package in Ubuntu:
  Invalid

Bug description:
  Installed lsb package and installed epson's drivers. Not working.
  Printer setting identifies printer correctly(EPSON-L210-Series). but
  in Simple scan, an error"unable to connect to scanner" arise. when
  tried to change scanner there the scanner name is given as
  "Epson(unknown model)". It seems that there is something wrong with
  hardware detection/identification and/or communication gap between
  printer and scanner modules.

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

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

[Touch-packages] [Bug 1662357] [NEW] Can't use lsb_release on Ubuntu Core 16

Public bug reported:

brian-murray@localhost:~$ snap list 


Name Version Rev  Developer  Notes
core 16.04.1 888  canonical  -


brian-murray@localhost:~$ lsb_release
Traceback (most recent call last):
  File "/usr/bin/lsb_release", line 95, in 
main()
  File "/usr/bin/lsb_release", line 59, in main
distinfo = lsb_release.get_distro_information()
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
distinfo = guess_debian_release()
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
get_distro_info(distinfo['ID'])
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
ValueError: could not convert string to float: '16.04 LTS'

brian-murray@localhost:~$ lsb_release -a
Traceback (most recent call last):
  File "/usr/bin/lsb_release", line 95, in 
main()
  File "/usr/bin/lsb_release", line 59, in main
distinfo = lsb_release.get_distro_information()
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
distinfo = guess_debian_release()
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
get_distro_info(distinfo['ID'])
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
ValueError: could not convert string to float: '6.06 LTS'

** Affects: ubuntu-core
 Importance: Undecided
 Status: New

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

** Also affects: ubuntu-core
   Importance: Undecided
   Status: New

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

Title:
  Can't use lsb_release on Ubuntu Core 16

Status in Snappy Ubuntu Core:
  New
Status in lsb package in Ubuntu:
  New

Bug description:
  brian-murray@localhost:~$ snap list   

  
  Name Version Rev  Developer  Notes
  core 16.04.1 888  canonical  -

  
  brian-murray@localhost:~$ lsb_release
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '16.04 LTS'

  brian-murray@localhost:~$ lsb_release -a
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '6.06 LTS'

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

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

[Touch-packages] [Bug 1661809] Re: package ufw (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2017-02-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package ufw (not installed) failed to install/upgrade: subprocess
  installed post-removal script returned error exit status 1

Status in ufw package in Ubuntu:
  New

Bug description:
  I purged ufw from the system. systemctl list-unit-files showed UFW
  enabled.

  
  The reason I noticed was firewalld is not starting on boot, firewalld.service 
is running and it loads inactive.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   ufw: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Feb  4 00:04:25 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-25 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ufw
  Title: package ufw (not installed) failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661809] Re: package ufw (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2017-02-06 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package ufw (not installed) failed to install/upgrade: subprocess
  installed post-removal script returned error exit status 1

Status in ufw package in Ubuntu:
  New

Bug description:
  I purged ufw from the system. systemctl list-unit-files showed UFW
  enabled.

  
  The reason I noticed was firewalld is not starting on boot, firewalld.service 
is running and it loads inactive.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   ufw: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Feb  4 00:04:25 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-25 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ufw
  Title: package ufw (not installed) failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1662355] [NEW] Signon shows up as Safari

2017-02-06 Thread Shaun Crampton

Public bug reported:

Signon UI popped up and asked me to log into Google.  After logging in,
Google immediately sent me a message asking whether I logged in as
Safari, with my public IP (so I have no reason to think it was anyone
but me).  Is signon-ui spoofing as safari?

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: signon-ui 0.17+16.04.20160406-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb  6 22:41:44 2017
InstallationDate: Installed on 2012-09-26 (1594 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
PackageArchitecture: all
SourcePackage: signon-ui
UpgradeStatus: Upgraded to yakkety on 2017-01-23 (13 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Signon shows up as Safari

Status in signon-ui package in Ubuntu:
  New

Bug description:
  Signon UI popped up and asked me to log into Google.  After logging
  in, Google immediately sent me a message asking whether I logged in as
  Safari, with my public IP (so I have no reason to think it was anyone
  but me).  Is signon-ui spoofing as safari?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: signon-ui 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  6 22:41:44 2017
  InstallationDate: Installed on 2012-09-26 (1594 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  PackageArchitecture: all
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to yakkety on 2017-01-23 (13 days ago)

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

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

[Touch-packages] [Bug 1593877] Re: Reload shortcut is redundant and ambiguous

** Branch linked: lp:webbrowser-app/staging

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

Title:
  Reload shortcut is redundant and ambiguous

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  While researching why

  https://code.launchpad.net/~santoshbit2007/webbrowser-
  app/webcontainer_shortcut_fix/+merge/297355

  wasn't working for me I found that there is an inconsistency and
  confusion apparently in the Reload shortcuts in this branch and in the
  current webbrowser.

  For a given shortcut,

  StandardKey.Refresh

  as seen here:

  http://bazaar.launchpad.net/~phablet-team/webbrowser-
  app/trunk/view/head:/src/app/webbrowser/Browser.qml#L2086

  actually is platform dependant, and could refer to either F5, F5 AND
  Ctrl+r or Ctrl+r,

  When running the webbrowser-app tests or the tests for  the webapp-
  container branch above besides failing for me, they also report
  ambiguous events (ambiguous in the sense of
  http://doc.qt.io/qt-5/qshortcutevent.html#QShortcutEvent) which means
  that there is an overloaded shortcut. And there is since
  StandardKey.Refresh is redundant with F5 on my setup (Ubuntu 16.04
  with canadian keyboard),

  Check for the Refresh keyboard shortcut there

  http://doc.qt.io/qt-5/qkeysequence.html#standard-shortcuts

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

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

[Touch-packages] [Bug 1638611] Re: Rotating display to 90 and 270 degrees crashes shell

2017-02-06 Thread Bill Filler

@vanvugt
please see above trace and confirm problem not in mir.. thanks

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

Title:
  Rotating display to 90 and 270 degrees crashes shell

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  rotate display to mir_orientation_left

  What happens:
  (The following is a log from the client, in this case System Settings)
  [2016-11-02 16:51:04.111664]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-S1BioZ/mir-0.24.1+16.04.20160928/src/client/no_tls_future-inl.h(73): 
Throw in function T mir::client::PromiseState::get_value() [with T = 
std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: broken_promise

  2016-11-02 16:51:04,111 - WARNING - QEGLPlatformContext:
  eglSwapBuffers failed: 3000

  What should happen:
  like with mir_orientation_inverted it should just work.

  USC log: http://pastebin.ubuntu.com/23416688/
  U8 log: http://pastebin.ubuntu.com/23451419/

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

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

[Touch-packages] [Bug 1638611] Re: Rotating some display to 90 and 270 degrees makes mir throw

2017-02-06 Thread Bill Filler

Tested this with latest mir 0.26 and silo 2140
https://bileto.ubuntu.com/#/ticket/2140 for ubuntu-system-settings. when
I try rotating, I get the following crash from unity8

Thread 27 "QSGRenderThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fec84b6e700 (LWP 8251)]
0x7fec94716d07 in Screen::makeCurrent() ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
(gdb) bt
#0  0x7fec94716d07 in Screen::makeCurrent() ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
#1  0x7fec9471d516 in MirOpenGLContext::makeCurrent(QPlatformSurface*) ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
#2  0x7fec9d51b81c in QOpenGLContext::makeCurrent(QSurface*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#3  0x7fec9e6ba69b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7fec9cb447e8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fec9bc176ba in start_thread (arg=0x7fec84b6e700) at 
pthread_create.c:333
#6  0x7fec9c23c82d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb) 


** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Invalid

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

** Summary changed:

- Rotating some display to 90 and 270 degrees makes mir throw
+ Rotating display to 90 and 270 degrees crashes shell

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

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

** Changed in: qtmir
 Assignee: (unassigned) => Gerry Boland (gerboland)

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

** No longer affects: qtmir

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Rotating display to 90 and 270 degrees crashes shell

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  rotate display to mir_orientation_left

  What happens:
  (The following is a log from the client, in this case System Settings)
  [2016-11-02 16:51:04.111664]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-S1BioZ/mir-0.24.1+16.04.20160928/src/client/no_tls_future-inl.h(73): 
Throw in function T mir::client::PromiseState::get_value() [with T = 
std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: broken_promise

  2016-11-02 16:51:04,111 - WARNING - QEGLPlatformContext:
  eglSwapBuffers failed: 3000

  What should happen:
  like with mir_orientation_inverted it should just work.

  USC log: http://pastebin.ubuntu.com/23416688/
  U8 log: http://pastebin.ubuntu.com/23451419/

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

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

[Touch-packages] [Bug 1593877] Re: Reload shortcut is redundant and ambiguous

I couldn’t observe the issue when running webbrowser-app on unity7, but
I got hit by it on unity8 (reported by Bill as bug #1661690). I’ve
verified that the proposed change fixes the issue indeed. Thanks!

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Triaged

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

** Changed in: webbrowser-app (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Reload shortcut is redundant and ambiguous

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  While researching why

  https://code.launchpad.net/~santoshbit2007/webbrowser-
  app/webcontainer_shortcut_fix/+merge/297355

  wasn't working for me I found that there is an inconsistency and
  confusion apparently in the Reload shortcuts in this branch and in the
  current webbrowser.

  For a given shortcut,

  StandardKey.Refresh

  as seen here:

  http://bazaar.launchpad.net/~phablet-team/webbrowser-
  app/trunk/view/head:/src/app/webbrowser/Browser.qml#L2086

  actually is platform dependant, and could refer to either F5, F5 AND
  Ctrl+r or Ctrl+r,

  When running the webbrowser-app tests or the tests for  the webapp-
  container branch above besides failing for me, they also report
  ambiguous events (ambiguous in the sense of
  http://doc.qt.io/qt-5/qshortcutevent.html#QShortcutEvent) which means
  that there is an overloaded shortcut. And there is since
  StandardKey.Refresh is redundant with F5 on my setup (Ubuntu 16.04
  with canadian keyboard),

  Check for the Refresh keyboard shortcut there

  http://doc.qt.io/qt-5/qkeysequence.html#standard-shortcuts

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

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

[Touch-packages] [Bug 1661690] Re: Reload page shortcut not working in u8

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

** This bug has been marked a duplicate of bug 1593877
   Reload shortcut is redundant and ambiguous

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

Title:
  Reload page shortcut not working in u8

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  the keyboard shortcuts for reloading a page are not working in unity8 (ctrl-r 
and f5)
  they work fine in u7
  most other shortcuts I've tried in u8 work

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

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

[Touch-packages] [Bug 1645372] Re: support display scaling slider in unity8

2017-02-06 Thread Bill Filler

Just re-tested this with latest Mir 0.26 and silo 2140
https://bileto.ubuntu.com/#/ticket/2140 with changes from system
settings to add the scaling slider (uses mir api)

All of the app windows correctly scale. But the shell does not scale at
all. Obviously we'd want windows and the shell to scale together.

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

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

Title:
  support display scaling slider in unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

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

-- 
Mailing list: https://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 1662147] Re: Cannot stop pulseaudio

2017-02-06 Thread Luke Yelavich

Do you have pulseaudio-module-jack installed? I believe that includes a
module that will talk to jack and have pulse move out of the way, and
reroute itself through jack.

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

Title:
  Cannot stop pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I need to kill pulseaudio as I'm using Jackd instead. I don't want to
  delete it as I may need it back again.

  So far the only workaround I found was to delete /usr/bin/pulseaudio
  (or move it out of the way).

  
  norru@GBWWSRUNUBWS02:~$ pulseaudio -k
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29938  8557  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29940 29938  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29941 29940  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30111 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29938  8557  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29940 29938  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29941 29940  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30230 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29938  8557  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29940 29938  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29941 29940  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30250 28914  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30252 28942  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30297 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29941 1  1 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30469 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29941 1  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30486 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ pulseaudio -k
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru30489 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru30493 1  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30506 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ubuntu-bug pulseaudio

  norru@GBWWSRUNUBWS02:~$ sudo service pulseaudio stop
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru30493 1  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog

  norru@GBWWSRUNUBWS02:~$ kill 30493
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru32318 1  1 11:32 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog

  
  norru@GBWWSRUNUBWS02:~$ kill -9 32318

  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru32361  8557  0 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru32363 32361  0 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru32364 32363  1 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog

  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru32364 1  1 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru32381 29396  0 11:34 pts/000:00:00 grep --color=auto pulse

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  norru 30493 F pulseaudio
   /dev/snd/controlC0:  norru 30493 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Feb  6 11:28:49 2017
  InstallationDate: Installed on 2015-06-10 (606 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (97 days ago)
  dmi.bios.date: 10/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4502
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK

[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2017-02-06 Thread Chris Coulson

** Changed in: oxide
Milestone: branch-1.21 => branch-1.22

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

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

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

[Touch-packages] [Bug 1662327] Re: apt-daily.service was slowing down one system startup

2017-02-06 Thread Julian Andres Klode

The service is started by a (persistent) timer. The timer runs at 0600
and 1800 (+/-13). Apparently that timer elapsed before your boot.

That said, the reason it starts before a login manager is that it does
not depend on a login manager - why would it, it does not need that. And
systemd starts everything as soon as possible, and as parallel as
possible.

As you can see in the plot,  there is less than a second difference
between starting apt-daily and the login manager. But it seems
lightdm.service was waiting for gpu-manager.service, so there was no
delay at all.

Of course, you seem to be running an HDD. That's a niche use case not
well supported by systemd and performance there will of course be worse
than on an SSD, due to the parallel processes causing a lot of seeking.

But that's a general problem with HDDs, and not apt's problem, so I'm
closing this.

Also: You really want to switch to an SSD.

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

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

Title:
  apt-daily.service was slowing down one system startup

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I don't understand why this service started before the light-dm invite
  was displayed to the end user.

  Up to the light-dm invite, the system needed roughly twice the time it
  usualy needs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.19
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb  6 21:28:54 2017
  InstallationDate: Installed on 2017-02-01 (4 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apt: 2017-02-03T22:39:52.394852

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

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

[Touch-packages] [Bug 1552653] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I tried to open an xml file to see if it would display the xml in
  formatted way like firefox or IE.

  Then, I got this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160223-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Thu Mar  3 04:39:54 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-02-10 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  ProcCmdline: webbrowser-app 
/home/username/Desktop/00A474E0-1BE7-4A37-B478-F26C69200FB0.xml
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1643334] Re: root-ca-cert.crt could not be used

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

** This bug has been marked a duplicate of bug 1313370
   Support for installing Digital Certificates

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

Title:
  root-ca-cert.crt could not be used

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu Touch 15.04 (OTA-13) armhf Build 20160913-023544
  2) Ubuntu Touch web Browser
  3) Accessing HTTPS websites by importing root-ca-certificate once
  4) Does not work

  Hi,

  while accessing a HTTPS website, the browser tries to download an
  root-certificate.

  - Download fails
  - If I copy the root-cert to /usr/local/share/ca-certificates/, the browser 
does not care

  Please provide me with a hint to import and use https-certs.

  Many thanks!

  PS: This is a security issue, also.

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

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

[Touch-packages] [Bug 1500117] Re: webbrowser-app crashed with SIGABRT in QSGThreadedRenderLoop::handleExposure()

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

** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in
  QSGThreadedRenderLoop::handleExposure()

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Upon opening Ubuntu Browser after initial install of Operating System

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: webbrowser-app 0.23+15.10.20150922-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 26 20:24:23 2015
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2015-09-26 (0 days ago)
  InstallationMedia: It
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app 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/webbrowser-app/+bug/1500117/+subscriptions

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

[Touch-packages] [Bug 1562300] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  no Idea :-(

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 26 13:35:51 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-19 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app 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/webbrowser-app/+bug/1562300/+subscriptions

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

[Touch-packages] [Bug 1569367] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Immediately after dist. upgrade from 15.10 to 16.04 and logging in i opened 
  Browser and it crashed with provided error message.
  The last thing browsed on it in 15.10 was the generic lan ip addy 192.168.1.4
  which is a connection to an ip cam web interface.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160405-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Apr 12 06:46:14 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-04-10 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to xenial on 2016-04-12 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1540057] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  crash browser

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160122-0ubuntu1
  Uname: Linux 4.4.0-040400-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sun Jan 31 14:02:22 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-01-17 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to xenial on 2016-01-19 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1559531] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal() - during starting

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal() -
  during starting

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  During starting

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160311-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Mar 19 19:53:01 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-03 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160302)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1545467] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160129.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
  Uname: Linux 4.4.0-5-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 14 18:47:53 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-01-22 (23 days ago)
  InstallationMedia:
   
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app 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/webbrowser-app/+bug/1545467/+subscriptions

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

[Touch-packages] [Bug 1550548] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser never fully launched before crashing.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160223-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 13:45:23 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-02-10 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1565442] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  miked@free:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  miked@free:~$ apt-cache policy webbrowser-app
  webbrowser-app:
Installed: 0.23+16.04.20160322-0ubuntu1
Candidate: 0.23+16.04.20160322-0ubuntu1
Version table:
   *** 0.23+16.04.20160322-0ubuntu1 500
  500 http://mirrors.us.kernel.org/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  miked@free:~$ 

  Webbrowser Crashes on start-up and wants to file report.

  I expected the webbrowser to open for me to use.

  Instead it Crashes and wants to send report.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sun Apr  3 03:54:19 2016
  ExecutablePath: /usr/bin/webbrowser-app
  ExecutableTimestamp: 1458630336
  InstallationDate: Installed on 2016-04-03 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: webbrowser-app
  ProcCwd: /home/miked
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app 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/webbrowser-app/+bug/1565442/+subscriptions

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

[Touch-packages] [Bug 1567729] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  trying to view manpage of ssh from krunner alt-f2 run man:/ssh , and
  it tries to start browser with manpage, but failed with browser window
  splashed once.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160405-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  8 10:57:06 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-31 (7 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160329)
  ProcCmdline: /usr/bin/webbrowser-app 
/home/username/.cache/kioexec/krun/12735_0_ssh
  ProcEnviron:
   LANGUAGE=en_GB:zh_CN:en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app 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/webbrowser-app/+bug/1567729/+subscriptions

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

[Touch-packages] [Bug 1591946] Re: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

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

** This bug is no longer a duplicate of private bug 1538601
** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  when I try to open ubuntu browser it crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: webbrowser-app 0.23+16.10.20160603.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Jun 13 09:16:38 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-06-10 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
   QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to yakkety on 2016-06-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1638071] Re: /usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderL

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New => 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/1638071

Title:
  /usr/bin/webbrowser-
  
app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
webbrowser-app.  This problem was most recently seen with package version 
0.23+16.10.20160928-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/5c26877e10d0ef3f581f16848dcd8a0d054bf44c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1638071] Re: /usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderL

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/bin/webbrowser-
  
app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
webbrowser-app.  This problem was most recently seen with package version 
0.23+16.10.20160928-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/5c26877e10d0ef3f581f16848dcd8a0d054bf44c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1662327] Re: apt-daily.service was slowing down one system startup

2017-02-06 Thread Jérôme

** Attachment added: "systemd-analyse plot"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1662327/+attachment/4814331/+files/systemd-analyse_plot.svg

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

Title:
  apt-daily.service was slowing down one system startup

Status in apt package in Ubuntu:
  New

Bug description:
  I don't understand why this service started before the light-dm invite
  was displayed to the end user.

  Up to the light-dm invite, the system needed roughly twice the time it
  usualy needs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.19
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb  6 21:28:54 2017
  InstallationDate: Installed on 2017-02-01 (4 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apt: 2017-02-03T22:39:52.394852

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

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

[Touch-packages] [Bug 1662259] Re: /usr/bin/webapp-container:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRende

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

** This bug has been marked a duplicate of bug 1638071
   
/usr/bin/webbrowser-app:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

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

Title:
  /usr/bin/webapp-
  
container:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
webbrowser-app.  This problem was most recently seen with package version 
0.23+16.04.20161028-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8bd90aedc28531ad72f1e3de383a16987ba6f094 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1662327] [NEW] apt-daily.service was slowing down one system startup

2017-02-06 Thread Jérôme

Public bug reported:

I don't understand why this service started before the light-dm invite
was displayed to the end user.

Up to the light-dm invite, the system needed roughly twice the time it
usualy needs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.19
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Feb  6 21:28:54 2017
InstallationDate: Installed on 2017-02-01 (4 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.d.apt: 2017-02-03T22:39:52.394852

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


** Tags: amd64 apport-bug xenial

** Attachment added: "systemd-analyse blame"
   
https://bugs.launchpad.net/bugs/1662327/+attachment/4814326/+files/systemd-analyse_blame.txt

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

Title:
  apt-daily.service was slowing down one system startup

Status in apt package in Ubuntu:
  New

Bug description:
  I don't understand why this service started before the light-dm invite
  was displayed to the end user.

  Up to the light-dm invite, the system needed roughly twice the time it
  usualy needs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.19
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb  6 21:28:54 2017
  InstallationDate: Installed on 2017-02-01 (4 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apt: 2017-02-03T22:39:52.394852

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

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

[Touch-packages] [Bug 1658117] Re: Chrome-less shell hint does not work any more

2017-02-06 Thread Lukáš Tinkl

** Changed in: unity8 (Ubuntu)
 Assignee: Nick Dedekind (nick-dedekind) => Lukáš Tinkl (lukas-kde)

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

** Branch linked: lp:~lukas-kde/qtmir/use-miral-shell-chrome

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

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

** Branch linked: lp:~lukas-kde/unity8/fix-shell-chrome

** No longer affects: qtubuntu (Ubuntu)

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

Title:
  Chrome-less shell hint does not work any more

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

Bug description:
  Test case.
  - Open camera in device mode.

  Expected result.
  - Camera opens full screen and top menu hides.

  Actual result.
  - Camera opens full screen but top menu is not hidden.

  current build number: 127
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

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

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

[Touch-packages] [Bug 1659412] Re: Ubuntu Budgie live session in virtualbox not displayed correctly

2017-02-06 Thread fossfreedom

ok - changing the display ram allocation from the default 12MB to 128MB
fixes this issue.

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

Title:
  Ubuntu Budgie live session in virtualbox not displayed correctly

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Budgie Alpha 2 AMD64 and i386

  see screenshot

  Note - this affect virtualbox only.

  In QEMU the display of the live-session is ok

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

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

[Touch-packages] [Bug 1389164] Re: Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in /etc/fstab

2017-02-06 Thread Michael Hohnbaum

** Changed in: mountall (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

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

Title:
  Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in
  /etc/fstab

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  Problem Description
  
  It seems the remote mounts in my /etc/fstab file are not being automatically 
mounted at bootup with ppc64le Ubuntu 14.10. This leads to some of my upstart 
scripts not running because they require certain mounts being available. I can 
give access to the machine via SSH key or password. Using mount -a or any other 
mount command works just fine after bootup. I don't personally notice a problem 
in logs with mounts.

  The machine is a VM hosted on a Power8 PowerKVM system running:
  # uname -a
  Linux kvm10d724t.rtp.raleigh.ibm.com 3.10.23-1700.pkvm2_1.2.ppc64 #1 SMP Mon 
Jun 2 20:14:25 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux
  # cat /etc/base-release
  IBM_PowerKVM release 2.1.0 build 18 Service (pkvm2_1)

  VM details:
  # uname -a
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.10
  DISTRIB_CODENAME=utopic
  DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)"

  If I recall correctly, we installed the 141002 daily build of Utopic
  Unicorn (14.10).

  I have implemented a workaround for now. I updated /etc/fstab to use
  IP addresses instead of names, put "mount -a" as the first non-
  commented line in /etc/init.d/mountnfs.sh and updated the crontab to
  run the jobs I had in the upstart configs. This works until the
  problem is fixed.

  ---uname output---
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ppc64le 
   
  Steps to Reproduce
  =
   Without the workaround implemented and NFS mounts in your /etc/fstab, boot 
up the machine. It should be evident the mount points aren't there with df -h.

  == Comment: #3 - Breno Henrique Leitao  -  ==
  I was able to reproduce this problem.
  NFS is not mounted automatically, but it is when you run 'mount -a'. 
  I also toggled ASYNCMOUNTNFS in /etc/defaults/rcS and no luck.

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

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

[Touch-packages] [Bug 1484249] Re: Add xserver-xorg-video-ati as a dependency for ubuntu-desktop/ubuntu-gnome-desktop

2017-02-06 Thread Manoj Iyer

** Changed in: xorg (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

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

Title:
  Add xserver-xorg-video-ati as a dependency for ubuntu-desktop/ubuntu-
  gnome-desktop

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Add xserver-xorg-video-ati as a dependency for ubuntu-desktop/ubuntu-
  gnome-desktop packages, to avoid X failure to start on machines that
  use this x driver.

  Please backport this feature to Ubuntu 14.04.

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

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

[Touch-packages] [Bug 1489483] Re: Enable llvmpipe on libgl-mesa-dri

2017-02-06 Thread Manoj Iyer

Based on comment #8 I am marking this as fix committed.

** Changed in: mesa (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: mesa (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

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

Title:
  Enable llvmpipe on libgl-mesa-dri

Status in mesa package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Gabriel Krisman Bertazi  - 2015-08-12 
09:53:27 ==
  The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) 
package for ppc64le, even though llvmpipe is fully supported on this 
architecture.  We need this feature enabled in order to run Unity with video 
cards lacking 3D Hardware Acceleration.

  Please enable it and, if possible, backport this change to 14.04.3.

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

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

2017-02-06 Thread Doug Goldstein

So this issue bit me in a weird way. I had my bridge called "xenbr0" and
the result of these two interacting gives me absolutely no DNS
resolution since the /etc/resolv.conf just pointed to 127.0.0.53 and
didn't include the DNS server from my "xenbr0". Renaming the bridge to
"renbr0" caused it to work. Why "renbr0"? Because in
/run/resolvconf/interface/ there is a file called systemd-resolved that
I was guessing was stopping combining the files once it hit the systemd-
resolved.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1337576] Re: dash inability - cron starts binary with /bin/sh

2017-02-06 Thread Manoj Iyer

Based on Steve's comment #8, this issue needs to worked with the
upstream dash. Marking this as incomplete and removing taco screen team
as the owner.

** Changed in: dash (Ubuntu)
   Status: Triaged => Incomplete

** Changed in: dash (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

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

Title:
  dash inability - cron starts binary with /bin/sh

Status in dash package in Ubuntu:
  Incomplete

Bug description:
  -- Problem Description --
  CRON uses shell to start a binary executable defined in crontab, which is a 
waste of the resources for the extra shell process hanging in the system. It's 
supposed to run it directly with exec system call.

  *** Here are some command outputs to see the extra process(12327) and 
relevant information: ***
  # ps -ef | grep -e CRON -e PMLnx
  root 12326   771  0 13:59 ?00:00:00 CRON
  root 12327 12326  0 13:59 ?00:00:00 /bin/sh -c 
/var/perf/pm/bin/daemon_PMLnx  <--- extra layer, a waste
  root 12328 12327  0 13:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # crontab -l
  59 * * * * /var/perf/pm/bin/daemon_PMLnx

  # file /var/perf/pm/bin/daemon_PMLnx
  /var/perf/pm/bin/daemon_PMLnx: ELF 64-bit LSB  executable, 64-bit PowerPC or 
cisco 7500, version 1 (SYSV), dynamically linked (uses shared libs), for 
GNU/Linux 3.0.0, BuildID[sha1]=1761d6d97eabb4e52870cb517fe6bf457e5bf89e, 
stripped

  # uname -a
  Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux

  # dpkg -l cron
  Name  VersionArchitecture  Description
  +++-=-==-=-=
  ii  cron  3.0pl1-124ubuntu2  ppc64el   process scheduling daemon

  *** Expect cron to directly execute a binary like this ***
  # ps -ef | grep -e CRON -e PMLnx
  root  2293  2223  0 09:59 ?00:00:00 /usr/sbin/CRON -n
  root  2294  2293  0 09:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # uname -a
  Linux hulala 3.12.15-3-default #1 SMP Wed Apr 2 17:08:55 UTC 2014 (69c2ea8) 
ppc64le ppc64le ppc64le GNU/Linux

  # cat /etc/SuSE-release
  SUSE Linux Enterprise Server 12 (ppc64le)
  VERSION = 12
  PATCHLEVEL = 0

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

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

[Touch-packages] [Bug 1641592] Re: nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

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

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

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

Title:
  nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

Status in nano package in Ubuntu:
  Triaged

Bug description:
  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  # apt-cache policy nano
  nano:
Installed: 2.5.3-2
Candidate: 2.5.3-2

  Reproducer:
  1. # nano -G 
999
  2. 
  3. # nano -G 
999
  4. 
  5. 

  Quick dissection:
  Looking at function do_lockfile in files.c, it seems that promptstr is 
statically allocated to 128 characters. Now with a sufficiently long filename, 
the following sprintf() call will overflow the allocated promptstr buffer and 
corrupt memory.

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

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

[Touch-packages] [Bug 1662260] [NEW] /usr/bin/pkexec:5:choose_identity:polkit_agent_text_listener_initiate_authentication:auth_agent_handle_begin_authentication:auth_agent_handle_method_call:call_in_i

2017-02-06 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
policykit-1.  This problem was most recently seen with package version 
0.105-14.1, the problem page at 
https://errors.ubuntu.com/problem/da61054648d6539774d46b1650c71096ced51621 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: precise raring saucy trusty utopic wily xenial

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

Title:
  
/usr/bin/pkexec:5:choose_identity:polkit_agent_text_listener_initiate_authentication:auth_agent_handle_begin_authentication:auth_agent_handle_method_call:call_in_idle_cb

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
policykit-1.  This problem was most recently seen with package version 
0.105-14.1, the problem page at 
https://errors.ubuntu.com/problem/da61054648d6539774d46b1650c71096ced51621 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1662253] [NEW] /usr/bin/pulseaudio:11:pa_bluetooth_device_any_transport_connected:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_

2017-02-06 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/611e08e54b2e1bab7707f341fda104668886d193 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: vivid xenial yakkety

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

Title:
  
/usr/bin/pulseaudio:11:pa_bluetooth_device_any_transport_connected:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/611e08e54b2e1bab7707f341fda104668886d193 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1662259] [NEW] /usr/bin/webapp-container:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRen

2017-02-06 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
webbrowser-app.  This problem was most recently seen with package version 
0.23+16.04.20161028-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8bd90aedc28531ad72f1e3de383a16987ba6f094 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: xenial

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

Title:
  /usr/bin/webapp-
  
container:6:qt_message_fatal:QMessageLogger::fatal:QSGRenderLoop::handleContextCreationFailure:QSGGuiThreadRenderLoop::renderWindow:QSGGuiThreadRenderLoop::exposureChanged

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
webbrowser-app.  This problem was most recently seen with package version 
0.23+16.04.20161028-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8bd90aedc28531ad72f1e3de383a16987ba6f094 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

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

2017-02-06 Thread Bill Erickson

dualshock3nerd's solution also works for me. It may also be worth
noting that the appearance of the bubble is often accompanied by a
slight, but noticeable gap in audio playback, which sounds like a click.
(I can tune out the bubble, but the click demands attention!) Seems
like the problem is pretty well understood at this point, though, so I
won't post any logs unless requested.

--
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 1662220] Re: [ListItem] Popupmenu shows traces of disabled actions

2017-02-06 Thread Tim Peeters

Can it be reproduced with ActionSelectionPopover too? That is the base
component of the ListItemPopover.

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

Title:
  [ListItem] Popupmenu shows traces of disabled actions

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

Bug description:
  Invisible actions on ListItem appears on top of the popup menu (check
  image)

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

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

[Touch-packages] [Bug 1662244] [NEW] lightdm fails to start

2017-02-06 Thread Doug Goldstein

Public bug reported:

lightdm is failing to start. Best guess is because of unity-session-
manager. This is from .xsession-errors.

dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
upstart: click-user-hooks main process (4028) terminated with status 1
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon main process ended, respawning
upstart: unity-settings-daemon respawning too fast, stopped
upstart: indicator-application main process ended, respawning
upstart: indicator-application main process ended, respawning
upstart: indicator-application respawning too fast, stopped
xbrlapi: window 0x03a00084 changed to NULL name
xbrlapi: window 0x03a00084 changed to NULL name
xbrlapi: window 0x03c00084 changed to NULL name
xbrlapi: window 0x03c00084 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
xbrlapi: window 0x0484 changed to NULL name
upstart: dbus main process (4023) killed by TERM signal


I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: lightdm 1.19.5-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Mon Feb  6 10:21:29 2017
InstallationDate: Installed on 2015-07-20 (566 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: lightdm
UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  lightdm fails to start

Status in lightdm package in Ubuntu:
  New

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL

[Touch-packages] [Bug 1650056] Re: /bin/nano:* Error in `nano': munmap_chunk(): invalid pointer: ADDR *

#0  0x7fb32f9ed428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 3997
selftid = 3997
#1  0x7fb32f9ef02a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x2e33322e322d646c, 
sa_sigaction = 0x2e33322e322d646c}, sa_mask = {__val = {3689400710896185203, 
3256155515023405872, 3473454209073047095, 3276212736508309552, 
347401934595760, 3544397105330139184, 3689067352599901472, 
2314885530818453536, 2314885530818453536, 7091318037929795616, 
3257288213055174703, 7955377262162766188, 3615882721364815733, 
7090415181300444723, 3472328296294789939, 3473176235347488048}}, sa_flags = 
808529972, sa_restorer = 0x4d}
sigs = {__val = {32, 0 }}
#2  0x7fb32fa2f7ea in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7fb32fb482e0 "*** Error in `%s': %s: 0x%s ***\n") at 
../sysdeps/posix/libc_fatal.c:175
ap = 
fd = 4
on_2 = 
list = 
nlist = 
cp = 
written = 
#3  0x7fb32fa3bae8 in malloc_printerr (ar_ptr=0x0, ptr=, 
str=0x7fb32fb48308 "munmap_chunk(): invalid pointer", action=) 
at malloc.c:5004
buf = "01520410"
cp = 
ar_ptr = 0x0
ptr = 
str = 0x7fb32fb48308 "munmap_chunk(): invalid pointer"
action = 
#4  munmap_chunk (p=) at malloc.c:2840
size = 
block = 
total_size = 
#5  __GI___libc_free (mem=) at malloc.c:2961
ar_ptr = 
p = 
hook = 
#6  0x7fb32ffbdd83 in _nc_freewin (win=0x15415b0) at 
/build/ncurses-pKZ1BN/ncurses-6.0+20160213/ncurses/base/lib_newwin.c:118
p = 0x15415a0
q = 
i = 
result = -1
#7  0x7fb32ffb5f90 in delwin (win=) at 
/build/ncurses-pKZ1BN/ncurses-6.0+20160213/ncurses/base/lib_delwin.c:88
result = -1
#8  0x00412f87 in window_init () at ../../src/nano.c:726
No locals.
#9  0x00414189 in regenerate_screen () at ../../src/nano.c:1378
tty = 
result = 0
win = {ws_row = 24, ws_col = 81, ws_xpixel = 0, ws_ypixel = 0}
#10 0x004201b9 in get_key_buffer (win=0x1520d20) at 
../../src/winio.c:136
input = -1
errcount = 0
#11 0x004203d2 in get_key_buffer (win=0x1520d20) at 
../../src/winio.c:300
No locals.
#12 get_input (win=win@entry=0x1520d20, input_len=input_len@entry=1) at 
../../src/winio.c:262
input = 
#13 0x004224fd in parse_kbinput (win=win@entry=0x1520d20) at 
../../src/winio.c:345
escapes = 0
byte_digits = 0
kbinput = 
retval = -1
#14 0x00422ab8 in get_kbinput (win=0x1520d20) at ../../src/winio.c:316
kbinput = 
#15 0x0041619d in do_yesno_prompt (all=all@entry=false, 
msg=msg@entry=0x1520380 "File 
/etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla is 
being edited (by root with nano 2.5.3, PID 3956); continue?") at 
../../src/prompt.c:876
kbinput = 32764
func = 
mouse_x = 3956
mouse_y = 0
response = -2
width = 16
yesstr = 0x429778 "Yy"
nostr = 0x42977b "Nn"
allstr = 0x42977e "Aa"
oldmenu = 0
#16 0x00408b4c in do_lockfile (filename=filename@entry=0x7ffcc6f0d7c1 
"/etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla") at 
../../src/files.c:373
readtot = 
promptstr = 0x1520380 "File 
/etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla is 
being edited (by root with nano 2.5.3, PID 3956); continue?"
readamt = 
lockbuf = 0x1582390 "/dev/pts/1"
ans = 
namecopy1 = 
namecopy2 = 
locknamesize = 
lockfilename = 0x1520440 
"/etc/polkit-1/localauthority/50-local.d/.com.ubuntu.enable-hibernate.pkla.swp"
lockprog = "nano 2.5.3"
lockuser = "root", '\000' 
fileinfo = {st_dev = 64513, st_ino = 789642, st_nlink = 1, st_mode = 
33188, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 1024, 
st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1477472655, tv_nsec = 
339666299}, st_mtim = {tv_sec = 1477472655, tv_nsec = 339666299}, st_ctim = 
{tv_sec = 1477472655, tv_nsec = 339666299}, __glibc_reserved = {0, 0, 0}}
lockpid = 3956
retval = -1
#17 0x0040ccf1 in open_buffer (filename=0x7ffcc6f0d7c1 
"/etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla", 
undoable=undoable@entry=false) at ../../src/files.c:457
lockstatus = 
quiet = false
new_buffer = true
f = 0x3b
rc = 
#18 0x0040431c in main (argc=2, argv=0x7ffcc6f0bd28) at 
../../src/nano.c:2599
optchr = 
startline = 0
startcol = 0
fill_used = 
forced_wrapping = 
old_multibuffer = false
long_options = {{name = 0x428236 "boldtext", has_arg = 0, flag = 0x0, 
val = 68}, {name =

[Touch-packages] [Bug 1661757] Re: libc6 Depends line for xenial i386 package appears to be incorrect.

2017-02-06 Thread Rodney Lott

Oops! I just realized my mistake in comprehension. There is nothing to
suggest that i386 and amd64 can't be linked against different versions
of libc6, given that each arch may have different revision histories.
Sorry about that: tired Friday work brain strikes again! :-(

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

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

Title:
  libc6 Depends line for xenial i386 package appears to be incorrect.

Status in ncurses package in Ubuntu:
  Invalid

Bug description:
  Upon inspecting the i386 and amd64 packages of libncurses5/xenial,
  there appears to be an error in the libc6 dependency for the i386
  case:

  $ dpkg -I libncurses5_6.0+20160213-1ubuntu1_amd64.deb | grep Depends
   Depends: libtinfo5 (= 6.0+20160213-1ubuntu1), libc6 (>= 2.14)
  $ dpkg -I libncurses5_6.0+20160213-1ubuntu1_i386.deb | grep Depends
   Depends: libtinfo5 (= 6.0+20160213-1ubuntu1), libc6 (>= 2.4)

  As you can see, the amd64 version indicates a libc6 version of 2.14 or
  greater, but the i386 version says 2.4 or greater. It would appear
  that this is a typo, since it should match the amd64 case and that
  there is no libc6 version in Ubuntu with that version number. Ubuntu
  Zesty has a libc6 version of 2.24-7ubuntu2.

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

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

[Touch-packages] [Bug 1662220] Re: [ListItem] Popupmenu shows traces of disabled actions

2017-02-06 Thread Renato Araujo Oliveira Filho

** Attachment added: "example code"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1662220/+attachment/4814141/+files/menu_item.qml

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

Title:
  [ListItem] Popupmenu shows traces of disabled actions

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

Bug description:
  Invisible actions on ListItem appears on top of the popup menu (check
  image)

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

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

[Touch-packages] [Bug 1662220] Re: [ListItem] Popupmenu shows traces of disabled actions

2017-02-06 Thread Renato Araujo Oliveira Filho

** Attachment added: "Screenshot from 2017-02-06 13-05-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1662220/+attachment/4814140/+files/Screenshot%20from%202017-02-06%2013-05-32.png

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

Title:
  [ListItem] Popupmenu shows traces of disabled actions

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

Bug description:
  Invisible actions on ListItem appears on top of the popup menu (check
  image)

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

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

[Touch-packages] [Bug 1662220] [NEW] [ListItem] Popupmenu shows traces of disabled actions

2017-02-06 Thread Renato Araujo Oliveira Filho

Public bug reported:

Invisible actions on ListItem appears on top of the popup menu (check
image)

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [ListItem] Popupmenu shows traces of disabled actions

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

Bug description:
  Invisible actions on ListItem appears on top of the popup menu (check
  image)

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

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

[Touch-packages] [Bug 1662213] [NEW] update not working

2017-02-06 Thread tubaplayer

Public bug reported:

Updater on Unbuntu 16.10 not working.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb  6 15:01:22 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:390b]
InstallationDate: Installed on 2017-02-03 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 80E5
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=c9733e2b-2374-49a4-a1c6-d3cf821ecfe1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: B0CN95WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo G50-80
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-80
dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN95WW:bd07/31/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
dmi.product.name: 80E5
dmi.product.version: Lenovo G50-80
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Mon Feb  6 14:03:12 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


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

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

Title:
  update not working

Status in xorg package in Ubuntu:
  New

Bug description:
  Updater on Unbuntu 16.10 not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb  6 15:01:22 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:390b]
  InstallationDate: Installed on 2017-02-03 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 80E5
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=c9733e2b-2374-49a4-a1c6-d3cf821ecfe1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN95WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN95WW:bd07/31/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoG50-80:

[Touch-packages] [Bug 1559821] Re: Camera app does not rotate when rotation lock is enabled

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

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

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

Title:
  Camera app does not rotate when rotation lock is enabled

Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  1. Enable "Rotation Lock"
  2. Open the Camera app
  3. Take a picture/video in landscape and in portrait.

  Actual Result:
  The picture/video is in correct orientation but the controls doesn't indicate 
that the phone is rotated.

  Expected:
  I think the camera app UI should still rotate even when "Rotation Lock" is 
enabled.
  The resulting picture and video are already not affected by this setting so 
it will make sense to make it more obvious to users.


  Device:
  bq Aquaris E5 HD
  OTA 9.1

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

2017-02-06 Thread ChristianEhrhardt

Issue did no more show up on two retries of the test, also what showed up was 
totally unrelated to the upload we made.
That said should be safe to migrate now.

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

2017-02-06 Thread ChristianEhrhardt

I found (thank apw) that this triggers an unrelated dep8 test fail which is the 
reason it stalled.
Investigating ...

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1648959] Re: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-02-06 Thread Dimitri John Ledkov

Are you running a live CD session and trying to upgrade that? One should
not do that, as it's not supported to dist-upgrade CDs.

cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file or 
directory
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package udev 229-4ubuntu12 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  after installing updates via Software Updater
  Ubuntu version:16.04.1 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Sat Dec 10 10:52:01 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  MachineType: TOSHIBA Satellite L650
  ProcKernelCmdLine: 
file=/cdrom/multiboot/hostname-16.04.1-desktop-amd64/preseed/hostname.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/hostname-16.04.1-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/hostname-16.04.1-desktop-amd64/casper/ 
initrd=/multiboot/hostname-16.04.1-desktop-amd64/casper/initrd.lz quiet splash 
--- debian-installer/language=cs keyboard-configuration/layoutcode?=cz
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: systemd
  Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.40
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL650:pvrPSK1JE-0CR008CZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite L650
  dmi.product.version: PSK1JE-0CR008CZ
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1662178] [NEW] not compatible

2017-02-06 Thread agus

Public bug reported:

IBM xserver3200

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Feb  6 20:47:16 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02) (prog-if 00 
[VGA controller])
   Subsystem: IBM ES1000 [1014:0325]
InstallationDate: Installed on 2016-10-23 (106 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
LightdmDisplayLog: [mi] Increasing EQ size to 1024 to prevent dropped events.
MachineType: IBM IBM System x3200 -[4362IQS]-
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f9c6019e-9d83-4793-85ee-5447f37389a0 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2007
dmi.bios.vendor: IBM
dmi.bios.version: IBM BIOS Version 1.34-[G8E134AUS-1.34]-
dmi.board.name: M31IX
dmi.board.vendor: IBM
dmi.board.version: SIT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 7
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnIBM:bvrIBMBIOSVersion1.34-[G8E134AUS-1.34]-:bd08/10/2007:svnIBM:pnIBMSystemx3200-[4362IQS]-:pvrIBMCORPORATION:rvnIBM:rnM31IX:rvrSIT:cvnNoEnclosure:ct7:cvrN/A:
dmi.product.name: IBM System x3200 -[4362IQS]-
dmi.product.version: IBM CORPORATION
dmi.sys.vendor: IBM
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75+git20170206.fe7cb34e-0ubuntu0ricotz~xenial
version.libgl1-mesa-dri: libgl1-mesa-dri 
17.0.0~git20170126+17.0.d283ec0a-0ubuntu0ricotz~xenial
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
17.0.0~git20170126+17.0.d283ec0a-0ubuntu0ricotz~xenial
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git20161127.487aa62a-0ubuntu0ricotz~xenial
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20161127.bde94605-0ubuntu0ricotz~xenial
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20161127.1516d35b-0ubuntu0ricotz~xenial
xserver.bootTime: Thu Feb  2 22:08:02 2017
xserver.configfile: default
xserver.errors:
 AIGLX error: Calling driver entry point failed
 AIGLX: reverting to software rendering
 evdev:  USB OPTICAL MOUSE: Unable to open evdev device "/dev/input/event2".
 PreInit returned 2 for " USB OPTICAL MOUSE"
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug third-party-packages 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/1662178

Title:
  not compatible

Status in xorg package in Ubuntu:
  New

Bug description:
  IBM xserver3200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  6 20:47:16 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02) (prog-if 
00 [VGA controller])
 Subsystem: IBM ES1000 [1014:0325]
  InstallationDate: Installed on 2016-10-23 (106 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog: [mi] Increasing EQ size to 1024 to prevent dropped events.
  MachineType: IBM IBM System x3200 -[4362IQS]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f9c6019e-9d83-4793-85ee-5447f37389a0 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: IBM BIOS Version 1.34-[G8E134AUS-1.34]-
  dmi.board.name: M31IX
  dmi.board.vendor: IBM
  dmi.board.version: SIT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 7
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias:

[Touch-packages] [Bug 1662176] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all

2017-02-06 Thread Charanjeet09

Public bug reported:

the inbuilt speaker is having no sound but in headphone the sound is coming .
Note: After i have readjust internal speaker jack to headphone the sound 
started but the problem now is that the sound does not mute even while using 
using headphone

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mrsingh3701 F pulseaudio
CurrentDesktop: Unity
Date: Mon Feb  6 19:06:58 2017
InstallationDate: Installed on 2017-02-03 (3 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mrsingh3701 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/30/2011:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

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


** Tags: apport-bug i386 yakkety

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

Title:
  [HDA-Intel - HDA Intel, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the inbuilt speaker is having no sound but in headphone the sound is coming .
  Note: After i have readjust internal speaker jack to headphone the sound 
started but the problem now is that the sound does not mute even while using 
using headphone

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrsingh3701 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  6 19:06:58 2017
  InstallationDate: Installed on 2017-02-03 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrsingh3701 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/30/2011:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015PE
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1662175] [NEW] Gallery should play videos in-app

2017-02-06 Thread TheJeje20

Public bug reported:

Currently, playing a video by clicking the button "play" inside the gallery 
takes the user to the media player app.
I see 3 downsides to this approach:
-launching the media player app is slow
-the user has to exit the media player to return to the gallery
-the user cannot swipe to the left or to the right in order to see the next or 
previous image/video

The 'videos' scope has the good approach: hitting the play button inside
the scope keeps the user inside the scope and plays the video in the
dedicated zone.

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

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

Title:
  Gallery should play videos in-app

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Currently, playing a video by clicking the button "play" inside the gallery 
takes the user to the media player app.
  I see 3 downsides to this approach:
  -launching the media player app is slow
  -the user has to exit the media player to return to the gallery
  -the user cannot swipe to the left or to the right in order to see the next 
or previous image/video

  The 'videos' scope has the good approach: hitting the play button
  inside the scope keeps the user inside the scope and plays the video
  in the dedicated zone.

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

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

[Touch-packages] [Bug 1662137] Re: 16.04 recovery shell works only for two minutes

2017-02-06 Thread Dimitri John Ledkov

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.02

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

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

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

Title:
  16.04 recovery shell works only for two minutes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Selecting "Rescue" shell from the "Advanced options" menu in grub
  enters the "friendly-recovery" service and allows to drop into a root
  shell.  After ~120 seconds, systemd sees a timeout and starts another
  "friendly-recovery" whiptail process.  This and the running shell now
  compete for tty access (input and output) thus making the shell nearly
  unusable.

  Diagnosing this, it becomes clear that in the first root shell entered
  from friendly-recovery, "systemctl list-jobs" lists the generated
  "wait for disk" tasks for the /boot partition and the swap partition
  still to be running.  Only when they run into a timeout, the next
  friendly-recovery is spawned.  I'll attach a log session for such a
  boot that has two manual "logger" entries in it:

  Feb 06 10:54:57 harry root[605]: now in root shell from friendly-recovery
  ...
  Feb 06 10:56:41 harry root[1254]: now running in parallel

  This clearly shows the timing of the startup.

  I have no idea why the "wait for disk" units run into a timeout as the
  system boots correctly in the "non-rescue" mode.  I'll further attach
  a "systemd-analyze blame" from a regular bootup to show that there is
  no trace of such a timeout to be found.

  Furthermore i do have this behaviour on a real machine and on an
  (independent) VM, so affects more than the machine the bug was
  reported from.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  6 11:02:37 2017
  InstallationDate: Installed on 2015-03-27 (681 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 
loop.max_part=63 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-12-01 (66 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.asset.tag: 617H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

2017-02-06 Thread ChristianEhrhardt

Verification was done 17 days ago, I think that should be ok to migrate
right?

Also we have another set of SRU in queue waiting for this to get out of
the way.

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1655839] Re: amd64 build of heimdal 7.1.0+dfsg-9 FAIL: test_rfc3961

2017-02-06 Thread dino99

** Tags added: ftbfs

** Summary changed:

-   amd64 build of heimdal 7.1.0+dfsg-9  FAIL: test_rfc3961
+ [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9  FAIL: test_rfc3961

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

Title:
  [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9  FAIL: test_rfc3961

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  A few builds have failed: amd64, ppc64el & s390x for Zesty proposed

  for example amd64 fails on test_rfc3961

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

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

[Touch-packages] [Bug 1662165] [NEW] package libunity9:amd64 (not installed) failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

2017-02-06 Thread virendra jangid

Public bug reported:

I am facing this issue while trying to install or remove any application
and softwares.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libunity9:amd64 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 libunity9: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Feb  6 18:01:07 2017
DpkgTerminalLog:
 dpkg: error processing package libunity9:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-02-02 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: libunity
Title: package libunity9:amd64 (not installed) failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libunity9:amd64 (not installed) failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libunity package in Ubuntu:
  New

Bug description:
  I am facing this issue while trying to install or remove any
  application and softwares.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9:amd64 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   libunity9: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb  6 18:01:07 2017
  DpkgTerminalLog:
   dpkg: error processing package libunity9:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-02-02 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libunity
  Title: package libunity9:amd64 (not installed) failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1662166] [NEW] [TM1612, Realtek ALC233, Speaker, Internal] No sound at all

2017-02-06 Thread Li Haomin

Public bug reported:

Description:Ubuntu 16.04.1 LTS
Release:16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lihaomin   3433 F pulseaudio
CurrentDesktop: Unity
Date: Mon Feb  6 20:48:01 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-06 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lihaomin   3433 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [TM1612, Realtek ALC233, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2016
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: A04
dmi.board.asset.tag: Any
dmi.board.name: TM1612
dmi.board.vendor: Timi
dmi.board.version: MP
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Timi
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrA04:bd08/06/2016:svnTimi:pnTM1612:pvr:rvnTimi:rnTM1612:rvrMP:cvnTimi:ct10:cvrChassisVersion:
dmi.product.name: TM1612
dmi.sys.vendor: Timi

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


** Tags: amd64 apport-bug xenial

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

Title:
  [TM1612, Realtek ALC233, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lihaomin   3433 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  6 20:48:01 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lihaomin   3433 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [TM1612, Realtek ALC233, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: A04
  dmi.board.asset.tag: Any
  dmi.board.name: TM1612
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrA04:bd08/06/2016:svnTimi:pnTM1612:pvr:rvnTimi:rnTM1612:rvrMP:cvnTimi:ct10:cvrChassisVersion:
  dmi.product.name: TM1612
  dmi.sys.vendor: Timi

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

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

[Touch-packages] [Bug 1570335] Re: MusicBrainz integration

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

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

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

Title:
  MusicBrainz integration

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Music App:
  Triaged
Status in mediascanner2 package in Ubuntu:
  Confirmed
Status in thumbnailer package in Ubuntu:
  Confirmed

Bug description:
  I'd love to see the ability to download missing metadata for music
  from MusicBrainz (the Open Source equivalent of Sony's
  CDDB/Gracenote)... Either automatically, or on-request (by the user).

  Ubuntu for mobile devices is already very much an "online first"
  operating system and my understanding is that this is unlikely to
  change anytime soon, so it is reasonable to expect that MusicBrainz
  integration would have access to a data connection most - if not all -
  of the time.

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

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

[Touch-packages] [Bug 1488386] Re: [performance] Rendering is only smooth while you're touching the screen

Possibly fixed now. But we'll need to wait for Mir release 0.26.1 to be
able to verify (due to bug 1661128)

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

Title:
  [performance] Rendering is only smooth while you're touching the
  screen

Status in Mir:
  Incomplete
Status in QtMir:
  New
Status in Unity System Compositor:
  In Progress
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New

Bug description:
  On some devices (mako at least) it's possible to force double
  buffering and it will often keep up:

     restart unity8 QML_NO_TOUCH_COMPRESSION=1 MIR_SERVER_NBUFFERS=2

  Curiously however it only keeps up smoothly (eg. during a dash scroll)
  while you're touching the screen. If you lift off or fling the dash
  then it immediately stutters, quite badly.

  So the issue is not that the device can't keep up with double buffering. It 
seems more like we're not keeping the kernel sufficiently awake and it's 
clocking down prematurely, as soon as we're not touching it. Certainly 
adjusting the variables in:
     /sys/devices/system/cpu/cpu0/cpufreq
  it is possible to raise the performance and minimum frequency to make double 
buffering smooth.

  The challenge of this bug is to find a way in Mir/QtMir to keep the
  kernel more awake so it doesn't clock down when we need smooth
  animations and we're not touching the screen.

  Also note that while this bug sounds like bad news for mako, mako is
  actually the best performing device. Others like arale don't reliably
  speed up in response to short touches.

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

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

[Touch-packages] [Bug 1570335] Re: MusicBrainz integration

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

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

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

Title:
  MusicBrainz integration

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Music App:
  Triaged
Status in mediascanner2 package in Ubuntu:
  Confirmed
Status in thumbnailer package in Ubuntu:
  Confirmed

Bug description:
  I'd love to see the ability to download missing metadata for music
  from MusicBrainz (the Open Source equivalent of Sony's
  CDDB/Gracenote)... Either automatically, or on-request (by the user).

  Ubuntu for mobile devices is already very much an "online first"
  operating system and my understanding is that this is unlikely to
  change anytime soon, so it is reasonable to expect that MusicBrainz
  integration would have access to a data connection most - if not all -
  of the time.

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

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

[Touch-packages] [Bug 1455087] Re: [mako] Camera-app causing hard reset of device

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

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

Title:
  [mako] Camera-app causing hard reset of device

Status in camera-app:
  New
Status in Mir:
  Invalid
Status in camera-app package in Ubuntu:
  New

Bug description:
  I've had this 3 times now over the past 6 months, so it doesn't happen
  very often.

  The latest occurrence I was opening the camera-app in photo mode and
  as the viewfinder was opening the phone reboot instantly with the
  Google logo, the other occurrences happened when attempting to take a
  photo. I've been able to extract a log for the latest occurrence here
  [0]. As you can see from L134 there are Mir/EGL exceptions that happen
  very rapidly over a short period of time, therefore I'm going to add
  Mir to this bug as well.

  0 - http://pastebin.ubuntu.com/11130346/

  $ system-image-cli -i
  current build number: 193
  device name: mako
  channel: ubuntu-touch/devel-proposed-customized-here
  alias: ubuntu-touch/vivid-proposed-customized-here
  last update: 2015-05-14 13:51:16
  version version: 193
  version ubuntu: 20150514
  version device: 20150210
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1579957] Re: Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()

No offense... but this needs to be unassigned in order for the automatic
expiration period to begin.

** Changed in: canonical-devices-system-image
 Assignee: Stephen M. Webb (bregma) => (unassigned)

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

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

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

Title:
  Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from
  mir::client::rpc::MirProtobufRpcChannel::on_data_available()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.12+15.04.20160504.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/2c3cad3ba17d755e656dc7db06c77e7854c117b8
  contains more details.

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

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

[Touch-packages] [Bug 1661690] Re: Reload page shortcut not working in u8

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New => 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/1661690

Title:
  Reload page shortcut not working in u8

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  the keyboard shortcuts for reloading a page are not working in unity8 (ctrl-r 
and f5)
  they work fine in u7
  most other shortcuts I've tried in u8 work

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

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

[Touch-packages] [Bug 1649077] Re: [regression] OSK appears blank and/or flickers in the lock screen

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

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

Title:
  [regression] OSK appears blank and/or flickers in the lock screen

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 1617975] Re: Image flickers when pressing the screen after video playing ends

2017-02-06 Thread TheJeje20

Meizu Pro 5 OTA14 is also affected.
There is a flickering AND also the last frame of the video is mirrored upside 
down.

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

Title:
  Image flickers when pressing the screen after video playing ends

Status in Canonical System Image:
  New
Status in mediaplayer-app:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Enviroment:

  current build number: 176
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-29 08:48:35
  version version: 176
  version ubuntu: 20160827
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Camera app: com.ubuntu.camera 3.0.0.659

  Product: BQ M10 FHD
  Preconditions:

  Steps to reproduce:

  1º Record a video with Frieza
  2º Watch it with media player 
  3º Once it ends, tap the screen and check that image flickers

  Current result: Image flickers after playing a video
  Expected result: Pressing the screen should not make image flickers

  Reproducibility: 100%

  Add info: video attached

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

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

[Touch-packages] [Bug 876279] Re: Upowerd excessive CPU usage

2017-02-06 Thread Daniel Robbers

Had the same 'issue', after unlocking my Iphone (6) and trusting the
computer. Upowerd cpu usage dropped.

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

Title:
  Upowerd excessive CPU usage

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  Fresh installation of Oneiric on Activo A-1100 (Atom N450-based)
  netbook. Top reports CPU usage fluctuating between 60% and 100%,
  averaging around 80%. Machine still marginally usable, due to having a
  second core.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: upower 0.9.13-1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Mon Oct 17 18:59:31 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup

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

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

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

Title:
  hugepages for non-default pagesize need manual setup

Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in nova-compute package in Juju Charms Collection:
  Triaged

Bug description:
  This is a amd64 xenial/mitaka deploy using 1607 charms release
  where I need to have 1G hugepages available for openstack/kvm.

  nova-compute charm should provide ways to ease e.g.
  1G hugepages setup, currently only exposes a 
  "hugepages" setting that ends setting vm.nr_hugepages
  for the node, but even after settings kernel cmdline
  parameters for 1G hugepages (hugepagesz=1G hugepages=128),
  is not usable by libvirt-bin:

  #1 systemd:
  Installs /lib/systemd/system/dev-hugepages.mount with
  default pagesize
  => no hugetblfs mount with (e.g.) pagesize=1G

  #2 libvirt-bin:
  Installs apparmor profile ("libvirt-qemu") which only allows:
# for access to hugepages
owner "/run/hugepages/kvm/libvirt/qemu/**" rw,
owner "/dev/hugepages/libvirt/qemu/**" rw,
  => not possible to have other mount points for other pagesizes.

  I've workaround'd #1,#2 above by overriding systemd's
  by creating a /etc/systemd/system/dev-hugepages.mount
  with below extra line at [Mount] section:
  Options=pagesize=1G
  -> https://paste.ubuntu.com/23513048/

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

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

[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup