[Touch-packages] [Bug 1512956] Re: Update IBus to 1.5.11 on Wily

[Aron Xu]

** Changed in: ibus (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Update IBus to 1.5.11 on Wily

Status in ibus package in Ubuntu:
  In Progress

Bug description:
  newest release of Intellj IDEA does shows a warning:
  "IBus prior to 1.5.11 may cause input problems."

  that's why i request for an update of ibus to that version.

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

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

[Touch-packages] [Bug 1515089] Re: The sound through my onboard soundcard sounds very disorted

[Raymond]

ov 11 04:24:51 hostname kernel: usb 1-5: ep 0x81 - rounding interval to 64 
microframes, ep desc says 80 microframes
Nov 11 04:24:51 hostname kernel: usb 1-6: ep 0x81 - rounding interval to 64 
microframes, ep desc says 80 microframes
Nov 11 04:24:51 hostname kernel: usb 1-6: ep 0x82 - rounding interval to 64 
microframes, ep desc says 80 microframes
Nov 11 04:24:51 hostname systemd[1]: Failed to insert module 'kdbus': Function 
not implemented
Nov 11 04:24:52 hostname kernel: snd_hda_intel :00:1f.3: failed to add i915 
component master (-19)


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

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

Title:
  The sound through my onboard soundcard sounds very disorted

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  The sound through my onboard soundcard sounds very disorted, it does not 
matter wether i turn the volume down or not (even all the way down), but it 
does stop when i "mute" the sound through the graphical user interface. 
  I have alsa-base version 1.0.25+dfsg-0ubuntu5 installed.
  I tried following https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS, but 
unfortunately there are no packages for 15.10 yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adamt  1204 F...m pulseaudio
   /dev/snd/controlC0:  adamt  1204 F pulseaudio
   /dev/snd/controlC1:  adamt  1204 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 11 04:28:40 2015
  InstallationDate: Installed on 2015-11-10 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [System Product Name, Realtek ALC1150, Green Line Out, Rear] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170 PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd09/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1515089/+subscriptions

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

[Touch-packages] [Bug 1515207] [NEW] /bin/login aborted due to pointer double free in libpam.so

[Boyuan Yang]

Public bug reported:

After a system update in xenial on my notebook, I was unable to login
through GDM and tty. After some investigation, I found a probable cause
for this problem: when logging in from getty using /bin/login, the
program would abort. Here comes a example for debugging, I moved
/bin/login to /bin/login.real, and make /bin/login a bash script:

$ cat /bin/login

#!/bin/bash
export MALLOC_CHECK_=1
/bin/login.real "$@"

$ file /bin/login.real
/bin/login.real: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
2.6.32, BuildID[sha1]=e5d2ebf80be6b1a4f2fc0073e7857ccbe3b875a1, stripped

# /bin/login
arch-s400ca.hosiet.me login: hosiet
Password: 
Last login: Wed Nov 11 18:54:52 CST 2015 on UNKNOWN
Welcome to Ubuntu Xenial Xerus (development branch) (GNU/Linux 4.2.5-1-ARCH 
x86_64)

 * Documentation:  https://help.ubuntu.com/

No mail.
*** Error in `/bin/login.real': free(): invalid pointer: 0x0118dd80 ***
/bin/login: line 6:  3452 Aborted /bin/login.real "$@"

--

After using env "MALLOC_CHECK_" to 0, the login will be successful.

After editing the env "MALLOC_CHECK_" to 3 (which is an invalid number),
the detailed output is as follows:

--
arch-s400ca.hosiet.me login: hosiet
Password: 
Last login: Wed Nov 11 19:02:51 CST 2015 on UNKNOWN
Welcome to Ubuntu Xenial Xerus (development branch) (GNU/Linux 4.2.5-1-ARCH 
x86_64)

 * Documentation:  https://help.ubuntu.com/

No mail.
*** Error in `/bin/login.real': free(): invalid pointer: 0x00e42590 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x78c4e)[0x7f3dcbba4c4e]
/lib/x86_64-linux-gnu/libc.so.6(+0x801da)[0x7f3dcbbac1da]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0xf7)[0x7f3dcbbb0947]
/lib/x86_64-linux-gnu/libpam.so.0(pam_set_data+0x49)[0x7f3dcc3217f9]
/lib/x86_64-linux-gnu/security/pam_smbpass.so(pam_sm_setcred+0x50)[0x7f3dc8b39a10]
/lib/x86_64-linux-gnu/libpam.so.0(+0x2dcf)[0x7f3dcc321dcf]
/lib/x86_64-linux-gnu/libpam.so.0(pam_setcred+0x2c)[0x7f3dcc3216fc]
/bin/login.real[0x4031a5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f3dcbb4ca40]
/bin/login.real[0x4042f9]
=== Memory map: 
0040-0040b000 r-xp  08:11 657435 
/bin/login.real
0060a000-0060b000 r--p a000 08:11 657435 
/bin/login.real
0060b000-0060c000 rw-p b000 08:11 657435 
/bin/login.real
00e09000-00e8d000 rw-p  00:00 0  [heap]
7f3dbcfe6000-7f3dbcffc000 r-xp  08:11 1049017
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3dbcffc000-7f3dbd1fb000 ---p 00016000 08:11 1049017
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3dbd1fb000-7f3dbd1fc000 r--p 00015000 08:11 1049017
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3dbd1fc000-7f3dbd1fd000 rw-p 00016000 08:11 1049017
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3dbd22d000-7f3dbd294000 rw-s  08:09 390938 
/var/cache/samba/gencache.tdb
7f3dbd294000-7f3dbd2a r-xp  08:11 1049787
/lib/x86_64-linux-gnu/libnss_files-2.21.so
7f3dbd2a-7f3dbd49f000 ---p c000 08:11 1049787
/lib/x86_64-linux-gnu/libnss_files-2.21.so
7f3dbd49f000-7f3dbd4a r--p b000 08:11 1049787
/lib/x86_64-linux-gnu/libnss_files-2.21.so
7f3dbd4a-7f3dbd4a1000 rw-p c000 08:11 1049787
/lib/x86_64-linux-gnu/libnss_files-2.21.so
7f3dbd4a1000-7f3dbd4ac000 r-xp  08:11 1049001
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
7f3dbd4ac000-7f3dbd6ab000 ---p b000 08:11 1049001
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
7f3dbd6ab000-7f3dbd6ac000 r--p a000 08:11 1049001
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
7f3dbd6ac000-7f3dbd6ad000 rw-p b000 08:11 1049001
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
7f3dbd6ad000-7f3dbd6b5000 r-xp  08:11 1049790
/lib/x86_64-linux-gnu/libnss_compat-2.21.so
7f3dbd6b5000-7f3dbd8b4000 ---p 8000 08:11 1049790
/lib/x86_64-linux-gnu/libnss_compat-2.21.so
7f3dbd8b4000-7f3dbd8b5000 r--p 7000 08:11 1049790
/lib/x86_64-linux-gnu/libnss_compat-2.21.so
7f3dbd8b5000-7f3dbd8b6000 rw-p 8000 08:11 1049790
/lib/x86_64-linux-gnu/libnss_compat-2.21.so
7f3dbd8b6000-7f3dbd8c r-xp  08:11 12176  
/lib/x86_64-linux-gnu/security/pam_gnome_keyring.so
7f3dbd8c-7f3dbdabf000 ---p a000 08:11 12176  
/lib/x86_64-linux-gnu/security/pam_gnome_keyring.so
7f3dbdabf000-7f3dbdac r--p 9000 08:11 12176   

[Touch-packages] [Bug 1515012] Re: SIM not selected in header on incoming call

[Launchpad Bug Tracker]

** Branch linked: lp:~boiko/dialer-app/fix_sim_live_call

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

Title:
  SIM not selected in header on incoming call

Status in Canonical System Image:
  Confirmed
Status in dialer-app package in Ubuntu:
  In Progress

Bug description:
  latest rc-proposed
  When you receive a call, the dialer shows the correct SIM label in the header 
but it is not selected. It should be selected (i.e. should have orange 
highlighting).

  See attached screenshot

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

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

[Touch-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink

[Christopher M. Penalver]

** Tags added: xenial

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1485682

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  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 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782 
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1515012] Re: SIM not selected in header on incoming call

[Gustavo Pichorim Boiko]

** Changed in: dialer-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  SIM not selected in header on incoming call

Status in Canonical System Image:
  Confirmed
Status in dialer-app package in Ubuntu:
  In Progress

Bug description:
  latest rc-proposed
  When you receive a call, the dialer shows the correct SIM label in the header 
but it is not selected. It should be selected (i.e. should have orange 
highlighting).

  See attached screenshot

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

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Alan Pope ]

** Branch linked: lp:~popey/ubuntu-terminal-app/fix-1514519

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  Confirmed
Status in logviewer:
  New
Status in Ubuntu Terminal App:
  In Progress
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1515095] Re: Cannot launch gallery from photo scope

[Dave Morley]

This is in the Custom tarball.

Tested by installing 169 krillin rc-proposed, Tested that images opened.
Install Url-dispatcher which was the other suspect and still the image
opened.

Installed a fresh 170 (the image with just the custom-tarball) and the
image no longer opens from the photo's scope.

I am pushing this over to penk and kyleN

** Changed in: gallery-app (Ubuntu)
   Status: New => Triaged

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

Title:
  Cannot launch gallery from photo scope

Status in gallery-app package in Ubuntu:
  Triaged

Bug description:
  Test Env:
  ~$ system-image-cli -i
  current build number: 171
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 08:12:47
  version version: 171
  version ubuntu: 20151110.1
  version device: 20150821-736d127
  version custom: 2015111

  Steps:
  1. take photos by camera
  2. go to photo scope
  3. tap on photo to preview page
  4. tap on "open" button

  Actual:
  Tapping on open button does nothing

  Expected:
  Should be able to launch gallery app and display the photo

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

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

[Touch-packages] [Bug 1515091] Re: Thumbnail of photo/video displays incorrect size in preview page

[Michi Henning]

Hmmm... I wouldn't call the current behavior "acceptable". The photo
scope shouldn't show a preview image that's too large. The thumbnailer
really has nothing to do with it. It'll produce a thumbnail of pretty
much any size very efficiently. This really is a UI bug in the photo
scope: the screen layout gets messed up by the too-large preview image.
By the looks of things, the photo scope just displays the original image
full size. I haven't verified whether it goes to the thumbnailer to
obtain the image. But, seeing that it is full size, I suspect it is not.

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

Title:
  Thumbnail of photo/video displays incorrect size in preview page

Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  Test Env.
  ~$ system-image-cli -i
  current build number: 171
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 08:12:47
  version version: 171
  version ubuntu: 20151110.1
  version device: 20150821-736d127
  version custom: 2015111

  Steps:
  1. take photos by camera 
  2. go to photo scope
  3. tap on a photo to preview page
  4. check the page

  Actual:
  Thumbnail of photo displays original size in preview page

  Expected:
  Thumbnail of photo should have a fixed size in preview page

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

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

[Touch-packages] [Bug 1513600] Re: [Scopes] Music scope blank using url-dispatcher

[Albert Astals Cid]

How often can you reproduce the 
  url-dispatcher scope://musicaggregator
issue? Every single time or just randomly?

Which device are you using and which image for the device device are you
using?

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

Title:
  [Scopes] Music scope blank using url-dispatcher

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sporadically I get a blank page when I use the url-dispatcher to go to
  the music scope.

  The same issue has been reproduced going to the photos scope.

  After go to the scope I am waiting until the scope header is loaded
  and the loading bar has disappeared.

  To go to both affected scopes we I am doing:
  > url-dispatcher scope://musicaggregator
  > url-dispatcher scope://com.canonical.scopes.photos_photos

  I see a similar behavior when from the music scope I go to an online
  music scope such as "7 digital". What I see is that the 7digital scope
  doesn't show any data. I checked there is internet in the device.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates [mako]

[Pat McGowan]

from the client.log during a check from system settings

[systemimage] Nov 11 08:09:49 2015 (32286) SystemImage dbus main loop starting 
[ubuntu-touch/rc-proposed/ubuntu-pd/mako]
[systemimage] Nov 11 08:09:49 2015 (32286) Mediator created 
[systemimage] Nov 11 08:09:49 2015 (32286) CheckForUpdate(): checking lock test 
and acquire
[systemimage] Nov 11 08:09:49 2015 (32286) CheckForUpdate(): checking lock 
acquired
[systemimage] Nov 11 08:09:49 2015 (32286) Mediator recreated 
[systemimage] Nov 11 08:09:49 2015 (32286) Enter _check_for_update()
[systemimage] Nov 11 08:09:49 2015 (32286) Looking for blacklist: 
https://system-image.ubuntu.com/gpg/blacklist.tar.xz
[systemimage] Nov 11 08:09:49 2015 (32286) [0xb59c0ff0] Requesting group 
download:
https://system-image.ubuntu.com/gpg/blacklist.tar.xz -> 
/var/lib/system-image/keyring.tar.xz
https://system-image.ubuntu.com/gpg/blacklist.tar.xz.asc -> 
/var/lib/system-image/keyring.tar.xz.asc

[systemimage] Nov 11 08:09:49 2015 (32286)
[/com/canonical/applications/download/d2a599a14f254d8ca3971b7921d25464]
Running group download reactor

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

Title:
  Fails to receive OTA updates [mako]

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

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  *Apologies for posting bug here, I cannot find correct location to
  file a bug against release/image/OTA/etc.

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

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

