[Touch-packages] [Bug 1148116] Re: not all packages from PPAs have '[origin: ' in Package section

[Brian Murray]

** Description changed:

  Test Case
  -
  1) Install galicaster package from wiki.teltek.es (or any other random deb 
file will do)
  2) Run the executable
  3) Find the pid of the program and kill it with signal 11
  4) Inspect the .crash file (after it is finished being written) and observe 
the "Package: " key doesn't not contain "[origin: unknown]"
  
  With the version of apport from -proposed it will contain information
  about it being from an unknown origin.
  
- 
+ Original Description
+ 
  I was querying for columns in the counters column family starting with 
'Ubuntu ' as I was looking for the counts of bugs reported about packages.  In 
the column family I discovered 'Ubuntu 12.10:indicator-stickynotes' and was 
having trouble finding errors for that package because it is from a PPA.  Given 
that the package is from a PPA it shouldn't be appearing in the counters column 
family at all though.
  
  From daisy/submit.py:
  
  package = data.get('Package', '')
  src_package = data.get('SourcePackage', '')
  problem_type = data.get('ProblemType', '')
  third_party = False
  if '[origin:' in package:
  third_party = True
  
  Then before running update_release_pkg_counter we check for 'if not
  third_party'.  Looking at least some of the oops for indicator-
  stickynotes all of them had '[origin:' in the Package key.

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

Title:
  not all packages from PPAs have '[origin: ' in Package section

Status in Daisy:
  Invalid
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Triaged

Bug description:
  Test Case
  -
  1) Install galicaster package from wiki.teltek.es (or any other random deb 
file will do)
  2) Run the executable
  3) Find the pid of the program and kill it with signal 11
  4) Inspect the .crash file (after it is finished being written) and observe 
the "Package: " key doesn't not contain "[origin: unknown]"

  With the version of apport from -proposed it will contain information
  about it being from an unknown origin.

  Original Description
  
  I was querying for columns in the counters column family starting with 
'Ubuntu ' as I was looking for the counts of bugs reported about packages.  In 
the column family I discovered 'Ubuntu 12.10:indicator-stickynotes' and was 
having trouble finding errors for that package because it is from a PPA.  Given 
that the package is from a PPA it shouldn't be appearing in the counters column 
family at all though.

  From daisy/submit.py:

  package = data.get('Package', '')
  src_package = data.get('SourcePackage', '')
  problem_type = data.get('ProblemType', '')
  third_party = False
  if '[origin:' in package:
  third_party = True

  Then before running update_release_pkg_counter we check for 'if not
  third_party'.  Looking at least some of the oops for indicator-
  stickynotes all of them had '[origin:' in the Package key.

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

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

[Touch-packages] [Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops

[Scott Sweeny]

** Changed in: location-service (Ubuntu)
 Assignee: Manuel de la Peña (mandel) => Scott Sweeny (ssweeny)

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

Title:
  [Ubuntu Phone] With WIFI = ON the GPS stops

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  New
Status in ubuntu-system-settings:
  New
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  Steps: 
  1. Enable WIFI = ON on phone.
  2. Run one of these apps: GPS Navigation, HERE maps, Sensor Status.
  3. Drive.
  4. When you'll be into a WIFI area as a town or city, I'm thinking the WIFI 
will try to search WIFIs and then the GPS will stop, the GPS apps will not 
receive more new positions from the GPS.

  Extra info1: If you had GPS Navigation & Sensor running, both of them
  will not receive new GPS positions from the device. If you restart for
  example GPS Navigation, GPS Navigation will receive new positions, but
  Sensor Status not, until you restart it too.

  Extra info2: When the GPS stops the icon in the status disappears, but
  it you kill and relaunch the app, the icon will appear again.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1497996] Re: When a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second run of heath-check

[Parameswaran Sivatharman]

This is occurring on both i386 and amd64 VM's. The description has been
updated to this effect.

** Description changed:

- This is noticed during health-check's tests on trusty (mostly i386)
- ISO's.
+ This is noticed during health-check's tests on trusty (mostly i386 but
+ also on amd64) ISO's.
  
  The failed builds in
  https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job
  /trusty-desktop-i386-smoke-health-check/ are all due to this issue.
- 
  
  The following is excerpts from cking's debugging of the failure:
  
  "NetworkManager does not show this issue when no connections are made old
  connections are re-established. Only new connections since reboot seem
  to trigger this.
  
  The large mmap is a bit ridiculous, it's either the heap (via
  malloc/free) or glib memory allocator being a bit generous in the way it
  requests more memory for the heap or network manager itself doing a
  large mmap request (which I think is very unlikely).
  
  The good news is that the memory is mapped but not all used, so there is
  little actual physical demand for these mapped in pages.  Even so, I
  think it may be worth somebody with NetworkManager experience to dig in
  deeper to see why and where this allocation is occurring as a medium/low
  bug.
  
  To reproduce this issue:
  
  1. Clean boot
  2. Wait until existing network connections are established (e.g. wifi)
  3. Run health-check on Network Manager
  4. Make a new connection, e.g. plug in ethernet connection for an
  auto-ethernet connection to be established.
  5. Stop health-check, observe that a huge allocation has occurred."
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  Date: Mon Sep 21 13:24:45 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-08 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150908)
  IpRoute:
   default via 192.168.122.1 dev eth0  proto static
   192.168.122.0/24 dev eth0  proto kernel  scope link  src 192.168.122.148  
metric 1
  IwConfig:
   lono wireless extensions.
  
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
  
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
   Wired connection 185b3134d-a657-40be-8229-248bcd0ce79c   
802-3-ethernet1442841756   Mon 21 Sep 2015 01:22:36 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

Title:
  When a new connection occurs, NetworkManager mmaps 64Mb hunk which is
  equivalent to the 32.28Kb per second rate over a 1800 second run of
  heath-check

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is noticed during health-check's tests on trusty (mostly i386 but
  also on amd64) ISO's.

  The failed builds in
  https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job
  /trusty-desktop-i386-smoke-health-check/ are all due to this issue.

  The following is excerpts from cking's debugging of the failure:

  "NetworkManager does not show this issue when no connections are made old
  connections are re-established. Only new connections since reboot seem
  to trigger this.

  The large mmap is a bit ridiculous, it's either the heap (via
  malloc/free) or glib memory allocator being a bit generous in the way it
  requests more memory for the heap or network manager itself doing a
  large mmap request (which I think is very unlikely).

  The good news is that the memory is mapped but not all used, so there is
  little actual physical demand for these mapped in pages.  Even so, I
  think it may be worth somebody with NetworkManager experience to dig in
  deeper to see why and where this allocation is 

Re: [Touch-packages] [Bug 1495103] Re: no idee

[bouman4]

i have no idee waht is the problem my pc wil not start good 
only in the tty1 mode i try set back to gui at start not work 
now my pc only start  recovery mode
root  option mount -o remount,rw /network option  to start network gifs  error 
but network works then start option 1 normal mode 
problems come whit a reset 
sorry for my bad english im from duth
my system ubuntu studio hp compaq dx 2420 emu sound card 
xorg rest have not worked to fix my problems
bugs and problems not bad problems always good to fix them and making a beter 
system


dj-d (aalburg)

> Date: Sun, 20 Sep 2015 00:31:34 +
> From: christopher.m.penal...@gmail.com
> To: dj_d...@hotmail.com
> Subject: [Bug 1495103] Re: no idee
> 
> bouman4, thank you for taking the time to report this and helping to
> make Ubuntu better. Unfortunately, this report didn't include enough
> information. You may find it helpful to read "How to report bugs
> effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and
> https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would
> then provide a more complete description of the problem.
> 
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures
> 
> At a minimum, we need:
> 1. The specific steps or actions you took that caused you to encounter the 
> problem,
> 2. The behavior you expected, and
> 3. The behavior you actually encountered (in as much detail as possible).
> 
> Thank you for your understanding.
> 
> ** Tags added: bios-outdated-5.31
> 
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
> 
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1495103
> 
> Title:
>   no idee
> 
> Status in xorg package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   no idee
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: xorg 1:7.7+7ubuntu4
>   ProcVersionSignature: Ubuntu 3.16.0-33.44-lowlatency 3.16.7-ckt7
>   Uname: Linux 3.16.0-33-lowlatency x86_64
>   .tmp.unity.support.test.1:
>
>   ApportVersion: 2.17.2-0ubuntu1.4
>   Architecture: amd64
>   BootLog: Scanning for Btrfs filesystems
>   CompizPlugins: No value set for 
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Sat Sep 12 17:14:28 2015
>   DistUpgraded: Fresh install
>   DistroCodename: vivid
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] RV635 [Radeon HD 
> 3650/3750/4570/4580] [1002:9598] (prog-if 00 [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. Device [1043:01e4]
>   InstallationDate: Installed on 2015-01-13 (241 days ago)
>   InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Release amd64 
> (20141022.2)
>   MachineType: Hewlett-Packard HP Compaq dx2420 Microtower
>   ProcEnviron:
>PATH=(custom, no user)
>LANG=nl_NL.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-lowlatency 
> root=/dev/mapper/ubuntu--studio--vg-root ro recovery nomodeset
>   Renderer: Software
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/20/2009
>   dmi.bios.vendor: Phoenix Technologies, LTD
>   dmi.bios.version: 5.18
>   dmi.board.name: 2A78h
>   dmi.board.vendor: MSI
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: CZC9320FDL
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias: 
> dmi:bvnPhoenixTechnologies,LTD:bvr5.18:bd02/20/2009:svnHewlett-Packard:pnHPCompaqdx2420Microtower:pvr:rvnMSI:rn2A78h:rvr1.0:cvnHewlett-Packard:ct3:cvr:
>   dmi.product.name: HP Compaq dx2420 Microtower
>   dmi.sys.vendor: Hewlett-Packard
>   version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.60-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917-1~exp1ubuntu2.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
> 1:1.0.11-1ubuntu2build1
>   xserver.bootTime: Sat Sep 12 16:57:12 2015
>   xserver.configfile: default
>   xserver.devices:
>inputPower Button KEYBOARD, id 6
>inputPower Button KEYBOARD, id 7
>inputAT Translated Set 2 keyboard KEYBOARD, id 8
>inputImPS/2 Generic Wheel Mouse MOUSE, id 9
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.17.1-0ubuntu3
> 
> To manage 

[Touch-packages] [Bug 1457518] Re: Knime freezes after viewing a plot (since upgrade to 15.04)

[Andrea Azzarone]

Closing the bug. Unlikely unity is the cause for your problem.

** Changed in: unity
   Status: Incomplete => Invalid

** Changed in: unity (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: unity (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  Knime freezes after viewing a plot (since upgrade to 15.04)

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Knime (an eclipse based program) https://www.knime.org/ was working
  perfectly in 14.04. Since my upgrade to 15.05 each time a try to
  visualize any kind of plot or table (that means a new window), the new
  window is created and the plot appears. But, from that point on, Knime
  entirely freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu May 21 16:40:55 2015
  DistUpgraded: 2015-04-28 15:12:19,082 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1522]
  InstallationDate: Installed on 2014-06-20 (335 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK Computer Inc. N53Jq
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=b4957094-21ba-430f-b351-d88669003f19 ro quiet splash
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago)
  dmi.bios.date: 09/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N53Jq.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N53Jq
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN53Jq.207:bd09/30/2010:svnASUSTeKComputerInc.:pnN53Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN53Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N53Jq
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu May 21 11:27:54 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1320981] Re: unity fails to load after login - screen garbled; desktop unusable

[Andrea Azzarone]

Yeah, but let's close the bug. Open a new bug if you'll reproduce it in
the future.

** Changed in: unity
   Status: Incomplete => Invalid

** Changed in: unity (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  unity fails to load after login - screen garbled; desktop unusable

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  everything was working fine until the recent kernel update.

  switching to tty1 and running unity --replace restores some (but not all) 
desktop functionality:
  - desktop loads (no longer garbled)
  - unity sidebar now loads
  - top menu bar doesn't load
  - many window decorations, font etc. not working so windows look awful
  - shortcut keys do not work
  - start up programs don't load

  some of the output from unity --replace is similar to this bug:
  https://bugs.launchpad.net/unity/+bug/1282507 suggesting a problem
  connecting to dbus (see attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.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: Mon May 19 11:37:35 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] 
[1002:68d8] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2294]
  InstallationDate: Installed on 2014-04-04 (45 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=35f2a23b-ea35-4160-a1c7-2d945a4bede8 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  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.:bvr1701:bd09/27/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon May 19 11:34:27 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: fglrx

To manage notifications 

Re: [Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[vedavata]

22/09/2015 17:21 "madbiologist" <160...@bugs.launchpad.net> :
>
> JohnWashington - This bug is about the default resize grab handle at
> window borders being too small (1 pixel, or 4 pixels by some accounts)
> to be easily usable.  This has been fixed with the implementation of a
> larger default resize grab handle (10 pixels I think).

Why I cannot note this?
It seems to me, that it's still needed to try to catch 4 pixels, not 10 or
wider?..

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 1496743] Re: /usr/bin/ld.gold: --push-state: unknown option

[Matthias Klose]

I'm working on it

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

Title:
  /usr/bin/ld.gold: --push-state: unknown option

Status in gcc-5 package in Ubuntu:
  Triaged
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  With gcc 5.2.1-17ubuntu4, we're seeing
  https://launchpadlibrarian.net/218108553/buildlog_ubuntu-wily-amd64
  .ubuntu-ui-
  toolkit_1.3.1639%2B15.10.20150916.2-0ubuntu1_BUILDING.txt.gz

  TJ- on #ubuntu-devel suggested:
  < TJ-> Mirv: bzoltan: the issue could be in qtbase-opensource-src-5.4.2+dfsg 
(qmake) which does "mkspecs/common/gcc-base-unix.conf:19:QMAKE_LFLAGS_USE_GOLD  
 = -fuse-ld=gold" irrespective of libraries being linked.

  Ideas for a proper fix welcome.

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

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

[Touch-packages] [Bug 1495688] Re: system-image-cli tool fails on dangling symlink

[Barry Warsaw]

** Changed in: ubuntu-system-image
   Status: In Progress => Fix Committed

** Changed in: system-image (Ubuntu)
   Status: New => Triaged

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

Title:
  system-image-cli tool fails on dangling symlink

Status in Snappy:
  Fix Released
Status in Ubuntu system image:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in system-image package in Ubuntu:
  Triaged

Bug description:
  
  (amd64)ubuntu@localhost:~$ system-image-cli -i
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 253, in 
last_update_date
  timestamp = datetime.fromtimestamp(os.stat(LAST_UPDATE_FILE).st_mtime)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/userdata/.last_update'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/system-image-cli", line 9, in 
  load_entry_point('system-image==3.0.1', 'console_scripts', 
'system-image-cli')()
File "/usr/lib/python3/dist-packages/systemimage/main.py", line 289, in main
  last_update=last_update_date(),
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in 
last_update_date
  for path in config.ini_files)
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in 

  for path in config.ini_files)
File "/usr/lib/python3.4/pathlib.py", line 1048, in stat
  return self._accessor.stat(self)
File "/usr/lib/python3.4/pathlib.py", line 326, in wrapped
  return strfunc(str(pathobj), *args)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/system-image/config.d/00_default.ini'

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

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

[Touch-packages] [Bug 1320981] Re: unity fails to load after login - screen garbled; desktop unusable

[Alex Chubaty]

yes, feel free to close. it's good to know people are looking at the
launchpad bugs, so thank you. unfortunately, for this one I've had to
move on in order to stay productive.

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

Title:
  unity fails to load after login - screen garbled; desktop unusable

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  everything was working fine until the recent kernel update.

  switching to tty1 and running unity --replace restores some (but not all) 
desktop functionality:
  - desktop loads (no longer garbled)
  - unity sidebar now loads
  - top menu bar doesn't load
  - many window decorations, font etc. not working so windows look awful
  - shortcut keys do not work
  - start up programs don't load

  some of the output from unity --replace is similar to this bug:
  https://bugs.launchpad.net/unity/+bug/1282507 suggesting a problem
  connecting to dbus (see attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.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: Mon May 19 11:37:35 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] 
[1002:68d8] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2294]
  InstallationDate: Installed on 2014-04-04 (45 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=35f2a23b-ea35-4160-a1c7-2d945a4bede8 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  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.:bvr1701:bd09/27/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon May 19 11:34:27 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: fglrx

To manage notifications about this bug go to:

[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@vedavata I imagine that it is because (according to comment #397 you
are using Xubuntu.  This bug is about Unity, where it has been fixed.
If you have a problem on Xubuntu you should file a bug for that or
extend this bug to Xubuntu.  I don't know what the appropriate package
on Xubuntu would be.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 1292396] Re: After upgrade Unity session is broken

[NickTh]

Thank you for taking the time to report this bug.  We have tried to
recreate this on the latest release of Ubuntu and cannot reproduce it.
This bug is being marked as Invalid.  If you believe the problem to
still exist in the latest version of Ubuntu please comment on why that
is the case and change the bug status to NEW.

Maybe a bad configuration ?

Try to restore original settings.

$ gconftool --shutdown
$ sudo killall -r -I gconf
$ sudo killall -r -I dconf
$ tar czf confbackup.tar.gz .compiz* .gconf* .config/dconf/ .config/compiz*

then

$ rm -rf .compiz* .gconf* .config/dconf/ .config/compiz*

and reboot.

** Changed in: unity (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  After upgrade Unity session is broken

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After yesterdays upgrade, when I log in into default session (Unity),
  there was no Panel, no Launcher, no windows decorations. there was
  Yesterday's upgrade was related to Unity packadges, so after reboot I
  logged into Gnome Flashback session - works as expected. Reboot - and
  there is no Unity session in Unity Greeter. I logged again into
  Flashback and launch Synaptic. I saw, that Unity package wasn't even
  installed, so I installed it - Unity session shows up in Greeter, but
  thaths all, still no Panel, no Launcher, etc. In CCSM Unity plugin was
  uncheck. I was able to launch window decorations, but launching Unity
  plugin caused CCSC crash. In another try there was info, that launch
  of Unity plugin is in conflict with Window Decorations plugin, but
  somehow launching Unity plugin does nothing, but Compiz crash
  (https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1292393).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140313-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,resize,gnomecompat,regex,imgpng,move,commands,mousepoll,vpswitch,animation,place,wall,unitymtgrabhandles,grid,wobbly,fade,expo,workarounds,session,scale,ezoom]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar 14 08:26:59 2014
  DistUpgraded: 2013-11-26 21:17:59,613 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7576]
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=23985ff5-112f-4dab-9da1-5c21397013fe ro splash quiet vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-26 (107 days ago)
  dmi.bios.date: 11/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785G-E53 (MS-7576)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd11/27/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785G-E53(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7576
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar 14 08:13:38 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 8
   inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 9
   inputMicrosoft Microsoft® 2.4GHz 

[Touch-packages] [Bug 1292396] Re: After upgrade Unity session is broken

[NickTh]

Thank you for taking the time to report this bug.  We have tried to
recreate this on the latest release of Ubuntu and cannot reproduce it.
This bug is being marked as Invalid.  If you believe the problem to
still exist in the latest version of Ubuntu please comment on why that
is the case and change the bug status to NEW.

Maybe a bad configuration ?

Try to restore original settings.

$ gconftool --shutdown
$ sudo killall -r -I gconf
$ sudo killall -r -I dconf
$ tar czf confbackup.tar.gz .compiz* .gconf* .config/dconf/ .config/compiz*

then

$ rm -rf .compiz* .gconf* .config/dconf/ .config/compiz*

and reboot.

** Changed in: unity
   Status: Confirmed => Invalid

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

Title:
  After upgrade Unity session is broken

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After yesterdays upgrade, when I log in into default session (Unity),
  there was no Panel, no Launcher, no windows decorations. there was
  Yesterday's upgrade was related to Unity packadges, so after reboot I
  logged into Gnome Flashback session - works as expected. Reboot - and
  there is no Unity session in Unity Greeter. I logged again into
  Flashback and launch Synaptic. I saw, that Unity package wasn't even
  installed, so I installed it - Unity session shows up in Greeter, but
  thaths all, still no Panel, no Launcher, etc. In CCSM Unity plugin was
  uncheck. I was able to launch window decorations, but launching Unity
  plugin caused CCSC crash. In another try there was info, that launch
  of Unity plugin is in conflict with Window Decorations plugin, but
  somehow launching Unity plugin does nothing, but Compiz crash
  (https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1292393).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140313-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,resize,gnomecompat,regex,imgpng,move,commands,mousepoll,vpswitch,animation,place,wall,unitymtgrabhandles,grid,wobbly,fade,expo,workarounds,session,scale,ezoom]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar 14 08:26:59 2014
  DistUpgraded: 2013-11-26 21:17:59,613 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7576]
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=23985ff5-112f-4dab-9da1-5c21397013fe ro splash quiet vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-26 (107 days ago)
  dmi.bios.date: 11/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785G-E53 (MS-7576)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd11/27/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785G-E53(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7576
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar 14 08:13:38 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 8
   inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 9
   inputMicrosoft Microsoft® 2.4GHz 

[Touch-packages] [Bug 1498310] [NEW] udev is missing /lib/udev/udev-finish in wily

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

$ lsb_release -rd
Description:Ubuntu Wily Werewolf (development branch)
Release:15.10

$ apt-cache policy udev
udev:
  Installed: 225-1ubuntu4
  Candidate: 225-1ubuntu4
  Version table:
 *** 225-1ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status

The udev package in wily is missing /lib/udev/udev-finish, hence systemd 
reports the udev-finish.service as failed.
Placing this script , which is in udev package 219-7ubuntu6 (vivid-updates), 
into the correct location rectifies this.

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

-- 
udev is missing /lib/udev/udev-finish in wily
https://bugs.launchpad.net/bugs/1498310
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

[Martin Pitt]

** Changed in: apport (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1
  min watchdog timeout on longer kernel lockups

Status in apport package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain

  
  Sometimes userspace get locked up hard: A QEMU instance sees long hangs while 
the host gets suspended, USB devices/drivers lock up for some time (like in 
this bug's dmesg), or Google hangouts in bug 1495585.
  The kernel detects that some process(es) get hard-locked up, the hardware 
watchdog (which systemd configures for some crucial services to auto-restart 
them via "WatchdogSec=1min") picks this up and restarts the process. 

  In that case, these crash reports only describe the symptom, not the
  cause. They should be suppressed since they provide no information
  that can be used to diagnose the actual root problem.


  
  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 17 17:18:08 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2014-02-24 (386 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash
  Signal: 6SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe7c6e2f98) at libc-start.c:287
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Touch-packages] [Bug 1493185] Re: missing icons in dash/app scope for ubuntu touch vivid image

[Hawk]

Is there any thing I can do to help with resolving the bug?

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

Title:
  missing icons in dash/app scope for ubuntu touch vivid image

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

Bug description:
  Try porting Ubuntu touch to Sony Xperia L. The icons are missing on
  the dash and in App scope.

  Image of App scope with no icon: http://postimg.org/image/g0twu5pyf

  Following is the OpenGL errors seen in unity log:

  qtmir.mir: SessionListener::starting - this= SessionListener(0x462d5384) 
session= 0x18c4794
  qtmir.sessions: SessionManager::onSessionStarting - sessionName= 
UbuntuLocationService
  qtmir.sessions: Session::Session()  "UbuntuLocationService"
  QOpenGLShader::link: "--From Vertex Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  --From Fragment Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  "
  shader compilation failed: 
  "--From Vertex Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  --From Fragment Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  "
  qtmir.mir: SessionListener::stopping - this= SessionListener(0x462d5384) 
session= 0x18c4794
  QOpenGLShader::link: "--From Vertex Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  --From Fragment Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  "
  QOpenGLShader::link: "--From Vertex Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  --From Fragment Shader:
  Error: Symbol textured defined with different precision in vertex and 
fragment shaders.
  "
  QOpenGLShaderProgram::uniformLocation( shapeTexture ): shader program is not 
linked
  QOpenGLShaderProgram::uniformLocation( sourceTexture ): shader program is not 
linked
  QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked
  QOpenGLShaderProgram::uniformLocation( opacityFactors ): shader program is 
not linked
  QOpenGLShaderProgram::uniformLocation( dfdtFactor ): shader program is not 
linked
  QOpenGLShaderProgram::uniformLocation( sourceOpacity ): shader program is not 
linked
  QOpenGLShaderProgram::uniformLocation( distanceAA ): shader program is not 
linked
  QOpenGLShaderProgram::uniformLocation( textured ): shader program is not 
linked
  QOpenGLShaderProgram::uniformLocation( aspect ): shader program is not linked

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Launchpad Bug Tracker]

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  Confirmed
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1275076] Re: pkexec cannot be used in Unity!

