date:20160729

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

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

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

Title:
  unity8-dash + maliit-server crashes on arale (2016-04)

Status in Canonical System Image:
  Incomplete
Status in ubuntu-keyboard package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  I'm seeing unity8-dash and maliit-server crashes lately on arale
  during power tests.  They usually seem to happen together, and might
  be a recurrence of an earlier issue at the end of 2015.

  I've collected a total of 19 unity8-dash crash dumps so far, and 14
  for maliit-server, starting on 2016-04-04 and continuing to today.
  Prior to 2016-04, I saw similar paired crashes in January, December,
  and November, but those were mostly on krillin.

  Here are some examples:

  https://errors.ubuntu.com/oops/254319ac-1cd2-11e6-a5f5-fa163e30221b 
(unity8-dash)
  https://errors.ubuntu.com/oops/1f7710b4-1cd2-11e6-998a-fa163e192766 (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-18_02:04:57-arale-328-power_usage_video/3/

  https://errors.ubuntu.com/oops/8f791fee-1cfd-11e6-9e43-fa163eec78fa 
(unity8-dash)
  https://errors.ubuntu.com/oops/8a7c5786-1cfd-11e6-a175-fa163e8d4bab (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-18_07:14:53-arale-329-power_usage_video/3/

  https://errors.ubuntu.com/oops/9ef5c9f8-22ee-11e6-a2a7-fa163e839e11 
(unity8-dash)
  https://errors.ubuntu.com/oops/9d30a840-22ee-11e6-9c70-fa163e171d9b (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-25_20:52:43-arale-333-power_usage_video/2/

  https://errors.ubuntu.com/oops/fa1d1592-234e-11e6-85ab-fa163e8d4bab 
(unity8-dash)
  https://errors.ubuntu.com/oops/f870ebc4-234e-11e6-9005-fa163eec78fa (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-26_08:22:28-arale-336-power_usage_video/2/

  The two usually coincide, but not always.  Here is a diff between the test 
runs where each one occurred:
  --- maliit.crashes
  +++ unity8-dash.crashes
   2016-04-04_21:11:32-arale-28-power_usage_video/2/
  +2016-04-09_20:49:41-arale-29-power_usage_display_on/12/
  +2016-04-09_20:49:41-arale-29-power_usage_display_on/9/
  +2016-04-10_04:19:02-arale-29-power_usage_video/6/
   2016-04-11_09:06:44-arale-30-power_usage_video/4/
   2016-04-20_22:56:38-arale-308-power_usage_video/5/
  -2016-04-25_17:11:09-arale-31-power_usage_display_on/8/
  +2016-04-26_01:41:35-arale-31-power_usage_video/4/
   2016-05-04_22:58:30-arale-315-power_usage_music/2/
   2016-05-05_05:05:20-arale-316-power_usage_video/2/
  +2016-05-06_22:49:51-arale-32-power_usage_display_on/12/
  +2016-05-12_21:58:22-arale-319-power_usage_bt_on_wifi_disconnected/1/
   2016-05-13_08:09:00-arale-321-power_usage_video/7/
   2016-05-13_14:50:11-arale-321-power_usage_bt_on_wifi_disconnected/1/
   2016-05-14_01:49:40-arale-324-power_usage_idle/1/

  I'm assuming these have a common cause, even if it doesn't always kill
  both processes.

  It may also be related to bug 1586276 and bug 1586255, which started
  happening at the same time.

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

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

[Touch-packages] [Bug 1586272] Re: unity8-dash + maliit-server crashes on arale (2016-04)

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  unity8-dash + maliit-server crashes on arale (2016-04)

Status in Canonical System Image:
  Incomplete
Status in ubuntu-keyboard package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  I'm seeing unity8-dash and maliit-server crashes lately on arale
  during power tests.  They usually seem to happen together, and might
  be a recurrence of an earlier issue at the end of 2015.

  I've collected a total of 19 unity8-dash crash dumps so far, and 14
  for maliit-server, starting on 2016-04-04 and continuing to today.
  Prior to 2016-04, I saw similar paired crashes in January, December,
  and November, but those were mostly on krillin.

  Here are some examples:

  https://errors.ubuntu.com/oops/254319ac-1cd2-11e6-a5f5-fa163e30221b 
(unity8-dash)
  https://errors.ubuntu.com/oops/1f7710b4-1cd2-11e6-998a-fa163e192766 (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-18_02:04:57-arale-328-power_usage_video/3/

  https://errors.ubuntu.com/oops/8f791fee-1cfd-11e6-9e43-fa163eec78fa 
(unity8-dash)
  https://errors.ubuntu.com/oops/8a7c5786-1cfd-11e6-a175-fa163e8d4bab (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-18_07:14:53-arale-329-power_usage_video/3/

  https://errors.ubuntu.com/oops/9ef5c9f8-22ee-11e6-a2a7-fa163e839e11 
(unity8-dash)
  https://errors.ubuntu.com/oops/9d30a840-22ee-11e6-9c70-fa163e171d9b (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-25_20:52:43-arale-333-power_usage_video/2/

  https://errors.ubuntu.com/oops/fa1d1592-234e-11e6-85ab-fa163e8d4bab 
(unity8-dash)
  https://errors.ubuntu.com/oops/f870ebc4-234e-11e6-9005-fa163eec78fa (maliit)
  
http://people.canonical.com/~platform-qa/power-results/2016-05-26_08:22:28-arale-336-power_usage_video/2/

  The two usually coincide, but not always.  Here is a diff between the test 
runs where each one occurred:
  --- maliit.crashes
  +++ unity8-dash.crashes
   2016-04-04_21:11:32-arale-28-power_usage_video/2/
  +2016-04-09_20:49:41-arale-29-power_usage_display_on/12/
  +2016-04-09_20:49:41-arale-29-power_usage_display_on/9/
  +2016-04-10_04:19:02-arale-29-power_usage_video/6/
   2016-04-11_09:06:44-arale-30-power_usage_video/4/
   2016-04-20_22:56:38-arale-308-power_usage_video/5/
  -2016-04-25_17:11:09-arale-31-power_usage_display_on/8/
  +2016-04-26_01:41:35-arale-31-power_usage_video/4/
   2016-05-04_22:58:30-arale-315-power_usage_music/2/
   2016-05-05_05:05:20-arale-316-power_usage_video/2/
  +2016-05-06_22:49:51-arale-32-power_usage_display_on/12/
  +2016-05-12_21:58:22-arale-319-power_usage_bt_on_wifi_disconnected/1/
   2016-05-13_08:09:00-arale-321-power_usage_video/7/
   2016-05-13_14:50:11-arale-321-power_usage_bt_on_wifi_disconnected/1/
   2016-05-14_01:49:40-arale-324-power_usage_idle/1/

  I'm assuming these have a common cause, even if it doesn't always kill
  both processes.

  It may also be related to bug 1586276 and bug 1586255, which started
  happening at the same time.

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

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

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

2016-07-29 Thread Benjamin Morgan

Just confirmed that Gyula's notes work for me too. Post #'s 25 & 27 work
great to get my Microsoft Arc BTLE Mouse paired. Flawless connect,
disconnect, and general usage. Thanks guys!

What I did:
- editing /etc/bluetooth/main.conf as it is said in #25
- editing /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules as it is

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1577168] Re: Browser hangs Ubuntu 16.04

2016-07-29 Thread John Tollendal

I have notice this today.  I am using ubuntu 14.04 (32bits)

3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:32 UTC 2016 i686 i686
i686 GNU/Linux

The webbrowser-app is the main affected with this problem.

Console (DISPLAY=:0) freezes and using a ssh to my desktop from a
different system I can logging and notice that:

1) console user is gone!

2) sudo update-alternatives --config x-www-browser show:

  SelectionPath   Priority   Status

* 0/usr/bin/epiphany-browser   85auto mode
  1/usr/bin/epiphany-browser   85manual mode
  2/usr/bin/firefox40manual mode

dpkg -l webbrowser-app lightdm
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
ii  webbrowser-app 0.23+14.04.2 i386 Ubuntu web browser
ii  lightdm1.10.6-0ubun i386 Display Manager

3) lightdm does not restart

4) any app that depends on webbrowser-app will crash the system

5) I can only recover the system console by ssh from other device and
using a sudo reboot

This problem might suggest very important vulnerability of ubuntu

Could be related to new updates. Please help!

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

Title:
  Browser hangs Ubuntu 16.04

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  When I activate Browser or click on Amazon button (which activates Browser), 
Ubuntu 16.04 hangs. This occurrence should not happen.
  An exception to this problem is that the mouse pointer is movable initially. 
In the extreme case, the mouse pointer hangs also. 

  This problem does not occur when activating Firefox or Chromium.
  Occurs in a freshly installed Ubuntu 16.04 system.
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  N: Unable to locate package pkgname

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

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

[Touch-packages] [Bug 1584393] Re: systemctl restart networking hangs reloading ssh.service

2016-07-29 Thread Bug Watch Updater

** Changed in: openssh (Debian)
   Status: New => Fix Released

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

Title:
  systemctl restart networking hangs reloading ssh.service

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Xenial:
  Confirmed
Status in openssh package in Debian:
  Fix Released

Bug description:
  Issues "systemctl restart networking" never exits. It hangs during a
  call to "systemctl reload ssh.service":

  ● networking.service - Raise network interfaces
 Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
 Active: activating (start) since Sat 2016-05-21 21:41:58 UTC; 18s ago
   Docs: man:interfaces(5)
Process: 1288 ExecStop=/sbin/ifdown -a --read-environment (code=exited, 
status=0/SUCCESS)
Process: 1376 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] 
&& [ -n "$(ifquery --read-environment --list --exclude=lo)" ] &
   Main PID: 1383 (ifup)
  Tasks: 7 (limit: 512)
 Memory: 1.8M
CPU: 111ms
 CGroup: /system.slice/networking.service
 ├─1383 /sbin/ifup -a --read-environment
 ├─1479 /sbin/dhclient -1 -v -pf /run/dhclient.enp0s3.pid -lf 
/var/lib/dhcp/dhclient.enp0s3.leases -I -df /var/lib/dhcp/dhclient6
 ├─1480 /bin/sh -c /bin/run-parts --exit-on-error 
/etc/network/if-up.d
 ├─1481 /bin/run-parts --exit-on-error /etc/network/if-up.d
 ├─1504 /bin/sh /etc/network/if-up.d/openssh-server
 ├─1507 /bin/sh /usr/sbin/invoke-rc.d ssh reload
 └─1527 systemctl reload ssh.service

  Then issuing the same command from another terminal causes the first
  to exit successfully (the second also exists successfully).

  On the official vagrant image, I get this problem independently of
  whether the command is issued through and ssh session. I've gotten the
  same behavior on the official xenial AMIs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May 21 21:35:08 2016
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state

2016-07-29 Thread wombat

Hi, 
I have had the same issue after installing Ubuntu 16.04. I have tried the fix 
from comment #31 and it didn't work for me. However, as soon as I plug my 
headphone into the front panel headphone plug, the annoying issue disappeared, 
and the popping up comes back if headphone is unplugged.
Now I unplugged my rear speaker's plug, and no popping up at all. 
Additionally, when I adjust the "Sound Setting", I was unable to hear the Test 
Sound if I try to play sound from Digital Output (S/PDIF). Not sure if this is 
relevant. 
Ubuntu gurus, perhaps the issue links to the audio plug scan or config?
Thanks in advance.

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