[Touch-packages] [Bug 1451448] Re: bzr fails to build on vivid (release) and trusty (test-rebuild only)

[Vincent Ladeuil]

** Changed in: bzr
   Status: In Progress => Fix Released

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

Title:
  bzr fails to build on vivid (release) and trusty (test-rebuild only)

Status in Bazaar:
  Fix Released
Status in bzr package in Ubuntu:
  Confirmed
Status in python2.7 package in Ubuntu:
  Invalid
Status in bzr source package in Trusty:
  Fix Committed
Status in python2.7 source package in Trusty:
  New
Status in bzr source package in Vivid:
  Fix Released
Status in python2.7 source package in Vivid:
  Invalid
Status in bzr package in Debian:
  Fix Released

Bug description:
  bzr fails to build on vivid (release) and trusty (test-rebuild only)

  various test failures seen, likely exposed by python 2.7.10.

  release:
  https://launchpad.net/ubuntu/+archive/test-rebuild-20150402/+build/7133674

  test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20150501-updates/+build/7375272

  how to validate: successful build. the testsuite is run during the
  build

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

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

[Touch-packages] [Bug 1514928] Re: ListItem outside ListView segfaults

[Launchpad Bug Tracker]

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

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

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

Title:
  ListItem outside ListView segfaults

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

Bug description:
  Reproduce:
  Use the code from the documentation [1] but add selected: true to any 
ListItem.

  What happens:
  UUITK segfaults

  What should happen:
  It should highlight and not crash

  Stack trace:
  http://pastebin.ubuntu.com/13217004/

  Seems selectedList.contains(-1) segfaults for some reason.

  [1] http://pastebin.ubuntu.com/13217263/

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

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Alan Pope ]

** Changed in: ubuntu-terminal-app
   Status: New => In Progress

** Changed in: ubuntu-terminal-app
 Assignee: (unassigned) => Alan Pope  (popey)

** Changed in: ubuntu-terminal-app
   Importance: Undecided => High

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  Confirmed
Status in logviewer:
  New
Status in Ubuntu Terminal App:
  In Progress
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1391286] Re: Fails to generate thumbnail for small videos recorded with camera-app

[Michi Henning]

Pragmatically, there is probably nothing we can do about this, short of
finding someone who is willing to dig into the codec and figure out why
it fails (which, in turn, might involve fixing some problem in the
Android media elements.

For what it's worth, the thumbnailer will recover gracefully from this
kind of failure, in the sense that, once it has tried to produce a
thumbnail for such a video and has failed, it will permanently cache the
failure and not try again until the modification time of the video
changes. In other words, once the thumbnailer has encountered a failure
for such a file, for future requests for a thumbnail of the same file,
it will deliver a failure notification instantly.

Given the potential cost of fixing the problem compared to how often the
problem actually occurs, I'd be inclined to mark this as "won't fix"
because it doesn't happen very often that someone takes a video that
lasts for less than a second.

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

Title:
  Fails to generate thumbnail for small videos recorded with camera-app

Status in Canonical System Image:
  In Progress
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in thumbnailer package in Ubuntu:
  Confirmed

Bug description:
  Videos with less than one sec recorded by camera-app (like when you
  click on the record button and immediately stops the recording
  process) have problems while generating thumbnail. This seems to be a
  problem to gallery-app since if we have one file like this on the
  collection the thumbnails took a long time to generate.

  I added an unit test that seems to fail on this branch:
  lp:~artmello/thumbnailer/thumbnailer-no_thumbnail_video

  Attached a video sample that seems to fail

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

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

[Touch-packages] [Bug 1513600] Re: [Scopes] Music scope blank using url-dispatcher

[Albert Astals Cid]

"I see a similar behavior when from the music scope I go to an online
music scope such as '7 digital'."

Are you using url-dispatcher for that or just clicking on the "new
albums from 7digtal >"?

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

Title:
  [Scopes] Music scope blank using url-dispatcher

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sporadically I get a blank page when I use the url-dispatcher to go to
  the music scope.

  The same issue has been reproduced going to the photos scope.

  After go to the scope I am waiting until the scope header is loaded
  and the loading bar has disappeared.

  To go to both affected scopes we I am doing:
  > url-dispatcher scope://musicaggregator
  > url-dispatcher scope://com.canonical.scopes.photos_photos

  I see a similar behavior when from the music scope I go to an online
  music scope such as "7 digital". What I see is that the 7digital scope
  doesn't show any data. I checked there is internet in the device.

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

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

[Touch-packages] [Bug 1515261] [NEW] package init 1.22ubuntu11 failed to install/upgrade: pre-dependency problem - not installing init (not aturized to anything)

[Vemund Sjøvold Sundal]

Public bug reported:

i updated ubuntu and got some errors under update.
then i had problem turning the pc off, and it said i was not authorized to do 
almost anything

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: init (not installed)
ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.7
Architecture: amd64
Date: Wed Nov 11 14:10:43 2015
DuplicateSignature: package:init:1.22ubuntu11:pre-dependency problem - not 
installing init
ErrorMessage: pre-dependency problem - not installing init
InstallationDate: Installed on 2015-11-11 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
SourcePackage: init-system-helpers
Title: package init 1.22ubuntu11 failed to install/upgrade: pre-dependency 
problem - not installing init
UpgradeStatus: Upgraded to vivid on 2015-11-11 (0 days ago)

** Affects: init-system-helpers (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package init 1.22ubuntu11 failed to install/upgrade: pre-dependency
  problem - not installing init (not aturized to anything)

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  i updated ubuntu and got some errors under update.
  then i had problem turning the pc off, and it said i was not authorized to do 
almost anything

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: init (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  Date: Wed Nov 11 14:10:43 2015
  DuplicateSignature: package:init:1.22ubuntu11:pre-dependency problem - not 
installing init
  ErrorMessage: pre-dependency problem - not installing init
  InstallationDate: Installed on 2015-11-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: init-system-helpers
  Title: package init 1.22ubuntu11 failed to install/upgrade: pre-dependency 
problem - not installing init
  UpgradeStatus: Upgraded to vivid on 2015-11-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1515261/+subscriptions

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

[Touch-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink

[Hannes Bochmann]

No it's not reproducible if I turn off the 3rd monitor which is
connected through DisplayLink.

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1485682

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  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 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782 
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1515095] Re: Cannot launch gallery from photo scope

[Penk Chen]

** Attachment added: "com.canonical.scopes.photos-local_1.26_armhf.click"
   
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1515095/+attachment/4516887/+files/com.canonical.scopes.photos-local_1.26_armhf.click

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

Title:
  Cannot launch gallery from photo scope

Status in gallery-app package in Ubuntu:
  Triaged

Bug description:
  Test Env:
  ~$ system-image-cli -i
  current build number: 171
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 08:12:47
  version version: 171
  version ubuntu: 20151110.1
  version device: 20150821-736d127
  version custom: 2015111

  Steps:
  1. take photos by camera
  2. go to photo scope
  3. tap on photo to preview page
  4. tap on "open" button

  Actual:
  Tapping on open button does nothing

  Expected:
  Should be able to launch gallery app and display the photo

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

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

[Touch-packages] [Bug 1515095] Re: Cannot launch gallery from photo scope

[Penk Chen]

Removed 'image://thumbnailer/' prefix from uri fixed this.

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

Title:
  Cannot launch gallery from photo scope

Status in gallery-app package in Ubuntu:
  Triaged

Bug description:
  Test Env:
  ~$ system-image-cli -i
  current build number: 171
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 08:12:47
  version version: 171
  version ubuntu: 20151110.1
  version device: 20150821-736d127
  version custom: 2015111

  Steps:
  1. take photos by camera
  2. go to photo scope
  3. tap on photo to preview page
  4. tap on "open" button

  Actual:
  Tapping on open button does nothing

  Expected:
  Should be able to launch gallery app and display the photo

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

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

[Touch-packages] [Bug 1515282] [NEW] The name of the wily's package break the search of apt-get

[VinsS]

Public bug reported:

Related to: http://packages.ubuntu.com/wily/libopencv-core-dev

Hi,

I've these depends in my lib

-
Package: liboqapy-iproc0
Architecture: any
Section: libs
Priority: optional
Depends: ${misc:Depends},
${shlibs:Depends},
libcv2.3, 
libcvaux2.3, 
libhighgui2.3
Description: Image 
--

I can install it on vivid but not on wily.

vincent@vincent:~$ sudo LC_CTYPE=LangC apt-get install liboqapy-iproc0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 liboqapy-iproc0 : Depends: libopencv-core2.4 but it is not installable
   Depends: libopencv-highgui2.4 but it is not installable
   Depends: libopencv-imgproc2.4 but it is not installable
E: Unable to correct problems, you have held broken packages.

vincent@vincent:~$ sudo LC_CTYPE=LangC apt-get install libopencv-core2.4
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package libopencv-core2.4 is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libopencv-core2.4v5:i386 libopencv-core2.4v5

E: Package 'libopencv-core2.4' has no installation candidate
-

I can rebuild the package of  liboqapy-iproc (this is on my own ppa) but what 
name do I use instead of:
libcv2.3, 
libcvaux2.3, 
libhighgui2.3
?

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

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

Title:
  The name of the wily's package break the search of apt-get

Status in opencv package in Ubuntu:
  New

Bug description:
  Related to: http://packages.ubuntu.com/wily/libopencv-core-dev

  Hi,

  I've these depends in my lib

  -
  Package: liboqapy-iproc0
  Architecture: any
  Section: libs
  Priority: optional
  Depends: ${misc:Depends},
  ${shlibs:Depends},
  libcv2.3, 
  libcvaux2.3, 
  libhighgui2.3
  Description: Image 
  --

  I can install it on vivid but not on wily.
  
  vincent@vincent:~$ sudo LC_CTYPE=LangC apt-get install liboqapy-iproc0
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   liboqapy-iproc0 : Depends: libopencv-core2.4 but it is not installable
 Depends: libopencv-highgui2.4 but it is not installable
 Depends: libopencv-imgproc2.4 but it is not installable
  E: Unable to correct problems, you have held broken packages.

  vincent@vincent:~$ sudo LC_CTYPE=LangC apt-get install libopencv-core2.4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package libopencv-core2.4 is not available, but is referred to by another 
package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
libopencv-core2.4v5:i386 libopencv-core2.4v5

  E: Package 'libopencv-core2.4' has no installation candidate
  -

  I can rebuild the package of  liboqapy-iproc (this is on my own ppa) but what 
name do I use instead of:
  libcv2.3, 
  libcvaux2.3, 
  libhighgui2.3
  ?

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

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

[Touch-packages] [Bug 1436973] Re: konsole crashes on closing due to kuniqueapplication

[Mathew Hodson]

** Package changed: konsole (Ubuntu) => qtbase-opensource-src (Ubuntu)

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Medium => High

** Changed in: qtbase-opensource-src (Ubuntu Wily)
Milestone: ubuntu-15.10 => wily-updates

** Changed in: qtbase-opensource-src (Ubuntu Vivid)
   Importance: Medium => High

** Changed in: qtbase-opensource-src (Ubuntu Wily)
   Importance: Medium => High

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

Title:
  konsole crashes on closing due to kuniqueapplication

Status in KDE Base:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src source package in Vivid:
  Confirmed
Status in qtbase-opensource-src source package in Wily:
  Confirmed

Bug description:
  https://bugs.kde.org/show_bug.cgi?id=344920

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1436973/+subscriptions

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Tony Espy]

@taiebot65

I don't think this is related to bug #1462664.   This is specifically
related to the number of processes watching individual network-manager
access point objects, and the fact that these processes leak match
rules, so they continue to add match rules to dbus for new access
points, but never cleanup the old rules for access points that
disappear.  Also, per an earlier comment, as a vivid fix related to the
ubuntu-software-center relaxed the per process dbus match limits to 5000
( from 512 ), when all of these processes max out, the total is
something like 40k rules that DBus has to match for every incoming
message on the bus.

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in location-service package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Tony Espy]

Here's a script that calls dbus-monitor with the correct match rules in
order to catch AccessPointAdded and Removed signals, as well as
PropertiesChanged signals for the Device.Wireless 'AccessPoints'
property.

** Attachment added: "monitor-aps.sh"
   
https://bugs.launchpad.net/ubuntu-rtm/+source/location-service/+bug/1480877/+attachment/4517317/+files/monitor-aps.sh

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in location-service package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1515067] Re: Redunt requests for artist art

[Victor Thompson]

** Changed in: music-app
   Status: New => Confirmed

** Changed in: music-app
 Assignee: (unassigned) => Victor Thompson (vthompson)

** Changed in: music-app
   Status: Confirmed => In Progress

** Branch linked: lp:~vthompson/music-app/fix-1515067

** Changed in: music-app
   Importance: Undecided => Low

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

Title:
  Redunt requests for artist art

Status in Ubuntu Music App:
  In Progress
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  I'm seeing redundant requests in the thumbnailer for every artist. For
  example:

  thumbnailer-service: [00:33:58.397] "artist: Mamady Keïta/Afö (512,512): 
5.732672 [q: 4.476239, d: 1.065771] sec (MISS)"
  thumbnailer-service: [00:33:58.439] "artist: Mamady Keïta/ (512,512): 
5.774881 [q: 3.434976, d: 2.267816] sec (MISS)"

  thumbnailer-service: [00:33:56.041] "artist: Passport/ (512,512): 3.741614 
[d: 3.681184] sec (MISS)"
  thumbnailer-service: [00:33:56.144] "artist: Passport/Passport to Paradise 