[Andrea Azzarone]

Can you still reproduce this?

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

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

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

Title:
  pkexec cannot be used in Unity!

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  polkit's pkexec replacement for gksu/gksudo, does not work in unity,
  nothing appears to happen. The error can be seen by launching Ubuntu
  12.04 or 12.10 (and possibly 13.10), opening a terminal, and typing
  "unity --replace", then launching an app requiring pkexec in the dash.
  The error "Refusing to render service to dead parents." is shown upon
  launch, and nothing appears to happen on the desktop. I can confirm
  this happens in both Precise and Quantal, and perhaps (untested) in
  Saucy. It doesn't happen in Trusty, as of 30 Jan.  This affects quite
  a few applications, and prevents them from running, and also affects
  mine. For the mean time I'll fix it by using gksudo in my .desktop
  files for Ubuntu only, but it's only a matter of time until gksudo is
  deprecated, and removed from the PPAs. Update: if you adopt gparteds
  method from a bash script, it does work.

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

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

[Touch-packages] [Bug 1498321] [NEW] Touchpad use and multitouch gestures very inconvinient

[Matthias]

Public bug reported:

The use of the touchpad is a horrible user experience on unity. A few
examples:

- Two finger scrolling is too sensitive. (there is no setting to change the 
sensitivity of the touchpad).
- Two finger scrolling all the time activates the window switcher (probably 
because a minor disturbance actually counts as "3 finger tap followed by 
3-fingers hold ") instead of just scrolling.
- Two finger scrolling often highlights the content.
- "4 finger swipe left/right to reveal launcher" is actually useful. 
- "4 finger tap to open dash" often activates right-click and moves cursor 
before dash appears. 
- I tried to learn the 3 finger variations a couple of time, but the never 
stick. Too complicated, not intuitive at all and they also often collide with 
each other.

My suggestion, add a touchpad sensitivity setting and revise the
multitouch options.

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

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

Title:
  Touchpad use and multitouch gestures very inconvinient

Status in unity package in Ubuntu:
  New

Bug description:
  The use of the touchpad is a horrible user experience on unity. A few
  examples:

  - Two finger scrolling is too sensitive. (there is no setting to change the 
sensitivity of the touchpad).
  - Two finger scrolling all the time activates the window switcher (probably 
because a minor disturbance actually counts as "3 finger tap followed by 
3-fingers hold ") instead of just scrolling.
  - Two finger scrolling often highlights the content.
  - "4 finger swipe left/right to reveal launcher" is actually useful. 
  - "4 finger tap to open dash" often activates right-click and moves cursor 
before dash appears. 
  - I tried to learn the 3 finger variations a couple of time, but the never 
stick. Too complicated, not intuitive at all and they also often collide with 
each other.

  My suggestion, add a touchpad sensitivity setting and revise the
  multitouch options.

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

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

[Touch-packages] [Bug 1310280] Re: hud and dash don't take keyboard input

[Andrea Azzarone]

Can you still reproduce this problem?

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

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

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

Title:
  hud and dash don't take keyboard input

Status in Unity HUD:
  Invalid
Status in Unity:
  Incomplete
Status in hud package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Hud and dash (key  or key ) appear correctly, can also be
  closed with the same key, but I can't type anything. Sometimes one or
  two letters can be entered (if I'm fast), but any further input does
  absolutely nothing.

  I've seen a bug related to ibus with same symptoms, but that one is
  fixed (and my problem is not). Further I selected scim with im-config,
  so ibus should not be running at all (but I see ibus related processes
  on my system). Killing those does not solve the problem. SCIM is
  running (but not activated), but killing it does not make hud or dash
  accept keyboard input either. -- I see no other keyboard related
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hud 13.10.1+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Apr 20 21:52:18 2014
  InstallationDate: Installed on 2009-12-23 (1579 days ago)
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 702157] Re: unity reboots when changing tabs in kile or evolution

[NickTh]

Thank you for taking the time to report this bug.  We have tried to
recreate this on the latest release of Ubuntu and cannot reproduce it.
This bug is being marked as Invalid.  If you believe the problem to
still exist in the latest version of Ubuntu please comment on why that
is the case and change the bug status to NEW.

** Changed in: unity (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  unity reboots when changing tabs in kile or evolution

Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Distribution : Maverick.

  Problem with Kile : when I've loaded more than one file and wants to
  switch from one tab to another, Unity seems to turn off and reboot :
  the menus disappear, then the Kile window to (wallpaper appearing),
  then the Kile windos fits all the screen, and finally everything goes
  back to normal. But it happens 95% of the time when I switch from one
  tab to another.

  With Evolution : same thing when switching from Mail to Calendar, or
  Tasks, but only the first time.

  Also, in Evolution Tasks, the Actions menu is missing.

  The Kile bug is a big problem and would prevent using Unity in the future.
  --- 
  Architecture: i386
  CheckboxSubmission: 1cf592f419e1561b4122217c1967344a
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  CompizPlugins: 
[core,ccp,move,resize,place,decoration,vpswitch,workarounds,gnomecompat,svg,neg,dbus,regex,mousepoll,session,widget,text,png,imgjpeg,commands,animation,ezoom,resizeinfo,fade,snap,staticswitcher,cube,rotate,scale,3d,scaleaddon]
  DistroRelease: Ubuntu 10.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Inspiron 1545
  NonfreeKernelModules: wl
  Package: compiz 1:0.8.6-0ubuntu9.1
  PackageArchitecture: all
  PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) 
(prog-if 00 [VGA controller])
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic 
root=UUID=443de4c6-93ca-4189-b94b-d7963a5aff62 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  RelatedPackageVersions:
   xserver-xorg 1:7.5+6ubuntu3
   libgl1-mesa-glx 7.9~git20100924-0ubuntu2
   libdrm2 2.4.21-1ubuntu2.1
   xserver-xorg-video-intel 2:2.12.0-1ubuntu5.1
   xserver-xorg-video-ati 1:6.13.1-1ubuntu5
  Tags: maverick ubuntu-une
  Uname: Linux 2.6.35-25-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
  dmi.bios.date: 10/23/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd10/23/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  system: distro = Ubuntu, architecture = i686, kernel = 2.6.35-25-generic

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

-- 
Mailing list: https://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 1496743] [NEW] /usr/bin/ld.gold: --push-state: unknown option

[Steve Langasek]

On Mon, Sep 21, 2015 at 01:56:46PM -, Launchpad Bug Tracker wrote:
> With gcc 5.2.1-17ubuntu4, we're seeing
> https://launchpadlibrarian.net/218108553/buildlog_ubuntu-wily-amd64
> .ubuntu-ui-toolkit_1.3.1639%2B15.10.20150916.2-0ubuntu1_BUILDING.txt.gz

The error in the log is:

g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,-O1 -fuse-ld=gold 
-o ubuntu-ui-toolkit-launcher .obj/launcher.o .obj/MouseTouchAdaptor.o 
-L/usr/X11R6/lib64 -lQt5Quick -lQt5Gui -lQt5Qml -lQt5Network -lQt5Test 
-lQt5Core -lGL -lpthread 
/usr/bin/ld.gold: --push-state: unknown option
/usr/bin/ld.gold: use the --help option for usage information
collect2: error: ld returned 1 exit status

But --push-state only ever appears in the error message; it does not appear
in the g++ commandline that the build system claims to be invoking.  Has
anyone tracked down the origin of this?  I do see '--push-state' in the
output of 'strings /usr/bin/g++', so it's certainly possible that g++ itself
is adding it to the commandline when invoking ld.  If so this is definitely
a gcc bug, passing extra arguments to ld regardless of which ld is being
called, and it doesn't matter what libraries are being passed.

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

Title:
  /usr/bin/ld.gold: --push-state: unknown option

Status in gcc-5 package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  With gcc 5.2.1-17ubuntu4, we're seeing
  https://launchpadlibrarian.net/218108553/buildlog_ubuntu-wily-amd64
  .ubuntu-ui-
  toolkit_1.3.1639%2B15.10.20150916.2-0ubuntu1_BUILDING.txt.gz

  TJ- on #ubuntu-devel suggested:
  < TJ-> Mirv: bzoltan: the issue could be in qtbase-opensource-src-5.4.2+dfsg 
(qmake) which does "mkspecs/common/gcc-base-unix.conf:19:QMAKE_LFLAGS_USE_GOLD  
 = -fuse-ld=gold" irrespective of libraries being linked.

  Ideas for a proper fix welcome.

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

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

[Touch-packages] [Bug 1404824] Re: [Scopes] There is no way to uninstall a scope on ubuntu phone

[Yuan-Chen Cheng]

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

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

** Changed in: savilerow
   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/1404824

Title:
  [Scopes] There is no way to uninstall a scope on ubuntu phone

Status in Canonical System Image:
  New
Status in The Savilerow project:
  Triaged
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Currently, I only know that "click unregister" may help to remove an
  installed scope. May I know how I can remove an installed scope on the
  phone if a user does not like to have it in the phone?

  -- UX Comment --

  There are two possibilities for "removing" a scope from the phone:

  1 - Unfavourite a scope: 
  If we access the 'Manage Dash' screen (via bottom edge gesture), you can tap 
on the star icon to remove any scope from the Dash (except the Apps Scope). 
After doing this, that scope will not be shonw as part of the Dash pagination. 
You can reverse the action by tapping on the star again.

  2 - Uninstall a scope:
  If we go to the Ubunut Store (accessible from the Apps Scope or by tapping on 
the Store icon on the Manage Dash header) and we search for a specific scope 
(e.g.: Today Scope), we can tap on the 'Uninstall' button to uninstall it from 
the system. A confirmation dialog will prompt you and if you confirm, the scope 
will be uninstalled and therefore removed permantly from the Dash (pagination) 
and the Manage Dash screen. You can reverse this action by installing the scope 
again (same steps as any other app in the store).

  However, we are working towards a entire redesign of Scopes and Dash,
  therefore this is subject to change in the near future. The desired
  solution and specs will be updated as soon as they are available.

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

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

[Touch-packages] [Bug 1277726] Re: As soon as I log in, I am logged out again

[Andrea Azzarone]

Closing because of comment #3.

** Changed in: unity
   Status: New => Invalid

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

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

Title:
  As soon as I log in, I am logged out again

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Type password

  2. Press enter

  This bug does not affect the guest account, which I am using to file
  this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  Uname: Linux 3.12.0-031200-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Feb  8 11:08:42 2014
  InstallationDate: Installed on 2014-01-05 (33 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1437765] Re: No desktop after upgrade to 14.10

[Andrea Azzarone]

Closing the bug as per comment #6.

** Changed in: unity
   Status: New => Invalid

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

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

Title:
  No desktop after upgrade to 14.10

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After upgrading my desktop machine from 14.04 to 14.10, I no longer
  have a desktop.  The login screen works, but after logging in, I get
  just the backdrop image and a mouse pointer.  Nothing else.

  The pointer responds to mouse movements, and I can switch to a text
  console using ctrl-alt-F, which is how I installed KDE in order to
  file this bug.  But I can no longer open a terminal with ctrl-alt-T,
  or switch workspaces with ctrl-alt-.

  My .xsession-errors after logging in showed:

  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  19 (X_GLXQueryServerString)
Serial number of failed request:  22
Current serial number in output stream:  22
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  upstart: hud main process (2389) terminated with status 1
  upstart: unity-settings-daemon main process (2393) terminated with status 1
  upstart: unity7 main process (2405) terminated with status 1
  upstart: gnome-session (Unity) main process (2411) terminated with status 1
  upstart: unity-panel-service main process (2422) terminated with status 1
  upstart: indicator-keyboard main process (2496) terminated with status 1
  upstart: indicator-printers main process (2502) terminated with status 1
  upstart: upstart-dbus-session-bridge main process (2366) terminated with 
status 1
  upstart: indicator-bluetooth main process (2485) killed by TERM signal
  upstart: indicator-power main process (2486) killed by TERM signal
  upstart: indicator-datetime main process (2494) killed by TERM signal
  upstart: indicator-sound main process (2501) killed by TERM signal
  upstart: indicator-session main process (2503) killed by TERM signal
  upstart: indicator-application main process (2536) killed by TERM signal
  upstart: Disconnected from notified D-Bus bus

  This is quite a slow machine, so normally it'd take a while to
  complete a graphical login.  But now, when I log in and immediately
  switch to a graphical console to run "top," it doesn't show much going
  on.  External filesystem volumes are not auto-mounted under /media the
  way they usually are.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: KDE
  Date: Sun Mar 29 09:23:52 2015
  InstallationDate: Installed on 2012-11-25 (853 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago)

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

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

[Touch-packages] [Bug 1221827] Re: HUD Shortcut to Thunderbird Menu Item Disables Text Alignment Menu

[Andrea Azzarone]

Can you still reproduce it?

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

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

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

Title:
  HUD Shortcut to Thunderbird Menu Item Disables Text Alignment Menu

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  If the Unity HUD is used while composing a new Thunderbird HTML email
  message to insert a horizontal line, a subsequent attempt to use the
  text alignment menu fails. Clicking the toolbar button has no effect
  thereafter.

  To reproduce this failure:

  1. Start Thunderbird.

  2. Click "Create a new message" toolbar button to open the HTML
  message composition window.

  3. Enter some text in the message body.

  4. Select the text.

  5. Click the text alignment menu button and choose "Center."

  6. Tap the left  key to bring up the HUD.

  7. Enter the three letters "h", "o", "r".

  8. "Insert > Horizontal Line" becomes the selected default choice.

  9. Press .

  10. Re-select the text entered in step 3 above.

  11. Click the text alignment menu button. The menu will no longer
  display.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
  Uname: Linux 3.2.0-53-generic i686
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  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]
  Date: Fri Sep  6 11:08:39 2013
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1296249] Re: Default workspace navigation key shortcuts do not work

