Re: [Touch-packages] [Bug 1614158] Re: Don't get up by starting

[modaell]

Hi

sorry but since I installed the new version of ubuntu I have problems to 
start the computer again the same problem..

Greetins

Monique


Am 17.08.2016 um 18:50 schrieb Paul White:
> Hi modaell,
>
> You say: "I have to wait lontimes till the programm start up. Sometimes
> i close cold and try again. Then I make esc and take the programm ubuntu
> and then it works better"
>
> I appreciate that English may not be your native language but which
> programs are you referring to? Please gives us some examples.
>
> You have reported a bug against the xorg package. Was that your
> intention?
>
> Are you referring to the startup of your PC or the startup of individual
> applications that you have installed?
>
> Please clarify, thanks.
>
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Don't get up by starting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have to wait lontimes till the programm start up. Sometimes i close
  cold and try again. Then I make esc and take the programm ubuntu and
  then it works better

  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
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 17 18:07:07 2016
  DistUpgraded: 2016-08-04 11:16:38,062 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-92-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:180f]
  InstallationDate: Installed on 2015-04-29 (476 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 6475b
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=9d20e8cc-fbe8-4310-8a57-2061e2a6c8bf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (13 days ago)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68RTU Ver. F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 180F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 47.19
  dmi.chassis.asset.tag: CNU3329NSY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68RTUVer.F.46:bd10/07/2013:svnHewlett-Packard:pnHPProBook6475b:pvrA1029D1103:rvnHewlett-Packard:rn180F:rvrKBCVersion47.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6475b
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard
  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.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 17 18:05:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3
  xserver.video_driver: radeon

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

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

Re: [Touch-packages] [Bug 1599952] Re: Blurred images with kernels after 4.2.x

[RD]

You don't say whether there is any reason to believe there might have 
been a change to address the regression that affects my system.  Even 
so, I will try to get to the store tomorrow and try the new kernel, as 
you suggest, as soon as I can - maybe tomorrow evening.  If it works for 
me Iĺl let you know, and if it doesn't I'll send you a screenshot before 
going back to Mint.

RD


On 08/29/2016 09:26 AM, Christopher M. Penalver wrote:
> RD, it is most helpful if your testing results are from Ubuntu
> specifically (not derivatives, etc.).
>
> To advise, Trusty with the original 3.13 kernel is fully supported as
> outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack . This
> would also help here as you would have a working environment to perform
> tests from.
>

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

Title:
  Blurred images with kernels after 4.2.x

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Have used Ubuntu or its flavors for 3 years with no issues on this
  machine. Installed Ubuntu 16.04 64-bit lts, and successively xubuntu
  16.04, ubuntuMATE 16.04, and lubuntu 16.04. Each installed, but with
  blurred images.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-07-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6850
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic 
root=UUID=30188e44-b1e6-4cdc-bd16-62f107d213a7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6850
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd12/21/2011:svnASUSTeKComputerINC.:pnCM6850:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM6850:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6850
  dmi.product.version: System Version
  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

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

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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Martin Pitt]

> Where will the public policy discuss take place?

It should happen on https://lists.ubuntu.com/mailman/listinfo/ubuntu-
devel . However, I'm not going to start it now, we are past feature
freeze for yakkety and I have enough other things to work on in this
release. Feel free to start it yourself of course!

> Perhaps one possibility for a interim solution is for rsyslog to log
to journald by default

No, it's the other way around -- rsyslog should pull its data from the
journal (but that's a different topic actually). The journal already
collects all syslog() calls, it logs what rsyslog does plus a lot more.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- systemd journal should be persistent by default: /var/log/journal should be 
created
+ systemd journal should be persistent by default: /var/log/journal should be 
created; remove rsyslog from default installs

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

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

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created; remove rsyslog from default installs

Status in systemd package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1561859] Re: touchscreen not working

[Christopher M. Penalver]

Anupam Datta, to keep this relevant to upstream, one would want to
continue testing the latest mainline kernel (4.8-rc3) as they are
released.

Could you please advise?

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

Title:
  touchscreen not working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  up vote
  0
  down vote
  favorite
  My laptop touchscreen is not working in 16.04 In Windows 10, it works. Even 
in 14.04 it was working, and in 15.10 as well.

  anupam@hpEnvy15:~$ xinput list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=10   [slave  pointer  (2)]
  ⎜   ↳ SYNA1359:00 06CB:1359 id=12   [slave  pointer  (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPadid=14   [slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Power Button  id=9[slave  keyboard (3)]
  ↳ HP Truevision HD  id=11   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]
  ↳ HP WMI hotkeysid=15   [slave  keyboard (3)]
  ↳ HP Wireless hotkeys   id=16   [slave  keyboard (3)]
  Can anyone help me regarding this ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  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 Mar 25 11:56:21 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  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:80dd]
 Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd]
  InstallationDate: Installed on 2016-02-21 (32 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/16/2015:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  

Re: [Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display

[Michael Thayer]

Hello,

Short answer (mobile mail). On the whole a bug with a workaround is
usually (understandably) less important to people than one without. I am
slightly surprised that Canonical have not looked at this since I have
provided a fix which may well be acceptable as is, but of course I do
not presume to try to tell them what their priorities should be.

Regards,

Michael

On 30. August 2016 02:58:14 GMT+03:00, "S. McCandlish"  
wrote:
>Re: "I note that the person asking the question seemingly never
>bothered
>to create an Ubuntu bug, so it can't have been that important to them."
>That's not actually a safe assumption at all.  Many people are on the
>clock and are not paid to file bug reports for the rest of the world.
>As
>soon they find a work-around that deals with the problem temporarily
>and
>locally, they move on.  This problem has been reported world-wide in
>multiple circumstances, and is still happening with 16.04. It just
>happened to me right now (with the Xubunutu 16.04.1 ISO in a VirtualBox
>VM).  The Right-Ctrl F1 and Right-Ctrl F7 (or "Host" F1, "Host" F7, if
>you've redefined the "Host" key) trick worked for me in this case, so
>I'm done with it and getting back to work.  It is possible I (or
>someone
>in my situation) might remember to try to replicate and debug this
>problem further for everyone, on a VM at home, on our own time. But
>Canonical cannot depend on this happening. It's a "bad administrator
>experience" issue that should be dealt with like any other serious bug.
>
>-- 
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1443853
>
>Title:
>  Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a
>  corrupted display
>
>Status in Virtualbox:
>  Invalid
>Status in console-setup package in Ubuntu:
>  Confirmed
>Status in kbd package in Ubuntu:
>  Confirmed
>Status in virtualbox package in Ubuntu:
>  Incomplete
>
>Bug description:
>  (Content copied from "Ubuntu 14.10 ISO live boot ends up with a
>  corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz)
>
>Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10
>from ISO ends up with a corrupted screen. See the screenshot:
>  https://launchpadlibrarian.net/186864347/ubu.png
>
>  Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7)
>  fixes the display.
>
>  I think that this might be a problem with resolution setting:
>
>  ```
>00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0,
>pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
>00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0,
>BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to
>async-handler..
>00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0,
>BitsPerPixel=0, BytesPerLine=0, Size=1152x400
>00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK
>buffer due to format is invalid..
>  ```
>
>  After switching back and forth to the tty7 (what fixes the display)
>  the log says:
>
>  ```
>00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0,
>pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
>00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0,
>BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to
>async-handler..
>00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0,
>BitsPerPixel=0, BytesPerLine=0, Size=1152x400
>00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK
>buffer due to format is invalid..
>00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0,
>pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
>00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0,
>BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to
>async-handler..
>00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0,
>BitsPerPixel=0, BytesPerLine=0, Size=720x400
>00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK
>buffer due to format is invalid..
>00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0,
>pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1
>00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0,
>Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768,
>Sending to async-handler..
>00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434,
>BitsPerPixel=32, BytesPerLine=4096, Size=1024x768
>00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly
>use VGA device content..
>  ```
>
>  I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens
>  on both of them.
>
>  You can download the ISO images of these two systems here:
>
>   https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10
>  -desktop-amd64.iso
>
>  http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-
>  gnome-14.10-desktop-amd64.iso
>
>To manage notifications about this bug go to:

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Aravind Gopal]

Its a LSB problem? status?

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

[Daniel van Vugt]

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

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

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

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

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

[Touch-packages] [Bug 1618298] [NEW] Gdk-WARNING **: Ignoring unknown Mir event 11

[Daniel van Vugt]

Public bug reported:

GTK apps now say:

Gdk-WARNING **: Ignoring unknown Mir event 11

Which is a harmless event to ignore. We should just silence the warning.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: gtk-mir

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

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

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

Title:
  Gdk-WARNING **: Ignoring unknown Mir event 11

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  GTK apps now say:

  Gdk-WARNING **: Ignoring unknown Mir event 11

  Which is a harmless event to ignore. We should just silence the
  warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1618298/+subscriptions

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

[Touch-packages] [Bug 1576032] Re: Software compositing of EGL clients is much slower than software compositing of software clients

[Daniel van Vugt]

This is possibly not a bug at all.

It's quite reasonable that uploading a software texture in software
should be much faster than interpreting an EGL image in software and
uploading that. Although leave the bug open because I hope we can get
the figure of 7FPS closer to the 30FPS seen elsewhere.

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

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

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

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

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

Title:
  Software compositing of EGL clients is much slower than software
  compositing of software clients

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Software compositing of EGL clients is much slower than software
  clients. Even when the EGL client is allowed to render in hardware.
  There is something weirdly slow about our EGL texture binding compared
  to software textures...

  Start the server with software rendering:
  $ sudo env GBM_ALWAYS_SOFTWARE=1 mir_proving_server --compositor-report=log

  Now start a fullscreen client (even with hardware rendering enabled)
  and drag the window around (so it's no longer bypassed).

  Compositor performance:
  7 FPS with mir_demo_client_eglflash (rendered in hardware, only rendering 1 
FPS)
  7 FPS with mir_demo_client_egltriangle (rendered in hardware)
  30 FPS with mir_demo_client_fingerpaint (not redrawing at all)
  30 FPS with 'mir_demo_client_progressbar 1' (rendered in software at 1 FPS)
  30 FPS with 'mir_demo_client_progressbar 60' (rendered in software at 60 FPS)
  30 FPS with 'mir_demo_client_flicker' (rendered in software at 60 FPS)

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

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

[Touch-packages] [Bug 1618288] [NEW] wget using "if-modified-since" is not idempotent and corrupts downloaded copy of website on second use

[Carl Hauser]

Public bug reported:

I use wget to copy a web site from one server to another, adjusting file
suffixes and paths.

Since updating to 16.04 LTS from 14.04 the command that I used
previously  has begun corrupting the destination site on second and
subsequent invocations.

The options relevant to the problem seem to be -N (use timestamping), -k
(convert links) and -E (adjust extensions). The problem arises with
linked files whose names do not end in .html. On the first invocation
everything is good: file foo.txt is downloaded and linked as foo.txt. On
the second invocation the wget log (option -v) suggests that it has
examined foo.txt on the server, but then it reports "File
'/foo.txt.html' not modified on server. Omitting
download." and then it changes the link in the referring file to
foo.txt.html.

I think this is a bug. Do others have an opinion?

Workaround: include the option "--no-if-modified-since" which seems to
restore the old, correct behavior.

Thanks.

P.S. The full command that misbehaves is: wget -nH -r -E -k -N -x -l inf
-P  "http://"

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

** Package changed: ubuntu => wget (Ubuntu)

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

Title:
  wget using "if-modified-since" is not idempotent and corrupts
  downloaded copy of website on second use

Status in wget package in Ubuntu:
  New

Bug description:
  I use wget to copy a web site from one server to another, adjusting
  file suffixes and paths.

  Since updating to 16.04 LTS from 14.04 the command that I used
  previously  has begun corrupting the destination site on second and
  subsequent invocations.

  The options relevant to the problem seem to be -N (use timestamping),
  -k (convert links) and -E (adjust extensions). The problem arises with
  linked files whose names do not end in .html. On the first invocation
  everything is good: file foo.txt is downloaded and linked as foo.txt.
  On the second invocation the wget log (option -v) suggests that it has
  examined foo.txt on the server, but then it reports "File
  '/foo.txt.html' not modified on server. Omitting
  download." and then it changes the link in the referring file to
  foo.txt.html.

  I think this is a bug. Do others have an opinion?

  Workaround: include the option "--no-if-modified-since" which seems to
  restore the old, correct behavior.

  Thanks.

  P.S. The full command that misbehaves is: wget -nH -r -E -k -N -x -l
  inf -P  "http://"

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

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

[Touch-packages] [Bug 1618288] [NEW] wget using "if-modified-since" is not idempotent and corrupts downloaded copy of website on second use

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I use wget to copy a web site from one server to another, adjusting file
suffixes and paths.

Since updating to 16.04 LTS from 14.04 the command that I used
previously  has begun corrupting the destination site on second and
subsequent invocations.

The options relevant to the problem seem to be -N (use timestamping), -k
(convert links) and -E (adjust extensions). The problem arises with
linked files whose names do not end in .html. On the first invocation
everything is good: file foo.txt is downloaded and linked as foo.txt. On
the second invocation the wget log (option -v) suggests that it has
examined foo.txt on the server, but then it reports "File
'/foo.txt.html' not modified on server. Omitting
download." and then it changes the link in the referring file to
foo.txt.html.

I think this is a bug. Do others have an opinion?

Workaround: include the option "--no-if-modified-since" which seems to
restore the old, correct behavior.

Thanks.

P.S. The full command that misbehaves is: wget -nH -r -E -k -N -x -l inf
-P  "http://"

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

-- 
wget using "if-modified-since" is not idempotent and corrupts downloaded copy 
of website on second use
https://bugs.launchpad.net/bugs/1618288
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wget 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 1603175] Re: No resolution configuration available

[Daniel van Vugt]

Fabio: "low DPI" is a poorly chosen term, almost passive-aggressive,
that describes any _normal_ resolution where you can actually see
individual pixels. Us calling it "low DPI" should not diminish the
importance of supporting it correctly :)

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

Title:
  No resolution configuration available

Status in Ubuntu UX:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In my desktop unity8 is clearly in the wrong resolution:
   - the font in the titlebar is quite pixelated
   - the cursor is huge

  It would be required to have a setting like the one in unity7 to set
  the correct resolution of the screen.

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

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

[Touch-packages] [Bug 1618282] Re: libgl1-mesa-dri install error

[Jesse]

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730382/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730383/+files/XorgLogOld.txt

** Attachment removed: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730371/+files/LightdmDisplayLog.txt

** Attachment removed: "Df.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730364/+files/Df.txt

** Attachment removed: "BootDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730360/+files/BootDmesg.txt

** Attachment removed: "Dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730366/+files/Dmesg.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730380/+files/UdevDb.txt

** Attachment removed: "UdevLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1618282/+attachment/4730381/+files/UdevLog.txt

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