(512,512): 3.480054 [d: 3.446207] sec (MISS)"

  thumbnailer-service: [00:34:02.958] "artist: Pink Floyd/The Dark Side Of The 
Moon [2011 - Remaster] (512,512): 10.288417 [q: 6.923973, d: 3.262566] sec 
(MISS)"
  thumbnailer-service: [00:34:04.315] "artist: Pink Floyd/ (512,512): 11.646238 
[q: 10.182878, d: 1.348939] sec (MISS)"

  For every artist, it appears that a request is sent for the artist
  with an empty album title, plus a request for the artist with an album
  title. This is not great because it results in two remote server
  accesses for each artist. This hammers the CPU and the network on the
  phone, as well as the server on dash.ubuntu.com.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Ian Booth]

Stephane, you are right. We can change Juju to use mangle the output of
the cloud-image-query to add "root.tar.xz". Is this guaranteed to always
work for all series / arch? Are there the correct root.tar.xz files on
cloud-image.ubuntu.com ?

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Brad Marshall]

FWIW and a totally expected result, I just downgraded the LXC packages
on these hosts and redeployed, and things came up ok.

$ dpkg-query -W lxc
lxc 1.0.7-0ubuntu0.10

I don't think this changes anything, but just putting it here for
completeness.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 147216] Re: LVM filesystems not mounted at boot

[Anthony Kamau]

Being that I'm still having this issue on Ubuntu 15.10, I can only
conclude that this appears to be a design philosophy at Canonical rather
than a bug.  Logical volumes that are not necessary for system boot
and/or are not on the primary disk where the OS is installed are not
made available / mounted on (re)boot!

It is much better that the system comes up rather than waiting for a
user input at (re)boot.

Case closed, at least for me!

ak.

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

Title:
  LVM filesystems not mounted at boot

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  My system has a root filesystem in an LVM logical volume, backed up by
  two MD RAID-1 arrays.  It fails to boot propertly after upgrading to
  kubuntu gutsy gibbon prerelease (latest packages as of today).  In
  order to boot it, I have to specify the break=mount boot option, then
  subsequently run

  lvm vgscan
  lvm vgchange -a y

  to manually enable the LVM volumes.  I should note that the MD arrays
  are started successfully.

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

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

[Touch-packages] [Bug 1513958] Re: arm64: failure with small objects passed on stack

[Mathew Hodson]

** Changed in: libffi (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  arm64: failure with small objects passed on stack

Status in libffi package in Ubuntu:
  Fix Released
Status in libffi source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  It isn't possible to build newer versions of python-cffi on trusty/arm64 
because it's test cases will fail due to this bug. The thing that's biting me 
is that cloud-archive:liberty is incomplete on arm64, making key packages 
uninstallable on arm64 (e.g. nova-compute).

  Additionally, libffi is used by several languages in Ubuntu (python,
  ruby, haskell, etc), so this may also be causing issues in the closed
  set of Ubuntu/trusty packages. I don't have evidence either way.

  [TestCase]
  Build python-cffi_1.1.2-1ubuntu2 from wily on trusty/arm64. With unfixed 
libffi, the build will fail during dh_auto_test in the
  "TestFFI.test_struct_by_value" test case.

  [Regression Risk]
  The fix is in the aarch64-specific code, so there's a negligible risk of 
regression on other platforms. This exact fix was included in vivid and wily 
and no regressions have been triaged to libffi in those releases.

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

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

[Touch-packages] [Bug 1429140] Re: lxc-net upstart script fails on nonexistent iptables rules

[Mathew Hodson]

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

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

Title:
  lxc-net upstart script fails on nonexistent iptables rules

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

Bug description:
  Hello,

  On Trusty, the stop of lxc-net fails if the iptables rules are not
  present.

  I added “exec >> /tmp/lxc-net.log 2>&1” at the beginning of pre-start
  and post-stop and get:

  iptables: Bad rule (does a matching rule exist in that chain?).

  On Precise, a “|| true” was added to avoid errors.

  I attach a patch to disable exit on failing iptables call.

  Regards.

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

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

[Touch-packages] [Bug 1436973] [NEW] konsole crashes on closing due to kuniqueapplication

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

https://bugs.kde.org/show_bug.cgi?id=344920

** Affects: kde-baseapps
 Importance: High
 Status: Fix Released

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: qtbase-opensource-src (Ubuntu Vivid)
 Importance: Medium
 Status: Confirmed

** Affects: qtbase-opensource-src (Ubuntu Wily)
 Importance: Medium
 Status: Confirmed


** Tags: kubuntu
-- 
konsole crashes on closing due to kuniqueapplication
https://bugs.launchpad.net/bugs/1436973
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu.

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Mathew Hodson]

** Tags added: regression-proposed trusty

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1511704] Re: Xorg crash (probably on window resize)

[nimu]

penalvch, thank you for your help.

I don't want to risk a BIOS update for now, so I cannot tell you if the
bug is somehow BIOS-related.

Instead, I have decided to try an update of my graphics drivers using this repo:
ppa:oibaf/graphics-drivers

This "fixes" the crash problem.

So, while it may still be true, that this bug is somehow BIOS-related,
the fact that I am not experiencing any crashes since I've updated the
graphics drivers suggests that there probably is something wrong with
the graphics drivers that Ubuntu 15.10 uses by default.

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

Title:
  Xorg crash (probably on window resize)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Whole UI crashes and returns to login screen. All open applications
  are closed (the whole session is gone). Crashes happen irregularly but
  seem to be provoked by window resizes or window animations

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 30 12:49:07 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:16c2]
  InstallationDate: Installed on 2015-05-22 (160 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: FUJITSU LIFEBOOK A532
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=cc91c7ea-2cb7-4ac7-ae59-560aa09e6167 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 2.05
  dmi.board.name: FJNBB2A
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion2.05:bd09/28/2012:svnFUJITSU:pnLIFEBOOKA532:pvr:rvnFUJITSU:rnFJNBB2A:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A532
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-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
  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: Fri Oct 30 12:30:17 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1446231] Re: console-setup prompts for keyboard layout during upgrade from Utopic to Vivid desktop

[Mathew Hodson]

** No longer affects: ubiquity (Ubuntu)

** No longer affects: ubiquity (Ubuntu Vivid)

** Changed in: console-setup (Ubuntu)
Milestone: ubuntu-15.04 => None

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

Title:
  console-setup prompts for keyboard layout during upgrade from Utopic
  to Vivid desktop

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Vivid:
  Fix Released

Bug description:
  There is a debconf prompt for keyboard-configuration during an upgrade
  from a stock Utopic in French to Vivid (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: keyboard-configuration 1.108ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 20 14:13:50 2015
  InstallationDate: Installed on 2013-09-03 (593 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515463] [NEW] Broken juju LXC deployments

[Brad Marshall]

Public bug reported:

I've just tried using juju to deploy to a container with trusty-proposed
repo enabled, and I get an error message about 'failed to retrieve the
template to clone'.  The underlying error appears to be:

  tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
  xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
  Error is not recoverable: exiting now;

This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.

The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.

This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file.  You can see what juju is
providing from:

  $ ubuntu-cloudimg-query trusty released amd64 --format %{url}
  
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

>From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
  Installed: 1.0.8-0ubuntu0.1
  Candidate: 1.0.8-0ubuntu0.1
  Version table:
 *** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status

>From the host running juju:
$ apt-cache policy juju-core
juju-core:
  Installed: 1.22.8-0ubuntu1~14.04.1
  Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
  Version table:
 1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
 *** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status

All machine involved are running trusty:

$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04

Please let me know if you need any more information.

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


** Tags: canonical-bootstack

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1393752] Re: missing symbols in libssl1.0.1f-1ubuntu2.7

[Launchpad Bug Tracker]

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

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

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

Title:
  missing symbols in libssl1.0.1f-1ubuntu2.7

Status in openssl package in Ubuntu:
  Expired

Bug description:
  _CONF_new_data is not exported.

  The function definition is still in the headers:

  # grep -r _CONF_new_data /usr/include/
  /usr/include/openssl/conf_api.h:int _CONF_new_data(CONF *conf);

  The library itself does not export the symbol:
  $ readelf -Ws /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 | grep CONF_new
    1540: 0012f63084 FUNCGLOBAL DEFAULT   12 
NCONF_new@@OPENSSL_1.0.0

  LSB Relase:
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

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

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

[Touch-packages] [Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)

[Mathew Hodson]

** Description changed:

- We have released LXC 1.0.7 upstream:
+ We have released LXC 1.0.8 upstream:
  https://linuxcontainers.org/lxc/news
  
  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.
  
  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html
  
  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.
  
  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Medium

** Changed in: lxc (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  New upstream bugfix release 1.0.8 (LXC MRE)

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

Bug description:
  We have released LXC 1.0.8 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

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

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

[Touch-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink

[Christopher M. Penalver]

Hannes Bochmann, as per
http://support.displaylink.com/knowledgebase/articles/641668-known-
issues-with-displaylink-ubuntu-support only two HD monitors are
officially supported.

Despite this, you may be able to seek support from DisplayLink anyways
following http://support.displaylink.com/knowledgebase/articles/757047
-how-can-i-report-ubuntu-issues-to-displaylink . Could you please report
this to them 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/1511244

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1485682

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  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 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782 
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Stéphane Graber]

root.tar.xz images are available for all series and all architectures
and are indeed on cloud-images.ubuntu.com

I've not checked them all myself but after the CPC team told me they
added them to their generated images, I did confirm (through LXD which
uses them) that at least precise, trusty, vivid, wily and xenial are all
available and working on x86 and armhf.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Stéphane Graber]

Note that the only different between root.tar.gz and root.tar.xz is the
last compression step, the uncompressed tarball is the same.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1436952] Re: X crashes on some runs of Kubuntu live image returning in SDDM login

[Mathew Hodson]

** Changed in: xorg (Ubuntu)
Milestone: ubuntu-15.04 => None

** Changed in: xorg (Ubuntu Vivid)
Milestone: ubuntu-15.04 => None

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

Title:
  X crashes on some runs of Kubuntu live image returning in SDDM login

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg source package in Vivid:
  Incomplete

Bug description:
  Running a Kubuntu vivid beta 2 live image on my laptop I get the
  ubituity-dm screen.  I press "Try Kubuntu" and it takes me to the SDDM
  login screen.  Autologin should work and trying the exact same USB
  drive on a different computer it does reliable autologin.  It's also
  reported to work fine on Virtualbox.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Stéphane Graber]

Well, the string returned by ubuntu-cloudimg-query already requires
mangling to be usable with the lxc-ubuntu-cloud template (as we do
inside the ubuntu-cloud template).

As there are no full cloud images compressed using .tar.xz, ubuntu-
cloudimg-query will continue to return .tar.gz and it's up to whatever
piece of software currently mangles its return value to the .root.tar.gz
equivalent to instead mangle it to .root.tar.xz (as I did in the ubuntu-
cloud template).

Anyway, as I said, I'll be changing the tar commands so they don't care
about the compression algorithm, that should make transitioning much
easier.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1436973] Re: konsole crashes on closing due to kuniqueapplication

[Mathew Hodson]

** Bug watch removed: KDE Bug Tracking System #344918
   https://bugs.kde.org/show_bug.cgi?id=344918

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

Title:
  konsole crashes on closing due to kuniqueapplication

Status in KDE Base:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src source package in Vivid:
  Confirmed
Status in qtbase-opensource-src source package in Wily:
  Confirmed

Bug description:
  https://bugs.kde.org/show_bug.cgi?id=344920

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1436973/+subscriptions

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

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Mathew Hodson]

** Changed in: bluez (Ubuntu)
Milestone: vivid-updates => None

** Changed in: pulseaudio (Ubuntu)
Milestone: vivid-updates => None

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Confirmed
Status in pulseaudio source package in Vivid:
  Confirmed

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Touch-packages] [Bug 1473727] Re: No DNS servers after netboot

[Launchpad Bug Tracker]

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

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

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

Title:
  No DNS servers after netboot

Status in resolvconf package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.04 / resolvconf 1.69ubuntu1.1

  When netbooting a xen VM, I see the following output:

   address: 192.168.1.180broadcast: 192.168.1.255netmask:
  255.255.255.0

   gateway: 192.168.1.1  dns0 : 192.168.1.1  dns1   :
  0.0.0.0

  So I know DHCP is working.

  However, resolv.conf doesn't get updated - the interface is set to
  manual as DHCP was handled at the initrd level.

  Please let me know how I can help get this fixed.

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

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

[Touch-packages] [Bug 1515179] Re: [nexus7][bluez5] Unable to pair with Arc Touch Bluetooth

[Yung Shen]

** Description changed:

  Unable to pair arc touch bluetooth mouse with nexus 7.
  
  Steps to reproduce:
  
- 1. install bluez5 stack on nexus7(fresh flashed)
+ 1. install bluez5 stack on nexus7(fresh flashed), instruction: 
https://wiki.ubuntu.com/Bluetooth/TouchBluez5Testing
  2. adb shell into nexus7, then type following commands:
  $ bluetoothctl (entering interactive mode)
  $ discoverable on
  $ pairable on
  $ scan on
  $ devices (to see the device mac that you want to pair)
  $ pair 
  $ trust 
  $ connect 

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

Title:
  [nexus7][bluez5] Unable to pair with Arc Touch Bluetooth

Status in ubuntu-nexus7:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Unable to pair arc touch bluetooth mouse with nexus 7.

  Steps to reproduce:

  1. install bluez5 stack on nexus7(fresh flashed), instruction: 