[Andrea Azzarone]

Closing as per comment #2.

** Changed in: unity
   Status: New => Invalid

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

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

Title:
  Default workspace navigation key shortcuts do not work

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Symptoms (on up-to-date Ubuntu 13.10 Saucy installation):
  
  * Default 2x2 workspaces are enabled (Workspace switcher icon in Launchbar):
   (System settings > Appearance > Behaviour : Enable workspaces)
  * Can navigate between workspaces using Workspace switcher in Launchbar or 
   the Super+S key and arrow keys
  * Workspace navigation defaut shortcuts are apparently defined:
   (System settings > Keyboard > Shortcuts > Navigation)
     Eg  'Switch to workspace right' is shown as  'Ctrl+Alt+Right'
     but this key combination does not have any effect.

  Solution / workaround:
  --
  * Install ccsm package:
  $ sudo apt-get install compizconfig-settings-manager
  Run the compiz settings program:
  $ ccsm
  * You should see that 'Desktop Wall' in the Desktop section is not 
checked/enabled
  *  Enable/check 'Desktop Wall' in the Desktop section
  * Exit ccsm
  * Log out and log in again
  * Workspace navigation keys should now work

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Mar 23 12:56:41 2014
  InstallationDate: Installed on 2014-03-14 (8 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 702157] Re: unity reboots when changing tabs in kile or evolution

[NickTh]

Thank you for taking the time to report this bug.  We have tried to
recreate this on the latest release of Ubuntu and cannot reproduce it.
This bug is being marked as Invalid.  If you believe the problem to
still exist in the latest version of Ubuntu please comment on why that
is the case and change the bug status to NEW.

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

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

Title:
  unity reboots when changing tabs in kile or evolution

Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Distribution : Maverick.

  Problem with Kile : when I've loaded more than one file and wants to
  switch from one tab to another, Unity seems to turn off and reboot :
  the menus disappear, then the Kile window to (wallpaper appearing),
  then the Kile windos fits all the screen, and finally everything goes
  back to normal. But it happens 95% of the time when I switch from one
  tab to another.

  With Evolution : same thing when switching from Mail to Calendar, or
  Tasks, but only the first time.

  Also, in Evolution Tasks, the Actions menu is missing.

  The Kile bug is a big problem and would prevent using Unity in the future.
  --- 
  Architecture: i386
  CheckboxSubmission: 1cf592f419e1561b4122217c1967344a
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  CompizPlugins: 
[core,ccp,move,resize,place,decoration,vpswitch,workarounds,gnomecompat,svg,neg,dbus,regex,mousepoll,session,widget,text,png,imgjpeg,commands,animation,ezoom,resizeinfo,fade,snap,staticswitcher,cube,rotate,scale,3d,scaleaddon]
  DistroRelease: Ubuntu 10.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Inspiron 1545
  NonfreeKernelModules: wl
  Package: compiz 1:0.8.6-0ubuntu9.1
  PackageArchitecture: all
  PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) 
(prog-if 00 [VGA controller])
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic 
root=UUID=443de4c6-93ca-4189-b94b-d7963a5aff62 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  RelatedPackageVersions:
   xserver-xorg 1:7.5+6ubuntu3
   libgl1-mesa-glx 7.9~git20100924-0ubuntu2
   libdrm2 2.4.21-1ubuntu2.1
   xserver-xorg-video-intel 2:2.12.0-1ubuntu5.1
   xserver-xorg-video-ati 1:6.13.1-1ubuntu5
  Tags: maverick ubuntu-une
  Uname: Linux 2.6.35-25-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
  dmi.bios.date: 10/23/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd10/23/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  system: distro = Ubuntu, architecture = i686, kernel = 2.6.35-25-generic

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

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

[Touch-packages] [Bug 1497547] Re: Mir on X11 server crashed: mir_proving_server: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

[Daniel van Vugt]

As a workaround you can run Mir natively using the option:   --vt 1
Then just switch to it with Ctrl+Alt+F1/F7

** Summary changed:

- mir_proving_server assert failure: mir_proving_server: 
../../src/xcb_io.c:274: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
+ Mir on X11 server crashed: mir_proving_server: ../../src/xcb_io.c:274: 
poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

** Information type changed from Private to Public

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

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

Title:
  Mir on X11 server crashed: mir_proving_server: ../../src/xcb_io.c:274:
  poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

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

