[Touch-packages] [Bug 1547510] Re: tracker for xorg-server 1.18 migration

[Timo Aaltonen]

and these drivers can be removed from the archive then:

https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-
updates/+bug/1541369

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

Title:
  tracker for xorg-server 1.18 migration

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  While testing new X I noticed that display scaling didn't work, and it
  was due to new randr-1.5 code. The GDK backend is buggy, running

  python -c 'from gi.repository import Gdk; 
 print(Gdk.Screen.get_default().get_monitor_plug_name(0))'

  returns "None"

  this is a blocker for the xserver update.

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

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

[Touch-packages] [Bug 1503465] Re: Update to 0.2.16

[Bug Watch Updater]

** Changed in: grilo-plugins (Debian)
   Status: New => Fix Released

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

Title:
  Update to 0.2.16

Status in grilo-plugins package in Ubuntu:
  Triaged
Status in grilo-plugins package in Debian:
  Fix Released

Bug description:
  Requires lua5.3 and gnome-online-accounts 3.17.91

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

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

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

[Dmitry Shachnev]

@Ross: The difference between Debian and Xubuntu is that the latter has
an indicators-based tray, so Qt tries to use that too.

Anyway, have you tested if the bug still occurs with the latest qtbase
upload? If that is the case, I will try to look at it.

As a temporary workaround, try installing appmenu-qt5 package (after
logout/login the bug should be gone).

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

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

Title:
  Systray option does not work.

Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Daniel van Vugt]

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

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

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Mir:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  New

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

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

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

[Touch-packages] [Bug 905682] Re: [Realtek ALC887-VD, Green Line Out, Rear] No sound at all

[suntek]

Thanks bug-fixed already..more power!

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

Title:
  [Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  i dont get any sound at all,
  will try compiling alsa from scratch next.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drunkeneye   2027 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb0 irq 16'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,10438445,00100302'
 Controls  : 34
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfea3 irq 54'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Sat Dec 17 13:42:54 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Internal Audio - HD-Audio Generic
  Symptom_DevicesInUse: 2027  1648
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A75-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd11/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 905682] Re: [Realtek ALC887-VD, Green Line Out, Rear] No sound at all

[suntek]

please if you could help fix the audio problem after updated to
15.10..thanks!

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

Title:
  [Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  i dont get any sound at all,
  will try compiling alsa from scratch next.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drunkeneye   2027 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb0 irq 16'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,10438445,00100302'
 Controls  : 34
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfea3 irq 54'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Sat Dec 17 13:42:54 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Internal Audio - HD-Audio Generic
  Symptom_DevicesInUse: 2027  1648
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A75-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd11/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Simon Fels]

Generally I don't think this is because of a lacking key event. If the
keyboard goes away also its corresponding input device node will
disappear. If that happens the upper input stack should take care about
that. Adding mir as component here too to get their view on this while
doing some more investigation.

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

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

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  New

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

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

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Simon Fels]

Got this reproduced after following the steps to turn off the keyboard
while holding a key.

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

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

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

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

[Touch-packages] [Bug 1541210] Re: Photos are displayed as 90 degree rotated in photo roll

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Photos are displayed as 90 degree rotated in photo roll

Status in Canonical System Image:
  Fix Committed
Status in camera-app package in Ubuntu:
  Fix Committed
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  On some devices where the camera is such that the Orientation exif
  data gets written  "Orientation |Right-top", as on Turbo.

  The camera app has problems showing the photo in the photo roll. Gallery also 
has this problem. Other apps will show it normally.
  The camera app view finder shows it as it should.

  When taking photo is portrait mode, the photo roll shows it rotated
  wrong.

  When taking photo in landscape mode, the photo roll shows it properly.

  The "My Photos" scope shows both portrait and landscape taken photos
  properly.

  ---

  This also affects photos transferred from elsewhere to the phone and
  viewed in Gallery.

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

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

[Touch-packages] [Bug 1523574] Re: Support video export from content-hub

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Support video export from content-hub

Status in Canonical System Image:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  the latest messaging-app will allow attaching videos to messages (use
  silo 52 to test). The following needs to be done on camera-app for
  Videos (it already does this correctly for Images)

  1) expose exporting Videos via content-hub
  2) when in picking mode for Videos, user should be able to take a new video 
from the camera or pick one from Photo Roll (same as we do for Images - just 
need the equivalent for videos)
  3) main picking UI from viewfinder should be similar to for Images, but only 
allow taking videos

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

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

[Touch-packages] [Bug 1390423] Re: Actually detect flash support for active camera

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Fix Released

** No longer affects: camera-app

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

Title:
  Actually detect flash support for active camera

Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  Most front cameras on phones do not have a flash, so naturally the
  control for this in the sub-controls doesn't work. However there is
  nothing to visually distinguish this from the other controls (Location
  and HDR) that do work, so it's slightly confusing from a users
  perspective. This control should be removed, or at least be dependent
  on the presence of a flash for the front camera

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

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

[Touch-packages] [Bug 1323373] Re: Strings missing proper plural formatting in camera app

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Strings missing proper plural formatting in camera app

Status in camera-app:
  Fix Committed
Status in Canonical System Image:
  Fix Released
Status in Ubuntu Translations:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  The following strings in https://translations.launchpad.net/camera-
  app/trunk/+pots/camera-app are not coming up with the proper number of
  plurals offered for each locale (e.g for our locale I should be
  offered 4 translatable strings as we have 4 plural forms). As plurals
  are normally presented correctly, these must have been prepped wrongly
  I'm guessing:

  %1 photos taken today
  Located in camera-app.qml:370 

  No photos taken today
  Located in camera-app.qml:371 

  %1 videos recorded today
  Located in camera-app.qml:379 

  No videos recorded today
  Located in camera-app.qml:380

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

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

[Touch-packages] [Bug 1546265] Re: While photo roll hint is visible record button is still available

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  While photo roll hint is visible record button is still available

Status in camera-app package in Ubuntu:
  Fix Committed

Bug description:
  At first time camera-app is used a hint is displayed showing how to
  get the photo roll view after the first photo/video is taken. While
  this hint is visible the record/shutter button is still available (but
  not visible) It it is clicked new photos are taken or a new recording
  starts.

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

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

[Touch-packages] [Bug 1540876] Re: Not all results recieved when there is a lot of them (>=3000?)

[Michi Henning]

** Changed in: unity-scopes-api (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Not all results recieved when there is a lot of them (>=3000?)

Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  It looks like ZMQ high water-mark limits the number of results that
  can succesfuly be received by a client to something around 2000; this
  may depend on the result size and delays between pushes though. With
  3000 results in my test code I was receiving approximately 1900, the
  remainder was dropped on the floor. While these numbers are probably
  more than we will ever need, it may be worth looking into it. Perhaps
  ZMQ queue size can be increased, also a meaningful error in the logs
  about hitting such cases would be nice (if possible at all).

  I'll add a pointer to a sample test case from unity-scopes-shell at a
  later time, please contact me if I forget to do so ;)

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

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

[Touch-packages] [Bug 1438935] Re: ? just got the something wrong procedure

[Rolf Leggewie]

** Tags added: trusty

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

Title:
  ? just got the something wrong procedure

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  no forther information at hand

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 15.04
  Package: upstart 1.13.2-0ubuntu10
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic i686
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  Date: Wed Apr  1 00:13:26 2015
  DuplicateSignature: indicator-session-unknown-user-error
  ExecutablePath: /sbin/upstart
  InstallationDate: Installed on 2015-03-31 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326)
  ProcCmdline: upstart --user --startup-event indicator-services-start
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 2
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist
  UserGroups:
   
  icon_file: (null)
  is_current_user: false
  is_logged_in: false
  real_name: (null)
  uid: 0
  user_name: (null)

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

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

[Touch-packages] [Bug 1523573] Re: Doesn't let you share several images

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.04.20160224-0ubuntu1

