[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Martin Pitt]

For the record: the "hang" was the ~ 10s timeout for IPv6 RA. I was
testing with Yakkety/Zesty's QEMU whose "user" net has a builtin RA (you
get an fec0::* address), while xenial's doesn't.

We enable RA (on the client side) by default, and IMHO should really do
so -- selling a new solution in 2016 which does not speak IPv6 would be
hilarious. You can't also significantly reduce the timeout, as this
would make RA unreliable and it's presumably also a specification
somewhere.

So AFAICS the remaining issue is just to make networkd run before
dbus.service/socket in systemd, and add "After=networking.service
systemd-networkd-wait-online.service" and drop
"Wants=networking.service" in cloud-init.service.

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

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

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  In Progress
Status in cloud-init source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  
  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
└─basic.target @11.403s
  └─sockets.target @11.401s
└─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
└─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
└─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
└─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
└─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
└─system.slice @783ms
  └─-.slice @721ms

  
  cloud-init would need networkd to run at or before 'networking.service' so it 
can raise networking to then find and use network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list 
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   

[Touch-packages] [Bug 1637801] Re: Incorrect Russian translation of "apt list --upgradeable" results

[Martin Pitt]

> The correct approach is to have gettext look into the langpack
translations first, and then fall back to the package's translations.

No, it's not. Normal/released Ubuntu packages get their translations
stripped out of the debs. But if you install a backport, third-party
package, or self-built package, you want to see the translation that it
ships, not the Ubuntu translations as they now apply to an older version
only. Hence /usr/share/locale/ must have precedence over /usr/share
/locale-langpack/.

There are just a handful of packages which you need for upgrading and
*installing* langpacks which have their translations built-in, like apt
or language-selector.

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

Title:
  Incorrect Russian translation of "apt list --upgradeable" results

Status in Ubuntu Translations:
  Invalid
Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  bor@bor-Latitude-E5450:~$ apt list --upgradeable
  Вывод списка… Готово
  build/неизвестно 20161025 all [может быть обновлён до: 20151105]

  In Russian this means "version 20161025 can be upgraded TO version
  20151105)

  While original English says exactly opposite:

  bor@bor-Latitude-E5450:~$ LC_ALL=C LANG=C apt list --upgradeable
  Listing... Done
  build/unknown 20161025 all [upgradable from: 20151105]

  Literal translation (that does not require serious phrase change)
  would probably be

  "может быть обновлен с"

  although it sounds also artificial, as in Russian subject is package
  that is being updated (currently installed), not new version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 30 09:39:47 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-07-02 (485 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-10-29 (0 days ago)

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

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Michi Henning]

Thanks for all the detective work!

I suspect that the MiddlewareException in coincidental and caused by an
earlier timeout. But we shouldn't get stuck like this and things should
recover transparently if the network goes away. I'll have a look and see
what's going on.

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1638922] Re: [needs-packaging] tar : CVE-2016-6321 not patched in stable

[vishnunaini]

I removed the needs-packaging tag. Wasn't aware that it is only for new
packages.

** Tags removed: needs-packaging

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

Title:
  [needs-packaging] tar : CVE-2016-6321 not patched in stable

Status in tar package in Ubuntu:
  New

Bug description:
  CVE-2016-6321 path name extract bypass vulnerability is not patched in
  stable releases of yakkety, xenial and other supported releases.

  The maintainer appears to have only pushed the patch to zesty
  proposed.

  Please push the patch for the stable releases as this bug could have
  seroius implications in certain environments.

  Upstream debian has already pushed the patch to stable.

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842339

  https://people.canonical.com/~ubuntu-
  security/cve/2016/CVE-2016-6321.html

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

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

[Touch-packages] [Bug 1354793] Re: Radeon X-Server Error

[Launchpad Bug Tracker]

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

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

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

Title:
  Radeon X-Server Error

Status in xorg package in Ubuntu:
  Expired

Bug description:
  whenever i click or move the pointer with the help of arrow keys the
  screen disappears and returns to desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-input-synaptics 1.7.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 10 11:03:38 2014
  DistUpgraded: 2014-08-10 07:19:28,008 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DistroCodename: trusty
  DistroVariant: ubuntu
  InstallationDate: Installed on 2012-12-18 (599 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. Inspiron 5521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=74efedff-26f6-43c4-8270-ac5121afd682 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: Upgraded to trusty on 2014-08-10 (0 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0HK2KG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/24/2012:svnDellInc.:pnInspiron5521:pvrA03:rvnDellInc.:rn0HK2KG:rvrA00:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Inspiron 5521
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Aug 10 10:20:22 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1378566] Re: My touchpad functions (scrolling, two fingers tapping) doesn't work

[Launchpad Bug Tracker]

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

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

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

Title:
  My touchpad functions (scrolling, two fingers tapping) doesn't work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  It looks like my touchpad isn't detected correctly:

  here are the results of the following commands:

  cat /proc/bus/input/devices :

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0011 Vendor=0002 Product=0001 Version=
  N: Name="PS/2 Generic Mouse"
  P: Phys=isa0060/serio4/input0
  S: Sysfs=/devices/platform/i8042/serio4/input/input11
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=3

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:5f/LNXVIDEO:00/input/input12
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input13
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input14
  U: Uniq=
  H: Handlers=rfkill kbd event7 
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input16
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input15
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel HDMI HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input19
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel HDMI HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input18
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel HDMI HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=1bcf Product=2883 Version=0429
  N: Name="ASUS USB2.0 Webcam"
  P: Phys=usb-:00:14.0-7/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-7/3-7:1.0/input/input20
  U: Uniq=
  H: Handlers=kbd event13 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0
   --
  xinput --list :

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus

[Touch-packages] [Bug 1380218] Re: Backport xserver-xorg-input-synaptics 1.8.1 to 14.04 LTS

[Launchpad Bug Tracker]

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

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

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

Title:
  Backport xserver-xorg-input-synaptics 1.8.1 to 14.04 LTS

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Clickpads are a part of a wide range of professional Lenovo Thinkpad
  machines. The touchpads/clickpads on these laptops do not work well
  with the synaptics driver version 1.7.x. Since the 14.04 is an LTS
  version, I do not plan to upgrade to 14.10. I imagine many users of
  the Lenovo Thinkpad line are in a similar situation.

  Since version 1.8.x fixes a lot of these issues, see commit here:

  http://cgit.freedesktop.org/xorg/driver/xf86-input-
  synaptics/tag/?id=xf86-input-synaptics-1.8.1

  and blog post here:

  http://who-t.blogspot.de/2014/03/xorg-synaptics-support-for-
  lenovo-t440.html

  Please offer 1.8.x as backported package in 14.04.

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

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

[Touch-packages] [Bug 1618794] Re: freeze when switching between users

[Launchpad Bug Tracker]

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

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

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

Title:
  freeze when switching between users

Status in xorg package in Ubuntu:
  Expired

Bug description:
  When I switch between user sometimes the display freeze or the text
  disappear below the icons.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/sda1: clean, 305091/1152816 files, 2068249/4607910 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 31 10:11:07 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   nvidia-340, 340.96, 4.4.0-28-generic, x86_64: installed
   nvidia-340, 340.96, 4.4.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1682]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-07-17 (44 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer Inc. U30Sd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=cfe5d040-0340-4ee6-b491-3846f5742d2d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U30Sd.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U30Sd
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU30Sd.211:bd07/06/2011:svnASUSTeKComputerInc.:pnU30Sd:pvr1.0:rvnASUSTeKComputerInc.:rnU30Sd:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U30Sd
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 31 06:02:57 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13612 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Touch-packages] [Bug 1436646] Re: Touchpad on HP Stream 14-z040wm is a "PS/2 Generic Mouse", is missing features

[Launchpad Bug Tracker]

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

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

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

Title:
  Touchpad on HP Stream 14-z040wm is a "PS/2 Generic Mouse", is missing
  features

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Missing features include scroll & multitouch. Verified these features
  are present in windows. I am not able to identify which manufacturer
  the touchpad is from.

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

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

[Touch-packages] [Bug 1447317] Re: Tripple tap to click (middle button) not enabled by default on Thinkpad Yoga 12

[Launchpad Bug Tracker]

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

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

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

Title:
  Tripple tap to click (middle button) not enabled by default on
  Thinkpad Yoga 12

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Three finger tap to middle-click is not enabled by default on Thinkpad
  Yoga S12, need setting with:

  synclient TapButton3=2

  Should this be default (or an option to enable it be provided?)

  Possibly a duplicate of bug #840509 but that details a behavioural
  regression since 11.10 (I'm not sure if my hardware would ever have
  had this functionality working and enabled by default on that old a
  distro for this to be the same issue).

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

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

[Touch-packages] [Bug 1619668] Re: Brightness is not changed after pluging or restore after sleep

[Launchpad Bug Tracker]

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

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

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

Title:
  Brightness is not changed after pluging or restore after sleep

Status in xorg package in Ubuntu:
  Expired

Bug description:
  All these happens after 14-->16 upgrade

  Scenario:

  1. let my laptop go to asleep mode after some idle(say 5 minutes)
  2. let switch on it by 'power' button
  3. monitor's brightness is dark - expected to be normal brightness not that 
dark
  4. if do unplug AC adapter(or unplug from docking station)  - monitor's 
become bright so one can read text

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep  2 16:22:49 2016
  DistUpgraded: 2016-08-17 13:31:37,867 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 3.19.0-66-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  DpkgLog:

  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d2]
  InstallationDate: Installed on 2015-12-17 (259 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 41716PG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=14d23f0e-cfcc-40fd-87e2-7ca166c9b29f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (16 days ago)
  dmi.bios.date: 04/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CET59WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 41716PG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CET59WW(1.39):bd04/29/2015:svnLENOVO:pn41716PG:pvrThinkPadT420s:rvnLENOVO:rn41716PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 41716PG
  dmi.product.version: ThinkPad T420s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 31 22:23:57 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Launchpad Bug Tracker]

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

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

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

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1619851] Re: Sometimes second screen shutdown

[Launchpad Bug Tracker]

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

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

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

Title:
  Sometimes second screen shutdown

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04 x64

  
  xserver-xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.espol.edu.ec/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  When connect second screen with DisplayPort mini, It displays correctly.

  4) Sometimes second screen shutdown when i use DisplayPort mini.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep  3 00:51:45 2016
  DistUpgraded: 2016-04-26 21:08:25,311 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:802d]
  InstallationDate: Installed on 2015-11-15 (292 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Hewlett-Packard HP Spectre x360 Convertible 13
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=fbb7dc63-2e63-4e68-b131-403474f09c39 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (129 days ago)
  dmi.bios.date: 06/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 802D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 58.62
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.42:bd06/22/2016:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.62:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Spectre x360 Convertible 13
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Sep  3 00:50:47 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4951 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3

[Jeremy Bicha]

Amir, if you're using Ubuntu 16.04, you can do the verification. Just
install the proposed gstreamer1.0 packages and ensure that playing audio
and videos files still works, etc.

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1522675] Re: Can't drop privileges for downloading : _apt user not allowed

[Evan Carroll]

Also getting this, re: @Chris Pollock on the same package which is now
required with the deprecation and removal of pepperflash on Oct 26.

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

Title:
  Can't drop privileges for downloading : _apt user not allowed

Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1639077] Re: unity8-dash crashed with SIGSEGV in QExplicitlySharedDataPointer from QDBusPendingCall::QDBusPendingCall from UbuntuClipboard::operator() from QtPrivate::FunctorCall

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/unity8-dash:11:QExplicitlySharedDataPointer:QDBusPendingCall::QDBusPendingCall:UbuntuClipboard:::QtPrivate::FunctorCall:QtPrivate::Functor
+ unity8-dash crashed with SIGSEGV in QExplicitlySharedDataPointer from 
QDBusPendingCall::QDBusPendingCall from UbuntuClipboard::operator() from 
QtPrivate::FunctorCall from QtPrivate::Functor

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

Title:
  unity8-dash crashed with SIGSEGV in QExplicitlySharedDataPointer from
  QDBusPendingCall::QDBusPendingCall from UbuntuClipboard::operator()
  from QtPrivate::FunctorCall from QtPrivate::Functor

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity8.  This problem was most recently seen with package version 
8.14+16.10.20160922-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/efd4a878819f23377a041dd286ddab032f9a04c2 
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/unity8/+bug/1639077/+subscriptions

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