Bug description:
  mir_proving_server assert failure: mir_proving_server:
  ../../src/xcb_io.c:274: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost' failed.

  mousing arround with mir on x

   mir_proving_server --platform-input-lib server-mesa-x11.so.4
   mir_demo_client_egltriangle

  died wile mousing arround egltriangle's window

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: mir-demos 0.15.1+15.10.20150903-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AssertionMessage: mir_proving_server: ../../src/xcb_io.c:274: poll_for_event: 
Assertion `!xcb_xlib_threads_sequence_lost' failed.
  CurrentDesktop: Unity
  Date: Sat Sep 19 15:13:02 2015
  ExecutablePath: /usr/bin/mir_proving_server
  InstallationDate: Installed on 2015-09-18 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918)
  ProcCmdline: mir_proving_server --platform-input-lib server-mesa-x11.so.4
  Signal: 6
  SourcePackage: mir
  StacktraceTop:
   __assert_fail_base (fmt=0x7fbfd6d7c028 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fbfd294a7a0 
"!xcb_xlib_threads_sequence_lost", file=file@entry=0x7fbfd294a5eb 
"../../src/xcb_io.c", line=line@entry=274, 
function=function@entry=0x7fbfd294aaa6 "poll_for_event") at assert.c:92
   __GI___assert_fail (assertion=0x7fbfd294a7a0 
"!xcb_xlib_threads_sequence_lost", file=0x7fbfd294a5eb "../../src/xcb_io.c", 
line=274, function=0x7fbfd294aaa6 "poll_for_event") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  Title: mir_proving_server assert failure: mir_proving_server: 
../../src/xcb_io.c:274: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  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/mir/+bug/1497547/+subscriptions

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

[Touch-packages] [Bug 1280555] Re: Square Icons should not have a border

[Andrea Azzarone]

** Changed in: unity
   Status: Incomplete => Opinion

** Changed in: unity (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: unity
   Importance: Low => Wishlist

** Changed in: unity (Ubuntu)
   Importance: Low => Wishlist

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

Title:
  Square Icons should not have a border

Status in Unity:
  Opinion
Status in unity package in Ubuntu:
  Opinion

Bug description:
  Square Icons (e.g. the new friends icon in trusty) shouldn't have an
  additional border around them.

  I know this bug is similar to #703536, but as more and more icons of
  this (unity8) style land in trusty I think it would be best to
  evaluate adding such an improvement again.

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

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

[Touch-packages] [Bug 1496743] Re: /usr/bin/ld.gold: --push-state: unknown option

[Steve Langasek]

The --push-state tracks to a Debian-specific patch in the source,
debian/patches/pr65913-workaround.diff.  This was added to fix Debian
bug #797577, a build failure with a particular boost-using package in
Debian.

This new failure was introduced in the latest upload (5.2.1-17ubuntu4)
and can be resolved by reverting the change in this version to
debian/rules.patch.  If this is an urgent problem (and it looks like it
might be, if it impacts all qmake-using packages in the archive), I
would recommend that someone upload this revert now, until a cleaner fix
for the original bug can be found.

** Changed in: gcc-5 (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gcc-5 (Ubuntu)
 Assignee: Canonical Foundations Team (canonical-foundations) => Matthias 
Klose (doko)

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

Title:
  /usr/bin/ld.gold: --push-state: unknown option

Status in gcc-5 package in Ubuntu:
  Triaged
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  With gcc 5.2.1-17ubuntu4, we're seeing
  https://launchpadlibrarian.net/218108553/buildlog_ubuntu-wily-amd64
  .ubuntu-ui-
  toolkit_1.3.1639%2B15.10.20150916.2-0ubuntu1_BUILDING.txt.gz

  TJ- on #ubuntu-devel suggested:
  < TJ-> Mirv: bzoltan: the issue could be in qtbase-opensource-src-5.4.2+dfsg 
(qmake) which does "mkspecs/common/gcc-base-unix.conf:19:QMAKE_LFLAGS_USE_GOLD  
 = -fuse-ld=gold" irrespective of libraries being linked.

  Ideas for a proper fix welcome.

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

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

[Touch-packages] [Bug 702157] Re: unity reboots when changing tabs in kile or evolution

[NickTh]

Thank you for taking the time to report this bug.  We have tried to
recreate this on the latest release of Ubuntu and cannot reproduce it.
This bug is being marked as Invalid.  If you believe the problem to
still exist in the latest version of Ubuntu please comment on why that
is the case and change the bug status to NEW.

** Changed in: unity
   Status: Confirmed => Invalid

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

Title:
  unity reboots when changing tabs in kile or evolution

Status in Unity:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Distribution : Maverick.

  Problem with Kile : when I've loaded more than one file and wants to
  switch from one tab to another, Unity seems to turn off and reboot :
  the menus disappear, then the Kile window to (wallpaper appearing),
  then the Kile windos fits all the screen, and finally everything goes
  back to normal. But it happens 95% of the time when I switch from one
  tab to another.

  With Evolution : same thing when switching from Mail to Calendar, or
  Tasks, but only the first time.

  Also, in Evolution Tasks, the Actions menu is missing.

  The Kile bug is a big problem and would prevent using Unity in the future.
  --- 
  Architecture: i386
  CheckboxSubmission: 1cf592f419e1561b4122217c1967344a
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  CompizPlugins: 
[core,ccp,move,resize,place,decoration,vpswitch,workarounds,gnomecompat,svg,neg,dbus,regex,mousepoll,session,widget,text,png,imgjpeg,commands,animation,ezoom,resizeinfo,fade,snap,staticswitcher,cube,rotate,scale,3d,scaleaddon]
  DistroRelease: Ubuntu 10.10
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Inspiron 1545
  NonfreeKernelModules: wl
  Package: compiz 1:0.8.6-0ubuntu9.1
  PackageArchitecture: all
  PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) 
(prog-if 00 [VGA controller])
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic 
root=UUID=443de4c6-93ca-4189-b94b-d7963a5aff62 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  RelatedPackageVersions:
   xserver-xorg 1:7.5+6ubuntu3
   libgl1-mesa-glx 7.9~git20100924-0ubuntu2
   libdrm2 2.4.21-1ubuntu2.1
   xserver-xorg-video-intel 2:2.12.0-1ubuntu5.1
   xserver-xorg-video-ati 1:6.13.1-1ubuntu5
  Tags: maverick ubuntu-une
  Uname: Linux 2.6.35-25-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
  dmi.bios.date: 10/23/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd10/23/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  system: distro = Ubuntu, architecture = i686, kernel = 2.6.35-25-generic

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

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

[Touch-packages] [Bug 1498310] Re: udev is missing /lib/udev/udev-finish in wily

[Martin Pitt]

udev-finish.service is gone, together with /lib/udev/udev-finish. That's
quite deliberate, we don't need it any more.

Please give me the output of "sudo systemctl status -l udev-
finish.service". Thanks!

** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

** Summary changed:

- udev is missing /lib/udev/udev-finish in wily
+ udev-finish.service still present in wily

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

Title:
  udev-finish.service still present in wily

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  $ apt-cache policy udev
  udev:
Installed: 225-1ubuntu4
Candidate: 225-1ubuntu4
Version table:
   *** 225-1ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  The udev package in wily is missing /lib/udev/udev-finish, hence systemd 
reports the udev-finish.service as failed.
  Placing this script , which is in udev package 219-7ubuntu6 (vivid-updates), 
into the correct location rectifies this.

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

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

[Touch-packages] [Bug 1471560] Re: Laptop does not wake properly from suspend/sleep

[Raphael Mankin]

I  deleted lightlocker and replaced it with xscreensaver. Since then I
have had no problems.

IIRC I already did a BIOS update, but I'm not absolutely sure. I know I
updated the BIOS on *a* computer, but was it this one?

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

Title:
  Laptop does not wake properly from suspend/sleep

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am running xfce4/lightdm/lihg-locker on ubuntu 14.04.2

  The bug does not always manifest itself, but does so frequently.

  When waking from sleep/suspend I get the unlock screen but after
  entering my password the main display does not appear; it remains
  blanked. Sometimes re-suspending and re-waking the machine resolves
  the problem, but not always.

  Alternatively, the main screen does appear ut the mouse pointer is
  missing. I can tell where it ought to be by the highlighting of menu
  items. In this case re-sleep/re-waken has always resolved the problem.

  Sometimes I can get to a console seesion with ctl-alt-f1. In this case
  killing xfce4-session clears the problem, but after doing this a few
  times skype will not restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul  5 15:59:03 2015
  InstallationDate: Installed on 2015-06-03 (31 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.16.0-48-generic, x86_64: installed
   virtualbox, 4.3.10, 3.16.0-49-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 
[1002:9591] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2127]
  InstallationDate: Installed on 2015-06-03 (109 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1439): WARNING **: Failed to load user background: 
Failed to open file '/home/raph/Pictures/Firefox_wallpaper.png': Permission 
denied
   
   ** (lightdm-gtk-greeter:1439): WARNING **: Failed to load user image: Failed 
to open file '/home/raph/.face': Permission denied
   init: indicator-power main process (1474) killed by TERM signal
   init: indicator-application main process (1483) killed by TERM signal
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1497): WARNING **: Failed to load user image: Failed 
to open file '/home/raph/.face': Permission denied
   init: indicator-power main process (1531) killed by TERM signal
   init: indicator-application main process (1543) killed by TERM signal
  MachineType: LENOVO 4063A46
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=6be0f400-b5cc-4ff7-9adb-2b5cda6c2bc2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  Tags:  trusty ubuntu
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/09/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET56WW (2.02 )
  dmi.board.name: 4063A46
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 1780238
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6FET56WW(2.02):bd01/09/2009:svnLENOVO:pn4063A46:pvrThinkPadW500:rvnLENOVO:rn4063A46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4063A46
  dmi.product.version: ThinkPad W500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Touch-packages] [Bug 1414303] Re: sudo show predefine PAM prompt with some PAM Modules, no default sudo prompt

[Mathieu Trudel-Lapierre]

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

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

Title:
  sudo show predefine PAM prompt with some PAM Modules, no default sudo
  prompt

Status in sudo package in Ubuntu:
  In Progress

Bug description:
  I use libpam-krb5 for authentication, when I use sudo it show this
  prompt

  Password:

  Not the default of sudo

  [sudo] password for (user):

  But if it's set LANG=C (no locale) with module libpam-krb5 show the
  default prompt of sudo.

  With the module pam_unix (default of system) work without problems.

  Then the problem is in locale support of one of these packages. At
  check the source code of two I reached the conclusion.

  1. libpam-krb5 not support translations.

  2. sudo replaces the PAM prompt if this is "Password:" or translate of
  this. But sudo only check "Password:" translated on current language
  config (example "Contraseña:" on "es" locale).

  This bug not cause "real" problem but it may reveal the authentication
  system in use.

  This report has attached a (possible) patch of sudo for fix the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: sudo 1.8.9p5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Sat Jan 24 07:50:23 2015
  InstallationDate: Installed on 2015-01-12 (12 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1495207] Re: BQ E4.5 (r24): after fine update to r25 system is reported as r-1 and as "never" updated

[Matthias Apitz]

some small remarks:

1) the chroot in *my* phone  is based on http://cdimage.ubuntu.com
/ubuntu-touch/vivid/daily-preinstalled/current/vivid-preinstalled-touch-
armhf.tar.gz and my wife's phone was never polluted with thing like
this; she does not do Linux/UNIX;

2) we can just calm and wait for the next such incident and nail it down
then;

thanks

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

Title:
  BQ E4.5 (r24): after fine update to r25 system is reported as r-1 and
  as "never" updated

Status in Canonical System Image:
  New
Status in system-image package in Ubuntu:
  Confirmed

Bug description:
  After the vacation I have updated today (September 13, 2015)  my BQ
  4.5 and the one of my wife to r25. Both updates went without any
  problem and mine does not show any issue.  The one of my wife shows in
  About the device window:

  OS number: -1 (and not r25)
  last updated: never
  version: Ubuntu 15.04-armhf (20150825-170536)

  What went wrong and what can I do? I'm afraid that the next update will
  fail completely now because it can not see the current version.

  Apart of this the device is working.

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

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

[Touch-packages] [Bug 1498594] Re: Rejected send message auth.log warnings

[Sebastien Bacher]

dbus[903]: [system] Rejected send message, 2 matched rules;
type="method_call", sender=":1.576" (uid=123 pid=3965
comm="/usr/lib/i386-linux-gnu/indicator-bluetooth/indica")
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=833
comm="/usr/lib/bluetooth/bluetoothd ")

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided => High

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

Title:
  Rejected send message auth.log warnings

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Using wily desktop, those errors are in the auth.log

  dbus[903]: [system] Rejected send message, 2 matched rules;
  type="method_call", sender=":1.576" (uid=123 pid=3965
  comm="/usr/lib/i386-linux-gnu/indicator-bluetooth/indica")
  interface="org.freedesktop.DBus.Properties" member="GetAll" error
  name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=833
  comm="/usr/lib/bluetooth/bluetoothd ")

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

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

[Touch-packages] [Bug 1497785] Re: indicator-bluetooth-service crashed with SIGSEGV in bluez_update_device()

[Sebastien Bacher]

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

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1497928
   
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service:11:bluez_update_device:___lambda5_:lambda5__object_manager_interfaces_added:g_closure_invoke:signal_emit_unlocked_R

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

Title:
  indicator-bluetooth-service crashed with SIGSEGV in
  bluez_update_device()

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Installing daily updates via apt and suddenly I got this crash popup.
  Wasn't actually using bluetooth at all.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: indicator-bluetooth 0.0.6+15.10.20150915-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 20 22:32:15 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  InstallationDate: Installed on 2014-06-16 (461 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x408515:  mov(%rax,%r12,4),%rdi
   PC (0x00408515) ok
   source "(%rax,%r12,4)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-bluetooth
  StacktraceTop:
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-bluetooth-service crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to wily on 2015-05-09 (134 days ago)
  UserGroups: adm autopilot cdrom dialout dip kismet libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Touch-packages] [Bug 1497600] Re: indicator-bluetooth-service crashed with SIGSEGV in bluez_update_device()

[Sebastien Bacher]

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

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1497928
   
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service:11:bluez_update_device:___lambda5_:lambda5__object_manager_interfaces_added:g_closure_invoke:signal_emit_unlocked_R

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

Title:
  indicator-bluetooth-service crashed with SIGSEGV in
  bluez_update_device()

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  No information available. The indicator is available in the head-bar
  of the gui.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: indicator-bluetooth 0.0.6+15.10.20150915-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Sep 19 14:47:11 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  InstallationDate: Installed on 2015-07-08 (73 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150707)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=de_AT.UTF-8
   LANGUAGE=de_AT:de
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x408515:  mov(%rax,%r12,4),%rdi
   PC (0x00408515) ok
   source "(%rax,%r12,4)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-bluetooth
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers

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

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

[Touch-packages] [Bug 1497928] Re: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service:11:bluez_update_device:___lambda5_:____lambda5__object_manager_interfaces_added:g_closure_i

[Sebastien Bacher]

** Tags added: rls-w-incoming

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

Title:
  /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-
  
service:11:bluez_update_device:___lambda5_:lambda5__object_manager_interfaces_added:g_closure_invoke:signal_emit_unlocked_R

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-bluetooth.  This problem was most recently seen
  with version 0.0.6+15.10.20150915-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5819c2721723a35013649535ed691c84f7eb06d7
  contains more details.

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

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

[Touch-packages] [Bug 1481798] Re: package:modemmanager:1.4.10-1:subprocess installed post-installation script returned error exit status 100

[Christopher]

I had the same issue upgrading, but was able to force restart and fix
everything afterwards with Synaptic. It took a few reboots and Bleachbit
to get rid of the apport errors, but all is well now. It isn't my work
computer.

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

Title:
  package:modemmanager:1.4.10-1:subprocess installed post-installation
  script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding modemmanager.  This problem was most recently seen with
  version 1.4.10-1, the problem page at
  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738
  contains more details.

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

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

[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

[Ivan Zakharyaschev]

Some good results: the somewhat offending module was coretemp. (Here, I
have an Intel processor. On the computer, where there is no
crash/reboot, the processor is AMD, and there k10temp or k9temp module
is used. The other computer is fine with 14.04 (Trusty) and 14.10
(Utopic).)

Moving coretemp module away makes the system boot successful in a much
more stable way. But still there is a possibility of a crash/reboot at a
much earlier stage of the boot; that is not affected by removing
coretemp.

I've also moved away samsung-laptop.ko , because it was also near the
place where the crash happened (see below about my usage of the
modprobe-debugging script), but that seems not to be essential as a
remedy.

I've modified the above script a bit (not to break on spaces in the
modaliases, and to print a summary about how many modeprobes are going
to be done to know how the progress goes). I also modified the sleep
time in my experiments (1 second or 0 seconds). And I added a call to
sync, because I was saving the output to a file with tee.

With a 1 second delay, there was no crash at all. WIth 0 second delay,
the crash happened between loading coretemp and samsung-laptop. (I have
compared the output on an i386 kernel and the crashing amd64 kernel.)

Here is my modified script:

$ cat /sbin/modprobedebug_udev.sh
#!/bin/bash

print_modules() {
find /sys -name modalias -print0 | xargs -0 cat
}

echo 'This much modules I am about to process (the output of wc):'
print_modules | wc

print_modules | while read module ; do
if [ -n "$module" ]; then
echo "Loading module for $module in 0 seconds"
sync
#sleep 1
/sbin/modprobe -a -v "$module"
udevadm settle
fi
done

I ran it like this:

modprobedebug_udev.sh | tee modprobedebug-"$(uname -r)".txt

The diff between the results (after the crash, you see lines prefixed
with minuses only; with 0 delay):

# diff -du modprobedebug-3.19.0-28-generic.txt 
modprobedebug-4.2.0-10-generic.txt 
--- modprobedebug-3.19.0-28-generic.txt 2015-09-22 16:54:09.924195494 +0300
+++ modprobedebug-4.2.0-10-generic.txt  2015-09-22 16:52:49.864205114 +0300
@@ -1,149 +1,70 @@
 This much modules I am about to process (the output of wc):
-112 1143892
+113 1153973
 Loading module for pci:v8086d2A40sv144DsdC042bc06sc00i00 in 0 
seconds
 Loading module for pci:v10DEd06E8sv144DsdC042bc03sc00i00 in 0 
seconds
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/i2c/algos/i2c-algo-bit.ko 
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/gpu/drm/drm.ko 
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/gpu/drm/drm_kms_helper.ko 
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/gpu/drm/ttm/ttm.ko 
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/acpi/video.ko 
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/platform/x86/wmi.ko 
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/platform/x86/mxm-wmi.ko 
-insmod 
/lib/modules/3.19.0-28-generic/kernel/drivers/gpu/drm/nouveau/nouveau.ko 
 Loading module for pci:v8086d2A41sv144DsdC042bc06sc04i00 in 0 
seconds
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/pci/hotplug/shpchp.ko 
-Loading module for usb:v1D6Bp0001d0319dc09dsc00dp00ic09isc00ip00in00 in 0 
seconds
+insmod /lib/modules/4.2.0-10-generic/kernel/drivers/pci/hotplug/shpchp.ko 
+Loading module for usb:v1D6Bp0001d0402dc09dsc00dp00ic09isc00ip00in00 in 0 
seconds
 Loading module for pci:v8086d2937sv144DsdC042bc0Csc03i00 in 0 
seconds
-Loading module for usb:v1D6Bp0001d0319dc09dsc00dp00ic09isc00ip00in00 in 0 
seconds
+Loading module for usb:v1D6Bp0001d0402dc09dsc00dp00ic09isc00ip00in00 in 0 
seconds
 Loading module for pci:v8086d2938sv144DsdC042bc0Csc03i00 in 0 
seconds
-Loading module for usb:v1D6Bp0001d0319dc09dsc00dp00ic09isc00ip00in00 in 0 
seconds
+Loading module for usb:v1D6Bp0001d0402dc09dsc00dp00ic09isc00ip00in00 in 0 
seconds
 Loading module for pci:v8086d2939sv144DsdC042bc0Csc03i00 in 0 
seconds
 Loading module for usb:v0AC8pC302d0100dcEFdsc02dp01ic0Eisc01ip00in00 in 0 
seconds
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/media/media.ko 
-insmod 
/lib/modules/3.19.0-28-generic/kernel/drivers/media/v4l2-core/videodev.ko 
-insmod 
/lib/modules/3.19.0-28-generic/kernel/drivers/media/v4l2-core/v4l2-common.ko 
-insmod 
/lib/modules/3.19.0-28-generic/kernel/drivers/media/v4l2-core/videobuf2-core.ko 
-insmod 
/lib/modules/3.19.0-28-generic/kernel/drivers/media/v4l2-core/videobuf2-memops.ko
 
-insmod 
/lib/modules/3.19.0-28-generic/kernel/drivers/media/v4l2-core/videobuf2-vmalloc.ko
 
-insmod /lib/modules/3.19.0-28-generic/kernel/drivers/media/usb/uvc/uvcvideo.ko 
+insmod /lib/modules/4.2.0-10-generic/kernel/drivers/media/media.ko 
+insmod 

[Touch-packages] [Bug 1148116] Re: not all packages from PPAs have '[origin: ' in Package section

[Brian Murray]

I noticed that the Error Tracker retracers experience many retrace
failures from packages that are not official Ubuntu packages, for
example we asked for core files, and failed to retrace, for all of the
following crashes.

OOPS   Package  
 Release
c4e3cf3e-5db4-11e5-a4ce-fa163e4aaad4  phoneflashtool 12.04
a29e7956-5d96-11e5-aa63-fa163e4ccdf2  rstudio   12.04
dd29fcd4-5ec8-11e5-940c-fa163e22e467  imule  12.04
ffa4c758-5d92-11e5-afe2-fa163e78b027   ultimate-player 12.04
0a01a590-5da2-11e5-aaef-fa163e339c81   sogoupinyin  12.04
ed60591e-5ddc-11e5-974e-fa163e707a72 galicaster  12.04 (modified 
conf file?)

We shouldn't be asking for core files for these crashes because these
packages aren't from Ubuntu, but we are because Precise does not contain
the fix for this bug.


** Also affects: apport (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

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

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

Title:
  not all packages from PPAs have '[origin: ' in Package section

Status in Daisy:
  Invalid
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Triaged

Bug description:
  Test Case
  -
  1) Install galicaster package from wiki.teltek.es (or any other random deb 
file will do)
  2) Run the executable
  3) Find the pid of the program and kill it with signal 11
  4) Inspect the .crash file (after it is finished being written) and observe 
the "Package: " key doesn't not contain "[origin: unknown]"

  With the version of apport from -proposed it will contain information
  about it being from an unknown origin.

  
  I was querying for columns in the counters column family starting with 
'Ubuntu ' as I was looking for the counts of bugs reported about packages.  In 
the column family I discovered 'Ubuntu 12.10:indicator-stickynotes' and was 
having trouble finding errors for that package because it is from a PPA.  Given 
that the package is from a PPA it shouldn't be appearing in the counters column 
family at all though.

  From daisy/submit.py:

  package = data.get('Package', '')
  src_package = data.get('SourcePackage', '')
  problem_type = data.get('ProblemType', '')
  third_party = False
  if '[origin:' in package:
  third_party = True

  Then before running update_release_pkg_counter we check for 'if not
  third_party'.  Looking at least some of the oops for indicator-
  stickynotes all of them had '[origin:' in the Package key.

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

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

[Touch-packages] [Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language

[Treviño]

** No longer affects: gnome-screensaver (Ubuntu)

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

Title:
  Lock screen uses last active window's language instead of default
  keyboard language

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Lock screen (gnome-screensaver) uses last active window's language
  (keyboard layout) instead of default keyboard language.

  Steps to reproduce this bug:
  1. In the system Text Entry settings:
1a. add two or more languages to the input sources list, e.g. English (as 
first and default) and Russian (as second);
1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock).
1c. Select "Allow different sources for each window" radio button.
1d. Select "New windows use the default source" radio button.
  2. Run any application (e.g. gedit) and switch keyboard to second input 
language (Russian).
  3. Lock the screen (Ctrl+Alt+L) or just wait idle time.
  4. See what language set by default for password input in the lock screen.

  Expected: lock screen uses first input language (English) by default.
  What happened instead: lock screen uses last active window's language 
(Russian).

  Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds)
  gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9

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

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

[Touch-packages] [Bug 1414303] Re: sudo show predefine PAM prompt with some PAM Modules, no default sudo prompt

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/sudo

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

Title:
  sudo show predefine PAM prompt with some PAM Modules, no default sudo
  prompt

Status in sudo package in Ubuntu:
  In Progress

Bug description:
  I use libpam-krb5 for authentication, when I use sudo it show this
  prompt

  Password:

  Not the default of sudo

  [sudo] password for (user):

  But if it's set LANG=C (no locale) with module libpam-krb5 show the
  default prompt of sudo.

  With the module pam_unix (default of system) work without problems.

  Then the problem is in locale support of one of these packages. At
  check the source code of two I reached the conclusion.

  1. libpam-krb5 not support translations.

  2. sudo replaces the PAM prompt if this is "Password:" or translate of
  this. But sudo only check "Password:" translated on current language
  config (example "Contraseña:" on "es" locale).

  This bug not cause "real" problem but it may reveal the authentication
  system in use.

  This report has attached a (possible) patch of sudo for fix the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: sudo 1.8.9p5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Sat Jan 24 07:50:23 2015
  InstallationDate: Installed on 2015-01-12 (12 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

[Michał Sawicz]

The above log suggests it's not the tool that's failing, but rather the
shell environment isn't complete - i.e. dbus and upstart details are not
available.

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

Title:
  Automated screen unlock not working on wily images

Status in unity8 package in Ubuntu:
  New

Bug description:
  The method to automatically unlock the screen prior to running
  autopilot tests is not working on wily images. For example:

  https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-
  mako/417/console

  The CI automation uses this script to setup and perform the unlock:
  
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh

  The failure is seen on images from "ubuntu-touch/devel-
  proposed/ubuntu", in this case image 276.

  Attached is the full console log from that run.

  [The relavent messages are:]
  I: Unlock attempt 1 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 2 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 3 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 4 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 5 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Too many unlock failures, giving up

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

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

[Touch-packages] [Bug 1498591] [NEW] Rejected send message auth.log errors

[Sebastien Bacher]

Public bug reported:

Using wily desktop, seems to be triggered when using e.g xchat-gnome and
receiving messages integrated to the indicator

"dbus[903]: [system] Rejected send message, 9 matched rules;
type="method_return", sender=":1.6" (uid=0 pid=874
comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)"
member="(unset)" error name="(unset)" requested_reply="0"
destination=":1.66" (uid=1000 pid=2311 comm="/usr/lib/i386-linux-gnu
/indicator-messages/indicat")"

** Affects: indicator-messages (Ubuntu)
 Importance: High
 Status: New


** Tags: rls-w-incoming

** Changed in: indicator-messages (Ubuntu)
   Importance: Undecided => High

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

Title:
  Rejected send message auth.log errors

Status in indicator-messages package in Ubuntu:
  New

Bug description:
  Using wily desktop, seems to be triggered when using e.g xchat-gnome
  and receiving messages integrated to the indicator

  "dbus[903]: [system] Rejected send message, 9 matched rules;
  type="method_return", sender=":1.6" (uid=0 pid=874
  comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)"
  member="(unset)" error name="(unset)" requested_reply="0"
  destination=":1.66" (uid=1000 pid=2311 comm="/usr/lib/i386-linux-gnu
  /indicator-messages/indicat")"

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

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

[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

[Ivan Zakharyaschev]

And I needed to add "debug" kernel parameter as a workaround, otherwise
the boot was not stable during the early stage.

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in udev package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  

[Touch-packages] [Bug 1455241] Re: Gnome window manager dies shortly after login

[Fabio Marconi]

Hallo
Still this issue reproducible with the latest upgrades ?
Best regards

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

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

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

Title:
  Gnome window manager dies shortly after login

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Whenever I log in, the window manager dies immediately. The file menus
  goes missing in all windows and it is not possible to switch between
  windows with alt+tab. I always have to invoke gnome-wm --replace from
  the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session-flashback 1:3.8.0-1ubuntu12.2
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 22:58:20 2015
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-17 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

[Ivan Zakharyaschev]

Now, as I have localized the problem, I'm ready to debug the problems of
the coretemp module, if you give me advices.

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

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

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

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

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  

[Touch-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart

[Ivan Zakharyaschev]

** Tags added: wily

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

Title:
  booting with amd64 kernel and completely i386 userland is unstable
  during the system upstart

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
  so I added that architecture and apt-get-installed the amd64 linux-
  image and linux-image-extra (I learned this was possible thanks to the
  advice at http://askubuntu.com/a/635774/19753 ).

  However, the system upstart procedure more often fails than not: it
  fails by rebooting the computer. (Only around 1 time of 4 is
  successful.)

  A limited system start is (probably, always) successful: either with
  init=/bin/bash parameter to the kernel, or choosing the recovery boot
  option. (However, if I "resume" from the recovery menu, or run "exec
  init" in bash, then the upstart procedure is similarly unstable: it
  usually fails/crashes and reboots.)

  I checked my suspection that  the video driver (nouveau) and X might
  be involved, but that turned out not true: the upstart procedure is
  similarly unstable with "nomodesetting" kernel parameter and without,
  booting into runlevel 3 or the default one.

  Perhaps, I'd like to debug the upstart procedure step-by-step to
  detect which step makes the system crash and reboot, but I don't know
  how. As concerns the timing, the moment the reboot happens can be
  different: it can happen rather early (when I see the message about
  activating the swap) or much later.

  If the system upstart procedure has completed successfully, then it
  works in a quite stable manner and doesn't crash/reboot. So, there is
  something bad specifically during the system upstart procedure.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 12 18:36:28 2015
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: 
'/etc/at.deny']
  modified.conffile..etc.cron.daily.upstart: [modified]
  modified.conffile..etc.cups.cups.browsed.conf: [modified]
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.binfmt.support: [modified]
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
  mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
  mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
  mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
  mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
  mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
  mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
  --- 
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marsmorgana   1972 F pulseaudio
  CRDA:
   country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
  InstallationDate: Installed on 2014-06-04 (464 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-44-generic N/A
   linux-backports-modules-3.16.0-44-generic  N/A
   linux-firmware 1.138.1
  Tags: utopic utopic third-party-packages
  Uname: Linux 3.16.0-44-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
  

[Touch-packages] [Bug 1498594] [NEW] Rejected send message auth.log warnings

[Sebastien Bacher]

Public bug reported:

Using wily desktop, those errors are in the auth.log

dbus[903]: [system] Rejected send message, 2 matched rules;
type="method_call", sender=":1.576" (uid=123 pid=3965
comm="/usr/lib/i386-linux-gnu/indicator-bluetooth/indica")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=833
comm="/usr/lib/bluetooth/bluetoothd ")

** Affects: indicator-bluetooth (Ubuntu)
 Importance: High
 Status: New


** Tags: rls-w-incoming

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

Title:
  Rejected send message auth.log warnings

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Using wily desktop, those errors are in the auth.log

  dbus[903]: [system] Rejected send message, 2 matched rules;
  type="method_call", sender=":1.576" (uid=123 pid=3965
  comm="/usr/lib/i386-linux-gnu/indicator-bluetooth/indica")
  interface="org.freedesktop.DBus.Properties" member="GetAll" error
  name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=833
  comm="/usr/lib/bluetooth/bluetoothd ")

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

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

[Touch-packages] [Bug 1457518] Re: Knime freezes after viewing a plot (since upgrade to 15.04)

[Fabio Marconi]

Hallo Igor
The problem you are reporting isn't related to Unity, but only to the app that 
freeze.
Can you please verify with the developer if it can work on 15.04 or is only 
designed for LTS relases ?
Best regards


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

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

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

Title:
  Knime freezes after viewing a plot (since upgrade to 15.04)

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Knime (an eclipse based program) https://www.knime.org/ was working
  perfectly in 14.04. Since my upgrade to 15.05 each time a try to
  visualize any kind of plot or table (that means a new window), the new
  window is created and the plot appears. But, from that point on, Knime
  entirely freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu May 21 16:40:55 2015
  DistUpgraded: 2015-04-28 15:12:19,082 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1522]
  InstallationDate: Installed on 2014-06-20 (335 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK Computer Inc. N53Jq
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=b4957094-21ba-430f-b351-d88669003f19 ro quiet splash
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago)
  dmi.bios.date: 09/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N53Jq.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N53Jq
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN53Jq.207:bd09/30/2010:svnASUSTeKComputerInc.:pnN53Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN53Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N53Jq
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu May 21 11:27:54 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1498474] Re: Incorrect MTU on VPN connect

[Ubuntu Foundations Team Bug Bot]

The attachment "upstream patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Incorrect MTU on VPN connect

Status in NetworkManager:
  In Progress
Status in network-manager package in Ubuntu:
  New

Bug description:
  On update to wily, vpnc vpn connects, but MTU is incorrectly set to
  1500, instead of default value which is 1412.  This results in
  connectivity issues (packet loss).

  Gnomezilla bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=754781

  I have attached the included patch from above for convenience, and
  tested that this indeed resolves the issue for me.

  It might be worth mentioning that I had to disable the built in tests
  (--enable-tests=no), or pakage generation with "debuild -us -uc -b"
  fails on 2 of the tests relating to ipv6.

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

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

[Touch-packages] [Bug 1498580] [NEW] Images added to Pictures folder don't show up

[Víctor R . Ruiz]

Public bug reported:

Test case.
- Open gallery app.
- Go to the Events view.
- Connect the phone to the desktop via MTP.
- Copy two JPG files.

Expected result.
- Both files are displayed in the Events tab.

Actual result.
- Only one of them shows.

current build number: 119
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en

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

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Assignee: Arthur Mello (artmello)
 Status: New


** Tags: qa-silo

** Tags added: qa-silo

** 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 gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1498580

Title:
  Images added to Pictures folder don't show up

Status in Canonical System Image:
  New
Status in gallery-app package in Ubuntu:
  New

Bug description:
  Test case.
  - Open gallery app.
  - Go to the Events view.
  - Connect the phone to the desktop via MTP.
  - Copy two JPG files.

  Expected result.
  - Both files are displayed in the Events tab.

  Actual result.
  - Only one of them shows.

  current build number: 119
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

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

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

[Touch-packages] [Bug 1498562] Re: bliptv service has been closed, should disable the option

[Sebastien Bacher]

reported to debiian https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=799791

** Changed in: grilo-plugins (Ubuntu)
   Importance: Undecided => High

** Changed in: grilo-plugins (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  bliptv service has been closed, should disable the option

Status in grilo-plugins package in Ubuntu:
  Confirmed

Bug description:
  The bliptv website has been closed, the option should be turned off
  from grilo since it leads to have a non working bliptv channel listed
  e.g in the totem UI

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

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

[Touch-packages] [Bug 1415480] Re: [indicators]/OSD provide no visual clue that they modify bluetooth device volumes

[Alejandro J. Cura]

** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: Charles Kerr (charlesk) => Xavi Garcia (xavi-garcia-mena)

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

Title:
  [indicators]/OSD provide no visual clue that they modify bluetooth
  device volumes

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Connect a bluetooth audio device (headset, speakers) to the ubuntu
  phone.

  Play music/enter into a call, so that you have active audio to the
  device.

  Adjust the volume, using the UI or keys on the ubuntu phone.

  The volume of the bluetooth headset changes (good) but the ui contains
  no clue that this is what the phone is doing (less good). The standard
  volume indicator is shown. This can lead to user confusion if they are
  not currently using the paired bluetooth accessory, and have forgotten
  it is paired. On other devices the volume indicator changes to provide
  visual feedback that the bluetooth device volume is being set.

  --

  Desired resolution:

  Please use this icon to replace the volume icon. The icon is bluetooth
  volume which we had design already.

  https://www.dropbox.com/s/a5r3ro1h0917p0a/audio-speakers-bluetooth-
  symbolic.svg?dl=0

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

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

[Touch-packages] [Bug 1484279] Re: [FFe] Mesa 11.0.0

[Jason Gerard DeRose]

Likewise, I've been doing extensive testing with mesa 11 from the
x-staging PPA on Haswell, Broadwell, and Skylake hardware, haven't hit
any issues.

Timo, when do you expect mesa 11 to at least hit wily-proposed? I'll
admit it makes me a bit nervous that mesa 11 isn't in wily proper yet :D

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

Title:
  [FFe] Mesa 11.0.0

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mesa 11.0.0 will be released as follows:

  August 21st 2015 - Feature freeze/Release candidate 1
  August 28th 2015 - Release candidate 2
  September 04th 2015 - Release candidate 3
  September 11th 2015 - Release candidate 4/Mesa 11.0.0

  so even rc1 will miss feature freeze, which is why this bug exists.

  [Changes]
  Wily has 10.6.3 (in proposed as of now), biggest new features compared to it 
are:
  - support for new 'amdgpu' driver (to be merged)
  - support for OpenGL 4.2 in core mesa
  - VMware OpenGL 3.3 support
  .
  .

  [Packaging status]
  - snapshots pushed to debian git
  - packaging updated when necessary
  - builds & works

  [Plan for testing]
  - a snapshot will be uploaded to debian-experimental and 
canonical-x/x-staging ppa, call-for-testing sent once it's available
  - piglit runs on most common hw (intel, radeon, nouveau)

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

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

[Touch-packages] [Bug 1485522] Re: Volume obtained is 100% in multimedia sink for sounds from app

[John McAleely]

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

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

Title:
  Volume obtained is 100% in multimedia sink for sounds from app

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure 100% this is a bug but it is related to
  https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506

  When the "Marron in trouble" games launches a sound the multimedia
  sink it's updated and when reading the volume it's always 100%.

  I'ts not 100% for other applications using the multimedia role, like
  the music app or other games/apps. The volume in that case is in sync
  with the volume that was previously set for it.

  This is the code from the indicator-sound where we get the 100%
  volume.

  var props_variant = yield _pconn.call 
("org.PulseAudio.Ext.StreamRestore1.RestoreEntry",
sink_input_objp, 
"org.freedesktop.DBus.Properties", "Get",
new Variant ("(ss)", 
"org.PulseAudio.Ext.StreamRestore1.RestoreEntry", "Volume"),
null, DBusCallFlags.NONE, -1);
Variant tmp;
props_variant.get ("(v)", out tmp);
uint32 type = 0, volume = 0;
VariantIter iter = tmp.iterator ();
iter.next ("(uu)", , );

  I did a workaround branch in the indicator-sound that reads the volume
  at initilaization for every role and stores any change When the sink
  is updated I read the volume in it that is already stored instead of
  reading the volume from pulse.

  I'm not convinced of that, and would like to know why I get 100%
  volume only for this particular game.

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

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

[Touch-packages] [Bug 1491566] Re: unresponsive shell including power button doesn't blank/unblank display

[Launchpad Bug Tracker]

** Branch linked: lp:~afrantzis/unity-system-
compositor/fix-1491566-deadlock

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

Title:
  unresponsive shell including power button doesn't blank/unblank
  display

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  In Progress

Bug description:
  Note: based on descriptions we spawned bug 1495871 to cover cases
  where the power button still works, this bug will only be for cases
  where the ui input is frozen as well as the power button being
  unresponsive

  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also suspected to be triggering the issue

  Note this has been impossible to reproduce, and in use only happens
  very rarely

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

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

[Touch-packages] [Bug 1484279] Re: [FFe] Mesa 11.0.0

[Timo Aaltonen]

Uploaded, still building on arm

https://launchpad.net/ubuntu/+source/mesa/11.0.0-1ubuntu1

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

Title:
  [FFe] Mesa 11.0.0

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mesa 11.0.0 will be released as follows:

  August 21st 2015 - Feature freeze/Release candidate 1
  August 28th 2015 - Release candidate 2
  September 04th 2015 - Release candidate 3
  September 11th 2015 - Release candidate 4/Mesa 11.0.0

  so even rc1 will miss feature freeze, which is why this bug exists.

  [Changes]
  Wily has 10.6.3 (in proposed as of now), biggest new features compared to it 
are:
  - support for new 'amdgpu' driver (to be merged)
  - support for OpenGL 4.2 in core mesa
  - VMware OpenGL 3.3 support
  .
  .

  [Packaging status]
  - snapshots pushed to debian git
  - packaging updated when necessary
  - builds & works

  [Plan for testing]
  - a snapshot will be uploaded to debian-experimental and 
canonical-x/x-staging ppa, call-for-testing sent once it's available
  - piglit runs on most common hw (intel, radeon, nouveau)

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

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

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

[Michał Sawicz]

I just noticed:

+ export REVISION=--revision=276
[...]
2015/09/22 12:38:36 Flashing version 276 from 
ubuntu-touch/devel-proposed/ubuntu channel and server 
https://system-image.ubuntu.com to device mako

The job seems hardcoded on image 276 for some reason, when we're at 311
already, and that's what I've tested. Trying with image 276 now.

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

Title:
  Automated screen unlock not working on wily images

Status in Ubuntu Test Cases:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The method to automatically unlock the screen prior to running
  autopilot tests is not working on wily images. For example:

  https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-
  mako/417/console

  The CI automation uses this script to setup and perform the unlock:
  
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh

  The failure is seen on images from "ubuntu-touch/devel-
  proposed/ubuntu", in this case image 276.

  Attached is the full console log from that run.

  [The relavent messages are:]
  I: Unlock attempt 1 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 2 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 3 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 4 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 5 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Too many unlock failures, giving up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-test-cases/+bug/1498541/+subscriptions

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

[Touch-packages] [Bug 1441095] Re: novatel: improve probing for Dell branded modems

[Launchpad Bug Tracker]

This bug was fixed in the package modemmanager - 1.4.10-1ubuntu1

---
modemmanager (1.4.10-1ubuntu1) wily; urgency=medium

  * New hardware enablement: Support the new MBIM devices from Dell.
(LP: #1441095)

 -- Bin Li   Mon, 21 Sep 2015 15:01:04 -0400

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

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

Title:
  novatel: improve probing for Dell branded modems

Status in ModemManager:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  New
Status in modemmanager source package in Trusty:
  New
Status in network-manager source package in Trusty:
  New

Bug description:
  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  
  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

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

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

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

[Michał Sawicz]

I just tried following http://ubuntu-test-cases-
touch.readthedocs.org/en/latest/ on mako with devel-proposed:

$> IMAGE_OPT="--bootstrap --developer-mode 
--channel=ubuntu-touch/devel-proposed" ./scripts/provision.sh -w
FLASHING DEVICE
Attempting adb reboot bootloader
=== Device in fastboot ==
WARNING --developer-mode and --password are dangerous as they remove security 
features from your device
2015/09/22 19:00:23 Expecting the device to be in the bootloader... waiting
2015/09/22 19:00:23 Device is |mako|
2015/09/22 19:00:23 Flashing version 311 from ubuntu-touch/devel-proposed 
channel and server https://system-image.ubuntu.com to device mako
6.29 MB / 6.29 MB 
[]
 100.00 % 5.02 MB/s 
52.43 MB / 52.43 MB 
[==]
 100.00 % 9.61 MB/s 
302.71 MB / 302.71 MB 
[===]
 100.00 % 16.90 MB/s 
2015/09/22 19:00:59 Start pushing 
/home/michal/.cache/ubuntuimages/pool/ubuntu-347a20361b2397d6875cbacec432acd51a6771f82038a2ee29afd5a74d5d4938.tar.xz
 to device
2015/09/22 19:00:59 Start pushing 
/home/michal/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2015/09/22 19:00:59 Start pushing 
/home/michal/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2015/09/22 19:00:59 Start pushing 
/home/michal/.cache/ubuntuimages/pool/custom-a4fc258c566f523739147a951e9dd53c03b46d7b0ca768dd4d5dd5a3738a0a4d.tar.xz
 to device
2015/09/22 19:00:59 Start pushing 
/home/michal/.cache/ubuntuimages/pool/device-00f7ea9bb6e1b445460b981872b273c4a49cea282a4478831543ccf9d83d7ab2.tar.xz
 to device
2015/09/22 19:00:59 Start pushing 
/home/michal/.cache/ubuntuimages/ubuntu-touch/devel-proposed/ubuntu/mako/version-311.tar.xz
 to device
2015/09/22 19:00:59 Done pushing 
/home/michal/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2015/09/22 19:00:59 Done pushing 
/home/michal/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2015/09/22 19:00:59 Done pushing 
/home/michal/.cache/ubuntuimages/ubuntu-touch/devel-proposed/ubuntu/mako/version-311.tar.xz
 to device
2015/09/22 19:01:02 Done pushing 
/home/michal/.cache/ubuntuimages/pool/custom-a4fc258c566f523739147a951e9dd53c03b46d7b0ca768dd4d5dd5a3738a0a4d.tar.xz
 to device
2015/09/22 19:01:13 Done pushing 
/home/michal/.cache/ubuntuimages/pool/device-00f7ea9bb6e1b445460b981872b273c4a49cea282a4478831543ccf9d83d7ab2.tar.xz
 to device
2015/09/22 19:01:59 Done pushing 
/home/michal/.cache/ubuntuimages/pool/ubuntu-347a20361b2397d6875cbacec432acd51a6771f82038a2ee29afd5a74d5d4938.tar.xz
 to device
2015/09/22 19:01:59 Created ubuntu_command: 
/home/michal/.cache/ubuntuimages/ubuntu_commands149842736
2015/09/22 19:01:59 Rebooting into recovery to flash
SETTING UP WIFI
UPSTART_SESSION=unix:abstract=/com/ubuntu/upstart-session/32011/1876
ADB_RC=0
Network file is /home/michal/.ubuntu-ci/wifi.conf
Provisioning network on device
Device 'wlan0' successfully activated with 
'332e3b2f-782c-42ae-ab32-a065f7ec3ac5'.

Network setup complete
PING launchpad.net (91.189.89.223) 56(84) bytes of data.
CUSTOMIZING IMAGE



The process was stuck here. The device is in limbo, I believe it tried
to reboot but got stuck after shutting down processes. This is
consistent with the behaviour I saw while using the device - it does not
reboot during normal use either.

Holding power button for a long time got me the charging screen, and
turning the device on again made the process continue.



PING launchpad.net (91.189.89.222) 56(84) bytes of data.
SETTING UP SUDO
[sudo] password for phablet: method return time=1442942215.865996 sender=:1.7 
-> destination=:1.41 serial=30 reply_serial=2
SETTING UP CLICK PACKAGES
UPSTART_SESSION=unix:abstract=/com/ubuntu/upstart-session/32011/1607
ADB_RC=0
Fetching unity8 - into /tmp/tmpiwvUuQ
Downloading unity8 version 8.11+15.10.20150915-0ubuntu1 from 
https://launchpad.net/ubuntu/+archive/primary/+files/unity8_8.11%2B15.10.20150915.orig.tar.gz
Keeping tests from obtained package
Moving /tmp/tmpiwvUuQ/unity8-8.11+15.10.20150915/tests/autopilot/unity8 to 
/tmp/tmpviQ5tL
Fetching ubuntu-ui-toolkit - into /tmp/tmpKAp0g_
Downloading ubuntu-ui-toolkit version 1.3.1627+15.10.20150908-0ubuntu1 from 
https://launchpad.net/ubuntu/+archive/primary/+files/ubuntu-ui-toolkit_1.3.1627%2B15.10.20150908.orig.tar.gz
Keeping tests from obtained package
Moving 

[Touch-packages] [Bug 1148116] Re: not all packages from PPAs have '[origin: ' in Package section

[Brian Murray]

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

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

Title:
  not all packages from PPAs have '[origin: ' in Package section

Status in Daisy:
  Invalid
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  In Progress

Bug description:
  Test Case
  -
  1) Install galicaster package from wiki.teltek.es (or any other random deb 
file will do)
  2) Run the executable
  3) Find the pid of the program and kill it with signal 11
  4) Inspect the .crash file (after it is finished being written) and observe 
the "Package: " key doesn't not contain "[origin: unknown]"

  With the version of apport from -proposed it will contain information
  about it being from an unknown origin.

  Original Description
  
  I was querying for columns in the counters column family starting with 
'Ubuntu ' as I was looking for the counts of bugs reported about packages.  In 
the column family I discovered 'Ubuntu 12.10:indicator-stickynotes' and was 
having trouble finding errors for that package because it is from a PPA.  Given 
that the package is from a PPA it shouldn't be appearing in the counters column 
family at all though.

  From daisy/submit.py:

  package = data.get('Package', '')
  src_package = data.get('SourcePackage', '')
  problem_type = data.get('ProblemType', '')
  third_party = False
  if '[origin:' in package:
  third_party = True

  Then before running update_release_pkg_counter we check for 'if not
  third_party'.  Looking at least some of the oops for indicator-
  stickynotes all of them had '[origin:' in the Package key.

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

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

[Touch-packages] [Bug 1498162] Re: unable to make backup link of `./usr/sbin/uuidd' before installing new version: Operation not permitted