---
messaging-app (0.1+16.04.20160224-0ubuntu1) xenial; urgency=medium

  * Enable receiving multiple files from content-hub. (LP: #1523573)
  * Makes text in the swipe demo use relative positioning instead of
absolute. (LP: #1518344)
  * Remove all line breaks from the text message preview and set a
maximum line count, so the Text component correctly respect the
elide property. (LP: #1532895)
  * Set width based on the screen size to avoid removing views from the
stack when the app is resized. (LP: #1549352)

 -- Tiago Salem Herrmann   Wed, 24 Feb
2016 18:29:28 +

** Changed in: messaging-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  In Progress
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

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

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

[Touch-packages] [Bug 1518344] Re: "Swipe to reveal actions" label needs more space.

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.04.20160224-0ubuntu1

---
messaging-app (0.1+16.04.20160224-0ubuntu1) xenial; urgency=medium

  * Enable receiving multiple files from content-hub. (LP: #1523573)
  * Makes text in the swipe demo use relative positioning instead of
absolute. (LP: #1518344)
  * Remove all line breaks from the text message preview and set a
maximum line count, so the Text component correctly respect the
elide property. (LP: #1532895)
  * Set width based on the screen size to avoid removing views from the
stack when the app is resized. (LP: #1549352)

 -- Tiago Salem Herrmann   Wed, 24 Feb
2016 18:29:28 +

** Changed in: messaging-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  "Swipe to reveal actions" label needs more space.

Status in Canonical System Image:
  In Progress
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  Hi!

  I translated the following string to Hungarian:

  "Swipe to reveal actions"

  But it needs more space (see attached screenshot). Additional info: In
  the Phone app the same translation looks okay.

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

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

[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases

[Rob Whyte]

I too have struggled with this on my server, leaving us without internet
until sudo dhclient eth0 or the interace is taken down and brought back
up.

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

Title:
  dhclient does not renew leases

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Release: Xenial

  I think this only recently started after some bind9 updates triggered a 
rebuild. When booting dhclient gets started and acquires an IP address, but it 
does seem to lock up somewhere as it does not renew the lease.
  In my environment I set the lease time to 5 minutes, so I notice such things 
rather soon. I looked on the dhcp server side but saw any further dhcp messages 
come in from the client side.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Feb 29 12:32:52 2016
  DhclientLeases:
   
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1532895] Re: Messages with a trailing CR are not displayed properly in the main list

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.04.20160224-0ubuntu1

---
messaging-app (0.1+16.04.20160224-0ubuntu1) xenial; urgency=medium

  * Enable receiving multiple files from content-hub. (LP: #1523573)
  * Makes text in the swipe demo use relative positioning instead of
absolute. (LP: #1518344)
  * Remove all line breaks from the text message preview and set a
maximum line count, so the Text component correctly respect the
elide property. (LP: #1532895)
  * Set width based on the screen size to avoid removing views from the
stack when the app is resized. (LP: #1549352)

 -- Tiago Salem Herrmann   Wed, 24 Feb
2016 18:29:28 +

** Changed in: messaging-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Messages with a trailing CR are not displayed properly in the main
  list

Status in Canonical System Image:
  In Progress
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Normally a long message is truncated and "..." is shown to indicate its 
longer than the box.
  When the message ends with a CR it is not truncated and the text extends to 
the end f the screen, and is shown underneath the new message count.

  Not reproducible on krillin, only arale

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

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

[Touch-packages] [Bug 1549352] Re: New message to contact only opens messaging app

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.04.20160224-0ubuntu1

---
messaging-app (0.1+16.04.20160224-0ubuntu1) xenial; urgency=medium

  * Enable receiving multiple files from content-hub. (LP: #1523573)
  * Makes text in the swipe demo use relative positioning instead of
absolute. (LP: #1518344)
  * Remove all line breaks from the text message preview and set a
maximum line count, so the Text component correctly respect the
elide property. (LP: #1532895)
  * Set width based on the screen size to avoid removing views from the
stack when the app is resized. (LP: #1549352)

 -- Tiago Salem Herrmann   Wed, 24 Feb
2016 18:29:28 +

** Changed in: messaging-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  New message to contact only opens messaging app

Status in Canonical System Image:
  In Progress
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  Test case.
  - Open Contacts app.
  - Add a new contact with a phone number.
  - Save the contact.
  - On the contact list, tap on the contact.
  - Tap on the messaging button to send a message to the contact.

  Expected result.
  - Messaging app is opened but the message list is displayed, instead of the 
screen to write the message to the contact.

  Through Dialer app, the message creation screen is opened correctly.

  current build number: 266
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

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

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

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

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1551553

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

Status in systemd package in Ubuntu:
  New

Bug description:
  does not install completely problem with freedesktop.org

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  AptOrdering:
   udev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb 29 22:55:03 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-17 (12 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  MachineType: PDS Inc. Vision Mi-VI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=121b3ff2-805d-40fe-9f5b-2002e0141a86 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: systemd
  Title: package udev 229-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: i965GMx-IF
  dmi.board.vendor: AOpen
  dmi.board.version: Unknown
  dmi.chassis.asset.tag: 11650
  dmi.chassis.type: 3
  dmi.chassis.vendor: PDS Inc.
  dmi.chassis.version: i965GMx-IF
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/01/2008:svnPDSInc.:pnVisionMi-VI:pvrOEM:rvnAOpen:rni965GMx-IF:rvrUnknown:cvnPDSInc.:ct3:cvri965GMx-IF:
  dmi.product.name: Vision Mi-VI
  dmi.product.version: OEM
  dmi.sys.vendor: PDS Inc.

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

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

[Touch-packages] [Bug 1551553] [NEW] package udev 229-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Bob]

Public bug reported:

does not install completely problem with freedesktop.org

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
AptOrdering:
 udev: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Feb 29 22:55:03 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-02-17 (12 days ago)
InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
MachineType: PDS Inc. Vision Mi-VI
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=121b3ff2-805d-40fe-9f5b-2002e0141a86 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.3
SourcePackage: systemd
Title: package udev 229-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: i965GMx-IF
dmi.board.vendor: AOpen
dmi.board.version: Unknown
dmi.chassis.asset.tag: 11650
dmi.chassis.type: 3
dmi.chassis.vendor: PDS Inc.
dmi.chassis.version: i965GMx-IF
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/01/2008:svnPDSInc.:pnVisionMi-VI:pvrOEM:rvnAOpen:rni965GMx-IF:rvrUnknown:cvnPDSInc.:ct3:cvri965GMx-IF:
dmi.product.name: Vision Mi-VI
dmi.product.version: OEM
dmi.sys.vendor: PDS Inc.

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  does not install completely problem with freedesktop.org

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  AptOrdering:
   udev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb 29 22:55:03 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-17 (12 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  MachineType: PDS Inc. Vision Mi-VI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=121b3ff2-805d-40fe-9f5b-2002e0141a86 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: systemd
  Title: package udev 229-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: i965GMx-IF
  dmi.board.vendor: AOpen
  dmi.board.version: Unknown
  dmi.chassis.asset.tag: 11650
  dmi.chassis.type: 3
  dmi.chassis.vendor: PDS Inc.
  dmi.chassis.version: i965GMx-IF
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/01/2008:svnPDSInc.:pnVisionMi-VI:pvrOEM:rvnAOpen:rni965GMx-IF:rvrUnknown:cvnPDSInc.:ct3:cvri965GMx-IF:
  dmi.product.name: Vision Mi-VI
  dmi.product.version: OEM
  dmi.sys.vendor: PDS Inc.

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

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

[Touch-packages] [Bug 318325] Re: [X1100] flickering after resume from ram

[Tommy Trussell]

I have the same hardware as reported in Bug #1333697

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

Title:
  [X1100] flickering after resume from ram

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-radeon

  System : Ubuntu 8.10 (up to date)
  GPU : ATI express X1100
  Video driver : radeon

  Steps to reproduce :
  - put the computer on standby
  - resume from ram
  => the screen will flicker while CPU activity is not high

  workaround :
  - just launch an infinite loop that consume CPU : $ while true; do echo 
>/dev/null; done
  => the screen won't flicker while the CPU is use (even if only one core is 
being used)

  There isn't error either in Xorg, xsession logs or in dmesg after
  resuming.

  
  Notice that this trouble doesn't occured with fglrx driver.

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

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

[Touch-packages] [Bug 318325] Re: [X1100] flickering after resume from ram

[Christopher M. Penalver]

Tommy Trussell, it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  [X1100] flickering after resume from ram

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-radeon

  System : Ubuntu 8.10 (up to date)
  GPU : ATI express X1100
  Video driver : radeon

  Steps to reproduce :
  - put the computer on standby
  - resume from ram
  => the screen will flicker while CPU activity is not high

  workaround :
  - just launch an infinite loop that consume CPU : $ while true; do echo 
>/dev/null; done
  => the screen won't flicker while the CPU is use (even if only one core is 
being used)

  There isn't error either in Xorg, xsession logs or in dmesg after
  resuming.

  
  Notice that this trouble doesn't occured with fglrx driver.

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

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

[Touch-packages] [Bug 318325] Re: [X1100] flickering after resume from ram

[Tommy Trussell]

I can confirm the bug still exists in Trusty, and I just tried a Wily
live image and it exists there, too. The affected hardware is getting a
bit old but still seems to work fine with Ubuntu in all other ways.

As I am not Id2ndR should I run apport-collect on a new bug and mark it
as a duplicate of this one?

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

Title:
  [X1100] flickering after resume from ram

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-radeon

  System : Ubuntu 8.10 (up to date)
  GPU : ATI express X1100
  Video driver : radeon

  Steps to reproduce :
  - put the computer on standby
  - resume from ram
  => the screen will flicker while CPU activity is not high

  workaround :
  - just launch an infinite loop that consume CPU : $ while true; do echo 
>/dev/null; done
  => the screen won't flicker while the CPU is use (even if only one core is 
being used)

  There isn't error either in Xorg, xsession logs or in dmesg after
  resuming.

  
  Notice that this trouble doesn't occured with fglrx driver.

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

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

[Touch-packages] [Bug 743731] Re: [i915] SEGV in i915_dri.so:translate_program() under wine

[Christopher M. Penalver]

Peter Maydell, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/743731/comments/1
regarding this being fixed with an update. 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: mesa (Ubuntu)
   Status: New => Invalid

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

Title:
  [i915] SEGV in i915_dri.so:translate_program() under wine

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  If you try to run the game Scarlet Weather Rhapsody under Wine on
  Ubuntu natty, it segfaults on startup. This seems to be a bug that's
  fixed in mesa's git repo. This used to work on lucid, but regressed in
  maverick and is still present in natty alpha-3.

  Sorry the how-to-reproduce instructions are a bit convoluted.

  You can take the demo version of the game from
  http://tasofro.net/touhou105/download.html (you want the 83.8MB
  download link), and run under natty's wine:

  LANG=ja_JP.UTF-8 winedbg  ./th105.exe
  Unhandled exception: page fault on read access to 0x0018 in 32-bit code 
(0x677827c7).
  Register dump:
   CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
   EIP:677827c7 ESP:0563e224 EBP:0563e2dc EFLAGS:00210246(  R- --  I  Z- -P- )
   EAX: EBX:677c1ff4 ECX:0008 EDX:677c2580
   ESI:0008 EDI:
  Stack dump:
  0x0563e224:  7c494908 7c7ab520  
  0x0563e234:     
  0x0563e244:     
  0x0563e254:     
  0x0563e264:    7c494908 0003
  0x0563e274:  0005 0001 0002 
  Backtrace:
  =>0 0x677827c7 in i915_dri.so (+0x267c7) (0x0563e2dc)
1 0x67784d07 in i915_dri.so (+0x28d06) (0x0563e2ec)
2 0x4ed391a3 _mesa_GetProgramivARB+0x322() in libdricore.so (0x0563e31c)
3 0x7192073e in wined3d (+0x2073d) (0x0563e4ac)
  [etc]

  Here's a version of the backtrace with debug symbols (you'll notice
  that it's for maverick's mesa 7.9 and a custom wine, but it's the same
  crash, honest):

  =>0 0x2002d52a translate_program+0xba(p=)
  
[/home/pm215/src/mesa-7.9~git20100924/build/dri/src/mesa/drivers/dri/i915/i915_fragprog.c:356]
  in i915_dri.so (0x0605e314)
1 0x2002f9b7 i915IsProgramNative+0x46(ctx=0x7d03b198, target=0x8804, 
prog=0x7d128380)
  
[/home/pm215/src/mesa-7.9~git20100924/build/dri/src/mesa/drivers/dri/i915/i915_fragprog.c:1261]
  in i915_dri.so (0x0605e344)
2 0x20063433 _mesa_GetProgramivARB+0x352(target=0x202f82e0, pname=0x88b6, 
params=0x605e4a4)
  
[/home/pm215/src/mesa-7.9~git20100924/build/dri/src/mesa/main/arbprogram.c:844]
  in i915_dri.so (0x0605e4d4)
3 0x46d7bd2f fragment_prog_arbfp+0x175e(state_id=0x0176, 
stateblock=0x1410e0, context=0x4eaec38)
  [/home/pm215/src/wine-for-touhou.git/dlls/wined3d/arb_program_shader.c:6196]
  in wined3d (0x0605e534)
4 0x46d9a737 context_apply_draw_state+0xb6(context=0x4eaec38, 
device=0x13e050)
  [/home/pm215/src/wine-for-touhou.git/dlls/wined3d/context.c:2201] in wined3d
  (0x0605e7c4)
5 0x46dd6735 drawPrimitive+0x1b4(device=0x13e050, index_count=0x0004, 
StartIdx=0, idxSize=0, idxData=0x0(nil))
  [/home/pm215/src/wine-for-touhou.git/dlls/wined3d/drawprim.c:629] in wined3d
  (0x0605e814)
6 0x46dab286 IWineD3DDeviceImpl_DrawPrimitiveUP+0xc5(iface=0x13e050, 
vertex_count=0x0004, pVertexStreamZeroData=0x605e898, 
VertexStreamZeroStride=0x0014)
  [/home/pm215/src/wine-for-touhou.git/dlls/wined3d/device.c:4898] in wined3d
  (0x0605e874)
7 0x4738cd3d IDirect3DDevice9Impl_DrawPrimitiveUP+0xbc(iface=0x13b9a8, 
PrimitiveType=D3DPT_TRIANGLESTRIP, PrimitiveCount=0x0002, 
pVertexStreamZeroData=0x605e898, VertexStreamZeroStride=0x0014)
  [/home/pm215/src/wine-for-touhou.git/dlls/d3d9/device.c:1951] in d3d9
  (0x0605ea44)
8 0x00401423 in th123 (+0x1422) (0x0605ea58)
9 0x7bc72bf0 call_thread_entry_point+0x6f(entry=0x408330, arg=0x0(nil))
  [/home/pm215/src/wine-for-touhou.git/dlls/ntdll/signal_i386.c:2473] in ntdll

  ...we crash in upload_program() because
  p->ctx->FragmentProgram._Current is NULL.

  I built a version of the natty mesa-7.10.1-0ubuntu3 with this patch from mesa 
git applied:
  
http://cgit.freedesktop.org/mesa/mesa/commit/?id=a99b23752b0182c64ebe1dc9c18ab821550771ff
  and the game no longer segfaults on startup (it seems to hang under wine 1.2 
at a later point, though -- wine 1.3 works better but for purposes of this bug 
report I wanted to stick to in-Ubuntu versions.)

  So I guess this bug report is 

[Touch-packages] [Bug 767970] Re: xterm font corruption and X crash with nouveau experimental 3d (not just Unity)

[Christopher M. Penalver]

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

As per https://wiki.ubuntu.com/Releases, Natty reached EOL on October
28, 2012.

Is this reproducible on a supported release?

** No longer affects: unity (Ubuntu)

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

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

Title:
  xterm font corruption and X crash with nouveau experimental 3d (not
  just Unity)

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: unity

  Running FOSS/3D-nouveau drivers on Natty as of today, xterm fonts are
  corrupted horribly on input (not on output).

  To reproduce:
  - install natty beta 2
  - update all packages
  - Choose "additional drivers" and "experimental FOSS/3d support"
  - reboot.
  - open xterm in reverse video mode 'xterm -rv' (so it's white-on-black, the 
one true way)
  - type into the window, all fonts will be horribly corrupted, almost just 
plain white blocks.  however, typing 'ls' blind, the output of ls is fine. but 
type anything else at the prompt and it works.
  - If not immediately, this will cause X to crash.

  Update: This happens with or without Unity

  This is with an NV50-based video card.  My home machine with a radeon
  3450 running the FOSS drivers and unity runs xterm without this issue.

  Crash has this stacktrace:
  Program received signal SIGSEGV, Segmentation fault.
  0x7f01e23f00e2 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  (gdb) bt
  #0 0x7f01e23f00e2 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #1 0x7f01e23f231e in malloc () from /lib/x86_64-linux-gnu/libc.so.6
  #2 0x7f01df964b44 in exaPrepareAccessReg_mixed (pPixmap=0x2516880,
  index=0, pReg=0x0) at ../../exa/exa_migration_mixed.c:203
  #3 0x7f01df96f167 in ExaCheckImageGlyphBlt (pDrawable=0x23aef50,
  pGC=0x13a5b50, x=2, y=13, nglyph=,
  ppci=, pglyphBase=0x0) at ../../exa/exa_unaccel.c:326
  #4 0x004db8ab in damageText (pDrawable=0x23aef50, pGC=0x13a5b50, x=2,
  y=13, count=, chars=,
  fontEncoding=TwoD16Bit, textType=3) at ../../../miext/damage/damage.c:1486
  #5 0x004df4fc in damageImageText16 (pDrawable=0x23aef50,
  pGC=0x13a5b50, x=2, y=13, count=,
  chars=) at ../../../miext/damage/damage.c:1567
  #6 0x0042ff47 in doImageText (client=0x23ad880, c=0x7fffe7caccd0)
  at ../../dix/dixfonts.c:1548
  #7 0x00431410 in ImageText (client=,
  pDraw=, pGC=,
  nChars=, data=,
  xorg=, yorg=13, reqType=77, did=71303213)
  at ../../dix/dixfonts.c:1590
  #8 0x0042b8d0 in ProcImageText16 (client=0x23ad880)
  at ../../dix/dispatch.c:2320
  #9 0x0042e2a9 in Dispatch () at ../../dix/dispatch.c:431
  #10 0x00421a7e in main (argc=8, argv=,
  envp=) at ../../dix/main.c:287

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

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

[Touch-packages] [Bug 763461] Re: [natty intel 945gme kde] Xorg crashes when exiting fullscreen with KDE set to suspend effects for fullscreen windows

[Christopher M. Penalver]

Zorael, thank you for reporting this and helping make Ubuntu better. As
per https://wiki.ubuntu.com/Releases, Kubuntu Natty reached EOL on
October 28, 2012.

Is this reproducible on a supported release?

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

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

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

Title:
  [natty intel 945gme kde] Xorg crashes when exiting fullscreen with KDE
  set to suspend effects for fullscreen windows

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Kubuntu natty, packages up-to-date as of 2011-04-17. No ppas added, so
  mesa packages are version 7.10.2-0ubuntu1, xorg-server packages are
  version 1.10.0.902-1ubuntu1, -video-intel is version 2.14.0-4ubuntu7
  and KDE packages are version 4.6.2-0ubuntu1. Please reassign bug if
  the bug is not in mesa.

  When exiting a fullscreen window (eg Flash, fullscreen games) with
  KDE's desktop effects set to suspend effects when any such are
  fullscreened, Xorg crashes. Reproducible everytime and stops happening
  if that option is disabled in the Advanced tab of the Desktop Effects
  kcm module, perhaps to the detriment of performance.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a531b]
1: /usr/bin/X (0x8048000+0x60808) [0x80a8808]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xbbf40c]
3: /usr/lib/dri/i915_dri.so (intelClearWithBlit+0x162) [0x41b742]
4: /usr/lib/dri/i915_dri.so (0x3fc000+0x18670) [0x414670]
5: /usr/lib/dri/libdricore.so (_mesa_Clear+0x172) [0x1015512]
6: /usr/lib/xorg/modules/extensions/libglx.so (0x35d000+0x7fd9) [0x364fd9]
7: /usr/lib/xorg/modules/extensions/libglx.so (0x35d000+0x351b0) [0x3921b0]
8: /usr/lib/xorg/modules/extensions/libglx.so (0x35d000+0x3813f) [0x39513f]
9: /usr/bin/X (0x8048000+0x282c7) [0x80702c7]
10: /usr/bin/X (0x8048000+0x1a81c) [0x806281c]
11: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x1b8e37]
12: /usr/bin/X (0x8048000+0x1a411) [0x8062411]
Segmentation fault at address 0x30

  Even with -dbg packages installed I could not get a better backtrace.

  How to reproduce:
  1. Enable KDE's desktop effects if not already enabled
  2. Go to System Settings -> Desktop Effects, Advanced tab and check Suspend 
desktop effects for fullscreen windows
  3. Open a browser (Chromium in this case)
  4. Navigate to a youtube clip
  5. Play and hit fullscreen
  6. Exit fullscreen
  7. Observe complete Xorg crash

  As Xorg crashes you're returned to the kdm login screen - however a
  "broken" kded remains in memory, which prevents new wireless
  connections being established. It won't exit by itself, it won't exit
  when sent SIGTERM, has to be sent SIGKILL. That is perhaps a different
  bug, but worthy of mention to emphasize bug importance. The user has
  to reboot to be able to use Xorg again with a wireless connection,
  alternatively switch to a tty and kill the kded process before logging
  in again.

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

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

[Touch-packages] [Bug 1393502] Re: [MacBookPro11, 3, Cirrus Logic CS4208, Pink Mic] Combo jack not recognized.

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic] Combo jack not
  recognized.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  New Macbook comes with a four-conductor TRRS jack for headset.

  With headset plugged in the microfone is recognized on Mac os-x.
  Ubuntu recognizes the external headphones but not the microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mikaelb2403 F pulseaudio
   /dev/snd/controlC0:  mikaelb2403 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 17 18:58:35 2014
  InstallationDate: Installed on 2014-10-20 (28 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Pink Mic, N/A
  Symptom_Type: No auto-switch between inputs
  Title: [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic, N/A] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-11-10T22:25:45.211791

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

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

[Touch-packages] [Bug 1549979] Re: xorg freezes upon system boot with kernel 4.2.0-30

[Christopher M. Penalver]

Mattias H, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Alex Deucher, Christian König, and Kamal Mostafa CC dri-devel)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your understanding.

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

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

** Summary changed:

- xorg freezes upon system boot with kernel 4.2.0-30
+ freezes upon system boot with kernel 4.2.0-30

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

Title:
  freezes upon system boot with kernel 4.2.0-30

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Was working fine with kernel 4.2.0-27, now freezes on boot with kernel
  4.2.0-30

  $ lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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 Feb 25 21:24:38 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
   virtualbox-guest, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox-guest, 5.0.14, 4.2.0-30-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-02-16 (374 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ZBook 14
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.21
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.55
  dmi.chassis.asset.tag: 5CG4491SW6
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.21:bd09/03/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.55:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 14
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Feb 25 21:19:25 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4669 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

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

[Bug Watch Updater]

** Changed in: grilo-plugins (Debian)
   Status: New => Fix Released

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

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

Status in grilo-plugins package in Ubuntu:
  Fix Released
Status in grilo-plugins package in Debian:
  Fix Released

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

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

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

[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend

[lee worden]

That link doesn't work for me

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate

[Jared Dominguez]

Also tracked at https://bugs.launchpad.net/somerville/+bug/1551518

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

Title:
  periodically after suspend/resume wpasupplicant fails to authenticate

Status in wpa package in Ubuntu:
  New

Bug description:
  After suspending and resuming, periodically wpasupplicant fails to
  reauthenticate. I'm prompted for a password to reconnect. I enabled
  debugging for wpasupplicant. Something that draws attention is seeing
  "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be
  incorrect". This is with the Ubuntu 14.04 OEM image for the Dell
  Precision 5510. All updates have been installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1.4 [modified: 
usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service]
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 13:38:06 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550504] Re: lightdm unresponsive after suspend

[Jared Dominguez]

Also tracked at https://bugs.launchpad.net/somerville/+bug/1551514

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

Title:
  lightdm unresponsive after suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back (or also
  after failing to suspend), lightdm does not show a password field, and
  selecting my username does not bring up a password field. If I click
  on the gear in the upper right corner, I can choose to switch
  accounts; doing that, after several seconds, lightdm comes back, and I
  can unlock the user session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:53:36 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend

[Jared Dominguez]

Also tracked at https://bugs.launchpad.net/somerville/+bug/1551516

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1551528] Re: scope-runner-dbus.py crashed when calculator scope was used

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1539853, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1551528/+attachment/4585007/+files/CoreDump.gz

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

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

** This bug has been marked a duplicate of bug 1539853
   scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': 
corrupted double-linked list: 0x01fdb260 ***

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  scope-runner-dbus.py crashed when calculator scope was used

Status in libunity package in Ubuntu:
  New

Bug description:
  Enter 2+2 in the Dash, select the Calculator scope, see the crash
  happen (behind the Dash).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 29 22:28:42 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-08-28 (185 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
info/calculator.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=fr_CA:fr
   PATH=(custom, no user)
   LANG=fr_CA.UTF-8
  Signal: 6
  SourcePackage: libunity
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (3 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1313332] Re: 45+ seconds to boot

[Felicia]

Hi Christopher,

I followed the link and it looks like trying it would mean upgrading my OS?
I'll try it out as a dual boot but that will have to wait until this
weekend.

Thanks for following up on my bug report.

Felicia


On Sun, Feb 28, 2016 at 4:24 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Felicia, to see if this is already resolved, could you please test
> http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
>
> ** Tags added: latest-bios-423
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1313332
>
> Title:
>   45+ seconds to boot
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   14.04 takes noticably longer to boot than 13.04 (pretty fast) and
>   13.10 (also slow)
>
>   Others have suggested that I try the proprietary drivers for my Radeon
>   Graphics HD7340. I tried both of the proprietary drivers and they each
>   took longer than the xorg driver (by a couple seconds).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: xorg 1:7.7+1ubuntu8
>   ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
>   Uname: Linux 3.13.0-24-generic x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.14.1-0ubuntu3
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Sun Apr 27 08:52:22 2014
>   DistUpgraded: Fresh install
>   DistroCodename: trusty
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340]
> [1002:9808] (prog-if 00 [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. Device [1043:14e7]
>   InstallationDate: Installed on 2014-04-26 (0 days ago)
>   InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140417)
>   MachineType: ASUSTeK COMPUTER INC. X55U
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
> root=UUID=6e30bde6-6b06-4b41-a7ef-90bec98a8300 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/06/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: X55U.423
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: X55U
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.name: X55U
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>   version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.52-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
>   version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.8.2-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.910-0ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.10-1ubuntu2
>   xserver.bootTime: Sun Apr 27 07:14:03 2014
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.15.1-0ubuntu2
>   xserver.video_driver: radeon
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313332/+subscriptions
>


--


*Felicia James Being self-disciplined fosters internal
peace and thus a willingness to help others realize the same.*

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

Title:
  45+ seconds to boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  14.04 takes noticably longer to boot than 13.04 (pretty fast) and
  13.10 (also slow)

  Others have suggested that I try the proprietary drivers for my Radeon
  Graphics HD7340. I tried both of the proprietary drivers and they each
  took longer than the xorg driver (by a couple seconds).

  

[Touch-packages] [Bug 1551524] [NEW] Lots of irrelevant thumbnail requests

[Michi Henning]

Public bug reported:

I have a bunch of songs in the Music directory, some without embedded
art, some with. I leave the music app in the song list and kill it.
Then:

thumbnailer-admin clear

tail -f ~phablet/.cache/upstart/dbus.log

Now I start the music app. I've attached the dbus.log.

Looking through the requests that are issue to the thumbnailer, I would
expect to see only thumbnail and album requests, depending on whether a
song contains embedded cover art or not. However, there are artist
requests interspersed with all the other requests, even though no artist
is shown in the current view.

Doing this is not great because the remote server is slow, and the
useless artist requests just delay the album requests that need to be
shown. In other words, it makes for a worse user experience.

Would it be possible to restrict requests to only what is actually
needed for the current view? Things would move considerably faster that
way.

** Affects: music-app
 Importance: Undecided
 Status: New

** Affects: thumbnailer (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Attachment added: "dbus.log"
   https://bugs.launchpad.net/bugs/1551524/+attachment/4585002/+files/dbus.log

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

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

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

Title:
  Lots of irrelevant thumbnail requests

Status in Ubuntu Music App:
  New
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  I have a bunch of songs in the Music directory, some without embedded
  art, some with. I leave the music app in the song list and kill it.
  Then:

  thumbnailer-admin clear

  tail -f ~phablet/.cache/upstart/dbus.log

  Now I start the music app. I've attached the dbus.log.

  Looking through the requests that are issue to the thumbnailer, I
  would expect to see only thumbnail and album requests, depending on
  whether a song contains embedded cover art or not. However, there are
  artist requests interspersed with all the other requests, even though
  no artist is shown in the current view.

  Doing this is not great because the remote server is slow, and the
  useless artist requests just delay the album requests that need to be
  shown. In other words, it makes for a worse user experience.

  Would it be possible to restrict requests to only what is actually
  needed for the current view? Things would move considerably faster
  that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1551524/+subscriptions

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

[Touch-packages] [Bug 1542846] Re: [HP ProBook 450 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at all

[Raymond]

[ 3.216843] pci :01:00.0: can't claim BAR 6 [mem
0xfffe-0x pref]: no compatible bridge window

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

Title:
  [HP ProBook 450 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at
  all

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I bought hp probook 450 g3 . it does'nt sound.
  In sound setting play sound throught is empty.

  lspci :
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation Skylake Integrated 
Graphics (rev 07)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Device 9d18 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-LP HD 
Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT 
[Radeon R7 M260/M265] (rev 83)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  03:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  Uname: Linux 4.4.1-040401-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  engmmrj1562 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb  7 16:17:54 2016
  InstallationDate: Installed on 2016-02-06 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  engmmrj1562 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HP ProBook 450 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.03
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.1F
  dmi.chassis.asset.tag: 5CD546198T
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.03:bd10/15/2015:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion16.1F:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)

[Raymond]

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/oxygen?qt=grep=dg%28x%29

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

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

Title:
  No sound on ASUS Xonar DGX Soundcard (16.04)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), 
Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. 
Tested with the app to test speakers, Firefox, VLC, and checked with 
pavucontrol, the progress bar indicate that a sound is played on the card, but 
no sound on the speakers.

  I report this bug because it works on the same version with the
  integrated card of my motherboard. (ASUS H87-PLUS)

  On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all
  defaults params)

  The speakers connected are the Logitech Z9600 (by 3 jacks), and I
  precise that they are correctly plugged in, etc..., it works when I
  connect it to the integrated sound card of my motherboard (and if I
  use Ubuntu 14.04 LTS)

  I don't know if it's a normal development bug, but in doubt I report it.
  Thank you,
  Valentin Crône

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

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

[Touch-packages] [Bug 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  My phone's bluetooth  is displayed dozens of times under the network
  list (wifi icon)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can hardly even start describing how screwed up this is.
  Have a look at the screenshot.

  I had seen this before and hadn't even realized that "XT1039 Network"
  repeated like 37 times had something to do with my own Android phone,
  a motorola Moto G. Needless to say I have only one.

  Out of curiosity I clicked on one of "them" (thinking this was some
  neighboor's device, obviously suspecting it was just one device
  repeated several times because of a bug), and then my phone vibrated
  prompting me whether to accept the connection from the computer.

  Which I did. As a result, the bluetooth indicator next to the network
  indicator showed a lock icon for a fraction of a second, which
  immediately disappeared. I guess that means that the computer and the
  phone peered via bluetooth for a few instants. At the same time, the
  wifi icon started animating (as if the computer was connecting to a
  wifi network... or a network of any kind I guess, since the same
  stupidly designed wifi-like animation is used when connecting to LAN
  via an ethernet cable). After that, the small lock below the bluetooth
  icon disappeared, the wifi icon stopped animating and went back to its
  normal "connected" status (I was previously and still connected to my
  home router's wifi network), and a baloon saying "Disconnected [NL]
  Network" appeared and disappeared.

  Then I repeated the test several times with the same result, except
  that the phone didn't prompt me any more to accept the connection.

  
  This is totally screwed up in several ways.

  First, there's no reason "XT1039 Network" should be listed AT ALL
  together with wifi and ethernet networks. What kind of "network" is it
  supposed to be?? Of course I have not turned on bluetooth tethering on
  the phone, and bluetooth connection to the phone is already available
  under the bluetooth indicator.

  If it makes any sense at all to show the mobile device as a "network" 
alongside with wifi and cable networks because, well, bluetooth is a network as 
well, then
  1) the list of bluetooth "networks" should have a header, just like "wifi 
networks" and "ethernet network". Right now, there is just a list of networks 
that you don't know what kind they are
  2) the device should be only listed once, not 37  times
  3) I also suspect the 3 items called just "network" are related
  4) If it is there at all, it must work. What is it supposed to do? The same 