[Touch-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

[Daniel van Vugt]

Is your backlight coming back on? If not then that part is a Mir bug.

** Project changed: mir => unity8 (Ubuntu)

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

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

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

** Tags added: multimonitor unity8-desktop

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

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

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/

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

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

[Touch-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

[Launchpad Bug Tracker]

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

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

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/

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

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

[Touch-packages] [Bug 1532944] Re: flashplugin-installer shows a warning after downloading the file with apt 1.1.x

[Evan Carroll]

How is this not an error? Getting this in 16.10. If we can't write to
the directory, why is that? We didn't do anything? Who set the perms
wrong. And, if they are wrong why does the package proceed to tell us it
worked... "Installing from local file" (when there file isn't there) and
then "Flash Plugin installed." There is nothing in that directory.
Nothing was installed. It didn't work. Status messages are not status
messages when they assume success.

Please reopen. This is a overzealous closing.

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

Title:
  flashplugin-installer shows a warning after downloading the file with
  apt 1.1.x

Status in apt package in Ubuntu:
  Invalid
Status in flashplugin-nonfree package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04 dev with apt 1.1.10 and on trying to install
  flashplugin-installer I'm always getting an error message after the
  file got downloaded. Here is an example output:

  root@ubuntu:~# apt-get install flashplugin-installer --reinstall
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    libapt-inst1.7 libapt-pkg4.16
  Use 'apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/6838 B of archives.
  After this operation, 0 B of additional disk space will be used.
  debconf: delaying package configuration, since apt-utils is not installed
  (Reading database ... 99770 files and directories currently installed.)
  Preparing to unpack .../flashplugin-installer_11.2.202.559ubuntu1_amd64.deb 
...
  Unpacking flashplugin-installer (11.2.202.559ubuntu1) over 
(11.2.202.559ubuntu1) ...
  Processing triggers for update-notifier-common (3.164) ...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20151228.1.orig.tar.gz
  Get:1 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20151228.1.orig.tar.gz
 [26.8 MB]
  Fetched 26.8 MB in 3min 8s (143 kB/s)
  W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20151228.1.orig.tar.gz'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
  Installing from local file 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20151228.1.orig.tar.gz
  Flash Plugin installed.
  Setting up flashplugin-installer (11.2.202.559ubuntu1) ...

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

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

[Touch-packages] [Bug 1638929] [NEW] after disabling a display, enabling makes screens go black

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Reproduce:
turn off then turn on some display (output.used = false then output.used = true)

What happens:
Turning off works fine, turning it back on does not

What should happen:
it should work as expected

USC log: http://pastebin.ubuntu.com/23420797/
Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/

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

-- 
after disabling a display, enabling makes screens go black
https://bugs.launchpad.net/bugs/1638929
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity8 in Ubuntu.

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

[Touch-packages] [Bug 1638565] Re: HP Envy 34c resolution maxes out at 1920x1200

[Daniel van Vugt]

Yep, Xorg.log seems to suggest the HDMI port is on the Intel output. So
possibly a duplicate of bug 1606103. Although I would not have expected
going back to kernel 4.4 would help (!?).

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

Title:
  HP Envy 34c resolution maxes out at 1920x1200

Status in xorg package in Ubuntu:
  New

Bug description:
  Using get-edid, the best resolution is "Mode 0" below, but this
  doesn't show up in the Display systems settings panel.

  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  No EDID on bus 0
  No EDID on bus 1
  No EDID on bus 2
  No EDID on bus 3
  No EDID on bus 5
  No EDID on bus 7
  No EDID on bus 8
  No EDID on bus 9
  No EDID on bus 10
  2 potential busses found: 4 6
  Will scan through until the first EDID is found.
  Pass a bus number as an option to this program to go only for that one.
  256-byte EDID successfully retrieved from i2c bus 4
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "HP ENVY 34c"
ModelName "HP ENVY 34c"
VendorName "HWP"
# Monitor Manufactured week 22 of 2015
# EDID version 1.3
# Digital Display
DisplaySize 800 330
Gamma 2.20
Option "DPMS" "true"
Horizsync 27-90
VertRefresh 24-60
# Maximum pixel clock is 250MHz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1920x1200, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1600x1200, 60Hz
#Not giving standard mode: 1280x1024, 60Hz

#Extension block found. Parsing...
Modeline"Mode 17" 241.50 2560 2608 2640 2720 1440 1443 1448 
1481 +hsync -vsync 
Modeline"Mode 0" 196.25 3440 3600 3952 4464 1440 1443 1453 1468 
+hsync -vsync 
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 
+hsync +vsync
Modeline"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 6" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 10" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 11" 74.250 1920 2008 2052 2200 1080 1082 1087 
1125 +hsync +vsync interlace
Modeline"Mode 12" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 14" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 16" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 18" 198.00 2560 2808 2852 3000 1080 1084 1089 
1100 +hsync +vsync 
Modeline"Mode 19" 185.62 2560 3108 3152 3300 1080 1084 1089 
1125 +hsync +vsync 
Modeline"Mode 20" 154.24 1920 1968 2000 2080 1200 1203 1209 
1235 +hsync -vsync 
Option "PreferredMode" "Mode 17"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  Uname: Linux 4.8.0-26-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.98  Mon Sep 19 17:31:03 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Nov  2 14:22:07 2016
  DistUpgraded: 2016-10-29 

[Touch-packages] [Bug 1638565] Re: HP Envy 34c resolution maxes out at 1920x1200

[Daniel van Vugt]

Since your system has hybrid graphics (both Intel and Nvidia GPUs) it's
unclear which monitor connectors are connected to which GPU. The answer
varies between laptop models...

If we assume the answer is that your HDMI port is connected to the Intel
GPU (which would be pretty normal) then this is a duplicate of bug
1606103.

If your HDMI is connected directly to the Nvidia GPU then that's an
Nvidia bug.

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

Title:
  HP Envy 34c resolution maxes out at 1920x1200

Status in xorg package in Ubuntu:
  New

Bug description:
  Using get-edid, the best resolution is "Mode 0" below, but this
  doesn't show up in the Display systems settings panel.

  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  No EDID on bus 0
  No EDID on bus 1
  No EDID on bus 2
  No EDID on bus 3
  No EDID on bus 5
  No EDID on bus 7
  No EDID on bus 8
  No EDID on bus 9
  No EDID on bus 10
  2 potential busses found: 4 6
  Will scan through until the first EDID is found.
  Pass a bus number as an option to this program to go only for that one.
  256-byte EDID successfully retrieved from i2c bus 4
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "HP ENVY 34c"
ModelName "HP ENVY 34c"
VendorName "HWP"
# Monitor Manufactured week 22 of 2015
# EDID version 1.3
# Digital Display
DisplaySize 800 330
Gamma 2.20
Option "DPMS" "true"
Horizsync 27-90
VertRefresh 24-60
# Maximum pixel clock is 250MHz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1920x1200, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1600x1200, 60Hz
#Not giving standard mode: 1280x1024, 60Hz

#Extension block found. Parsing...
Modeline"Mode 17" 241.50 2560 2608 2640 2720 1440 1443 1448 
1481 +hsync -vsync 
Modeline"Mode 0" 196.25 3440 3600 3952 4464 1440 1443 1453 1468 
+hsync -vsync 
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 
+hsync +vsync
Modeline"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 6" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 10" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 11" 74.250 1920 2008 2052 2200 1080 1082 1087 
1125 +hsync +vsync interlace
Modeline"Mode 12" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 14" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 16" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 18" 198.00 2560 2808 2852 3000 1080 1084 1089 
1100 +hsync +vsync 
Modeline"Mode 19" 185.62 2560 3108 3152 3300 1080 1084 1089 
1125 +hsync +vsync 
Modeline"Mode 20" 154.24 1920 1968 2000 2080 1200 1203 1209 
1235 +hsync -vsync 
Option "PreferredMode" "Mode 17"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  Uname: Linux 4.8.0-26-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.98  Mon Sep 19 17:31:03 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 

[Touch-packages] [Bug 1639017] Re: Unable to have Higher Resolution on Ubuntu 16.04

[Daniel van Vugt]

It appears Xorg is unable or unwilling to get the EDID from your monitor
over VGA...

[18.735] (II) intel(0): switch to mode 1024x768@60.0 on VGA1 using
pipe 0, position (0, 0), rotation normal, reflection none

There is no mention of it trying to find other modes.

Do you have a digital connector you can try? (DisplayPort, DVI or HDMI)

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

Title:
  Unable to have Higher Resolution on Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am only able to view the screen in 1024x768 resolution here is my
  output for lshw -c Video

*-display   
 description: VGA compatible controller
 product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:25 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  I think the xorg driver is fully updated but still I am unable to run
  in higher resolution on ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  4 00:33:25 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
  InstallationDate: Installed on 2016-10-31 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=361b7ddd-636c-40e8-98a4-6f7c6ceb1f69 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61MS
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd06/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MS:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Nov  4 00:10:15 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputUSB Optical MouseMOUSE, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Touch-packages] [Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up

[Guga]

Hello, cyphermox!

Do you think you could send your patches upstream as well?

The same bug affects Debian (http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=756633) and, probably, the source packages. It's
sad seeing this fixed in Ubuntu only.

Thanks!

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

Title:
  Delay during PXE Boot, IP-Config gives up

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Released
Status in klibc source package in Wily:
  Won't Fix
Status in klibc source package in Xenial:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  [Impact]
  PXE booting users with live images or other minimal setups using klibc-utils.

  [Test case]
  Attempt to PXE boot using Ubuntu live images; see below for details.

  [Regression potential]
  This forces the yiaddr (client requested/current IP) to be set to 0 when 
sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, 
which should typically only happen when there is no IP set on the device and it 
is otherwise unable to receive unicast (on account of not being configured). 
Should there be a need to send other messages which would require setting the 
yiaddr value to the current configured IP address, a naive change would break. 
The yiaddr variable would need to be adjusted to pull value from a new 
location, or initialized directly by the callers to dhcp_send() where the 
business logic would reside.

  ---

  Attempting to PXE boot both the 12.04.3 and 14.04 Live images.   PXE
  boot works normally (PXE Menu, select desired image, image begins
  loading), then the boot process hangs while IP-Config attempts to get
  an IP address:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 3 secs - giving up

  These lines appear very quickly (5 seconds has NOT elapsed), after
  about a minute, we get this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 4 secs - giving up

  Some time later, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 6 secs - giving up

  Until finally, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 9 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: eth0 guessed broadcast address 172.25.11.31
  IP-Config: eth0 complete (dhcp from 172.25.10.20):
  (snip)

  While watching the DHCP server logs, Ubuntu is either not sending a
  DHCP Discover at times, or is not replying back with a DHCPRequest
  during these sessions, presumably ignoring an response from the DHCP
  server.  From the initial booting of the system via PXE, to when
  Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.

  I am seeing this same behavior on both 12.04.3 and 14.04.  After
  finding a number of similar erros via Google and no real resolution, I
  have opened this bug.

  The system experiencing this issue has multiple ethernet interfaces
  (actual HW, not a VM), some Google found solutions suggest hard coding
  DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
  acceptable as a system attempting to PXE boot may be using an
  alternate port for the network.

  I have found what looks to be a very similar bug filed for Debian,
  #584583, which also contains a patch for this issue (under Debian).

  I have no problems in PXE booting to various Windows, RedHat, Centos,
  or Fedora OSs.  Ubuntu is the only Live OS that I'm attempting to boot
  at present.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jun  6 20:22:09 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably 

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

[Jarno Suni]

Julian, it protects the kernel currently booted at the time of running
/etc/kernel/postinst.d/apt-auto-removal. If you later boot another
kernel that is not protected, it may be removed. Not a likely case,
though.

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  New

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

[Guga]

Hello, cyphermox!

Do you think you could send your patches upstream as well?

The same bug affects Debian (http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=756633) and, probably, the source packages. It's
sad seeing this fixed in Ubuntu only.

Thanks!

** Bug watch added: Debian Bug tracker #756633
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633

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

Title:
  Wrong bit set in klibc PXE dhcp/bootp flags

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Committed
Status in klibc source package in Xenial:
  Fix Released
Status in klibc source package in Yakkety:
  Fix Released

Bug description:
  [Description]

  The patch for bug 1327412 set the wrong bit in the bootp flags field.
  It set flags to 0x800, but the correct value is 0x8000.  That sets the
  "broadcast" bit, and the spec requires all other bits to be 0.

  Setting one of the "must be zero" bits in the flags field causes some
  DHCP relay agents to drop the packets, causing PXE to fail.

  [Test Case]

  Get a DHCP relay agent that drops PXE packets with an invalid
  bootp.flags bit set, and try to PXE boot; it fails.

  [Regression]

  None, the previous patch introduced this regression.

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

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

[Touch-packages] [Bug 1639097] [NEW] Clicking on the "Installing Software" window's "Close" (X) gadget hangs gdebi

[Scott Cowles Jacobs]

Public bug reported:

When gdebi is installing or removing software, an "Installing Software" window 
pops up.
When it is finished, instead of clicking on the "Close" button, I keep 
forgetting and
click on the window's "Close" gadget instead.
The window disappears, but the main window does not recover.
The buttons are greyed out, and the main window's "Close" gadget is 
non-functional.

I have to keep using htop in a terminal to kill (SIGTERM) gdebi's
process.

One expects using the window's "Close" gadget will accomplish the same thing as 
clicking the
"Close" button, but it does not.


scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 
14:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc
Ubuntu 16.10
yakkety
scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
Lubuntu
scott@scott-ASUS-M2N68-AM-PLUS:~$ gdebi --version
0.9.5.7ubuntu1



ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gdebi 0.9.5.7ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: LXDE
Date: Thu Nov  3 20:34:44 2016
InstallationDate: Installed on 2016-10-20 (15 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Clicking on the "Installing Software" window's "Close" (X) gadget
  hangs gdebi

Status in gdebi package in Ubuntu:
  New

Bug description:
  When gdebi is installing or removing software, an "Installing Software" 
window pops up.
  When it is finished, instead of clicking on the "Close" button, I keep 
forgetting and
  click on the window's "Close" gadget instead.
  The window disappears, but the main window does not recover.
  The buttons are greyed out, and the main window's "Close" gadget is 
non-functional.

  I have to keep using htop in a terminal to kill (SIGTERM) gdebi's
  process.

  One expects using the window's "Close" gadget will accomplish the same thing 
as clicking the
  "Close" button, but it does not.

  
  scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
  Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 
14:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc
  Ubuntu 16.10
  yakkety
  scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
  Lubuntu
  scott@scott-ASUS-M2N68-AM-PLUS:~$ gdebi --version
  0.9.5.7ubuntu1

  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Nov  3 20:34:44 2016
  InstallationDate: Installed on 2016-10-20 (15 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1635906] Re: Low graphics mode in multi monitor setup after upgrade to 16.10

[isotope]

Hi Paolo.

Glad to hear you managed to resolve the issue! Did not work for me
though. Also there seems to be some progress done. I tried fresh install
with downloading latest updates and this time it went as far as splash
screen on both external monitors, but then all the same. Flickering and
eventually bumping to low graphics mode.

Regards,
Vadim.

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

Title:
  Low graphics mode in multi monitor setup after upgrade to 16.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  After upgrading from 16.04 to 16.10 my multi monitor setup is unable to reach 
login screen. Computer is Panasonic CF-52 on dock station with two external 
monitors. The error says low graphics mode enabled.Used to work just fine in 
previous distributions. the last error in the log file says: ScreenInit failed 
for driver 0. I have Intel graphics. 

  Workaround found so far: boot laptop out of dock station, then dock it
  and monitors are recognized no problem.

  Troubleshooting done:
  Reintsall Ubuntu from thumb drive - reinstall option: same results
  Reinstall Ubuntu from thumb drive - clean install except for /home drive 
kept: same results
  Run X -configure: same results

  Regards,
  isotope

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Oct 22 18:47:00 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
  InstallationDate: Installed on 2016-10-22 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-52GCMBSAE
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=54989005-afb3-4eb2-9813-17ee5bf134c2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.50L20
  dmi.board.name: CF52-2L
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.50L20:bd03/27/2009:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-52GCMBSAE:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF52-2L:rvr1:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-52GCMBSAE
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.
  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
  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: Sat Oct 22 17:49:03 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   OutputDP-1DP-2
DP-3  HDMI-1  HDMI-2  LVDS-1   VGA-1 
   product id   
17709 
   vendor 
VSC
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1631236] Re: Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Posted first about this issue at
  https://ubuntuforums.org/showthread.php?t=2339198

  Pasted post below:

  "I installed Ubuntu 16.04 Desktop alongside Windows 10 Home on a Dell
  Inspiron 15-7559 with an Nvidia 960m card and embeded Intel Skylake
  graphics.

  When I first installed Ubuntu and attempted to boot, the display would
  freeze on the Ubuntu splash screen after entering my disk password.
  Strangely, by removing "quiet" and "splash" from my grub configuration
  during my next boot, I was able to finally boot to the login screen
  and access the desktop. I installed the Intel and Nvidia drivers in
  the "Additional Drivers" app and now I can boot to the login screen
  with no issues.

  Now, when closing the laptop lid to suspend the system, it resumes to
  a blank screen and I can't get it to recover from this state without
  holding the power button to force shutdown. I verified that it is a
  display issue because I was able to ssh into the machine while it had
  the blank screen.

  I was able to install and boot into the latest (4.8) mainline kernel,
  which also gave me a warning/error because of my installed proprietary
  drivers. I tried uninstalling the Nvidia drivers to see if Nouveau had
  been fixed/improved, but the previous splash screen freeze returned; I
  was able to reinstall the drivers by booting into 4.8 recovery mode
  and using the Failsafe graphics mode to reinstall the Nvidia drivers.

  Any help on getting Nouveau to work nicely with the 960m so I don't
  have to run proprietary drivers or solve the suspend issue?"

  Now, I sometimes cannot shutdown properly without getting warnings
  about cpu soft lockups from gpu-manager. I also get these when I boot
  without nvidia drivers with "quiet" and "splash" options removed from
  my grub config.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Oct  6 20:47:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-040800-generic, x86_64: installed
   nvidia-361, 361.42: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2016-09-29 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-040800-generic 
root=UUID=7dd53585-5dcb-4071-a47a-d1a7fede0e3f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd11/05/2015:svnDellInc.:pnInspiron7559:pvr1.1.3:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 

[Touch-packages] [Bug 1631236] Re: Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

[Jimmy Pan]

I can never boot with the nvidia drivers. For the latest nvidia-367.75
in the repo, neither. This time, after the boot info shows up, it just
leaved a blinking cursor for a while and then the screen completely went
black.

Without the nvidia driver, it cannot shutdown right. But looks like the
problem is getting better now, I sometimes don't need to press the
powerbutton to shutdown.

This looks like the gtx 960m problem since I found other users not only
on dell 7559 have the problem.

Anyway, hope this problem can be fix soon.

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

Title:
  Xorg freeze with Nvidia 960m on Dell Inspiron 15-7559

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Posted first about this issue at
  https://ubuntuforums.org/showthread.php?t=2339198

  Pasted post below:

  "I installed Ubuntu 16.04 Desktop alongside Windows 10 Home on a Dell
  Inspiron 15-7559 with an Nvidia 960m card and embeded Intel Skylake
  graphics.

  When I first installed Ubuntu and attempted to boot, the display would
  freeze on the Ubuntu splash screen after entering my disk password.
  Strangely, by removing "quiet" and "splash" from my grub configuration
  during my next boot, I was able to finally boot to the login screen
  and access the desktop. I installed the Intel and Nvidia drivers in
  the "Additional Drivers" app and now I can boot to the login screen
  with no issues.

  Now, when closing the laptop lid to suspend the system, it resumes to
  a blank screen and I can't get it to recover from this state without
  holding the power button to force shutdown. I verified that it is a
  display issue because I was able to ssh into the machine while it had
  the blank screen.

  I was able to install and boot into the latest (4.8) mainline kernel,
  which also gave me a warning/error because of my installed proprietary
  drivers. I tried uninstalling the Nvidia drivers to see if Nouveau had
  been fixed/improved, but the previous splash screen freeze returned; I
  was able to reinstall the drivers by booting into 4.8 recovery mode
  and using the Failsafe graphics mode to reinstall the Nvidia drivers.

  Any help on getting Nouveau to work nicely with the 960m so I don't
  have to run proprietary drivers or solve the suspend issue?"

  Now, I sometimes cannot shutdown properly without getting warnings
  about cpu soft lockups from gpu-manager. I also get these when I boot
  without nvidia drivers with "quiet" and "splash" options removed from
  my grub config.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Oct  6 20:47:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-040800-generic, x86_64: installed
   nvidia-361, 361.42: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2016-09-29 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-040800-generic 
root=UUID=7dd53585-5dcb-4071-a47a-d1a7fede0e3f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 

[Touch-packages] [Bug 1638922] Re: [needs-packaging] tar : CVE-2016-6321 not patched in stable

[Brian Murray]

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- tar : CVE-2016-6321 not patched in stable
+ [needs-packaging] tar : CVE-2016-6321 not patched in stable

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

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

Title:
  [needs-packaging] tar : CVE-2016-6321 not patched in stable

Status in tar package in Ubuntu:
  New

Bug description:
  CVE-2016-6321 path name extract bypass vulnerability is not patched in
  stable releases of yakkety, xenial and other supported releases.

  The maintainer appears to have only pushed the patch to zesty
  proposed.

  Please push the patch for the stable releases as this bug could have
  seroius implications in certain environments.

  Upstream debian has already pushed the patch to stable.

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842339

  https://people.canonical.com/~ubuntu-
  security/cve/2016/CVE-2016-6321.html

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

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

[Touch-packages] [Bug 1639085] [NEW] package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

[Andrey Lelikov]

Public bug reported:

14.04 -> 16.04 upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.133-1ubuntu10
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov  3 18:09:59 2016
ErrorMessage: subprocess new pre-installation script returned error exit status 
2
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: lvm2
Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 2
UpgradeStatus: Upgraded to xenial on 2016-11-03 (0 days ago)

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


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

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

Title:
  package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess
  new pre-installation script returned error exit status 2

Status in lvm2 package in Ubuntu:
  New

Bug description:
  14.04 -> 16.04 upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov  3 18:09:59 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: lvm2
  Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-11-03 (0 days ago)

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

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

[Touch-packages] [Bug 1639077] [NEW] /usr/bin/unity8-dash:11:QExplicitlySharedDataPointer:QDBusPendingCall::QDBusPendingCall:UbuntuClipboard:::QtPrivate::FunctorCall:QtPrivate::Functor

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity8.  This problem was most recently seen with package version 
8.14+16.10.20160922-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/efd4a878819f23377a041dd286ddab032f9a04c2 
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: unity8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid yakkety

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

Title:
  
/usr/bin/unity8-dash:11:QExplicitlySharedDataPointer:QDBusPendingCall::QDBusPendingCall:UbuntuClipboard:::QtPrivate::FunctorCall:QtPrivate::Functor

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity8.  This problem was most recently seen with package version 
8.14+16.10.20160922-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/efd4a878819f23377a041dd286ddab032f9a04c2 
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/unity8/+bug/1639077/+subscriptions

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

[Touch-packages] [Bug 1637032] Re: The screen keeps flashing (even in text terminal mode)

[Poldi]

As I indicated in the original post, the problem also occurs when booting from 
the LiveCD.
Not sure what additional info to provide, so have attached a few files I 
thought may be important.

Pretty much stuck here as the only option right now seems to be be to go back 
to 16.04.
Thanks

** Attachment added: "LiveCDLogs.zip"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637032/+attachment/4772096/+files/LiveCDLogs.zip

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

Title:
  The screen keeps flashing (even in text terminal mode)

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 the screen (Desktop and Terminal)flashes
  intermittently making the system unusable.

  I get the same behaviour when booting 16.10 from the LiveCD

  Booting with the 4.4.0 Kernel still works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Oct 27 11:56:38 2016
  InstallationDate: Installed on 2015-02-15 (619 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-10-24 (2 days ago)
  VarLogDistupgradeAptlog: Error: [Errno 13] Permission denied: 
'/var/log/dist-upgrade/apt.log'
  VarLogDistupgradeMainlog: Error: [Errno 13] Permission denied: 
'/var/log/dist-upgrade/main.log'

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

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

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

[Mathieu Trudel-Lapierre]

d) is "unavoidable" if we're do make use of ROUNDTTT, and to be frank,
seems like a reasonable side-effect. There's only so much that can be
done to handle both IPv4 and IPv6 in the initramfs, and I think we can
live we a few extra seconds booting. Furthermore, systems that do not
get their IP addresses in the first few seconds probably deserve a good
revision -- it is likely happening due to suboptimal network
configuration (you shouldn't have to wait multiple seconds for the DHCP
server to respond). In the case where there is no IPv4 available, it
won't change the end result -- the system will still fail to boot, it
will just take longer doing so (and on IPv6-only, people should set
ip=off explicitly, and that use case was not previously supported).

In the context of an SRU, it seems like a better deal to cause things to
take a little longer in the less used, deprecated method of using
ipconfig than to change ipconfig parameters in a way that might cause
other issues (reducing the timeout generally, and using the sleep
"alone" means systems that are genuinely slow might fail completely for
no good reason. Making the timeout 2 seconds every time would yield to
such an effect; whereas making the timeout 30 every time would lead to a
substantial delay in bringing up the network if the first tries fail).

b) I haven't seen a proper use case where this was important. There
isn't straightforward way to set the hostname request for dhclient; and
properly configuring the DHCP server would get you the right hostname.
Furthermore, the hostname in use when enlisting or deploying MAAS
systems should not matter, as it's the kind of information that should
be written out to the final system (and doesn't matter on ephemeral,
"get how many disks this machine has" instances -- the hostname there is
already known and set by MAAS).

a) A valid concern, but let's focus on making things work at all before
optimizing. This should be verified in the devel release before a SRU.

c) I don't know what it will do; it will need to be properly watched in
SRUs and the devel release. My initial testing shows absolutely no
adverse effects.

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

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

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  In Progress
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  In Progress
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  In Progress
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  In Progress
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) 

  
  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1639068] [NEW] package libllvm3.4 1:3.4-1ubuntu3 failed to install/upgrade: 62.069:package is in a very bad inconsistent state; you should reinstall it before attempting configu