Title:
  libgl1-mesa-dri install error

Status in mesa package in Ubuntu:
  New

Bug description:
  Package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade
  with the following error message:

  trying to overwrite shared '/etc/drirc', which is different from other
  instances of package libgl1-mesa-dri:i386

  Platform: Ubuntu 14.04 LTS.

  I was installing it as a dependency while installing
  libqt5opengl5-dev.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 29 21:00:55 2016
  DistUpgraded: 2016-08-04 00:14:27,819 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6:trying to 
overwrite shared '/etc/drirc', which is different from other instances of 
package libgl1-mesa-dri:i386
  ErrorMessage: trying to overwrite shared '/etc/drirc', which is different 
from other instances of package libgl1-mesa-dri:i386
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6450 [1028:2120]
  MachineType: Dell Inc. OptiPlex 790
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-66-generic 
root=/dev/mapper/gs11709-root ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:i386
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  UpgradeStatus: Upgraded to trusty on 2016-08-04 (25 days ago)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Aug 29 20:48:06 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   input  

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

[Yura Nosenko]

I can confirm the same issue on Ubuntu 16.04/4.4.0-31-generic with
Jaybird X2. It connects and then disconnects immediately.

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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

[Touch-packages] [Bug 1618282] Re: libgl1-mesa-dri install error

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  libgl1-mesa-dri install error

Status in mesa package in Ubuntu:
  New

Bug description:
  Package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade
  with the following error message:

  trying to overwrite shared '/etc/drirc', which is different from other
  instances of package libgl1-mesa-dri:i386

  Platform: Ubuntu 14.04 LTS.

  I was installing it as a dependency while installing
  libqt5opengl5-dev.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 29 21:00:55 2016
  DistUpgraded: 2016-08-04 00:14:27,819 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6:trying to 
overwrite shared '/etc/drirc', which is different from other instances of 
package libgl1-mesa-dri:i386
  ErrorMessage: trying to overwrite shared '/etc/drirc', which is different 
from other instances of package libgl1-mesa-dri:i386
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6450 [1028:2120]
  MachineType: Dell Inc. OptiPlex 790
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-66-generic 
root=/dev/mapper/gs11709-root ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:i386
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  UpgradeStatus: Upgraded to trusty on 2016-08-04 (25 days ago)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Aug 29 20:48:06 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Entry Keyboard KEYBOARD, id 8
   inputUSB Optical MouseMOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1618282] [NEW] libgl1-mesa-dri install error

[Jesse]

Public bug reported:

Package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade with
the following error message:

trying to overwrite shared '/etc/drirc', which is different from other
instances of package libgl1-mesa-dri:i386

Platform: Ubuntu 14.04 LTS.

I was installing it as a dependency while installing libqt5opengl5-dev.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6
ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-66-generic x86_64
NonfreeKernelModules: openafs
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Aug 29 21:00:55 2016
DistUpgraded: 2016-08-04 00:14:27,819 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6:trying to 
overwrite shared '/etc/drirc', which is different from other instances of 
package libgl1-mesa-dri:i386
ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from 
other instances of package libgl1-mesa-dri:i386
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 6450 [1028:2120]
MachineType: Dell Inc. OptiPlex 790
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-66-generic 
root=/dev/mapper/gs11709-root ro splash quiet vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: mesa
Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:i386
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
UpgradeStatus: Upgraded to trusty on 2016-08-04 (25 days ago)
dmi.bios.date: 05/28/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0HY9JP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 790
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Aug 29 20:48:06 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Entry Keyboard KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-package compiz-0.9 package-conflict trusty ubuntu

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

Title:
  libgl1-mesa-dri install error

Status in mesa package in Ubuntu:
  New

Bug description:
  Package libgl1-mesa-dri 10.1.3-0ubuntu0.6 failed to install/upgrade
  with the following error message:

  trying to overwrite shared '/etc/drirc', which is different from other
  instances of package libgl1-mesa-dri:i386

  Platform: Ubuntu 14.04 LTS.

  I was installing it as a dependency while installing
  libqt5opengl5-dev.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: 

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[D. Charles Pyle]

Same here.  Ubuntu 16.04.  ASUSTek Radeon HD 5750 Formula card and
Sabrent DisplayLink, with Dual Dell S2440L monitors connected to the
ASUSTek card and a ViewSonic VX922 monitor connected to the Sabrent
device via native DVI.  Heavy flickering on the mouse cursor with
updating of the DisplayLink device.  I have it set up so I can see the
blinking light and notice that when it flickers the mouse cursor
flickers on both the primary display and the secondary display, but not
the one connected to the DisplayLink device.  No flickering there at
all.  Another problem is that responsiveness seems slower on the other
displays since connecting the DisplayLink device.  I ran the Unity
Support test and it shows that Unity is supported.

$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string:   X.Org
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER (DRM 2.43.0, LLVM 3.8.0)
OpenGL version string:  3.0 Mesa 11.2.0

Not software rendered:yes
Not blacklisted:  yes
GLX fbconfig: yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:yes
GL fragment program:  yes
GL vertex buffer object:  yes
GL framebuffer object:yes
GL version is 1.4+:   yes

Unity 3D supported:   yes

It is really seeming to bog down the performance of the system's other
displays.  It does not do that on Mac OS X or on Windows 7 or on Windows
10.  Even typing has been slowed down noticeably.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Grey Blackbeard]

I tinkered with a similar command, then could install Gnome.  It meets 
my needs so I might not even try to install Unity, but I think it would 
install now, too.


On 08/29/2016 02:27 PM, Mohammed Alkindi wrote:
> when I wrote
> sudo apt remove account-plugin-google unity-scope-gdrive 
> kde-telepathy-minimal kde-telepathy
>
> The problem solved and the setup continued!
>

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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

[Touch-packages] [Bug 1618256] [NEW] Error code 1.108067

[Laurie]

Public bug reported:

@ every start up

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
Date: Tue Aug 30 09:15:59 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.26, 4.4.0-28-generic, x86_64: installed
 vboxhost, 5.0.26, 4.4.0-34-generic, x86_64: installed
 vboxhost, 5.0.26, 4.4.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 82Q35 Express Integrated Graphics Controller 
[8086:4f4a]
   Subsystem: Intel Corporation 82Q35 Express Integrated Graphics Controller 