as unfolding the menu under the Bluetooth indicator, hovering on the device 
there (which is listed only once there) and turning on the "Connection" switch? 
That one does work. This one (in the list of networks) doesn't. And if it is 
supposed to do something different, it's clearly failing as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  1 03:29:50 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-11 (871 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.167  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-20T16:52:59.722501
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1551515] [NEW] My phone's bluetooth is displayed dozens of times under the network list (wifi icon)

[teo1978]

Public bug reported:

I can hardly even start describing how screwed up this is.
Have a look at the screenshot.

I had seen this before and hadn't even realized that "XT1039 Network"
repeated like 37 times had something to do with my own Android phone, a
motorola Moto G. Needless to say I have only one.

Out of curiosity I clicked on one of "them" (thinking this was some
neighboor's device, obviously suspecting it was just one device repeated
several times because of a bug), and then my phone vibrated prompting me
whether to accept the connection from the computer.

Which I did. As a result, the bluetooth indicator next to the network
indicator showed a lock icon for a fraction of a second, which
immediately disappeared. I guess that means that the computer and the
phone peered via bluetooth for a few instants. At the same time, the
wifi icon started animating (as if the computer was connecting to a wifi
network... or a network of any kind I guess, since the same stupidly
designed wifi-like animation is used when connecting to LAN via an
ethernet cable). After that, the small lock below the bluetooth icon
disappeared, the wifi icon stopped animating and went back to its normal
"connected" status (I was previously and still connected to my home
router's wifi network), and a baloon saying "Disconnected [NL] Network"
appeared and disappeared.

Then I repeated the test several times with the same result, except that
the phone didn't prompt me any more to accept the connection.


This is totally screwed up in several ways.

First, there's no reason "XT1039 Network" should be listed AT ALL
together with wifi and ethernet networks. What kind of "network" is it
supposed to be?? Of course I have not turned on bluetooth tethering on
the phone, and bluetooth connection to the phone is already available
under the bluetooth indicator.

If it makes any sense at all to show the mobile device as a "network" alongside 
with wifi and cable networks because, well, bluetooth is a network as well, then
1) the list of bluetooth "networks" should have a header, just like "wifi 
networks" and "ethernet network". Right now, there is just a list of networks 
that you don't know what kind they are
2) the device should be only listed once, not 37  times
3) I also suspect the 3 items called just "network" are related
4) If it is there at all, it must work. What is it supposed to do? The same as 
unfolding the menu under the Bluetooth indicator, hovering on the device there 
(which is listed only once there) and turning on the "Connection" switch? That 
one does work. This one (in the list of networks) doesn't. And if it is 
supposed to do something different, it's clearly failing as well.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar  1 03:29:50 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-10-11 (871 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.167  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago)
modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-20T16:52:59.722501
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug wily