https://wiki.ubuntu.com/Bluetooth/TouchBluez5Testing
  2. adb shell into nexus7, then type following commands:
  $ bluetoothctl (entering interactive mode)
  $ discoverable on
  $ pairable on
  $ scan on
  $ devices (to see the device mac that you want to pair)
  $ pair 
  $ trust 
  $ connect 

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

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

[Touch-packages] [Bug 1363482] Re: ubuntu-keyring includes 1024D keys

[Colin Watson]

I've added double-signing support to cdimage, and re-signed everything
with both old and new keys.  For good measure I've also updated
https://help.ubuntu.com/community/VerifyIsoHowto.

** Changed in: ubuntu-cdimage
   Status: New => Fix Released

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

Title:
  ubuntu-keyring includes 1024D keys

Status in Ubuntu CD Images:
  Fix Released
Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-keyring as shipped in trusty contains old 1024D keys dating
  back to 2004 which are still being trusted for the main archive:

   % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg | grep 1024D
  pub  1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key 

  pub  1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key 


  Given that newer 4096R keys are present and have been in precise
  (through -updates) and trusty, it seems to be about time to drop the
  older keys. (In the hope that apt does not chose on signatures it
  cannot verify, otherwise the publisher would need to stop signing with
  the old key as well.)

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

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

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

[Phillip Susi]

I just tried a fresh install of 14.04.2 in a vm with a 20 tb virtual
disk and fsck seemed to work fine.  It might be specific to your disk
contents.  If you can reproduce this, please capture an image of the
filesystem metadata with e2image -r ( and bzip2 that ) and attach it and
I can try running on that.

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

Title:
  fsck on 24TB ext4 keeps crashing

Status in e2fsprogs package in Ubuntu:
  Incomplete

Bug description:
  date; fsck -vy /dev/mapper/raid61p1 ;date
  Thu Jul 17 11:54:21 PDT 2014
  fsck from util-linux 2.20.1
  I can't get my ext4 24TB to fsck clean. there came a whole bunch of file stat 
problems after a clean reboot.
  I tried 3 times so far, and each does something like segfault. I looked 
twice, and the errors were different,
  but was able to capture one output. The system has 6GB ram, and it used up 
all the memory. ended up adding 25GB
  of swap as fsck seems to use up a huge amount of memory. After a long while, 
usually after mem use is >90%,
  I come back to see the fsck has crashed and file system is still not clean.

  The reboot was clean and should not  have caused any corruption. the
  system is using ubuntu-14.04

  # uname -a
  Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
  root@gigabyte133:~# 

  I had to use the 64 bit version since the 32 bit version I couldn't get more 
than 15TB file system built and read 
  that there were compatibility problems between 32bit version with the -O 
64bit and the 64 bit version so just
  built the whole thing in 64 bit ubuntu..

  
  e2fsck 1.42.9 (4-Feb-2014)

  
  /dev/mapper/raid61p1 contains a file system with errors, check forced.
  Pass 1: Checking inodes, blocks, and sizes
  Inode 203167820 has compression flag set on filesystem without compression 
support.  Clear? yes

  Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
  fsck.ext4[0x4266f1]
  /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0]
  /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43]
  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670]
  fsck.ext4[0x4100f6]# lsb_release -va
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d]
  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78]
  
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13]
  fsck.ext4[0x4115c4]
  fsck.ext4[0x412699]
  fsck.ext4[0x412761]
  
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9]
  fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8]
  fsck.ext4(e2fsck_run+0x52)[0x40deb2]
  fsck.ext4(main+0xd27)[0x40a0e7]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5]
  fsck.ext4[0x40bde6]
  Thu Jul 17 15:55:01 PDT 2014

  # lsb_release -va
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Jul 19 18:49:32 2014
  InstallationDate: Installed on 2014-07-11 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Stéphane Graber]

Oh yeah, I can see how this is going to be a problem.

I'll look at changing the code path to use auto-detected compression
rather than specific one.

The reason for this change in the first place is that the .tar.gz images
will be deprecated in favor for .tar.xz, so I'd recommend JuJu also
switch to .tar.xz at some point soon (I don't believe the cloud team has
set a timeframe for phasing out tar.gz yet, but it's planned).

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1514350] Re: /usr/bin/history-daemon:*** Error in `/usr/bin/history-daemon': double free or corruption (out): ADDR ***

[Timo Jyrinki]

** Also affects: qtpim-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  /usr/bin/history-daemon:*** Error in `/usr/bin/history-daemon': double
  free or corruption (out): ADDR ***

Status in Canonical System Image:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in qtpim-opensource-src package in Ubuntu:
  New

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

  Rank 4 on errors.u.c, started with 0.1+15.04.20151020.1-0ubuntu1

  See also bug 1513261 which started with the same version

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

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

[Touch-packages] [Bug 1515106] Re: sound was working completely stopped.sound was working then stopped.[LCI43NB, Realtek ALC888, Green Line Out, Rear] No sound at all

[Raymond]

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

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

Title:
  sound was working completely stopped.sound was working then
  stopped.[LCI43NB, Realtek ALC888, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  sound was working then stopped. when i access the sound settings
  window in system settings the window appears transparent and bugging
  out? thank you!!! Love Ubuntu!!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic i686
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  electricdigits   1807 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 10 21:14:33 2015
  InstallationDate: Installed on 2015-10-17 (24 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (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_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  electricdigits   1807 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [LCI43NB, Realtek ALC888, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-10-26 (16 days ago)
  dmi.bios.date: 07/28/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: NBG4310H.86A.0090.2009.0728.1547
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG43NB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE34877-404
  dmi.chassis.type: 3
  dmi.chassis.vendor: LeByte
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrNBG4310H.86A.0090.2009.0728.1547:bd07/28/2009:svnLeByteComputers:pnLCI43NB:pvr:rvnIntelCorporation:rnDG43NB:rvrAAE34877-404:cvnLeByte:ct3:cvr:
  dmi.product.name: LCI43NB
  dmi.sys.vendor: LeByte Computers

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

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

[Touch-packages] [Bug 1195353] Re: SDK should provide support to rearrange items in a ListView

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
   Status: New => Fix Released

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

Title:
  SDK should provide support to rearrange items in a ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
  Fix Released

Bug description:
  For the clock core app, as per design, it is required to implement
  ListView where the user can drag and drop to rearrange the items in
  the ListView. You can see the official wireframe designs at
  http://design.canonical.com/wp-content/uploads/clock_add_city-
  1024x8901.png to see what I meant.

  It would be best if the SDK can provide support to implement this
  since it may also be useful to other apps.

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

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

[Touch-packages] [Bug 1303843] Re: Window is distorted when it lays out on a size change

[Mathew Hodson]

** No longer affects: webbrowser-app (Ubuntu)

** Project changed: webbrowser-app => ubuntu

** No longer affects: ubuntu

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

Title:
  Window is distorted when it lays out on a size change

Status in Oxide:
  Fix Released
Status in Oxide 1.0 series:
  Fix Released

Bug description:
  This is most easily seen on the phone but also is present on the desktop. 
  On the phone get the OSK to appear and disappear. On desktop change the 
height of the window.
  The rendering is quite jumpy, it scales the text and images before changing 
the layout itself.

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

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

[Touch-packages] [Bug 1039792] Re: [needs-packaging] [MIR] ubuntu-default-settings

[Launchpad Bug Tracker]

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

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

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

Title:
  [needs-packaging] [MIR] ubuntu-default-settings

Status in ubuntu-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu has customized several GNOME packages with gsettings overrides.
  Moving these overrides to a separate package, recommended by ubuntu-
  desktop would have these advantages:

  1. Reduce our diff with Debian
  2. Make it easier for those who want a pure/custom GNOME experience to get it
  3. Give the GNOMEbuntu project more independence to ship a purer GNOME, or 
possibly tweak GNOME defaults without needing to affect the flagship Ubuntu 
desktop.

  This was discussed at UDS:
  http://summit.ubuntu.com/uds-q/meeting/20832/desktop-q-gnome-flavor/

  And "reducing the delta with Debian" is a recurring UDS discussion.
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-gnome-plans-review

  Code is temporarily at https://code.launchpad.net/~ubuntu-
  desktop/+junk/ubuntu-default-settings and will be uploaded shortly.

  This will also need to be promoted to main. However since it only
  contains copies of gsettings overrides (most of which are already in
  main), there's not really any code to review.

  There's also an ubuntu-artwork package which maybe should be merged
  into this one.

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

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

[Touch-packages] [Bug 1512608] Re: No thumbnails generated for OGG audio

[Fred Vkigg]

Thanks for the feedback. Sorry to respond so slowly.

I'm still still seeing a slow increase in thumbnails. I suspect it will
not converge to a complete coverage!

I need to further analyse the logs. One possibility is that I see a lot of OOM 
killer activity when Music app is open. I need to check the memory usage of the 
associated processes when Music is running. 
The BQ 5 seems chronicly short of RAM for the current touch releases!

I will wait to see if the retry changes in thumbnailer in OTA-8 effect
the results. If still bad I can post an SD card.

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

Title:
  No thumbnails generated for OGG audio

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Setup:
Core Music app 
BQ HD5
OTA-7 15.04 r6
Large collection of audio files in .ogg and .mp3 format on SD card
Audio files tagged with Artist, Album titile, Track title etc.

  Expected result:
Album covers and Artist images are displayed in Music app

  Actual result:
Only mp3 audio files generate thumbnails. No Album of Artist thumbnails are 
generated for any OGG files

  To test the situation I have
  a) Cleared the thumbnailer failure cache
  b) removed the whole thumbnail cache directory
  c) Removed and reinsterted the SD card
  d) Uninstallled and reinstalled the core Music app

  Before the OTA-7 upgrade the thumbnails were shown for .ogg and .mp3
  files

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

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

[Touch-packages] [Bug 1290514] Re: LibreOffice KDE4 backend crashes in Qt4 recursive paint events

[Mathew Hodson]

** Changed in: qt4-x11 (Ubuntu Precise)
   Status: Fix Committed => Confirmed

** Changed in: qt4-x11 (Ubuntu)
Milestone: ubuntu-14.04 => None

** Changed in: qt4-x11 (Ubuntu)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Quantal)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Saucy)
   Importance: Undecided => High

** Tags added: precise

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

Title:
  LibreOffice KDE4 backend crashes in Qt4 recursive paint events

Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in qt4-x11 source package in Precise:
  Confirmed
Status in qt4-x11 source package in Quantal:
  Won't Fix
Status in qt4-x11 source package in Saucy:
  Won't Fix
Status in qt4-x11 source package in Trusty:
  Fix Released

Bug description:
  Distribution: Kubuntu 12.04
  Package: qt4-x11 4:4.8.1-0ubuntu4.6
  Program: LibreOffice 4.3 (current master build).

  This bugs origin is a crash when using KDE4 native file picker dialogs
  from within LibreOffice [1].

  There are several similar ones in all distributions.

  In the backtrace you can see, that LO calls the Qt event dispatcher,
  which processes a draw event, which - at some point - waits for the
  clipboard using the Qt / LO event loop, which processes another (now
  nested) draw event -> crash.

  This happens, because LO sets
    qApp->clipboard()->setProperty( "useEventLoopWhenWaiting", true );
  because the X11 event processing in clipboardWaitForEvents would interfere 
with the LO X11 handling / locking.

  QX11Data::clipboardWaitForEvents (gui/kernel/qclipboard_x11.cpp:520)
  actually installs the correct clipboard event filter in the qapp,
  which should just handle Clipboard events.

  But actually the Qt internal glib event loop doesn't honor the
  QEventLoop::ExcludeSocketNotifiers (see
  src/corelib/kernel/qeventdispatcher_glib.cpp).

  Originally I opened [2], because I didn't want to deep dive into the
  Qt codebase. Since I didn't get any usable replies and all my
  implemented workarounds in LibreOffice didn't work I tried to
  understand the backtrace from [2] and realized the missing
  QEventLoop::ExcludeSocketNotifiers handling in the Qt glib code. I
  opened [3] and pushed a patch for Qt review as [4].

  [1] https://bugs.freedesktop.org/show_bug.cgi?id=69002
  [2] https://bugreports.qt-project.org/browse/QTBUG-34614
  [3] https://bugreports.qt-project.org/browse/QTBUG-37380
  [4] https://codereview.qt-project.org/#change,80528

  [IMPACT]
  The patch fixes the glib event loop to pass a currently failing testcase in 
the Qt4 library (processEventsExcludeSocket in 
tests/auto/qeventloop/tst_qeventloop.cpp). The flag was never handled in the 
glib eventloop.

  [TEST CASE]
  LibreOffice uses a very rarely used Qt codepath to poll the X11 clipboard 
(using the event loop), which needs this patch. Otherwise it crashes very often 
with the KDE 4 backend when polling the clipboard. There is no other codepath.
  Test by using LibreOffice with the KDE theme until it crashes.  After the 
patch is applied it will no longer crash.

  [REGRESSION POTENTIAL]
  I can't imagine a program out there which relies on this brokeness.
  If the patch was really broken to invert the behaviour, the impact would be 
immediately visible, as no socket events would be processed, including X11 
events.

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

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

[Touch-packages] [Bug 1501397] Re: Can't use Action id's in ActionList

[Zsombor Egri]

First, when you declare a list, you can only initialise it with objects,
not with their IDs. Seems we have this limitation on that. See Object
component implementation how its data is implemented.

Second, Page.head.actions is a list, not an object. You are trying to
assign an object to a list.

Better start with reading the docs carefully.

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

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

Title:
  Can't use Action id's in ActionList

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