[Phillip Susi]

That is a very strange error.  What if you try this:

sudo -s
cd /usr/sbin
ln uuidd uuidd.bak
rm uuidd.bak


** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  unable to make backup link of `./usr/sbin/uuidd' before installing new
  version: Operation not permitted

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  Upon trying to do an apt-get upgrade I run into this error:

  
  sudo apt-get dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
uuid-runtime
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  2 not fully installed or removed.
  Need to get 0 B/12.3 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 27622 files and directories currently installed.)
  Preparing to unpack .../uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb ...
  Unpacking uuid-runtime (2.20.1-5.1ubuntu20.7) over (2.20.1-5.1ubuntu20.6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb (--unpack):
   unable to make backup link of `./usr/sbin/uuidd' before installing new 
version: Operation not permitted
  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/uuid-runtime_2.20.1-5.1ubuntu20.7_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.7
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Mon Sep 21 19:43:02 2015
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1498202] Re: No policy available for in-app-purchases

[Jamie Strandboge]

** Changed in: ubuntu-personal-security (Ubuntu)
   Status: New => Fix Committed

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: New => 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/1498202

Title:
  No policy available for in-app-purchases

Status in Canonical Click Reviewers tools:
  New
Status in Ubuntu Developer Portal:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Committed
Status in ubuntu-personal-security package in Ubuntu:
  Fix Committed