Title:
  Volume Slider Jumps, due to rapidly changing hardware jack sense state

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  In Oneiric Release,  The volume slider randomly jump down a notch or
  two for fraction of  a second, even when there is no audio playing on
  the system.  If mute is selected, the menu will quickly flip out of
  mute mode and back again.  This change actually affects the audio
  output, resulting in pops correlated with the volume changes.

  nVidia GF106 Audio Controller
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfrorie9959 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1462522c,00100302'
 Controls  : 35
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Package: pulseaudio 1:1.0-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD45 (MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 5.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: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
  dmi.product.name: MS-7522
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-07-29 Thread Richard Laager

chiluk is looking to work on this for upstream. I might jump in too.
https://github.com/zfsonlinux/zfs/issues/4680

** Bug watch added: Github Issue Tracker for ZFS #4680
   https://github.com/zfsonlinux/zfs/issues/4680

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

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

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

[Touch-packages] [Bug 1576576] Re: [needs-packaging] Update to 3.20 needs work and coordination

2016-07-29 Thread Brian Murray

*** This is an automated message ***

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

** Summary changed:

- Update to 3.20 needs work and coordination
+ [needs-packaging] Update to 3.20 needs work and coordination

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [needs-packaging] Update to 3.20 needs work and coordination

Status in Mozilla Firefox:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  The current upstream stable/Debian version is 3.20 but that includes quite 
some changes in the css handling which means we are going to need to update/fix 
the unity themes and make sure you main application look fine before landing.
  The transition needs to be prepared in a staging ppa before being considered, 
help is welcome since it's likely the desktop team is not going to have lot of 
cycles to work on that.

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

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

[Touch-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

2016-07-29 Thread Samuel Walladge

Also, probably related, I just discovered through an irc conversation on
#ubuntu-touch (thanks Mister_Q) that using the bq flash tool (which I did to 
fix an unbootable
system) and selecting 'format and download' (which I also did), would have
deleted the imei partition.

Quite possible, seeing as the serial number displayed in the 'about' section
shows "0123456789ABCDEF".

Apparently it could also cause my other problem of the tablet not recognizing
or outputting to HDMI monitors via a micro-hdmi to hdmi cable.

Although... that doesn't explain why the wifi problem has been seen before, or
why there's plenty of other reports of the M10 not outputting to displays (at
least not reliably). - see
http://askubuntu.com/questions/762148/bq-m10-ubuntu-touch-micro-hdmi-not-outputting-to-tv
for example.

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

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

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

[Touch-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-07-29 Thread Steve Langasek

No reason to fix this via sysvinit, which should be considered
deprecated at this point.

** Changed in: sysvinit (Ubuntu)
   Status: New => Won't Fix

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

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

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

[Touch-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

2016-07-29 Thread Samuel Walladge

- syslog is attached
- wifi access point is set up as following: 2.4Ghz, channel 11, 20MHz width, AU
region, WPA2 PSK security, wps disabled.

** Attachment added: "syslog"

https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+attachment/4709989/+files/syslog

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

Title:
wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
Incomplete
Status in network-manager package in Ubuntu:
New

Bug description:
I have a M10, on ubuntu touch OTA-12 (and same issue previously on
OTA-11).

The issue is that it doesn't remember wifi networks properly. To
explain:

1. turn on tablet
2. select my wifi network from the list
3. enter password and click connect
4. reboot device
5. select my wifi network from the list
6. enter password and click connect
.
.
.
30. go to wifi settings -> previous networks
31. view long list that looks like:

MyWifinetwork1
MyWifinetwork2
MyWifinetwork3
MyWifinetwork4
...

What it should do (and did some time ago), is see that MyWifinetwork
was saved in previous networks and automatically connect using the
saved password/settings.

So, I'm wondering is this a bug, something badly configured in my wifi
network (although other devices remember it fine), or something else?

Thanks.

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

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

[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

2016-07-29 Thread Christian Boltz

Patch commited to bzr trunk r3498, 2.10 branch r3341 and 2.9 branch
r3016.

Updating the Ubuntu update package is ENOTMYJOB ;-)

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

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

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

[Touch-packages] [Bug 1607845] Re: List of versioned kernels is not right for Ubuntu

2016-07-29 Thread David Kalnischkies

btw: "apt-cache pkgnames" should have better/quicker result than
searching.

Don't know what that goldfish is nor am I particular interested in
cloud, but I guess they could be added if there is need/interest. Its
not like there is any real cost attached to it and false positives are
pretty unlikely with the kernel versions attached… in the case of
goldfish it seems to be unneeded through as they have "normally" named
images/headers packages, too, which depend on the strange ones, so the
autoremover wouldn't kick in anyhow for those.

kfreebsd, gnumach (= hurd) do not share the same version, they do share
the kernel postinst scripts which apt is using here through, so even
through they use entirely different version schemes, its still a version
we can work with. Excluding specific items depending on the architecture
we built apt for would be possible, but not really worth the
implementation effort I presume.

And yes, -modules/-kernel is for out-of-tree modules as created by
module-assistant (from -source packages), but I think dkms can built
packages, too, and its the naming scheme which tends to be used for
packages for modules which happen to be distributable as binary builds…
(not that there would be many).

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

[Touch-packages] [Bug 1524053] Re: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line.

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

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

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

Title:
  Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu
  Session than a line.

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I've tried both Ubuntu Minimal+XFCE & Xubuntu 16.04
  This gravely affect of XFCE, Openbox session on Ubuntu 16.04.
  However this doesn't happen on Xubuntu 16.04 Session at all it shows 
dependencies list normally
  But on XFCE, Openbox session it only shows a line.

  We need more tester to  confirm other session as well such as:
  Unity, Ubuntu, KDE, Kubuntu, lxde, lxde, Lubuntu, Edubuntu, Mythbuntu,
  To confirm if it's only affect on non-Ubuntu flavor Sessions.
  or are they affect to all Sessions Except Xubuntu Session?

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

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

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

2016-07-29 Thread Michał Sawicz

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

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

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

** Changed in: qtubuntu (Ubuntu)
   Importance: Medium => High

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

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

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

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

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

2016-07-29 Thread Sergi Quiles Pérez

I have done some tests (spanish layout, catalan language):

- In bq Aquaris E4.5 (OTA 12):
 Accented dead characters doesn't work in any app nor webapp.

- In bq Aquaris M10 (OTA 12):
 Accented dead characters doesn't work in any app nor webapp.
 Accented dead characters works in all Xapps.

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

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (OTA-12)

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

2016-07-29 Thread Sergi Quiles Pérez

I have done some tests (spanish layout, catalan language):

- In bq Aquaris E4.5 (OTA 12):
 ALTGR works in most of the native apps except Navigator and Terminal (for 
me).
 ALTGR doesn't work in webapps.

- In bq Aquaris M10 (OTA 12):
 ALTGR works in most of the native apps except Navigator and Terminal (for 
me).
 ALTGR doesn't work in webapps.
 ALTGR works in all Xapps. In Firefox it works in the address bar as well 
in any field inside a web page.

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1607966] [NEW] X doesn't start with r128 driver with PM 3, 1 PPC ATI Rage

Public bug reported:

I was working on bug #1541082 which was reporting "blotchy" graphics
images on my PowerMac3,1 with Rage ATI Pro 128 card . . . and got the
suggestion to try to add the "r128" driver, which I did.  After that the
display went black.  After fiddling around with it, I removed the r128
driver, made an xorg.conf file . . . and after numerous attempts to get
the display back, today I got "fbdev" and mode "1920 x 1200" to bring
the GUI back online . . . but, there was another "xorg" crash on reboot,
which I reported, along with filing this bug against the r128 module for
this PPC machine.

F

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
Uname: Linux 4.4.0-31-powerpc-smp ppc
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: powerpc
BootLog:
 fsck from util-linux 2.27.1
 /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Jul 29 14:34:22 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-01-31 (179 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
Lsusb:
 Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
 Bus 002 Device 003: ID 05ac:0201 Apple, Inc. USB Keyboard [Alps or Logitech, 
M2452]
 Bus 002 Device 002: ID 05ac:1001 Apple, Inc. Keyboard Hub [ALPS]
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jul 29 14:15:13 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputAlps Electric Apple USB Keyboard KEYBOARD, id 6
 inputKensington  USB/PS2 Wheel Mouse MOUSE, id 7
 inputPMU  KEYBOARD, id 8
xserver.errors: AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: apport-bug powerpc ubuntu xenial

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

Title:
  X doesn't start with r128 driver with PM 3,1 PPC ATI Rage

Status in xorg package in Ubuntu:
  New

Bug description:
  I was working on bug #1541082 which was reporting "blotchy" graphics
  images on my PowerMac3,1 with Rage ATI Pro 128 card . . . and got the
  suggestion to try to add the "r128" driver, which I did.  After that
  the display went black.  After fiddling around with it, I removed the
  r128 driver, made an xorg.conf file . . . and after numerous attempts
  to get the display back, today I got "fbdev" and mode "1920 x 1200" to
  bring the GUI back online . . . but, there was another "xorg" crash on
  reboot, which I reported, along with filing this bug against the r128
  module for this PPC machine.

  F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
  Uname: Linux 4.4.0-31-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jul 29 14:34:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (179 days ago)

[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

2016-07-29 Thread Niklas Janz

You're the best! Thanks ;-)

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

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

-- 
Mailing list: https://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 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

On Fri, Jul 29, 2016 at 11:20 AM, Fritz Hudnut 
wrote:

> But, I was thinking this morning I have some notes about the display
> "modes" where I have used something like "1024 x 768@60-32" . . .
> something like that, and ***that*** did make a difference on my iBook to
> get the display to work properly . . . possibly that is worth trying out .
> . . .  I'll post back on the "progress" . . . when I get there.

Good news, after trying three or four different variations, the GUI is back
using "fbdev" and I also changed the mode to "1920 x 1200" . . . and the
log in splash image is "smoother" than it was before, "blotchy" but not as
"blotchy" as it was before the xorg.conf file.

Only caveat is there was a "crash report" generated relating to
"xorg-server" or something like that.  I "reported" it.  There was an
obvious "glitch" in the mouse cursor movement when I logged in which I've
come to understand indicates a "crash."

I'm typing this in the MATE 16 GUI; we'll see how it goes on reboot.
Sending the apport-collect data to the new bug r128 related.

F

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

2016-07-29 Thread Christian Boltz

Nice finding.

The code is:

if e['request_mask'] in ('send', 'receive'):
self.debug_logger.debug('UNHANDLED (request_mask is send or 
receive): %s' % e)
return None

so with requested_mask="send receive" I'm not surprised that you still
see a crash ;-)

I just sent a patch to the mailinglist for review.

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

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

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

[Touch-packages] [Bug 290639] Re: NetworkManager cannot handle both eth0 and ppp0 at the same time

2016-07-29 Thread Anita Kuno

This bug looks a bit dusty, what is the status on this? I connect via
eth0 to my ip provider which uses ppp0 and can't seem to connect using
xenial. I'm wondering if this is the issue.

Right now I'm considering dropping back to Trusty which comes with an
earlier version of network-manager and seems to be able to get me
connected without an issue.

Would love to see an update to this bug. Thank you, Anita.

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

Title:
  NetworkManager cannot handle both eth0 and ppp0 at the same time

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: network-manager

  Okay, so I have a pppoe-connection to my internet-provider which I
  connect to via a WLAN-AP that's connected with my home-network.

  In network-manager I can set up my Ethernet (eth0) connection to
  connect to the local network and my ppp0e (ppp0) connection to the
  internet. When I click on network-manager, I only have radio-buttons
  to select the desired "wired connection" which only allows me to
  EITHER start eth0 OR ppp0. When I'm connected to the internet, I can't
  access the LAN and vice-versa.

  The ony solution for me right now is to use pppoeconf and configure
  the eth0-connection via config file, which of course breaks network-
  manager.

  What I am asking for is simple: Allow the use of more than just one
  "wired connection" in network-manager (ditch the radio buttons and
  make them "multiple choice"?)

  here's my etc/network/interfaces: (comments were made by me for better
  readability here, they're not in the file itself)

  ##BEGIN interfaces
  auto lo
  iface lo inet loopback

  auto dsl-provider
  iface dsl-provider inet ppp
  pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
  provider dsl-provider

  auto eth0
  iface eth0 inet static
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.1
  ##END interfaces 

  System is 8.10 with all the latest updates,
  network-manager is:
  network-manager:
Installiert: 0.7~~svn20081018t105859-0ubuntu1
Kandidat: 0.7~~svn20081018t105859-0ubuntu1
Versions-Tabelle:
   *** 0.7~~svn20081018t105859-0ubuntu1 0
  500 http://at.archive.ubuntu.com intrepid/main Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1441325] Re: Sound plays randomly or not at all

2016-07-29 Thread Jim Hodapp

I'm curious what you ended up doing as a workaround for the issue? Have
you tried using the SoundEffect class at all?

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

Title:
  Sound plays randomly or not at all

Status in Media Hub:
  Invalid
Status in PulseAudio:
  New
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I'm making an simple app. In the app on a click of a button a sound should 
play. Unfortunately it plays sometimes but mostly not at all. Here's the place 
in the app code where the sound I want to play is: 
http://bazaar.launchpad.net/~mpredotka/+junk/pop-that-wrap/view/head:/Bubble.qml#L16
  When I run my app from SDK to my bq phone I get errors like this:
  Debug-helper> Environment: confined
  Debug-helper> Environment initialized, starting the application
  Debug-helper> Executing /usr/bin/qmlscene['/usr/bin/qmlscene', '$@', 
'Main.qml']
  shm_open() failed: Permission denied
  process 26220: arguments to dbus_message_new_method_call() were incorrect, 
assertion "_dbus_check_is_valid_path (path)" failed in file 
../../dbus/dbus-message.c line 1266.
  This is normally a bug in some application using the D-Bus library.
  process 26220: arguments to dbus_message_set_auto_start() were incorrect, 
assertion "message != NULL" failed in file ../../dbus/dbus-message.c line 2951.
  This is normally a bug in some application using the D-Bus library.
  process 26220: arguments to dbus_message_iter_init_append() were incorrect, 
assertion "message != NULL" failed in file ../../dbus/dbus-message.c line 2348.
  This is normally a bug in some application using the D-Bus library.
  QDBusConnection: error: could not send message to service 
"org.freedesktop.NetworkManager" path "" interface 
"org.freedesktop.DBus.Introspectable" member "Introspect": 
  using blocking call!
  Using blocking call!
  process 26220: arguments to dbus_message_new_method_call() were incorrect, 
assertion "_dbus_check_is_valid_path (path)" failed in file 
../../dbus/dbus-message.c line 1266.
  This is normally a bug in some application using the D-Bus library.
  process 26220: arguments to dbus_message_set_auto_start() were incorrect, 
assertion "message != NULL" failed in file ../../dbus/dbus-message.c line 2951.
  This is normally a bug in some application using the D-Bus library.
  process 26220: arguments to dbus_message_iter_init_append() were incorrect, 
assertion "message != NULL" failed in file ../../dbus/dbus-message.c line 2348.
  This is normally a bug in some application using the D-Bus library.
  QDBusConnection: error: could not send message to service 
"org.freedesktop.NetworkManager" path "" interface 
"org.freedesktop.DBus.Introspectable" member "Introspect": 
  using blocking call!
  Using blocking call!
  UbuntuWindow::handleSurfaceFocusChange(focused=true)
  UbuntuWindow::handleSurfaceResize(width=540, height=919)
  UbuntuClipboard - Got invalid serialized mime data. Ignoring it.
  QSoundEffect(pulseaudio): Error in pulse audio stream
  QSoundEffect(pulseaudio): Error in pulse audio stream
  QSoundEffect(pulseaudio): Error in pulse audio stream
  QSoundEffect(pulseaudio): Error in pulse audio stream

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1441325/+subscriptions

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

[Touch-packages] [Bug 1607845] Re: List of versioned kernels is not right for Ubuntu

2016-07-29 Thread Jarno Suni

This lists packages containing "goldfish": 
http://packages.ubuntu.com/search?keywords=goldfish=names=all=all
According to it there is linux-goldfish-headers-3.4.0-4 for yakkety
Please note that I am talking about versioned kernel packages.
In Trusty, 
apt-cache search --names-only '.*' | awk '/^linux-.+-[0-9]+\.[0-9]+.+/{print 
$1}' | grep linux-.*-tools
gives currently 473 matches of which 165 does not match "linux-cloud-tools" 
such as linux-goldfish-tools-3.4.0-3 and linux-lts-xenial-tools-4.4.0-31.

I have been creating a script that keeps linux kernel packages that have
certain version and purge other linux kernel packages, so I was just
wondering, if I have to care about the other operating systems. I am
neither familiar with the kernels of other operation systems than linux
nor their versioning. Do linux, kfreebsd and gnumach possibly share a
version? It is hard to use the configuration variable to purge linux
kernels exclusively for what it is worth.

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

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

2016-07-29 Thread Chris Coulson

** Changed in: oxide
Milestone: branch-1.17 => branch-1.18

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

Title:
  implement the HTML5 pointer lock API

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

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

  https://archive.org/details/win3_Mono3Dlx

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

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

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

[Touch-packages] [Bug 1540108] Re: Blue dots for text marking/placing a cursor are too small

2016-07-29 Thread GTriderXC

:-) "in response to user feedback. Evidently we haven't found a solution that
works for everyone". Is there anyone who may explain me how the present
solution works? It does not unless we use a touchpen, a very thin one. Who
likes now the blue thing wchich covers the text(photo)?
As I understand it should help us place the cursor »precisely« where we want
to. I can't do it neither with M10 nor 4.5 aquaris. But I know how it can work
on 5inch Nexus5 on Android. Nexus 5 with Android is an example to follow. It
works, precisely and without even zooming the screen.