Bug description:
  Latest rc-proposed, UbuntuComponents 1.3

  I can't use Action id's to compile an ActionList in order to re-use
  those actions elsewhere.

  Please see example: http://paste.ubuntu.com/12625111/

  You may want to reference ActionSelectionPopover documentation here:
  
https://developer.ubuntu.com/api/devel/ubuntu-12.04/qml/ui-toolkit/qml-ubuntu-components-popups0-actionselectionpopover.html

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

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

[Touch-packages] [Bug 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group

[Serge Hallyn]

So the problem is indeed that the cgroups are deleted using the
cgroupfs, and fuse doesn't get that information.  The fuse kernel module
is caching the information for one second before re-querying userspace.

I've pushed a patch to lxcfs to drop the caching to a half second.  I'm
posting a patch to lxc-devel to sleep for half a second during reboot.
This reliably fixes the race in my tests.

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

Title:
  rebooting container with systemd >= 226 fails to create /lxc/adt-
  xenial/init.scope control group

Status in lxc package in Ubuntu:
  In Progress

Bug description:
  Even after fixing bug 1497420 rebooting containers with systemd >= 226
  (i. e. with supporting unified cgroups) does not work. Build a
  standard xenial container (using the ubuntu template; e. g. "adt-
  build-lxc ubuntu xenial"), start it:

sudo lxc-start -n adt-xenial -F

  then log in and run "sudo reboot". It shuts down, but reboot fails
  with

  Rebooting.
  systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR 
+SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP 
+BLKID -ELFUTILS +KMOD -IDN)
  Detected virtualization lxc.
  Detected architecture x86-64.

  Welcome to Ubuntu 16.04!

  Set hostname to .
  Failed to install release agent, ignoring: No such file or directory
  Failed to create /lxc/adt-xenial/init.scope control group: No such file or 
directory
  Failed to allocate manager object: No such file or directory
  [!!] Failed to allocate manager object, freezing.
  Freezing execution.

  During that time, I get the following errors:

  Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path 
/run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file 
or directory)
  Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_children_main: Could 
not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope)
  Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path 
/run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file 
or directory)
  Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_keys_main: Could not 
determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope)
  Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager 
method call org.linuxcontainers.cgmanager0_0.ListChildren failed: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use 
G_DBUS_DEBUG=message for more info.
  Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager 
method call org.linuxcontainers.cgmanager0_0.ListKeys failed: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use 
G_DBUS_DEBUG=message for more info.h

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 1.1.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 10 06:30:28 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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

[Touch-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink

[Hannes Bochmann]

Only one monitor is plugged into the DisplayLink docking station so I
think the limitation of two monitors is not the problem. If I deactivate
the internal laptop monitor or the monitor plugged directly into the
laptop nothing changes. The mouse keeps flickering on the monitor that
is not connected to the docking station.

Thanks for the advice using the support forum of DisplayLink. The bug
was already reported
(http://www.displaylink.org/forum/showthread.php?p=79054#post79054). The
only "solution" they came up with is switching from Unity to another
desktop environment like gnome or metacity. As I like the Unity Dock
Launcher this is not a real option for me.

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1485682

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  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 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782 
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

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

[Thomas Voß]

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

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

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

Bug description:
  Hi!

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

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

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

  Thanks in advance!

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

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

[Touch-packages] [Bug 1212360] Re: Cannot import OpenVPN profiles

[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/1212360

Title:
  Cannot import OpenVPN profiles

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.10 / Intel / ASUS Zenbook
  Package: network-manager

  1. receive an OpenVPN profile (ovpn and crt files) by email or download.
  2. open Network Manager
  3. look in vain for an "import" button or link.

  What should have happened instead:

  3. there should be an "import OpenVPN profile" button on the "new VPN"
  dialog

  Prior to Unity, the gnome network manager had an "import VPN" button
  which allowed importing configuration files for OpenVPN and Cisco.
  The new Unity network manager has removed that button and not replaced
  it with anything.  The only workaround is to install the old Gnome
  network manager, launch it from the command line, and use it to import
  the VPN profile.

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

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

[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup

[Mathew Hodson]

** Changed in: ubiquity (Ubuntu Trusty)
Milestone: ubuntu-14.04.3 => ubuntu-14.04.4

** Changed in: ecryptfs-utils (Ubuntu Trusty)
Milestone: None => ubuntu-14.04.4

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

Title:
  Encrypted swap no longer mounted at bootup

Status in eCryptfs:
  Fix Released
Status in systemd:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Trusty:
  Triaged
Status in ubiquity source package in Trusty:
  Triaged
Status in ecryptfs-utils source package in Vivid:
  Fix Released
Status in systemd source package in Vivid:
  Fix Released
Status in ubiquity source package in Vivid:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  SUMMARY
  ===
  During installation with "encrypt my home folder" mode, a broken 
/etc/crypttab gets created which defines a non-existing swap device (usually 
"cryptswap1") with a UUID. This will also be put into /etc/fstab. As after 
installation the UUID does not exist, such systems don't have any actual swap.

  UPGRADE FIX
  ===
  An upgrade to Ubuntu 15.04 ("vivid") will detect and comment out these broken 
swap devices from /etc/fstab and /etc/crypttab. If you actually want  to use 
those, do these steps:

   - Find the swap device that was meant to be used in "sudo fdisk -l" (it 
should say "Linux swap" in the last column), remember the device name 
(something like "/dev/sda5")
   - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=)
   - Run "sudo mkswap -U 1234... /dev/sda5", replacing "1234" with the above 
UUID, and /dev/sda5 with the device name from step 1.
   - Edit /etc/crypttab to append ",offset=1024" in the fourth (last) column of 
the cryptswap1 line; ensure that there is *no space* between the 
"cipher=aes-cbc-essiv:sha256" and the appended option. If there is a leading 
"#" in the file, remove that too.
   - If there is a leading "#" in /etc/fstab in the line starting with 
/dev/mapper/cryptswap1 line, remove that.
   - Run "sudo update-initramfs -u".

  
  ORIGINAL REPORT
  ===

  Clean install of 12.04 and with encrypted home for my user. Did all
  updates and now the bootup hangs waiting for swap to become available
  and it never seems to ever finish. The 200GB SSD below is my boot
  drive and root filesystem.

  alan@mesh:~$ sudo swapon -a
  [sudo] password for alan:
  swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory

  alan@mesh:~$ grep swap /etc/fstab
  # swap was on /dev/sdg5 during installation
  #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 
 0   0
  /dev/mapper/cryptswap1 none swap sw 0 0

  alan@mesh:~$ sudo fdisk -l

  Disk /dev/sda: 115.0 GB, 115033153536 bytes
  255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x000ba2ed

     Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  206847  1024007  HPFS/NTFS/exFAT
  /dev/sda2  206848   224671743   1122324487  HPFS/NTFS/exFAT

  Disk /dev/sdb: 200.0 GB, 200049647616 bytes
  255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xf0fa0806

     Device Boot  Start End  Blocks   Id  System
  /dev/sdb12048   349304831   1746513927  HPFS/NTFS/exFAT
  /dev/sdb2   374722558   390721535 79994895  Extended
  /dev/sdb3   *   349304832   37472051112707840   83  Linux
  /dev/sdb5   374722560   390721535 7999488   82  Linux swap / Solaris

  Partition table entries are not in disk order

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libecryptfs0 96-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 13 09:56:56 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120215)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ecryptfs-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1387643] Re: Pruning of probably stale sessions should be less aggressive

[Thomas Voß]

** Changed in: location-service (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Pruning of probably stale sessions should be less aggressive

Status in Canonical System Image:
  Fix Committed
Status in location-service package in Ubuntu:
  Fix Committed

Bug description:
  Right now, after 10 non-successful attempts to deliver location
  updates to clients, the service considers the client to be hanging or
  dead and prunes the session from the service's cache. With that, if
  the app wakes up again, it does not receive updates for the same
  session anymore. A restart of the app fixes the issue.

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

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

[Touch-packages] [Bug 1427995] Re: lscpu -p is showing wrong values for Node component

[Mathew Hodson]

** No longer affects: util-linux (Ubuntu)

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

Title:
  lscpu -p is showing wrong values for Node component

Status in util-linux source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Any user of lscpu on systems with multiple NUMA nodes.

  [Test case]
  On a POWER8 system:
  1) Run 'lscpu'; take note of the values for "NUMA node# CPU(s)".
  2) Run 'lscpu -p'.

  The values on the fourth column in lscpu -p output should match the
  node for which the CPU (first column) is listed (or contained in the
  displayed range). For example:

  $ lscpu
  [...]
  NUMA node0 CPU(s): 0-12,14-39
  [...]
  NUMA node3 CPU(s): 13,40-79
  [...]
  $ lscpu -p
  [...]
  12,1,0,0,,1,1,1,1
  13,1,0,3,,1,1,1,1
  [...]
  39,4,0,0,,4,4,4,4
  40,5,1,3,,5,5,5,5
  [..]

  The fourth column for CPU 12 and 39 is "0", which matches the "node0" range 
of 0-12,14-39.
  The fourth column for CPU 13 and 40 is "3", which matches the "node3" range 
13,40-79.

  [Regression potential]
  This change is limited to the output of a command that can be parsed; so any 
regression would be erroneous values for node "names" or numbers, which may 
throw off data retrieved by parsing the output of lscpu.

  This particular bug constitutes the fix to a regression in a previous
  SRU (ubuntu7.4), which included changes to support discontinuous NUMA
  nodes, and introduced the code this SRU changes, so the regression
  potential is minimal (this particular feature of lscpu is already
  broken).

  ---

  ---Problem Description---
  lscpu -p is showing wrong values for Node component

  ---uname output---
  Linux ubuntu 3.16.0-25-generic #14-Ubuntu ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = P8

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  Install a P8 machine with Ubuntu 14.04.02 ISO image in Power NV mode.
  Then execute the below test scenario.

  root@ubuntu-daily:~# lscpu -p
  # The following is the parsable format, which can be fed to other
  # programs. Each different item in every column has an unique ID
  # starting from zero.
  # CPU,Core,Socket,Node,,L1d,L1i,L2,L3
  0,0,0,0,,0,0,0,0
  1,0,0,1,,0,0,0,0
  2,0,0,16,,0,0,0,0
  3,0,0,17,,0,0,0,0
  4,0,0,0,,0,0,0,0
  5,0,0,0,,0,0,0,0
  6,0,0,33,,0,0,0,0
  7,0,0,0,,0,0,0,0
  8,1,0,0,,1,1,1,1
  9,1,0,0,,1,1,1,1
  10,1,0,-1429431768,,1,1,1,1
  11,1,0,16383,,1,1,1,1
  12,1,0,1852125029,,1,1,1,1
  13,1,0,777213279,,1,1,1,1
  14,1,0,81,,1,1,1,1
  15,1,0,0,,1,1,1,1
  16,2,0,1920169263,,2,2,2,2
  17,2,0,1634235183,,2,2,2,2
  18,2,0,1815045490,,2,2,2,2
  19,2,0,1818321775,,2,2,2,2
  20,2,0,1852125029,,2,2,2,2
  21,2,0,777213279,,2,2,2,2
  22,2,0,759583829,,2,2,2,2
  23,2,0,1953836600,,2,2,2,2
  24,3,0,1278163046,,3,3,3,3
  25,3,0,1162698563,,3,3,3,3
  26,3,0,1195463507,,3,3,3,3
  27,3,0,1966035781,,3,3,3,3
  28,3,0,762079604,,3,3,3,3
  29,3,0,1970170220,,3,3,3,3
  30,3,0,1869426296,,3,3,3,3
  31,3,0,0,,3,3,3,3
  32,4,1,0,,4,4,4,4
  33,4,1,0,,4,4,4,4
  34,4,1,177,,4,4,4,4
  35,4,1,0,,4,4,4,4
  36,4,1,269092192,,4,4,4,4
  37,4,1,256,,4,4,4,4
  38,4,1,1,,4,4,4,4
  39,4,1,16383,,4,4,4,4
  40,5,1,0,,5,5,5,5
  41,5,1,0,,5,5,5,5
  42,5,1,269096544,,5,5,5,5
  43,5,1,256,,5,5,5,5
  44,5,1,269092512,,5,5,5,5
  45,5,1,256,,5,5,5,5
  46,5,1,269097536,,5,5,5,5
  47,5,1,256,,5,5,5,5
  48,6,1,269092688,,6,6,6,6
  49,6,1,256,,6,6,6,6
  50,6,1,269098208,,6,6,6,6
  51,6,1,256,,6,6,6,6
  52,6,1,269096960,,6,6,6,6
  53,6,1,256,,6,6,6,6
  54,6,1,269097456,,6,6,6,6
  55,6,1,256,,6,6,6,6
  56,7,1,269096544,,7,7,7,7
  57,7,1,256,,7,7,7,7
  58,7,1,269098592,,7,7,7,7
  59,7,1,256,,7,7,7,7
  60,7,1,269097344,,7,7,7,7
  61,7,1,256,,7,7,7,7
  62,7,1,269098016,,7,7,7,7
  63,7,1,256,,7,7,7,7
  64,8,2,269096880,,8,8,8,8
  65,8,2,256,,8,8,8,8
  66,8,2,269098400,,8,8,8,8
  67,8,2,256,,8,8,8,8
  68,8,2,269097184,,8,8,8,8
  69,8,2,256,,8,8,8,8
  70,8,2,269097856,,8,8,8,8
  71,8,2,256,,8,8,8,8
  72,9,2,269096672,,9,9,9,9
  73,9,2,256,,9,9,9,9
  74,9,2,0,,9,9,9,9
  75,9,2,0,,9,9,9,9
  76,9,2,0,,9,9,9,9
  77,9,2,0,,9,9,9,9
  78,9,2,65,,9,9,9,9
  79,9,2,0,,9,9,9,9
  80,10,2,1920169263,,10,10,10,10
  81,10,2,1634235183,,10,10,10,10
  82,10,2,1815045490,,10,10,10,10
  83,10,2,1818321775,,10,10,10,10
  84,10,2,1852125029,,10,10,10,10
  85,10,2,777213279,,10,10,10,10
  86,10,2,759583829,,10,10,10,10
  87,10,2,1129066296,,10,10,10,10
  88,11,2,1397050719,,11,11,11,11
  89,11,2,1162297683,,11,11,11,11
  90,11,2,1953836883,,11,11,11,11
  91,11,2,1814916201,,11,11,11,11
  92,11,2,2020961897,,11,11,11,11
  93,11,2,7302446,,11,11,11,11
  94,11,2,113,,11,11,11,11
  95,11,2,0,,11,11,11,11
  96,12,3,269092448,,12,12,12,12
  97,12,3,256,,12,12,12,12
  98,12,3,1,,12,12,12,12
  99,12,3,16383,,12,12,12,12
  100,12,3,0,,12,12,12,12
  101,12,3,0,,12,12,12,12
  102,12,3,269092272,,12,12,12,12
  103,12,3,256,,12,12,12,12
  