Bug description:
  There is currently no security policy available for in-app-purchases.
  We will need such a policy, in order to deliver the feature for
  developers to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1498202/+subscriptions

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

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

[Michał Sawicz]

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

** Changed in: ubuntu-test-cases
   Status: New => Invalid

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

Title:
  Automated screen unlock not working on wily images

Status in Ubuntu Test Cases:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The method to automatically unlock the screen prior to running
  autopilot tests is not working on wily images. For example:

  https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-
  mako/417/console

  The CI automation uses this script to setup and perform the unlock:
  
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh

  The failure is seen on images from "ubuntu-touch/devel-
  proposed/ubuntu", in this case image 276.

  Attached is the full console log from that run.

  [The relavent messages are:]
  I: Unlock attempt 1 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 2 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 3 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 4 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 5 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Too many unlock failures, giving up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-test-cases/+bug/1498541/+subscriptions

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

[Touch-packages] [Bug 1498539] Re: FaviconFetcherTests random failures in silo builds

[Olivier Tilloy]

When the test fails, it appears TestHTTPServer::discardClient() is being
called even before TestHTTPServer::readClient() (or rather,
TestHTTPServer::readClient() is never being called), so the socket is
deleted but the server never registers that a request was made.

On the FaviconFetcher side, the request is emitted, but immediately
after I’m seeing the "QIODevice::write: device not open" warning. The
test server receives the incoming connection but it is immediately
disconnected so it discards the client socket.

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

Title:
  FaviconFetcherTests random failures in silo builds

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Since yesterday (2015-09-21), FaviconFetcherTests started failing at
  random in silo builds (not failing all the time, but in about 75% of
  the builds, on amd64 and i386, not on armhf).

  Since it has been happening in several silos, it’s very unlikely that
  it’s a change in webbrowser-app itself that triggered the failure.
  It’s more likely a change somewhere else in the stack that triggered a
  bug that was already there.

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

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

[Touch-packages] [Bug 1463865] Re: Under Unity, HUD in the Firefox Web Browser shows no available menu entries

[madbiologist]

I can't reproduce this in Firefox on a clean install of Vivid with
updates either.

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

Title:
  Under Unity, HUD in the Firefox Web Browser shows no available menu
  entries

Status in Unity:
  Confirmed
Status in hud package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  1. Open the Firefox Web Browser.
  2. Click on a menu, then in any empty place of the Firefox window.
  3. Press the Alt key.
  4. Write any menu command that should be in the Firefox menu.

  RESULT:
  No command is shown as available, as seen in 