[David Wassell]

Public bug reported:

just locks up

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libllvm3.4 1:3.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Nov  4 11:13:12 2016
DuplicateSignature: package:libllvm3.4:1:3.4-1ubuntu3:62.069:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: 62.069:package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-11-03 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.15
SourcePackage: llvm-toolchain-3.4
Title: package libllvm3.4 1:3.4-1ubuntu3 failed to install/upgrade: 
62.069:package is in a very bad inconsistent state; you should  reinstall it 
before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: llvm-toolchain-3.4 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package libllvm3.4 1:3.4-1ubuntu3 failed to install/upgrade:
  62.069:package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  just locks up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libllvm3.4 1:3.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Nov  4 11:13:12 2016
  DuplicateSignature: package:libllvm3.4:1:3.4-1ubuntu3:62.069:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: 62.069:package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: llvm-toolchain-3.4
  Title: package libllvm3.4 1:3.4-1ubuntu3 failed to install/upgrade: 
62.069: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/llvm-toolchain-3.4/+bug/1639068/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

Given my above experiences, and given that you do have elpais installed
and it may be enabled in your Today scope (can't see from your settings
image in comment #7), can you please:

Ensure that El Pais and holidays scopes are DISABLED in today scope
settings, and see if you can reproduce this? (if you have the twitter
scope installed, disable that too).

Thanks for your patience!

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1637801] Re: Incorrect Russian translation of "apt list --upgradeable" results