[Touch-packages] [Bug 1512180] Re: [datetime] Standard alarms are not work correctly for Timers, after timezone/DST change

[Zsombor Egri]

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

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

Title:
  [datetime] Standard alarms are not work correctly for Timers, after
  timezone/DST change

Status in Canonical System Image:
  Incomplete
Status in Timer:
  Confirmed
Status in Ubuntu Clock App:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Standard alarms will not work correctly after changing timezone and
  during DST change.

  Steps to reproduce:
  1. Install Timer from Store: https://uappexplorer.com/app/timer.mivoligo
  2. Set timer to 5 minutes
  3. Open Clock app. Look for alarm, and notice that alarm is correctly set
  3. Switch to System Settings -> Time & Date -> Time zone:
  4.  Change Time zone to something different (eg. New York). (Or wait for DST 
change: https://en.wikipedia.org/wiki/Daylight_saving_time)

  Expected behaviour:
  - timer ringing as expected after timezone/DST change

  Current behaviour:
  - alarm is not ringing. (you could check active alarms in "Ubuntu Clock app)

  Proposal solution:
  - introduce new type of alarms, which is based on UTC 
(https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and independent from 
time zones.
  - This alatms will not be visible in applications which is using standard 
alarms (Ubuntu Clock, Ubuntu Calendar etc.)

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

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

[Touch-packages] [Bug 1513449] Re: 1.3 DraggingArea reference error MathUtils is not defined

[Zsombor Egri]

This should pop up only if you use Panel in your app. Do you happen to
have that?

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

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

Title:
  1.3 DraggingArea reference error MathUtils is not defined

Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  This shows up in the log:
  - when resizing the app window on desktop (15.04 with phone overlay installed)
  - occasionally on the phone

  I think the error is pretty obvious, so probably the bug report need
  to be super detailed.

  file:///usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/1.3/DraggingArea.qml:27: ReferenceError:
  MathUtils is not defined

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

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

[Touch-packages] [Bug 1499872] Re: Right swipe showing running apps, some apps are grayed out

[Zsombor Egri]

This is not a toolkit bug, rather Unity8.

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

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

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

Title:
  Right swipe showing running apps, some apps are grayed out

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

Bug description:
  I am using the Meizu MX4 with the latest updates(15.04 r4). Sometimes
  when I look at my running apps with a right swipe, some of the running
  apps are greyed out (transparent). If I then select the app it opens
  after a few seconds. On checking the running apps again I can now see
  the running app as normal. Please see picture attached.

  Thanks for your hard work,

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1499845] Re: Expose whether an app has a visible BottomEdge

[Zsombor Egri]

It is way easier to detect on an app whether it is the first run or not
than on shell. Shell would need to keep track about each app on how many
times it has been launched, and that is just not its task.

I mentioned Tutorial component simply because I do see this whole logic being 
tracked by it:
- is this the first launch
- show the required information over a given point with a given animation full 
screen

I definitely see this should be all on the app's hand and not on the
system. Apps know whether they have bottom edge and they should handle
the tutorial. No reason to do extra communication and slow the UI
interaction with that even more than we have to. Toolkit can provide the
building blocks to get this handled without extra burden for the apps.

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

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

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

Title:
  Expose whether an app has a visible BottomEdge

Status in ubuntu-ui-toolkit package in Ubuntu:
  Opinion

Bug description:
  == The Design ==

  The edge tutorial that is shown during the first-boot is getting a
  redesign [1].

  As part of it, the bottom edge tutorial screen is intended to only
  appear after a certain amount of time and only if a user is opening or
  switching to an app with a bottom edge to drag up.

  When that happens, a page appears covering the whole screen, pointing
  to the bottom and saying "Swipe from the bottom edge to manage the
  app".  Then when the user does swipe up, it fades out as the bottom is
  swiped.   I've attached a screenshot of an early mockup for this (back
  when it was designed for the App scope, not an actual app).

  Since it must cover the entire screen (and turn off the launcher and
  panel during it), it should probably be rendered by the shell (which
  is rendering the rest of the tutorial anyway).  So we have to
  coordinate between the app and the shell.

  There are two main technical difficulties in implementing this, the
  way I see it.  Detecting if the current page has a valid BottomEdge
  and synchronizing the fade-out with the bottom-edge drag.

  [1] https://docs.google.com/document/d/1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s

  == Detecting BottomEdge ==

  We need:
  1) A BottomEdge SDK component
  2) That is enabled
  3) That is attached to the bottom edge of the app
  4) That is currently being rendered (might be in a Page that isn't on top 
right now)
  5) That isn't obscured by some other widget or MouseArea

  #5 is going to be hard to detect in the wild west of apps from the
  store.  But one thing we could do restrict this to known-well-behaved
  apps that are shipped by default anyway.  The user is most likely to
  be in one of those early on in their phone experience anyway.

  Once the SDK can detect this situation, it needs to signal it somehow.
  Maybe the "valid-bottom-edge" state can bubble up to qtmir's
  ApplicationManager and then the shell.  Any ideas on the best way to
  do that?

  == Synchronizing fade transition ==

  I'm thinking there are two ways:

  1) Communicate from the app to the shell how far the bottom edge has
  been dragged, as it is being dragged.  Presumably via the same channel
  as we communicate that there is a valid bottom edge in the first
  place.

  2) Fake it and have the shell track the drag itself.  It then needs to
  mirror the input to the app so that it also receives the drag.

  #2 is probably easier.  Slightly brittle in case for whatever reason
  the app interferes with the drag or does something on its own that
  would desynchronize the animation.  But again, if we limit this to
  well-known apps, we can avoid that.

  == Open tasks ==

  1) Get general feedback on these ideas
  2) Determine how feasible it is for the SDK to detect a valid BottomEdge
  3) Determine the best way to signal that state from the SDK up to the shell
  4) Implement it

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

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

[Touch-packages] [Bug 1369632] Re: After disconnecting and reconnecting device to MTP host it is not possible to delete a folder using MTP

[Mathew Hodson]

** No longer affects: mtp (Ubuntu)

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

Title:
  After disconnecting and reconnecting device to MTP host it is not
  possible to delete a folder using MTP

Status in gvfs package in Ubuntu:
  New

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09-proposed build 40
  Desktop: Windows 8.1 / Ubuntu

  SUMMARY:
  After disconnecting and reconnecting device to MTP host it is not possible to 
delete a folder using MTP

  STEPS:
  1) Connect Ubuntu device to host PC over USB
  2) Copy some music content to the music folder on MTP device including some 
folder structure
  3) Eject the Ubuntu device's USB connection
  4) Re-insert Ubuntu device USB
  5) Browse to MTP Music folder on device
  6) Try to delete some of the music folders that were just added

  EXPECTED RESULT:

  The content should be deleted successfully.

  ACTUAL RESULT:

  After a delay of about 30 seconds Ubuntu presents error:
  "libmtp error: could not delete object".
  It is then not possible to copy any content to or from the device.

  Windows also fails to delete the content with error stating that
  device has been disconnected.

  Note that it is possible to delete files when the device is re-
  connected. It is when deleting a parent folder that the problem
  occurs.

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

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

[Touch-packages] [Bug 1512608] Re: No thumbnails generated for OGG audio

[Michi Henning]

Fred, thanks for getting bad to us!

If the music app gets killed, it might be because it asks for more than
it can eat. If it sends a large number of requests to the thumbnailer,
and lots of requests get a cache hit, the thumbnailer will deliver close
to a thousand images per second, which can eat a lot of memory.

I suspect that the retry in the thumbnailer is not going to fix this.
This sounds more like a scalability issue outside of the thumbnailer to
me.

The SD card option would be ideal. I thought about doing something with
my own music library, but all of my songs have embedded cover art in
them, and it would take me an eternity to strip out all the cover
images. And, even then, I would have no guarantee that I can reproduce
the problem.

** Also affects: music-app (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No thumbnails generated for OGG audio

Status in music-app package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Setup:
Core Music app 
BQ HD5
OTA-7 15.04 r6
Large collection of audio files in .ogg and .mp3 format on SD card
Audio files tagged with Artist, Album titile, Track title etc.

  Expected result:
Album covers and Artist images are displayed in Music app

  Actual result:
Only mp3 audio files generate thumbnails. No Album of Artist thumbnails are 
generated for any OGG files

  To test the situation I have
  a) Cleared the thumbnailer failure cache
  b) removed the whole thumbnail cache directory
  c) Removed and reinsterted the SD card
  d) Uninstallled and reinstalled the core Music app

  Before the OTA-7 upgrade the thumbnails were shown for .ogg and .mp3
  files

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

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

[Touch-packages] [Bug 1226329] Re: [TextField] The placeholderText does not apper when inputMask is setted

[Zsombor Egri]

Christian, not sure whether is this still valid.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana)

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

Title:
  [TextField] The placeholderText does not apper when inputMask  is
  setted

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The inputMask makes the placehorlderText invisible even when the text
  property is empty.

  Example:
  TextInputDetail {
  height: units.gu(4)

  // this will never appears
  placeholderText: i18n.tr("Date of birth")
  inputMask: "09/09/"
  }

  
  WORKAROUND:
  TextInputDetail {
  height: units.gu(4)

  // this will never appears
  placeholderText: i18n.tr("Date of birth")
  inputMask: activeFocus ? "09/09/" : ""
  }

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

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

[Touch-packages] [Bug 1289433] Re: "No accounts" doesn't use the list placeholder font style

[Zsombor Egri]

This can be achieved with simple Label within an Item, no need for
special toolkit component.

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

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

Title:
  "No accounts" doesn't use the list placeholder font style

Status in Online Accounts setup for Ubuntu Touch:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Trusty r188

  1. Flash the phone or remove any existing online accounts.
  2. Go to System Settings > "Accounts".

  What you see: "No accounts" in the normal label font style.

  What you should see: "No accounts" in the standard list placeholder
  font style, large and semi-transparent.

  : "If you have none,
  the list of accounts should have 'No accounts' placeholder text..."

  Exactly the same style should be used for "Software is up to date" in
  the Updates screen. If that style is not implemented in the toolkit,
  that should be done first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1289433/+subscriptions

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

[Touch-packages] [Bug 1259876] Re: No support for colourizing ListItems.Standard Icon.

[Zsombor Egri]

No changes will be done for ListItems submodule, the new ListItemLayout
gives the freedom to include anything in the slots and thus you can
colorise in whichever way you like.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  No support for colourizing ListItems.Standard Icon.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  Previously we could override the icon and supply our own icon which
  could be coloured. This has now been deprecated for
  iconSource/iconName.

  Use case: 
  The date indicator appointments use colour coding for the calendar. The 
alarm/calendar icon should be keyed in with the specified calendar colour. Want 
to be able to use ListItems.Standard for the event list item.

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

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

[Touch-packages] [Bug 1369651] Re: "libmtp error: Could not send object info" when copying content to root MTP folder

[Mathew Hodson]

** Changed in: mtp (Ubuntu)
Milestone: ubuntu-14.09 => None

** Tags added: utopic

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

Title:
  "libmtp error: Could not send object info" when copying content to
  root MTP folder

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Ubuntu device: ubuntu-rtm/14.09-proposed build 40
  Desktop: Ubuntu 14.10

  SUMMARY:
  "libmtp error: Could not send object info" when copying content to root MTP 
folder

  STEPS:
  1) Connect Ubuntu MTP device over USB
  2) Attempt to copy some content to the root of the MTP folder

  EXPECTED RESULT:
  The copy operation should succeed. (This is the Android behaviour).

  ACTUAL RESULT:
  An error message is presented on desktop: "libmtp error: Could not send 
object info"

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

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

[Touch-packages] [Bug 1363046] Re: No message/call notification tone plays through Bluetooth headset

[Mathew Hodson]

** Changed in: bluez (Ubuntu Utopic)
Milestone: ubuntu-14.09 => None

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