.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hud 14.10+14.10.20140924-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 10 16:34:07 2015
  InstallationDate: Installed on 2013-05-21 (750 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: hud
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (46 days ago)

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

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

[Touch-packages] [Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10, nm-applet fills with irrelevant entries.

[Mark Jaroski]

I'm experiencing exactly the same thing as the other report.

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

Title:
  NetworkManager breaks vboxnet* connections since 15.04, worked in
  14.04 and 14.10, nm-applet fills with irrelevant entries.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm-
  applet shows that NetworkManager wants to manage vboxnet0 and
  vboxnet1. These are created by virtualbox which runs some guest OS
  inside a VM. On previous Ubuntu releases, network-manager did not try
  to manage them and there was no problem.

  # Observed behavior

  * nm-applet shows spinning animation for a long time, while it is not 
relevant. Clicking on "disconnect" in the menu unconfigures the interface which 
breaks it.
  * after suspend-resume of the host, vboxnet* lose their correct 
configurations. vboxnet0 (a host-only interface where virtualbox runs a private 
dhcp server) gets a different IP address. Looks like 
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not 
feel like a bug in virtualbox.

  # Expected behavior

  * Just like in 14.04 and 14.10, these interfaces are just ignored by
  network-manager and they just work.

  # Additional information

  * After reading http://superuser.com/questions/9720/disabling-
  networkmanager-for-a-specific-interface tried to add these lines to
  /etc/network/interfaces. Even after restarting network-manager, it has
  no effect.

  iface vboxnet0 inet manual
  iface vboxnet1 inet manual

  So, reverted the change.

  * Tried from https://blogs.gnome.org/dcbw/2015/02/16/networkmanager-
  for-administrators-part-1/ to add in /etc/NetworkManager/conf.d/ a
  file 50-virtualbox.conf containing the following lines. Even after
  restarting network-manager, it is ignored.

  [keyfile]
  unmanaged-devices=vboxnet0,vboxnet1

  * This is not eactly like https://www.virtualbox.org/ticket/13873, I'm not 
using Vagrant.
  * Booting to 14.04 or 14.10 (that have been kept intact on the same machine) 
things just work as expected.
  * /usr/share/doc/network-manager/NEWS.gz states that "'veth' interfaces are 
now unmanaged by default to cooperate better with external tools". Should 
vboxnet* be treated the same ?
  * This seems on the topic but unclear to me: 
https://bugzilla.gnome.org/show_bug.cgi?id=731014

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  Date: Mon Aug 17 13:13:04 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-15 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  IpRoute:
   default via 192.168.47.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev vboxnet0  scope link  metric 1000 
   192.168.47.0/24 dev wlan0  proto kernel  scope link  src 192.168.47.6 
   192.168.56.0/24 dev vboxnet0  proto kernel  scope link  src 192.168.56.102
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1447157] Re: Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

[Mathew Hodson]

** Changed in: console-setup (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

Status in One Hundred Papercuts:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from stock Utopic + updates to Vivid

  On Utopic I had 2 keyboard layouts 'Fr' and 'En', 'Fr' set as default
  After upgrade to Vivid 'En' was enabled but the indicator showed 'Fr'.
  Reselecting 'Fr' set 'Fr' as default and was kept upon reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: console-setup 1.108ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 14:53:03 2015
  InstallationDate: Installed on 2015-04-22 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to vivid on 2015-04-22 (0 days ago)
  modified.conffile..etc.console.setup.compose.VISCII.inc: # Compose sequences 
for VISCII
  mtime.conffile..etc.console.setup.compose.ISO.8859.1.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.13.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.14.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.15.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.2.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.3.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.4.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.7.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.9.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.VISCII.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.remap.inc: 2015-04-22T09:47:24

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

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

[Touch-packages] [Bug 1447157] Re: Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

[Launchpad Bug Tracker]

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

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

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

Title:
  Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

Status in One Hundred Papercuts:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from stock Utopic + updates to Vivid

  On Utopic I had 2 keyboard layouts 'Fr' and 'En', 'Fr' set as default
  After upgrade to Vivid 'En' was enabled but the indicator showed 'Fr'.
  Reselecting 'Fr' set 'Fr' as default and was kept upon reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: console-setup 1.108ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 14:53:03 2015
  InstallationDate: Installed on 2015-04-22 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to vivid on 2015-04-22 (0 days ago)
  modified.conffile..etc.console.setup.compose.VISCII.inc: # Compose sequences 
for VISCII
  mtime.conffile..etc.console.setup.compose.ISO.8859.1.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.13.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.14.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.15.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.2.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.3.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.4.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.7.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.9.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.VISCII.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.remap.inc: 2015-04-22T09:47:24

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

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

[Touch-packages] [Bug 1447157] Re: Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

[Mathew Hodson]

** Project changed: console-setup => ubuntu

** No longer affects: ubuntu

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

Title:
  Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

Status in One Hundred Papercuts:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from stock Utopic + updates to Vivid

  On Utopic I had 2 keyboard layouts 'Fr' and 'En', 'Fr' set as default
  After upgrade to Vivid 'En' was enabled but the indicator showed 'Fr'.
  Reselecting 'Fr' set 'Fr' as default and was kept upon reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: console-setup 1.108ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 14:53:03 2015
  InstallationDate: Installed on 2015-04-22 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to vivid on 2015-04-22 (0 days ago)
  modified.conffile..etc.console.setup.compose.VISCII.inc: # Compose sequences 
for VISCII
  mtime.conffile..etc.console.setup.compose.ISO.8859.1.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.13.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.14.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.15.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.2.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.3.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.4.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.7.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.9.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.VISCII.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.remap.inc: 2015-04-22T09:47:24

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

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

[Touch-packages] [Bug 1498705] [NEW] screen resolution

[ibnu]

Public bug reported:

cannot change screen resolution and stuck in 640x480

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
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 Sep 23 07:38:38 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:0801]
InstallationDate: Installed on 2015-09-23 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
Lsusb:
 Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 
802.11g 54Mbps Network Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: clevo M7x0S
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=e2d9e4a4-8627-4223-ab53-4466b48fd5ba ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/0892
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.asset.tag: 1234567890
dmi.board.name: M7x0S
dmi.board.vendor: clevo
dmi.board.version: Bottom
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SiS
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/08/0892:svnclevo:pnM7x0S:pvrRev.A1:rvnclevo:rnM7x0S:rvrBottom:cvnSiS:ct1:cvrN/A:
dmi.product.name: M7x0S
dmi.product.version: Rev. A1
dmi.sys.vendor: clevo
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.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: Wed Sep 23 07:29:13 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  screen resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  cannot change screen resolution and stuck in 640x480

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  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 Sep 23 07:38:38 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:0801]
  InstallationDate: Installed on 2015-09-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  Lsusb:
   Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B 
Wireless 802.11g 54Mbps Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: clevo M7x0S
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=e2d9e4a4-8627-4223-ab53-4466b48fd5ba ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/0892
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: 1234567890
  dmi.board.name: 

[Touch-packages] [Bug 1447157] Re: Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

[Mathew Hodson]

** Tags added: dist-upgrade

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

Title:
  Keyboard layout reset to en_US after an upgrade from Utopic to Vivid

Status in One Hundred Papercuts:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from stock Utopic + updates to Vivid

  On Utopic I had 2 keyboard layouts 'Fr' and 'En', 'Fr' set as default
  After upgrade to Vivid 'En' was enabled but the indicator showed 'Fr'.
  Reselecting 'Fr' set 'Fr' as default and was kept upon reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: console-setup 1.108ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 14:53:03 2015
  InstallationDate: Installed on 2015-04-22 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to vivid on 2015-04-22 (0 days ago)
  modified.conffile..etc.console.setup.compose.VISCII.inc: # Compose sequences 
for VISCII
  mtime.conffile..etc.console.setup.compose.ISO.8859.1.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.13.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.14.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.15.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.2.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.3.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.4.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.7.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.ISO.8859.9.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.compose.VISCII.inc: 2015-04-22T09:47:24
  mtime.conffile..etc.console.setup.remap.inc: 2015-04-22T09:47:24

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

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

[Touch-packages] [Bug 469005] Re: GDB: Failed to set controlling terminal

[Shawn]

Confirmed on Ubuntu 14.04LTS with Code::Blocks

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

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

Title:
  GDB: Failed to set controlling terminal

Status in Code::Blocks:
  New
Status in gdb:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: netbeans

  Im using Ubuntu 9.10 and Netbeans 6.7 and gdb 7.0, and it keeps
  complaining that gdb couldnt get control of the terminal, it seems tht
  gdb used in ubuntu 9.10 is newer than netbeans can accept. Maybe keep
  a special gdb 6.8 like a dependency for netbeans would solve this
  problem.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Nov  1 14:57:52 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: netbeans 6.7.1-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR.UTF-8
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: netbeans
  Uname: Linux 2.6.31-14-generic i686

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

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

[Touch-packages] [Bug 1484279] Re: [FFe] Mesa 11.0.0

[Robert Hooker]

I have been running it for a week on Ivybridge with no issues in a Unity
environment as well.

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

Title:
  [FFe] Mesa 11.0.0

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Mesa 11.0.0 will be released as follows:

  August 21st 2015 - Feature freeze/Release candidate 1
  August 28th 2015 - Release candidate 2
  September 04th 2015 - Release candidate 3
  September 11th 2015 - Release candidate 4/Mesa 11.0.0

  so even rc1 will miss feature freeze, which is why this bug exists.

  [Changes]
  Wily has 10.6.3 (in proposed as of now), biggest new features compared to it 
are:
  - support for new 'amdgpu' driver (to be merged)
  - support for OpenGL 4.2 in core mesa
  - VMware OpenGL 3.3 support
  .
  .

  [Packaging status]
  - snapshots pushed to debian git
  - packaging updated when necessary
  - builds & works

  [Plan for testing]
  - a snapshot will be uploaded to debian-experimental and 
canonical-x/x-staging ppa, call-for-testing sent once it's available
  - piglit runs on most common hw (intel, radeon, nouveau)

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

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

[Touch-packages] [Bug 469005] Re: GDB: Failed to set controlling terminal

[Shawn]

My apologizes, fixed by updating gdb. warning still persists tho

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

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

Title:
  GDB: Failed to set controlling terminal

Status in Code::Blocks:
  New
Status in gdb:
  New
Status in gdb package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: netbeans

  Im using Ubuntu 9.10 and Netbeans 6.7 and gdb 7.0, and it keeps
  complaining that gdb couldnt get control of the terminal, it seems tht
  gdb used in ubuntu 9.10 is newer than netbeans can accept. Maybe keep
  a special gdb 6.8 like a dependency for netbeans would solve this
  problem.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Nov  1 14:57:52 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: netbeans 6.7.1-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR.UTF-8
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: netbeans
  Uname: Linux 2.6.31-14-generic i686

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

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

[Touch-packages] [Bug 1020075] Re: compiz crashed with SIGSEGV in unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent()

[Mathew Hodson]

** Changed in: unity (Ubuntu Precise)
 Assignee: peterstan (stasnel) => (unassigned)

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

Title:
  compiz crashed with SIGSEGV in
  unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent()

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  [Test Case]
  No clear test case. Ensure that unity does not crash when adjusting screen 
settings or after login.

  [Regression Potential]
  Launchers not put correctly on multiple monitors, edge barriers broken.

  Original description:

  This happened when adjusting my second monitor to be twin view and w/o
  sticky edges.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: compiz-core 1:0.9.8+bzr3249-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
  Uname: Linux 3.5.0-2-generic x86_64
  ApportVersion: 2.2.5-0ubuntu1
  Architecture: amd64
  Date: Mon Jul  2 07:34:15 2012
  Disassembly: => 0x3d77:   Cannot access memory at address 0x3d77
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120629)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x3d77:Cannot access memory at address 0x3d77
   PC (0x3d77) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   
unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent(unity::ui::PointerBarrierWrapper*,
 std::shared_ptr) () from 
/usr/lib/compiz/libunityshell.so
   sigc::internal::slot_call2, void, 
unity::ui::PointerBarrierWrapper*, std::shared_ptr 
>::call_it(sigc::internal::slot_rep*, unity::ui::PointerBarrierWrapper* const&, 
std::shared_ptr const&) () from 
/usr/lib/compiz/libunityshell.so
   unity::ui::PointerBarrierWrapper::EmitCurrentData() () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in 
unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (compiz:1883): GConf-CRITICAL **: gconf_client_add_dir: assertion 
`gconf_valid_key (dirname, NULL)' failed
   gnome-session[1806]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1806]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1806]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   (compiz:2518): GConf-CRITICAL **: gconf_client_add_dir: assertion 
`gconf_valid_key (dirname, NULL)' failed

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

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

[Touch-packages] [Bug 1486522] Re: [SKL] GPU hang with webgl demo

[Mathew Hodson]