** Summary changed:

- My phone's bluetooth  is displayed dozens of times under the wifi/network list
+ My phone's bluetooth  is displayed dozens of times under the network list 
(wifi icon)

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

Title:
  My phone's bluetooth  is displayed dozens of times under the network
  list (wifi icon)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can hardly even start describing how screwed up this is.
  Have a look at the screenshot.

  I had seen this before and hadn't even realized that "XT1039 Network"
  repeated like 37 times had something to do with my own Android phone,
  a motorola Moto G. Needless to say I have only one.

  Out of curiosity I clicked on one of "them" (thinking this was some

[Touch-packages] [Bug 1551511] [NEW] apt: packages that need to download other files do not work

[Hariharan Iyer]

Public bug reported:

Packages that need to download and install other files, such as 
pepperflashplugin-nonfree and msttfcorefonts fail to download the files. Errors 
similar to the following are observed:
Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/courie32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
or
ERROR: failed to retrieve status information from google : W: Can't drop 
privileges for downloading as file 
'./var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_InRelease'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
More information might be available at:
  http://wiki.debian.org/PepperFlashPlayer

Ubuntu version: 16.04
apt version: 1.2.3 (amd64)

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

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

Title:
  apt: packages that need to download other files do not work

Status in apt package in Ubuntu:
  New

Bug description:
  Packages that need to download and install other files, such as 
pepperflashplugin-nonfree and msttfcorefonts fail to download the files. Errors 
similar to the following are observed:
  Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/courie32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
  or
  ERROR: failed to retrieve status information from google : W: Can't drop 
privileges for downloading as file 
'./var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_InRelease'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
  More information might be available at:
http://wiki.debian.org/PepperFlashPlayer

  Ubuntu version: 16.04
  apt version: 1.2.3 (amd64)

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

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

[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend

[Jared Dominguez]

Note that trying to turn on and off the wireless card using the wireless
hotkey did not help. As can be seen from the logs, NM reports wifi's
killswitch status change but still does not see any APs or try
reconnecting.

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate

[Jared Dominguez]

The failure was seen with WPA2 Personal with an Aruba access point.

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

Title:
  periodically after suspend/resume wpasupplicant fails to authenticate

Status in wpa package in Ubuntu:
  New

Bug description:
  After suspending and resuming, periodically wpasupplicant fails to
  reauthenticate. I'm prompted for a password to reconnect. I enabled
  debugging for wpasupplicant. Something that draws attention is seeing
  "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be
  incorrect". This is with the Ubuntu 14.04 OEM image for the Dell
  Precision 5510. All updates have been installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1.4 [modified: 
usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service]
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 13:38:06 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend

[Jared Dominguez]

This occurred about every five to ten reboots.

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1550504] Re: lightdm unresponsive after suspend

[Jared Dominguez]

I can't reproduce on a system with the FHD panel. It may be restricted
to the UHD model.

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

Title:
  lightdm unresponsive after suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back (or also
  after failing to suspend), lightdm does not show a password field, and
  selecting my username does not bring up a password field. If I click
  on the gear in the upper right corner, I can choose to switch
  accounts; doing that, after several seconds, lightdm comes back, and I
  can unlock the user session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:53:36 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend

[Jared Dominguez]

The failure was seen with WPA2 Personal with an Aruba access point.

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

-- 
Mailing list: https://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 1549918] Re: USB mouse stopped working after kernel upgrade

[Tim Schutte]

Hi Christopher,

Thank you for all the help.  As I have tried to explain on 
launchpad.net, the problem was solved by rebooting several times--it was 
just  a transient error.

Thanks,
Tim

On 02/29/2016 12:47 PM, Christopher M. Penalver wrote:
> Tim Schutte, in order to allow additional upstream developers to examine the 
> issue, at your earliest convenience, could you please test the latest 
> upstream kernel available from 
> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
> the following:
> 1) The one to test is at the very top line at the top of the page (not the 
> daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually was 
> released upstream.
> 4) Install instructions are available at 
> https://wiki.ubuntu.com/Kernel/MainlineBuilds .
>
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
>
> If the latest kernel did not allow you to test to the issue (ex. you couldn't 
> boot into the OS) please make a comment in your report about this, and 
> continue to test the next most recent kernel version until you can test to 
> the issue. Once you've tested the upstream kernel, please comment on which 
> kernel version specifically you tested. If this issue is fixed in the 
> mainline kernel, please add the following tags by clicking on the yellow 
> circle with a black pencil icon, next to the word Tags, located at the bottom 
> of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
>
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
>
> If the mainline kernel does not fix the issue, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
>
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
>
> Once testing of the latest upstream kernel is complete, please mark this
> report's Status as Confirmed. Please let us know your results.
>
> Thank you for your understanding.
>
> ** Tags added: latest-bios-f.13
>
> ** Changed in: xorg (Ubuntu)
> Importance: Low => Medium
>

-- 
*Tim Schutte
kc...@sbcglobal.net
kc...@yahoo.com
kc...@arrl.net
tjschu...@gmail.com
"Try not. Do, or do not. There is no try." --Yoda*

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