[Julian Andres Klode]

The correct approach is to have gettext look into the langpack
translations first, and then fall back to the package's translations.
That's also the way it was explained to work: Packages ship initial
translations for bootstrapping purposes, and those can be updated via
language packs.

I have no intention to ship translations from Launchpad in apt. That
would mean diverging from the upstream packaging, which I have no
intention to, I'm happy we got that working without a diff now. If
people want to help with the translations apt ships, they can do that
_upstream_ (talk to the previous translators, and take over if they
don't respond).

That said, even if I wanted to, merging the translations from launchpad
would be a pain in the ass:

First of all, the translation templates are not remotely up-to-date
(only since 1.3 there's a chance for Launchpad to import them, previous
versions only had templates without any of the headers). Thus, Xenial
does not have templates suitable for the apt version it ships with, but
rather for 1.0something or similar.

Secondly, the translation templates in launchpad are the split ones -
APT's build system requires a merged translation file of all domains.

What we can do, if neccessary, is fix translations in the stable
branches for strings not in master. But that really needs review by the
appropriate channels upstream as well. And especially for 17.04 and
17.10 - those will get the same release series as the next Debian stable
release. For Ubuntu-only branches, we can probably relax the
translation-ML-must-review requirement, but it seems a bit rude.

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

Title:
  Incorrect Russian translation of "apt list --upgradeable" results

Status in Ubuntu Translations:
  Invalid
Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  bor@bor-Latitude-E5450:~$ apt list --upgradeable
  Вывод списка… Готово
  build/неизвестно 20161025 all [может быть обновлён до: 20151105]

  In Russian this means "version 20161025 can be upgraded TO version
  20151105)

  While original English says exactly opposite:

  bor@bor-Latitude-E5450:~$ LC_ALL=C LANG=C apt list --upgradeable
  Listing... Done
  build/unknown 20161025 all [upgradable from: 20151105]

  Literal translation (that does not require serious phrase change)
  would probably be

  "может быть обновлен с"

  although it sounds also artificial, as in Russian subject is package
  that is being updated (currently installed), not new version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 30 09:39:47 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-07-02 (485 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-10-29 (0 days ago)

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

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

[Touch-packages] [Bug 1618364] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar

[Launchpad Bug Tracker]

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

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

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com
  dependências - a deixar triggers por processar

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from xenial to yakkety

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 30 09:34:31 2016
  ErrorMessage: problemas com dependências - a deixar triggers por processar
  InstallationDate: Installed on 2016-02-15 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com 
dependências - a deixar triggers por processar
  UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago)

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

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

[Touch-packages] [Bug 1405627] Re: Suspending while a program is fullscreen

[Nikita Yerenkov-Scott]

This issue is no longer present on trusty.

** Tags removed: trusty

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

** Changed in: ubuntu-gnome
   Status: Confirmed => 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/1405627

Title:
  Suspending while a program is fullscreen

Status in Ubuntu GNOME:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have found that my system initiates suspend and goes to sleep when
  the keyboard and mouse are inactive for the specified amount of time,
  and this is all very well. However it does it regardless of whether or
  not an application is fullscreen, and it would be preferable at least
  for me if this didn't happen. It doesn't happen on Xenial, but it does
  on Trusty (I originally reported here for Utopic). I haven't tested it
  on any other versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec 25 13:17:17 2014
  DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5002]
  InstallationDate: Installed on 2014-12-06 (19 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 62742SG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-12-13 (11 days ago)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H5ET69WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 62742SG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK IPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 62742SG
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Dec 25 11:51:51 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 827
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1.2

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

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

[Touch-packages] [Bug 1624641] Re: security updates with a new dependency don't get installed

[xtsbdu3reyrbrmroezob]

Still present, or new issue due to the changes?

"""
$ apt-cache policy unattended-upgrades
unattended-upgrades:
  Installed: 0.92ubuntu1
"""

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

Title:
  security updates with a new dependency don't get installed

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Yakkety:
  Fix Released

Bug description:
  Test Case
  -
  1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed
  2) Install the release version of chromium browser e.g. "sudo apt-get install 
chromium-browser=49.0.2623.108-0ubuntu1.1233 
chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 
chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233"
  3) Run apt-get update if you didn't already
  4) Run "sudo /usr/bin/unattended-upgrades -v -d"
  5) Observe the following output "Checking: chromium-browser ([, ])
  pkg 'libspeechd2' not in allowed origin
  sanity check failed"

  With the version of unattended-upgrades from -proposed libspeechd2
  should be from an allowed origin and chromium-browser will get
  updated.

  Regression Potential
  
  This change modifies the behavior of unattended-upgrades such that new 
packages will be installed on a user's system and they may not except such 
behavior (e.g. why was libspeechd2 insalled?).  However, this seems better than 
not installing security updates and leaving people's systems vulnerable to 
attack.

  Original Description
  
  E.g. chromium-browser has an update, but U-U does not update it. I saw in 
update-manager that the security update is available before running U-U. 
Afterwards I can install the update by update-manager.

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:13:40 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: allSourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624641] Re: security updates with a new dependency don't get installed

[xtsbdu3reyrbrmroezob]

This is a regression. I tested latest updates and still having issues,
albeit slightly different. Not sure if exactly the same bug and not sure
if this is really a duplicate, as currently linked. But it should be
checked out.

Bug #1638561

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

Title:
  security updates with a new dependency don't get installed

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Yakkety:
  Fix Released

Bug description:
  Test Case
  -
  1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed
  2) Install the release version of chromium browser e.g. "sudo apt-get install 
chromium-browser=49.0.2623.108-0ubuntu1.1233 
chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 
chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233"
  3) Run apt-get update if you didn't already
  4) Run "sudo /usr/bin/unattended-upgrades -v -d"
  5) Observe the following output "Checking: chromium-browser ([, ])
  pkg 'libspeechd2' not in allowed origin
  sanity check failed"

  With the version of unattended-upgrades from -proposed libspeechd2
  should be from an allowed origin and chromium-browser will get
  updated.

  Regression Potential
  
  This change modifies the behavior of unattended-upgrades such that new 
packages will be installed on a user's system and they may not except such 
behavior (e.g. why was libspeechd2 insalled?).  However, this seems better than 
not installing security updates and leaving people's systems vulnerable to 
attack.

  Original Description
  
  E.g. chromium-browser has an update, but U-U does not update it. I saw in 
update-manager that the security update is available before running U-U. 
Afterwards I can install the update by update-manager.

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:13:40 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: allSourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638561] Re: unattended-upgrade fails to apply security updates if the update is also in another suite suffix component, such as yakkety-updates

[xtsbdu3reyrbrmroezob]

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

Still present, or new issue due to the changes?

"""
$ apt-cache policy unattended-upgrades
unattended-upgrades:
  Installed: 0.92ubuntu1
"""

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

Title:
  unattended-upgrade fails to apply security updates if the update is
  also in another suite suffix component, such as yakkety-updates

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  As you can see below, the packages have security updates which are not
  being applied, presumably because the security updates are not only in
  yakkety-security, but also in yakkety-updates. This is a bug and
  leaves systems vulnerable that are expecting unattended-upgrades to
  apply the patches (it fails to do so).

  """
  # apt list --upgradable 2>/dev/null | grep yakkety-security
  liboxideqt-qmlplugin/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtcore0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtquick0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  oxideqt-codecs/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 amd64 
[upgradable from: 1.17.9-0ubuntu1]
  # unattended-upgrade --dry-run -v  
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=yakkety-security']
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: 
  
  """

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

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

[Touch-packages] [Bug 1638561] Re: unattended-upgrade fails to apply security updates if the update is also in another suite suffix component, such as yakkety-updates

[xtsbdu3reyrbrmroezob]

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

This is a regression. I tested latest updates and still having issues,
albeit slightly different. Not sure if exactly the same bug and not sure
if this is really a duplicate, as currently linked. But it should be
checked out.

bug #1624641

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

Title:
  unattended-upgrade fails to apply security updates if the update is
  also in another suite suffix component, such as yakkety-updates

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  As you can see below, the packages have security updates which are not
  being applied, presumably because the security updates are not only in
  yakkety-security, but also in yakkety-updates. This is a bug and
  leaves systems vulnerable that are expecting unattended-upgrades to
  apply the patches (it fails to do so).

  """
  # apt list --upgradable 2>/dev/null | grep yakkety-security
  liboxideqt-qmlplugin/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtcore0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtquick0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  oxideqt-codecs/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 amd64 
[upgradable from: 1.17.9-0ubuntu1]
  # unattended-upgrade --dry-run -v  
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=yakkety-security']
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: 
  
  """

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

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

twice now with elpais and holidays disabled in Today during refresh I
walked out of wifi range and *expected* resulted displayed [1]. Display
was not limited to Day scope.

Possibility: these child scopes do not handle loss of network during
refresh correctly. They should simply return from the run() method.

Does the unity::scopes::QueryMetadata::ConnectivityStatus [2] update
dynamically during a scope run() exuction, or does it just have a value
that was correct when first passed to the scope?

[1] there was also a twitter scope panic. I filed this bug for that:
https://bugs.launchpad.net/twitter-scope/+bug/1639056

[2]
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.4/unity.scopes.QueryMetadata/#a20eb916661728a7d9c00485e28f88701

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1619183] Re: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instan

[Flames_in_Paradise]

** Tags added: third-party-packages

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

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

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

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade:
  intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que
  es distinto de otras instancias del paquetes libqtcore4:i386

Status in One Hundred Papercuts:
  Confirmed
Status in qt4-x11 package in Ubuntu:
  Confirmed
Status in skype package in Ubuntu:
  Confirmed

Bug description:
  Trying to install skype with i386 support, breaks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  1 10:47:14 2016
  ErrorMessage: intentando sobreescribir el compartido 