Title:
  No message/call notification tone plays through Bluetooth headset

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Utopic:
  Fix Released

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez  4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth headset (Sony SBH50, Motorola S10-HD) is connected to 
krillin and a call/sms is received, no notification tone is played through the 
headset. Instead it plays normally through the device loud speakers.

  We have seen on some other versions of headset (Jawbone ERA, BQ Avrha
  Strauss) where a new sms notification tone is played through the
  headset, but not the call ringer tone.

  STEPS:
  1) Pair and connect the Bluetooth headset
  2) Receive an incoming sms
  3) Receive an incoming call

  EXPECTED RESULT:
  The notification tones should play through the Bluetooth headset

  ACTUAL RESULT:
  There is no notification tone played through the Bluetooth headset

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

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

[Touch-packages] [Bug 1370572] Re: Unknown libmtp error when copying content from internal storage to SD card using MTP

[Mathew Hodson]

** Changed in: mtp (Ubuntu)
Milestone: ubuntu-14.09 => None

** Tags added: trusty utopic

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

Title:
  Unknown libmtp error when copying content from internal storage to SD
  card using MTP

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09 build 1
  Desktop: Ubuntu 14.04/14.10

  SUMMARY:
  Unknown libmtp error when copying content from internal storage to SD card 
using MTP.

  This might be the case for someone who has a new memory card and they
  want to copy/move content to it from device's internal storage.

  STEPS:
  1) Connect Ubuntu device to Ubuntu host PC over USB
  2) Attempt to copy/move some music content directly from device's internal 
storage to device's SD card using MTP

  EXPECTED RESULT:
  The content should be copied/moved successfully.

  ACTUAL RESULT:
  The following error is displayed on desktop:
  "libmtp error: Unknown error".

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

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

[Touch-packages] [Bug 1184006] Re: wrong conffile prompt for /etc/default/rcS when UTC=no

[Mathew Hodson]

** Changed in: sysvinit (Ubuntu)
Milestone: ubuntu-14.04 => None

** Changed in: sysvinit (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  wrong conffile prompt for /etc/default/rcS when UTC=no

Status in clock-setup package in Ubuntu:
  Confirmed
Status in sysvinit package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in clock-setup source package in Saucy:
  Won't Fix
Status in sysvinit source package in Saucy:
  Won't Fix
Status in ubiquity source package in Saucy:
  Won't Fix

Bug description:
  Because we're not following Debian on the use of /etc/adjtime for UTC
  settings and instead keeping it in /etc/default/rcS, users who have
  the non-default setting of UTC=no will get inappropriate conffile
  prompts on upgrade to saucy.

  We need to deal with this by either reverting /etc/default/rcS's
  conffile status, or moving this UTC setting out of /etc/default/rcS
  (options: /etc/default/hwclock, /etc/init/hwclock{,-save}.override).

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

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

[Touch-packages] [Bug 1039792] Re: [needs-packaging] [MIR] ubuntu-default-settings

[Mathew Hodson]

** Package changed: baltix => ubuntu

** No longer affects: ubuntu

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

Title:
  [needs-packaging] [MIR] ubuntu-default-settings

Status in ubuntu-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu has customized several GNOME packages with gsettings overrides.
  Moving these overrides to a separate package, recommended by ubuntu-
  desktop would have these advantages:

  1. Reduce our diff with Debian
  2. Make it easier for those who want a pure/custom GNOME experience to get it
  3. Give the GNOMEbuntu project more independence to ship a purer GNOME, or 
possibly tweak GNOME defaults without needing to affect the flagship Ubuntu 
desktop.

  This was discussed at UDS:
  http://summit.ubuntu.com/uds-q/meeting/20832/desktop-q-gnome-flavor/

  And "reducing the delta with Debian" is a recurring UDS discussion.
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-gnome-plans-review

  Code is temporarily at https://code.launchpad.net/~ubuntu-
  desktop/+junk/ubuntu-default-settings and will be uploaded shortly.

  This will also need to be promoted to main. However since it only
  contains copies of gsettings overrides (most of which are already in
  main), there's not really any code to review.

  There's also an ubuntu-artwork package which maybe should be merged
  into this one.

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

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

[Touch-packages] [Bug 1513642] Re: [sdk] Change "Back button" to simple right-swipe from the center of the screen.

[Zsombor Egri]

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

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

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

Title:
  [sdk] Change "Back button" to simple right-swipe from the center of
  the screen.

Status in Ubuntu UX:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Back button is located in left-upper corner.
  Stretching the thumb to that corner is not easy (regardless left- or 
right-hand usage).
  More natural will be using horisontal swipe from the middle of the screen, 
the same way as it's done for shuffling scopes back.
  I think it will work almost everywhere, making interface experience more 
streamlined.

   UX comment ---

  While swiping left and right in the center of the screen for navigational 
purposes works for scopes, it would lead to issues in many other places.
  As stated below, list items have the ability being swiped to the left and to 
the right, which would interfere with the navigation. An other example is the 
camera app, where user access their camera roll/last picture shot.

  This is why the proposed interaction is not suitable navigating
  between applications.

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

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

[Touch-packages] [Bug 1514841] Re: [Ubuntu phone] Text in text entry is cut at the bottom (TextArea with autoSize=true)

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

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

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

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

Title:
  [Ubuntu  phone] Text in text entry is cut at the bottom (TextArea with
  autoSize=true)

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

Bug description:
  When I get a text message and try to answer from the notification text
  entry, the text I write is cut at the bottom. Also the scrollbar is
  visible. Please see attached screenshot. The text reads: „Hej zgadza
  się”.

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

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

[Touch-packages] [Bug 1315060] Re: Allow --confdir to look for system jobs in more than one directory

[Mathew Hodson]

** Changed in: upstart (Ubuntu Utopic)
Milestone: ubuntu-14.06 => None

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

Title:
  Allow --confdir to look for system jobs in more than one directory

Status in The Savilerow project:
  Fix Released
Status in upstart :
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Fix Released

Bug description:
  A requirement from OEMs/Carriers for customization is to allow for
  customized upstart jobs/overrides.  It seems that the best way to do
  this would be to allow --confdir to take multiple directories, so that
  we can include a directory under /custom.

  As for session jobs, I assume we can just set /custom as an
  XDG_CONFIG_DIR, and have /custom/upstart with jobs there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 12:30:09 2014
  InstallationDate: Installed on 2013-04-26 (370 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=610268d4-9acd-4bf8-a1a1-95c88b3ccf59 ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-11-23 (158 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

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

[Touch-packages] [Bug 1403955] Re: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0

[PshemK]

The bug is still present in 1.25.

The fact that it only manifests itself during the subsequent machine
reboots (and not during the initial build) makes it more difficult to
troubleshoot - services that worked before reboot do not work after.

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

Title:
  DHCP's "Option interface-mtu 9000" is being ignored on bridge
  interface br0

Status in juju-core:
  Triaged
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  In an env with jumbo frames enabled, and using MAAS as DHCP server,
  the client receives the following IPv4 lease:

  $ cat /var/lib/dhcp/dhclient.br0.leases
  lease {
    interface "br0";
    fixed-address 10.230.20.26;
    filename "pxelinux.0";
    option subnet-mask 255.255.248.0;
    option dhcp-lease-time 43200;
    option routers 10.230.16.1;
    option dhcp-message-type 5;
    option dhcp-server-identifier 10.230.20.1;
    option domain-name-servers 10.230.20.1;
    option interface-mtu 9000;
    option broadcast-address 10.230.23.255;
    option domain-name "ctsstack.qa.1ss";
    renew 3 2014/12/17 16:48:15;
    rebind 3 2014/12/17 21:52:09;
    expire 3 2014/12/17 23:22:09;
  }

  The interfaces show the following config after boot:

  $ ifconfig br0
  br0   Link encap:Ethernet  HWaddr a0:d3:c1:01:9d:58
    inet addr:10.230.20.26  Bcast:10.230.23.255  Mask:255.255.248.0
    inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:68713489 (68.7 MB)  TX bytes:213710979 (213.7 MB)

  $ ifconfig eth0
  eth0  Link encap:Ethernet  HWaddr a0:d3:c1:01:9d:58
    inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
    TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2320560616 (2.3 GB)  TX bytes:3562885157 (3.5 GB)
    Interrupt:32

  
  "option interface-mtu 9000;" from the lease file is being ignored by br0. 
Could it be related to eth0 MTU size? If that's the case, shouldn't both 
interfaces be updated?

  Other info:

  $ brctl show br0
  bridge name   bridge id   STP enabled interfaces
  br0   8000.a0d3c1019d58   no  eth0

  $ cat /etc/network/eth0.config
  iface eth0 inet manual

  auto br0
  iface br0 inet dhcp
    bridge_ports eth0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

[kevin gunn]

ok, went back to 159, verified no issue after several reboots.
updated only qtmir/qtubuntu to the very latest and the issue appeared on the 
first reboot.

so these 2 changes are the suspects
https://code.launchpad.net/~unity-team/qtmir/revert-occlusion-detection/+merge/277049
https://code.launchpad.net/~unity-team/qtubuntu/revert-occlusion-detection/+merge/277048

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

** No longer affects: unity8 (Ubuntu)

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

** Changed in: qtubuntu
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => kevin gunn (kgunn72)

** Changed in: qtubuntu
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  After a boot the dash doesn't display until touched

Status in Canonical System Image:
  Confirmed
Status in qtubuntu:
  New
Status in qtmir package in Ubuntu:
  New

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

[Peter Bittner]

Just wanted to confirm that this is still causing me pain daily on my bq
Aquaris E5 (OTA-7). I can not at all (or hardly) use any phone call
features (e.g. transfering to the loudspeaker to do hands-free talking
is an acrobatic act, because the screen insists in turning black
immediately again, e.g. I'm pressing the lock button on the right upper
side of the phone).

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

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

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

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

[Touch-packages] [Bug 1496845] Re: Number containing # are incorrectly sent unencoded to url-dispatcher

[Launchpad Bug Tracker]

This bug was fixed in the package dialer-app -
0.1+16.04.2015-0ubuntu1

---
dialer-app (0.1+16.04.2015-0ubuntu1) xenial; urgency=medium

  [ Gustavo Pichorim Boiko ]
  * We really just want to get the index of the account in the active
accounts list.

  [ Tiago Salem Herrmann ]
  * Avoid removing # and other characters from tel: uri's (LP: #1496845)
  * Fallback to original phone number when format() returns a blank
string

 -- Gustavo Pichorim Boiko   Wed, 11 Nov
2015 15:17:07 +

** Changed in: dialer-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 address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1496845

Title:
  Number containing # are incorrectly sent unencoded to url-dispatcher

Status in Canonical System Image:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Invalid
Status in dialer-app package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  Reproduce:
  * Open System Settings and call a SIM Service number containing a #, e.g. 
+47005#1
  * Create a contact in address-book-app with the number “+47005#1” and call it.

  What happens:
  “+47005” appears in dialer

  What should happen:
  “+47005#1” should appear in dialer, i.e. affected apps needs to urlencode the 
number.

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

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

[Pat McGowan]

** Summary changed:

- Firs boot after an update the dash doesn't display until touched
+ After a boot the dash doesn't display until touched

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

Title:
  After a boot the dash doesn't display until touched

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

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

[Touch-packages] [Bug 1496845] Re: Number containing # are incorrectly sent unencoded to url-dispatcher

[Pat McGowan]

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

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

Title:
  Number containing # are incorrectly sent unencoded to url-dispatcher

Status in Canonical System Image:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Invalid
Status in dialer-app package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  Reproduce:
  * Open System Settings and call a SIM Service number containing a #, e.g. 
+47005#1
  * Create a contact in address-book-app with the number “+47005#1” and call it.

  What happens:
  “+47005” appears in dialer

  What should happen:
  “+47005#1” should appear in dialer, i.e. affected apps needs to urlencode the 
number.

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

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

[Touch-packages] [Bug 1515371] [NEW] Using search from omnibar causes Xorg to restart or crash

[Radics Ottó]

Public bug reported:

I just happened, nothing special. Using chrome, typing into the omnibar
to search on Google, and Xorg crashes. No crash on normal domain input.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-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: Wed Nov 11 20:07:33 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05fe]
InstallationDate: Installed on 2015-07-04 (129 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. XPS 15 9530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=904a0ffb-8477-46ae-bbb8-775512ba4e95 ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+15.10.20151015-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
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: Wed Nov 11 20:03:17 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5169 
 vendor SHP
xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu wily

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

Title:
  Using search from omnibar causes Xorg to restart or crash

Status in xorg package in Ubuntu:
  New

Bug description:
  I just happened, nothing special. Using chrome, typing into the
  omnibar to search on Google, and Xorg crashes. No crash on normal
  domain input.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-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: Wed Nov 11 20:07:33 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05fe]
  InstallationDate: Installed on 2015-07-04 (129 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 15 9530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=904a0ffb-8477-46ae-bbb8-775512ba4e95 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8

[Touch-packages] [Bug 1130571] Re: wired network disabled after resume

[Gabriel]

I have this bug too. I had this issue on 14.04, 14. 10, 15.04 and 15.10.
Now I will download 12.04.2 LTS* maybe is more stable to our AR9485
Wireless Network Adapter. My PC is HP 1000 Notebook PC and googled
somethings and can be usable:

1. *Certified systems: 
http://www.ubuntu.com/certification/catalog/component/pci/168c%3A0032/
2. Linux kernel backports: 
http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/
Instructions: 
http://www.vivaolinux.com.br/dica/Configurando-Wireless-no-GNULinux
3. Stabilizing an atheros ar9485: 
http://pkill-9.com/stabilizing-atheros-ar9485-ath9k-connection-linux-wheezy/

But nothing worked as well.

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

Title:
  wired network disabled after resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have both a wired network and wireless. On first boot both are
  functional, but on resuming from sleep the wired controller is
  disabled (wireless still works). This behaviour started with the
  latest kernel installed yesterday.

  From syslog on resume

  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): now managed
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): bringing up 
device.
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): deactivating 
device (reason 'managed') [2]

   uname -a
  Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo lshw -C network
  [sudo] password for mthornton: 