Title:
  USB mouse stopped working after kernel upgrade

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I upgraded via synaptic yesterday, and my Logitech USB wireless mouse
  stopped working.  The upgrade included the latest kernel.

  Linux sempai 3.16.0-62-generic #82~14.04.1-Ubuntu SMP Fri Feb 19
  18:56:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-62.82~14.04.1-generic 3.16.7-ckt23
  Uname: Linux 3.16.0-62-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Feb 25 12:41:08 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3638]
  InstallationDate: Installed on 2015-11-22 (95 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-62-generic 
root=UUID=a5ae3032-edad-4cdc-8264-5550f4e90f1a ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.name: 3638
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 33.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd01/25/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr049C212412202:rvnHewlett-Packard:rn3638:rvr33.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 049C212412202
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  

[Touch-packages] [Bug 1540372] Re: [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound

[Raymond]

http://www.intel.com/content/www/us/en/support/boards-and-kits/desktop-
boards/05512.html

Check your computer chassis front audio panel

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

Title:
  [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I cant record or play on my sound card ubuntu 14.04.1

  Alsa is detecting the sound card
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  but PulseAudio is not detecting the card 

  attached the log file

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuned  1851 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:09:35 2016
  InstallationDate: Installed on 2015-10-26 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct2:cvr:
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-29T17:09:52.179523

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

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

[Touch-packages] [Bug 1540372] Re: [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound

[Raymond]

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_sigmatel.c?id=eb63212868c348cc6d3ec6929d7d98f7d29493e9


ALSA: hda - Power up always when no jack detection is available
When no jack detection is available, the pins should be always
turned on since it can't be turned on/off dynamically via unsol
events.


This mean you need to set bit 8 of all jacks if jack detect always fail

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

Title:
  [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I cant record or play on my sound card ubuntu 14.04.1

  Alsa is detecting the sound card
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  but PulseAudio is not detecting the card 

  attached the log file

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuned  1851 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:09:35 2016
  InstallationDate: Installed on 2015-10-26 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct2:cvr:
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-29T17:09:52.179523

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

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

[Touch-packages] [Bug 1502586] Re: libfreetype6 ftbfs due to autoconf version

[themusicgod1]

...i don't have autoconf2.13 installed, i have autoconf2.64 installed.

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

Title:
  libfreetype6 ftbfs due to autoconf version

Status in freetype package in Ubuntu:
  Won't Fix

Bug description:
  According to the README, the process to build libfreetype6 seems to
  start with

  ./debian/rules patch

  which fails due to the correct version of autoconf not being detected,
  even though it is installed:

  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ ./debian/rules patch
  # Unpack upstream tarballs
  Unpacking freetype-2.5.2.tar.bz2 ...
  Unpacking freetype-doc-2.5.2.tar.bz2 ...
  Unpacking ft2demos-2.5.2.tar.bz2 ... 
  [...]
  Applying patch savannah-bug-41590.patch
  patching file src/type1/t1load.c

  Now at patch savannah-bug-41590.patch
  cd freetype-2.5.2 && ./autogen.sh
  ERROR: Your version of the `autoconf' tool is too old.
 Minimum version 2.62 is required (yours is version 2.13).
 Please upgrade or use the AUTOCONF variable to point to a more recent 
one.

  debian/rules:72: recipe for target 'patch-stamp' failed
  make: *** [patch-stamp] Error 1
   
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ which autoconf2.64 
  /usr/bin/autoconf2.64
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ echo $AUTOCONF
  /usr/bin/autoconf2.64

  (same happens if $AUTOCONF is set differently, or not set)

  Ubuntu: 15.10 wily werewolf

  libfreetype6:
Installed: 2.5.2-4ubuntu2
Candidate: 2.5.2-4ubuntu2
Version table:
   *** 2.5.2-4ubuntu2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status 
  autoconf:
Installed: 2.69-8
Candidate: 2.69-8

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6 2.5.2-4ubuntu2
  Uname: Linux 4.1.0-040100rc1-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct  4 07:00:25 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (451 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1502586] Re: libfreetype6 ftbfs due to autoconf version

[themusicgod1]

Hrm guess I do have autoconf2.13 installed also.  I can remove that and
try again.

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

Title:
  libfreetype6 ftbfs due to autoconf version

Status in freetype package in Ubuntu:
  Won't Fix

Bug description:
  According to the README, the process to build libfreetype6 seems to
  start with

  ./debian/rules patch

  which fails due to the correct version of autoconf not being detected,
  even though it is installed:

  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ ./debian/rules patch
  # Unpack upstream tarballs
  Unpacking freetype-2.5.2.tar.bz2 ...
  Unpacking freetype-doc-2.5.2.tar.bz2 ...
  Unpacking ft2demos-2.5.2.tar.bz2 ... 
  [...]
  Applying patch savannah-bug-41590.patch
  patching file src/type1/t1load.c

  Now at patch savannah-bug-41590.patch
  cd freetype-2.5.2 && ./autogen.sh
  ERROR: Your version of the `autoconf' tool is too old.
 Minimum version 2.62 is required (yours is version 2.13).
 Please upgrade or use the AUTOCONF variable to point to a more recent 
one.

  debian/rules:72: recipe for target 'patch-stamp' failed
  make: *** [patch-stamp] Error 1
   
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ which autoconf2.64 
  /usr/bin/autoconf2.64
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ echo $AUTOCONF
  /usr/bin/autoconf2.64

  (same happens if $AUTOCONF is set differently, or not set)

  Ubuntu: 15.10 wily werewolf

  libfreetype6:
Installed: 2.5.2-4ubuntu2
Candidate: 2.5.2-4ubuntu2
Version table:
   *** 2.5.2-4ubuntu2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status 
  autoconf:
Installed: 2.69-8
Candidate: 2.69-8

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6 2.5.2-4ubuntu2
  Uname: Linux 4.1.0-040100rc1-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct  4 07:00:25 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (451 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1502586] Re: libfreetype6 ftbfs due to autoconf version

[themusicgod1]

nm that works.

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

Title:
  libfreetype6 ftbfs due to autoconf version

Status in freetype package in Ubuntu:
  Won't Fix

Bug description:
  According to the README, the process to build libfreetype6 seems to
  start with

  ./debian/rules patch

  which fails due to the correct version of autoconf not being detected,
  even though it is installed:

  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ ./debian/rules patch
  # Unpack upstream tarballs
  Unpacking freetype-2.5.2.tar.bz2 ...
  Unpacking freetype-doc-2.5.2.tar.bz2 ...
  Unpacking ft2demos-2.5.2.tar.bz2 ... 
  [...]
  Applying patch savannah-bug-41590.patch
  patching file src/type1/t1load.c

  Now at patch savannah-bug-41590.patch
  cd freetype-2.5.2 && ./autogen.sh
  ERROR: Your version of the `autoconf' tool is too old.
 Minimum version 2.62 is required (yours is version 2.13).
 Please upgrade or use the AUTOCONF variable to point to a more recent 
one.

  debian/rules:72: recipe for target 'patch-stamp' failed
  make: *** [patch-stamp] Error 1
   
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ which autoconf2.64 
  /usr/bin/autoconf2.64
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ echo $AUTOCONF
  /usr/bin/autoconf2.64

  (same happens if $AUTOCONF is set differently, or not set)

  Ubuntu: 15.10 wily werewolf

  libfreetype6:
Installed: 2.5.2-4ubuntu2
Candidate: 2.5.2-4ubuntu2
Version table:
   *** 2.5.2-4ubuntu2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status 
  autoconf:
Installed: 2.69-8
Candidate: 2.69-8

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6 2.5.2-4ubuntu2
  Uname: Linux 4.1.0-040100rc1-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct  4 07:00:25 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (451 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1540372] Re: [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound

[Raymond]

You have to find out your onboard audio still work with jack detection
and analog back at which version of alsa driver/kernel by boot from live
cd

in theory, you lost the automute feature when jack detection of hp is
not functioning but the aggressive power saving use jack detection to
power down the widgets in unused path this may mean analog loopback only
function when some appplication open both playback and capture stream

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

Title:
  [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I cant record or play on my sound card ubuntu 14.04.1

  Alsa is detecting the sound card
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  but PulseAudio is not detecting the card 

  attached the log file

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuned  1851 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:09:35 2016
  InstallationDate: Installed on 2015-10-26 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct2:cvr:
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-29T17:09:52.179523

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

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

[Touch-packages] [Bug 405294] Re: a2dp skips terribly

[yayfortrees]

I was encountering this same issue on Gentoo. It appeared to be at
random times but persistent once it started. I realized that it only
happens if 'gnome-control-center bluetooth' is open. I would often leave
this open after pairing the device, not really thinking about it. As
soon as I close it the "module-bluez5-device.c: Skipping..." messages
stop and the choppy sound goes away.

Posting in case it helps track this down.

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

Title:
  a2dp skips terribly

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1550910] Re: fglrx renders extremely slow in latest kernels

[Daniel van Vugt]

** No longer affects: mesa (Ubuntu)

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

Title:
  fglrx renders extremely slow in latest kernels

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  I am using latest development version of xenial (ubuntu 16.04).

  My video card is AMD HD7950, and I use an MiniDP-to-DP line to connect
  it with an Acer XB240H display.

  With fglrx or fglrx-updates installed, everything renders extremely
  slow, even raw terminal renders like 100 lines per second.

  Workarounds failed:

  * AMD official driver failed to build due to bug #1502978.
  * The open source driver can only provide 1024x768 resolution.

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

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

[Touch-packages] [Bug 1550719] Re: Add output of usb-devices when ubuntu-bug linux or apport-collect'ing existing report affecting linux (Ubuntu)

[Christopher M. Penalver]

** Description changed:

  What is expected to happen is when an original reporter files a report via a 
terminal:
  ubuntu-bug linux
  
  or performs an apport-collect to a report that is affecting tbe linux 
(Ubuntu) package, apport automatically gathers the following command and adds 
it as an attachment:
  usb-devices
  
- Without this information, bluetooth device patches can't be committed
- upstream.
+ Lsusb is not sufficient. Upstream bluetooth maintainer requires the output of:
+ cat /sys/kernel/debug/usb/devices
+ 
+ Without this information patches are never accepted.
  
  Please add this output to apport.
  
  If needed, I can provide a patch, but it is very straight-forward to
  add.
  
- The is motivated due to the circumstances surrounding:
+ The is motivated due to the circumstances surrounding the following report, 
and future bluetooth bugs reported:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546694
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.19
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
  
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 27 17:23:18 2016
  InstallationDate: Installed on 2013-10-17 (863 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-04-16 (681 days ago)

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

Title:
  Add output of usb-devices when ubuntu-bug linux or apport-collect'ing
  existing report affecting linux (Ubuntu)

Status in apport package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when an original reporter files a report via a 
terminal:
  ubuntu-bug linux

  or performs an apport-collect to a report that is affecting tbe linux 
(Ubuntu) package, apport automatically gathers the following command and adds 
it as an attachment:
  usb-devices

  Lsusb is not sufficient. Upstream bluetooth maintainer requires the output of:
  cat /sys/kernel/debug/usb/devices

  Without this information patches are never accepted.

  Please add this output to apport.

  If needed, I can provide a patch, but it is very straight-forward to
  add.

  The is motivated due to the circumstances surrounding the following report, 
and future bluetooth bugs reported:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546694

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.19
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 27 17:23:18 2016
  InstallationDate: Installed on 2013-10-17 (863 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-04-16 (681 days ago)

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

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

[Touch-packages] [Bug 1551476] [NEW] /usr/bin/webapp-container:11:base::DefaultDeleter:base::internal::scoped_ptr_impl:base::internal::scoped_ptr_impl:scoped_ptr:net::HttpCache::PendingOp::~PendingOp

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding webbrowser-app.  This problem was most recently seen with
version 0.23+15.10.20150929-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/4679928eb1ffa72c37832fc5c0b331d478ec6de7
contains more details.

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


** Tags: trusty vivid wily

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

Title:
  /usr/bin/webapp-
  
container:11:base::DefaultDeleter:base::internal::scoped_ptr_impl:base::internal::scoped_ptr_impl:scoped_ptr:net::HttpCache::PendingOp::~PendingOp

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding webbrowser-app.  This problem was most recently seen with
  version 0.23+15.10.20150929-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/4679928eb1ffa72c37832fc5c0b331d478ec6de7
  contains more details.

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

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

[Touch-packages] [Bug 1518586] Re: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: forsøger at overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som er forskellig fra andr

[Steve Langasek]

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

** This bug is no longer a duplicate of bug 1518562
   package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different 
from other instances of package libfreetype6-dev:i386
** This bug has been marked a duplicate of bug 1390767
   trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which 
is different from other instances of package libfreetype6-dev:i386

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

Title:
  package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade:
  forsøger at overskrive delt '/usr/share/man/man1/freetype-
  config.1.gz', som er forskellig fra andre instanser af pakken
  libfreetype6-dev:i386

Status in freetype package in Ubuntu:
  New

Bug description:
  Happened during while this command executed:
  sudo apt-get install libxft-dev:i386

  Følgende NYE pakker vil blive installeret:
libfreetype6-dev:i386
  0 opgraderes, 1 nyinstalleres, 0 afinstalleres og 5 opgraderes ikke.
  14 ikke fuldstændigt installerede eller afinstallerede.
  0 B/633 kB skal hentes fra arkiverne.
  Efter denne handling, vil 3.551 kB yderligere diskplads være brugt.
  (Læser database ... 267671 filer og kataloger installeret i øjeblikket.)
  Gør klar til at udpakke .../libfreetype6-dev_2.5.2-4ubuntu2_i386.deb ...
  Udpakker libfreetype6-dev:i386 (2.5.2-4ubuntu2) ...
  dpkg: fejl under behandling af arkivet 
/var/cache/apt/archives/libfreetype6-dev_2.5.2-4ubuntu2_i386.deb (--unpack):
   forsøger at overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som 
er forskellig fra andre instanser af pakken libfreetype6-dev:i386
  dpkg-deb: fejl: underproces indsæt blev dræbt af signal (Kanalen blev brudt)
  Behandler udløsere for doc-base (0.10.6) ...
  Behandler udløsere for man-db (2.7.4-1) ...
  Der opstod fejl under behandlingen:
   /var/cache/apt/archives/libfreetype6-dev_2.5.2-4ubuntu2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  john@john-Aspire-5733Z:~$

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6-dev 2.5.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Nov 21 14:36:42 2015
  DuplicateSignature: package:libfreetype6-dev:2.5.2-4ubuntu2:forsøger at 
overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som er forskellig 
fra andre instanser af pakken libfreetype6-dev:i386
  ErrorMessage: forsøger at overskrive delt 
'/usr/share/man/man1/freetype-config.1.gz', som er forskellig fra andre 
instanser af pakken libfreetype6-dev:i386
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: freetype
  Title: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: 
forsøger at overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som er 
forskellig fra andre instanser af pakken libfreetype6-dev:i386
  UpgradeStatus: Upgraded to wily on 2015-10-28 (24 days ago)

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

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

[Touch-packages] [Bug 1518727] Re: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/share/man/man1/freetype-config.1.gz' partilhado, que é diferente de o

[Steve Langasek]

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

** This bug is no longer a duplicate of bug 1518562
   package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different 
from other instances of package libfreetype6-dev:i386
** This bug has been marked a duplicate of bug 1390767
   trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which 
is different from other instances of package libfreetype6-dev:i386

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

Title:
  package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: a
  tentar sobreescrever '/usr/share/man/man1/freetype-config.1.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libfreetype6-dev:i386

Status in freetype package in Ubuntu:
  New

Bug description:
  weiller@weiller-desktop:~$ lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  weiller@weiller-desktop:~$ sudo apt-cache policy libfreetype6
  libfreetype6:
Instalado: 2.5.2-4ubuntu2
Candidato: 2.5.2-4ubuntu2
Tabela de versão:
   *** 2.5.2-4ubuntu2 0
  500 http://br.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  Installed

  Broken

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6-dev 2.5.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Nov 22 13:30:07 2015
  DuplicateSignature: package:libfreetype6-dev:2.5.2-4ubuntu2:a tentar 
sobreescrever '/usr/share/man/man1/freetype-config.1.gz' partilhado, que é 
diferente de outras instâncias do pacote libfreetype6-dev:i386
  ErrorMessage: a tentar sobreescrever 
'/usr/share/man/man1/freetype-config.1.gz' partilhado, que é diferente de 
outras instâncias do pacote libfreetype6-dev:i386
  InstallationDate: Installed on 2015-11-12 (10 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: freetype
  Title: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: a 
tentar sobreescrever '/usr/share/man/man1/freetype-config.1.gz' partilhado, que 
é diferente de outras instâncias do pacote libfreetype6-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1518562] Re: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different from oth

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1390767
   trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which 
is different from other instances of package libfreetype6-dev:i386

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

Title:
  package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz',
  which is different from other instances of package
  libfreetype6-dev:i386

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  Done with removing /usr/share/man/man1/freetype-config.1.gz

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6-dev 2.5.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Nov 21 21:32:32 2015
  DuplicateSignature: package:libfreetype6-dev:2.5.2-4ubuntu2:trying to 
overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different 
from other instances of package libfreetype6-dev:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/man/man1/freetype-config.1.gz', which is different from other 
instances of package libfreetype6-dev:i386
  InstallationDate: Installed on 2015-11-14 (6 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: freetype
  Title: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: 
trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is 
different from other instances of package libfreetype6-dev:i386
  UpgradeStatus: Upgraded to wily on 2015-11-14 (6 days ago)

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

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

[Touch-packages] [Bug 1502586] Re: libfreetype6 ftbfs due to autoconf version

[Steve Langasek]

Current versions of the autoconf2.13 package install the program as
/usr/bin/autoconf2.13.  And autoconf2.13 is ancient.  You should
uninstall this package when building freetype.

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

Title:
  libfreetype6 ftbfs due to autoconf version

Status in freetype package in Ubuntu:
  Won't Fix

Bug description:
  According to the README, the process to build libfreetype6 seems to
  start with

  ./debian/rules patch

  which fails due to the correct version of autoconf not being detected,
  even though it is installed:

  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ ./debian/rules patch
  # Unpack upstream tarballs
  Unpacking freetype-2.5.2.tar.bz2 ...
  Unpacking freetype-doc-2.5.2.tar.bz2 ...
  Unpacking ft2demos-2.5.2.tar.bz2 ... 
  [...]
  Applying patch savannah-bug-41590.patch
  patching file src/type1/t1load.c

  Now at patch savannah-bug-41590.patch
  cd freetype-2.5.2 && ./autogen.sh
  ERROR: Your version of the `autoconf' tool is too old.
 Minimum version 2.62 is required (yours is version 2.13).
 Please upgrade or use the AUTOCONF variable to point to a more recent 
one.

  debian/rules:72: recipe for target 'patch-stamp' failed
  make: *** [patch-stamp] Error 1
   
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ which autoconf2.64 
  /usr/bin/autoconf2.64
  themusicgod1@Hedy:~/libfreetype/freetype-2.5.2$ echo $AUTOCONF
  /usr/bin/autoconf2.64

  (same happens if $AUTOCONF is set differently, or not set)

  Ubuntu: 15.10 wily werewolf

  libfreetype6:
Installed: 2.5.2-4ubuntu2
Candidate: 2.5.2-4ubuntu2
Version table:
   *** 2.5.2-4ubuntu2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status 
  autoconf:
Installed: 2.69-8
Candidate: 2.69-8

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6 2.5.2-4ubuntu2
  Uname: Linux 4.1.0-040100rc1-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct  4 07:00:25 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (451 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550719] Re: Add output of usb-devices when ubuntu-bug linux or apport-collect'ing existing report affecting linux (Ubuntu)

[Christopher M. Penalver]

I agree with Jeremy and Pilot6. I don't have any objections to this, nor
do any stand at this point.

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

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

Title:
  Add output of usb-devices when ubuntu-bug linux or apport-collect'ing
  existing report affecting linux (Ubuntu)

Status in apport package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when an original reporter files a report via a 
terminal:
  ubuntu-bug linux

  or performs an apport-collect to a report that is affecting tbe linux 
(Ubuntu) package, apport automatically gathers the following command and adds 
it as an attachment:
  usb-devices

  Without this information, bluetooth device patches can't be committed
  upstream.

  Please add this output to apport.

  If needed, I can provide a patch, but it is very straight-forward to
  add.

  The is motivated due to the circumstances surrounding:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546694

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.19
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 27 17:23:18 2016
  InstallationDate: Installed on 2013-10-17 (863 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-04-16 (681 days ago)

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

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

[Touch-packages] [Bug 1483437] Re: Mouse cursor disappears permanently after watching full screen videos

[Christopher M. Penalver]

Vasya Pupkin, to see if this is already resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

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

Title:
  Mouse cursor disappears permanently after watching full screen videos

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes after watching a YouTube video in Google Chrome in full
  screen mode, my mouse pointer disappears. I can move mouse, scroll
  using mouse wheel, click everywhere, but I can't see a cursor. I can
  only guess where it is. This drives me mad because the only solution
  is to restart PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug 11 02:36:08 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13bd]
  InstallationDate: Installed on 2015-05-06 (96 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=b9c815db-e4fe-4e08-8d62-0c68991fa8be ro quiet splash rootfstype=ext4 
pcie_aspm=force acpi_osi= vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Tue Aug 11 02:34:47 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1547152] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thierry.fa...@fr.ibm.com 2016-02-29 18:40 EDT---
I am really confused with current status - I took the version as related in 
LP##1398143, added the Ubuntu specific patches from the current ltrace source 
and
- ltrace ps
- ltrace ls
do work properly
make check is however broken mainly because of missing include files ... so I 
need to fix that first.

On current dev tree I found a commit which creates a loop: commit 
6db31e662a7461c23b76c1de7a488e284d2e8613
but without that commit I get a lot of ltrace: trace.c:234: arch_type_alignof: 
Assertion `info->type != info->type' failed.
Aborted (core dumped)

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

Title:
  ltrace is throwing segfault while running any of the userspace command

Status in procps package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-01-25 
01:18:25 ==
  Hi ,

 I Installed Ubuntu16.04 In PowerNV and try to run ltrace ls or
  ltrace ps it will fail with segfault .

  
  Reproducible Step :

  1- Install Ubuntu16.04 in PowerNV or as KVM or as PowerVM
  2- Install ltrace  package
  3- Try to run ltrace with any userspace utility like "ltrace ps"

  Actual Result :

  Throw Seg fault

  Expected :

  LOG

  root@lep8d:~# uname -a
  Linux lep8d 4.3.0-7-generic #18-Ubuntu SMP Tue Jan 19 15:47:35 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@lep8d:~#

  
  root@lep8d:~# ltrace ps
  __printf_chk(1, 0x3fffe4d40028, 0x3fffe4d40038, 0x3fffe4d400e0 
  qsort(0x10017850, 0, 0, 0x3fffe4d400e0)   
   = 
  __gmon_start__(0x3fffe4d4f8df, 47, 0, 0x3fff81c51d68) 
   = 0
  ferror(0x6)   
   = 230428656
  __libc_start_main(0x10017e10, 0x10017df8, 0x3fff81d68f48, 0x3fff81d68f38) 
   = 0x3fff81c1ccb0
  readproctab3(0x10017e10, 24, 0x7000, 0x6c00)  
   = 0x1000dbc1040
  uptime(0x3fffe4d3faf0, 0, 152, 103)   
   = 0x3fffe4d3faf0
  __fpending(0x3fffe4d3faf8, 0, 152, 103)   
   = 0
  strrchr("\037 !"#$%&'()*+,-./0123456789:;<=>"..., '\360') 
   = nil
  escape_command(0x10030f50, 0x3fffe4d3f968, 0, 8)  
   = 0
  setlocale(LC_NUMERIC, 
"hijklmnopqrstuvwxyz{|}~\177\200\201\202\203\204\205\206\207"...)   
   = nil
  select(1, 0x40087468, 0x3fffe4d3fa00, 0)  
   = 1
  __xstat(268534584, "\017", 0x13)  
   = 0
  strncmp("", "unknown", 7) 
   = -455870136
  sigfillset(~<1,3,7-8,12,15,18,20,23-24,28,31,36,39,43,47-48,52,55-63>)
   = 230428768
  getpagesize() 
   = 6
  meminfo(0, 0x100182d0, 0, 0)  
   = 0
  getpagesize( 
  __stack_chk_fail(0, 0x100182d0, 0, 0 
  --- SIGSEGV (Segmentation fault) ---
  strncpy(0, "Signa", 5)
   = 0x10017da8
  dlerror() 
   = "SEGV"
  strcmp("\206 \255\373", 
"\001\002\003\004\005\006\a\b\t\n\v\f\r\016\017\020\021\022\023\024\025\026\027\030\031\032\033\034\035\036\037
 "...Signal 11 (SEGV) caught by ps (procps-ng version 3.3.10).
  ) = 58
  readtask(0, 0, 0x10017de8, 66ps:display.c:66: please report this bug
  ) 
  = 0
  __snprintf_chk(11, 0, 0x3fff81c5175b, 0)  
   = 0x10003e90
  time(0x10003e90)  
   = 30039
  fork()
   = 0
  unexpected breakpoint at 0x3fff81b339a4
  --- SIGSEGV (Segmentation fault) ---
  +++ killed by SIGSEGV +++
  root@lep8d:~#

  
  == Comment: #7 - Thierry Fauck  - 2016-02-17 
14:11:52 ==
  The problem is related to procps-ng 3.3.10
  Upgrade to procps-ng 3.3.11 solves the issue
  Going to Mirror and ask Canonical to 

[Touch-packages] [Bug 1518562] Re: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different from oth

[Launchpad Bug Tracker]

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

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

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

Title:
  package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz',
  which is different from other instances of package
  libfreetype6-dev:i386

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  Done with removing /usr/share/man/man1/freetype-config.1.gz

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6-dev 2.5.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Nov 21 21:32:32 2015
  DuplicateSignature: package:libfreetype6-dev:2.5.2-4ubuntu2:trying to 
overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different 
from other instances of package libfreetype6-dev:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/man/man1/freetype-config.1.gz', which is different from other 
instances of package libfreetype6-dev:i386
  InstallationDate: Installed on 2015-11-14 (6 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: freetype
  Title: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: 
trying to overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is 
different from other instances of package libfreetype6-dev:i386
  UpgradeStatus: Upgraded to wily on 2015-11-14 (6 days ago)

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

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

[Touch-packages] [Bug 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail

[Timo Aaltonen]

another visual regression is thicker underlines in thunderbird showing
threads with unread messages, patched version is good

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

Title:
  Removal of revert_scalable_fonts_metric.patch causes ugliness in
  Claws-Mail

Status in freetype package in Ubuntu:
  New
Status in freetype package in Debian:
  New

Bug description:
  This is mostly a tracking bug for this discussion on ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-February/039224.html

  The following precise-era patch was recently removed from freetype:

  http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/wily/freetype/wily/view/head:/debian/patches-
  freetype/revert_scalable_fonts_metric.patch

  which caused a number of visual effects in various applications.  In
  Emacs, the lines get vertically closer so that more lines are visible
  on screen.  This is subtle and doesn't look too bad otherwise.

  However, in Claws-Mail several negative effects were noticed.  The
  lines in the Summary window are more squished together and the
  characters appear squished too.  This is with Sans 10 font.  This is
  less readable.

  In the Message window it's worse.  There I use Ubuntu  Mono 14.  The
  problem isn't the vertical spacing, but the horizontal spacing.  Now
  there is more space between characters and that actually makes the
  window less readable.

  I will contact the upstream Claws mailing list to see if they have any
  thoughts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libfreetype6 2.6.1-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 18 14:34:57 2016
  Dependencies:
   gcc-6-base 6-20160217-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160217-0ubuntu1
   libpng12-0 1.2.54-1ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1518727] Re: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: a tentar sobreescrever '/usr/share/man/man1/freetype-config.1.gz' partilhado, que é diferente de o

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1518562
   package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different 
from other instances of package libfreetype6-dev:i386

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

Title:
  package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: a
  tentar sobreescrever '/usr/share/man/man1/freetype-config.1.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libfreetype6-dev:i386

Status in freetype package in Ubuntu:
  New

Bug description:
  weiller@weiller-desktop:~$ lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  weiller@weiller-desktop:~$ sudo apt-cache policy libfreetype6
  libfreetype6:
Instalado: 2.5.2-4ubuntu2
Candidato: 2.5.2-4ubuntu2
Tabela de versão:
   *** 2.5.2-4ubuntu2 0
  500 http://br.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  Installed

  Broken

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6-dev 2.5.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Nov 22 13:30:07 2015
  DuplicateSignature: package:libfreetype6-dev:2.5.2-4ubuntu2:a tentar 
sobreescrever '/usr/share/man/man1/freetype-config.1.gz' partilhado, que é 
diferente de outras instâncias do pacote libfreetype6-dev:i386
  ErrorMessage: a tentar sobreescrever 
'/usr/share/man/man1/freetype-config.1.gz' partilhado, que é diferente de 
outras instâncias do pacote libfreetype6-dev:i386
  InstallationDate: Installed on 2015-11-12 (10 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: freetype
  Title: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: a 
tentar sobreescrever '/usr/share/man/man1/freetype-config.1.gz' partilhado, que 
é diferente de outras instâncias do pacote libfreetype6-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1453474] Re: package libfreetype6:i386 2.5.2-2ubuntu3 failed to install/upgrade: package libfreetype6:i386 is already installed and configured

[Steve Langasek]

The attached logs do not provide sufficient information to diagnose and
correct this issue. Closing this report as invalid.

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

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

Title:
  package libfreetype6:i386 2.5.2-2ubuntu3 failed to install/upgrade:
  package libfreetype6:i386 is already installed and configured

Status in freetype package in Ubuntu:
  Invalid

Bug description:
  Tried to install Wine meta package from Ubuntu Software Centre. Not
  sure of the end result. Next morning, saw the system prompting with a
  lot of crashes.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libfreetype6:i386 2.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu3
  Architecture: amd64
  Date: Sun May 10 09:27:48 2015
  DuplicateSignature: package:libfreetype6:i386:2.5.2-2ubuntu3:package 
libfreetype6:i386 is already installed and configured
  ErrorMessage: package libfreetype6:i386 is already installed and configured
  InstallationDate: Installed on 2015-04-28 (11 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: freetype
  Title: package libfreetype6:i386 2.5.2-2ubuntu3 failed to install/upgrade: 
package libfreetype6:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1518586] Re: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: forsøger at overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som er forskellig fra andr

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1518562
   package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/man/man1/freetype-config.1.gz', which is different 
from other instances of package libfreetype6-dev:i386

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

Title:
  package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade:
  forsøger at overskrive delt '/usr/share/man/man1/freetype-
  config.1.gz', som er forskellig fra andre instanser af pakken
  libfreetype6-dev:i386

Status in freetype package in Ubuntu:
  New

Bug description:
  Happened during while this command executed:
  sudo apt-get install libxft-dev:i386

  Følgende NYE pakker vil blive installeret:
libfreetype6-dev:i386
  0 opgraderes, 1 nyinstalleres, 0 afinstalleres og 5 opgraderes ikke.
  14 ikke fuldstændigt installerede eller afinstallerede.
  0 B/633 kB skal hentes fra arkiverne.
  Efter denne handling, vil 3.551 kB yderligere diskplads være brugt.
  (Læser database ... 267671 filer og kataloger installeret i øjeblikket.)
  Gør klar til at udpakke .../libfreetype6-dev_2.5.2-4ubuntu2_i386.deb ...
  Udpakker libfreetype6-dev:i386 (2.5.2-4ubuntu2) ...
  dpkg: fejl under behandling af arkivet 
/var/cache/apt/archives/libfreetype6-dev_2.5.2-4ubuntu2_i386.deb (--unpack):
   forsøger at overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som 
er forskellig fra andre instanser af pakken libfreetype6-dev:i386
  dpkg-deb: fejl: underproces indsæt blev dræbt af signal (Kanalen blev brudt)
  Behandler udløsere for doc-base (0.10.6) ...
  Behandler udløsere for man-db (2.7.4-1) ...
  Der opstod fejl under behandlingen:
   /var/cache/apt/archives/libfreetype6-dev_2.5.2-4ubuntu2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  john@john-Aspire-5733Z:~$

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libfreetype6-dev 2.5.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Nov 21 14:36:42 2015
  DuplicateSignature: package:libfreetype6-dev:2.5.2-4ubuntu2:forsøger at 
overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som er forskellig 
fra andre instanser af pakken libfreetype6-dev:i386
  ErrorMessage: forsøger at overskrive delt 
'/usr/share/man/man1/freetype-config.1.gz', som er forskellig fra andre 
instanser af pakken libfreetype6-dev:i386
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: freetype
  Title: package libfreetype6-dev 2.5.2-4ubuntu2 failed to install/upgrade: 
forsøger at overskrive delt '/usr/share/man/man1/freetype-config.1.gz', som er 
forskellig fra andre instanser af pakken libfreetype6-dev:i386
  UpgradeStatus: Upgraded to wily on 2015-10-28 (24 days ago)

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

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

[Touch-packages] [Bug 1550719] Re: Add output of usb-devices when ubuntu-bug linux or apport-collect'ing existing report affecting linux (Ubuntu)

[Jeremy]

I agree with Pilot6 but can this info be used to fix the Atheros
bluetooth issue with 0cf3:3004 with some being Rome chipsets like in
this bug report

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1542743

The older chipsets like I have use ath3k to load the firmware from
/lib/firmware/ar3k/ and the newer ones(Rome) use btusb to load the
firmware from /lib/firmware/qca/

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

Title:
  Add output of usb-devices when ubuntu-bug linux or apport-collect'ing
  existing report affecting linux (Ubuntu)

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  What is expected to happen is when an original reporter files a report via a 
terminal:
  ubuntu-bug linux

  or performs an apport-collect to a report that is affecting tbe linux 
(Ubuntu) package, apport automatically gathers the following command and adds 
it as an attachment:
  usb-devices

  Without this information, bluetooth device patches can't be committed
  upstream.

  Please add this output to apport.

  If needed, I can provide a patch, but it is very straight-forward to
  add.

  The is motivated due to the circumstances surrounding:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546694

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.19
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 27 17:23:18 2016
  InstallationDate: Installed on 2013-10-17 (863 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-04-16 (681 days ago)

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

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

[Touch-packages] [Bug 1485622] Re: [needs-packaging] Import libzmq5-dev from Debian.

[Launchpad Bug Tracker]

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

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

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

Title:
  [needs-packaging] Import libzmq5-dev from Debian.

Status in zeromq3 package in Ubuntu:
  Confirmed

Bug description:
  Per connection permissions are very difficult to do with ZMQ 4.0.4,
  which is the current state of the libzmq3-dev package.  The current
  stable release for ZMQ is 4.1.3, which includes the zmq_msg_gets
  function which exposes the individual authentication information.  The
  4.1 release has been packaged as libzmq5-dev in the Debian unstable
  release (https://packages.debian.org/experimental/libzmq5-dev) and it
  would be highly useful if it could be made available in Ubuntu.

  Thanks,
  Charlie West

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

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

[Touch-packages] [Bug 1470700] Re: QNetworkAccessManager hangs when in flight mode

[Lorn Potter]

Just verified using the test app that this is fixed on:

phablet@ubuntu-phablet:~/1470700$ system-image-cli -i
current build number: 377
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-03-01 09:20:40
version version: 377
version ubuntu: 20160227
version device: 20160112
version custom: 20160227

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

Title:
  QNetworkAccessManager hangs when in flight mode

Status in Canonical System Image:
  Fix Committed
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Testing the fix:

  - Update rc-proposed (vivid) to citrain device-upgrade 32 
  - Optional: If you want to test using the 'generic' bearer plugin instead of 
the Network Manager bearer, either do not upgrade ubuntu-touch-session or move 
away the file /etc/profile.d/qt_networkmanager_bearer.sh
  - Reboot

  ---

  When my phone is in flight mode, HTTP requests made using
  QNetworkAccessManager seem to hang rather than erroring out
  immediately.

  From my tests, it looks like the HTTP request is blocked until the
  flight mode is disabled and a network connection is reestablished.
  This is contrary to the documentation, which states:

  """If the network is not accessible the network access manager will
  not process any new network requests, all such requests will fail with
  an error. Requests with URLs with the file:// scheme will still be
  processed."""

  http://doc.qt.io/qt-5/qnetworkaccessmanager.html#networkAccessible-
  prop

  By running strace on my test program, it doesn't even look like it
  attempts to open a TCP connection when blocked in flight mode.

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

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

[Touch-packages] [Bug 1551464] [NEW] apt-get sources should support TLS SNI (server name)

[TJ Pusateri]

Public bug reported:

There needs to be an option in apt source.list entries to specify the
server name to be used by TLS for the Server Name Indication (SNI).

The openSSL equivalent is '-servername'.

Currently, when accessing sources over https when multiple names are
used on the same IP address, there is no way to specify which server
name should be used and so the default name is always used.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.11
ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Mon Feb 29 17:25:22 2016
InstallationDate: Installed on 2016-02-26 (3 days ago)
InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  apt-get sources should support TLS SNI (server name)

Status in apt package in Ubuntu:
  New

Bug description:
  There needs to be an option in apt source.list entries to specify the
  server name to be used by TLS for the Server Name Indication (SNI).

  The openSSL equivalent is '-servername'.

  Currently, when accessing sources over https when multiple names are
  used on the same IP address, there is no way to specify which server
  name should be used and so the default name is always used.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.11
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb 29 17:25:22 2016
  InstallationDate: Installed on 2016-02-26 (3 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

[Tony Espy]

Re-tested on arale ( rc-proposed - 258 ) with bluez 5.37 ( from silo 39
) and I'm able to terminate a call from the headset.

Re-tested on krillin ( rc-proposed - 419 ) with bluez 5.37 ( same silo )
and I'm also able to terminate the call from the headset.

Note - I also installed pulseaudio from silo 47, which fixes a
regression in rc-proposed on arale and krillin.

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

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

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

[Touch-packages] [Bug 1085766] Re: /var/log/upstart/ureadahead.log contains garbage

[Jason Gerard DeRose]

This problem seems to exist currently on both 15.10 and Xenial

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

Title:
  /var/log/upstart/ureadahead.log contains garbage

Status in linux package in Ubuntu:
  Fix Released
Status in ureadahead package in Ubuntu:
  Fix Released

Bug description:
  After an upgrade to Raring (as of today) from Quantal I'm seeing tons
  of these in /var/log/upstart/ureadahead.log:

  Counted 8 CPUs

  ureadahead:  ��&a��w: Ignored relative path
  ureadahead:  : Ignored relative path
  ureadahead:  �=%���n�T9: Ignored relative path
  ureadahead:  �=%v9T9: Ignored relative path
  ureadahead:  �=%���U�Ek�: Ignored relative path
  ureadahead:  �=%���`�a: Ignored relative path

  
  (the boot was wonderfully fast - not sure if that's because ureadahead was 
working well or if it's because it didn't do anything).

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ureadahead 0.100.0-12build1
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Uname: Linux 3.7.0-4-generic x86_64
  ApportVersion: 2.6.3-0ubuntu2
  Architecture: amd64
  Date: Mon Dec  3 02:06:14 2012
  InstallationDate: Installed on 2012-07-17 (138 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120717)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: Upgraded to raring on 2012-12-02 (0 days ago)

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

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

[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects

[Konrad Zapałowicz]

>From a quick assessment I agree that the root cause might be a lack of
"key up" event as this would explain the repetitions.

** Tags added: ubuntu-classic

** Tags added: ubuntu-touch

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

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

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

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

[Touch-packages] [Bug 1550846] Re: package identification is awful

[Brian Murray]

Addressing the specific issue of not being able to use "ubuntu-bug
linux", I've tried to recreate on two systems running xenial and a fresh
install of xenial and was unsuccessful. We can see that apport in
appor/ui.py has special casing for linux.

391 def run_report_bug(self, symptom_script=None):
392 '''Report a bug.
...
 441 # "Do what I mean" for filing against "linux"
 442 if self.options.package == 'linux':
 443 self.cur_package = apport.packaging.get_kernel_package()

Then in apport/packaging.py we have:

621 def get_kernel_package(self):
 622 '''Return the actual Linux kernel package name.
 623 
 624 This is used when the user reports a bug against the "linux" 
package.
 625 '''
 626 # TODO: Ubuntu specific
 627 return 'linux-image-' + os.uname()[2]

Do you have linux-image-4.4.0-2-generic installed?


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

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

Title:
  package identification is awful

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Recently I reported a bug against the kernel - apport made this very
  difficult.

  The instructions at 
  clearly state that the correct thing to do is to report kernel bugs
  against the package "linux".  That does not work.

  "ubuntu-bug linux" reports that linux is not installed!

  After some head-scratching I tried "ubuntu-bug linux-image", that also
  failed.  It did finally work with "ubuntu-bug linux-image-generic",
  but that is not an obvious choice *and it is contrary to the
  instructions*.  The obvious choice was "ubuntu-bug kernel" (which I
  tried first) that also failed.

  So, I tried to report a bug against ubuntu-bug with "ubuntu-bug
  ubuntu-bug", not installed!  According to the web site
   ubuntu-bug does not belong to
  any package!  OK it is a link.  Try again with the real binary name;
  apport-bug is not installed either!

  If you want feedback from ordinary users, bugs in the bug reporting
  system are serious.

  When apport is given a name that is not a package name it could follow a few 
simple steps to at lest provide hints to user; 
  "ls -l $(which ubuntu-bug)" shows that it is a link, 
  "ls -l --dereference $(which ubuntu-bug)" shows what it links to, and
  "dpkg-query --search $(ls  --dereference $(which ubuntu-bug))" even reports 
"apport: /usr/bin/ubuntu-bug".  
  That would be a useful clue to most users.  Note, "dpkg-query --search 
ubuntu-bug" is less useful.  

  As for kernel bugs, it should at least behave as documented.  Please
  add an extra line of code so that as a special case both "ubuntu-bug
  linux" and "ubuntu-bug kernel" work.

  There have been many times that apport has stated that a bug could not
  be reported and I had believed that it was because there were non-
  standard packages installed, now I am not so sure.

  TIA

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.19.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb 28 13:06:32 2016
  InstallationDate: Installed on 2016-02-03 (24 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160202)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550719] Re: Add output of usb-devices when ubuntu-bug linux or apport-collect'ing existing report affecting linux (Ubuntu)

[Pilot6]

Christopher,

I do not see any privacy concerns at all. The output just lists the devices 
with the additional information.
The most private that can be there is a serial number of some devices, like 
Broadcom.

But it can be seen in dmesg either way. So it adds nothing new in this
regard.

The problem is that if someone forgets to get the output, a bug will
never be fixed upstream.

Marcel Holtman is very strict with his rules. And I agree with him.

Threre is very many USB devices and the kernel filters it not only by
PID & VID.

If we commit some device without Cls, Sub, Prot fields, then it will be
impossible to re-arrange it later, if needed.

The change is very easy and the output is small enough. So I see no
reasons not to add it.

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

Title:
  Add output of usb-devices when ubuntu-bug linux or apport-collect'ing
  existing report affecting linux (Ubuntu)

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  What is expected to happen is when an original reporter files a report via a 
terminal:
  ubuntu-bug linux

  or performs an apport-collect to a report that is affecting tbe linux 
(Ubuntu) package, apport automatically gathers the following command and adds 
it as an attachment:
  usb-devices

  Without this information, bluetooth device patches can't be committed
  upstream.

  Please add this output to apport.

  If needed, I can provide a patch, but it is very straight-forward to
  add.

  The is motivated due to the circumstances surrounding:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546694

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.19
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 27 17:23:18 2016
  InstallationDate: Installed on 2013-10-17 (863 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-04-16 (681 days ago)

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

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

[Touch-packages] [Bug 1506544]

[Libreoffice-commits]

Bjoern Michaelsen committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=c0da1080b61a1d51654fc34fdaeba373226065ff

lp#1506544 tdf#92458: default to breeze theme on unity desktops

It will be available in 5.2.0.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  Change default Theme for LibreOffice to Breeze for Ubuntu 16.04

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Breeze has a much more pleasing appearance and is better maintained
  than the human theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1506544/+subscriptions

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

[Touch-packages] [Bug 1551450] [NEW] ich weis nicht

[jasmin]

Public bug reported:

hallo   ich denke  das mein computer hat virus   : dailer  , proxy ,
remote virus ,boot virus ,recycle bin ,concurent boot . und magen und
darm krebs  lol  shönen tag

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb 29 23:07:04 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3802]
InstallationDate: Installed on 2016-02-29 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: LENOVO 20240
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=feb1a3b2-448e-45cc-9447-409b3eb88dda ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 82CN23WW(V2.03)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo G505
dmi.board.vendor: LENOVO
dmi.board.version: 3193Std
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G505
dmi.modalias: 
dmi:bvnLENOVO:bvr82CN23WW(V2.03):bd09/27/2013:svnLENOVO:pn20240:pvrLenovoG505:rvnLENOVO:rnLenovoG505:rvr3193Std:cvnLENOVO:ct10:cvrLenovoG505:
dmi.product.name: 20240
dmi.product.version: Lenovo G505
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Feb 29 22:58:25 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3~trusty1

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


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

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

Title:
  ich weis nicht

Status in xorg package in Ubuntu:
  New

Bug description:
  hallo   ich denke  das mein computer hat virus   : dailer  , proxy ,
  remote virus ,boot virus ,recycle bin ,concurent boot . und magen und
  darm krebs  lol  shönen tag

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb 29 23:07:04 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3802]
  InstallationDate: Installed on 2016-02-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20240
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=feb1a3b2-448e-45cc-9447-409b3eb88dda ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 82CN23WW(V2.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G505
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193Std
  dmi.chassis.asset.tag: No Asset Tag
  

[Touch-packages] [Bug 1534835] Re: Reset device isn't reseting password

[Pat McGowan]

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

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

Title:
  Reset device isn't reseting password

Status in Canonical System Image:
  Incomplete
Status in system-image package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash the phone with latest rc-proposed
  2. run through the wizzard setting a pin
  3. run through the edge demo
  4. Open system settings
  5. Select Reset Device
  6. Then Reset Everything
  7. Run through the wizard again

  EXPECTED:
  I expect to be asked for a pin/password again

  ACTUAL:
  I am not asked for pin/password

  Also I can't remember being asked for my wifi password again either
  But will double check this Monday Morning.

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

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

[Touch-packages] [Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-2ubuntu1

---
systemd (229-2ubuntu1) xenial; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.
- systemd.postinst: Migrate mountall specific fstab options to standard
  util-linux "nofail" option.
- systemctl: Don't forward telinit u to upstart. This works around
  upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
  that changes to point to systemd during the upgrade. This avoids running
  systemd during a dist-upgrade. (LP: #1430479)
- Provide shutdown fallback for upstart. (LP: #1370329)
- Break lvm (<< 2.02.133-1ubuntu1) and remove our dummy /etc/init.d/lvm2
  on upgrades, as it's shipped by lvm2 now.
- Make udev break on mdadm << 3.3-2ubuntu3, as udev's init script dropped
  the "Provides: raid-mdadm".
- Clean up /var/log/udev on upgrade (which is written under upstart, but
  not under systemd). (LP: #1537211)
- Migrate existing s390x network configuration to new names. (LP: #1526808)
- systemd.postinst: Bump Version comparison for migrating the UTC setting
  from /etc/default/rcS to /etc/adjtime, to run it for upgrades to 16.04.

systemd (229-2) unstable; urgency=medium

  * time-util: map ALARM clockids to non-ALARM clockids in now(), to work on
architectures which don't support CLOCK_BOOTTIME_ALARM. Fixes FTBFS on
many architectures.
  * debian/systemd.postinst: Add missing newline to /etc/adjtime migration.
(See #699554)
  * debian/systemd.postinst: Only try to enable tmp.mount if we actually
copied it to /etc. Don't try to enable a generated unit. (LP: #1545707)
  * debian/tests/boot-and-services: Increase timeouts of test_bash_crash from
5 to 10 seconds, and sync the journal after every iteration.
  * debian/extra/checkout-upstream: Try again after one minute if git checkout
fails, to avoid failures from transient network errors.
  * debian/tests/systemd-fsckd: Use grub.d/50-cloudimg-settings.cfg as a
template for generating our custom one instead of 90-autopkgtest.cfg. The
latter does not exist on non-x86 architectures and is not relevant for
this test.
  * debian/tests/boot-and-services: Skip journal test for test_bash_crash when
running against upstream, as this currently fails most of the time. To be
investigated.
  * debian/tests/networkd: Skip test_coldplug_dhcp_ip6 when running against
upstream, as this is brittle there. To be investigated.
  * debian/tests/bootchart: Skip test if bootchart is not available or
testing in upstream mode. bootchart got removed from master and will be
moved to a separate repository.
  * debian/tests/boot-and-services: Show verbose journal output on failure in
nspawn test, and sync journal before.
  * Move systemd-coredump socket and service into systemd-coredump binary
package.
  * Revert changing the default core dump ulimit and core_pattern. This
completely breaks core dumps without systemd-coredump. It's also
contradicting core(8). (Closes: #815020)
  * Fix addresses for type "sit" tunnels. (Closes: #816132)
  * networkd: Go back to letting the kernel handle IPv6 router advertisements,
as networkd's own currently has too many regressions. Thanks to Stefan
Lippers-Hollmann for investigating this! (Closes: #814566,
#814667, #815586, #815884, #815793)

 -- Martin Pitt   Sun, 28 Feb 2016 22:58:06
+0100

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

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

Title:
  Error message "Operation failed: No such file or directory" on
  installing/reconfiguring systemd

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
  installing/reconfiguring it I'm getting this output (the first error
  has already its own bug report here:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):

  root@ubuntu:~# dpkg-reconfigure systemd
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Operation failed: No such file or directory

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

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

[Touch-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

[Tony Espy]

** Branch linked: lp:~bluetooth/bluez/new-rel-5-37-plus-touch-xenial-
sync

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

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

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

[Touch-packages] [Bug 1550148] Re: Only tapping on left part of the 'To:' field can place the cursor into the inputting field.

[Pat McGowan]

This changed since the last update, was it intentional?

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: messaging-app (Ubuntu)
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

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

Title:
  Only tapping on left part of the 'To:' field can place the cursor into
  the inputting field.

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  New

Bug description:
  ~$ system-image-cli  -i
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-26 03:27:27
  version version: 267
  version ubuntu: 20160225
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  
  Reproduce steps:
  Step 1.Open the messaging application.
  Step 2.Swipe up to create a new message.
  Step 3.Type the name of the contact to send to in the To.. field.


  Actual result:
  Only tapping on left part of the field can place the cursor into the 
inputting field.

  Expected result:Tapping on left or right part of the field can place
  the cursor into the inputting field.

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

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend

[kevin gunn]

adding u-s-c as I'm not sure unity8 will even be involved here

** Also affects: unity-system-compositor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-system-compositor (Ubuntu)
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

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

Title:
  Sometimes devices don't suspend

Status in Canonical System Image:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet: 
  System State Requests:
Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

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

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

[Touch-packages] [Bug 1551115] Re: "Password incorrect" after wakeup from suspend

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

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

Title:
  "Password incorrect" after wakeup from suspend

Status in unity package in Ubuntu:
  New

Bug description:
  Everytime I suspend my vanilla Ubuntu 15.10 (upgraded from clean
  15.04) I have the same issue: the login screen after I wake up my
  laptop says my password is incorrect, which is not true. I use two
  keyboard layouts (Croatian and English) and don't use any special
  characters, so I chose a simple password for this - all of the letters
  are at the same place on both of those keyboard layouts!

  The background image on the login screen is also not loaded completely
  after the computer was suspended - it loads only 50% or so, and the
  rest of the image is filled with grey.

  I tried to switch to both of my keyboard layouts and the same message
  appears: Incorrect password, please try again.

  Then I tried to suspend it again from the menu at the upper-right
  corner, but it refuses to suspend from there. Each time I have to
  manually turn off my laptop by pressing and holding the power-off
  button. After the same login screen appears, (but this time it's NOT
  after the laptop was suspended) I have no problems to login.

  It's also not a caps lock issue with my password. And when I don't
  suspend my laptop, open tty1, I could login normally.

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

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

[Touch-packages] [Bug 1549894] Re: No audio while recording video

[Pat McGowan]

On an E4.5 I hear audio but its at an extremely low volume level
On the MX4 its fine

** Also affects: camera-app (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  No audio while recording video

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  New

Bug description:
  Using the camera app and recording video, no audio is recorded in the video.
  I tested on 1080p, 720p and 480p resolution.
  Ubuntu Phone version: OTA 9.1
  Hardware: Aquaris E5

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

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

[Touch-packages] [Bug 1550831] Re: btrfs RAID on USB drives mounted multiple times

[Brian Murray]

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  btrfs RAID on USB drives mounted multiple times

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a btrfs RAID5 on 9 external USB3 drives. When I started the 16.04 
beta1 Lubuntu live CD, the btrfs volume (named Backup) was mounted 8 times:
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sdk1 at 
/media/lubuntu/Backup on behalf of uid 999
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sdj1 at 
/media/lubuntu/Backup1 on behalf of uid 999
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sdi1 at 
/media/lubuntu/Backup2 on behalf of uid 999
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sdh1 at 
/media/lubuntu/Backup3 on behalf of uid 999
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sdf1 at 
/media/lubuntu/Backup4 on behalf of uid 999
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sde1 at 
/media/lubuntu/Backup5 on behalf of uid 999
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sdc1 at 
/media/lubuntu/Backup6 on behalf of uid 999
  /var/log/syslog:Feb 28 00:45:51 lubuntu udisksd[2620]: Mounted /dev/sdb1 at 
/media/lubuntu/Backup7 on behalf of uid 999

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu3 [modified: usr/sbin/update-initramfs]
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CurrentDesktop: LXDE
  Date: Sun Feb 28 01:02:46 2016
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend

[Pat McGowan]

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

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

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

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

Title:
  Sometimes devices don't suspend

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

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet: 
  System State Requests:
Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

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

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

[Touch-packages] [Bug 1549256] Re: UbuntuTestCase's flick() function is unreliable, does not always flick a Flickable

[Pat McGowan]

** No longer affects: canonical-devices-system-image

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

Title:
  UbuntuTestCase's flick() function is unreliable, does not always flick
  a Flickable

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  revision 1864

  System setup: Vivid + Overlay PPA (i.e. same as phones/tablets)

  libqt5qml5:
    Installed: 5.4.1-1ubuntu11~overlay3
  libqt5core5a:
    Installed: 5.4.1+dfsg-2ubuntu11~vivid4

  UbuntuTestCase provides a flick() function whose main purpose is to
  produce a flick event when executed on Flickable.

  I noticed that this does not always happen, causing flakiness of some
  of the UITK tests (in my case, it's the Scrollbar/ScrollView tests I'm
  working on)

  Here is a test case that reproduces the issue, once every 10-200 runs,
  depending on the configuration (I use a simple script to run it until
  it fails)

  Please note that uncommenting the debug lines such as onMovingChanged
  onFlickingChanged will make it harder to reproduce the bug.

  Enabling QT_LOGGING_RULES="qt.quick.mouse.debug=true" or
  onContentYChanged will make it even harder.

  Since I already went through the effort, I'm posting here the debug log 
coming from the failed and successful runs:
  - Typical failed run ---> http://pastebin.ubuntu.com/15186789/ Note how 
"flicking" never becomes true
  - Typical successful run ---> http://pastebin.ubuntu.com/15186784/

  - Failed test with qt.quick.mouse.debug=true  --> 
http://pastebin.ubuntu.com/15186851/
  - Successful test with qt.quick.mouse.debug=true -> 
http://pastebin.ubuntu.com/15186853/

  Here's the code I used to reproduce the bug:

  import QtQuick 2.4
  import QtTest 1.0
  import Ubuntu.Test 1.0
  import Ubuntu.Components 1.3
  import Ubuntu.Components.Styles 1.3
  import QtQml.Models 2.1

  Item {
  id: main
  width: units.gu(50)
  height: units.gu(100)

  SignalSpy {
  id: signalSpy
  }
  SignalSpy {
  id: anotherSignalSpy
  }

  Item {
  anchors.fill: parent
  Item {
  width: units.gu(20)
  height: units.gu(30)
  property alias flickable: freshFlickable
  Flickable {
  id: freshFlickable
  anchors.fill: parent
  contentHeight: content.height
  contentWidth: content.width
  clip: true
  //onContentYChanged: console.log(contentY)
  //onMovingChanged: console.log("MOVING", moving)
  //onFlickingChanged: console.log("FLICKING", flicking)
  Rectangle {
  id: content
  width: units.gu(40)
  height: units.gu(200)
  color: "blue"
  }
  }
  }
  }

  UbuntuTestCase {
  name: "FlickBug"
  when: windowShown

  function setupSignalSpy(spy, target, signalName) {
  spy.clear()
  //reset signalName otherwise it will look for the old signalName 
in the new target
  spy.signalName = ""
  spy.target = target
  spy.signalName = signalName
  }

  function test_flickUbuntuTestCase() {
  setupSignalSpy(signalSpy, freshFlickable, "movingChanged")
  flick(freshFlickable, 50, 50, -units.gu(10), -units.gu(10))
  signalSpy.wait()
  compare(signalSpy.count, 1, "No movingChanged signal after 
simulating a flick.")
  }
  }
  }

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

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

[Touch-packages] [Bug 1507829] Re: upowerd crashed with SIGSEGV in malloc_consolidate()

[Launchpad Bug Tracker]

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

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

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

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

Title:
  upowerd crashed with SIGSEGV in malloc_consolidate()

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Gnome 15.10

  Issue occurred after plugging in iPhone, didn't do anything else. Not
  sure if related event, but that was the only thing that I was doing at
  that time.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: upower 0.99.3-1build2
  Uname: Linux 4.3.0-040300rc5-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 19 20:35:15 2015
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2015-09-30 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f7c66c541cb :   mov
0x8(%r12),%r13
   PC (0x7f7c66c541cb) ok
   source "0x8(%r12)" (0xd52ff8bd1560) not located in a known VMA region 
(needed readable region)!
   destination "%r13" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f7c66f99c00 ) at malloc.c:4136
   _int_malloc (av=av@entry=0x7f7c66f99c00 , 
bytes=bytes@entry=4096) at malloc.c:3417
   __GI___libc_malloc (bytes=4096) at malloc.c:2895
   xmlDictCreate () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   xmlInitParserCtxt () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
  Title: upowerd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1551433] [NEW] /etc/init.d/clvm requires cman_tool which isn't provided by any package in Ubuntu 15.10

[Karl-Philipp Richter]

Public bug reported:

`/etc/init.d/clvm` requires `cman_tool` which isn't provided by any
package in Ubuntu 15.10. Furthermore required
`/etc/cluster/cluster.conf` isn't created (with commented default
values) and not documented with a manpage.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: clvm 2.02.122-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
Uname: Linux 4.2.0-32-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 29 22:33:49 2016
InstallationDate: Installed on 2013-10-17 (865 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: lvm2
UpgradeStatus: Upgraded to wily on 2015-11-19 (102 days ago)

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


** Tags: amd64 apport-bug wily

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

Title:
  /etc/init.d/clvm requires cman_tool which isn't provided by any
  package in Ubuntu 15.10

Status in lvm2 package in Ubuntu:
  New

Bug description:
  `/etc/init.d/clvm` requires `cman_tool` which isn't provided by any
  package in Ubuntu 15.10. Furthermore required
  `/etc/cluster/cluster.conf` isn't created (with commented default
  values) and not documented with a manpage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: clvm 2.02.122-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-32-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 29 22:33:49 2016
  InstallationDate: Installed on 2013-10-17 (865 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to wily on 2015-11-19 (102 days ago)

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

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

[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings

[teo1978]

WTF it's been FOUR F***ING YEARS and the problem has only got worse.

Now the workaround in comment 11 no longer works. There's NO WAY to
receive files over bluetooth. They are systematically rejected.

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

Title:
  "Receive files over bluetooth" randomly stops working - plus setting
  should be available under BlueTooth settings

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I often send image files via bluetooth from my android phone to my
  ubuntu PC.

  It worked fine until yesterday, but now I systematically get "the
  remote bluetooth device rejected the request".

  Nothing has changed in the way I transfer files and I'm trying from
  the very same phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-16-generic 3.0.0-16.29
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo   32650 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
     Mixer name : 'Realtek ALC660-VD'
     Components : 'HDA:10ec0660,1043,0011 
HDA:10573055,10431316,00100700'
     Controls  : 25
     Simple ctrls  : 16
  Date: Sun Mar 18 17:55:36 2012
  HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-16-generic N/A
   linux-backports-modules-3.0.0-16-generic  N/A
   linux-firmware1.60.1
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
  UserAsoundrc:
   pcm.!default { type pulse }
   ctl.!default { type pulse }
   pcm.pulse { type pulse }
   ctl.pulse { type pulse }
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Touch-packages] [Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

[Rick R]

I confirm that this is still an issue in Trusty. However, in #1326412,
Dimitri John Ledkov wrote

> This is fixed in utopic, and will not be fixed in trusty. 
> One will have to boot under upstart to dist-upgrade reliable within trusty.

https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1326412

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

Title:
  failure to update libpam-systemd in 14.04 due to missing logind init
  script

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Released
Status in systemd source package in Utopic:
  Fix Released

Bug description:
  Hi,

  while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
  systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
  state. 'apt-get -f install' from within the chroot will not fix it,
  but if the build is made bootable and put into a iso/VM you can
  recover that way in a live session.

  the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm 
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind 
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't 
exist) and not /etc/init/systemd-logind.conf (does exist).
  ?

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
libpam-systemd
  1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/25.2 kB of archives.
  After this operation, 1024 B of additional disk space will be used.
  (Reading database ... 113986 files and directories currently installed.)
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg: trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Our build logs available upon request, but the scripts to setup the chroot to 
recreate it are here:

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh

  
  In a web-search I notice a few others running into the same bug,

  chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
  /%23ubuntu-devel.txt

  someone else's build log:
  https://launchpad.net/~qutim/+archive/qutim/+build/6039800

  launchpad bug #1323575 seems to be a duplicate of this one.

  
  perhaps related to older launchpad bug #1305395 ?

  note we are also suffering from a failure with update-initramfs, not sure of 
the root cause of that one but I thought I'd mention it in case they were 
related, since they both started happening about the same time, a couple weeks 
ago. (launchpad bug #1317602)
  It all worked ok after the inital releases of 14.04, so something to do with 
a package update since then.

  
  thanks,
  Hamish

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

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

[Touch-packages] [Bug 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)

[Valentin Crone]

Ok, now I have tested with Ubuntu 14.10: Pulseaudio 4.0, Linux 3.16,
same problem, so because the PulseAudio version is the same between
Ubuntu 14.04 and Ubuntu 14.10 it seem it's a bug in the kernel module
snd-oxygen :(

It's a regression from Linux 3.13 to Linux 3.16 → 4.4

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

Title:
  No sound on ASUS Xonar DGX Soundcard (16.04)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), 
Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. 
Tested with the app to test speakers, Firefox, VLC, and checked with 
pavucontrol, the progress bar indicate that a sound is played on the card, but 
no sound on the speakers.

  I report this bug because it works on the same version with the
  integrated card of my motherboard. (ASUS H87-PLUS)

  On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all
  defaults params)

  The speakers connected are the Logitech Z9600 (by 3 jacks), and I
  precise that they are correctly plugged in, etc..., it works when I
  connect it to the integrated sound card of my motherboard (and if I
  use Ubuntu 14.04 LTS)

  I don't know if it's a normal development bug, but in doubt I report it.
  Thank you,
  Valentin Crône

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

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

[Touch-packages] [Bug 1547978] Re: Bluetooth does not forward metadata to slave devices.

[Pat McGowan]

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

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

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

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

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

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

Title:
  Bluetooth does not forward metadata to slave devices.

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

Bug description:
  Tested using the bluetooth stereo in a Mitsubishi FUSO Rosa and a Ford
  Territory (both less than three years old, Australian models), using a
  bluetooth-stereo (A2DP) connection.

  With other (Android) devices, the Mitsubishi FUSO Rosa displays
  complete metadata, whilst the Ford Territory displays only basic
  metadata (artist/group and track information).

  bq Aquaris E5 HD Ubuntu Edition:
  * OS build number: OTA-9
  * Ubuntu Image part: 20160123.1
  * Ubuntu build description: Ubuntu 15.04 - armhf (20160123-115651)
  * Device Image part: 20160108-efc96d8
  * Device build description: VEGETA01A-S23A_BQ_L100EN_2009_160123
  * Customization Image part: 20160111-926-36--vivid

  Reproduce:
  - "Pair" Ubuntu mobile device with another device, which has a display and is 
capable of displaying metadata (artist/group, track, album and/or coverart 
information) from bluetooth audio input.
  - Play music on Ubuntu mobile device.

  Result:
  Music plays through slave device, however no metadata is displayed.

  Expectation:
  To be able to see artist/group, track, album and/or coverart information 
whilst listening to music over a bluetooth connection.

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

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

[Touch-packages] [Bug 1546559] Re: Can't set multiple VPN connection properties in rapid succession

[Pat McGowan]

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Can't set multiple VPN connection properties in rapid succession

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  Always. Quickly change three properties.

  What happens:
  Only one property changes

  What should happen:
  All properties should change.

  See dbus monitor log http://pastebin.ubuntu.com/15100164/

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

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

[Touch-packages] [Bug 1547835] Re: ubuntu-bug uploading does not allow to fill in additional info

[Pat McGowan]

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

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

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

Title:
  ubuntu-bug uploading does not allow to fill in additional info

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

Bug description:
  I currently experience an application crash with Telegram. The
  resulting crash file could be uploaded with ubuntu-bug, but the
  message about the web page which should be filled in indicates for me
  that the report is not complete. Shouldn´t there be a way to
  comment/link etc?

  Also I would like to attach a report to an existing bug in Launchpad.
  I currently see no way of doing this.

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

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