** Attachment added: "screenshot20160729_220022034.png"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1540108/+attachment/4709911/+files/screenshot20160729_220022034.png

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

Title:
Blue dots for text marking/placing a cursor are too small

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

Bug description:
I mean the blue dots that are visible in the photo. Ok my hands are not the
smallest but I saw already bigger ones. I can not place the cursor in the text
where I want to as well as mark/highlight the text to cut or copy. On Android
these dots are big raindrops. I have no problem. In Ubuntu it simply doesn't
work at all without a touchpen. These dots are too tiny.
--
I'm updating the bug with an additional information which is actually another
problem which You can see in the photo in a comment #3

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

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

[Touch-packages] [Bug 1540108] Re: Blue dots for text marking/placing a cursor are too small

2016-07-29 Thread GTriderXC

Nexus 5/Android 6

Just try how it should work and how it doesn't on Ubuntu.

** Attachment added: "image20160729_221614328.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1540108/+attachment/4709913/+files/image20160729_221614328.jpg

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

Title:
  Blue dots for text marking/placing a cursor are too small

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

Bug description:
  I mean the blue dots that are visible in the photo. Ok my hands are not the 
smallest but I saw already bigger ones. I can not place the cursor in the text 
where I want to as well as mark/highlight the text to cut or copy. On Android 
these dots are big raindrops. I have no problem. In Ubuntu it simply doesn't 
work at all without a touchpen. These dots are too tiny.
  --
  I'm updating the bug with an additional information which is actually another 
problem which You can see in the photo in a comment #3

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

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

[Touch-packages] [Bug 1540108] Re: Blue dots for text marking/placing a cursor are too small

2016-07-29 Thread GTriderXC

** Attachment added: "image20160729_221432656.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1540108/+attachment/4709912/+files/image20160729_221432656.jpg

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

Title:
  Blue dots for text marking/placing a cursor are too small

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

Bug description:
  I mean the blue dots that are visible in the photo. Ok my hands are not the 
smallest but I saw already bigger ones. I can not place the cursor in the text 
where I want to as well as mark/highlight the text to cut or copy. On Android 
these dots are big raindrops. I have no problem. In Ubuntu it simply doesn't 
work at all without a touchpen. These dots are too tiny.
  --
  I'm updating the bug with an additional information which is actually another 
problem which You can see in the photo in a comment #3

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

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

[Touch-packages] [Bug 1607935] Re: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-07-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  error occurred while upgrading from 14.0.4 LTS to 16.0.4 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 29 00:14:56 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-07-03 (391 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1607935] [NEW] package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-07-29 Thread Robert Melson

Public bug reported:

error occurred while upgrading from 14.0.4 LTS to 16.0.4 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul 29 00:14:56 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-07-03 (391 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  error occurred while upgrading from 14.0.4 LTS to 16.0.4 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 29 00:14:56 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-07-03 (391 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1573773] Re: System freezes randomly a few times a day

** Description changed:

  ~ % cat /var/log/xdm.log
  
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  resize called 1920 1200
  Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstartup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session 
/etc/X11/xdm/Xsession
  resize called 3840 1200
  resize called 1920 1200
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] EQ overflow continuing.  200 events have been dropped.
  
- My system info:
+ WORKAROUND: Use nvidia-358 driver.
  
-  ~ % uname -a
- Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
-  ~ % cat /etc/debian_version
- stretch/sid
- 
-  ~ % lsb_release -a
- No LSB modules are available.
- Distributor ID:   Ubuntu
- Description:  Ubuntu Xenial Xerus (development branch)
- Release:  16.04
- Codename: xenial
-  ~ %
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 720] [10de:1288] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK208 [GeForce GT 720] 
[1462:8c90]
   NVIDIA Corporation GK208

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

2016-07-29 Thread Christopher Townsend

** Branch linked: lp:~dandrader/qtubuntu/content-hub-clipboard

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

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Tags removed: xmir

** No longer affects: xorg-server (Ubuntu)

** No longer affects: unity8 (Ubuntu)

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

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

Status in Libertine:
  In Progress
Status in Libertine devel series:
  In Progress
Status in Libertine trunk series:
  Triaged
Status in Mir:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in libertine package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  In Progress

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

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

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

[Touch-packages] [Bug 1607930] Re: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-07-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04 on Samsung S3510 Laptop. Lots of errors
  during upgrade process, then had to manual restart the machine. This
  gave me the error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 29 19:37:05 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-02-15 (164 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

-- 
Mailing list: https://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 1573773] Re: System freezes randomly a few times a day

Yes, that is correct.

On Fri, Jul 29, 2016 at 7:41 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, to confirm, you are stating that when using nvidia-358 from
> the Ubuntu repositories (not PPA, third party installs, etc.) doesn't
> crash at all?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] EQ overflow continuing.  200 events have been dropped.
>
>   My system info:
>
>~ % uname -a
>   Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18
> 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>~ % cat /etc/debian_version
>   stretch/sid
>
>~ % lsb_release -a
>   No LSB modules are available.
>   Distributor ID:   Ubuntu
>   Description:  Ubuntu

[Touch-packages] [Bug 1607930] [NEW] package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-07-29 Thread Thomas

Public bug reported:

After upgrading to 16.04 on Samsung S3510 Laptop. Lots of errors during
upgrade process, then had to manual restart the machine. This gave me
the error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul 29 19:37:05 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-02-15 (164 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04 on Samsung S3510 Laptop. Lots of errors
  during upgrade process, then had to manual restart the machine. This
  gave me the error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 29 19:37:05 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-02-15 (164 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1573773] Re: System freezes randomly a few times a day

rohshall, to confirm, you are stating that when using nvidia-358 from
the Ubuntu repositories (not PPA, third party installs, etc.) doesn't
crash at all?

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

Title:
  System freezes randomly a few times a day

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ~ % cat /var/log/xdm.log

  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  resize called 1920 1200
  Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstartup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session 
/etc/X11/xdm/Xsession
  resize called 3840 1200
  resize called 1920 1200
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] EQ overflow continuing.  200 events have been dropped.

  My system info:

   ~ % uname -a
  Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
   ~ % cat /etc/debian_version
  stretch/sid

   ~ % lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  Codename: xenial
   ~ %
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None

Re: [Touch-packages] [Bug 1573773] Re: System freezes randomly a few times a day

Sorry, I meant nvidia-358 and not nvidia-258

On Fri, Jul 29, 2016 at 7:01 PM, Salil Wadnerkar 
wrote:

> nvidia-258, available in the ubuntu repository, worked mostly. I don't
> remember what didn't work. However, I can vouch for nvidia-367, which is
> avalable through ppa ppa:graphics-drivers/ppa. It worked without any issues.
>
> On Fri, Jul 29, 2016 at 6:17 PM, Christopher M. Penalver <
> christopher.m.penal...@gmail.com> wrote:
>
>> rohshall, to clarify, if you use the nvidia proprietary drivers provided
>> by the Ubuntu repositories as per
>> https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
>> problem a WORKAROUND?
>>
>> ** Tags removed: bios-outdated-2902
>> ** Tags added: latest-bios-2902
>>
>> ** Changed in: xorg (Ubuntu)
>>Importance: Low => Medium
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1573773
>>
>> Title:
>>   System freezes randomly a few times a day
>>
>> Status in xorg package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   ~ % cat /var/log/xdm.log
>>
>>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>>   resize called 1920 1200
>>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
>> /etc/X11/xdm/Xsetup
>>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
>> /etc/X11/xdm/Xstartup
>>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
>> /etc/X11/xdm/Xsession
>>   resize called 3840 1200
>>   resize called 1920 1200
>>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
>> existing events are processed.
>>   (EE)
>>   (EE) Backtrace:
>>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x61f3) [0x7f27e538b1f3]
>>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x6a5d) [0x7f27e538ba5d]
>>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
>> [0x7f27ee6db4a0]
>>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
>> [0x7f27efa880f8]
>>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
>> [0x7f27efa8adbb]
>>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
>> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
>> [0x7f27ee6c6830]
>>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>>   (EE)
>>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
>> higher up the stack.
>>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>>   (EE)
>>   (EE) Backtrace:
>>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x61f3) [0x7f27e538b1f3]
>>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x6a5d) [0x7f27e538ba5d]
>>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
>> [0x7f27ee6db4a0]
>>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
>> [0x7f27efa880f8]
>>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
>> [0x7f27efa8adbb]
>>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
>> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>>   (EE) 16:

[Touch-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-07-29 Thread Dave Chiluk

Personally I think we should modify MNTTAB in zfs-linux to point to
/proc/self/mounts.  This may not be completely straightforward *(there
are a number of places that point to /etc/mnttab directly, or have logic
around it and /proc/mounts), but it should be doable.  I like this
solution most because it doesn't require us to increase the number of
dependencies in the zfs systemd scripts.

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

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

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

[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

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

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

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed
Status in phone-app package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

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

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

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed
Status in phone-app package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

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

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

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed
Status in phone-app package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

-- 
Mailing list: https://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 1573773] Re: System freezes randomly a few times a day

nvidia-258, available in the ubuntu repository, worked mostly. I don't
remember what didn't work. However, I can vouch for nvidia-367, which is
avalable through ppa ppa:graphics-drivers/ppa. It worked without any issues.

On Fri, Jul 29, 2016 at 6:17 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, to clarify, if you use the nvidia proprietary drivers provided
> by the Ubuntu repositories as per
> https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
> problem a WORKAROUND?
>
> ** Tags removed: bios-outdated-2902
> ** Tags added: latest-bios-2902
>
> ** Changed in: xorg (Ubuntu)
>Importance: Low => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi]

[Touch-packages] [Bug 1594776] Re: add-apt-repository explodes on missing ppa

2016-07-29 Thread Brian Murray

I did not receive a Traceback with the version of the package from
-proposed:

[ 11:58AM 10015 ]  [ bdmurray@impulse:~ ]
 $ sudo add-apt-repository ppa:juju/next
Cannot add PPA: 'ppa:~juju/ubuntu/next'.
The team named '~juju' has no PPA named 'ubuntu/next'
Please choose from the following available PPAs:
 * '1.22':  1.22 Updates
 * '1.22-proposed':  1.22 Proposed
 * '1.23':  1.23 Updates
 * 'daily':  Juju Daily
 * 'devel':  juju devel packages
 * 'enablement':  Juju Enablement
 * 'experimental':  juju experimental packages
 * 'golang':  juju-golang
 * 'proposed':  juju proposed packages
 * 'stable':  juju stable packages
[ 11:59AM 10016 ]  [ bdmurray@impulse:~ ]
 $ apt-cache policy software-properties-common
software-properties-common:
  Installed: 0.96.20.3
  Candidate: 0.96.20.3
  Version table:
 *** 0.96.20.3 100
100 /var/lib/dpkg/status
 0.96.20.2 500
500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu xenial-updates/main i386 Packages
 0.96.20 500
500 http://192.168.10.7/ubuntu xenial/main amd64 Packages
500 http://192.168.10.7/ubuntu xenial/main i386 Packages


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

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

Title:
  add-apt-repository explodes on missing ppa

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed

Bug description:
  Just saw this on freshly updated Xenial. I think it's trying to be
  helpful and tell me what PPAs a particular LP team has published, but
  in the end it explodes:

  $ sudo add-apt-repository ppa:juju/next
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 102, 
in _get_https_content_py3
  lp_page = urllib.request.urlopen(request, cafile=LAUNCHPAD_PPA_CERT)
File "/usr/lib/python3.5/urllib/request.py", line 162, in urlopen
  return opener.open(url, data, timeout)
File "/usr/lib/python3.5/urllib/request.py", line 471, in open
  response = meth(req, response)
File "/usr/lib/python3.5/urllib/request.py", line 581, in http_response
  'http', request, response, code, msg, hdrs)
File "/usr/lib/python3.5/urllib/request.py", line 509, in error
  return self._call_chain(*args)
File "/usr/lib/python3.5/urllib/request.py", line 443, in _call_chain
  result = func(*args)
File "/usr/lib/python3.5/urllib/request.py", line 589, in http_error_default
  raise HTTPError(req.full_url, code, msg, hdrs, fp)
  urllib.error.HTTPError: HTTP Error 404: Not Found

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 327, 
in get_ppa_info
  ret = get_ppa_info_from_lp(user, ppa)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 92, 
in get_ppa_info_from_lp
  return get_info_from_lp(lp_url)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 88, 
in get_info_from_lp
  return _get_https_content_py3(lp_url)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 108, 
in _get_https_content_py3
  raise PPAException("Error reading %s: %s" % (lp_url, reason), e)
  softwareproperties.ppa.PPAException: 'Error reading 
https://launchpad.net/api/1.0/~juju/+archive/ubuntu/next: Not Found'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 393, 
in shortcut_handler
  return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 356, 
in __init__
  info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 339, 
in get_ppa_info
  _get_suggested_ppa_message(user, ppa))
  softwareproperties.shortcuts.ShortcutException: Cannot add PPA: 
'ppa:~juju/ubuntu/next'.
  The team named '~juju' has no PPA named 'ubuntu/next'
  Please choose from the following available PPAs:
   * '1.22':  1.22 Updates
   * '1.22-proposed':  1.22 Proposed
   * '1.23':  1.23 Updates
   * 'daily':  Juju Daily
   * 'devel':  juju devel packages
   * 'enablement':  Juju Enablement
   * 'experimental':  juju experimental packages
   * 'golang':  juju-golang
   * 'proposed':  juju proposed packages
   * 'stable':  juju stable packages
  Error: 'ppa:juju/next' invalid

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

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

[Touch-packages] [Bug 1607920] [NEW] zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-07-29 Thread Dave Chiluk

Public bug reported:

[Impact]

 * zfs services fail on firstboot if zfs-utils is integrated into the
deployment image.

 * Output from systemd - 
sudo systemctl --failed 
UNIT LOAD ACTIVE SUB DESCRIPTION 
● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
● zfs-mount.service loaded failed failed Mount ZFS filesystems 

 * This is particularly frustrating for users who use automated
monitoring as it means virtual machines must always be restarted before
showing as clean.

 * This failure is due to zfs services starting up before /etc/mtab has
a chance to be symlinked to /proc/mounts.

[Test Case]

 1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
 2. Boot machine
 3. Check systemctl --failed.

[Regression Potential]

 *
 
[Other Info]
 
 * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

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

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

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

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

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

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

[Touch-packages] [Bug 1607921] [NEW] package libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1 failed to install/upgrade: no package named 'libopencv-features2d2.4v5' is installed, cannot configure

2016-07-29 Thread Sherman Anderson

Public bug reported:

This happened while upgrading to latest Ubuntu version.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul 29 12:09:17 2016
ErrorMessage: no package named 'libopencv-features2d2.4v5' is installed, cannot 
configure
InstallationDate: Installed on 2015-10-14 (288 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: opencv
Title: package libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1 failed to 
install/upgrade: no package named 'libopencv-features2d2.4v5' is installed, 
cannot configure
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1 failed to
  install/upgrade: no package named 'libopencv-features2d2.4v5' is
  installed, cannot configure

Status in opencv package in Ubuntu:
  New

Bug description:
  This happened while upgrading to latest Ubuntu version.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 29 12:09:17 2016
  ErrorMessage: no package named 'libopencv-features2d2.4v5' is installed, 
cannot configure
  InstallationDate: Installed on 2015-10-14 (288 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: opencv
  Title: package libopencv-features2d2.4v5 2.4.9.1+dfsg-1.5ubuntu1 failed to 
install/upgrade: no package named 'libopencv-features2d2.4v5' is installed, 
cannot configure
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1350782] Re: Upstart does not reopen /var/log/upstart/* logfiles upon log rotation

2016-07-29 Thread Vahid Mardani

Useful thread

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

Title:
  Upstart does not reopen /var/log/upstart/* logfiles upon log rotation

Status in upstart package in Ubuntu:
  Invalid

Bug description:
  Note: this issue is reported from a 12.04 system, but I've confirmed
  the same behavior on a 14.04 system.

  Logrotate configuration for Upstart logs has no postrotate action:

  /var/log/upstart/*.log {
  daily
  missingok
  rotate 7
  compress
  notifempty
nocreate
  }

  As a result, when logs are rotated, upstart keeps open handles on
  deleted log files instead of reopening the new log files:

  # lsof -p1 | fgrep /var/log/upstart
  . . .
  init  1 root8w   REG  253,1   62  789436 
/var/log/upstart/dbus.log.1 (deleted)
  . . .

  From this point on, all subsequent log messages are lost, delivered
  into a deleted file.

  I could not find a way to get the upstart init process to reopen its
  log files, short of restarting _all_ services that log to
  /var/log/upstart/*.log files, which does not seem like a good solution
  at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upstart 1.5-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Thu Jul 31 10:43:25 2014
  InstallationMedia: Ubuntu-Server 10.04.4 LTS "Lucid Lynx" - Release amd64 
(20120214.2)
  MarkForUpload: True
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to precise on 2013-10-23 (280 days ago)

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

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

[Touch-packages] [Bug 1607891] Re: X doesn't start with r128 driver (PowerMac 3, 1) [powerpc]

2016-07-29 Thread Bug Watch Updater

** Changed in: xserver-xorg-video-r128 (Debian)
   Status: Unknown => Confirmed

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

Title:
  X doesn't start with r128 driver (PowerMac 3,1) [powerpc]

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Debian:
  Confirmed

Bug description:
  X seems to start, but only produces a black display. Happens on a
  PowerMac 3,1 with Rage 128 PRO AGP 4x grapics card. Driver used:
  xserver-xorg-video-r128

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1607891/+subscriptions

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

[Touch-packages] [Bug 1573773] Re: System freezes randomly a few times a day

rohshall, to clarify, if you use the nvidia proprietary drivers provided
by the Ubuntu repositories as per
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
problem a WORKAROUND?

** Tags removed: bios-outdated-2902
** Tags added: latest-bios-2902

** Changed in: xorg (Ubuntu)
   Importance: Low => Medium

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

Title:
  System freezes randomly a few times a day

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ~ % cat /var/log/xdm.log

  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  resize called 1920 1200
  Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstartup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session 
/etc/X11/xdm/Xsession
  resize called 3840 1200
  resize called 1920 1200
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] EQ overflow continuing.  200 events have been dropped.

  My system info:

   ~ % uname -a
  Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
   ~ % cat /etc/debian_version
  stretch/sid

   ~ % lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  Codename: xenial
   ~ %
  ---

Re: [Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

On Fri, Jul 29, 2016 at 10:24 AM, ernsteiswuerfel 
wrote:

> Added the upstream bug to this tracker. Then I realized that strictly
> speaking this bug "X doesn't start with r128 driver (ATI RAGE)
> [powerpc]" has a different meaning from this one here "blotchy
> graphics". I think it's best to create a new Ubuntu Xorg bug and add the
> upstream info there.
>
> Sorry for the noise!
>
> @Fritz:
>
> Your xorg.conf looks fine. After altering parameters check your Xorg.log
> after you restarted X, to look what exactly went wrong with the driver you
> selected xorg.conf. Just use the different drivers "modesetting", "fbdev",
> "fbdevhw" with different bit depths and see what happens.
> If your monitor is capacle also always use the native resolution of your
> monitor. The Rage 128 is able to do 1920x1080 if you got the most recent PM
> 3,1 (http://identimac.com/modelDetails/Power%20Macintosh%20G4/23.html)
>

Yes, I'm also sorry for the "noise," but I decided to include it here as
well to show the personal efforts being expended to work on this problem .
. . and the resultant, "now it's not blotchy, now it is a blackish screen
with no images . . . that is happening, etc.

@ernsteiswuerfel:

OK, glad to hear that, yes, I thought it looked "OK" as well, but, it made
no difference in display showing up, or even trying to show up.  Although
when I booted the live DVD session it took literally 3 or 4 minutes for the
cursor to appear and then the desktop; and perhaps I haven't been letting
it take that long with these recent efforts??  It's all become a tad bit
"odd" . . . in that trying the --configure gambit was returned as "failed"
. . . and looking through "lsmod" shows none of the usual suspects as far
as video drivers goes . . . and I did "autoclean" trying to remove "r128"
to see if that would let the xorg.conf get busy . . . and r128 didn't show
up in that list, so I did "sudo rm x-x-v-r128" (spelled out) and then it
said "no such file or directory" . . . .

And, multiple reboots and so forth, makes for a lot of time . . . .
Anyway, as it is now, the graphics are not "blotchy" . . . they are "gone"
so I don't know how I can support a "new" Bugzilla r128 bug with "evidence"
because . . . now the screen is black, etc . . . and there is an xorg.conf
file whereas before there wasn't, etc.

I did look over the Xorg.log a couple times . . . nothing of any apparent
relevance showed up, but then this area is an area of weakness . . . I have
the "dual-boot" install process down, and years back I spent endless hours
trying to get 12.04 to run the display on my old iMac 800 . . . now I'm
generally finding that it is easier to do a fresh install than to mess
around with the console on the tiny details . . . .

But, I was thinking this morning I have some notes about the display
"modes" where I have used something like "1024 x 768@60-32" . . . something
like that, and ***that*** did make a difference on my iBook to get the
display to work properly . . . possibly that is worth trying out . . . .
I'll post back on the "progress" . . . when I get there.

F

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log

[Touch-packages] [Bug 1607845] Re: List of versioned kernels is not right for Ubuntu

2016-07-29 Thread Julian Andres Klode

There are no 'linux-goldfish-headers' packages. In fact, there is no
package with goldfish in its name in yakkety.

Regarding 'linux-.*-tools', there is "linux-cloud-tools" which is
missing.

Concerning the second part: They are mostly irrelevant, but they don't
hurt. Better than keeping a packaging diff just to have a few lines less
in an automatically generated config file... I think the modules part
might be useful if you build stuff with module-assistant, but not sure.

So, unless I missed something, I'm going to fix the linux-cloud-tools
(or linux-.*-tools, but that might be too broad?) part and thats it.

In any case, if that's an issue for you, you can easily work around it
by adding your own stuff to "APT::VersionedKernelPackages".

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

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

[Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

For the sake of correctness I added a new bug:
https://bugs.launchpad.net/xorg-server/+bug/1607891

If you like just add the relevant data with "apport-collect" to this bug
after "r128" failed.

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1434603] Re: Ubuntu should add default support for exFAT partitions

2016-07-29 Thread Zeioth

+1

** Description changed:

  If a USB pendrive containing an exFAT partition is connected, Ubuntu
  can't mount the partition. Test has been done on a Vivid amd64 live
  system using today's daily ISO.
  
  Steps to reproduce:
  1- Insert an USB pendrive containing an exFAT partition
  2- The partition is not automatically mounted
  3- Trying to manually mount the partition via the terminal shows this output:
- mount: unknown filesystem type 'exfat'
+ mount: unknown filesystem type 'exfat'
  
  Steps to fix the issue:
  1- Install packages exfat-fuse and exfat-utils
  
  exFAT pendrives are more and more common in newer devices, and this
  issue is not easily fixable by the average John Doe. We should add the
  two packages above to the seeds and grant default support to our users.

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

Title:
  Ubuntu should add default support for exFAT partitions

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  If a USB pendrive containing an exFAT partition is connected, Ubuntu
  can't mount the partition. Test has been done on a Vivid amd64 live
  system using today's daily ISO.

  Steps to reproduce:
  1- Insert an USB pendrive containing an exFAT partition
  2- The partition is not automatically mounted
  3- Trying to manually mount the partition via the terminal shows this output:
  mount: unknown filesystem type 'exfat'

  Steps to fix the issue:
  1- Install packages exfat-fuse and exfat-utils

  exFAT pendrives are more and more common in newer devices, and this
  issue is not easily fixable by the average John Doe. We should add the
  two packages above to the seeds and grant default support to our
  users.

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

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

[Touch-packages] [Bug 1607891] [NEW] X doesn't start with r128 driver (PowerMac 3, 1) [powerpc]

Public bug reported:

X seems to start, but only produces a black display. Happens on a
PowerMac 3,1 with Rage 128 PRO AGP 4x grapics card. Driver used:
xserver-xorg-video-r128

** Affects: xorg-server
 Importance: Unknown
 Status: Unknown

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

** Affects: xserver-xorg-video-r128 (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: xserver-xorg-video-r128 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820233
   Importance: Unknown
   Status: Unknown

** Bug watch added: freedesktop.org Bugzilla #94916
   https://bugs.freedesktop.org/show_bug.cgi?id=94916

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=94916
   Importance: Unknown
   Status: Unknown

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

Title:
  X doesn't start with r128 driver (PowerMac 3,1) [powerpc]

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Debian:
  Unknown

Bug description:
  X seems to start, but only produces a black display. Happens on a
  PowerMac 3,1 with Rage 128 PRO AGP 4x grapics card. Driver used:
  xserver-xorg-video-r128

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1607891/+subscriptions

-- 
Mailing list: https://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 1573773] Re: System freezes randomly a few times a day

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2902
03/31/2016


On Fri, Jul 29, 2016 at 4:46 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, as previously requested, please provide the output of the
> following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] EQ overflow continuing.  200 events have been dropped.
>
>   My system info:
>
>~ % uname -a
>   Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18
> 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>~ % cat /etc/debian_version
>   stretch/sid
>
>~ % lsb_release -a
>   No LSB

[Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

Added the upstream bug to this tracker. Then I realized that strictly
speaking this bug "X doesn't start with r128 driver (ATI RAGE)
[powerpc]" has a different meaning from this one here "blotchy
graphics". I think it's best to create a new Ubuntu Xorg bug and add the
upstream info there.

Sorry for the noise!

@Fritz:

Your xorg.conf looks fine. After altering parameters check your Xorg.log after 
you restarted X, to look what exactly went wrong with the driver you selected 
xorg.conf. Just use the different drivers "modesetting", "fbdev", "fbdevhw" 
with different bit depths and see what happens.
If your monitor is capacle also always use the native resolution of your 
monitor. The Rage 128 is able to do 1920x1080 if you got the most recent PM 3,1 
(http://identimac.com/modelDetails/Power%20Macintosh%20G4/23.html)

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1607075] Re: systemd 229-4ubuntu7 ADT test failure with linux 4.4.0-33.52

2016-07-29 Thread Andy Whitcroft

FAIL: test_no_failed (__main__.ServicesTest)
No failed units
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest.qQr62c/build.1BH/systemd-229/debian/tests/boot-and-services", 
line 54, in test_no_failed
self.assertEqual(failed, [])
AssertionError: Lists differ: ['keyboard-setup.service loaded failed failed Set 
console keymap'] != []

First list contains 1 additional elements.
First extra element 0:
'keyboard-setup.service loaded failed failed Set console keymap'

- ['keyboard-setup.service loaded failed failed Set console keymap']
+ []

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

Title:
  systemd 229-4ubuntu7 ADT test failure with linux 4.4.0-33.52

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/s/systemd/20160727_170251@/log.gz

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

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

[Touch-packages] [Bug 1574425] Re: Installing nvidia-361 leaves me unable to log in

Jeramy Rutley, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574425/comments/4
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1574425

Title:
  Installing nvidia-361 leaves me unable to log in

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have never successfully gotten the nvidia drivers to work properly.
  Before I used nvidia-304 because that seemed to be the only driver
  other than Nouveau that worked... the other nvidia drivers just give
  me a black screen

  With nvidia-361 I get a different outcome:
  I get to the login screen, and when I try to log in, it kicks me back out to 
the login screen.

  The only thing that I can do to resolve this is Ctrl-Alt-F1, log in,
  and try to undo anything that I just broke.

  So there are a number of things that look wrong in the logs, and I am
  willing to provide any necessary information, or try things.

  
  Version: Ubuntu 16.04 LTS

  apt-cache policy nvidia-361:
  Installed and Candidate: 361.42-0ubuntu2
  Version table:
  *** 361.42-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages
100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Apr 24 22:16:46 2016
  DistUpgraded: 2016-04-24 07:38:36,778 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.2.0-35-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6]
  InstallationDate: Installed on 2015-09-28 (209 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=cda70297-42ac-43e6-aeb2-8ce418cd09cd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 24 22:09:57 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id6125 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1607572] Re: upgrade aborted because of ppp, pptp-linux, network-manager-pptp

2016-07-29 Thread Brian Murray

** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager
(Ubuntu)

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

Title:
  upgrade aborted because of ppp, pptp-linux, network-manager-pptp

Status in network-manager package in Ubuntu:
  New

Bug description:
  Please check the attached screen shot. 
  The bug happened at the end of installation at configurations.
  It says: Errors were encountered while processing:
  ppp
  pptp-linux
  network-manager-pptp
  ...
  pppconfig
  If you find a solution can you please email me.

  Regards
  Horea

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jul 28 21:09:57 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-28 (335 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1607799] Re: Dash freezes after U1 login

2016-07-29 Thread Víctor R . Ruiz

Image 385 (arale) is good, 386 is bad. This is the changelog
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-
proposed/meizu.en/arale/386.commitlog

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

Title:
  Dash freezes after U1 login

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Without U1 account, go to Ubuntu Store.
  - Tap on an app.
  - Tap on the install button.
  - Introduce credentials.

  Expected result.
  - After credentials, the app is installed.

  Actual result.
  - Dash is frozen. Cannot go back to the scopes. Launcher and indicators do 
work, though. There is no crash.

  current build number: 389
  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/1607799/+subscriptions

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

[Touch-packages] [Bug 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

Oliver, regarding this report, please post directly here (not send
personal emails). This allows others to contribute towards this.

Despite this, to see if this is a regression, if you test earlier
versions of the nvidia driver in your present install as per
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
issue improve?

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

Title:
  HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm working with an acer VN7-592G, with an Intel Core i7 Quad-Core-
  Prozessor and the NVIDIA GeForce GTX 960M. Since the upgrade to Ubuntu
  16.04 I have problems with the HDMI connection.

  If plugged in, the HDMI is recognised (xrandr), but the second monitor
  shows "no signal". After restarting the lightdm service (sudo service
  lightdm restart), the second monitor is working in most cases.
  Sometimes ubuntu freezes after lightdm restart and a hard reset has to
  be performed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 28 08:13:41 2016
  DistUpgraded: 2016-06-05 13:36:30,607 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039]
     Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039]
  InstallationDate: Installed on 2015-11-24 (246 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire VN7-592G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=347e424a-f916-4ca8-a254-caa35281e9c3 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (52 days ago)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-592G
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd09/25/2015:svnAcer:pnAspireVN7-592G:pvrV1.03:rvnAcer:rnAspireVN7-592G:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.name: Aspire VN7-592G
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 09:13:51 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: evdev: Dell Dell USB Wired Entry Keyboard: Unable to open 
evdev device "/dev/input/event7".
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

** No longer affects: xorg-server

** No longer affects: debian

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1607874] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-07-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sysv-
  rc.0.crash'

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul 29 23:52:04 2016
  DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-18 (833 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.14
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1607572] [NEW] upgrade aborted because of ppp, pptp-linux, network-manager-pptp

You have been subscribed to a public bug:

Please check the attached screen shot. 
The bug happened at the end of installation at configurations.
It says: Errors were encountered while processing:
ppp
pptp-linux
network-manager-pptp
...
pppconfig
If you find a solution can you please email me.

Regards
Horea

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.14
ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-65-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu Jul 28 21:09:57 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-28 (335 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz:
 Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
VarLogDistupgradeTermlog:

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade xenial
-- 
upgrade aborted because of ppp, pptp-linux, network-manager-pptp
https://bugs.launchpad.net/bugs/1607572
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1594400] Re: Wrong statement about "persistentSelection" property of TextArea

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Wrong statement about "persistentSelection" property of TextArea

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  In the documentation for UITK TextArea[1]:
  "Whether the TextArea should keep the selection visible when it loses 
active focus to another item in the scene. By default this is set to true;"

  In the documentation for QML TextEdit component (inherited by UITK TextArea):
  "Whether the TextEdit should keep the selection visible when it loses 
active focus to another item in the scene. By default this is set to false."

  The component from UITK[3] only set an alias to the TextEdit property,
  without changing its default value. This leads to an unexpected
  behaviour whenever the default property is set to a different value by
  the upstream project.

  In Qt 5.0.2 the property was set to true[4]. Since Qt 5.1.1, the value
  has been changed[5].

  

  [1] 
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.TextArea/
  [2] http://doc.qt.io/qt-5/qml-qtquick-textedit.html#persistentSelection-prop

  [3] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  toolkit/staging/view/head:/src/Ubuntu/Components/1.3/TextArea.qml

  [4] 
http://qt.apidoc.info/5.0.2/qtquick/qml-qtquick2-textedit.html#persistentSelection-prop
  [5] 
http://qt.apidoc.info/5.1.1/qtquick/qml-qtquick2-textedit.html#persistentSelection-prop

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

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

[Touch-packages] [Bug 1588172] Re: qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:828: TypeError: Cannot read property 'header' of null

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:828: TypeError:
  Cannot read property 'header' of null

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Using the AdaptivePageLayout in something other than a MainView causes it to 
look for a header that isn't there even if all Page's use their own header.
  Note: Functionally this works fine.

  Item {
  AdaptivePageLayout {
  anchors.fill: parent
  primaryPage: Page {
  header: PageHeader {
  }
  }
  }
  }

  qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:828: TypeError: Cannot read 
property 'header' of null
  qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:827: TypeError: Cannot read 
property 'header' of null
  qml/Ubuntu/Components/1.3/AdaptivePageLayout.qml:826: TypeError: Cannot read 
property 'header' of null

  This occurs with a hypothetical MainView alternative (bug 1587431) as
  well as a custom root component tailored to the app.

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

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

[Touch-packages] [Bug 1424696] Re: package libva1 1.3.1-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libva1/changelog.Debian.gz', which is different from other instances of

2016-07-29 Thread Sebastian Ramacher

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

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

Title:
  package libva1 1.3.1-3 failed to install/upgrade: trying to overwrite
  shared '/usr/share/doc/libva1/changelog.Debian.gz', which is different
  from other instances of package libva1:i386

Status in Libva:
  Invalid
Status in libva package in Ubuntu:
  Invalid

Bug description:
  I get this error after logging in

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libva1 1.3.1-3
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Sun Feb 22 15:29:59 2015
  DuplicateSignature: package:libva1:1.3.1-3:trying to overwrite shared 
'/usr/share/doc/libva1/changelog.Debian.gz', which is different from other 
instances of package libva1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libva1/changelog.Debian.gz', which is different from other 
instances of package libva1:i386
  InstallationDate: Installed on 2014-09-15 (160 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: libva
  Title: package libva1 1.3.1-3 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libva1/changelog.Debian.gz', which is different from 
other instances of package libva1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1593048] Re: ubuntu-themes should support GTK 3.20

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
yakkety-landing-042

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

Title:
  ubuntu-themes should support GTK 3.20

Status in arc-theme package in Ubuntu:
  Triaged
Status in breeze-gtk package in Ubuntu:
  Triaged
Status in mate-themes package in Ubuntu:
  Triaged
Status in ubuntu-mate-artwork package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  This is a tracking bug. ubuntu-themes needs to be updated to support
  GTK+ 3.20 before GTK+ 3.20 can land in Ubuntu.

  Some initial work has been done at
  https://code.launchpad.net/~laney/ubuntu-themes/gtk320

  If you would like to help, please contact the Ubuntu Desktop Team.

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

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

[Touch-packages] [Bug 1607875] [NEW] pulsaudio not showing a52 device

2016-07-29 Thread kenjo

Public bug reported:

so I have a external decoder that is connecting over a optical SPDIF link.
Stereo works fine and I had 5.1 working in earlier versions of ubuntu.

now I'm on 16.10 (Yakkety Yak)and I try to follow this description.
https://help.ubuntu.com/community/DigitalAC-3Pulseaudio

I have 5.1 now working in alsa with 
speaker-test -Da52:0 -c6

But I can not get it to show up in pulsaudio.  It used to be possible to
select it and do the speaker test from inside the gnome sound gui. but
now nothing :(

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-1.1ubuntu1
Uname: Linux 4.7.0-rc7+ x86_64
ApportVersion: 2.20.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   kenjo 31687 F...m pulseaudio
CurrentDesktop: Unity
Date: Fri Jul 29 18:42:37 2016
InstallationDate: Installed on 2015-10-18 (284 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to yakkety on 2016-04-22 (97 days ago)
dmi.bios.date: 02/22/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.B0
dmi.board.asset.tag: Default string
dmi.board.name: Z170A GAMING M7 (MS-7976)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7976
dmi.product.version: 1.0
dmi.sys.vendor: MSI
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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


** Tags: amd64 apport-bug yakkety

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

Title:
  pulsaudio not showing a52 device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  so I have a external decoder that is connecting over a optical SPDIF link.
  Stereo works fine and I had 5.1 working in earlier versions of ubuntu.

  now I'm on 16.10 (Yakkety Yak)and I try to follow this description.
  https://help.ubuntu.com/community/DigitalAC-3Pulseaudio

  I have 5.1 now working in alsa with 
  speaker-test -Da52:0 -c6

  But I can not get it to show up in pulsaudio.  It used to be possible
  to select it and do the speaker test from inside the gnome sound gui.
  but now nothing :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  Uname: Linux 4.7.0-rc7+ x86_64
  ApportVersion: 2.20.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   kenjo 31687 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 29 18:42:37 2016
  InstallationDate: Installed on 2015-10-18 (284 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (97 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1607874] [NEW] package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-07-29 Thread Didi Dwi Novianto

Public bug reported:

ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sysv-
rc.0.crash'

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sysv-rc 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Jul 29 23:52:04 2016
DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-04-18 (833 days ago)
InstallationMedia:
 
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.0.1ubuntu2.14
SourcePackage: sysvinit
Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages uec-images xenial

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sysv-
  rc.0.crash'

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul 29 23:52:04 2016
  DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-18 (833 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.14
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1540240] Re: Automatic Header height adjustment should be optional

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Automatic Header height adjustment should be optional

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  I am currently developing a convergence capable CAD App and i recently
  switched the UI to use AdaptivePageLayout and the new headers. I have
  noticed that the header automatically resizes across columns to match
  the column with the greatest header height.

  This doesn't suit my particular application as I would like to
  maintain maximum screen space for the drawing canvas.

  I have attached some screenshots (early development - dont judge me!!)
  of what I am seeing.

  It would be super cool if you could include a flag or option to
  disable the header adjustment for any particular page or column.

  UX Fix:

  A flag will be included in the header component to disable header 
adjustments, allowing developers to have different header heights for 
convergence apps. 
  Ideally for full screen applications the header should be set to hidden.

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

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

[Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=94916
   Importance: Unknown
   Status: Unknown

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

** Also affects: debian via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820233
   Importance: Unknown
   Status: Unknown

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1573773] Re: System freezes randomly a few times a day

rohshall, as previously requested, please provide the output of the following 
terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

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

Title:
  System freezes randomly a few times a day

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ~ % cat /var/log/xdm.log

  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  resize called 1920 1200
  Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstartup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session 
/etc/X11/xdm/Xsession
  resize called 3840 1200
  resize called 1920 1200
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] EQ overflow continuing.  200 events have been dropped.

  My system info:

   ~ % uname -a
  Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
   ~ % cat /etc/debian_version
  stretch/sid

   ~ % lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  Codename: xenial
   ~ %
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'

[Touch-packages] [Bug 1475223] Re: Crash during Clock application start on Desktop

2016-07-29 Thread Marcus Endberg

@Bartosz

Thank you for the hint, I'll do so.

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

Title:
  Crash during Clock application start on Desktop

Status in Ubuntu Clock App:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Statistically once per 8 Clock runs, the application is crashing with
  following BackTrace:

  #0  0x754539fc in g_type_check_instance 
(type_instance=type_instance@entry=0xf1a0b0) at 
/build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136
  #1  0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, 
signal_id=289, detail=0, var_args=var_args@entry=0x7fffd250)
  at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090
  #2  0x7544a8ff in g_signal_emit (instance=, 
signal_id=, detail=) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
  #3  0x7fffbe19e271 in  () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0
  #4  0x7fffdfb0ef3c in marshal_dbus_message_to_g_marshaller 
(closure=0x1520db0, return_value=0x0, n_param_values=, 
param_values=, invocation_hint=0x7fffd530, marshal_data=0x0) 
at dbus-gproxy.c:1736
  #8  0x7544a8ff in  (instance=instance@entry=0xf0f780, 
signal_id=, detail=) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
  #5  0x754302d5 in g_closure_invoke (closure=0x1520db0, 
return_value=0x0, n_param_values=3, param_values=0x7fffd590, 
invocation_hint=0x7fffd530)
  at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768
  #6  0x7544203c in signal_emit_unlocked_R 
(node=node@entry=0x151e740, detail=detail@entry=1533, 
instance=instance@entry=0xf0f780, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd590) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549
  #7  0x7544a698 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffd740)
  at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305
  #9  0x7fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, 
proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789
  #10 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (connection=, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356
  #11 0x7fffec3e21d1 in dbus_connection_dispatch () at 
/lib/x86_64-linux-gnu/libdbus-1.so.3
  #12 0x7fffdfb095d5 in message_queue_dispatch (source=, 
callback=, user_data=) at dbus-gmain.c:90
  #13 0x7515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122
  #14 0x7515ac3d in g_main_context_dispatch 
(context=context@entry=0x7fffe40016f0) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737
  #15 0x7515af20 in g_main_context_iterate 
(context=context@entry=0x7fffe40016f0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=)
  at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808
  ---Type  to continue, or q  to quit---
  #16 0x7515afcc in g_main_context_iteration (context=0x7fffe40016f0, 
may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869
  #17 0x767bcc57 in 
QEventDispatcherGlib::processEvents(QFlags) () 
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #18 0x767613e2 in 
QEventLoop::exec(QFlags) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #19 0x7676902c in QCoreApplication::exec() () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #20 0x00404098 in  ()
  #21 0x75ac1a40 in __libc_start_main (main=
  0x4037d0, argc=4, argv=0x7fffdf38, init=, 
fini=, rtld_fini=, stack_end=0x7fffdf28) at 
libc-start.c:289
  #22 0x004058b9 in  ()

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

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

[Touch-packages] [Bug 1606835] Re: Wrong usage of map{To, From}Item

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

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

Title:
  Wrong usage of map{To,From}Item

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Logs from yakkety-proposed autopkgtests failures:

  amd64
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/u/unity8/20160727_034401@/log.gz

  i386
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/u/unity8/20160726_220251@/log.gz

  ---
  FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 0) Uncaught 
exception: Type error
  FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 1) Uncaught 
exception: Type error
  FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 2) Uncaught 
exception: Type error
  FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 3) Uncaught 
exception: Type error
  FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 4) Uncaught 
exception: Type error
  FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 5) Uncaught 
exception: Type error
  ---
  FAIL!  : qmltestrunner::Launcher::test_quicklist_positioning(top) 'verify()' 
returned FALSE. ()
  FAIL!  : qmltestrunner::Launcher::test_quicklist_positioning(bottom) 
'verify()' returned FALSE. ()
  ---

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

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

[Touch-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

2016-07-29 Thread Pat McGowan

How is you access point configured?

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

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

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

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

[Touch-packages] [Bug 1607390] Re: serious bug on bluetooth (Ubuntu 16.04 LTS)

2016-07-29 Thread Mohamed

** Summary changed:

- serious bug on bluetooth (only Ubuntu 16.04 LTS)
+ serious bug on bluetooth (Ubuntu 16.04 LTS)

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

Title:
  serious bug on bluetooth (Ubuntu 16.04 LTS)

Status in bluez package in Ubuntu:
  New

Bug description:
  I've recently installed ubuntu 16.04 LTS twice -and i discovered that
  the problem was from the tool katoolin so i didn't install it- after i
  installed ubuntu the bluetooth didn't work for me.

  P.S:the bluetooth was working when my laptop was ubuntu 15.04

  when i turn bluetooth on to connect my mouse the switch was on but it
  said that

  Bluetooth is disabled

  i entered the command

  sudo rfkill unblock bluetooth

  it worked but didn't connect to the mouse even after the next restart
  i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock 
bluetooth before last line and restarting)

  and i've tried **sudo hciconfig hci0 reset** with output

  > Can't init device hci0: Connection timed out (110)

  my lsusb; rfkill list output:

  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  0: asus-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
   1: asus-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
   11: hci0: Bluetooth
    Soft blocked: no
   Hard blocked: no

  and output of **dmesg | grep -Ei 'ath3k|blue'**

  [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   34.157120] Bluetooth: Core ver 2.21
  [   34.157135] Bluetooth: HCI device and connection manager initialized
  [   34.157138] Bluetooth: HCI socket layer initialized
  [   34.157140] Bluetooth: L2CAP socket layer initialized
  [   34.157145] Bluetooth: SCO socket layer initialized
  [   35.604410] usbcore: registered new interface driver ath3k
  [   51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   53.810045] Bluetooth: hci0 command 0x0c25 tx timeout
  [   55.814079] Bluetooth: hci0 command 0x0c38 tx timeout
  [   57.818111] Bluetooth: hci0 command 0x0c39 tx timeout
  [   59.822149] Bluetooth: hci0 command 0x0c05 tx timeout
  [   66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   66.997552] Bluetooth: BNEP filters: protocol multicast
  [   66.997556] Bluetooth: BNEP socket layer initialized
  [  195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  195.328480] Bluetooth: RFCOMM TTY layer initialized
  [  195.328488] Bluetooth: RFCOMM socket layer initialized
  [  195.328495] Bluetooth: RFCOMM ver 1.11
  [  199.131870] Bluetooth: hci0 command 0x1009 tx timeout
  [  276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  294.258992] Bluetooth: hci0 command 0x1005 tx timeout
  [  296.263065] Bluetooth: hci0 command 0x0c23 tx timeout
  [  298.267076] Bluetooth: hci0 command 0x0c14 tx timeout
  [  306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  346.417970] Bluetooth: hci0 command 0x0c56 tx timeout
  [  348.421916] Bluetooth: hci0 command 0x0c45 tx timeout
  [  350.425782] Bluetooth: hci0 command 0x0c58 tx timeout
  [  352.429744] Bluetooth: hci0 command 0x1004 tx timeout
  [  366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  368.145218] Bluetooth: hci0 command 0x1001 tx timeout
  [  370.149130] Bluetooth: hci0 command 0x1009 tx timeout
  [  410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  421.612041] Bluetooth: hci0 command 0x0c23 tx timeout
  [  423.616060] Bluetooth: hci0 command 0x0c14 tx timeout
  [  425.620018] Bluetooth: hci0 command 0x0c25 tx timeout
  [  427.623984] Bluetooth: hci0 command 0x0c38 tx timeout
  [  442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  444.727752] Bluetooth: hci0 command 0x0c52 tx timeout
  [  446.731800] Bluetooth: hci0 command 0x0c45 tx timeout
  [  448.735743] Bluetooth: hci0 command 0x0c58 tx timeout
  [  450.739762] Bluetooth: hci0 command 0x1004 tx timeout
  [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller
  [ 4011.801141] Bluetooth: hci0 command 0x2002 tx timeout
  [ 4013.805106]

[Touch-packages] [Bug 1607686] Re: testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1

2016-07-29 Thread Daniel d'Andrada

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  testWizard and testShellWithPin crashes on yakkety-proposed with Qt
  5.6.1

Status in qtdeclarative-opensource-src package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In yakkety-proposed two tests are crashing reliably:

  testWizard
  testShellWithPin

  The trace for both is quite similar:

  [testWizard]
  #0  0x73b159b4 in QQuickItem::window (this=0x56249c40) at 
items/qquickitem.cpp:2837
  No locals.
  #1  0x7fffddeb58db in TouchEventSequenceWrapper::commit 
(this=0x557623d0, processEvents=true)
  at 
/home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:30
  No locals.
  #2  0x7fffddeb9e8b in TouchEventSequenceWrapper::qt_static_metacall 
(_o=0x557623d0, 
  _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90
  _t = 0x557623d0
  #3  0x7fffddeba046 in TouchEventSequenceWrapper::qt_metacall 
(this=0x557623d0, 
  _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126
  No locals.
  [...]

  
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickitem.cpp?h=5.6.1#n2834

  [testShellWithPin]
  #0  QQuickWindowPrivate::flushDelayedTouchEvent (this=0x385586ff) at 
items/qquickwindow.cpp:1964
  No locals.
  #1  0x7fffdd15790d in TouchEventSequenceWrapper::commit 
(this=0x570f9310, processEvents=true) at 
/home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:32
  wp = 0x385586ff
  #2  0x7fffdd15be8b in TouchEventSequenceWrapper::qt_static_metacall 
(_o=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90
  _t = 0x570f9310
  #3  0x7fffdd15c046 in TouchEventSequenceWrapper::qt_metacall 
(this=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, 
_a=0x7fff7040)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126
  No locals.
  [...]

  
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickwindow.cpp?h=5.6.1#n1962

  
  Looks to me like Qt-internal issue potentially.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 (not installed)
  ProcVersionSignature: User Name 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.3-0ubuntu1
  Architecture: amd64
  Date: Fri Jul 29 08:21:31 2016
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1607686] Re: testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1

** Branch linked: lp:~dandrader/unity8/testFailuresYakkety

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

Title:
  testWizard and testShellWithPin crashes on yakkety-proposed with Qt
  5.6.1

Status in qtdeclarative-opensource-src package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In yakkety-proposed two tests are crashing reliably:

  testWizard
  testShellWithPin

  The trace for both is quite similar:

  [testWizard]
  #0  0x73b159b4 in QQuickItem::window (this=0x56249c40) at 
items/qquickitem.cpp:2837
  No locals.
  #1  0x7fffddeb58db in TouchEventSequenceWrapper::commit 
(this=0x557623d0, processEvents=true)
  at 
/home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:30
  No locals.
  #2  0x7fffddeb9e8b in TouchEventSequenceWrapper::qt_static_metacall 
(_o=0x557623d0, 
  _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90
  _t = 0x557623d0
  #3  0x7fffddeba046 in TouchEventSequenceWrapper::qt_metacall 
(this=0x557623d0, 
  _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126
  No locals.
  [...]

  
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickitem.cpp?h=5.6.1#n2834

  [testShellWithPin]
  #0  QQuickWindowPrivate::flushDelayedTouchEvent (this=0x385586ff) at 
items/qquickwindow.cpp:1964
  No locals.
  #1  0x7fffdd15790d in TouchEventSequenceWrapper::commit 
(this=0x570f9310, processEvents=true) at 
/home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:32
  wp = 0x385586ff
  #2  0x7fffdd15be8b in TouchEventSequenceWrapper::qt_static_metacall 
(_o=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90
  _t = 0x570f9310
  #3  0x7fffdd15c046 in TouchEventSequenceWrapper::qt_metacall 
(this=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, 
_a=0x7fff7040)
  at 
/home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126
  No locals.
  [...]

  
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickwindow.cpp?h=5.6.1#n1962

  
  Looks to me like Qt-internal issue potentially.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 (not installed)
  ProcVersionSignature: User Name 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.3-0ubuntu1
  Architecture: amd64
  Date: Fri Jul 29 08:21:31 2016
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1573773] Re: System freezes randomly a few times a day

I updated the BIOS and still the same result.
I also tried using ppa ppa:oibaf/graphics-drivers
.
But, still the same.
Finally, I switched to nvidia-367 drivers and it works without crashing
(though not everything works -
 gdm does not work with nvidia drivers - only xdm
)
.
Anyway, I don't like proprietory stuff and would really love to have
nouveau drivers work
.

On Tue, Jul 26, 2016 at 10:57 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, as per
> https://www.asus.com/Motherboards/Z97K/HelpDesk_Download/ an update to
> your computer's buggy, insecure, and outdated BIOS is available (2902).
> When you update to this following
> https://help.ubuntu.com/community/BIOSUpdate how does this improve the
> situation?
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful.
>
> Also, you don't have to create a new bug report.
>
> Once the BIOS is updated, if the problem is still reproducible:
> 1) Please provide the output of the following terminal command (not
> perform an apport-collect):
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
> 2) Please make a comment specifically advising on what improved.
> 3) Please mark this report Status New.
>
> If it's not reproducible, please mark this as Invalid.
>
> Thank you for your help.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9:

Re: [Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

2016-07-29 Thread jordibardaji

OK. Thanks a lot!!! @Michael Zanetti.

I hope OTA-13 will be released soon!!


2016-07-29 17:57 GMT+02:00 Michael Zanetti
:

> I have just switched my tablet to spanish. @ works fine there. Note that
> there is a separate issue which affects only the Browser and the
> Terminal and it is tracked here:
> https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1590515
>
> This issue is already fixed, but sadly did not make it into OTA-12. It
> will land in rc-proposed soon and be included in OTA-13.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1565236
>
> Title:
>   AltGr not working on external keyboards
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions
>


-- 
Jordi
http://www.elmarathon.com

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

-- 
Mailing list: https://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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-07-29 Thread Marco Graziotti

Hi Konrad,

I tryed to pair again the phone with my car, but it don't work. The car 
say "Pairing failed".
After this, to remove the device, I needed to use the terminal again.

To resolve, I need to wait for OTA-13, or I need instruction for 
installing the new bluez silo.

Thank you,
Marco


Il 29/07/2016 12:43, Konrad Zapałowicz ha scritto:
> Marco,
>
> this is super strange, I will think of possible solutions however in 
> the meantime what is the output from
>
> info 60:38:0E:59:32:39
>
> Thanks,
> K
>
> On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti 
> > wrote:
>
> Hi Konrad,
>
> I tried to remove the "Nissan Connect" device, but i got this
> error: "*Failed to remove device: org.bluez.Error.NotReady*".
> Here you can read what I'm doing:
>
> *user@user-laptop:~$ adb shell*
> * daemon not running. starting it now on port 5037 *
> * daemon started successfully *
>
> phablet@ubuntu-phablet:~$ $ bluetoothctl
> bash: $: command not found
>
> *phablet@ubuntu-phablet:~$ bluetoothctl*
> [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default]
> [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar
> [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT
>
> *[bluetooth]# devices*
> Device 90:F1:AA:7B:80:0F [Samsung] Soundbar
> Device 60:38:0E:59:32:39 NISSAN CONNECT
>
> *[bluetooth]# remove 60:38:0E:59:32:39**
> **Failed to remove device: org.bluez.Error.NotReady*
>
> What can I do?
>
> Thank you
>
>
> Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto:
>> Hey,
>>
>> I'll try to help a bit here.
>>
>> First as for the unknown or unwanted entries on the paired devices lists
>> [and such] you can try to remove them from the bluetoothctl level.
>>
>> ) enable developers mode & connect it via usb cable
>> ) login with adb shell to the deivce
>> ) type $ bluetoothctl
>> ) then type: devices - to list the known devices
>> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address 
>> of the device [not it's name]
>>
>> Second we are in the of releasing the newest bluez 5.41 which is now in
>> silo 37. If you are familiar with installing silos on your device you
>> can try it out and check if it improves anything. It includes fixes for
>> link management and pairing therefore there is a chance [although not
>> certain] that there might be joy.
>>
>> If unsure please ask.
>>
>> Best,
>> Konrad
>>
>
>

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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

[Touch-packages] [Bug 1593048] Re: ubuntu-themes should support GTK 3.20

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
yakkety-landing-014

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

Title:
  ubuntu-themes should support GTK 3.20

Status in arc-theme package in Ubuntu:
  Triaged
Status in breeze-gtk package in Ubuntu:
  Triaged
Status in mate-themes package in Ubuntu:
  Triaged
Status in ubuntu-mate-artwork package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  This is a tracking bug. ubuntu-themes needs to be updated to support
  GTK+ 3.20 before GTK+ 3.20 can land in Ubuntu.

  Some initial work has been done at
  https://code.launchpad.net/~laney/ubuntu-themes/gtk320

  If you would like to help, please contact the Ubuntu Desktop Team.

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

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

[Touch-packages] [Bug 1607845] [NEW] List of versioned kernels is not right for Ubuntu

2016-07-29 Thread Jarno Suni

Public bug reported:

The following command outputs the list:
$ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
linux-image
linux-headers
linux-image-extra
linux-signed-image
kfreebsd-image
kfreebsd-headers
gnumach-image
.*-modules
.*-kernel
linux-backports-modules-.*
linux-tools

but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
headers', which are versioned kernel packages as well, if I have
understood correctly.

On the other hand are these values appropriate for Ubuntu?
kfreebsd-image
kfreebsd-headers
gnumach-image
.*-modules
.*-kernel

Same thing for Ubuntu 14.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jul 29 18:55:50 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-21 (250 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: apt
UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  New

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

2016-07-29 Thread Michael Zanetti

I have just switched my tablet to spanish. @ works fine there. Note that
there is a separate issue which affects only the Browser and the
Terminal and it is tracked here:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1590515

This issue is already fixed, but sadly did not make it into OTA-12. It
will land in rc-proposed soon and be included in OTA-13.

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1590944] Re: Disconnecting aethercast doesn't set display mode to staged

2016-07-29 Thread Michał Sawicz

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

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Disconnecting aethercast doesn't set display mode to staged

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

Bug description:
  Phone: Meizu Pro 5 with OTA-11
  External Display: Panasonic TX-P50-GW30 TV with 
  Microsoft Wireless Display Adapter V2, Firmware 2.0.8350

  HID: KeySonic KSK-3023BT(DE) BT Keyboard + hama M2140 BT Mouse, both
  connected before using aethercast (staged mode).

  When connecting the Pro5 via aethercast to MS Wireless Display
  Adapter, the TV-Display changes to window-mode. BT HID are connected.
  After disconnecting from external TV-Display, the Pro5-Display doesn't
  return into staged mode by itself. I have to disconnect BT HID Devices
  to get staged mode.

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

-- 
Mailing list: https://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 1565236] Re: AltGr not working on external keyboards

2016-07-29 Thread jordibardaji

@Michael Zanetti

Spanish is the layout I'm using.  I live in Spain,

The most important characters I need are those: á é í ó ú à è ò ü ï @

Obviously I'm writing this message from ubuntu 16.04 PC. This is impossible
to write those characters in Tablet M10 ubuntu edition or BQ aquaris E4.5.
Both on OTA-12 with external bluetooth keyboard.


I tried in default navigator: "@" nor á é í ó ú, . Its don't work.
Libreoffice has dissapeard when I update to OTA 12 in M10 ubuntu tablet!!!


Thanks for your interest,

Jordi


2016-07-29 17:05 GMT+02:00 Michael Zanetti :

> @jordibardaji, what layout are you using, what characters are you trying
> to type?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1565236
>
> Title:
>   AltGr not working on external keyboards
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions
>


-- 
Jordi
http://www.elmarathon.com

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel 
wrote:

> It would be a good idea to let the
> upstream devs know that. xorg/driver/xf86-video-r128 is actively
> maintained and still receives patches (last one 8 days ago). You could
> file a bug against upstream:
> https://bugs.freedesktop.org/buglist.cgi?quicksearch=r128 Just be sure
> to have a complete Xorg.log ready to post this bug upstream and state
> that it happens on an Apple PowerMac 3,1.
>

I added my comments/issues to this bugzilla bug:

94916 - X doesn't start with r128 driver (ATI RAGE) [powerpc]
https://bugs.freedesktop.org/show_bug.cgi?id=94916

** Bug watch added: freedesktop.org Bugzilla #94916
   https://bugs.freedesktop.org/show_bug.cgi?id=94916

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1590944] Re: Disconnecting aethercast doesn't set display mode to staged

** Branch linked: lp:~mzanetti/unity8/fix-usage-mode-switch

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

Title:
  Disconnecting aethercast doesn't set display mode to staged

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

Bug description:
  Phone: Meizu Pro 5 with OTA-11
  External Display: Panasonic TX-P50-GW30 TV with 
  Microsoft Wireless Display Adapter V2, Firmware 2.0.8350

  HID: KeySonic KSK-3023BT(DE) BT Keyboard + hama M2140 BT Mouse, both
  connected before using aethercast (staged mode).

  When connecting the Pro5 via aethercast to MS Wireless Display
  Adapter, the TV-Display changes to window-mode. BT HID are connected.
  After disconnecting from external TV-Display, the Pro5-Display doesn't
  return into staged mode by itself. I have to disconnect BT HID Devices
  to get staged mode.

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

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

[Touch-packages] [Bug 1590944] Re: Disconnecting aethercast doesn't set display mode to staged

2016-07-29 Thread Michael Zanetti

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

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

Title:
  Disconnecting aethercast doesn't set display mode to staged

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

Bug description:
  Phone: Meizu Pro 5 with OTA-11
  External Display: Panasonic TX-P50-GW30 TV with 
  Microsoft Wireless Display Adapter V2, Firmware 2.0.8350

  HID: KeySonic KSK-3023BT(DE) BT Keyboard + hama M2140 BT Mouse, both
  connected before using aethercast (staged mode).

  When connecting the Pro5 via aethercast to MS Wireless Display
  Adapter, the TV-Display changes to window-mode. BT HID are connected.
  After disconnecting from external TV-Display, the Pro5-Display doesn't
  return into staged mode by itself. I have to disconnect BT HID Devices
  to get staged mode.

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

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

[Touch-packages] [Bug 1579551] Re: Most scopes are missing (no Apps scope etc)

This bug was fixed in the package unity8-desktop-session -
1.0.13+16.10.20160726.1-0ubuntu1

---
unity8-desktop-session (1.0.13+16.10.20160726.1-0ubuntu1) yakkety; 
urgency=medium

  [ Chris Townsend ]
  * Reduce the priority of the Unity 8 session so it is will not appear
as the default in Ubuntu 16.10. (LP: #1603102)

  [ Stephen M. Webb ]
  * load /etc/profile.d in Unity 8 desktop session (LP: #1590439,
#1606246)
  * recommend additional packages to be co-installed with the Unity 8
Desktop Session (LP: #1579551, #1591366, #1591394)

 -- stephen.w...@canonical.com (Stephen M. Webb)  Tue, 26 Jul 2016
13:32:01 +

** Changed in: unity8-desktop-session (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Most scopes are missing (no Apps scope etc)

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have installed Unity8 on my 16.04 laptop, not a fresh install.

  The session starts fine and the scopes window shows, but it's empty.
  Using the bottom edge button I can see that most scopes are not
  installed, including the App scope (but also Today, Nearby, Ubuntu
  Store, etc). There are about 10 scopes installed, things like Amazon
  or Wikipedia, and those do work.

  There are a few apps in the launcher, but I'm also affected by bug
  #1535058, meaning I can't launch anything.

  Let me know what kind of info I can provide and where to find it!

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

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

[Touch-packages] [Bug 1607079] Re: Cellular Option immediately crashes [OTA-12]

2016-07-29 Thread Antti Kaijanmäki

This is clearly a crash of i-network. I will address this ASAP.

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: indicator-network (Ubuntu)
   Status: Won't Fix => In Progress

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

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

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

Title:
  Cellular Option immediately crashes [OTA-12]

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  After upgrading to OTA-12 today, everything seemed to work perfectly.
  But after rebooting the first time, I was not asked for a SIM PIN
  number. I had to deactivate/activate the SIM card so I could use the
  phone again.

  Due to the fact that the indicator-network is empty, I tried to
  activate the 3G connection by using the cellular option in the system
  settings.

  The cellular data option immediately crashes when selecting it.

  Edit:
  After rebooting a few times and deactivate/activate the SIM card again I 
could use this option. But I cannot activate/deactivate the cellular data 
option. My carrier is shown correctly.

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

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

[Touch-packages] [Bug 1607079] Re: Cellular Option immediately crashes [OTA-12]

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

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

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

Title:
  Cellular Option immediately crashes [OTA-12]

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  After upgrading to OTA-12 today, everything seemed to work perfectly.
  But after rebooting the first time, I was not asked for a SIM PIN
  number. I had to deactivate/activate the SIM card so I could use the
  phone again.

  Due to the fact that the indicator-network is empty, I tried to
  activate the 3G connection by using the cellular option in the system
  settings.

  The cellular data option immediately crashes when selecting it.

  Edit:
  After rebooting a few times and deactivate/activate the SIM card again I 
could use this option. But I cannot activate/deactivate the cellular data 
option. My carrier is shown correctly.

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

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

[Touch-packages] [Bug 1601976] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:11:nmofono::wwan::Sim::initialDataOn:nmofono::ManagerImpl::Private::modemReady:QtPrivate::QS

2016-07-29 Thread Antti Kaijanmäki

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

** This bug has been marked a duplicate of bug 1607079
   Cellular Option immediately crashes [OTA-12]

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-
  
service:11:nmofono::wwan::Sim::initialDataOn:nmofono::ManagerImpl::Private::modemReady:QtPrivate::QSlotObjectBase::call:QMetaObject::activate:QMetaObject::activate

Status in indicator-network package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1607079] Re: Cellular Option immediately crashes [OTA-12]