`/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes 
libqtcore4:i386
  InstallationDate: Installed on 2016-07-06 (57 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es 
distinto de otras instancias del paquetes libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Treviño]

I'm not sure if that has happened because the fix was marked as
released, however maybe something changed in gtk, but this change is
just something right to do, and I'd like to backport it to 16.04, thus
the need of fixing it in both.

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  New

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

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

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

[Touch-packages] [Bug 1522988] Re: stdout and stderr are not synced on lines

[Sworddragon]

If I remember correctly the broken error messages were the one from this
issue ( https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1524196 ) as
they appeared around the same time.

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

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

Title:
  stdout and stderr are not synced on lines

Status in apt package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04 dev with apt 1.1.3 and I'm noticing that for
  example if on executing "apt-get update" error messages are shown they
  are often broken. They are missing sometimes characters which seem to
  be splitted across multiple lines. It looks that apt doesn't ensure
  writing complete lines if stdout and stderr are used.

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

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

[Touch-packages] [Bug 1637801] Re: Incorrect Russian translation of "apt list --upgradeable" results

[Gunnar Hjalmarsson]

I talked with Martin Pitt, who let me know that it's intentional
behavior that gettext gives precedence to /usr/share/locale over
/usr/share/locale-langpack.

apt is one of those 'special' packages in main where the translations
shipped with the source package are not stripped at build time. It means
that the apt.mo files installed by the language packs are not effective
(as we have already figured out). So in case of apt (and a few other
special packages) translation updates need to go into the package to
make a difference to the users.

@Julian: The Xenial template in Launchpad seems to have been updated
2016-03-25 (attached). The easiest (I think) way to get the actual
translations is to download them from Launchpad, and simply replace the
PO files in the package.

https://translations.launchpad.net/ubuntu/xenial/+source/apt/+pots/apt

There shouldn't be a need to manually merge as you described. (Possibly
I have missed something.)

** Attachment added: "build_po_apt.pot"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1637801/+attachment/4772060/+files/build_po_apt.pot

** No longer affects: gettext (Ubuntu)

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

Title:
  Incorrect Russian translation of "apt list --upgradeable" results

Status in Ubuntu Translations:
  Invalid
Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  bor@bor-Latitude-E5450:~$ apt list --upgradeable
  Вывод списка… Готово
  build/неизвестно 20161025 all [может быть обновлён до: 20151105]

  In Russian this means "version 20161025 can be upgraded TO version
  20151105)

  While original English says exactly opposite:

  bor@bor-Latitude-E5450:~$ LC_ALL=C LANG=C apt list --upgradeable
  Listing... Done
  build/unknown 20161025 all [upgradable from: 20151105]

  Literal translation (that does not require serious phrase change)
  would probably be

  "может быть обновлен с"

  although it sounds also artificial, as in Russian subject is package
  that is being updated (currently installed), not new version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 30 09:39:47 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-07-02 (485 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-10-29 (0 days ago)

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

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

ok, with holiday scope disabled, I walk out of wifi range while a today scope 
refresh is ongoing and I get similar results:
* only the Day scope displays
* but this time a different child scope displays the TimeoutExecption: elpais

[2016-11-03 17:12:03.323] ERROR:
com.canonical.scopes.dashboard_dashboard: QueryBase::run():
unity::scopes::TimeoutException: Request timed out after 500
milliseconds (endpoint =
ipc:///run/user/32011/zmq/priv/com.canonical.elpais_ELPAIS, op =
debug_mode)

again, restarting scope-registry fixes today scope.

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history - patch

[Nikita Yerenkov-Scott]

I have tested the packages from -proposed on both Trusty and Xenial and
I can confirm that they both solve the problem with no currently
noticeable regressions.

The package versions I tested were:

- Xenial: 0.6.40-2ubuntu11.3
- Trusty: 0.6.35-0ubuntu7.3

I tested the Xenial one in an Ubuntu GNOME 16.04.1 (GNOME 3.18) 64-bit
VM, and I tested the Trusty one in an Ubuntu (Unity) 14.04.5 64-bit VM.

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

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

by the way, issuing "restart scope-registry" brings holidays scope back
to life and fixes the today scope on refresh.

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

Noting the TimeoutException on holidays scope above, I've tried
launching holidays from Manage page. No results display.

running holidays scope from command line with scope-data tool I get this with 
no displayed results:
phablet@ubuntu-phablet:~$ ./scope-data com.canonical.scopes.holidays_holidays 
--results
unity::scopes::TimeoutException: Request timed out after 500 milliseconds 
(endpoint = 
ipc:///run/user/32011/zmq/priv/com.canonical.scopes.holidays_holidays, op = 
debug_mode)

I will now try reproducing the Today scope bug with Holidays scope
disabled.

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)

[Launchpad Bug Tracker]

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

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

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

Title:
  Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I can not ssh to any host with Turkish locales.

  What I expected to happen:

  I expected that 'ssh some_host' command would successfully run.

  What actually happened

  'ssh some_host' command failed with an error.

  Steps to produce:

  1. Open a terminal
  2. Run LANG=tr_TR.UTF-8 ssh some_host

  If I run ssh with tr_TR.UTF-8 locale, the first error I get is:

  $HOME/.ssh/config: line 7: Bad configuration option: Identityfile
  $HOME/.ssh/config: terminating, 1 bad configuration options

  If I commend IdentityFile option from $HOME/.ssh/config file and re-
  run the command, I get this:

  debug1: Reading configuration data ~/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  /etc/ssh/ssh_config: line 55: Bad configuration option: 
gssapIauthentication
  /etc/ssh/ssh_config: line 56: Bad configuration option: 
gssapIdelegatecredentials
  /etc/ssh/ssh_config: terminating, 2 bad configuration options

  If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials
  option, I can ssh to a host.

  So to ssh to a host with tr_TR.UTF-8 locale, one must commend out
  IdentityFile, if it is used, GSSAPIAuthentication and
  GSSAPIDelegateCredentials optons.

  Workaround:

  LC_ALL=C ssh some_host

  
  LC_ALL=C apt-cache policy openssh-client
  openssh-client:
Installed: 1:7.3p1-1
Candidate: 1:7.3p1-1
Version table:
   *** 1:7.3p1-1 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  LC_ALL=C lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: openssh-client 1:7.3p1-1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 19:37:35 2016
  InstallationDate: Installed on 2016-10-23 (9 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1639050] [NEW] Wrong package section, should be in "introspection"

[Michael Biebl]

Public bug reported:

Packages shipping gobject introspection should be in the dedicated
section "introspection". This archive section was added a while ago, see
also the corresponding entry in the debian policy 3.9.3.0:

2.6. Version 3.9.3.0


 Released February, 2012.

 2.4
  New archive sections _education_, _introspection_, and
  _metapackages_ added.


Packages shipping gobject introspection should be named 
gir1.2-NAMESPACE-VERSION.

Based on the output of apt-cache, the following packages are in the
wrong section. I didn't file a separate bug for all of them. I would
appreciate if you can adjust the archive section for all the following
packages in one go.

#!/bin/bash

while read pkg ; do
   apt-cache show $pkg | grep Section | grep -v introspection -q && echo 
$pkg
done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' )


gir1.2-accounts-1.0
gir1.2-accountsservice-1.0
gir1.2-appindicator-0.1
gir1.2-appindicator3-0.1
gir1.2-atk-1.0
gir1.2-atspi-2.0
gir1.2-bamf-3
gir1.2-cheese-3.0
gir1.2-clutter-1.0
gir1.2-cogl-1.0
gir1.2-coglpango-1.0
gir1.2-colord-1.0
gir1.2-dbusmenu-glib-0.4
gir1.2-dbusmenu-gtk-0.4
gir1.2-dbusmenu-gtk3-0.4
gir1.2-dee-1.0
gir1.2-ebook-1.2
gir1.2-edataserver-1.2
gir1.2-fcitx-1.0
gir1.2-freedesktop
gir1.2-gconf-2.0
gir1.2-gdata-0.0
gir1.2-gdesktopenums-3.0
gir1.2-gdkpixbuf-2.0
gir1.2-gkbd-3.0
gir1.2-glib-2.0
gir1.2-gmenu-3.0
gir1.2-gnomebluetooth-1.0
gir1.2-gnomedesktop-3.0
gir1.2-goa-1.0
gir1.2-gtk-2.0
gir1.2-gtk-3.0
gir1.2-gtkclutter-1.0
gir1.2-gtksource-3.0
gir1.2-gtop-2.0
gir1.2-gucharmap-2.90
gir1.2-gudev-1.0
gir1.2-gweather-3.0
gir1.2-hud-2
gir1.2-hud-client-2
gir1.2-ido3-0.1
gir1.2-json-1.0
gir1.2-lightdm-1
gir1.2-messagingmenu-1.0
gir1.2-nautilus-3.0
gir1.2-networkmanager-1.0
gir1.2-notify-0.7
gir1.2-packagekitglib-1.0
gir1.2-pango-1.0
gir1.2-peas-1.0
gir1.2-polkit-1.0
gir1.2-rb-3.0
gir1.2-rest-0.7
gir1.2-rest-extras-0.7
gir1.2-rsvg-2.0
gir1.2-signon-1.0
gir1.2-soup-2.4
gir1.2-telepathyglib-0.12
gir1.2-timezonemap-1.0
gir1.2-totem-1.0
gir1.2-totem-plparser-1.0
gir1.2-unity-5.0
gir1.2-upowerglib-1.0
gir1.2-wnck-3.0
gir1.2-evince-3.0
gir1.2-geocodeglib-1.0
gir1.2-libertine
gir1.2-nmgtk-1.0
gir1.2-ubuntu-app-launch-2
gir1.2-anjuta-3.0
gir1.2-atril
gir1.2-caja
gir1.2-caribou-1.0
gir1.2-champlain-0.12
gir1.2-cryptui-0.0
gir1.2-diodon-1.0
gir1.2-eom
gir1.2-evd-0.1
gir1.2-folks-0.6
gir1.2-gdl-3
gir1.2-gssdp-1.0
gir1.2-gtk-vnc-2.0
gir1.2-gtkchamplain-0.12
gir1.2-gupnp-1.0
gir1.2-gupnp-av-1.0
gir1.2-gupnpigd-1.0
gir1.2-indicate-0.7
gir1.2-itl-1.0
gir1.2-keybinder-3.0
gir1.2-maliit-1.0
gir1.2-mate-menu
gir1.2-mate-panel
gir1.2-mate-polkit
gir1.2-matekbd
gir1.2-mutter-3.0
gir1.2-spice-client-glib-2.0
gir1.2-spice-client-gtk-3.0
gir1.2-telepathylogger-0.2
gir1.2-urfkill-glib0
gir1.2-v-sim-1.0
gir1.2-gladeui-2.0
gir1.2-grip
gir1.2-javascriptcoregtk-3.0
gir1.2-libvirt-glib-1.0
gir1.2-nemo-3.0
gir1.2-snapd-1
gir1.2-webkit-3.0

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gir1.2-accounts-1.0 1.22+16.10.20160520.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Nov  3 22:02:42 2016
InstallationDate: Installed on 2011-11-10 (1819 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: libaccounts-glib
UpgradeStatus: Upgraded to yakkety on 2016-11-03 (0 days ago)

** Affects: libaccounts-glib (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 libaccounts-glib in
Ubuntu.
https://bugs.launchpad.net/bugs/1639050

Title:
  Wrong package section, should be in "introspection"

Status in libaccounts-glib package in Ubuntu:
  New

Bug description:
  Packages shipping gobject introspection should be in the dedicated
  section "introspection". This archive section was added a while ago,
  see also the corresponding entry in the debian policy 3.9.3.0:

  2.6. Version 3.9.3.0
  

   Released February, 2012.

   2.4
New archive sections _education_, _introspection_, and
_metapackages_ added.

  
  Packages shipping gobject introspection should be named 
gir1.2-NAMESPACE-VERSION.

  Based on the output of apt-cache, the following packages are in the
  wrong section. I didn't file a separate bug for all of them. I would
  appreciate if you can adjust the archive section for all the following
  packages in one go.

  #!/bin/bash

  while read pkg ; do
 apt-cache show $pkg | grep Section | grep -v introspection -q && echo 
$pkg
  done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' )

  
  gir1.2-accounts-1.0
  gir1.2-accountsservice-1.0
  gir1.2-appindicator-0.1
  gir1.2-appindicator3-0.1
  gir1.2-atk-1.0
  gir1.2-atspi-2.0
  gir1.2-bamf-3
  

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

After walking back into wifi range (on my second reproduction) and
refreshing Today scope, only Day scope displays (although it does
display normally).

The scope-reg.log contains this now reliably on refresh with only Day scope 
showing:
[2016-11-03 16:56:46.984] INFO: Registry: RegistryObject::ScopeProcess::exec(): 
Process for scope: "com.canonical.scopes.dashboard_dashboard" started
"com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: 
com.canonical.scopes.day_day, local_id: day_localId"
"com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: 
com.canonical.scopes.weatherchannel, local_id: weather_channel_localId"
"com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: 
com.canonical.scopes.holidays_holidays, local_id: holidays_localID"
"com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: 
com.canonical.scopes.events_events, local_id: events_localID"
"com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: 
com.canonical.scopes.tasks_sctasks, local_id: tasks_localID"
"com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: 
com.canonical.scopes.contacts_contacts, local_id: contacts"
"com.canonical.scopes.dashboard_dashboard: ADDING DECLARED child scope: 
com.canonical.scopes.fitbit_fitbit, local_id: fitbit_localId"
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.canonical.scopes.calls_calls, by keyword recent, to department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.canonical.scopes.texts_texts, by keyword recent, to department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.ubuntu.telegram_sctelegram, by keyword recent, to department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.canonical.elpais_ELPAIS, by keyword news.headlines, to department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.canonical.scopes.bbc_bbc, by keyword news.headlines, to department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.canonical.scopes.eljueves_eljueves, by keyword news.headlines, to 
department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.canonical.scopes.euronews_euronews, by keyword news.headlines, to 
department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
com.canonical.scopes.testscope_testscope, by keyword news.headlines, to 
department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
knitzsche.testscope-art_testscope-art, by keyword news.headlines, to 
department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
knitzsche.testscope-emblem_testscope-emblem, by keyword news.headlines, to 
department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
knitzsche.testscope-mascot_testscope-mascot, by keyword news.headlines, to 
department: "
"com.canonical.scopes.dashboard_dashboard: ADDING CATEGORY KEYWORD child scope: 
twitter.canonicalpartners_twitter, by keyword twitter.home, to department: "
"com.canonical.scopes.dashboard_dashboard: NOT using departments"
aa_getcon failed, errno = 13
[2016-11-03 16:56:50.987] INFO: Registry: RegistryObject::ScopeProcess::exec(): 
Process for scope: "com.canonical.scopes.day_day" started
QSocketNotifier: Can only be used with threads started with QThread
QSocketNotifier: Can only be used with threads started with QThread
QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.1084" (uid=32011 pid=1344 
comm="/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperun") 
interface="org.freedesktop.DBus.Properties" member="GetAll" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1710 comm="NetworkManager ")"
QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.1084" (uid=32011 pid=1344 
comm="/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperun") 
interface="org.freedesktop.NetworkManager" member="GetDevices" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1710 comm="NetworkManager ")"
"Object path cannot be empty"
query complete, status:  ok 

[2016-11-03 16:56:51.548] ERROR: com.canonical.scopes.dashboard_dashboard: 
QueryBase::run(): unity::scopes::TimeoutException: Request timed out after 500 
milliseconds (endpoint = 
ipc:///run/user/32011/zmq/priv/com.canonical.scopes.holidays_holidays, op = 
debug_mode)
[2016-11-03 16:56:51.924] INFO: Registry: 
RegistryObject::ScopeProcess::on_process_death(): 

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

I was just able to produce a MiddelwareException twice by walking out of
range of my wifi while a Today scope refresh was in progress.

In both case the resulting display ONLY the Day scope.

In one case there was also a twitter scope panic/crash.

Attached my scope-reg.log


** Attachment added: "my2reproduced-scope-reg.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1637841/+attachment/4772036/+files/my2reproduced-scope-reg.log

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1638211] Re: Permission denied when trying to report Bug manually

[Brian Murray]

Permission denied might be because it was a service, not a user program
that crashed.  It failing with sudo is probably because apport is still
disabled for Zesty.  See /etc/apport/crashdb.conf and look for
"problem_types".

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

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

Title:
  Permission denied when trying to report Bug manually

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Permission denied when trying to report Bug manually using (ubuntu-bug -c 
bug.crash)
  and even when I trying to run it using (sudo ubuntu-bug -c bug.crash) or as 
Root user first bug window appears but when I click continue it doesn't do 
anything just disappearing and not opening browser.  
  Only working method is (ubuntu-bug package-name)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.3-0ubuntu8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Nov  1 12:20:15 2016
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638718] Re: apport-gtk dialog misses function to copy values

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1273752
   Can't Copy Crash Report Details to Clipboard

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

Title:
  apport-gtk dialog misses function to copy values

Status in apport package in Ubuntu:
  New

Bug description:
  It'd be really helpful if one was able to copy stacktraces from the
  `apport-gtk` dialog. I guess, the function is useful for all other
  parts of the report displayed in the dialog as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport-gtk 2.20.3-0ubuntu8
  Uname: Linux 4.8.6-040806-generic x86_64
  NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
  ApportLog:
   ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: called for pid 24933, 
signal 11, core limit 0
   ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: executable: 
/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess (command line 
"/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess 128 
/usr/lib/mozilla/plugins/flashplugin-alternative.so")
   ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 27227) Wed Nov  2 01:46:09 2016: wrote report 
/var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitPluginProcess.1000.crash
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  2 22:24:43 2016
  InstallationDate: Installed on 2015-12-12 (326 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (16 days ago)

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

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

[Touch-packages] [Bug 1637750] Re: incorrect wording in apport dialog

[Brian Murray]

This is from the package hook for compiz.

 $ dpkg -S /usr/share/apport/package-hooks/source_compiz.py
compiz-core: /usr/share/apport/package-hooks/source_compiz.py

 $ grep "is.*is" /usr/share/apport/package-hooks/source_compiz.py
if ui.yesno("Thanks for reporting this bug. It seems you have unity 
running. Is the issue you are reporting is related to unity itself rather than 
compiz?"):

** Package changed: apport (Ubuntu) => compiz (Ubuntu)

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

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

** Tags added: xenial

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

Title:
  incorrect wording in apport dialog

Status in compiz package in Ubuntu:
  Triaged

Bug description:
  the attached apport dialog says:
  "Thanks for reporting this bug. It seems you have unity running. Is the issue 
you are reporting is related to unity itself rather than compiz?"

  the word "is" is repeated twice. The correct wording should be:

  "Thanks for reporting this bug. It seems you have unity running. Is
  the issue you are reporting related to unity itself rather than
  compiz?"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu8
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 29 13:26:17 2016
  InstallationDate: Installed on 2016-10-28 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580290] Re: First tab is always reloaded when the session is restored

[Michal Predotka]

Hi.
I'm not sure how can I do the testing as that bug was affecting me on Ubuntu 
tablet. I don't use this app on Ubuntu desktop.

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

Title:
  First tab is always reloaded when the session is restored

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  bq M10 rc-proposed OS build 100
  If I have few tabs open and in the first tab is a youtube video, it will 
start playing even if that tap is in the background after restarting the 
Browser.

  Steps to reproduce:
  1. Start Browser
  2. Open a tab with a youtube video in it, for example 
http://summit.ubuntu.com/uos-1605/meeting/22651/convergent-ubuntu-apps
  3. Open few more tabs with other websites
  4. If necessary move the tab with the video so it's the first from the left
  5. Select any other tab
  6. Close  Browser
  7. Start Browser again

  Expected result:
  I don't hear the sound from the video in the background tab.

  What happens instead:
  I hear the sound from the video in the background tab.

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

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

[Touch-packages] [Bug 1638561] Re: unattended-upgrade fails to apply security updates if the update is also in another suite suffix component, such as yakkety-updates

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1624641
   security updates with a new dependency don't get installed

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

Title:
  unattended-upgrade fails to apply security updates if the update is
  also in another suite suffix component, such as yakkety-updates

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  As you can see below, the packages have security updates which are not
  being applied, presumably because the security updates are not only in
  yakkety-security, but also in yakkety-updates. This is a bug and
  leaves systems vulnerable that are expecting unattended-upgrades to
  apply the patches (it fails to do so).

  """
  # apt list --upgradable 2>/dev/null | grep yakkety-security
  liboxideqt-qmlplugin/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtcore0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtquick0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  oxideqt-codecs/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 amd64 
[upgradable from: 1.17.9-0ubuntu1]
  # unattended-upgrade --dry-run -v  
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=yakkety-security']
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: 
  
  """

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

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

David H,

Assuming you have not modified any other parts of your rootfs, let's get
you the latest Today scope and see if you can reproduce any of the
issues, just to be sure.

Please install the attached and reboot (just to get the logs cleared)
and comment back with further info.

** Attachment added: "com.canonical.scopes.dashboard_4.11.1_armhf.click"
   
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1637841/+attachment/4772035/+files/com.canonical.scopes.dashboard_4.11.1_armhf.click

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

David H.

In one of your other bugs about Today scope display issues [1], I think
you mentioned that you made the rootfs "/" read-write (in order to
change the default scope background as I recall).

Doing this is inherently dangerous and can cause all kinds of problems
that are essentially impossible to track down and are not real. The
problem is that over-the-air updates are applied as diffs to files. Any
file that has been modified and that gets an update is thereafter broken
with no recovery path short of reflashing the rootfs. I am not saying
that this is the cause of this bug. I am saying that by modifying the
rootfs you open the door to this possibility.

[1] https://bugs.launchpad.net/today-scope/+bug/1549983/comments/4

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

And provide the scope-registry.log if the issue is reproduceable with
that recent today scope. (I am interested to see if the
MiddlewareExecption occurs again).

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Brian Murray]

While we don't see any crashes about that this from 16.10 on the Error
Tracker, shouldn't this also be fixed in that release?

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

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  New

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

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

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

[Touch-packages] [Bug 1466427] Re: User agent string claims it's running Ubuntu 14.04

[Brian Murray]

Hello Matthew, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  User agent string claims it's running Ubuntu 14.04

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  Ubuntu 15.04 r35

  1. Go to a page that reports your user agent string, for example
   or .

  What you see: Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4)
  AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36

  What you should see: The UA string should not say "Ubuntu 14.04".

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

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

[Touch-packages] [Bug 1565063] Re: Update the chromium version in the user agent

[Brian Murray]

Hello Pat, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Update the chromium version in the user agent

Status in Canonical System Image:
  Fix Released
Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  We have never updated the version, which is 35, and now we are based on 49
  While this may not have any impact it does reflect the core support we have, 
and its possible some sites may check it.

  Ideally we would query oxide for this dynamically.

  
  [Manual test case]
  Open the browser and browse to http://whatsmyua.com.
  Verify that the chromium version number in the UA string is a recent one (> 
50), and not the previously hardcoded value of "35.0.1870.2".

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

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

[Touch-packages] [Bug 1565055] Re: google hangouts thinks we are unsupported

[Brian Murray]

Hello Pat, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  google hangouts thinks we are unsupported

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  We should be able to work properly with webrtc. Instead I got
  presented the unsupported page listing chrome, firefox and safari

  [Manual test case]
  1) Browse to https://hangouts.google.com/
  2) Click/tap the "Video Call" button
  3) Verify that a new hangout is created, and that both audio and video work 
(if a camera is available)

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

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

[Touch-packages] [Bug 1572673] Re: [webapp-container] Invalid variable access error 'popupWindowController'

[Brian Murray]

Hello Alexandre, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  [webapp-container] Invalid variable access error
  'popupWindowController'

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  There an error while opening an overlay:

  file:///home/alex/dev/work/webapps/branches/webbrowser-
  app/error/src/app/webcontainer/WebViewImplOxide.qml:191:
  ReferenceError: popupWindowController is not defined

  
  [Test case for verification]
  The fix comes with an autopilot test. To run the autopilot tests for the 
webapp container, install webapp-container-autopilot, and run `autopilot3 run 
webapp_container`. All the test cases should pass.

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

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

[Touch-packages] [Bug 1580290] Re: First tab is always reloaded when the session is restored

[Brian Murray]

Hello Michal, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  First tab is always reloaded when the session is restored

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  bq M10 rc-proposed OS build 100
  If I have few tabs open and in the first tab is a youtube video, it will 
start playing even if that tap is in the background after restarting the 
Browser.

  Steps to reproduce:
  1. Start Browser
  2. Open a tab with a youtube video in it, for example 
http://summit.ubuntu.com/uos-1605/meeting/22651/convergent-ubuntu-apps
  3. Open few more tabs with other websites
  4. If necessary move the tab with the video so it's the first from the left
  5. Select any other tab
  6. Close  Browser
  7. Start Browser again

  Expected result:
  I don't hear the sound from the video in the background tab.

  What happens instead:
  I hear the sound from the video in the background tab.

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

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

[Touch-packages] [Bug 1576639] Re: memory threshold is too high

[Brian Murray]

Hello Victor, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  memory threshold is too high

Status in Canonical Device Images:
  New
Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  When opening new tabs in the browser, it decides if it should close
  existing ones based on level of free memory available in the system.
  My understanding is that this is currenly set to 30% percentage of
  memory in the device.

  There are two issues with this approach and setting:
  1) a percentage means that the threshold changes from device to device. While 
theamount of memory needed to open a webpage is not device specific. For 
example at 30%, the browser would close open tabs if there less than 1.2Gb mem 
free in a 4Gb device, but will only need 300Mb free on a 1Gb device. This is a 
very large difference.

  2) In M10 with 2Gb it requires 600mb free. From idle, just opening the
  gmail in the browser, takes the avilable system memory below this.
  This means that in 2gb devices the threshold is never met, and the
  browser never runs more than one tab at the same time.  this impacts
  user experience, specially in desktop mode. For example is not
  possible to open a document in the browser while attending a hangout.

  How to reproduce
  open a tab in the browser, go to youtube and play any video
  then open a new tab

  expected:
  music/sound in the video continues to play

  actual in m10:
  sound stops playing shortly after opening the tab

  
  [Manual test case for verification]
  On various devices (desktop with large amount of physical memory, tablet, 
phone, …), open the browser, open a number of tabs and browse to pages known to 
require a large amount of memory (Gmail, G+, hangouts, youtube, Google maps, 
webgl games, …).
  Monitor the amount of available memory (e.g. using top) and verify that when 
the device is getting low on memory some cleanup is performed (background tabs 
are being unloaded) such that the OOM killer nevers kicks in, taking down the 
entire application.
  Verify that the mechanism is not too aggressive, i.e. that not all background 
tabs get unloaded all the time (having a background tab playing some audio is a 
good idea to easily spot when it’s being unloaded).
  As this mechanism is based on heuristics, it will never be 100% perfect, but 
the situation should have greatly improved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-device-images/+bug/1576639/+subscriptions

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

[Touch-packages] [Bug 1573017] Re: [webapp-container] SAML detection logic broken

[Brian Murray]

Hello David, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  [webapp-container] SAML detection logic broken

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  When trying to authenticate to my canonical.com account I keep being ejected 
into the browser application.
  Previously, the SAML detection logic was ensuring this extra authentication 
step was allowed, even if URLs were falling outside of the webapps defined set.

  
  [Test case for verification]
  The fix comes with an autopilot test. To run the autopilot tests for the 
webapp container, install webapp-container-autopilot, and run `autopilot3 run 
webapp_container`. All the test cases should pass.

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

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

[Touch-packages] [Bug 1577806] Re: [SRU] webbrowser app and webcontainer open under the same instance

[Brian Murray]

Hello Sergio, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] webbrowser app and webcontainer open under the same instance

Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed
Status in webbrowser-app source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  On desktop, when a webapp is launched and if the desktop Exec file
  does not specify a --app-id= parameter to the webapp-container
  executable, any new launched application will share the same instance
  as one that has already been launched.

  
  [Test Case]

  1. Install two webapps on desktop that use the webapp-container as a
  launcher,

  e.g.

  https://code.launchpad.net/~abreu-alexandre/+junk/webapp-test

  and

  https://code.launchpad.net/~ogra/+junk/slack-webapp

  2. Make sure that when you launch the slack-webapp nothing happens
  (no app id is provided the app is not launched),

  3. Modify the slack app so that the Exec= line contains the following
  argument:

  --app-id=slackclient

  re-install the app,

  4. Make sure that the 2 apps can be launched simultaneously,

  
  [Regression Potential] 

  All webapps that dont provide an app-id wont start anymore. All current
  webapps though do provide an app-id.


  Original report description:
  ---

  I have on xenial the webbrowser-app as my main browser; if I use the
  webapp-container for anything else it opens as a tab in the main
  browser window. If I open a container instance first, opening the
  webbrowser app opens a new tab in the container instance.

  One webcontainer example to use is
  http://bazaar.launchpad.net/~ogra/+junk/slack-webapp/files

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  3 11:47:05 2016
  InstallationDate: Installed on 2015-08-17 (259 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: webbrowser-app
  UpgradeStatus: Upgraded to xenial on 2015-11-06 (179 days ago)

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

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

[Touch-packages] [Bug 1581025] Re: Secure connection icon not showing

[Brian Murray]

Hello Víctor, or anyone else affected,

Accepted webbrowser-app into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+16.04.20161028-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: webbrowser-app (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Secure connection icon not showing

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  Test case.
  - Open webbrowser-app
  - Browse to https://youtube.com

  Expected result.
  - Secure connection icon is displayed, tap on it to display the certificate 
details.

  Actual result.
  - No secure connection icon is displayed.

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

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

[Touch-packages] [Bug 1581025] Re: Secure connection icon not showing

[Brian Murray]

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Secure connection icon not showing

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  Test case.
  - Open webbrowser-app
  - Browse to https://youtube.com

  Expected result.
  - Secure connection icon is displayed, tap on it to display the certificate 
details.

  Actual result.
  - No secure connection icon is displayed.

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

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

[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

[Kyle Nitzsche]

Hi David H.

So, a few things which I will address in separate comments for clarity.

First, your scope-registry.log contains a
unity::scopes::MiddlewareException

[2016-11-02 17:04:35.351] ERROR:
com.canonical.scopes.dashboard_dashboard: ReplyImpl::error():
unity::scopes::MiddlewareException: Cannot invoke operations while
middleware is stopped

Whenever I have seen this, it is a Game Over situation usually requiring
a reboot.

I am not sure what causes this, but it is part of the unity-scopes-api.
I suspect it is a bug there. so I will add unity-scopes-api package
here.


** Also affects: unity-scopes-api (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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

[Touch-packages] [Bug 1565063] Re: Update the chromium version in the user agent

[Brian Murray]

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Update the chromium version in the user agent

Status in Canonical System Image:
  Fix Released
Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  We have never updated the version, which is 35, and now we are based on 49
  While this may not have any impact it does reflect the core support we have, 
and its possible some sites may check it.

  Ideally we would query oxide for this dynamically.

  
  [Manual test case]
  Open the browser and browse to http://whatsmyua.com.
  Verify that the chromium version number in the UA string is a recent one (> 
50), and not the previously hardcoded value of "35.0.1870.2".

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

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

[Touch-packages] [Bug 1466427] Re: User agent string claims it's running Ubuntu 14.04

[Brian Murray]

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  User agent string claims it's running Ubuntu 14.04

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  Ubuntu 15.04 r35

  1. Go to a page that reports your user agent string, for example
   or .

  What you see: Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4)
  AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36

  What you should see: The UA string should not say "Ubuntu 14.04".

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

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

[Touch-packages] [Bug 1572673] Re: [webapp-container] Invalid variable access error 'popupWindowController'

[Brian Murray]

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  [webapp-container] Invalid variable access error
  'popupWindowController'

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  There an error while opening an overlay:

  file:///home/alex/dev/work/webapps/branches/webbrowser-
  app/error/src/app/webcontainer/WebViewImplOxide.qml:191:
  ReferenceError: popupWindowController is not defined

  
  [Test case for verification]
  The fix comes with an autopilot test. To run the autopilot tests for the 
webapp container, install webapp-container-autopilot, and run `autopilot3 run 
webapp_container`. All the test cases should pass.

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

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

[Touch-packages] [Bug 1580290] Re: First tab is always reloaded when the session is restored

[Brian Murray]

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  First tab is always reloaded when the session is restored

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  bq M10 rc-proposed OS build 100
  If I have few tabs open and in the first tab is a youtube video, it will 
start playing even if that tap is in the background after restarting the 
Browser.

  Steps to reproduce:
  1. Start Browser
  2. Open a tab with a youtube video in it, for example 
http://summit.ubuntu.com/uos-1605/meeting/22651/convergent-ubuntu-apps
  3. Open few more tabs with other websites
  4. If necessary move the tab with the video so it's the first from the left
  5. Select any other tab
  6. Close  Browser
  7. Start Browser again

  Expected result:
  I don't hear the sound from the video in the background tab.

  What happens instead:
  I hear the sound from the video in the background tab.

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

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

[Touch-packages] [Bug 1576639] Re: memory threshold is too high

[Brian Murray]

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  memory threshold is too high

Status in Canonical Device Images:
  New
Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  When opening new tabs in the browser, it decides if it should close
  existing ones based on level of free memory available in the system.
  My understanding is that this is currenly set to 30% percentage of
  memory in the device.

  There are two issues with this approach and setting:
  1) a percentage means that the threshold changes from device to device. While 
theamount of memory needed to open a webpage is not device specific. For 
example at 30%, the browser would close open tabs if there less than 1.2Gb mem 
free in a 4Gb device, but will only need 300Mb free on a 1Gb device. This is a 
very large difference.

  2) In M10 with 2Gb it requires 600mb free. From idle, just opening the
  gmail in the browser, takes the avilable system memory below this.
  This means that in 2gb devices the threshold is never met, and the
  browser never runs more than one tab at the same time.  this impacts
  user experience, specially in desktop mode. For example is not
  possible to open a document in the browser while attending a hangout.

  How to reproduce
  open a tab in the browser, go to youtube and play any video
  then open a new tab

  expected:
  music/sound in the video continues to play

  actual in m10:
  sound stops playing shortly after opening the tab

  
  [Manual test case for verification]
  On various devices (desktop with large amount of physical memory, tablet, 
phone, …), open the browser, open a number of tabs and browse to pages known to 
require a large amount of memory (Gmail, G+, hangouts, youtube, Google maps, 
webgl games, …).
  Monitor the amount of available memory (e.g. using top) and verify that when 
the device is getting low on memory some cleanup is performed (background tabs 
are being unloaded) such that the OOM killer nevers kicks in, taking down the 
entire application.
  Verify that the mechanism is not too aggressive, i.e. that not all background 
tabs get unloaded all the time (having a background tab playing some audio is a 
good idea to easily spot when it’s being unloaded).
  As this mechanism is based on heuristics, it will never be 100% perfect, but 
the situation should have greatly improved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-device-images/+bug/1576639/+subscriptions

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

[Touch-packages] [Bug 1573017] Re: [webapp-container] SAML detection logic broken

[Brian Murray]

** Also affects: webbrowser-app (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  [webapp-container] SAML detection logic broken

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  When trying to authenticate to my canonical.com account I keep being ejected 
into the browser application.
  Previously, the SAML detection logic was ensuring this extra authentication 
step was allowed, even if URLs were falling outside of the webapps defined set.

  
  [Test case for verification]
  The fix comes with an autopilot test. To run the autopilot tests for the 
webapp container, install webapp-container-autopilot, and run `autopilot3 run 
webapp_container`. All the test cases should pass.

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

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

[Touch-packages] [Bug 1637026] Re: kill incorrectly parses negative PIDs

[Brian Murray]

Hello dann, or anyone else affected,

Accepted procps into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.10-4ubuntu2.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed

** Tags added: verification-needed

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

Title:
  kill incorrectly parses negative PIDs

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When kill is called with a negative argument, incorrect parsing can lead it 
to call sys_kill(-1), thus sending a signal to all permitted processes on the 
system. A couple of users have hit this while deploying Hadoop, which seems to 
tickle this - basically killing everything on the system.

  [Test Case]
  Though I don't know what Hadoop is calling, here's a couple of ways to 
trigger this:

  One possibility is if kill were called w/ a numeric signal that
  happened to start with a '1' and while omitting the required 
  argument:

  kill -12

  Another would be to specify a numeric signal (that again happened to
  start with a 1) multiple times:
  kill -13 -13 12345

  [Regression Risk]
  This is a backport from upstream that is already available in 16.10, with no 
known regressions.

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

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

[Touch-packages] [Bug 1637300] Re: procps upgrades fail in a LXD container

[Brian Murray]

Hello dann, or anyone else affected,

Accepted procps into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.10-4ubuntu2.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  procps upgrades fail in a LXD container

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed
Status in procps package in Debian:
  Fix Released

Bug description:
  [Impact]
  procps cannot be upgraded - or even reinstalled - in an LXD container. This 
means we cannot deliver updates (like the pending fix for LP: #1637026 in 
xenial-proposed) w/o putting container users in a bad state that requires a 
container restart to resolve.

  [Test Case]
  $ lxc launch ubuntu:xenial procpstest
  Creating procpstest
  Starting procpstest
  $ lxc exec procpstest -- /bin/bash
  root@procpstest:~# apt --reinstall install procps
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 209 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 procps arm64 
2:3.3.10-4ubuntu2 [209 kB]
  Fetched 209 kB in 1s (113 kB/s)  
  (Reading database ... 25398 files and directories currently installed.)
  Preparing to unpack .../procps_2%3a3.3.10-4ubuntu2_arm64.deb ...
  Unpacking procps (2:3.3.10-4ubuntu2) over (2:3.3.10-4ubuntu2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for systemd (229-4ubuntu11) ...
  Setting up procps (2:3.3.10-4ubuntu2) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Job for systemd-sysctl.service failed because the control process exited with 
error code. See "systemctl status systemd-sysctl.service" and "journalctl -xe" 
for details.
  invoke-rc.d: initscript procps, action "start" failed.
  dpkg: error processing package procps (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   procps
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@procpstest:~#

  [Regression Risk]
  The proposed fix is to disable invoking the procps initscript on 
install/upgrade. This fix is already in yakkety, and I didn't find any bugs 
related to it in LP.

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

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

[Touch-packages] [Bug 1637758] Re: Revision 2409 introduces regression

[Martin Pitt]

** Changed in: lightdm
 Assignee: (unassigned) => Martin Pitt (pitti)

** Project changed: lightdm => lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
Milestone: None => ubuntu-16.11

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

Title:
  Revision 2409 introduces regression

Status in lightdm package in Ubuntu:
  New

Bug description:
  I am using lightdm with 2 seats. After 2409 revision randomly one of
  two seats does not work correctly.

  xsettings plugin from unity-settings-daemon or gnome-settings-deamon
  fails to start because there is already _XSESSION_S* manager running.

  After revision 2409 in system monitor I see that there is still
  running unity-settings-daemon started by lightdm. Reverting this
  revision fixes my problem.

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

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

[Touch-packages] [Bug 1637758] [NEW] Revision 2409 introduces regression

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I am using lightdm with 2 seats. After 2409 revision randomly one of two
seats does not work correctly.

xsettings plugin from unity-settings-daemon or gnome-settings-deamon
fails to start because there is already _XSESSION_S* manager running.

After revision 2409 in system monitor I see that there is still running
unity-settings-daemon started by lightdm. Reverting this revision fixes
my problem.

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Assignee: Martin Pitt (pitti)
 Status: New

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

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

[Touch-packages] [Bug 1496933] Re: Synchronization with google is a pure mess

[Launchpad Bug Tracker]

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

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

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

Title:
  Synchronization with google is a pure mess

Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  One of my main use of the cloud is my address-book witch is shared between my 
computers and my phone.
  I have about 1000 contacts in it.

  1- Synchronization duplicate some entries (and even tri or quadri -plicate)
  2- I lost about 10% of my contacts.
  4- Groups are not handled at all
  3- It does not seems to be running in the background  and must be launched 
manually.

  phablet@ubuntu-phablet:~$ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04
  phablet@ubuntu-phablet:~$ 

  phablet@ubuntu-phablet:~$ apt-cache policy address-book-app
  address-book-app:
Installé : 0.2+15.04.20150819-0ubuntu1
Candidat : 0.2+15.04.20150819-0ubuntu1
   Table de version :
   *** 0.2+15.04.20150819-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.2+15.04.20150402-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/universe armhf 
Packages
  phablet@ubuntu-phablet:~$

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

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

[Touch-packages] [Bug 1496933] Re: Synchronization with google is a pure mess

[Tomas Öqvist]

I can add to the list that the contacts app doesn't sync all contacts in
the google account. For me, it doesn't sync the starred contacts in
google. Not even after I have "unstarred" them in google.

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

Title:
  Synchronization with google is a pure mess

Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  One of my main use of the cloud is my address-book witch is shared between my 
computers and my phone.
  I have about 1000 contacts in it.

  1- Synchronization duplicate some entries (and even tri or quadri -plicate)
  2- I lost about 10% of my contacts.
  4- Groups are not handled at all
  3- It does not seems to be running in the background  and must be launched 
manually.

  phablet@ubuntu-phablet:~$ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04
  phablet@ubuntu-phablet:~$ 

  phablet@ubuntu-phablet:~$ apt-cache policy address-book-app
  address-book-app:
Installé : 0.2+15.04.20150819-0ubuntu1
Candidat : 0.2+15.04.20150819-0ubuntu1
   Table de version :
   *** 0.2+15.04.20150819-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.2+15.04.20150402-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/universe armhf 
Packages
  phablet@ubuntu-phablet:~$

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

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

[Touch-packages] [Bug 1600646] Re: Doesn't sync modified google contacts

[Launchpad Bug Tracker]

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

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

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

Title:
  Doesn't sync modified google contacts

Status in address-book-app:
  New
Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Add a Google account with contacts
  2. Open Google Contacts in browser
  3. Add one extra phone number to one of the contacts and save
  4. Open Contacts app and press the sync button and wait for a successful 
transfer

  Expected:
  The contact modified in the browser shows the newly added number here in 
Contacts app

  Happens:
  The modified contact doesn't show the newly added number

  Device: E5, stable channel, OTA-11
  Google account is set as the default address book

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1600646/+subscriptions

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

[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history - patch

[Brian Murray]

Hello Nikita, or anyone else affected,

Accepted accountsservice into xenial-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Description changed:

  Impact
  ---
  
  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.
  
  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.
  
  Test case
  --
  
  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough distance
  between them for you to tell that the timestamps are correct.
  
  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.
  
  Regression potential
  
  
  I have not encountered any regressions while testing this patch.
- 
+ [bdmurray] - What could go wrong? What should a user testing this look for?
  
  --
  
  Original description:
  
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which is
  meant to show the login history for that account), it will show you when
  you last logged in as "Session Started", but it will show that you
  "Session Ended" just before you login the next time.
  
  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I logged
  out, and then this morning I logged into my account somewhere around
  11:20, it will show this:
  
  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started
  
  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.
  
  I have attached a screenshot to show my example as I see it in the
  History GUI.
  
  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

** Tags added: verification-needed

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

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  

[Touch-packages] [Bug 1443052] Please test proposed package

[Brian Murray]

Hello Nikita, or anyone else affected,

Accepted accountsservice into trusty-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.35-0ubuntu7.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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

[Touch-packages] [Bug 1639017] [NEW] Unable to have Higher Resolution on Ubuntu 16.04

[Aditya Duggal]

Public bug reported:

Hi,

I am only able to view the screen in 1024x768 resolution here is my
output for lshw -c Video

  *-display   
   description: VGA compatible controller
   product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:25 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

I think the xorg driver is fully updated but still I am unable to run in
higher resolution on ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Nov  4 00:33:25 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-10-31 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=361b7ddd-636c-40e8-98a4-6f7c6ceb1f69 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61MS
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd06/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MS:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Nov  4 00:10:15 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2

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


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

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

Title:
  Unable to have Higher Resolution on Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am only able to view the screen in 1024x768 resolution here is my
  output for lshw -c Video

*-display   
 description: VGA compatible controller
 product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:25 memory:f780-f7bf 

[Touch-packages] [Bug 1639000] Re: New upstream release 0.4.13

[Hans Joachim Desserud]

** Tags added: upgrade-software-version

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

Title:
  New upstream release 0.4.13

Status in libproxy package in Ubuntu:
  New

Bug description:
  New in Version 0.4.13
  ==
  * Allow linking webkit pacrunner against javascriptcore-4.0
(webkit2).
  * Allow to disable building of the KDE module (-DWITH_KDE=ON/OFF).
  * Fix compilation errors with CLang on MacOSX.
  * bindings: perl: Add an option to explicitly link against libperl.so
Some distributions want to do it, other prefer not to, the library
is anyway in context of perl.
  * config_kde: Add a basic cache and invalidation: performance improvement
for the KDE module.

  New in version 0.4.12
  ==
  * Move development to github.com/libproxy/libproxy
  * Fix fd leak in get_pac (Bug #185)
  * Detect running MATE session (Bug #186, Part1).
  * Fix linking of perl bindings to pthread (Bug #182)
  * Correctly detect spidermonky (mozjs185) (Bug #188)
  * Stop pxgsettings from segfaulting on exit (Bug #192)
  * Fix test #10 (Bug #189)
  * Fix build on Mac OS X (Bug #183)
  * Add a generic KDE Config module (fix crashes of Qt5 based
  apps) (issue#4)

  We should get this in zesty

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

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

[Touch-packages] [Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64

[Kyle Nitzsche]

** Changed in: savilerow
   Status: Triaged => Won't Fix

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

Title:
  new armhf click build chroot is DEB_BUILD_ARCH=amd64

Status in Ubuntu Developer Portal:
  New
Status in The Savilerow project:
  Won't Fix
Status in click package in Ubuntu:
  Confirmed

Bug description:
  (note sure which project to file this against..)

  I just created a 14.04 armhf click build target from the Ubuntu SDK.

  A terminal into the chroot (from the Maintain button) shows this:

  (click-ubuntu-sdk-14.04-armhf)root@chroma:/home/knitzsche# dpkg-architecture 
  DEB_BUILD_ARCH=amd64
  DEB_BUILD_ARCH_BITS=64
  DEB_BUILD_ARCH_CPU=amd64
  DEB_BUILD_ARCH_ENDIAN=little
  DEB_BUILD_ARCH_OS=linux
  DEB_BUILD_GNU_CPU=x86_64
  DEB_BUILD_GNU_SYSTEM=linux-gnu
  DEB_BUILD_GNU_TYPE=x86_64-linux-gnu
  DEB_BUILD_MULTIARCH=x86_64-linux-gnu
  DEB_HOST_ARCH=amd64
  DEB_HOST_ARCH_BITS=64
  DEB_HOST_ARCH_CPU=amd64
  DEB_HOST_ARCH_ENDIAN=little
  DEB_HOST_ARCH_OS=linux
  DEB_HOST_GNU_CPU=x86_64
  DEB_HOST_GNU_SYSTEM=linux-gnu
  DEB_HOST_GNU_TYPE=x86_64-linux-gnu
  DEB_HOST_MULTIARCH=x86_64-linux-gnu

  I expected (perhaps naively) :DEB_BUILD_ARCH=armhf (and probably
  others).

  When I install pkgs in the chroot with apt-get install, the amd64 arch
  one is installed unless I specify armhf, which I did not expect
  either.

  Some pkgs/vers on my host system:
  $ apt-cache policy qtcreator-plugin-ubuntu
  qtcreator-plugin-ubuntu:
Installed: 3.0.1+14.10.20140521.1-0ubuntu1~0trusty1

  $ apt-cache policy click
  click:
Installed: 0.4.23.1ubuntu1i~0trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1322178/+subscriptions

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

[Touch-packages] [Bug 1573296] Re: obsolete conffiles not cleaned up on upgrade

[Brian Murray]

Hello Michael, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  Impact:

  When upgrading to xenial from earlier releases, some files are left on
  the user's system. They are not used, but may otherwise be mistaken
  for being used by the user if they are attempting to fix a problem.

  Regression potential:

  Low to none, as the relevant files are not used, and are being removed
  when the updated version of Pulseaudio is installed. These files are
  already removed in yakkety and later.

  Test case:

  When updating from trusty to xenial, one will note the presence of the
  below listed files on the system. Updating from pulseaudio in xenial
  or pulseaudio in trusty to what is in xenial-proposed shoudl delete
  the listed files. The /etc/init.d/pulseaudio script should also be
  unregistered.

  
  Original bug report:

  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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

[Touch-packages] [Bug 1574324] Please test proposed package

[Brian Murray]

Hello ian_hawdon, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Yakkety:
  Fix Committed

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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

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

[Brian Murray]

Hello ian_hawdon, or anyone else affected,

Accepted pulseaudio into yakkety-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:9.0-2ubuntu2.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

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

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

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Yakkety:
  Fix Committed

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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

[Touch-packages] [Bug 1522988] Re: stdout and stderr are not synced on lines

[David Kalnischkies]

Without an example nobody will ever know what you might mean.

You might be meaning accidentally debug output – I that happened
sometime ago, could be 1.1 and should be fixed in newer versions. Or
perhaps you mean that you enabled debug output and expect it to be all
orderly – not going to happen: Multiple processes are running here which
would need to be synced by an additional output layer all so that debug
output looks nicer…). Or you mean sometimes else which might or might
not be a bug (still). Without additional details it is at least not an
actionable bugreport hence set to 'incomplete'.

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

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

Title:
  stdout and stderr are not synced on lines

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 16.04 dev with apt 1.1.3 and I'm noticing that for
  example if on executing "apt-get update" error messages are shown they
  are often broken. They are missing sometimes characters which seem to
  be splitted across multiple lines. It looks that apt doesn't ensure
  writing complete lines if stdout and stderr are used.

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

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

[Touch-packages] [Bug 1638873] Re: package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[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 dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1638873

Title:
  package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in dbus package in Ubuntu:
  New

Bug description:
  install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov  3 09:37:50 2016
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2016-07-21 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: dbus
  Title: package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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