*-network   
 description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlan3
 version: 01
 serial: dc:85:de:03:c8:ce
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f790-f797 memory:f798-f798
*-network DISABLED
 description: Ethernet interface
 product: AR8161 Gigabit Ethernet
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: eth4
 version: 10
 serial: 10:bf:48:9f:e9:c6
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical
 configuration: broadcast=yes driver=alx latency=0 multicast=yes
 resources: irq:19 memory:f780-f783 ioport:d000(size=128)

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

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

[Touch-packages] [Bug 1363482] Re: ubuntu-keyring includes 1024D keys

[Colin Watson]

** Changed in: ubuntu-cdimage
 Assignee: Adam Conrad (adconrad) => Colin Watson (cjwatson)

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

Title:
  ubuntu-keyring includes 1024D keys

Status in Ubuntu CD Images:
  New
Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-keyring as shipped in trusty contains old 1024D keys dating
  back to 2004 which are still being trusted for the main archive:

   % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg | grep 1024D
  pub  1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key 

  pub  1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key 


  Given that newer 4096R keys are present and have been in precise
  (through -updates) and trusty, it seems to be about time to drop the
  older keys. (In the hope that apt does not chose on signatures it
  cannot verify, otherwise the publisher would need to stop signing with
  the old key as well.)

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

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

[Touch-packages] [Bug 1515356] [NEW] Firs boot after an update the dash doesn't display until touched

[Pat McGowan]

Public bug reported:

Saw this on 162 and 163
MX4

Get the update and reboot to install, open the greeter, there is a blank screen 
with just the bottom edge hint
touch the screen and it displays the scope contents immediately

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

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

Title:
  Firs boot after an update the dash doesn't display until touched

Status in unity8 package in Ubuntu:
  New

Bug description:
  Saw this on 162 and 163
  MX4

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

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

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

[Touch-packages] [Bug 1515095] Re: Cannot launch gallery from photo scope

[Pat McGowan]

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

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

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

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

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

Title:
  Cannot launch gallery from photo scope

Status in Canonical System Image:
  Fix Committed
Status in gallery-app package in Ubuntu:
  Triaged

Bug description:
  Test Env:
  ~$ system-image-cli -i
  current build number: 171
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 08:12:47
  version version: 171
  version ubuntu: 20151110.1
  version device: 20150821-736d127
  version custom: 2015111

  Steps:
  1. take photos by camera
  2. go to photo scope
  3. tap on photo to preview page
  4. tap on "open" button

  Actual:
  Tapping on open button does nothing

  Expected:
  Should be able to launch gallery app and display the photo

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

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

[Touch-packages] [Bug 1130571] Re: wired network disabled after resume

[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/1130571

Title:
  wired network disabled after resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have both a wired network and wireless. On first boot both are
  functional, but on resuming from sleep the wired controller is
  disabled (wireless still works). This behaviour started with the
  latest kernel installed yesterday.

  From syslog on resume

  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): now managed
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): bringing up 
device.
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): deactivating 
device (reason 'managed') [2]

   uname -a
  Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo lshw -C network
  [sudo] password for mthornton: 
*-network   
 description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlan3
 version: 01
 serial: dc:85:de:03:c8:ce
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f790-f797 memory:f798-f798
*-network DISABLED
 description: Ethernet interface
 product: AR8161 Gigabit Ethernet
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: eth4
 version: 10
 serial: 10:bf:48:9f:e9:c6
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical
 configuration: broadcast=yes driver=alx latency=0 multicast=yes
 resources: irq:19 memory:f780-f783 ioport:d000(size=128)

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

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

[Touch-packages] [Bug 1496163] Re: i915 firmware is not copied to initrd

[Peter Curtis]

I seem to have this bug with a Skylake machine where  the firmware load
for i915/skl_dmc_ver1.bin failed with error -2.

I am running (or trying to) with the Ubuntu LTS Trusty/14.04 version.

Is there any way I can use the Wily versions of initramfs-tools or do
you have an estimate when it will be backported to the LTS version as
per #13

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

Title:
  i915 firmware is not copied to initrd

Status in Linux:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Vivid:
  In Progress
Status in initramfs-tools source package in Wily:
  Fix Released

Bug description:
  On Skylake, the skl_dmc firmware is failing to load. From dmesg:

  [0.728803] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1.bin failed with error -2
  [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to 
load firmware i915/skl_dmc_ver1.bin (0)

  This means the GPU can't enter its lowest available power states, plus
  many display hotplugging scenarios (that only the skl_dmc firmware can
  handle) are broken.

  On a whim I tried some other firmware versions:

  1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin
  (instead of skl_dmc_ver1_19.bin)

  2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the
  skl_dmc_ver1.bin symlink to it

  But neither corrected the situation.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-10-generic 4.2.0-10.11
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1251 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 15 16:21:24 2015
  HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader 
Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic 
root=UUID=f967534a-9cc3-4d1a-a7f3-72d28959e3c6 ro i915.verbose_state_checks=1 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-10-generic N/A
   linux-backports-modules-4.2.0-10-generic  N/A
   linux-firmware1.147
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd08/19/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/linux/+bug/1496163/+subscriptions

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

[Touch-packages] [Bug 1515354] [NEW] netman icon does not show VPN status when VPN connected automatically at boot time

[Jeff Lane]

Public bug reported:

I have VPNs configured in Network Manager, one of which is a default
work VPN.  That VPN is configured to connect whenever the network
connection is active on my desktop, thus every time I reboot, the
connection for eth0 is active and the VPN connects automatically.

I've noticed, however, that the NM icon in the tray does not show this
connected status when the automatic connection is made.

Ordinarily, if I manually connect to a VPN, the status icon changes from
two arrows (this is a wired connection) to two arrows with a padlock
indicating a secured VPN connection.

When I boot this system and the VPN connection is established
automatically, however, the icon does not display the padlock, BUT if
you look at NM/VPN Connections/ you can clearly see the connection
marked as active by the check mark next to it.

If I boot the machine and the NM icon is in this state, I can manually
shut down and restart the VPN link and the icon changes to show the VPN
connection as it should.

The screen shot attached shows the icon after a boot, as well as the VPN
connections list with the currently active VPN highlighted by the
checkmark.

Additionally, If I manually disconnect the wired connection and
reconnect it, again, the icon shows the secure established VPN
connection.


Expected Behaviour:

The NM status icon should ALWAYS show the padlock when a VPN connection
is made, regardless of whether it is automatic or not.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov 11 13:16:05 2015
IfupdownConfig:
 auto lo
 iface lo inet loopback
 
 iface eth1:foo inet dhcp
InstallationDate: Installed on 2012-03-15 (1335 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2014-04-20 (569 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-07-30T16:31:50.821388
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth1   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


** Tags: amd64 apport-bug third-party-packages trusty

** Attachment added: "vpn-status.jpg"
   
https://bugs.launchpad.net/bugs/1515354/+attachment/4517104/+files/vpn-status.jpg

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

Title:
  netman icon does not show VPN status when VPN connected automatically
  at boot time

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have VPNs configured in Network Manager, one of which is a default
  work VPN.  That VPN is configured to connect whenever the network
  connection is active on my desktop, thus every time I reboot, the
  connection for eth0 is active and the VPN connects automatically.

  I've noticed, however, that the NM icon in the tray does not show this
  connected status when the automatic connection is made.

  Ordinarily, if I manually connect to a VPN, the status icon changes
  from two arrows (this is a wired connection) to two arrows with a
  padlock indicating a secured VPN connection.

  When I boot this system and the VPN connection is established
  automatically, however, the icon does not display the padlock, BUT if
  you look at NM/VPN Connections/ you can clearly see the connection
  marked as active by the check mark next to it.

  If I boot the machine and the NM icon is in this state, I can manually
  shut down and restart the VPN link and the icon changes to show the
  VPN connection as it should.

  The screen shot attached shows the icon after a boot, as well as the
  VPN connections list with the currently active VPN highlighted by the
  checkmark.

  Additionally, If I manually disconnect the wired connection and
  reconnect it, again, the icon shows the secure established VPN
  connection.

  
  Expected Behaviour:

  The NM status icon should ALWAYS show the padlock when a VPN
  connection is made, regardless of whether it is automatic or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: 

[Touch-packages] [Bug 1382233] Please test proposed package

[Chris J Arges]

Hello Brian, or anyone else affected,

Accepted whoopsie into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.49.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

Title:
  whoopsie does not upload UnreportableReason field in crash reports

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Precise:
  In Progress
Status in whoopsie source package in Trusty:
  Fix Committed
Status in whoopsie source package in Vivid:
  Fix Committed
Status in whoopsie source package in Wily:
  Fix Committed

Bug description:
  Test Case
  -
  1) Edit a .crash file to have an UnreportableReason key and value e.g.
 UnreportableReason: Your system is weird.
  2) sudo service whoopsie stop
  3) start whoopsie pointing to errors.staging.ubuntu.com e.g.
 sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com 
APPORT_REPORT_DIR=/var/crash/ whoopsie -f
  4) Put said .crash file in /var/crash/
  5) Put a corresponding .upload file in /var/crash/
  6) Observe whoopsie uploading the .crash file from the whoopsie log
 [16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8
  7) go to errors.staging.ubuntu.com/oops/$OOPS_ID
  8) verify the UnreportableReason appears there e.g.:
 https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8

  
  In src/whoopsie.c we can see the following:

  /* We would only want this to see how many bugs would otherwise go
   * unreported: */
  "UnreportableReason",

  The comment isn't exactly true.  apport uses the UnreportableReason
  key to include the following information:

    "You have some obsolete package versions installed."

  It'd be useful if this information was sent to the Error Tracker so
  that we can decide not to ask for a core dump from these crash
  reports. The "obsolete package versions" check is done by checking to
  see if the most recent available version of the package is installed,
  so if someone does not have -updates enabled then that pocket is not
  checked and "obsolete package versions" will not be present. This is
  desirable because the retracers will check to see if the package
  version is available from any pocket.

  So if we send UnreportableReason to the Error Tracker we can stop
  asking for core dumps and retracing crashes that will fail to retrace.

  However, the value for UnreportableReason is translated so this may
  not end up helping much.

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

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

[Touch-packages] [Bug 1515012] Re: SIM not selected in header on incoming call

[Pat McGowan]

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

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

Title:
  SIM not selected in header on incoming call

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

Bug description:
  latest rc-proposed
  When you receive a call, the dialer shows the correct SIM label in the header 
but it is not selected. It should be selected (i.e. should have orange 
highlighting).

  See attached screenshot

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

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

[Touch-packages] [Bug 1130571] Re: wired network disabled after resume

[Gabriel]

There my SystemLog when the problem came: http://pastebin.com/uZ43a28T
I needed restart some times. This sucks :(

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

Title:
  wired network disabled after resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have both a wired network and wireless. On first boot both are
  functional, but on resuming from sleep the wired controller is
  disabled (wireless still works). This behaviour started with the
  latest kernel installed yesterday.

  From syslog on resume

  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): now managed
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): bringing up 
device.
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): deactivating 
device (reason 'managed') [2]

   uname -a
  Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo lshw -C network
  [sudo] password for mthornton: 
*-network   
 description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlan3
 version: 01
 serial: dc:85:de:03:c8:ce
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f790-f797 memory:f798-f798
*-network DISABLED
 description: Ethernet interface
 product: AR8161 Gigabit Ethernet
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: eth4
 version: 10
 serial: 10:bf:48:9f:e9:c6
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical
 configuration: broadcast=yes driver=alx latency=0 multicast=yes
 resources: irq:19 memory:f780-f783 ioport:d000(size=128)

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

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

[Touch-packages] [Bug 1130571] Re: wired network disabled after resume (AR9485)

[Gabriel]

** Summary changed:

- wired network disabled after resume
+ wired network disabled after resume (AR9485)

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

Title:
  wired network disabled after resume (AR9485)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have both a wired network and wireless. On first boot both are
  functional, but on resuming from sleep the wired controller is
  disabled (wireless still works). This behaviour started with the
  latest kernel installed yesterday.

  From syslog on resume

  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): now managed
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): bringing up 
device.
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): deactivating 
device (reason 'managed') [2]

   uname -a
  Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo lshw -C network
  [sudo] password for mthornton: 
*-network   
 description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlan3
 version: 01
 serial: dc:85:de:03:c8:ce
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f790-f797 memory:f798-f798
*-network DISABLED
 description: Ethernet interface
 product: AR8161 Gigabit Ethernet
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: eth4
 version: 10
 serial: 10:bf:48:9f:e9:c6
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical
 configuration: broadcast=yes driver=alx latency=0 multicast=yes
 resources: irq:19 memory:f780-f783 ioport:d000(size=128)

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

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

[Touch-packages] [Bug 1515356] Re: Firs boot after an update the dash doesn't display until touched

[Pat McGowan]

seems like a recent regression

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

** Description changed:

  Saw this on 162 and 163
  MX4
  
  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately
+ 
+ Also reproduces occasionally after reboot

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

** 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 => ww46-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

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

Title:
  Firs boot after an update the dash doesn't display until touched

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

Bug description:
  Saw this on 162 and 163
  MX4

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces occasionally after reboot

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

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