[8086:4f4a]
InstallationDate: Installed on 2016-06-11 (79 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: AnabelleB Argyle M290
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: JOQ3510J.86A.1143.2010.1209.0048
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DQ35JO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD82085-800
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrJOQ3510J.86A.1143.2010.1209.0048:bd12/09/2010:svnAnabelleB:pnArgyleM290:pvr:rvnIntelCorporation:rnDQ35JO:rvrAAD82085-800:cvn:ct3:cvr:
dmi.product.name: Argyle M290
dmi.sys.vendor: AnabelleB
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug 30 09:04:37 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputSleep Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 625 
 vendor SAM
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

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

Title:
  Error code 1.108067

Status in xorg package in Ubuntu:
  New

Bug description:
  @ every start up

  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
  Date: Tue Aug 30 09:15:59 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.26, 4.4.0-28-generic, x86_64: installed
   vboxhost, 5.0.26, 4.4.0-34-generic, x86_64: installed
   vboxhost, 5.0.26, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82Q35 Express Integrated Graphics Controller 
[8086:4f4a]
 Subsystem: Intel Corporation 82Q35 Express Integrated Graphics Controller 
[8086:4f4a]
  InstallationDate: Installed on 2016-06-11 (79 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  

[Touch-packages] [Bug 1618256] Re: Error code 1.108067

[Laurie]

how do I fix this

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

Title:
  Error code 1.108067

Status in xorg package in Ubuntu:
  New

Bug description:
  @ every start up

  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
  Date: Tue Aug 30 09:15:59 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.26, 4.4.0-28-generic, x86_64: installed
   vboxhost, 5.0.26, 4.4.0-34-generic, x86_64: installed
   vboxhost, 5.0.26, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82Q35 Express Integrated Graphics Controller 
[8086:4f4a]
 Subsystem: Intel Corporation 82Q35 Express Integrated Graphics Controller 
[8086:4f4a]
  InstallationDate: Installed on 2016-06-11 (79 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: AnabelleB Argyle M290
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: JOQ3510J.86A.1143.2010.1209.0048
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DQ35JO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD82085-800
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrJOQ3510J.86A.1143.2010.1209.0048:bd12/09/2010:svnAnabelleB:pnArgyleM290:pvr:rvnIntelCorporation:rnDQ35JO:rvrAAD82085-800:cvn:ct3:cvr:
  dmi.product.name: Argyle M290
  dmi.sys.vendor: AnabelleB
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug 30 09:04:37 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputLogitech USB Receiver KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 625 
   vendor SAM
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1618256] Re: Error code 1.108067

[Laurie]

This is a view of crash report
Submitted Crash Reports
Report ID   Date Submitted
bp-244cef4e-2ff8-4fc7-80fc-2667b2160827
27/08/1610:39
bp-ff82bf42-b4f8-4f63-b825-278962160804
05/08/1604:52
bp-d628841e-0f63-4ff4-82e8-c6dd32160804
05/08/1604:23
bp-41d560ec-1c9b-4998-a823-ccdc42160730
30/07/1611:52
bp-711fa203-80e0-41cc-b9b5-7eb272160730
30/07/1611:49
bp-de410c2a-0631-4097-81d4-c82472160729
29/07/1610:52
bp-128517fa-12ed-4f4f-acc2-4c8952160729
29/07/1610:29
bp-75fc469d-28b8-4a30-85ca-ff80f2160728
29/07/1604:18
bp-234ce410-b09b-43cd-9d31-020d62160728
29/07/1604:18
bp-68e939c2-8fd7-479d-a0fa-86dc42160728
28/07/1612:49
bp-e6ae49e0-6b7b-4d75-b916-55e632160728
28/07/1612:19
bp-b6914246-d0c3-4d7f-8f66-175702160725
25/07/1610:47
bp-c3f93287-6db6-47d2-b9df-91c292160713
13/07/1611:15
bp-04d5a6c3-b178-4273-a54c-979ce2160713
13/07/1610:22
bp-44894360-0a85-481a-9a90-5637f2160712
12/07/1611:38
bp-cf26beb1-3887-4dbb-84d1-517cf2160712
12/07/1611:35
bp-480add8a-5d4d-463a-bcde-951752160712
12/07/1611:10
bp-9476c688-b305-421c-82a0-487e32160712
12/07/1610:46
bp-a68cdf64-da05-4220-8df3-d8ec02160712
12/07/1610:06
bp-d8678564-bc2b-4db5-91c4-a79c12160711
11/07/1611:01
bp-9c1e22c9-6334-4151-a995-557102160711
11/07/1610:59
bp-d6c942b6-c0ea-4366-bbd7-153bc2160711
11/07/1610:40
bp-70577961-5464-46e0-93c3-36f112160710
11/07/1608:36
bp-e95bcaab-a281-4efa-ad88-6a0102160710
11/07/1608:30
bp-a4d2297d-0dc2-41fe-9ee5-a82122160710
11/07/1608:30
bp-464cf7e5-cfb1-4f41-8a79-40ea92160707
07/07/1611:34
bp-aee93759-7ea7-404f-ae17-7640c2160707
07/07/1611:10
bp-7f3f9275-5da9-43e7-9688-3a1802160705
05/07/1610:14
bp-a616a2c3-266a-44a9-a213-de06d2160704
04/07/1612:18
bp-ba680c4b-b116-47fc-939a-e8d6d2160704
04/07/1610:27
bp-e91299eb-dc85-4b24-a6bf-114a42160627
27/06/1611:52
bp-7e32a346-ee1f-4e55-b776-e41a12160625
25/06/1610:49
bp-995d25dc-033e-4489-8940-27c802160625
25/06/1610:41
bp-81967501-18f6-4a06-883d-0a0482160625
25/06/1610:40
bp-03fd948b-b2e5-4a88-a49b-4037e2160625
25/06/1610:38
bp-6c154532-e777-4725-852b-dfde42160624
25/06/1609:51
bp-6b8d6aa2-0593-4477-86d8-59d442160624
25/06/1604:02
bp-17070c61-39a2-4086-9b73-d79d52160624
25/06/1604:01
bp-ab31f0e8-a351-40c6-a9b7-3cb2b2160624
25/06/1604:01
bp-081291c8-a065-46dc-ac7b-4cab72160624
25/06/1603:58
bp-2868117b-7628-4164-8216-bc9232160624
25/06/1603:47
bp-ba69fb0f-90ec-44fc-8653-c87342160624
25/06/1603:43
bp-5b27473c-57fb-4ae4-bffa-6f6102160624
25/06/1603:34
bp-cfc67733-0b2e-4e7a-bbb9-cea6e2160624
25/06/1603:30
bp-feab4f56-3a0d-414a-8bd9-640562160624
25/06/1603:14
bp-4c7ac8e2-6bb1-446b-899c-6e61d2160624
25/06/1603:08
bp-4fa999d0-9fc6-4540-b8b1-6606d2160624
25/06/1603:08
bp-8600e132-98c6-4381-9629-9a0382160624
25/06/1603:04
bp-af13443a-cb28-4c4d-a671-49c402160623
23/06/1612:29
bp-fe795300-c9ad-41ad-9706-5e4522160623
23/06/1610:51
bp-7b3d0a64-2e32-4574-89f6-b67232160623
23/06/1610:30
bp-6bc31668-399f-4d0a-83ba-23f242160623
23/06/1610:18
bp-a1937a63-84d4-4d08-a7f8-a40132160620
20/06/1611:17
bp-91b11153-f733-4daa-ad91-511342160620
20/06/1611:05
bp-73104a07-a968-493f-b652-b6c032160619
20/06/1609:59
bp-d5bda0dc-0c72-4d9b-96fd-b67fd2160619
19/06/1618:13
bp-ad7b31d4-e978-4199-aef2-564dc2160619
19/06/1610:55
bp-29692787-b559-46a4-88ef-9ecda2160619
19/06/1610:43
bp-471e41ec-01e8-43c6-bb70-3b8502160619
19/06/1610:41
bp-17715522-02aa-4f8a-b547-fd4d52160619
19/06/1610:41
bp-022d48b5-7404-410a-bc6e-1ce522160619
19/06/1610:35
bp-dff93855-7b62-4684-9fbe-08e1d2160616
16/06/1611:56
bp-52257baa-29bb-476b-9d00-27b752160614
15/06/1609:57
bp-7c435216-6bac-4286-be06-3cd692160614
15/06/1609:28
bp-1c335f22-eb64-4025-a6e8-7d4552160614
15/06/1609:26
bp-d40f41ad-848c-463d-9fd2-d309b2160614
15/06/1609:25
bp-2177af0f-d4cc-4963-81db-8a7d52160614
15/06/1609:15
bp-f90370fe-3fd5-4228-aa6e-3334c2160614
15/06/1609:15
bp-33c4af6b-f97b-4474-b205-a9c692160614
15/06/1603:42
bp-93d831c0-3c15-4548-b586-d73d82160614
15/06/1603:41

[Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display

[S. McCandlish]

Re: "I note that the person asking the question seemingly never bothered
to create an Ubuntu bug, so it can't have been that important to them."
That's not actually a safe assumption at all.  Many people are on the
clock and are not paid to file bug reports for the rest of the world. As
soon they find a work-around that deals with the problem temporarily and
locally, they move on.  This problem has been reported world-wide in
multiple circumstances, and is still happening with 16.04. It just
happened to me right now (with the Xubunutu 16.04.1 ISO in a VirtualBox
VM).  The Right-Ctrl F1 and Right-Ctrl F7 (or "Host" F1, "Host" F7, if
you've redefined the "Host" key) trick worked for me in this case, so
I'm done with it and getting back to work.  It is possible I (or someone
in my situation) might remember to try to replicate and debug this
problem further for everyone, on a VM at home, on our own time. But
Canonical cannot depend on this happening. It's a "bad administrator
experience" issue that should be dealt with like any other serious bug.

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

Title:
  Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a
  corrupted display

Status in Virtualbox:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed
Status in kbd package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Incomplete

Bug description:
  (Content copied from "Ubuntu 14.10 ISO live boot ends up with a
  corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz)

  Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO 
ends up with a corrupted screen. See the screenshot:
  https://launchpadlibrarian.net/186864347/ubu.png

  Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7)
  fixes the display.

  I think that this might be a problem with resolution setting:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  ```

  After switching back and forth to the tty7 (what fixes the display)
  the log says:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
  00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=720x400
  00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1
  00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler..
  00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768
  00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use 
VGA device content..
  ```

  I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens
  on both of them.

  You can download the ISO images of these two systems here:

   https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10
  -desktop-amd64.iso

   http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-
  gnome-14.10-desktop-amd64.iso

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

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

[Touch-packages] [Bug 1618229] Re: rsyslogd terminal escape sequences injection

[Seth Arnold]

This is a problem with using cat(1) or tail(1) to inspect potentially
malicious files; less(1) does not interpret the control chars by
default, so it's safer to use. Something like:

less +F /path/to/file
will behave similar to:
tail -f /path/to/file

For more information, see:

http://www.openwall.com/lists/oss-security/2015/08/11/8

Thanks

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

Title:
  rsyslogd terminal escape sequences injection

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Hi,

  It seems to me that it is possible to inject terminal escape sequences into 
log files via 
  syslog(3)

  # tail -f /var/log/messages

  Aug 23 13:50:33 ghetto kernel: ACPI Error: Method parse/execution failed 
[\_GPE._L10] 
  (Node 88017b0e47d0), AE_NOT_FOUND (20141107/psparse-536)
  (*) Aug 23 13:50:33 ghetto kernel: ACPI Exception: AE_NOT_FOUND, while 
evaluating GPE 
  method [_L10] (20141107/evgpe-581)

  $ logger `printf 'HELLO\n\033[2AA\033[2B'`

  # tail -f /var/log/messages

  Aug 23 13:50:33 ghetto kernel: ACPI Error: Method parse/execution failed 
[\_GPE._L10] 
  (Node 88017b0e47d0), AE_NOT_FOUND (20141107/psparse-536)
  (*) Aug 23 13:50:33 ghetto kernel: ACPI A_NOT_FOUND, while 
evaluating GPE 
  method [_L10] (20141107/evgpe-581)
  Aug 23 13:50:39 ghetto saken: HELLO

  
  On the (*) line, the escape sequence changed its contents, meaning that an 
unprivileged 
  user can take advantage of this to hide their presence on the system by 
changing 
  legitimate logs, modify a window's title, change background and foreground 
color, etc.

  
  While researching this, I found that rsyslogd has 
"$EscapeControlCharactersOnReceive" 
  which claims that is on by default and that "The intent is to provide a way 
to stop 
  non-printable messages from entering the syslog system as whole."

  On my system, this does not seem to be true, and actually went ahead and 
added 
  "$EscapeControlCharactersOnReceive on" to the /etc/rsyslog.conf file, 
restarted rsyslog 
  and the problem still persists.

  I am using rsyslogd 7.4.8

  Thanks,
  Federico Bento.

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

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

[Touch-packages] [Bug 1618229] Re: rsyslogd terminal escape sequences injection

[Seth Arnold]

** Information type changed from Private Security to Public Security

** Package changed: policykit-1 (Ubuntu) => rsyslog (Ubuntu)

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

Title:
  rsyslogd terminal escape sequences injection

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Hi,

  It seems to me that it is possible to inject terminal escape sequences into 
log files via 
  syslog(3)

  # tail -f /var/log/messages

  Aug 23 13:50:33 ghetto kernel: ACPI Error: Method parse/execution failed 
[\_GPE._L10] 
  (Node 88017b0e47d0), AE_NOT_FOUND (20141107/psparse-536)
  (*) Aug 23 13:50:33 ghetto kernel: ACPI Exception: AE_NOT_FOUND, while 
evaluating GPE 
  method [_L10] (20141107/evgpe-581)

  $ logger `printf 'HELLO\n\033[2AA\033[2B'`

  # tail -f /var/log/messages

  Aug 23 13:50:33 ghetto kernel: ACPI Error: Method parse/execution failed 
[\_GPE._L10] 
  (Node 88017b0e47d0), AE_NOT_FOUND (20141107/psparse-536)
  (*) Aug 23 13:50:33 ghetto kernel: ACPI A_NOT_FOUND, while 
evaluating GPE 
  method [_L10] (20141107/evgpe-581)
  Aug 23 13:50:39 ghetto saken: HELLO

  
  On the (*) line, the escape sequence changed its contents, meaning that an 
unprivileged 
  user can take advantage of this to hide their presence on the system by 
changing 
  legitimate logs, modify a window's title, change background and foreground 
color, etc.

  
  While researching this, I found that rsyslogd has 
"$EscapeControlCharactersOnReceive" 
  which claims that is on by default and that "The intent is to provide a way 
to stop 
  non-printable messages from entering the syslog system as whole."

  On my system, this does not seem to be true, and actually went ahead and 
added 
  "$EscapeControlCharactersOnReceive on" to the /etc/rsyslog.conf file, 
restarted rsyslog 
  and the problem still persists.

  I am using rsyslogd 7.4.8

  Thanks,
  Federico Bento.

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

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

[Touch-packages] [Bug 1618224] [NEW] Single quote character not handled well in associative array index

[Jarno Suni]

Public bug reported:

Say you have script named test.sh in current directory

#!/bin/bash
declare -A a
b="80's"
((++a[$b]))
((++a["$b"]))
[[ $((++a[$b])) ]] || true
[[ $((++a["$b"])) ]] || true
echo ${a["$b"]}
echo ${a[$b]}

It outputs

./test.sh: line 4: ((: ++a[80's]: bad array subscript (error token is "a[80's]")
./test.sh: line 5: ((: ++a[80's]: bad array subscript (error token is "a[80's]")
./test.sh: line 6: ++a[80's]: bad array subscript (error token is "a[80's]")
1
1

Expected output is

4
4

like it is when b is "80s". Note that only the incremention on line 7 of the 
script works.
This bug also happens by bash 4.3-7ubuntu1.5 (Trusty)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 30 00:24:58 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-21 (282 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bash
UpgradeStatus: Upgraded to xenial on 2016-06-24 (66 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Single quote character not handled well in associative array index

Status in bash package in Ubuntu:
  New

Bug description:
  Say you have script named test.sh in current directory

  #!/bin/bash
  declare -A a
  b="80's"
  ((++a[$b]))
  ((++a["$b"]))
  [[ $((++a[$b])) ]] || true
  [[ $((++a["$b"])) ]] || true
  echo ${a["$b"]}
  echo ${a[$b]}

  It outputs

  ./test.sh: line 4: ((: ++a[80's]: bad array subscript (error token is 
"a[80's]")
  ./test.sh: line 5: ((: ++a[80's]: bad array subscript (error token is 
"a[80's]")
  ./test.sh: line 6: ++a[80's]: bad array subscript (error token is "a[80's]")
  1
  1

  Expected output is

  4
  4

  like it is when b is "80s". Note that only the incremention on line 7 of the 
script works.
  This bug also happens by bash 4.3-7ubuntu1.5 (Trusty)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 30 00:24:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (282 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bash
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (66 days ago)

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

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

[Touch-packages] [Bug 1605189] Re: Authentication is required for suspending the system

[Henry J. Douglas]

There's also a message in the upper corner saying, "Power Manager:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Method call timed out."

Using Xubuntu 16.04

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

Title:
  Authentication is required for suspending the system

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspend from the xfce power manager does not work, as a
  window opens and asks for my password. Well, if it wants to suspend
  the system after a given timeout, I cannot enter my password as I'm
  not in front of my system then. Once I'm able to enter my password it
  is too late to run the suspend action.

  The window asking for my password prints:

  Password: 

  Details

  Action: org.freedesktop.login1.suspend
  Vendor: The systemd project

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jul 21 13:13:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-17 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4236ML1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4236ML1
  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:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4236ML1
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1577277] Re: Document Viewer app freezes/crashes on clicking back from pdf files

[Tim Peeters]

Confirmed in image r562 on Krillin.

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

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

Title:
  Document Viewer app freezes/crashes on clicking back from pdf files

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Document Viewer App:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Device: mako
  Channel: rc-proposed

  App freezes every time on clicking back arrow when trying to close pdf files 
and go back to the documents list.
  The only solution seems to be closing the app every time I want to open other 
pdf.
  On some occasions, the app will crash by itself when getting out of an pdf.

  [EDIT]:
  Former DocViewer contributor Stefano Verzegnassi took a look at this bug so 
I'll just paste his response here:

  I've found a few minutes for having a look at this issue, and I guess
  this has nothing to do with Document Viewer. The component which
  causes the issue hasn't received any update since an year.

  The issue in the DocViewer seems to be the same described in bug
  #1568016, which sounds to me as a regression in the UI Toolkit.

  During the last months a lot of regressions have been introduced with any 
UITK update, because critical changes are directly committed to a stable target.
  As long as core apps should always target the latest version of the toolkit, 
it should also be granted that a new toolkit update does not break any core app 
functionality.

  Anyway, since the UITK team is actually rewriting many components, I
  suspect the faulty component of the PDF viewer should be entirely
  rewritten too, since there's a small chance the issue gets fixed
  upstream (and that's what they did with the issue at the link below).

  I'm no more an active contributor of the Ubuntu Document Viewer, and
  whoever will join the team should also take care of fixing this.

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1568016

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

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

[Touch-packages] [Bug 1617415] Re: Menus are jumping up and down when moving mouse

[Launchpad Bug Tracker]

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

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

  [ Alberts Muktupāvels ]
  * Remove box-shadow from .background:backdrop.
  * Fix jumping menu items. (LP: #1617415)

  [ Dmitry Shachnev ]
  * Added styling for gnome-flashback: OSD windows, input source
switching, candidate popups and monitor labels.

 -- Dmitry Shachnev   Mon, 29 Aug 2016 18:42:30
+

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

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

Title:
  Menus are jumping up and down when moving mouse

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  If a menu is opened, when moving the cursor from the menu bar to the
  first menu item, the whole menu moves down for one pixel. The same
  happens when moving the mouse between two menu items separated with a
  separator: when a mouse is on the separator, the whole menu jumps.

  This happens with different menu types: "classic" GTK+ menus, Unity
  global menus and in-title menus.

  A screencast is attached.

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

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

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

[Bastien]

Linux 4.4.0-36-generic
HP x360 Spectre, core i7-5500U, Ubuntu 16.04.1 LTS

When lid is closed, screen is turned off but that is all.
Suspend works from the command line.
Playing with GNOME Tweak, dconf edidor or logind.conf doesn't help.
I don't find dock.0 in /sys/device/platform/.

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

  My System: HP Pavilion dv7.

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

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

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

[Touch-packages] [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

[Launchpad Bug Tracker]

** Branch linked: lp:curtin

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

Title:
  ifupdown does not set ipv6-only large mtu

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  ifupdown changes a device's mtu differently, between "inet" section
  mtu and "inet6" section mtu.  For "inet", ifupdown changes the
  device's mtu, using 'ip link set DEV mtu NNN'.  However for "inet6",
  ifupdown changes the interface's IPv6 mtu, using 'sysctl -q -e -w
  net.ipv6.conf.DEV.mtu=NNN'.

  The problem is that a device's ipv6 mtu cannot be larger than the
  device mtu.  Normally this is not a problem; the main reason a device
  needs a separate ipv6 mtu is to support ipv6 tunneling inside ipv4
  (e.g. 6in4 or 6rd), so ifupdown would also have a ipv4 "inet" section
  that contained a larger mtu (or, the ipv6 section would have a lower-
  than-default mtu).

  But, in the case of an interface that is configured only for ipv6
  *and* large frames (e.g. 9000 mtu), there is only an "inet6" section
  in the ifupdown config, and so ifupdown fails to set the device's mtu,
  which causes its attempt to set the ipv6 mtu to fail.

  I believe the correct behavior is for ifupdown to check if there is
  any "inet" config section for the same device as the "inet6" section,
  and if there is not then it should change the device mtu as well as
  the ipv6 mtu.  Additionally, the "inet6" configuration must be done
  after the "inet" configuration for the same device, since the ipv6 mtu
  can't be higher than the device mtu.

  I don't see any easy way to add that logic to inet6.defn, however...

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

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

[Touch-packages] [Bug 1577277] Re: Document Viewer app freezes/crashes on clicking back from pdf files

[Tim Peeters]

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

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

Title:
  Document Viewer app freezes/crashes on clicking back from pdf files

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Document Viewer App:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Device: mako
  Channel: rc-proposed

  App freezes every time on clicking back arrow when trying to close pdf files 
and go back to the documents list.
  The only solution seems to be closing the app every time I want to open other 
pdf.
  On some occasions, the app will crash by itself when getting out of an pdf.

  [EDIT]:
  Former DocViewer contributor Stefano Verzegnassi took a look at this bug so 
I'll just paste his response here:

  I've found a few minutes for having a look at this issue, and I guess
  this has nothing to do with Document Viewer. The component which
  causes the issue hasn't received any update since an year.

  The issue in the DocViewer seems to be the same described in bug
  #1568016, which sounds to me as a regression in the UI Toolkit.

  During the last months a lot of regressions have been introduced with any 
UITK update, because critical changes are directly committed to a stable target.
  As long as core apps should always target the latest version of the toolkit, 
it should also be granted that a new toolkit update does not break any core app 
functionality.

  Anyway, since the UITK team is actually rewriting many components, I
  suspect the faulty component of the PDF viewer should be entirely
  rewritten too, since there's a small chance the issue gets fixed
  upstream (and that's what they did with the issue at the link below).

  I'm no more an active contributor of the Ubuntu Document Viewer, and
  whoever will join the team should also take care of fixing this.

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1568016

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

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

Re: [Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Mark Stosberg]

Thanks for the response, Martin.

Where will the public policy discuss take place?

Perhaps one possibility for a interim solution is for rsyslog to log to
journald by default instead of to disk by default and otherwise
maximally direct services to log into journald instead of rsyslog. 

 Mark

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

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

[Luke Yelavich]

Ok, another package is on its way with another patch enabled.

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Jared Biel]

We have some servers that host git mirrors accessed via SSH that are
affected by this. Restarting systemd-logind via cron every 5 minutes
works for us (no full system restart necessary.)

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

Re: [Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Bernard Sabathé]

Thank you.


Le 29/08/2016 à 21:27, Mohammed Alkindi a écrit :
> when I wrote
> sudo apt remove account-plugin-google unity-scope-gdrive 
> kde-telepathy-minimal kde-telepathy
>
> The problem solved and the setup continued!
>

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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

[Touch-packages] [Bug 1618201] [NEW] deadlock in lttng_ust_init

[Daniel d'Andrada]

Public bug reported:

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

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

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

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

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

Title:
  deadlock in lttng_ust_init

Status in ust package in Ubuntu:
  New

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

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

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

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

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

[Touch-packages] [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

[Ryan Harper]

** Branch linked: lp:~raharper/curtin/trunk.more-ipv6

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

Title:
  ifupdown does not set ipv6-only large mtu

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  ifupdown changes a device's mtu differently, between "inet" section
  mtu and "inet6" section mtu.  For "inet", ifupdown changes the
  device's mtu, using 'ip link set DEV mtu NNN'.  However for "inet6",
  ifupdown changes the interface's IPv6 mtu, using 'sysctl -q -e -w
  net.ipv6.conf.DEV.mtu=NNN'.

  The problem is that a device's ipv6 mtu cannot be larger than the
  device mtu.  Normally this is not a problem; the main reason a device
  needs a separate ipv6 mtu is to support ipv6 tunneling inside ipv4
  (e.g. 6in4 or 6rd), so ifupdown would also have a ipv4 "inet" section
  that contained a larger mtu (or, the ipv6 section would have a lower-
  than-default mtu).

  But, in the case of an interface that is configured only for ipv6
  *and* large frames (e.g. 9000 mtu), there is only an "inet6" section
  in the ifupdown config, and so ifupdown fails to set the device's mtu,
  which causes its attempt to set the ipv6 mtu to fail.

  I believe the correct behavior is for ifupdown to check if there is
  any "inet" config section for the same device as the "inet6" section,
  and if there is not then it should change the device mtu as well as
  the ipv6 mtu.  Additionally, the "inet6" configuration must be done
  after the "inet" configuration for the same device, since the ipv6 mtu
  can't be higher than the device mtu.

  I don't see any easy way to add that logic to inet6.defn, however...

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

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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Martin Pitt]

This needs a public policy discussion first: We will not enable
persistent journal without also removing rsyslog by default, as we
really don't want to log everything twice.

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

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

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1471790] Re: Audiotrak MAYA U5 not fully supported

[Norbert Langner]

Unfortunately, above method does not work for me. After that LED
indicator is blinking repeatedly, but sometimes I still can't hear any
sound - it is needed to unplug and plug MAYA again several times.

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

Title:
  Audiotrak MAYA U5 not fully supported

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a problem with usb-audio Audiotrack Maya U5 on Ubuntu 14.04.2:

  Steps to reproduce:
  1) Try to play a sound
  2) You can either get a sound out of the speakers or not which is random
  3) Stop the sound and wait ~5 seconds for the device to suspend (light on 
device stops blinking)
  4) You are back at point 2

  Another way to reproduce it:
  1) Try to play a sound
  2) If the sound is not playing open pavucontrol try to change profile between 
analog stereo output and digital stereo output several times until it “clicks” 
and you get a sound through one of this outputs

  With analog speakers connected sound should be playing only with
  analog output and it should not reset outputs upon device suspend.

  This problem started after I upgraded firmware from Audiotrack's
  website (http://audiotrack.net/en/download/421) to RELEASE 10. I tried
  to downgrade firmware but with no luck.

  Other problem is that there are no inputs – either digital, line in or
  microphone in pavucotrol.

  I tried several kernels from 3.2 to 4.1 and this bug is present at all
  that I tested.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   drkp   1515 F...m pulseaudio
   /dev/snd/controlC1:  drkp   1515 F pulseaudio
   /dev/snd/controlC0:  drkp   1515 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  6 13:49:07 2015
  InstallationDate: Installed on 2015-07-01 (4 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Q77M-D2H
  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.:bvrF1:bd04/19/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H: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.

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

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

[Touch-packages] [Bug 1618188] [NEW] systemd journal should be persistent by default: /var/log/journal should be created

[Mark Stosberg]

Public bug reported:

After upgrading 14.04 -> 16.04, key services are now running on systemd
and using the systemd journal for logging. In 14.04, key system logs
like /var/log/messages and /var/log/syslog were persistent, but after
the upgrade to 16.04 there has a been a regression of sorts: Logs sent
to systemd's journald are now being thrown away during reboots.

This behavior is controlled by the `Storage=` option in
`/etc/systemd/journald.conf`. The default setting is `Storage=auto`
which will persist logs in `/var/log/journal/`, *only if the directory
already exists*. But the directory was not created as part of the 14.04
-> 16.04 upgrade, so logging was being lost for a while before I
realized what was happening.

This issue could be solved by either creating /var/log/journal or
changing the default Storage behavior to `Storage=persistent`, which
would create the directory if need be.

## Related reference

 * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
 * [User wonders where to find logs from previous boots, unaware that the logs 
were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

## Recommended fix

Restoring persistent logging as the default is recommended.

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

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1614215] Re: "md5sums differ" message seems to indicate an install problem

[Chris J Arges]

Hello Mike, or anyone else affected,

Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.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!

** Changed in: apparmor (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1614215

Title:
  "md5sums differ" message seems to indicate an install problem

Status in AppArmor:
  Invalid
Status in Ubuntu GNOME:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Confusing output from a diff command executed during the apparmor update 
process leaves users concerned about the state of their system.

  [Test Case]
  1. Make sure that apparmor 2.10.95-0ubuntu2 from the -release pocket is 
installed

  2. Update to the apparmor package in -proposed

  3. Look at the output during the update process to verify that the
  following message is *not* printed:

Files /var/lib/dpkg/info/apparmor.md5sums and
  /var/lib/apparmor/profiles/.apparmor.md5sums differ

  [Regression Potential]
  Considered to be extremely low. The change is a one-liner that pipes the 
stdout of diff command to /dev/null (the -q option of diff is not sufficient).

  [Original description]

  Upon applying the latest Ubuntu routine-update, I observed these
  messages:

  Setting up apparmor (2.10.95-0ubuntu2.2) ...
  Installing new version of config file 
/etc/apparmor.d/abstractions/dbus-session-strict ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Files /var/lib/dpkg/info/apparmor.md5sums and 
/var/lib/apparmor/profiles/.apparmor.md5sums differ

  "The reason why I am filing a bug report" is the LAST line.  I presume
  that if md5sums do not agree, something was probably done improperly
  in preparing this particular software-update blast.

  However, in-passing, I would also point out line #3, about "start and
  stop actions no longer supported." That seems to me to be something
  (of much less importance, obviously) that might have been overlooked.
  (I've seen =that= message for some time now.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug 17 14:22:55 2016
  InstallationDate: Installed on 2016-03-02 (168 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: apparmor
  Syslog:
   Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is 
enabled
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago)

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

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

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Chris J Arges]

Hello Sebastien, or anyone else affected,

Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.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!

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

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in im-config source package in Xenial:
  In Progress
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in progress. Currently the change should not
  regress snapdsbehavior due to other issues surrounding using ibus
  unrelated to security policy.

  = SRU apparmor =
  [Impact]
  The upload that adjusts ibus-daemon to start with "--address 
'unix:tmpdir=/tmp/ibus'" causes the ibus AppArmor abstraction to no longer be 
sufficient due to the lack of a rule for the new socket path. This upload adds 
such a rule.

  [Test Case]
  1. Start a unity session after updating to the im-config package in 

[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Mohammed Alkindi]

when I wrote 
sudo apt remove account-plugin-google unity-scope-gdrive kde-telepathy-minimal 
kde-telepathy

The problem solved and the setup continued!

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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

[Touch-packages] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

[Launchpad Bug Tracker]

This bug was fixed in the package sudo - 1.8.16-0ubuntu1.2

---
sudo (1.8.16-0ubuntu1.2) xenial; urgency=medium

  * debian/sudoers:
- include /snap/bin in the secure_path (LP: #1595558)

 -- Michael Vogt   Mon, 15 Aug 2016 18:10:18
+0200

** Changed in: sudo (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  Fix Released

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

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

[Touch-packages] [Bug 1595558] Update Released

[Chris J Arges]

The verification of the Stable Release Update for sudo has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  Fix Committed

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

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

[Touch-packages] [Bug 1615099] Re: SRU of LXC 2.0.4 (upstream bugfix release)

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.4-0ubuntu1~ubuntu16.04.2

---
lxc (2.0.4-0ubuntu1~ubuntu16.04.2) xenial; urgency=medium

  * Cherry-pick from upstream (fixes checkpoint/restore regression):
- 0003-c-r-use-proc-self-tid-children-instead-of-pidfile.patch
- 0004-c-r-Fix-pid_t-on-some-arches.patch

lxc (2.0.4-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.4) (LP: #1615099):
- core: Add a prefix to the lxc.pc
- core: Add flag in mount_entry to skip NODEV in case of a
  persistent dev entry
- core: Add missing cgroup namespace to ns_info struct
- core: attach: setns instead of unshare in lxc-attach
- core: bdev: Add subdirectories to search path
- core: bdev: Be smarter about btrfs subvolume detection
- core: cgfsng: Don't pre-calculate path
- core: cgfsng: Fix is_lxcfs() and is_cgroupfs()
- core: cgroups: Move cgroup files to common subfolder
- core: conf: Set pty_info to NULL after free
- core: Detect if we should send SIGRTMIN+3
- core: Replace readdir_r() with readdir()
- core: Set up MTU for vlan-type interfaces.
- core: tools, tests: Reorganize repo
- c/r: Add support for CRIU's --action-script
- c/r: Add support for ghost-limit in CRIU
- c/r: Drop in-flight connections during CRIU dump
- c/r: Initialize migrate_opts properly
- c/r: Make local function static
- c/r: Replace tmpnam() with mkstemp()
- c/r: Store criu version
- c/r: Use PRIu64 format specifier
- doc: Fix typo found by lintian
- doc: Update Japanese lxc-attach(1)
- doc: Update lxc-attach(1)
- lxc-attach: Add -f option (rcfile)
- lxc-attach: Cleanup whitespaces
- lxc-create: Add missing newline in output
- lxc-ls: Use correct runtime path
- templates: alpine: Add support for new arch
- templates: alpine: Mount tmpfs under /run
- templates: debian: Add more quotes to variables (at least $rootfs
  should now be covered)
- templates: debian: Avoid noisy perl warnings caused by missing locales
- templates: debian: fix regression when creating wheezy containers
- templates: debian: Make shellcheck (Ubuntu: 0.3.7-5 amd64) most
  possible happy
- tests: Add unit tests for lxc_string_in_array()
- tests: Add unit tests for lxc_string_replace()
  * Cherry-pick from upstream (for 4.6 kernel):
- 0002-bdev-use-correct-overlay-module-name
  * Sync packaging with yakkety:
- Tweak debian/tests/exercise to skip lxc-test-ubuntu on yakkety
- Build-depend on libgnutls28-dev rather than libgnutls-dev

 -- Stéphane Graber   Fri, 26 Aug 2016 16:31:18
-0400

** Changed in: lxc (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  SRU of LXC 2.0.4 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  LXC upstream released LXC 2.0.4 as a bugfix release with following changelog:
  - core: Add a prefix to the lxc.pc
  - core: Add flag in mount_entry to skip NODEV in case of a
persistent dev entry
  - core: Add missing cgroup namespace to ns_info struct
  - core: attach: setns instead of unshare in lxc-attach
  - core: bdev: Add subdirectories to search path
  - core: bdev: Be smarter about btrfs subvolume detection
  - core: cgfsng: Don't pre-calculate path
  - core: cgfsng: Fix is_lxcfs() and is_cgroupfs()
  - core: cgroups: Move cgroup files to common subfolder
  - core: conf: Set pty_info to NULL after free
  - core: Detect if we should send SIGRTMIN+3
  - core: Replace readdir_r() with readdir()
  - core: Set up MTU for vlan-type interfaces.
  - core: tools, tests: Reorganize repo
  - c/r: Add support for CRIU's --action-script
  - c/r: Add support for ghost-limit in CRIU
  - c/r: Drop in-flight connections during CRIU dump
  - c/r: Initialize migrate_opts properly
  - c/r: Make local function static
  - c/r: Replace tmpnam() with mkstemp()
  - c/r: Store criu version
  - c/r: Use PRIu64 format specifier
  - doc: Fix typo found by lintian
  - doc: Update Japanese lxc-attach(1)
  - doc: Update lxc-attach(1)
  - lxc-attach: Add -f option (rcfile)
  - lxc-attach: Cleanup whitespaces
  - lxc-create: Add missing newline in output
  - lxc-ls: Use correct runtime path
  - templates: alpine: Add support for new arch
  - templates: alpine: Mount tmpfs under /run
  - templates: debian: Add more quotes to variables (at least $rootfs
should now be covered)
  - templates: debian: Avoid noisy perl warnings caused by missing locales
  - 

[Touch-packages] [Bug 1618166] [NEW] /usr/bin/content-hub-service:11:QtPrivate::RefCount::ref:QString::QString:com::ubuntu::content::detail::Service::handle_exports:com::ubuntu::content::detail::Servi

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding content-hub.  This problem was most recently seen with version
0.1+15.04.20160825-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/f5464817b0af0222dfbf732f013f63c8b9df0813
contains more details.

** Affects: content-hub (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/bin/content-hub-
  
service:11:QtPrivate::RefCount::ref:QString::QString:com::ubuntu::content::detail::Service::handle_exports:com::ubuntu::content::detail::Service::qt_static_metacall:QMetaObject::activate

Status in content-hub package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding content-hub.  This problem was most recently seen with
  version 0.1+15.04.20160825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f5464817b0af0222dfbf732f013f63c8b9df0813
  contains more details.

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

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

[Touch-packages] [Bug 1615099] Re: SRU of LXC 2.0.4 (upstream bugfix release)

[Stéphane Graber]

I had production servers running this for the past week, all good.

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

Title:
  SRU of LXC 2.0.4 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream released LXC 2.0.4 as a bugfix release with following changelog:
  - core: Add a prefix to the lxc.pc
  - core: Add flag in mount_entry to skip NODEV in case of a
persistent dev entry
  - core: Add missing cgroup namespace to ns_info struct
  - core: attach: setns instead of unshare in lxc-attach
  - core: bdev: Add subdirectories to search path
  - core: bdev: Be smarter about btrfs subvolume detection
  - core: cgfsng: Don't pre-calculate path
  - core: cgfsng: Fix is_lxcfs() and is_cgroupfs()
  - core: cgroups: Move cgroup files to common subfolder
  - core: conf: Set pty_info to NULL after free
  - core: Detect if we should send SIGRTMIN+3
  - core: Replace readdir_r() with readdir()
  - core: Set up MTU for vlan-type interfaces.
  - core: tools, tests: Reorganize repo
  - c/r: Add support for CRIU's --action-script
  - c/r: Add support for ghost-limit in CRIU
  - c/r: Drop in-flight connections during CRIU dump
  - c/r: Initialize migrate_opts properly
  - c/r: Make local function static
  - c/r: Replace tmpnam() with mkstemp()
  - c/r: Store criu version
  - c/r: Use PRIu64 format specifier
  - doc: Fix typo found by lintian
  - doc: Update Japanese lxc-attach(1)
  - doc: Update lxc-attach(1)
  - lxc-attach: Add -f option (rcfile)
  - lxc-attach: Cleanup whitespaces
  - lxc-create: Add missing newline in output
  - lxc-ls: Use correct runtime path
  - templates: alpine: Add support for new arch
  - templates: alpine: Mount tmpfs under /run
  - templates: debian: Add more quotes to variables (at least $rootfs
should now be covered)
  - templates: debian: Avoid noisy perl warnings caused by missing locales
  - templates: debian: fix regression when creating wheezy containers
  - templates: debian: Make shellcheck (Ubuntu: 0.3.7-5 amd64) most
possible happy
  - tests: Add unit tests for lxc_string_in_array()
  - tests: Add unit tests for lxc_string_replace()

  
  Just like Ubuntu itself, upstream releases long term support releases, as is 
2.0 and then periodic point releases including all the accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Yakkety and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

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

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

[Touch-packages] [Bug 1615099] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU of LXC 2.0.4 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream released LXC 2.0.4 as a bugfix release with following changelog:
  - core: Add a prefix to the lxc.pc
  - core: Add flag in mount_entry to skip NODEV in case of a
persistent dev entry
  - core: Add missing cgroup namespace to ns_info struct
  - core: attach: setns instead of unshare in lxc-attach
  - core: bdev: Add subdirectories to search path
  - core: bdev: Be smarter about btrfs subvolume detection
  - core: cgfsng: Don't pre-calculate path
  - core: cgfsng: Fix is_lxcfs() and is_cgroupfs()
  - core: cgroups: Move cgroup files to common subfolder
  - core: conf: Set pty_info to NULL after free
  - core: Detect if we should send SIGRTMIN+3
  - core: Replace readdir_r() with readdir()
  - core: Set up MTU for vlan-type interfaces.
  - core: tools, tests: Reorganize repo
  - c/r: Add support for CRIU's --action-script
  - c/r: Add support for ghost-limit in CRIU
  - c/r: Drop in-flight connections during CRIU dump
  - c/r: Initialize migrate_opts properly
  - c/r: Make local function static
  - c/r: Replace tmpnam() with mkstemp()
  - c/r: Store criu version
  - c/r: Use PRIu64 format specifier
  - doc: Fix typo found by lintian
  - doc: Update Japanese lxc-attach(1)
  - doc: Update lxc-attach(1)
  - lxc-attach: Add -f option (rcfile)
  - lxc-attach: Cleanup whitespaces
  - lxc-create: Add missing newline in output
  - lxc-ls: Use correct runtime path
  - templates: alpine: Add support for new arch
  - templates: alpine: Mount tmpfs under /run
  - templates: debian: Add more quotes to variables (at least $rootfs
should now be covered)
  - templates: debian: Avoid noisy perl warnings caused by missing locales
  - templates: debian: fix regression when creating wheezy containers
  - templates: debian: Make shellcheck (Ubuntu: 0.3.7-5 amd64) most
possible happy
  - tests: Add unit tests for lxc_string_in_array()
  - tests: Add unit tests for lxc_string_replace()

  
  Just like Ubuntu itself, upstream releases long term support releases, as is 
2.0 and then periodic point releases including all the accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Yakkety and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

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

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

[Touch-packages] [Bug 1595695] Re: bluetooth indicator disappears every time bluetooth is being turned off

[Launchpad Bug Tracker]

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

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  bluetooth indicator disappears every time bluetooth is being turned
  off

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

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

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

[Touch-packages] [Bug 1618152] [NEW] NO sound after 16.04 upgrade & subsequent fresh install

[William Burden]

Public bug reported:

Sound settings used to offer "Play analog sound and allow 5.1 surround
sound through my Logitech X-540 5.1 Surround Sound Speaker System. 16.04
upgrade now only displays: Digital Output (S/PDIF) & Headphones  and
fresh install offered same.

sudo lspci displays (audio only):

00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
...
01:05.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RS880 HDMI Audio 
[Radeon HD 4200 Series]


aplay -l prints:

 List of PLAYBACK Hardware Devices 
card 0: MID [HDA Intel MID], device 0: ALC889 Analog [ALC889 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 1: ALC889 Digital [ALC889 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

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

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

Title:
  NO sound after 16.04 upgrade & subsequent fresh install

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound settings used to offer "Play analog sound and allow 5.1 surround
  sound through my Logitech X-540 5.1 Surround Sound Speaker System.
  16.04 upgrade now only displays: Digital Output (S/PDIF) & Headphones
  and fresh install offered same.

  sudo lspci displays (audio only):

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
  ...
  01:05.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RS880 HDMI Audio 
[Radeon HD 4200 Series]

  
  aplay -l prints:

   List of PLAYBACK Hardware Devices 
  card 0: MID [HDA Intel MID], device 0: ALC889 Analog [ALC889 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: MID [HDA Intel MID], device 1: ALC889 Digital [ALC889 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Timo Jyrinki]

My builds were missing this which explains the Id mismatch:
https://codereview.qt-project.org/#/c/145358/

https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-038/+packages is now updated with all of
these.

Currently I'm getting:

$ ./inputinfo 
0
Aborted (core dumped)

and:

$ QT_QPA_PLATFORM=ubuntumirclient qmlscene 
--desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop 
qml-inputinfo.qml 
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
ubuntumirclient: Got invalid serialized mime data. Ignoring it.
qml: number of mouse and keyboard devices: 0
qml: row count 0

So no devices for some reason but also at least more output and less
crashes.

Right now tested on xenial (staging channels) only.

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

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

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

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

[Touch-packages] [Bug 1612708] Re: Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

[prof2004]

Reading the bugs around colord, it seams to me, that this error is not related 
to colord.
It is most propably a problem of gvfs.

I will try to link this bug to gvfs. If there is any operator available,
pls support to re-link this bug to gvfs.

It is a critical error, because using the symbolic links is important for using 
the system.
You can find work arounds, but I am thinking about downgrading to ubuntu 14.04 
LTS.

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

Title:
  Symbolic Link does not work in 16.04 LTS as in 14.04 LTS

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1 LTS

  colord:
Installiert:   1.2.12-1ubuntu1
Installationskandidat: 1.2.12-1ubuntu1
Versionstabelle:
   *** 1.2.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Under Ubuntu 14.04 LTS I have created NAS access by using 'gvfs-mount
  smb://nasdo/public'. It is linked to '/run/user/1000/gvfs/ als smb-
  share:server=nasdo,share=public' and I have created a Symbolic Link to
  this point with 'ln -s /run/user/1000/gvfs/smb-
  share\:server\=nasdo\,share\=public ~/nasdo_public'. Using this link
  folders, and files on the NAS have been accessable with r/w from
  Ubuntu 14.04 LTS. This is, what I expect from 16.04, too.

  Since I have upgraded to ubuntu 16.04 LTS a few days ago, all the
  links seem to be the same, but opening a file does not work. It comes
  to an input/output error. I can use the links to folders to navigate,
  but there is no chance to open e.g. an LibreOffice Calc Sheet, nor do
  I have access to mail folder via Thunderbird.

  Using gvfs-mount creates a shared folder in Nautilus called public.
  Using this way to access the NAS, and open the Calc file works with
  ubuntu 16.04 LTS fine.

  Locking to the syslog while trying to open a file creates the following 
entries:
  Aug 12 16:47:19 UDO systemd[1]: Started Hostname Service.
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:22 UDO org.gtk.vfs.Daemon[3843]: ** (process:8645): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (gvfsd:3924): WARNING **: 
dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Empfangen der 
Freigabenliste vom Server ist gescheitert: Verbindungsaufbau abgelehnt
  Aug 12 16:47:25 UDO org.gtk.vfs.Daemon[3843]: ** (process:8663): WARNING **: 
Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: 
Der angegebene Ort ist nicht eingehängt
  Aug 12 16:47:48 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:47:48 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8722]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:50:15 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8842]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO systemd[1]: Started CUPS Scheduler.
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:54:32 UDO colord[2727]: (colord:2727): Cd-WARNING **: failed to get 
session [pid 8936]: Kein passendes Gerät bzw. keine passende Adresse gefunden
  Aug 12 16:55:01 UDO dbus[2427]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
  Aug 12 16:55:01 UDO systemd[1]: Starting Hostname Service...
  Aug 12 16:55:01 UDO dbus[2427]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Aug 12 16:55:01 UDO systemd[1]: Started Hostname Service.

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

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

[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

[prof2004]

I am running ubuntu 16.04.1 LTS, all updates applied until today,
and have this issue as well.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1618077] Re: [Lenovo ThinkPad T520] Regression: cannot set up 3 display configuration any more (Optimus)

[Christopher M. Penalver]

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

As per http://support.lenovo.com/us/en/products/Laptops-and-
netbooks/ThinkPad-T-Series-
laptops/ThinkPad-T520?tabName=Downloads=Mast:SubNav:Support:Drivers%20and%20Software|Drivers%20and%20Software=false
an update to your computer's buggy, insecure, and outdated BIOS is
available (1.45). When you update to this following
https://help.ubuntu.com/community/BIOSUpdate how does this improve the
situation?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new report.

It is most helpful that after the BIOS is updated, if the problem is still 
reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on how this improves the 
situation.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your help.

** Summary changed:

- follow-up to  [Lenovo ThinkPad W530] Regression: cannot set up 3 display 
configuration any more (Optimus) #1556459
+ [Lenovo ThinkPad T520] Regression: cannot set up 3 display configuration any 
more (Optimus)

** Description changed:

- as requested in #1556459
- 
- this is the bug created by "ubuntu-bug xorg" with xdiagnose installed
- 
- shortly after trying to enable the 3rd monitor and the error showed
+ Shortly after trying to enable the 3rd monitor and the error showed.
  
  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:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 29 16:37:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 5.0.24, 4.4.0-28-generic, x86_64: installed
-  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-28-generic, x86_64: installed
+  virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
+  virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d1]
-  NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d1]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d1]
+  NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d1]
  InstallationDate: Installed on 2016-02-07 (203 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  LightdmDisplayLog:
-  Cannot do multiple crtcs without X server dirty tracking 2 interface
-  randr: failed to set shadow slave pixmap
-  Cannot do multiple crtcs without X server dirty tracking 2 interface
-  randr: failed to set shadow slave pixmap
+  Cannot do multiple crtcs without X server dirty tracking 2 interface
+  randr: failed to set shadow slave pixmap
+  Cannot do multiple crtcs without X server dirty tracking 2 interface
+  randr: failed to set shadow slave pixmap
  MachineType: LENOVO 42435HG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=88e9500d-048c-4021-af00-6403ffc0c05e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42435HG
  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: 

[Touch-packages] [Bug 1581560] Re: system crash when attaching external display

[Christopher M. Penalver]

** Attachment removed: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581560/+attachment/4729829/+files/dmesg.log

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

Title:
  system crash when attaching external display

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes
  and reboots when I attach an external display.

  Process: 
  -  put laptop to sleep.
  - come into work the next day
  - open up laptop
  - plug in external display
  - observe bug

  Expected behavior: I can attach the external display
  Observed behavior: system shows black screen on both laptop and display and 
after a minute or two reboots.  Laptop drives external display fine after 
reboot.

  I ssh to the laptop from another machine and monitored
  /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors.  All I
  see in those files before the lockup is this, from Xorg.0.log:

  [ 34289.447] (II) intel(0): Enabled output DP1-8
  [ 34289.448] (II) intel(0): Enabled output DP1-1
  [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440
  [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 
0,
  (0, 0), rotation normal, reflection none

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 09:24:07 2016
  DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
  InstallationDate: Installed on 2015-09-10 (245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BS0031US
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago)
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BS0031US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BS0031US
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  drirc:
   
  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 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 13 09:04:56 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4669 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

[Touch-packages] [Bug 1474563] Re: 1:15/1:16 fails to report support for nvidia 173, 304 have terminated

[Christopher M. Penalver]

Galen Thurber, unfortunately, it appears you aren't following the
directions in
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/comments/1 .
Could you please make a comment specifically to respond to this?

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

Title:
  1:15/1:16 fails to report support for nvidia 173,304 have terminated

Status in xorg package in Ubuntu:
  Expired

Bug description:
  using several hardware configurations, the conclusion is that xorg
  versions above 1:12 fail to support legacy drivers such as 173, 304

  therefore it should be reported in release notes for users of such hardware 
that they will be unable to use hardware 3D acceleration
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-06-24 (1137 days ago)
  InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Tags:  trusty
  Uname: Linux 3.13.0-93-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-04-21 (471 days ago)
  UserGroups: adm cdrom debian-tor dialout dip disk kismet lp lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-06-24 (1161 days ago)
  InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
  Tags:  trusty
  Uname: Linux 3.13.0-95-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-04-21 (494 days ago)
  UserGroups: adm cdrom debian-tor dialout dip disk kismet lp lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1599952] Re: Blurred images with kernels after 4.2.x

[Christopher M. Penalver]

RD, it is most helpful if your testing results are from Ubuntu
specifically (not derivatives, etc.).

To advise, Trusty with the original 3.13 kernel is fully supported as
outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack . This
would also help here as you would have a working environment to perform
tests from.

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

Title:
  Blurred images with kernels after 4.2.x

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Have used Ubuntu or its flavors for 3 years with no issues on this
  machine. Installed Ubuntu 16.04 64-bit lts, and successively xubuntu
  16.04, ubuntuMATE 16.04, and lubuntu 16.04. Each installed, but with
  blurred images.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-07-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6850
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic 
root=UUID=30188e44-b1e6-4cdc-bd16-62f107d213a7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6850
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd12/21/2011:svnASUSTeKComputerINC.:pnCM6850:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM6850:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6850
  dmi.product.version: System Version
  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

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

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

Re: [Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

[David Barth]

Thanks Martin

On Mon, Aug 29, 2016 at 2:11 PM, Martin Pitt 
wrote:

> g-c-signon now has a higher version in yakkety, resetting to v-needed.
>
> ** Tags removed: verification-failed
> ** Tags added: verification-needed
>
> ** Changed in: gnome-control-center-signon (Ubuntu Yakkety)
>Status: In Progress => Fix Released
>
> ** Changed in: account-plugins (Ubuntu Yakkety)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1565772
>
> Title:
>   [SRU] Allow plugins to decide which username to set on new accounts
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions
>

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Fix Committed
Status in gnome-control-center-signon source package in Xenial:
  Fix Committed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

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

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

[Touch-packages] [Bug 1609367] Re: ifupdown does not set ipv6-only large mtu

[Dan Streetman]

> While we could see about getting the script included in yakkety (or y+1);
> curtin will still need to
> handle this unless we want to SRU ifdowndown in precise, trusty and
> xenial. This has an enormous
> impact; so it's not something we should take lightly.

As long as curtin handles it correctly, I don't see any need to SRU
ifupdown; just adding the scripts in y and forward should be enough.
Anyone manually configuring ifupdown in X or earlier can manually setup
both inet and inet6 sections to get the mtus right.

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

Title:
  ifupdown does not set ipv6-only large mtu

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  ifupdown changes a device's mtu differently, between "inet" section
  mtu and "inet6" section mtu.  For "inet", ifupdown changes the
  device's mtu, using 'ip link set DEV mtu NNN'.  However for "inet6",
  ifupdown changes the interface's IPv6 mtu, using 'sysctl -q -e -w
  net.ipv6.conf.DEV.mtu=NNN'.

  The problem is that a device's ipv6 mtu cannot be larger than the
  device mtu.  Normally this is not a problem; the main reason a device
  needs a separate ipv6 mtu is to support ipv6 tunneling inside ipv4
  (e.g. 6in4 or 6rd), so ifupdown would also have a ipv4 "inet" section
  that contained a larger mtu (or, the ipv6 section would have a lower-
  than-default mtu).

  But, in the case of an interface that is configured only for ipv6
  *and* large frames (e.g. 9000 mtu), there is only an "inet6" section
  in the ifupdown config, and so ifupdown fails to set the device's mtu,
  which causes its attempt to set the ipv6 mtu to fail.

  I believe the correct behavior is for ifupdown to check if there is
  any "inet" config section for the same device as the "inet6" section,
  and if there is not then it should change the device mtu as well as
  the ipv6 mtu.  Additionally, the "inet6" configuration must be done
  after the "inet" configuration for the same device, since the ipv6 mtu
  can't be higher than the device mtu.

  I don't see any easy way to add that logic to inet6.defn, however...

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

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

[Touch-packages] [Bug 1617693] Re: package evolution-data-server 3.21.90-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/systemd/user/evolution-addressbook-factory.service', which is

[Jeremy Bicha]

The issue is that you used the GNOME3 Staging PPA for Xenial. As soon as
yakkety opened up, you upgraded to yakkety keeping the GNOME 3.20
packages but without the GNOME3 PPAs.

The PPA has a note that you should run ppa-purge prior to upgrading to a new 
Ubuntu version:
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/

The systemd file was moved in this version. I didn't notice at the time that 
the PPA had installed the file in a different package than Debian did.
evolution-data-server - 3.20.3-1ubuntu1~xenial1 jbicha  2016-06-07

Had this issue been reported sooner (like in June), I would have added a
Breaks/Replaces for the move. By now, nearly everyone using the old
version should have upgraded already so I'm not sure it's necessary now.
Because Ubuntu 16.04 is an LTS, we'd have to keep the Breaks/Replaces
until 18.04 if we did add them.

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

Title:
  package evolution-data-server 3.21.90-0ubuntu2 failed to
  install/upgrade: trying to overwrite '/usr/lib/systemd/user/evolution-
  addressbook-factory.service', which is also in package evolution-data-
  server-common 3.20.2-0ubuntu1~xenial1

Status in evolution-data-server package in Ubuntu:
  Invalid

Bug description:
  upgrade to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: evolution-data-server 3.21.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 27 22:46:34 2016
  DuplicateSignature:
   package:evolution-data-server:3.21.90-0ubuntu2
   Unpacking evolution-data-server (3.21.90-0ubuntu2) over 
(3.20.2-0ubuntu1~xenial1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-DNws2R/149-evolution-data-server_3.21.90-0ubuntu2_amd64.deb
 (--unpack):
trying to overwrite 
'/usr/lib/systemd/user/evolution-addressbook-factory.service', which is also in 
package evolution-data-server-common 3.20.2-0ubuntu1~xenial1
  ErrorMessage: trying to overwrite 
'/usr/lib/systemd/user/evolution-addressbook-factory.service', which is also in 
package evolution-data-server-common 3.20.2-0ubuntu1~xenial1
  InstallationDate: Installed on 2015-10-28 (304 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: evolution-data-server
  Title: package evolution-data-server 3.21.90-0ubuntu2 failed to 
install/upgrade: trying to overwrite 
'/usr/lib/systemd/user/evolution-addressbook-factory.service', which is also in 
package evolution-data-server-common 3.20.2-0ubuntu1~xenial1
  UpgradeStatus: Upgraded to yakkety on 2016-03-12 (169 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1617693/+subscriptions

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

[Touch-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format

[Nathan Rennie-Waldock]

Could policykit be updated if it was ported to mozjs45?
It would be good if we could see it updated eventually as the javascript rules 
are much more flexible (one use would be restricting users to specific domains 
with libvirt).

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

Title:
  New PolicyKit 0.106 changes configuration file format

Status in policykit-1 package in Ubuntu:
  Triaged
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  From the NEWS file:

  This is polkit 0.106. There's a major change in this release which is
  a switch from .pkla files (keyfile-format) to .rules files
  (JavaScript).

  We may want to hold off on the new version because it requires
  rewriting the configuration files, and adds a dependency on mozjs185,
  which will need a MIR (and getting a MIR may be problematic)

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

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

[Touch-packages] [Bug 1617693] Re: package evolution-data-server 3.21.90-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/systemd/user/evolution-addressbook-factory.service', which is

[Jeremy Bicha]

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Invalid

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

Title:
  package evolution-data-server 3.21.90-0ubuntu2 failed to
  install/upgrade: trying to overwrite '/usr/lib/systemd/user/evolution-
  addressbook-factory.service', which is also in package evolution-data-
  server-common 3.20.2-0ubuntu1~xenial1

Status in evolution-data-server package in Ubuntu:
  Invalid

Bug description:
  upgrade to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: evolution-data-server 3.21.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 27 22:46:34 2016
  DuplicateSignature:
   package:evolution-data-server:3.21.90-0ubuntu2
   Unpacking evolution-data-server (3.21.90-0ubuntu2) over 
(3.20.2-0ubuntu1~xenial1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-DNws2R/149-evolution-data-server_3.21.90-0ubuntu2_amd64.deb
 (--unpack):
trying to overwrite 
'/usr/lib/systemd/user/evolution-addressbook-factory.service', which is also in 
package evolution-data-server-common 3.20.2-0ubuntu1~xenial1
  ErrorMessage: trying to overwrite 
'/usr/lib/systemd/user/evolution-addressbook-factory.service', which is also in 
package evolution-data-server-common 3.20.2-0ubuntu1~xenial1
  InstallationDate: Installed on 2015-10-28 (304 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: evolution-data-server
  Title: package evolution-data-server 3.21.90-0ubuntu2 failed to 
install/upgrade: trying to overwrite 
'/usr/lib/systemd/user/evolution-addressbook-factory.service', which is also in 
package evolution-data-server-common 3.20.2-0ubuntu1~xenial1
  UpgradeStatus: Upgraded to yakkety on 2016-03-12 (169 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1617693/+subscriptions

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

[Touch-packages] [Bug 1617297] Re: [windowed mode] camera app buttons wrong rotation

[Andrea Azzarone]

Cosing as per comment #3.

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

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

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

Title:
  [windowed mode] camera app buttons wrong rotation

Status in camera-app package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Enviroment:

  current build number: 175
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-26 12:27:57
  version version: 175
  version ubuntu: 20160826
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Switch to desktop mode when in landscape
  2º Open camera app
  3º Maximize it
  4º Minimize it
  5º Check camera app buttons change from landscape to portrait mode

  Current result: Camera app buttons change from landscape to portrait mode 
when maximize/minimize windows
  Expected result: Camera app buttons should only rotate when device rotates

  Additional info: if you are not able to reproduce it that way, rotate
  Frieza few times when in desktop mode and minimize/maximize the
  window. Video attached

  Logs time stamp: 14:13

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

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

[Touch-packages] [Bug 1617348] Re: unity shell is crashing for apps without icon

[Andrea Azzarone]

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

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

Title:
  unity shell is crashing for apps without icon

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

Bug description:
  Trying to launch a app from terminal that does not contains a "Icon"
  etry on it desktop file causes the shell to crash.

  How to test
  ===

  * Create a desktop entry without the icon entry (something like that):
  [Desktop Entry]
  Name=Sync Monitor
  Comment=Ask for online account authentication if the token expires
  Exec=/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor-helper %u
  Terminal=false
  Type=Application
  Version=1.0
  X-Ubuntu-Gettext-Domain=sync-monitor

  * try to launch it from terminal or url launch:
  /usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor-helper 
--desktop-file-hint=/usr/share/applications/sync-monitor-helper.desktop

  
  Expected
  

  App appears

  Current
  ===

  Shell crashes and go back to login screen.

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

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

[Touch-packages] [Bug 1617435] Re: libmirserver-dev is missing a depends for uuid-dev

[mir-ci-bot]

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

** Changed in: mir
   Status: In Progress => Fix Committed

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

Title:
  libmirserver-dev is missing a depends for uuid-dev

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

Bug description:
  From building qtmir:

  In file included from 
/«BUILDDIR»/qtmir-0.4.8+15.04.20160826.1/src/modules/Unity/Application/mirsurfacemanager.cpp:41:0:
  /usr/include/mirserver/mir/shell/persistent_surface_store.h:25:23: fatal 
error: uuid/uuid.h: No such file or directory
   #include 
 ^

  libmirserver-dev should depend on uuid-dev

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

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

[Touch-packages] [Bug 1618077] [NEW] follow-up to [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus) #1556459

[ligi]

Public bug reported:

as requested in #1556459

this is the bug created by "ubuntu-bug xorg" with xdiagnose installed

shortly after trying to enable the 3rd monitor and the error showed

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:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Aug 29 16:37:10 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 4.4.0-28-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d1]
 NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d1]
InstallationDate: Installed on 2016-02-07 (203 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
LightdmDisplayLog:
 Cannot do multiple crtcs without X server dirty tracking 2 interface
 randr: failed to set shadow slave pixmap
 Cannot do multiple crtcs without X server dirty tracking 2 interface
 randr: failed to set shadow slave pixmap
MachineType: LENOVO 42435HG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=88e9500d-048c-4021-af00-6403ffc0c05e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET56WW (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42435HG
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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn42435HG:pvrThinkPadT520:rvnLENOVO:rn42435HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42435HG
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.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: Fri Aug 26 19:58:54 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 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/1618077

Title:
  follow-up to  [Lenovo ThinkPad W530] Regression: cannot set up 3
  display configuration any more (Optimus) #1556459

Status in xorg package in Ubuntu:
  New

Bug description:
  as requested in #1556459

  this is the bug created by "ubuntu-bug xorg" with xdiagnose installed

  shortly after trying to enable the 3rd monitor and the error showed

  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:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 29 16:37:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-28-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  

[Touch-packages] [Bug 1437305] Re: Wrong date day icon display and one day before events day in month view

[Renato Araujo Oliveira Filho]

** Changed in: qtorganizer5-eds (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Wrong date day icon display and one day before events day in month
  view

Status in Ubuntu Calendar App:
  Fix Released
Status in qtorganizer5-eds package in Ubuntu:
  Fix Released

Bug description:
  All day events display one day too early in month view.

  Create an all day event on 27th March 2015, move month view and the
  dot is against 26th March.  Can be corrected by changing all day event
  to span 27th to 28th March but now event displays over two days on day
  view. Icon displays wrong date: next day date

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

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

[Touch-packages] [Bug 1618078] Re: "Grabbing" mouse cursor not shown when moving window on first press.

[Andrea Azzarone]

Added to Trello: https://trello.com/c/ieIge90r/51-bug-1618078-grabbing-
mouse-cursor-not-shown-when-moving-window-on-first-press

** Branch linked: lp:~azzar1/unity8/dragging-cursor-on-first-press

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

Title:
  "Grabbing" mouse cursor not shown when moving window on first press.

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  To reproduce on an unity8 desktop session:
  1. Open a window
  2. Press on the window decoration to start dragging the window

  Expected behavior:
  The "grabbing" mouse is shown.

  Actual behavior:
  The "grabbing" mouse is now shown until first mouse motion.

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

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

[Touch-packages] [Bug 1433630] Re: I would like to have contact info as part of the keyboard dictionary

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  I would like to have contact info as part of the keyboard dictionary

Status in ubuntu-keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Would be nice to have my contact info present on keyboard predictive
  text.

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

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

[Touch-packages] [Bug 1528058] Re: settings not readable from confined app/scope

[Rodney Dawes]

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

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

Title:
  settings not readable from confined app/scope

Status in Canonical System Image:
  Confirmed
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  The trace-client gsetting does not work and always returns false when
  running under confinement. We need a different way to enable this.

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

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

[Touch-packages] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

[Oliver Grawert]

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

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  Fix Committed

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

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

[Touch-packages] [Bug 1528058] Re: settings not readable from confined app/scope

[Jean-Baptiste Lallement]

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

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

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

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

Title:
  settings not readable from confined app/scope

Status in Canonical System Image:
  Confirmed
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  The trace-client gsetting does not work and always returns false when
  running under confinement. We need a different way to enable this.

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

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

[Touch-packages] [Bug 1618078] [NEW] "Grabbing" mouse cursor not shown when moving window on first press.

[Andrea Azzarone]

Public bug reported:

To reproduce on an unity8 desktop session:
1. Open a window
2. Press on the window decoration to start dragging the window

Expected behavior:
The "grabbing" mouse is shown.

Actual behavior:
The "grabbing" mouse is now shown until first mouse motion.

** Affects: unity8 (Ubuntu)
 Importance: Low
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress


** Tags: unity8-desktop

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Tags added: unity8-desktop

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

Title:
  "Grabbing" mouse cursor not shown when moving window on first press.

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  To reproduce on an unity8 desktop session:
  1. Open a window
  2. Press on the window decoration to start dragging the window

  Expected behavior:
  The "grabbing" mouse is shown.

  Actual behavior:
  The "grabbing" mouse is now shown until first mouse motion.

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

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

[Touch-packages] [Bug 1617290] Re: OS and apps can't update

[Simplehuman]

btw, I want to add. Something strange is going on with this folder.
Folder owner of many folder is root, but not for all. Some apps root
owner just can't launch?field.comment=btw, I want to add. Something
strange is going on with this folder. Folder owner of many folder is
root, but not for all. Some apps root owner just can't launch

** Attachment added: "ls.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1617290/+attachment/4730044/+files/ls.txt

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

Title:
  OS and apps can't update

Status in system-image package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  Hello, I have a problem on my M10 FHD witch is on rc-proposed channel (r173 
now). I can't receive any updates for system image or any installed app. I even 
receive a notify in message indicator, but when I open update manager it 
searches for updates and found nothing (saying that my system is up to date). 
There should be updates at least for some apps and 2 system image updates since 
then. Rebooting and shutdowning device didn't help. My Meizu MX4 is updating 
normally with
  the same network connection.

  It would be very nice to have some workaround and fix this.

  `system-image-cli -n -vv` ouput:

  phablet@ubuntu-phablet:~$ system-image-cli -n -vv
  [systemimage] Aug 25 12:31:41 2016 (5245) -> [ 1] _cleanup
  [systemimage] Aug 25 12:31:41 2016 (5245) -> [ 2] _get_blacklist_1
  [systemimage] Aug 25 12:31:41 2016 (5245) No valid image master key found, 
downloading
  [systemimage] Aug 25 12:31:41 2016 (5245) [0xf60d0850] Requesting group 
download:
  https://system-image.ubuntu.com/gpg/image-master.tar.xz -> 
/android/cache/recovery/keyring.tar.xz
  https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc -> 
/android/cache/recovery/keyring.tar.xz.asc

  [systemimage] Aug 25 12:31:41 2016 (5245) Allow GSM? No
  [systemimage] Aug 25 12:31:41 2016 (5245) 
[/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc]
 Running group download reactor
  [systemimage] Aug 25 12:31:41 2016 (5245) self: , self._iface:  :1.141 
/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc
 at 0xf60d0930> implementing 'com.canonical.applications.GroupDownload' at 
0xf60d0890>
  [systemimage] Aug 25 12:32:21 2016 (5245) 
https://system-image.ubuntu.com/gpg/image-master.tar.xz:
  [systemimage] Aug 25 12:32:21 2016 (5245) 
[/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc]
 Group download reactor done
  [systemimage] Aug 25 12:32:21 2016 (5245) Reactor error: 
https://system-image.ubuntu.com/gpg/image-master.tar.xz:
  Exception occurred during dry-run; see log file for details
  [systemimage] Aug 25 12:32:21 2016 (5245) system-image-cli exception
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/systemimage/main.py", line 365, in main
  state.run_until('download_files')
File "/usr/lib/python3/dist-packages/systemimage/state.py", line 179, in 
run_until
  step()
File "/usr/lib/python3/dist-packages/systemimage/state.py", line 210, in 
_get_blacklist_1
  'image-master', 'gpg/image-master.tar.xz', 'archive-master')
File "/usr/lib/python3/dist-packages/systemimage/keyring.py", line 107, in 
get_keyring
  (ascxz_src, ascxz_dst),
File "/usr/lib/python3/dist-packages/systemimage/download.py", line 209, in 
get_files
  self._get_files(records, pausable, signal_started)
File "/usr/lib/python3/dist-packages/systemimage/udm.py", line 175, in 
_get_files
  raise FileNotFoundError(reactor.error)
  FileNotFoundError: https://system-image.ubuntu.com/gpg/image-master.tar.xz:
  phablet@ubuntu-phablet:~$

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

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

[Touch-packages] [Bug 1602649] Re: need an option to disable launcher's autohide on desktop

[Jonas G. Drange]

Thank you for your report, I've requested a spec and visuals from
design.

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

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

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

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

Title:
  need an option to disable launcher's autohide on desktop

Status in Ubuntu UX:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  need an option to disable launcher's autohide on desktop
  you can't disable autohide now

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

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

[Touch-packages] [Bug 1603175] Re: No resolution configuration available

[Jonas G. Drange]

Thank you for your report, I've requested a spec and visuals from
design.

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

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

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

Title:
  No resolution configuration available

Status in Ubuntu UX:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In my desktop unity8 is clearly in the wrong resolution:
   - the font in the titlebar is quite pixelated
   - the cursor is huge

  It would be required to have a setting like the one in unity7 to set
  the correct resolution of the screen.

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

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

[Touch-packages] [Bug 1617290] Re: OS and apps can't update

[Simplehuman]

For some reason permissions were wrong. I can't reproduce permissions
state when the problem came up because I renamed this folder from root.
Now I changed permissions of old folder to correct ones and everything
is working.

But it is still a bug, because I didn't open Terminal, didn't connect to
device from PC or even open a File Browser for >2 weeks. Just using
phablet as a regular user. Permissions changed by something else and it
is interesting...what could cause that?

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

Title:
  OS and apps can't update

Status in system-image package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  Hello, I have a problem on my M10 FHD witch is on rc-proposed channel (r173 
now). I can't receive any updates for system image or any installed app. I even 
receive a notify in message indicator, but when I open update manager it 
searches for updates and found nothing (saying that my system is up to date). 
There should be updates at least for some apps and 2 system image updates since 
then. Rebooting and shutdowning device didn't help. My Meizu MX4 is updating 
normally with
  the same network connection.

  It would be very nice to have some workaround and fix this.

  `system-image-cli -n -vv` ouput:

  phablet@ubuntu-phablet:~$ system-image-cli -n -vv
  [systemimage] Aug 25 12:31:41 2016 (5245) -> [ 1] _cleanup
  [systemimage] Aug 25 12:31:41 2016 (5245) -> [ 2] _get_blacklist_1
  [systemimage] Aug 25 12:31:41 2016 (5245) No valid image master key found, 
downloading
  [systemimage] Aug 25 12:31:41 2016 (5245) [0xf60d0850] Requesting group 
download:
  https://system-image.ubuntu.com/gpg/image-master.tar.xz -> 
/android/cache/recovery/keyring.tar.xz
  https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc -> 
/android/cache/recovery/keyring.tar.xz.asc

  [systemimage] Aug 25 12:31:41 2016 (5245) Allow GSM? No
  [systemimage] Aug 25 12:31:41 2016 (5245) 
[/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc]
 Running group download reactor
  [systemimage] Aug 25 12:31:41 2016 (5245) self: , self._iface:  :1.141 
/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc
 at 0xf60d0930> implementing 'com.canonical.applications.GroupDownload' at 
0xf60d0890>
  [systemimage] Aug 25 12:32:21 2016 (5245) 
https://system-image.ubuntu.com/gpg/image-master.tar.xz:
  [systemimage] Aug 25 12:32:21 2016 (5245) 
[/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc]
 Group download reactor done
  [systemimage] Aug 25 12:32:21 2016 (5245) Reactor error: 
https://system-image.ubuntu.com/gpg/image-master.tar.xz:
  Exception occurred during dry-run; see log file for details
  [systemimage] Aug 25 12:32:21 2016 (5245) system-image-cli exception
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/systemimage/main.py", line 365, in main
  state.run_until('download_files')
File "/usr/lib/python3/dist-packages/systemimage/state.py", line 179, in 
run_until
  step()
File "/usr/lib/python3/dist-packages/systemimage/state.py", line 210, in 
_get_blacklist_1
  'image-master', 'gpg/image-master.tar.xz', 'archive-master')
File "/usr/lib/python3/dist-packages/systemimage/keyring.py", line 107, in 
get_keyring
  (ascxz_src, ascxz_dst),
File "/usr/lib/python3/dist-packages/systemimage/download.py", line 209, in 
get_files
  self._get_files(records, pausable, signal_started)
File "/usr/lib/python3/dist-packages/systemimage/udm.py", line 175, in 
_get_files
  raise FileNotFoundError(reactor.error)
  FileNotFoundError: https://system-image.ubuntu.com/gpg/image-master.tar.xz:
  phablet@ubuntu-phablet:~$

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

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

[Touch-packages] [Bug 1606955] Re: Renaming SIM in 'Mobile' does not change name in 'Phone'

[Jonas G. Drange]

** Also affects: dialer-app (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-system-settings (Ubuntu)

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: dialer-app (Ubuntu)

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

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

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

Title:
  Renaming SIM in 'Mobile' does not change name in 'Phone'

Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  I recently changed one of the two SIM cards in my Aquaris E5. I then
  rename this SIM in System Settings > Mobile.

  Today, after updating to OTA-12, I noticed that System Settings >
  Phone still has the old name of the new SIM. I don't know whether this
  is related to the new OTA as I didn't check before the update.

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

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

[Touch-packages] [Bug 1618031] Re: package tzdata 2016f-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package tzdata 2016f-0ubuntu0.14.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 29

Status in tzdata package in Ubuntu:
  New

Bug description:
  Software Updater reported an update to "Ubuntu Base" which I think was
  a kernel upgrade from 3.13.0-76, (I'm on 14.04.5 LTS) but the
  installation failed. This returned a different error exit status from
  the existing bug 1599555

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata 2016f-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  NonfreeKernelModules: rapidrecovery_vss
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Aug 29 08:44:13 2016
  DuplicateSignature: package:tzdata:2016f-0ubuntu0.14.04:subprocess installed 
post-installation script returned error exit status 29
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 29
  InstallationDate: Installed on 2013-05-07 (1209 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: tzdata
  Title: package tzdata 2016f-0ubuntu0.14.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 29
  UpgradeStatus: Upgraded to trusty on 2014-09-24 (705 days ago)

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

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

[Touch-packages] [Bug 1618031] [NEW] package tzdata 2016f-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29

[Brian Proffit]

Public bug reported:

Software Updater reported an update to "Ubuntu Base" which I think was a
kernel upgrade from 3.13.0-76, (I'm on 14.04.5 LTS) but the installation
failed. This returned a different error exit status from the existing
bug 1599555

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tzdata 2016f-0ubuntu0.14.04
ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
Uname: Linux 3.13.0-93-generic x86_64
NonfreeKernelModules: rapidrecovery_vss
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Mon Aug 29 08:44:13 2016
DuplicateSignature: package:tzdata:2016f-0ubuntu0.14.04:subprocess installed 
post-installation script returned error exit status 29
ErrorMessage: subprocess installed post-installation script returned error exit 
status 29
InstallationDate: Installed on 2013-05-07 (1209 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: tzdata
Title: package tzdata 2016f-0ubuntu0.14.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 29
UpgradeStatus: Upgraded to trusty on 2014-09-24 (705 days ago)

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


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

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

Title:
  package tzdata 2016f-0ubuntu0.14.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 29

Status in tzdata package in Ubuntu:
  New

Bug description:
  Software Updater reported an update to "Ubuntu Base" which I think was
  a kernel upgrade from 3.13.0-76, (I'm on 14.04.5 LTS) but the
  installation failed. This returned a different error exit status from
  the existing bug 1599555

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata 2016f-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  NonfreeKernelModules: rapidrecovery_vss
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Aug 29 08:44:13 2016
  DuplicateSignature: package:tzdata:2016f-0ubuntu0.14.04:subprocess installed 
post-installation script returned error exit status 29
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 29
  InstallationDate: Installed on 2013-05-07 (1209 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: tzdata
  Title: package tzdata 2016f-0ubuntu0.14.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 29
  UpgradeStatus: Upgraded to trusty on 2014-09-24 (705 days ago)

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

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

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

[Emily Ratliff]

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

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

Status in fontconfig package in Ubuntu:
  New

Bug description:
  This update sucks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 28 14:56:21 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-08-13 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (0 days ago)

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

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

[Touch-packages] [Bug 1589149] Re: the two Hotspots buttons seem to disagree

[Jonas G. Drange]

Bug reporter says the button in System Settings works and that the
button in the indicator does not. Either way, unless there's API
breakage, this is not something we can fix in System Settings.

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

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

Title:
  the two Hotspots buttons seem to disagree

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  When i try to activate the hotspot using the menu that you can make appear 
from above (the black-background one) it seems not to work (no hotspot and no 
hotspot symbol on the top menu appearing).
  If I open setting->hotspot, there the hotspot button is deactivated (not 
green) while the hotspot button in the black menu is green.
  It seems the button in the Settings if activated can really make the hotspot 
work (and make the hotspot button in the black menu green) but the hotspot 
button in the black menu seems to just do nothing (except cutting wifi)

  
  On the meizu 4 with ota 11. I think the problem came with ota 11.

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

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

[Touch-packages] [Bug 1583079] Re: Drop dependencies on qtdeclarative5-* transitional packages

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-ui-extras -
0.2+16.10.20160824.1-0ubuntu1

---
ubuntu-ui-extras (0.2+16.10.20160824.1-0ubuntu1) yakkety; urgency=medium

  [ Florian Boucault ]
  * Fix image orientation in photo image provider for Qt>=5.5

  [ Timo Jyrinki ]
  * Stop depending on transitional packages. (LP: #1583079) (LP:
#1583079)

 -- Kaleo   Wed, 24 Aug 2016 15:47:28 +

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

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

Title:
  Drop dependencies on qtdeclarative5-* transitional packages

Status in webapps-sprint:
  Confirmed
Status in address-book-app package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  New
Status in content-hub package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  Fix Released
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in telephony-service package in Ubuntu:
  New
Status in u1db-qt package in Ubuntu:
  New
Status in ubuntu-html5-theme package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in ubuntu-settings-components package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in ubuntu-ui-extras package in Ubuntu:
  Fix Released
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released
Status in unity-webapps-qml package in Ubuntu:
  New

Bug description:
  ** Please include offered MPs in your next landings of the projects **

  With Ubuntu 16.04 LTS as the recommended deadline many packages
  managed to transition to qml-module-xyz package naming from the
  qtdeclarative5-xyz-plugin package naming (bug #1342031). The next step
  is to update all packages that depend on transitioned qtdeclarative5
  -xyz-plugin to depend on the proper qml-module-xyz packages instead.

  The goal is to then drop the transitional packages now that 14.04 LTS
  -> 16.04 LTS upgrades are secured for all the packages that made the
  transition before 16.04 LTS release.

  You can run the following (not 100% complete) to automate this:

  sed -i 's/qtdeclarative5-accounts-plugin/qml-module-ubuntu-onlineaccounts/' 
debian/control
  sed -i 's/qtdeclarative5-qtcontacts-plugin/qml-module-qtcontacts/' 
debian/control
  sed -i 
's/qtdeclarative5-ubuntu-ui-toolkit-plugin/qml-module-ubuntu-components/' 
debian/control
  sed -i 
's/qtdeclarative5-ubuntu-thumbnailer0.1/qml-module-ubuntu-thumbnailer0.1/' 
debian/control
  sed -i 's/qtdeclarative5-qtquick2-plugin/qml-module-qtquick2/' debian/control
  sed -i 
's/qtdeclarative5-online-accounts-client0.1/qml-module-ubuntu-onlineaccounts-client/'
 debian/control
  sed -i 's/qtdeclarative5-window-plugin/qml-module-qtquick-window2/' 
debian/control
  sed -i 
's/qtdeclarative5-xmllistmodel-plugin/qml-module-qtquick-xmllistmodel/' 
debian/control
  sed -i 
's/qtdeclarative5-folderlistmodel-plugin/qml-module-qt-labs-folderlistmodel/' 
debian/control
  sed -i 
's/qtdeclarative5-localstorage-plugin/qml-module-qtquick-localstorage/' 
debian/control
  sed -i 's/qtdeclarative5-test-plugin/qml-module-qttest/' debian/control
  sed -i 's/qtdeclarative5-ubuntu-web-plugin/qml-module-ubuntu-web/' 
debian/control
  sed -i 's/qtdeclarative5-quicklayouts-plugin/qml-module-qtquick-layouts/' 
debian/control

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1583079/+subscriptions

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

[Touch-packages] [Bug 1613613] Re: sometimes header of the dialler is clipped on incoming calls

[Jean-Baptiste Lallement]

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

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

Title:
  sometimes header of the dialler is clipped on incoming calls

Status in Canonical System Image:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  current build number: 402
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Sometimes when receiving a call the dialler is not fully visible and
  the header is clipped, like the entire page is slightly scrolled (cf
  screenshot)

  Test Case:
  1. On the DUT, close the dialler app and lock the phone
  2. Call the DUT from another phone
  3. Take the call and wait until the dialler UI is fully rendered.

  Expected result
  The whole UI is visible

  Actual result
  The header is clipped.

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

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

[Touch-packages] [Bug 1595082] Re: Cannot preview in 16.04 desktop

[Launchpad Bug Tracker]

This bug was fixed in the package camera-app -
3.0.0+16.10.20160824-0ubuntu1

---
camera-app (3.0.0+16.10.20160824-0ubuntu1) yakkety; urgency=medium

  [ Florian Boucault ]
  * New release: (LP: #1563858, #1572576, #1584524, #1585942, #1595082,
#1615657)

 -- Kaleo   Wed, 24 Aug 2016 14:03:57 +

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Cannot preview in 16.04 desktop

Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 16.04, camera-app (version 3.0.0+16.04.20160323.3-0ubuntu1)
  cannot preview webcam or capture anything, the camera-app window is
  all black.

  From shell output:

  user@desktop:~$ camera-app 
  Import path added "/usr/lib/x86_64-linux-gnu/camera-app"
  Camera app directory "/usr/share/camera-app/"
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  Focus mode selection is not supported
  APP_ID isn't set, the handler can not be registered
  file:///usr/share/camera-app/ViewFinderOverlay.qml:23:1: module "QtSensors" 
is not installed
  APP_ID isn't set, the handler ignored
  QFileSystemWatcher::removePaths: list is empty

  ** (camera-app:3003): WARNING **: Unable to register app: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID
  file:///usr/share/camera-app/ViewFinderExportConfirmation.qml:75:17: QML 
Item: Binding loop detected for property "height"
  file:///usr/share/camera-app/ViewFinderExportConfirmation.qml:75:17: QML 
Item: Binding loop detected for property "height"
  file:///usr/share/camera-app/ViewFinderExportConfirmation.qml:75:17: QML 
Item: Binding loop detected for property "height"
  file:///usr/share/camera-app/SlideshowView.qml:43: TypeError: Cannot read 
property 'isSelected' of null
  file:///usr/share/camera-app/SlideshowView.qml:375: TypeError: Cannot read 
property 'actions' of null
  file:///usr/share/camera-app/ViewFinderOverlayLoader.qml:26: TypeError: 
Cannot read property 'settings' of null
  file:///usr/share/camera-app/ViewFinderView.qml:458: TypeError: Cannot read 
property 'contentType' of null
  user@desktop:~$

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

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

[Touch-packages] [Bug 1615657] Re: Reverse portrait orientation broken on BQ M10

[Launchpad Bug Tracker]

This bug was fixed in the package camera-app -
3.0.0+16.10.20160824-0ubuntu1

---
camera-app (3.0.0+16.10.20160824-0ubuntu1) yakkety; urgency=medium

  [ Florian Boucault ]
  * New release: (LP: #1563858, #1572576, #1584524, #1585942, #1595082,
#1615657)

 -- Kaleo   Wed, 24 Aug 2016 14:03:57 +

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Reverse portrait orientation broken on BQ M10

Status in Canonical System Image:
  Fix Committed
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Launch the camera in landscape with the camera on top
  2. Turn the tablet in portrait 90degrees to the left, the camera should now 
be on the left

  Expected result:
  Photo roll should be accessible to the right.
  Bottom edge should be accessible.

  Current result:
  Photo roll is accessible from the top.
  Bottom edge is not accessible.

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

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

[Touch-packages] [Bug 1597366] Re: testShell too slow

[Albert Astals Cid]

** Branch linked: lp:~aacid/unity8/makeTestShellFaster

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

Title:
  testShell too slow

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Our CI turnaround has gotten worse - to over two hours for a single
  MP.

  Part of this is testShell, which takes 25mins *after* all other tests
  finished already. That suite alone takes 50mins [1]:

  00:22:21.633 PASS   : qmltestrunner::Shell::initTestCase()
  [...]
  00:48:33.484 * Finished testing of ListViewWithPageHeaderTest 
*
  [...]
  01:12:00.463 PASS   : qmltestrunner::Shell::cleanupTestCase()

  We need to split this suite up at least, apart from speeding it up.

  [1]
  
https://unity8-jenkins.ubuntu.com/job/test-0-autopkgtest/1151/label=amd64,release=vivid+overlay,testname=qmluitests.sh/consoleFull

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160627.5-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 29 16:22:02 2016
  InstallationDate: Installed on 2016-05-06 (53 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1615657] Re: Reverse portrait orientation broken on BQ M10

[Jean-Baptiste Lallement]

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

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

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

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

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

Title:
  Reverse portrait orientation broken on BQ M10

Status in Canonical System Image:
  Fix Committed
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  1. Launch the camera in landscape with the camera on top
  2. Turn the tablet in portrait 90degrees to the left, the camera should now 
be on the left

  Expected result:
  Photo roll should be accessible to the right.
  Bottom edge should be accessible.

  Current result:
  Photo roll is accessible from the top.
  Bottom edge is not accessible.

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

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

[Touch-packages] [Bug 1599146] Re: captcha's don't work on Ubuntu browser

[Jean-Baptiste Lallement]

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

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

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

Title:
  captcha's don't work on Ubuntu browser

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

Bug description:
  captcha's don't work on Ubuntu browser

  Captcha's moan about Ubuntu browser not being compatible.  (good bug?)

  Google is unable to fully invade your privacy  Please keep this
  bug alive!

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

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

[Touch-packages] [Bug 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml

[Tim Peeters]

** Branch linked: lp:~fboucault/ubuntu-ui-toolkit/fix_async_width_height

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

Title:
  Invalid property assignment in ActivityIndicatorStyle.qml

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

Bug description:
  I get

  file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

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

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

[Touch-packages] [Bug 1440716] Re: software-properties-gtk crashed with aptdaemon.errors.AptDaemonError in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  software-properties-gtk crashed with aptdaemon.errors.AptDaemonError
  in _convert_dbus_exception(): org.debian.apt: Could not cancel
  transaction

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Crash during updating cache after changes in sources.list

  Lubuntu 15.04

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: software-properties-gtk 0.96.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Mon Apr  6 14:07:57 2015
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2015-01-09 (87 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with aptdaemon.errors.AptDaemonError 
in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction
  UpgradeStatus: Upgraded to vivid on 2015-02-23 (41 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

[Jean-Baptiste Lallement]

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

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

Title:
  oxide should use an app-specific path for shared memory files

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  Fix Released
Status in Oxide 1.17 series:
  Fix Committed
Status in webapps-sprint:
  Fix Committed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

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

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

[Jean-Baptiste Lallement]

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

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  Fix Committed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in usensord package in Ubuntu:
  Fix Committed

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  http://paste.ubuntu.com/10620834/

To 

[Touch-packages] [Bug 1440716] Re: software-properties-gtk crashed with aptdaemon.errors.AptDaemonError in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction

[Apport retracing service]

** Tags added: yakkety

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

Title:
  software-properties-gtk crashed with aptdaemon.errors.AptDaemonError
  in _convert_dbus_exception(): org.debian.apt: Could not cancel
  transaction

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Crash during updating cache after changes in sources.list

  Lubuntu 15.04

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: software-properties-gtk 0.96.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Mon Apr  6 14:07:57 2015
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2015-01-09 (87 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with aptdaemon.errors.AptDaemonError 
in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction
  UpgradeStatus: Upgraded to vivid on 2015-02-23 (41 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1617371] Re: Top bar is transparent in yakkety

[Launchpad Bug Tracker]

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

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

  [ Iain Lane ]
  * gedit: Don't set a border on the 'x of y' thing in the search
results
  * Set a proper minimum width on levelbar troughs

  [ Marco Trevisan (Treviño) ]
  * gnome-panel: don't apply the gnome-menubar rules to unity
decorations and panel too (LP: #1617371)

 -- Marco Trevisan (Treviño)   Mon, 29 Aug 2016 10:10:10
+

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

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

Title:
  Top bar is transparent in yakkety

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  In one of my two laptops, the top bar is transparent see
  http://i.imgur.com/6N52nhb.png

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

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

[Touch-packages] [Bug 1615751] Re: ROOTDELAY= causes unnecessary delay in boot

[Scott Moser]

Verified this is fixed.  Thank you!


** Changed in: cloud-images
   Status: Fix Committed => Fix Released

** Changed in: cloud-images
   Importance: Undecided => High

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

Title:
  ROOTDELAY= causes unnecessary delay in boot

Status in cloud-images:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  I launched 2 different yakkety systems on azure instance types:
    Basic_A0
    Standard_D1_v2
  More information what those things are at :
    https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/

  systemd-analize says:

  ## Basic A0
  smoser@sm-y-d1v2-1:~$ systemd-analyze
  Startup finished in 5min 8.172s (kernel) + 42.670s (userspace) = 5min 50.842s

  ## Standard D1 v2
  $ systemd-analyze
  Startup finished in 5min 13.347s (kernel) + 1min 31.532s (userspace) = 6min 
44.879s

  Systemd thinks that more than 5 minutes passed between the kernel
  being loaded and /sbin/init being run.  I'm pretty sure this isn't
  just a bad clock, as the system actually is not reachable for
  something like 6 minutes after boot, so it seems sane.  Additionally,
  I have some scripts that compare launch time and code ran inside the
  vm via cloud-init and they agree.

  For example:
    starting at Mon, 22 Aug 2016 15:37:43 +
    uptime: 349.77 seconds
    you launched me at: Mon, 22 Aug 2016 15:30:11 +
    it is now : Mon, 22 Aug 2016 15:37:43 +
    kernel booted : Mon, 22 Aug 2016 15:31:54 +
    launch to kernel boot: 103 seconds
    launch to user-data  : 452   seconds

  The full dmesg is attached, but interesting bits are
  [0.815692] Trying to unpack rootfs image as initramfs...
  [1.289093] Freeing initrd memory: 35660K (88001d47d000 - 
88001f75)
  ...
  [7.820798] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/input/input3
  [7.834419] input: AT Translated Set 2 keyboard as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_5/serio2/input/input5
  [   72.464227] random: nonblocking pool is initialized
  [  305.527657] Btrfs loaded
  [  305.628091] blk_update_request: I/O error, dev fd0, sector 0
  [  305.632007] floppy: error -5 while reading block 0
  [  306.027898] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  308.901437] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
  [  308.925746] systemd[1]: Detected virtualization microsoft.
  [  308.933658] systemd[1]: Detected architecture x86-64.
  [  308.999041] systemd[1]: Set hostname to .
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 22 15:37 seq
   crw-rw 1 root audio 116, 33 Aug 22 15:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Aug 22 17:31:18 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.160
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 

[Touch-packages] [Bug 1618008] Re: software-properties-gtk crashed with aptdaemon.errors.AptDaemonError in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

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

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

** This bug has been marked a duplicate of bug 1440716
   software-properties-gtk crashed with aptdaemon.errors.AptDaemonError in 
_convert_dbus_exception(): org.debian.apt: Could not cancel transaction

** Information type changed from Private to Public

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

Title:
  software-properties-gtk crashed with aptdaemon.errors.AptDaemonError
  in _convert_dbus_exception(): org.debian.apt: Could not cancel
  transaction

Status in software-properties package in Ubuntu:
  New

Bug description:
  bug lubuntu 16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.3
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Aug 29 08:30:55 2016
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2016-08-29 (0 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with aptdaemon.errors.AptDaemonError 
in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1618009] [NEW] using loadavg function in sysinfo.c errors out sometimes

[Lily Rivers]

Public bug reported:

Lines 379 - 383 in sysinfo.c have the following code:

if (sscanf(buf, "%lf %lf %lf", _1, _5, _15) < 3) {
fputs("bad data in " LOADAVG_FILE "\n", stderr);
free(savelocale);
exit(1);
}

At random, a program will exit when calling this function. If the
function succeeds the first time, it will succeed in all other attempts
to read /proc/loadavg. The file /proc/loadavg contains 5 numbers so
maybe only the first 3 should be read and the rest should just be
discarded.

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

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

Title:
  using loadavg function in sysinfo.c errors out sometimes

Status in procps package in Ubuntu:
  New

Bug description:
  Lines 379 - 383 in sysinfo.c have the following code:

  if (sscanf(buf, "%lf %lf %lf", _1, _5, _15) < 3) {
fputs("bad data in " LOADAVG_FILE "\n", stderr);
free(savelocale);
exit(1);
  }

  At random, a program will exit when calling this function. If the
  function succeeds the first time, it will succeed in all other
  attempts to read /proc/loadavg. The file /proc/loadavg contains 5
  numbers so maybe only the first 3 should be read and the rest should
  just be discarded.

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

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

[Touch-packages] [Bug 1614070] Re: Unity8 doesn't rotate on new images whether via flash or ota

[Jean-Baptiste Lallement]

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

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

Title:
  Unity8 doesn't rotate on new images whether via flash or ota

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Have a SIM-locked device
  2. Install the latest rc-proposed image (403 on arale)
  3. Once in the system rotate the device

  EXPECTED:
  Shell rotates and refreshes

  ACTUAL:
  Nothing happens

  http://paste.ubuntu.com/23064285/

  Above is the paste from 401 the image before the latest untiy8 landed
  you will note that the shell activates a rotate and the resolution
  changes, below it is the resolute of OTAing to 403 you'll note the
  sensor is still triggered but the shell no longer rotates.

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

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