** No longer affects: mesa-lts-vivid (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/1486522

Title:
  [SKL] GPU hang with webgl demo

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa-lts-vivid source package in Trusty:
  Fix Released
Status in mesa source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  Mesa 10.5.x suffers from a GPU hang on Skylake HW, bisected fix in
  10.6.x:

  commit 74fd226e34d0cf5e9ff43174ae69b4a66f5de1ab
  Author: Ben Widawsky 
  Date:   Wed Mar 25 16:52:46 2015 -0700

  i965/skl: Don't use the PMA depth stall workaround

  the system freezes soon after, causing loss of data.

  [Test Case]

  * installl chromium version 41.x (webgl disabled on later versions)
  * open https://jbouny.github.io/fft-ocean/
  * grab the ship, rotate quickly
  * should freeze in a few seconds

  [Regression Potential]

  * none, it's a gen9 specific workaround

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

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

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

[jfowlie]

I'm also on Thinkpad T520 with Ubuntu x64 15.04. I tend to use an
external Logitech M705 mouse with a Unifying Receiver -- but the
Logitech might just be a casualty.

This was not a problem until I moved to 15.04 -- I did a bare-metal
install to eliminate system cruft, but retained the home partition.

I'll try to file a report when the problem recurs.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-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: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1492864] Re: nvidia fails on nvidia via nvidia-prime on Ubuntu

[Doug McMahon]

On 2 new 09/22 image installs - 
Ubuntu-Gnome - install nvidia-352, reboot, works on nvidia fine
Ubuntu - install nvidia-352, reboot, no display (black) on unity-greeter, no 
display on log in (blind from greeter

** Summary changed:

- nvidia fails, likely from xserver-core
+ nvidia fails on nvidia via nvidia-prime on Ubuntu

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

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

Title:
  nvidia fails on nvidia via nvidia-prime on Ubuntu

Status in X.Org X server:
  New
Status in lightdm package in Ubuntu:
  New
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen
  Attached logs seem fine

  Downgrading xserver-xorg-core to 1.17.1 & nvidia works fine on optimus
  machine via nvidia-prime

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1492864/+subscriptions

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

[Touch-packages] [Bug 1464365] Re: Resolution is incorrect; screen mostly occluded

[Barry Warsaw]

Today's dist-upgrade, which pulled in new xserver-xorg-core
2:1.17-2-1ubuntu7 and a new unity 7.3.2+15.10.20150921-0ubuntu1 seems to
have restored my full desktop.  Closing as invalid for now.  Will reopen
if the problem recurs.

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

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

Title:
  Resolution is incorrect; screen mostly occluded

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have a 3440x1440 monitor and after today's full dist-upgrade, most
  of the screen real-estate is unusable.  I see a small rectangular
  patch in the lower left corner, and on this patch I can right-button
  to bring up the menu.  While the rest of the screen will display the
  cursor, it is neither the correct background color (nor can it be set
  to the right color; it's just black), and the rest of the screen will
  not respond to mouse clicks at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Jun 11 15:02:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2014-11-22 (201 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141120)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic 
root=UUID=9d28685f-2eae-4d72-8bdc-73fd28aba577 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.12.1+15.10.20150511-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jun 11 14:57:39 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   No surface to present from.
   No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.17.1-0ubuntu4
  xserver.video_driver: vmware

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

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

[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[JohnWashington]

Madbiologist: you write "This bug is about the default resize grab
handle at window borders being too small".

Can I gently suggest you read the title of this problem report?

"Resizing windows by grabbing window borders is difficult"

Window borders.  Nothing about a resize grab handle (which I assume is
the region in the lower right of some desktop's windows, is that so?).
And also read the substance of post #1.  It's about window borders.

I'm sorry, but if you think the solution to a request for set-ability of
window borders is to provide a feature in one corner of the window, I
feel you've misunderstood.  No doubt that feature is indeed a useful fix
for some bugs and feature requests, but not, I believe, this one.

So I would request this bug's status be changed.  Fixed is not correct.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 1498539] Re: FaviconFetcherTests random failures in silo builds

[Olivier Tilloy]

Mirv suggested that https://launchpadlibrarian.net/218473113/qtbase-
opensource-src_5.4.1%2Bdfsg-2ubuntu8_5.4.1%2Bdfsg-2ubuntu9.diff.gz could
very well be when the test started failing, and it looks plausible. Not
sure what conclusions to draw from the diff though. Is the issue in the
way the test server handles incoming connections, or is it an actual bug
in QNAM?

In doubt, I’ll mark qtbase-opensource-src also affected, for further
investigation.

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

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

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

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

Title:
  FaviconFetcherTests random failures in silo builds

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Since yesterday (2015-09-21), FaviconFetcherTests started failing at
  random in silo builds (not failing all the time, but in about 75% of
  the builds, on amd64 and i386, not on armhf).

  Since it has been happening in several silos, it’s very unlikely that
  it’s a change in webbrowser-app itself that triggered the failure.
  It’s more likely a change somewhere else in the stack that triggered a
  bug that was already there.

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

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

[Touch-packages] [Bug 1498202] Re: No policy available for in-app-purchases

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor-easyprof-ubuntu - 15.10.11

---
apparmor-easyprof-ubuntu (15.10.11) wily; urgency=medium

  * adjust autopkgtests for in-app-purchases

apparmor-easyprof-ubuntu (15.10.10) wily; urgency=medium

  [ Rodney Dawes ]
  * Add in-app-purchases policy group for IAP support (LP: #1498202)

apparmor-easyprof-ubuntu (15.10.9) wily; urgency=medium

  [ Alberto Mardegan ]
  * ubuntu/15.10/accounts: add back v1 API

 -- Jamie Strandboge   Mon, 21 Sep 2015 17:02:52 -0500

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

Title:
  No policy available for in-app-purchases

Status in Canonical Click Reviewers tools:
  New
Status in Ubuntu Developer Portal:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-personal-security package in Ubuntu:
  Fix Committed

Bug description:
  There is currently no security policy available for in-app-purchases.
  We will need such a policy, in order to deliver the feature for
  developers to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1498202/+subscriptions

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

[Touch-packages] [Bug 1498676] [NEW] Asus Xonar U7 S/PDIF output not recognized by pulseaudio

[aoandr]

Public bug reported:

duplicate of Bug #1498129

I was not able to make ubuntu-bug to upload the information to the
original bug, sorry. It would not allow me to select alsa-driver
package, because "it is not installed".

I applied the patch suggested by Raymond:
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/usb?id=a358a0ef861dae6f8330fb034aaa43adae71ebc1

Got rid of "cannot get ctl value:" error. Now alsamixer starts without
ignore_ctl_error=1 option for snd-usb-audio module.

Thank you, Raymond!

Still no luck with Pulseaudio: it does not recognize S/PDIF interface.
Even more: it shows "S/PDIF" interface, which is actually an alias to
the Analog Stereo output.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
Uname: Linux 3.13.0-63-lowlatency i686
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aoand  4448 F pulseaudio
 /dev/snd/controlC1:  aoand  4448 F pulseaudio
CurrentDesktop: Unity
Date: Wed Sep 23 01:01:27 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-02-20 (1675 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to trusty on 2014-05-19 (491 days ago)
dmi.bios.date: 11/29/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 7WET71WW (3.21 )
dmi.board.name: 7448CTO
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:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7448CTO
dmi.product.version: ThinkPad X200 Tablet
dmi.sys.vendor: LENOVO
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2015-09-23T00:33:57.990672

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


** Tags: apport-bug i386 trusty

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

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  duplicate of Bug #1498129

  I was not able to make ubuntu-bug to upload the information to the
  original bug, sorry. It would not allow me to select alsa-driver
  package, because "it is not installed".

  I applied the patch suggested by Raymond:
  
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/usb?id=a358a0ef861dae6f8330fb034aaa43adae71ebc1

  Got rid of "cannot get ctl value:" error. Now alsamixer starts without
  ignore_ctl_error=1 option for snd-usb-audio module.

  Thank you, Raymond!

  Still no luck with Pulseaudio: it does not recognize S/PDIF interface.
  Even more: it shows "S/PDIF" interface, which is actually an alias to
  the Analog Stereo output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aoand  4448 F pulseaudio
   /dev/snd/controlC1:  aoand  4448 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 01:01:27 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1675 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (491 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  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:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2015-09-23T00:33:57.990672

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

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

[Touch-packages] [Bug 1495467] Re: Memory leak on previews

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/unity8

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

Title:
  Memory leak on previews

Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Preview stack objects leak memory because of the custom
  QObject::event() handlers that shell plugin uses. These event handlers
  need to call base QOBject::event for unhandled events, and unity8
  needs to make sure it keeps the reference to PreviewStack object (not
  just preview model) for as long as needed till the preview is closed.

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

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

[Touch-packages] [Bug 1498541] Re: Automated screen unlock not working on wily images

[Francis Ginther]

The jenkins job was indeed hardcoded to use image 276 due to an
unbootable image at 277. We then failed to remove this once the image
was fixed. Image 311 is working and unlock is successful:

https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-
mako/421/consoleFull

[log snippet]
INFO:reboot-and-wait:Network is active
I: Unlock attempt 1 failed, script output: 'Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.canonical.UnityGreeter was not provided by any .service files
'
I: Unlock passed


This is now working (transient failed attempts are expected). I think we can 
close this.

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

Title:
  Automated screen unlock not working on wily images

Status in Ubuntu Test Cases:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The method to automatically unlock the screen prior to running
  autopilot tests is not working on wily images. For example:

  https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-
  mako/417/console

  The CI automation uses this script to setup and perform the unlock:
  
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh

  The failure is seen on images from "ubuntu-touch/devel-
  proposed/ubuntu", in this case image 276.

  Attached is the full console log from that run.

  [The relavent messages are:]
  I: Unlock attempt 1 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 2 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 3 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 4 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Unlock attempt 5 failed, script output: 'initctl: unable to determine 
sessions
  initctl: unable to determine sessions
  Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY
  '
  I: Too many unlock failures, giving up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-test-cases/+bug/1498541/+subscriptions

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

[Touch-packages] [Bug 1103881] Re: cloud-final is never executed if upstart or any dependency is upgraded during initialization

[Matt Rae]

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

With juju 1.24 this bug appears to be hit on state servers started with
'juju ensure-availability' during cloud-init upgrade, unless enable-os-
refresh-update and enable-os-upgrade are set to false.

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

Title:
  cloud-final is never executed if upstart or any dependency is upgraded
  during initialization

Status in cloud-init package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  During a cloud image initialization, the service cloud-final is never
  executed if the cloud-config script contains an "upgrade" directive
  and upstart is part of the upgraded packages:

  TESTCASE:
  1. Download a cloud image from http://cloud-images.ubuntu.com/raring/ with an 
outdated version of upstart (e.g 2013.01.23 - I saved this image, if you need 
it and it is not available from the mirror just ask)
  2. Prepare a cloud-config script with the directives (example cloud-config 
script used by lp:auto-package-testing attached):

  apt_update: true
  apt_upgrade: true

  3. Initialize the cloud image with this cloud-config script

  EXPECTED RESULT:
  Installation finish

  ACTUAL RESULT
  The service cloud-final is never executed and the flag boot-finished is not 
present.

  cloud-init logs of a failed installation attached.

  Related bugs:
   * bug 1080841: should reload configuration if an upstart job is added
   * bug 1124384: reload-configuration can confuse upstart
   * bug 1163669: cloud-init fails to install juju agent after bootstrap 

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cloud-init (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Thu Jan 24 09:08:19 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: Upgraded to raring on 2012-01-31 (358 days ago)

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

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

[Touch-packages] [Bug 1230352] Re: Scope results not updated when scope invalidates them

[Fabio Marconi]

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

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

Title:
  Scope results not updated when scope invalidates them

Status in Unity:
  Fix Released
Status in Unity 8:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Scope API provide a results_invalidated() method, which is supposed to
  signal the dash that the result set is no longer valid and the scope
  should be re-queried. But as of this moment Unity doesn't react to
  this signal and therefore if you for example download new music to the
  device and mediascanner plugin picks it up, Dash doesn't get updated.
  This should be fixed.

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

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

[Touch-packages] [Bug 1463865] Re: Under Unity, HUD in the Firefox Web Browser shows no available menu entries

[madbiologist]

I have menus set to show in the window's title bar.  Do you?

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

Title:
  Under Unity, HUD in the Firefox Web Browser shows no available menu
  entries

Status in Unity:
  Confirmed
Status in hud package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  1. Open the Firefox Web Browser.
  2. Click on a menu, then in any empty place of the Firefox window.
  3. Press the Alt key.
  4. Write any menu command that should be in the Firefox menu.

  RESULT:
  No command is shown as available, as seen in 
.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hud 14.10+14.10.20140924-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 10 16:34:07 2015
  InstallationDate: Installed on 2013-05-21 (750 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: hud
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (46 days ago)

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

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

[Touch-packages] [Bug 1498202] Re: No policy available for in-app-purchases

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-personal-security - 15.10.4

---
ubuntu-personal-security (15.10.4) wily; urgency=medium

  [ Rodney Dawes ]
  * Add in-app-purchases policy group for IAP support (LP: #1498202)

 -- Jamie Strandboge   Mon, 21 Sep 2015 17:19:06 -0500

** Changed in: ubuntu-personal-security (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 apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1498202

Title:
  No policy available for in-app-purchases

Status in Canonical Click Reviewers tools:
  New
Status in Ubuntu Developer Portal:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-personal-security package in Ubuntu:
  Fix Released

Bug description:
  There is currently no security policy available for in-app-purchases.
  We will need such a policy, in order to deliver the feature for
  developers to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1498202/+subscriptions

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

[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[madbiologist]

I am sorry for being unclear.  I was referring to the entire edges of
the window, not just the lower right corner.  I didn't use the word
"border" because now the area available for grabbing extends outside of
the admittedly narrow border.  All window borders are now surrounded by
an invisible/transparent grabbable area, which is larger than it was
when this bug was reported.  I was hoping to demonstrate this with a
screenshot but the mouse pointer does not show in screenshots.  I agree
that it would be even better if the size of this area was user-
configurable, but that will probably receive more attention if filed as
a new bug.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 1494796] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/smartscopesproxy:smartscopesproxy: src/lib_json/json_value.cpp:1177: const Json::Value& Json::Value::operator[](const char*

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/unity-scopes-api

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-
  scopes/smartscopesproxy:smartscopesproxy:
  src/lib_json/json_value.cpp:1177: const Json::Value&
  Json::Value::operator[](const char*) const: Assertion `type_ ==
  nullValue || type_ == objectValue' failed.

Status in Canonical System Image:
  New
Status in unity-scopes-api package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scopes-api.  This problem was most recently seen with
  version 0.6.19+15.04.20150724.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/82f3407ea224db29041027eca65d23d17eb2027e
  contains more details.

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

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

[Touch-packages] [Bug 1498676] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio

[aoandr]

** Description changed:

- Applied the patch
+ duplicate of Bug #1498129
+ 
+ I was not able to make ubuntu-bug to upload the information to the
+ original bug, sorry. It would not allow me to select alsa-driver
+ package, because "it is not installed".
+ 
+ I applied the patch suggested by Raymond:
  
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/usb?id=a358a0ef861dae6f8330fb034aaa43adae71ebc1
  
  Got rid of "cannot get ctl value:" error. Now alsamixer starts without
  ignore_ctl_error=1 option for snd-usb-audio module.
  
- Still no luck: Pulseaudio does not recognize S/PDIF interface. Even
- worse: it shows "S/PDIF" interface, which is actually an alias to the
- Analog Stereo output.
+ Thank you, Raymond!
+ 
+ Still no luck with Pulseaudio: it does not recognize S/PDIF interface.
+ Even more: it shows "S/PDIF" interface, which is actually an alias to
+ the Analog Stereo output.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  aoand  4448 F pulseaudio
-  /dev/snd/controlC1:  aoand  4448 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aoand  4448 F pulseaudio
+  /dev/snd/controlC1:  aoand  4448 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 01:01:27 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1675 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (491 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  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:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2015-09-23T00:33:57.990672

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

Title:
  Asus Xonar U7 S/PDIF output not recognized by pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  duplicate of Bug #1498129

  I was not able to make ubuntu-bug to upload the information to the
  original bug, sorry. It would not allow me to select alsa-driver
  package, because "it is not installed".

  I applied the patch suggested by Raymond:
  
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/usb?id=a358a0ef861dae6f8330fb034aaa43adae71ebc1

  Got rid of "cannot get ctl value:" error. Now alsamixer starts without
  ignore_ctl_error=1 option for snd-usb-audio module.

  Thank you, Raymond!

  Still no luck with Pulseaudio: it does not recognize S/PDIF interface.
  Even more: it shows "S/PDIF" interface, which is actually an alias to
  the Analog Stereo output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aoand  4448 F pulseaudio
   /dev/snd/controlC1:  aoand  4448 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 01:01:27 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-02-20 (1675 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-05-19 (491 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7448CTO
  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:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2015-09-23T00:33:57.990672

To manage 

[Touch-packages] [Bug 1308133] Re: Mir cursor is missing/invisible despite definitely being set by the client

[Daniel van Vugt]

Found a workaround that solves the issue in Xmir: Just ask Mir to set
the cursor three times. Then it will finally appear on screen.

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

Title:
  Mir cursor is missing/invisible despite definitely being set by the
  client

Status in Mir:
  Confirmed
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Triaged

Bug description:
  No cursor shown when booted to unity8 Mir on Samsung NP-300V5Z no cursor 
shown neither from touch pad nor usb wireless mouse. It's really hard to 
navigate when no cursor is shown, but it works apparently.
  All packages updated as of today (Apr-15)

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

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

[Touch-packages] [Bug 1498740] [NEW] /usr/bin/mediascanner-service-2.0:11:gst_audio_decoder_push_buffers:gst_audio_decoder_chain_forward:gst_audio_decoder_chain:gst_pad_chain_data_unchecked:gst_pad_pu

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: rtm-14.09 trusty utopic vivid wily

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

Title:
  /usr/bin/mediascanner-
  
service-2.0:11:gst_audio_decoder_push_buffers:gst_audio_decoder_chain_forward:gst_audio_decoder_chain:gst_pad_chain_data_unchecked:gst_pad_push_data

Status in mediascanner2 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1496743] Re: /usr/bin/ld.gold: --push-state: unknown option

[Olivier Tilloy]

This also affects building oxide-qt on wily (see e.g.
https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+build/7930449).

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

Title:
  /usr/bin/ld.gold: --push-state: unknown option

Status in gcc-5 package in Ubuntu:
  Triaged
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  With gcc 5.2.1-17ubuntu4, we're seeing
  https://launchpadlibrarian.net/218108553/buildlog_ubuntu-wily-amd64
  .ubuntu-ui-
  toolkit_1.3.1639%2B15.10.20150916.2-0ubuntu1_BUILDING.txt.gz

  TJ- on #ubuntu-devel suggested:
  < TJ-> Mirv: bzoltan: the issue could be in qtbase-opensource-src-5.4.2+dfsg 
(qmake) which does "mkspecs/common/gcc-base-unix.conf:19:QMAKE_LFLAGS_USE_GOLD  
 = -fuse-ld=gold" irrespective of libraries being linked.

  Ideas for a proper fix welcome.

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

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