date:20150521

Silo 002 with the not so complete fix was no freed to be reused for
other purposes. I made a backup of the package to https://launchpad.net
/~timo-jyrinki/+archive/ubuntu/ppa/+packages though.

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

Title:
  Qt5 applications crash when switching screens

Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in qtdeclarative-opensource-src source package in Wily:
  Confirmed

Bug description:
  # Impact
  When switching screens (e. g. when putting the laptop onto the docking 
station the notebook screen is turned off and the external one is turned on) 
Qt5 applications (including plasmashell) quite often crash.

  # Test Case
  * Have two screens. One plugged-in one not
  * Run plasma 5
  * Plug-in second screen and wait 10 seconds
  * Unplug and wait 10 seconds
  * Plug-in and wait 10 seconds
  * Unplug and wait 10 seconds
  * ...

  # Regression Potential
  Worst case scenario an application using qquickscreen would slow down because 
of erroneous screen change singals being emitted too often per second. This 
would however only reveal a lower level issue in the foundations that 
ultimately needs to be fixed anyway. 

  # Other Info
  The upstream code review [1] explains the issue and solution pretty well.

  https://codereview.qt-project.org/#/c/00/

  
  - original report ---

  When switching screens (e. g. when putting the laptop onto the docking
  station the notebook screen is turned off and the external one is
  turned on) Qt5 applications (including plasmashell) quite often crash.
  This makes my laptop unusable, since I do that very frequently.

  The problem has already been described here: 
https://bugs.kde.org/show_bug.cgi?id=341497
  Apparently it is fixed in Qt 5.5

  I am running Kubuntu 15.04 64bit and libqt5gui5 5.4.1+dfsg-2ubuntu4.

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

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

[Touch-packages] [Bug 1362033] Re: Icon for calendar item usually shows the wrong date

For me, it's a 25 I see for all events. Took me a while to realise why I
couldn't find these events in my calendar. I've attached a picture for
clarity. Even today's date (21st) is shown as 25th in the graphic.

** Attachment added: screenshot20152721_092748636[1].png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1362033/+attachment/4401520/+files/screenshot20152721_092748636%5B1%5D.png

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

Title:
  Icon for calendar item usually shows the wrong date

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1, Ubuntu 14.04

  1. Open the clock menu.
  2. Look at the icon for the date item.

  What you see: 28, regardless of the current date.

  What you should see: The current date.

  The Ubuntu Touch equivalent is bug 1362962.

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

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

[Touch-packages] [Bug 1457383] [NEW] Messaging app should only allow selecting one candidate for deletion at a time using swipe gesture

Public bug reported:

I swiped a message to one side to delete it, but three messages became
candidates.

** Affects: messaging-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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1457383

Title:
  Messaging app should only allow selecting one candidate for deletion
  at a time using swipe gesture

Status in messaging-app package in Ubuntu:
  New

Bug description:
  I swiped a message to one side to delete it, but three messages became
  candidates.

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

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

[Touch-packages] [Bug 1457384] [NEW] fully transparent windows

2015-05-21 Thread Xtien

Public bug reported:

Every now and then, a window is fully transparent. I see the border, but
nothing else,  see what should be behind the window. This happens in
Thunderbird, Eclipse, and most other programs and popups.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
Uname: Linux 3.19.0-17-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May 21 10:32:18 2015
DistUpgraded: 2015-05-05 14:05:58,436 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.3.28, 3.19.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:1370]
InstallationDate: Installed on 2014-04-21 (394 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-17-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to vivid on 2015-05-05 (15 days ago)
dmi.bios.date: 11/15/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CROSSHAIR V FORMULA-Z
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd11/15/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue May 12 13:19:18 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Optical Mouse MOUSE, id 8
 inputEee PC WMI hotkeys   KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: nouveau

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


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

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

Title:
  fully transparent windows

Status in xorg package in Ubuntu:
  New

Bug description:
  Every now and then, a window is fully transparent. I see the border,
  but nothing else,  see what should be behind the window. This happens
  in Thunderbird, Eclipse, and most other programs and popups.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
  Uname: Linux 3.19.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 21 10:32:18 2015
  DistUpgraded: 2015-05-05 14:05:58,436 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.19.0-17-generic, x86_64: installed

[Touch-packages] [Bug 1457357] [NEW] Don't hard code the date format of event card

Public bug reported:

Hard-coding the date format to MMM  causes problems when the month
name is too long, see screenshot.

Note MMM should be abbreviated, but at least for Finnish it's not and
it's even conjugated making it even longer. So it's probably also a Qt
(translation) bug but flexibility here would help.

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

** Attachment added: out.jpg
   https://bugs.launchpad.net/bugs/1457357/+attachment/4401485/+files/out.jpg

** Description changed:

  Hard-coding the date format to MMM  causes problems when the month
  name is too long, see screenshot.
+ 
+ Note MMM should be abbreviated, but at least for Finnish it's not and
+ it's even conjugated making it even longer. So it's probably also a Qt
+ (translation) bug but flexibility here would help.

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

Title:
  Don't hard code the date format of event card

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Hard-coding the date format to MMM  causes problems when the
  month name is too long, see screenshot.

  Note MMM should be abbreviated, but at least for Finnish it's not and
  it's even conjugated making it even longer. So it's probably also a Qt
  (translation) bug but flexibility here would help.

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

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

[Touch-packages] [Bug 1457357] Re: Don't hard code the date format of event card

https://bugreports.qt.io/browse/QTBUG-35139 is related.

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

Title:
  Don't hard code the date format of event card

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Hard-coding the date format to MMM  causes problems when the
  month name is too long, see screenshot.

  Note MMM should be abbreviated, but at least for Finnish it's not and
  it's even conjugated making it even longer. So it's probably also a Qt
  (translation) bug but flexibility here would help.

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

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

[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes

2015-05-21 Thread Toni Leino

** Information type changed from Private Security to Public

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

Title:
  Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes

Status in Ubuntu One Infrastructure:
  New
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  After two last updates (I remember second one was also a kernel
  update) my Ubuntu has started sudden crashing, either desktop view
  freezes, sometimes sound which was played goes to fast circuit.
  Sometimes it crashes to full terminal screen, reporting kernel panic
  mode. I'm sorry I dont know how to find these crash reports from my
  Ubuntu, hope you can advice me. After crash, only thing possible is to
  reset my laptop manually.

  Ubuntu has also started to inform internal failure with powerd, and
  asks to report them to developers. I think I have send that report
  three times now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions

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

[Touch-packages] [Bug 1457383] Re: Messaging app should only allow selecting one candidate for deletion at a time using swipe gesture

** Attachment added: screenshot20152120_202149153.png
   
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1457383/+attachment/4401546/+files/screenshot20152120_202149153.png

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

Title:
  Messaging app should only allow selecting one candidate for deletion
  at a time using swipe gesture

Status in messaging-app package in Ubuntu:
  New

Bug description:
  I swiped a message to one side to delete it, but three messages became
  candidates.

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

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

[Touch-packages] [Bug 1265611] Re: No sound with HDA Intel, VIA VT8237A/VT8251, kernel 3.12

2015-05-21 Thread WalterHangartner

I can confirm a similar behavior as described in post #7.

1. I installed Ubuntu Studio 15.04 on the harddisk and there was no way to get 
sound from speakers.
2. I started Ubuntu Studio 12.04.5 from a USB stick with persistence and did 
all updates.
3. With 12.04.5 initial system and also after update I had sound on speakers.
4. I boot 15.04, with power connected, and there is sound on speakers.
5. I boot 15.04 using the battery, and there is NO sound on speakers.
6. I boot 15.04, with power connected, and there is NN sound on speakers.

7. I go back and can repeat cycle starting at item 3.

I also verified, that when just temporarily removing power cable before
step 4, I still have sound in step 4.

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

Title:
  No sound with HDA Intel, VIA VT8237A/VT8251, kernel 3.12

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After updating my system to Ubuntu Trusty Tahr (development branch) Release:  
14.04
  my soundcard VIA Technologies, Inc. VT8237A/VT8251 HDA Controller is not 
working anymore on the newer kernel (3.12).
  After booting an older kernel  (3.2) the card is working.

  Already tried various options in /etc/modprobe.d/alsa-base.conf, 
  e.g. options snd-hda-intel probe_mask=1 model=3stack-dig but without success

  Configuration infos
  lspci: 04:01.0 Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA 
Controller

  Bad system configuration:
  --
  Linux version 3.12.0-7-generic (buildd@aatxe) (gcc version 4.8.2 
(Ubuntu/Linaro 4.8.2-8ubuntu1) ) #15-Ubuntu SMP Sun Dec 8 23:39:27 UTC 2013 
(Ubuntu 3.12.0-7.15-generic 3.12.4)

  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic
  root=UUID=cd684c44-c353-4cdf-8242-a865c65b61b3 ro quiet splash
  vt.handoff=7

  [   21.342849] hda-intel :04:01.0: Using VIACOMBO position fix
  [   21.342893] snd_hda_intel :04:01.0: irq 68 for MSI/MSI-X
  [   22.348029] hda-intel :04:01.0: Codec #0 probe error; disabling it...
  [   27.384025] hda-intel :04:01.0: no codecs initialized

  uploded alsa info of bad configuration:
  http://www.alsa-project.org/db/?f=c1cebc6d64b60684489e6143a813f529d01bc410

  
  Good system configuration:
  
  Linux version 3.2.0-56-generic (buildd@roseapple) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #86-Ubuntu SMP Wed Oct 23 09:20:45 UTC 2013 
(Ubuntu 3.2.0-56.86-generic 3.2.51)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-56-generic 
root=UUID=cd684c44-c353-4cdf-8242-a865c65b61b3 ro quiet splash vt.handoff=7

  
  [   23.147203] snd_hda_intel :04:01.0: PCI INT A - GSI 17 (level, low) 
- IRQ 17
  [   23.147262] snd_hda_intel :04:01.0: irq 68 for MSI/MSI-X
  [   23.147292] snd_hda_intel :04:01.0: setting latency timer to 64
  [   26.196033] hda-intel: azx_get_response timeout, switching to polling 
mode: last cmd=0x000f0001
  [   27.144807] hda_codec: ALC888: BIOS auto-probing.
  [   27.144813] hda_codec: ALC888: SKU not ready 0x41f0
  [   27.153432] input: HDA VIA VT82xx Line as 
/devices/pci:00/:00:13.0/:04:01.0/sound/card0/input7
  [   27.153568] input: HDA VIA VT82xx Mic as 
/devices/pci:00/:00:13.0/:04:01.0/sound/card0/input8
  [   27.153684] input: HDA VIA VT82xx Front Headphone as 
/devices/pci:00/:00:13.0/:04:01.0/sound/card0/input9
  [   27.153801] input: HDA VIA VT82xx Line-Out Side as 
/devices/pci:00/:00:13.0/:04:01.0/sound/card0/input10
  [   27.153914] input: HDA VIA VT82xx Line-Out CLFE as 
/devices/pci:00/:00:13.0/:04:01.0/sound/card0/input11
  [   27.154022] input: HDA VIA VT82xx Line-Out Surround as 
/devices/pci:00/:00:13.0/:04:01.0/sound/card0/input12
  [   27.154127] input: HDA VIA VT82xx Line-Out Front as 
/devices/pci:00/:00:13.0/:04:01.0/sound/card0/input13

  uploded alsa info of good configuration:
  http://www.alsa-project.org/db/?f=39d8e002614a92b0b9f993e3a9c46c7a5e86ae38

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

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

[Touch-packages] [Bug 1445913] Re: System hangs on restart on the Bq Aquaris 4.5

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

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: New = Confirmed

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

Title:
  System hangs on restart on the Bq Aquaris 4.5

Status in ubuntu-touch-meta package in Ubuntu:
  Confirmed

Bug description:
  It now happened the second time that I was not able to initiate a
  restart of the system on my Bq Aquaris 4.5. This happened after I
  pressed the power button for a few seconds and afterwards selected the
  restart option.

  Other symptoms are:

  - The white screen with the black bq logo does not appear. 
  - Instead, a pale violet background is permanently shown. Backlight of the 
display is on.
  - The phone cannot be turned off by pressing the power button for longer.
  - If the phone is connected to my desktop using an USB cable, the device is 
recognized but cannot be mounted.

  Since the battery cannot be physically removed on that phone, the only option 
to solve the situation was for me to let it run
  out of battery power until it turns off by itself. Afterwards, the phone can 
be put to live again after connecting the power cable.

  It appears as if the phone is hanging in the boot loader. The problem
  may be more prevalent when battery power is already low (50%) the
  time the restart is initiated.

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

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

[Touch-packages] [Bug 1457361] [NEW] Clipboard clear method crashes and Pushing data straight to clipboard is not working

2015-05-21 Thread XiaoGuo, Liu

Public bug reported:

- I tried to call the Clipboard.clear() method, and it crashes my
application for 100% sure.

- I tried the 2. Pushing data straight to clipboard method on page:

https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Clipboard/

it does not work at all. The method 1/3 work fine.

I have my test code:

https://gitcafe.com/ubuntu/clipboard/tree/master

You can check it out by running:

git clone https://gitcafe.com/ubuntu/clipboard.git

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

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

Title:
  Clipboard clear method crashes and Pushing data straight to clipboard
  is not working

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

Bug description:
  - I tried to call the Clipboard.clear() method, and it crashes my
  application for 100% sure.

  - I tried the 2. Pushing data straight to clipboard method on page:

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Clipboard/

  it does not work at all. The method 1/3 work fine.

  I have my test code:

  https://gitcafe.com/ubuntu/clipboard/tree/master

  You can check it out by running:

  git clone https://gitcafe.com/ubuntu/clipboard.git

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

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

[Touch-packages] [Bug 1457357] Re: Don't hard code the date format of event card

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

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

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

Title:
  Don't hard code the date format of event card

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  Hard-coding the date format to MMM  causes problems when the
  month name is too long, see screenshot.

  Note MMM should be abbreviated, but at least for Finnish it's not and
  it's even conjugated making it even longer. So it's probably also a Qt
  (translation) bug but flexibility here would help.

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

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

[Touch-packages] [Bug 1447504] Re: [system settings] Dialer-app: Wrong number is shown in call history

2015-05-21 Thread Matthew Paul Thomas

I made a mistake in my previous comment. When I said that formatting of
a phone number should not depend on what your locale setting happened
to be when you dialled it, and especially not on what your locale
setting happened to be at the moment you happened to look at the call
history, I think that's true for international numbers: they should
follow the E.123 standard regardless. But it is not true for domestic
numbers: they differ in grouping and separators.

The problem here seems to be that the Chinese number 18812345678 is
being displayed as if it was an North American (NANP) number, merely
because Wenfang is using the American locale. So the 1 is wrongly
interpreted as North America's optional trunk code and dropped, the
881 is wrongly interpreted as a North American area code and
bracketed, and the rest is wrongly displayed using the North American
- separator. Result: (881) 234-5678.

So, I guess what the call history needs to do is to remember what
country you were in for each domestic number you dial, and format it
following the locale for that country.

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

Title:
  [system settings] Dialer-app: Wrong number is shown in call history

Status in Ubuntu UX bugs:
  Triaged
Status in dialer-app package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  arale, r180, ubuntu-touch/vivid-proposed

  Steps
  1. Launch dialer-app
  2. Input number a Chinese phone number, e.g. 18812345678, and dial
  3. End the call
  4. Review in call history
  =
  The number is displayed as (881) 234-5678

  Expected:
  1) number should be complete whithout missing the leading 1
  2) format should be like 188-1234-5678, or just 18812345678

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

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

[Touch-packages] [Bug 1457298] Re: invalid auth for online-account

2015-05-21 Thread Alberto Mardegan

Hi! The signon-plugin-oauth only handles OAuth 1.0 and 2.0. Since yupoo
uses its own non-standard authentication, you cannot use the signon-
plugin-oauth with it.

You need to write a signon plugin specialized for yupoo. Unfortunately this is 
not well documented, but at least there are a few examples of signon plugins 
around.
The more complex is certainly signon-plugin-oauth, but here's a few simpler 
ones:

https://gitlab.com/accounts-sso/signon-plugin-digest
https://gitlab.com/accounts-sso/signon-plugin-sasl
(click on the Files tab on the left to see the project files)

I had a look at the yupoo documentation at
http://dev.yupoo.com/apidoc2/www/ but since it's in Chinese, I didn't
understand much about it. It appears that it all starts with this call
(please correct me if I'm wrong):

http://www.yupoo.com/services/auth/?api_key=[api_key]perms=[perms]api_sig=[api_sig]

The above link should be opened in a web view, where the user will be asked to 
authenticate and authorize the app, and then it will be redirected to the 
callback url, which will have the frob appended in a query item. Is my 
understanding correct?
And, what do you need in order to generate the api_sig?

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

Title:
  invalid auth for online-account

Status in signon-plugin-oauth2 package in Ubuntu:
  New

Bug description:
  In order to launch authentication like most other accounts, yupoo need
  to register a new .provider file to Online accounts.

   But this XML-format file requires an standard-parameter request for
  authenticating and  accessing token, including  client_id, token_path
  and others, which doesn't match with the request format of yupoo.

  Yupoo need to launch an auth with a link like
  
http://www.yupoo.com/services/auth/?api_key=[api_key]frob=[frob]perms=[perms]api_sig=[api_sig].
  It is an non standard-format request and need additional parameter
  requests before accessing token. So we can hardly integrating the
  entire auth of yupoo into Online-accounts.

  Shall we provide an more agile policy for configure when creating the
  .provide file?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-plugin-oauth2/+bug/1457298/+subscriptions

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

[Touch-packages] [Bug 1457298] Re: invalid auth for online-account

2015-05-21 Thread Alberto Mardegan

The yupoo API looks very similar to the old Flickr API:
https://www.flickr.com/services/api/auth.spec.html

Can you please have a look and confirm if they use the same
authentication method?

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

Title:
  invalid auth for online-account

Status in signon-plugin-oauth2 package in Ubuntu:
  New

Bug description:
  In order to launch authentication like most other accounts, yupoo need
  to register a new .provider file to Online accounts.

   But this XML-format file requires an standard-parameter request for
  authenticating and  accessing token, including  client_id, token_path
  and others, which doesn't match with the request format of yupoo.

  Yupoo need to launch an auth with a link like
  
http://www.yupoo.com/services/auth/?api_key=[api_key]frob=[frob]perms=[perms]api_sig=[api_sig].
  It is an non standard-format request and need additional parameter
  requests before accessing token. So we can hardly integrating the
  entire auth of yupoo into Online-accounts.

  Shall we provide an more agile policy for configure when creating the
  .provide file?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-plugin-oauth2/+bug/1457298/+subscriptions

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

[Touch-packages] [Bug 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)

2015-05-21 Thread Elvis Stansvik

Just like Guillermo, I'm trying to run BricsCAD on my X220 laptop and
get this error/crash. Anyone know if it has been reported upstream and
if there's a fix in sight?

To Guillermo: Did you ever find any workaround to getting BricsCAD to
run? I tried setting LIBGL_DISABLE_DRI3 in the environment since I saw
that tip here: https://bugs.freedesktop.org/show_bug.cgi?id=71759 , but
it didn't work :(

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

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

Title:
  Unity crashes when many windows are opened (intel_do_flush_locked
  failed: No space left on device)

Status in Unity:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in Debian:
  New
Status in mesa package in Fedora:
  Unknown

Bug description:
  Unity 5.8.0 (Ubuntu 12.04 Beta) crashes (or hanged up) on Fujitsu-Siemens 
S7020 (Intel 915GM Express Chipset) very often during attempt to use Dash or 
switch between applications when many winsows are opened with following error:
  intel_do_flush_locked failed: No space left on device

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
  Uname: Linux 3.2.0-22-generic-pae i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.0-0ubuntu4
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Tue Apr 10 11:25:45 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120314)
  MachineType: FUJITSU SIEMENS LIFEBOOK S7020
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae 
root=UUID=e6a4deb8-3e53-4afb-aed8-997537309262 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2005
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.07
  dmi.board.name: FJNB19C
  dmi.board.vendor: FUJITSU
  dmi.board.version: CP234410-02
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: S7020
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd09/16/2005:svnFUJITSUSIEMENS:pnLIFEBOOKS7020:pvr:rvnFUJITSU:rnFJNB19C:rvrCP234410-02:cvnFUJITSUSIEMENS:ct10:cvrS7020:
  dmi.product.name: LIFEBOOK S7020
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.7.4-0ubuntu3
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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

[Touch-packages] [Bug 1457321] [NEW] lxc-stop does not shut down container

Public bug reported:

lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should
shut down. This merely starts sigpwr.target right now, but nothing is
hooked into it. That's deliberate for real iron systems as there it's
usually UPSes sending that, which should be handled by e. g. nut, not
directly systemd. However, for containers I believe that's a safe
default.

https://lists.linuxcontainers.org/pipermail/lxc-
users/2015-May/009279.html

SRU TEST CASE:
--
- Create a vivid LXC container (system or unprivileged)
- Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.

REGRESSION POTENTIAL:
-
- This new unit is only active in containers (LXC, docker, nspawn, etc.). There 
a possible regression is that someone is running/testing nut or a similar UPS 
responder in a container, but that seems like a theoretical scenario only.
- There is no change for VMs or real hardware.

** Affects: systemd (Ubuntu)
 Importance: Medium
 Assignee: Martin Pitt (pitti)
 Status: In Progress

** Affects: systemd (Ubuntu Vivid)
 Importance: Medium
 Status: New

** Affects: systemd (Ubuntu Wily)
 Importance: Medium
 Assignee: Martin Pitt (pitti)
 Status: In Progress


** Tags: systemd-boot

** Also affects: systemd (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Tags added: systemd-boot

** Changed in: systemd (Ubuntu Wily)
   Importance: Undecided = Medium

** Changed in: systemd (Ubuntu Vivid)
   Importance: Undecided = Medium

** Description changed:

  lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should
  shut down. This merely starts sigpwr.target right now, but nothing is
  hooked into it. That's deliberate for real iron systems as there it's
  usually UPSes sending that, which should be handled by e. g. nut, not
  directly systemd. However, for containers I believe that's a safe
  default.
  
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2015-May/009279.html
+ 
+ SRU TEST CASE:
+ --
+ - Create a vivid LXC container (system or unprivileged)
+ - Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.

** Changed in: systemd (Ubuntu Wily)
   Status: New = In Progress

** Changed in: systemd (Ubuntu Wily)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  lxc-stop does not shut down container

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Vivid:
  New
Status in systemd source package in Wily:
  In Progress

Bug description:
  lxc-stop sends SIGPWR to a container's pid 1 to notify it that it
  should shut down. This merely starts sigpwr.target right now, but
  nothing is hooked into it. That's deliberate for real iron systems
  as there it's usually UPSes sending that, which should be handled by
  e. g. nut, not directly systemd. However, for containers I believe
  that's a safe default.

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2015-May/009279.html

  SRU TEST CASE:
  --
  - Create a vivid LXC container (system or unprivileged)
  - Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.

  REGRESSION POTENTIAL:
  -
  - This new unit is only active in containers (LXC, docker, nspawn, etc.). 
There a possible regression is that someone is running/testing nut or a similar 
UPS responder in a container, but that seems like a theoretical scenario only.
  - There is no change for VMs or real hardware.

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

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

[Touch-packages] [Bug 1444883] Re: Emergency numbers for China (110, 119) are not available in emergency mode

2015-05-21 Thread Evan Wang

Hi Sebastien, I collected the emergency call numbers of Mainland China
only (not include Hong KongMacau, and Taiwan), and they are all
available in my android phone(XiaoMi) with the same SIM card.

110Police
119Fire
120Ambulance
122Traffic Accident

Here is the output of /usr/share/ofono/scripts/list-modems on Arale
r46, channel: ubuntu-touch/tangxi/devel-proposed

$ /usr/share/ofono/scripts/list-modems 
[ /ril_0 ]
Model = Fake Modem Model
Manufacturer = Fake Manufacturer
Online = 1
Lockdown = 0
Type = hardware
Emergency = 0
Revision = MOLY.LR9.W1421.MD.LWTG.MP.V6.P11, 2014/09/10 10:13
Powered = 1
Interfaces = org.ofono.ConnectionManager org.ofono.Phonebook 
org.ofono.CallBarring org.ofono.CallForwarding org.ofono.CallSettings 
org.ofono.SupplementaryServices org.ofono.NetworkRegistration 
org.ofono.SmartMessaging org.ofono.PushNotification org.ofono.MessageManager 
org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager 
org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime 
Features = gprs ussd net sms rat sim 
Serial = 862095022035486
[ org.ofono.ConnectionManager ]
RoamingAllowed = 0
Bearer = lte
Attached = 1
Powered = 1
Suspended = 0
[ org.ofono.Phonebook ]
[ org.ofono.CallBarring ]
VoiceOutgoing = international
VoiceIncoming = disabled
[ org.ofono.CallForwarding ]
ForwardingFlagOnSim = 0
VoiceNoReply = 
VoiceUnconditional = 
VoiceNoReplyTimeout = 20
VoiceNotReachable = +8613800100103
VoiceBusy = +86138
[ org.ofono.CallSettings ]
CalledLinePresentation = disabled
CallingNamePresentation = unknown
HideCallerId = default
CallingLinePresentation = enabled
CallingLineRestriction = disabled
VoiceCallWaiting = enabled
ConnectedLinePresentation = unknown
ConnectedLineRestriction = unknown
[ org.ofono.SupplementaryServices ]
State = idle
[ org.ofono.NetworkRegistration ]
Strength = 83
Mode = auto
Technology = edge
CellId = 25617
MobileNetworkCode = 00
Name = CMCC
MobileCountryCode = 460
LocationAreaCode = 4335
Status = registered
[ org.ofono.SmartMessaging ]
[ org.ofono.PushNotification ]
[ org.ofono.MessageManager ]
ServiceCenterAddress = +8613800100500
UseDeliveryReports = 0
Bearer = cs-preferred
Alphabet = default
[ org.ofono.MessageWaiting ]
VoicemailWaiting = 0
VoicemailMailboxNumber = 
VoicemailMessageCount = 0
[ org.ofono.RadioSettings ]
ModemTechnologies = gsm umts lte 
TechnologyPreference = lte
FastDormancy = 0
[ org.ofono.SimManager ]
Retries = 
FixedDialing = 0
BarredDialing = 0
ServiceNumbers = [] = '' 
MobileCountryCode = 460
PinRequired = none
SubscriberIdentity = 460027013766397
CardIdentifier = 898600c00115
SubscriberNumbers = 
Present = 1
LockedPins = 
MobileNetworkCode = 02
[ org.ofono.CallVolume ]
Muted = 0
SpeakerVolume = 0
MicrophoneVolume = 0
[ org.ofono.VoiceCallManager ]
EmergencyNumbers = 112 911 
[ org.ofono.NetworkTime ]

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

Title:
  Emergency numbers for China (110,119) are not available in emergency
  mode

Status in telephony-service package in Ubuntu:
  Incomplete

Bug description:
  arale device, r177, ubuntu-touch/vivid-proposed

  Steps
  1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on 
Emergency Call)
  2. try input 911, 112 == OK
  2. try input 110, 119 == Dial button is inactive after number is input

  Expect
  Allow these numbers in emergency mode

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

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

[Touch-packages] [Bug 1457054] Re: journal is broken in unprivileged LXC and nspawn containers

** Description changed:

  Test case
  -
  - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
  - Boot it. You'll get a lot of errors like
  
    [FAILED] Failed to start Journal Service.
    systemd-journald-audit.socket failed to listen on sockets: Operation not 
permitted
    [FAILED] Failed to listen on Journal Audit Socket.
  
  - The same happens with systemd-nspawn -b.
  
  As a result, the journal isn't working at all, and you have a bunch of
  failed journal related units.
  
  With a fixed systemd package, systemd in the container should realize
  that it cannot listen to the audit socket (as the kernel doesn't allow
  that -- the audit subsystem isn't fit for namespaces right now), and
  sudo journalctl should show the journal and systemd-journald.service
  should be running. These systemd fixes are sufficient for nspawn, but
  not completely for unprivileged LXC containers -- there the journal will
  start working, but systemd-journald-audit.socket will still keep failing
  (this is less important)
+ 
+ REGRESSION POTENTIAL: Very low. This only affects the fallback error
+ code path if binding to the audit socket failed. In that case the
+ journal is currently not working at all. This usually doesn't happen on
+ real iron/VMs, so there is no practical change there.

** Description changed:

  Test case
  -
  - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
  - Boot it. You'll get a lot of errors like
  
    [FAILED] Failed to start Journal Service.
    systemd-journald-audit.socket failed to listen on sockets: Operation not 
permitted
    [FAILED] Failed to listen on Journal Audit Socket.
  
  - The same happens with systemd-nspawn -b.
  
  As a result, the journal isn't working at all, and you have a bunch of
  failed journal related units.
  
  With a fixed systemd package, systemd in the container should realize
  that it cannot listen to the audit socket (as the kernel doesn't allow
  that -- the audit subsystem isn't fit for namespaces right now), and
  sudo journalctl should show the journal and systemd-journald.service
  should be running. These systemd fixes are sufficient for nspawn, but
  not completely for unprivileged LXC containers -- there the journal will
  start working, but systemd-journald-audit.socket will still keep failing
  (this is less important)
  
  REGRESSION POTENTIAL: Very low. This only affects the fallback error
  code path if binding to the audit socket failed. In that case the
  journal is currently not working at all. This usually doesn't happen on
- real iron/VMs, so there is no practical change there.
+ real iron/VMs (they also always CAP_AUDIT_READ), so there is no
+ practical change there.

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

Title:
  journal is broken in unprivileged LXC and nspawn containers

Status in lxc package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Vivid:
  In Progress
Status in systemd source package in Wily:
  Fix Committed

Bug description:
  Test case
  -
  - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
  - Boot it. You'll get a lot of errors like

    [FAILED] Failed to start Journal Service.
    systemd-journald-audit.socket failed to listen on sockets: Operation not 
permitted
    [FAILED] Failed to listen on Journal Audit Socket.

  - The same happens with systemd-nspawn -b.

  As a result, the journal isn't working at all, and you have a bunch of
  failed journal related units.

  With a fixed systemd package, systemd in the container should realize
  that it cannot listen to the audit socket (as the kernel doesn't allow
  that -- the audit subsystem isn't fit for namespaces right now), and
  sudo journalctl should show the journal and systemd-journald.service
  should be running. These systemd fixes are sufficient for nspawn, but
  not completely for unprivileged LXC containers -- there the journal
  will start working, but systemd-journald-audit.socket will still keep
  failing (this is less important)

  REGRESSION POTENTIAL: Very low. This only affects the fallback error
  code path if binding to the audit socket failed. In that case the
  journal is currently not working at all. This usually doesn't happen
  on real iron/VMs (they also always CAP_AUDIT_READ), so there is no
  practical change there.

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

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

[Touch-packages] [Bug 1457311] [NEW] Xorg crash

2015-05-21 Thread Steven Basart

Public bug reported:

python tkinter causes xorg to crash.

I was using this http://ai.berkeley.edu/search.html

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May 21 00:46:12 2015
DistUpgraded: 2015-05-01 13:48:55,426 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
 virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:060a]
InstallationDate: Installed on 2014-10-01 (232 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: Dell Inc. XPS13 9333
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=25791661-9127-4464-b96a-9a016f64e1f7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to vivid on 2015-05-01 (19 days ago)
dmi.bios.date: 03/19/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0D13CR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: XPS13 9333
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Thu May 21 00:22:19 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4933 
 vendor CMN
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: amd64 apport-bug compiz-0.9 crash ubuntu vivid

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  python tkinter causes xorg to crash.

  I was using this http://ai.berkeley.edu/search.html

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 21 00:46:12 2015
  DistUpgraded: 2015-05-01 13:48:55,426 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-10-01 (232 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=25791661-9127-4464-b96a-9a016f64e1f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (19 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.

[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container

** Description changed:

  lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should
  shut down. This merely starts sigpwr.target right now, but nothing is
  hooked into it. That's deliberate for real iron systems as there it's
  usually UPSes sending that, which should be handled by e. g. nut, not
  directly systemd. However, for containers I believe that's a safe
  default.
  
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2015-May/009279.html
  
  SRU TEST CASE:
  --
  - Create a vivid LXC container (system or unprivileged)
  - Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.
+ 
+ REGRESSION POTENTIAL:
+ -
+ - This new unit is only active in containers (LXC, docker, nspawn, etc.). 
There a possible regression is that someone is running/testing nut or a similar 
UPS responder in a container, but that seems like a theoretical scenario only.
+ - There is no change for VMs or real hardware.

** Description changed:

  lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should
  shut down. This merely starts sigpwr.target right now, but nothing is
  hooked into it. That's deliberate for real iron systems as there it's
  usually UPSes sending that, which should be handled by e. g. nut, not
  directly systemd. However, for containers I believe that's a safe
  default.
+ 
+ For the record, in upstart we had /etc/init/shutdown.conf . This is
+ wrong, as it breaks UPS responders like nut (and it also halts instead
+ of poweroff). But we should provide this for containers under systemd.
  
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2015-May/009279.html
  
  SRU TEST CASE:
  --
  - Create a vivid LXC container (system or unprivileged)
  - Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.
  
  REGRESSION POTENTIAL:
  -
  - This new unit is only active in containers (LXC, docker, nspawn, etc.). 
There a possible regression is that someone is running/testing nut or a similar 
UPS responder in a container, but that seems like a theoretical scenario only.
  - There is no change for VMs or real hardware.

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

Title:
  lxc-stop does not shut down container

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Vivid:
  New
Status in systemd source package in Wily:
  In Progress

Bug description:
  lxc-stop sends SIGPWR to a container's pid 1 to notify it that it
  should shut down. This merely starts sigpwr.target right now, but
  nothing is hooked into it. That's deliberate for real iron systems
  as there it's usually UPSes sending that, which should be handled by
  e. g. nut, not directly systemd. However, for containers I believe
  that's a safe default.

  For the record, in upstart we had /etc/init/shutdown.conf . This is
  wrong, as it breaks UPS responders like nut (and it also halts instead
  of poweroff). But we should provide this for containers under systemd.

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2015-May/009279.html

  SRU TEST CASE:
  --
  - Create a vivid LXC container (system or unprivileged)
  - Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.

  REGRESSION POTENTIAL:
  -
  - This new unit is only active in containers (LXC, docker, nspawn, etc.). 
There a possible regression is that someone is running/testing nut or a similar 
UPS responder in a container, but that seems like a theoretical scenario only.
  - There is no change for VMs or real hardware.

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

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

[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container

Fix for Debian/wily: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimentalid=44c3369f97b

Backported for vivid: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu-vividid=7c45c5bc168df

** Changed in: systemd (Ubuntu Wily)
   Status: In Progress = Fix Committed

** Changed in: systemd (Ubuntu Vivid)
   Status: New = In Progress

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

Title:
  lxc-stop does not shut down container

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Vivid:
  In Progress
Status in systemd source package in Wily:
  Fix Committed

Bug description:
  lxc-stop sends SIGPWR to a container's pid 1 to notify it that it
  should shut down. This merely starts sigpwr.target right now, but
  nothing is hooked into it. That's deliberate for real iron systems
  as there it's usually UPSes sending that, which should be handled by
  e. g. nut, not directly systemd. However, for containers I believe
  that's a safe default.

  For the record, in upstart we had /etc/init/shutdown.conf . This is
  wrong, as it breaks UPS responders like nut (and it also halts instead
  of poweroff). But we should provide this for containers under systemd.

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2015-May/009279.html

  SRU TEST CASE:
  --
  - Create a vivid LXC container (system or unprivileged)
  - Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.

  REGRESSION POTENTIAL:
  -
  - This new unit is only active in containers (LXC, docker, nspawn, etc.). 
There a possible regression is that someone is running/testing nut or a similar 
UPS responder in a container, but that seems like a theoretical scenario only.
  - There is no change for VMs or real hardware.

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

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

[Touch-packages] [Bug 1243932] Re: aa-logprof: Log contains unknown mode senw

2015-05-21 Thread Steve Beattie

agent 8131, apparmor 2.9.2-0ubuntu1 just landed in wily and contains a
fix for this that attempts to only apply the transformation for file
based events, specifically in http://bazaar.launchpad.net/~apparmor-
dev/apparmor/2.9/revision/2905 , so you should no longer see this in
wily.

Also, this version (2.9.2) of the python tools has been backported to
trusty for an SRU. Please leave feedback on bug 1449769 if you are using
trusty as to whether the proposed packages improves the usability of the
tools in that release and if you discover significant regressions from
it.

Both 2.9.2 and the trusty SRU should also address the issue in  Bug
#1399027. Again, feedback in that bug on the trusty SRU would be greatly
appreciated.

Thanks for your patience!

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

Title:
  aa-logprof:  Log contains unknown mode senw

Status in AppArmor Linux application security framework:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  * aa-logprof does not work when dbus rule denials are present in the
  logs

  [Automated Test Case]

  * test_lp1243932_send, test_lp1243932_receive, and test_lp1243932_bind
  have been added to QRT's test-apparmor.py test script

  [Manual Test Case]

  * Load a profile that does not grant D-Bus access and create a D-Bus denial. 
Then,
    test aa-logprof.

    $ echo profile lp1243932 { file, } | sudo apparmor_parser -rq
    $ aa-exec -p lp1243932 -- dbus-send --print-reply --system \
    --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.ListNames
    Failed to open connection to system message bus: An AppArmor policy 
prevents this
    sender from sending this message to this recipient, 0 matched rules;
    type=method_call, sender=(null) (inactive) 
interface=org.freedesktop.DBus
    member=Hello error name=(unset) requested_reply=0
    destination=org.freedesktop.DBus (bus)
    $ aa-logprof -f /dev/null
    Reading log entries from /dev/null.
    Updating AppArmor profiles in /etc/apparmor.d.

  An unpatched aa-logprof will print similar output followed by:

    Log contains unknown mode senw.

  [Regression Potential]

  * The regression potential is low since aa-logprof currently refuses to work 
when D-Bus
    denials are present. The fix is minimal and has been reviewed by upstream.

  [Original Bug Report]

  since saucy aa-logprof does not work anymore:

  $ aa-logprof
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.

  Log contains unknown mode senw.

  the issues seem to be caused by dbus send denies:

  Oct 23 19:52:56 ubuntu dbus[2594]: apparmor=DENIED
  operation=dbus_method_call  bus=session
  path=/org/freedesktop/DBus interface=org.freedesktop.DBus
  member=Hello mask=send name=org.freedesktop.DBus pid=3552
  profile=/usr/bin/smuxi-frontend-gnome peer_profile=unconfined

  23:16 tyhicks my guess is the denial of a dbus send
  23:16 tyhicks senw is awful close to send
  23:17 tyhicks parse_event() in AppArmor.pm does this:
  23:18 tyhicks $rmask =~ s/d/w/g;
  23:18 tyhicks followed by:
  23:18 tyhicks fatal_error(sprintf(gettext('Log contains unknown mode %s.'), 
$rmask));

  ubuntu 13.10 amd64.

  apparmor-utils:
    Installed: 2.8.0-0ubuntu31
    Candidate: 2.8.0-0ubuntu31
    Version table:
   *** 2.8.0-0ubuntu31 0
  500 http://de.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

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

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

[Touch-packages] [Bug 1450213] Re: [SDK] cursor handle should not be visible if field is empty

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

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

Title:
  [SDK] cursor handle should not be visible if field is empty

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New

Bug description:
  On arale
  ui-tookit version 1.2.1485+15.04.20150429-0ubuntu1

  The big blue cursor handle should not be visible if the text field is
  empty, as dragging does nothing. It should only be displayed if the
  field has text (or spaces) in it where dragging would make sense.

  Steps to reproduce:

  1) reboot phone
  2) launch messaging-app
  3) swipe up from bottom to create new messaage

  Expected results:
  - cursor should be blinking in field
  - no text handle should be visible

  Actual results:
  - cursor is blinking in field
  - big blue cursor handle is visible

  NOTE, you can repeat this same thing by pressing the Search icon in
  the dash. The blue cursor appears even when nothing in paste buffer.

  SOLUTION:

  Don't show handler when tapping on an empty textfield. Long press
  textfield in order to access copy/paste

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

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

[Touch-packages] [Bug 1455567] Re: [UbuntuShape] Broken rendering under certain device orientation conditions

2015-05-21 Thread Loïc Molinari

** Summary changed:

- UbuntuShape fails to antialias when created while device is in landscape
+ [UbuntuShape] Broken rendering under certain device orientation conditions

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

Title:
  [UbuntuShape] Broken rendering under certain device orientation
  conditions

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  * flash latest vivid image
  * open the gallery
  * rotate device to landscape
  * pull in the launcher from above

  = see how launcher icons are not antialiased
  http://i.imgur.com/dh40r0N.png

  Or another way:

  * Open some random app
  * Rotate the device to landscape
  * using the right edge spread (now at the bottom) switch to the dash

  = see how all dash icons are not antialiased

  And potentially affects all apps:

  * Set the automaticOrientation property of the MainView to false
  * Rotate the device (ensuring the scene is updated)

  = See how the shape-based components are aliased and inner shadows
  are incorrect

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

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

[Touch-packages] [Bug 1449981] Re: BQ Device - r21: Browser sometimes overlaps notification menu

Screenshots showing other apps affected:
Messaging app
Dialer


** Attachment added: Desktop.tar
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1449981/+attachment/4401563/+files/Desktop.tar

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

Title:
  BQ Device - r21: Browser sometimes overlaps notification menu

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Conversely, sometimes the notification bar overlaps the URL bar or
  content of the browser. Swiping down still gets the notification menu
  in either case.

  But on first launch, it typically displays itself beneath the
  notification area like other apps so I assume this is the intended
  behaviour?

  So we have three possible states. killing and restarting the app
  solves the issue in the short-term.

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

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

[Touch-packages] [Bug 1445239] Re: apt's lists/partial fills disk

2015-05-21 Thread Alex Kretzschmar

Issue occurred again for me today when I interrupted apt-get update and
then reran a few minutes later.

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

Title:
  apt's lists/partial fills disk

Status in APT:
  New
Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Vivid:
  Confirmed

Bug description:
  Since I upgraded to vivid, apt fills the disk space at
  /var/lib/apt/lists/partial. This was triggered by the automatic update
  every day, and as a solution I killed the processes named `http`
  spawned by apt, and removed the offending file from lists/partial
  manually. Until now, `apt-get update` and `apt-get upgrade` had been
  working. However, today, when I tried `apt-get update`, it got stuck
  in some file, continuously increasing its size when at 100%.

  I tried inspecting the file to see if there is a repetition of data,
  and there seems to be, as I have suspected.

  First of all, the file is it.archive.ubuntu
  .com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 this time, but
  I'm not sure if the previous time it was also this file.

  I used `tail` and `hexdump` to figure out whether a certain pattern
  shows up in the file. Here are some examples:

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\bbdf\'
  c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\9b95\'
  c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\1234\'
  0002630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd
  0012630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd
  0022630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\76a8\'
  000fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c
  001fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c
  002fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c

  As you can see, it seems that after the error, a certain pattern seems
  to repeat every exactly 0x1 bytes. I attached a copy of those
  0x1 bytes that keep repeating (from an arbitrary offset).

  ---

  $ lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

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

  ---

  Do let me know if I can test further to see what could be wrong. I'll
  keep an eye next times the behavior repeat to make sure the file is
  the same / the pattern is the same and I'll report back. If you think
  the problem could be the Italy server, let me know and I'll try with a
  different one.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 17 00:04:05 2015
  SourcePackage: apt
  UpgradeStatus: Upgraded to vivid on 2015-03-28 (19 days ago)

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

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

[Touch-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

2015-05-21 Thread ThomasA

There might actually be something about the screen resolution. I am
observing this behaviour on my stationary PC with two Dell U2410 screens
running at 1920x1200. I am still running Ubuntu 14.04.

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

Title:
  Windows change Monitor/Desktop after screen lock

Status in Unity:
  Fix Released
Status in Unity 7.1 series:
  Fix Released
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I run a dual monitor configuration, with one portrait and one
  landscape.

  I nearly always have multiple applications open in multiple windows
  across both monitors and all virtual desktops.

  When I lock the screen and then unlock, my application windows will
  move from their original position.

  Sometimes they are in completely random positions;

  Other times they seem to get the monitors confused, and rather than
  being in the top half of the portrait monitor they are on the top half
  of the landscape monitor;

  Sometimes it is only a new desktop, but the monitor position is the
  same;

  Sometimes it is the same desktop, but on the other monitor.

  Description:  Ubuntu 13.10
  Release:  13.10

  What I expect to happen: When I unlock my computer, all the windows
  are in the same position on the same monitor and desktop as I left
  them.

  What actually happens: When I unlock my computer, some or all of the
  windows have been changed to a random position on a random monitor
  and/or desktop.

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

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

[Touch-packages] [Bug 1457400] [NEW] Ubuntu taking long to shutdown

2015-05-21 Thread johnygeorgemalayil

Public bug reported:

I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
onwards the ubuntu is taking long to shut down nearly 1:30 minutes.

I checked the shutdown log messages and I get the follow message.

A stop job is running for Session c2 of user * (25s/ 1min 30 s)

It count downs till 1:30 minutes and then shutdown the machine.

Why is it happening.

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


** Tags: plymouth shutdown time vivid

** Attachment added: error message
   https://bugs.launchpad.net/bugs/1457400/+attachment/4401579/+files/eVmf5.jpg

** Package changed: friends-app (Ubuntu) = plymouth (Ubuntu)

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

Title:
  Ubuntu taking long to shutdown

Status in plymouth package in Ubuntu:
  New

Bug description:
  I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
  onwards the ubuntu is taking long to shut down nearly 1:30 minutes.

  I checked the shutdown log messages and I get the follow message.

  A stop job is running for Session c2 of user * (25s/ 1min 30 s)

  It count downs till 1:30 minutes and then shutdown the machine.

  Why is it happening.

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

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

[Touch-packages] [Bug 1426589] Re: tc class statistics rates are all zero after upgrade to Trusty

2015-05-21 Thread Robie Basak

@Christopher

Why did you mark this Incomplete? It does not look Incomplete. As far as
I can tell, all information requested has been provided.

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

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

Title:
  tc class statistics rates are all zero after upgrade to Trusty

Status in iproute2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading an Ubuntu server from Lucid - Precise - Trusty the command:
  tc -s class show dev eth0
  no longer shows rates for my classification bands. This worked in Lucid, but 
not sure if something changed, or if I need to set some system configuration to 
make it work again. My current non-working version is:

  $ dpkg -s iproute2
  Package: iproute2
  Status: install ok installed
  Priority: important
  Section: net
  Installed-Size: 1147
  Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
  Architecture: amd64
  Multi-Arch: foreign
  Version: 3.12.0-2
  Replaces: iproute
  Provides: arpd
  Depends: libc6 (= 2.14), libdb5.3
  Recommends: libatm1 (= 2.4.1-17~), libxtables10
  Suggests: iproute2-doc
  Conflicts: arpd, iproute ( 2013-1)
  Conffiles:
   /etc/iproute2/group 3aea2c0e0dd75e13a5f8f48f2936915f
   /etc/iproute2/ematch_map b91e7f9b26918449bade9573f8871d61
   /etc/iproute2/rt_realms 7137bdf40e8d58c87ac7e3bba503767f
   /etc/iproute2/rt_tables a1313318d6778fe6b8c680248ef5a463
   /etc/iproute2/rt_dsfield 4264d5c7c8298300185aa04e1a736934
   /etc/iproute2/rt_protos 95ce0b4b5b79f5a8a45941fb418a904c
   /etc/iproute2/rt_scopes 6298b8df09e9bda23ea7da49021ca457
  Description: networking and traffic control tools
   The iproute2 suite is a collection of utilities for networking and
   traffic control.
   .
   These tools communicate with the Linux kernel via the (rt)netlink
   interface, providing advanced features not available through the
   legacy net-tools commands 'ifconfig' and 'route'.
  Original-Maintainer: Debian iproute2 Maintainers ah-ipro...@debian.org
  Homepage: http://www.linux-foundation.org/en/Net:Iproute2

  Here is the current output of the command, note that 'rate 0bit 0pps'
  is common to all classes, in Lucid this would produce non-zero values
  for active traffic:

  $ tc -s class show dev eth0
  class htb 2:1 root rate 4000Kbit ceil 1Kbit burst 1600b cburst 1600b
   Sent 140162776 bytes 377793 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 23022 borrowed: 0 giants: 0
   tokens: 46812 ctokens: 18725

  class htb 2:2 parent 2:1 leaf 3: prio 0 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2021584 bytes 6949 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 6505 borrowed: 189 giants: 0
   tokens: 187250 ctokens: 46812

  class htb 2:3 parent 2:1 leaf 4: prio 1 rate 2000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 16695548 bytes 216855 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 216846 borrowed: 9 giants: 0
   tokens: 94375 ctokens: 47187

  class htb 2:4 parent 2:1 leaf 5: prio 2 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2963040 bytes 46619 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 46619 borrowed: 0 giants: 0
   tokens: 193250 ctokens: 48312

  class htb 2:5 parent 2:1 leaf 6: prio 3 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 6 bytes 745 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 745 borrowed: 0 giants: 0
   tokens: 183000 ctokens: 45750

  class htb 2:6 parent 2:1 leaf 7: prio 4 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 80608262 bytes 79347 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 50544 borrowed: 13902 giants: 0
   tokens: 190750 ctokens: 47687

  class htb 2:7 parent 2:1 leaf 8: prio 5 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 37606539 bytes 26129 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 5617 borrowed: 8922 giants: 0
   tokens: -178485 ctokens: 24056

  class htb 2:8 parent 2:1 leaf 9: prio 6 rate 512000bit ceil 1000Kbit burst 
1600b cburst 1600b
   Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 0 borrowed: 0 giants: 0
   tokens: 390625 ctokens: 20

  class htb 2:9 parent 2:1 leaf a: prio 7 rate 1000Kbit ceil 1000Kbit burst 
1600b cburst 1600b
   Sent 167807 bytes 1149 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 1149 borrowed: 0 giants: 0
   tokens: 189875 ctokens: 189875

  Did something change upstream to

[Touch-packages] [Bug 1456112] [NEW] Phone doesn't use WiFi DNS when also connected to cell

You have been subscribed to a public bug:

Apologies if this is covered elsewhere but I couldn't find it and wasn't
sure what package would cover it so opted for system-settings. It is a
fairly specific bug given not everyone will be using BT wifi, but
probably the issue will arise with other ISPs.

When I turn on wifi at home, my phone connects to the Hub fine but Web
access is limited because the phone continues to use the DNS settings
from the cell network (I think). I get an error from BT about using
external DNS rather than those it supplies (required for the child
filter). I haven't tried disabling the filters yet but I could I
suppose.

If I turn on flight mode and then re-enable wifi everything works fine
but then I don't get phone calls, etc. of course.

Turing off flight mode breaks stuff again.

The phone is a BQ Aquaris E4.5 Ubuntu Edition running Ubuntu 14.10 (r22)
Image Part 20150508 Ubuntu Utopic Unicorn (Development branch)
armhf(20150508-031218), Device Image part 20150505-db7b5bd, Device build
description KRILIN01A-S14A_BQ_L100EN_1022_150508.

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


** Tags: bq dns touch
-- 
Phone doesn't use WiFi DNS when also connected to cell
https://bugs.launchpad.net/bugs/1456112
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

[Touch-packages] [Bug 1291575] Re: predictive text should be disabled on wifi password dialog

2015-05-21 Thread Christian Dywan

Once more the question, do we want universal show password and if so
what design?

** Also affects: ubuntu-ux
   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/1291575

Title:
  predictive text should be disabled on wifi password dialog

Status in Ubuntu UX bugs:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  on the wifi password dialog if you check show password and if word
  prediction/spell checking is on, the user is presented with word
  ribbon. this should be disabled by setting the Qt.ImNoPredicticveText
  hint on the entry field

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

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

[Touch-packages] [Bug 1455567] Re: [UbuntuShape] Broken rendering under certain device orientation conditions

2015-05-21 Thread Loïc Molinari

** Description changed:

  Steps to reproduce:
  
  * flash latest vivid image
  * open the gallery
  * rotate device to landscape
  * pull in the launcher from above
  
  = see how launcher icons are not antialiased
  http://i.imgur.com/dh40r0N.png
  
- 
  Or another way:
  
  * Open some random app
  * Rotate the device to landscape
  * using the right edge spread (now at the bottom) switch to the dash
  
  = see how all dash icons are not antialiased
+ 
+ And potentially affects all apps:
+ 
+ * Set the automaticOrientation property of the MainView to false
+ * Rotate the device (ensuring the scene is updated)
+ 
+ = See how the shape-based components are aliased and inner shadows are
+ incorrect

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

Title:
  [UbuntuShape] Broken rendering under certain device orientation
  conditions

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  * flash latest vivid image
  * open the gallery
  * rotate device to landscape
  * pull in the launcher from above

  = see how launcher icons are not antialiased
  http://i.imgur.com/dh40r0N.png

  Or another way:

  * Open some random app
  * Rotate the device to landscape
  * using the right edge spread (now at the bottom) switch to the dash

  = see how all dash icons are not antialiased

  And potentially affects all apps:

  * Set the automaticOrientation property of the MainView to false
  * Rotate the device (ensuring the scene is updated)

  = See how the shape-based components are aliased and inner shadows
  are incorrect

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

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

[Touch-packages] [Bug 1411640] Re: Super+Space key shortcut for Unity's launcher not always works

2015-05-21 Thread Miguel Rubio-Roy

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

I've observed that Super+Space actually works when space is pressed
very rapidly after Super. The delay must not exceed roughly half a
second.

This bug is probably a duplicate of
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136
and
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1201679

** This bug has been marked a duplicate of bug 1201679
   ibus' Super+Space shortcut (usually) doesn't work

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

Title:
  Super+Space key shortcut for Unity's launcher not always works

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

Bug description:
  When using the Super+Space key shortcut to show the launcher of
  Unity, sometimes I need to press several times the key combination to
  get the desired action.

  I've changed the default key shortcut using the Unity Tweak Tool. If
  I use Super+Rkey the shortcut always works the first time.

  I've had this problem during a year, first with 13.10 and now with
  14.04 LTS.

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

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

[Touch-packages] [Bug 1201679] Re: ibus' Super+Space shortcut (usually) doesn't work

2015-05-21 Thread Miguel Rubio-Roy

In 15.04 I've observed that Super+Space actually works when Space is
pressed very rapidly after Super. The delay must not exceed roughly
half a second.

** Changed in: unity
   Status: Expired = Confirmed

** Changed in: unity (Ubuntu)
   Status: Expired = Confirmed

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

Title:
  ibus' Super+Space shortcut (usually) doesn't work

Status in One Hundred Papercuts:
  Expired
Status in Unity:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  1. Add the ubuntu-desktop PPA on Ubuntu 13.10 Saucy
  sudo add-apt-repository ppa:ubuntu-desktop/ppa
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get install indicator-keyboard
  2. Log out and log back in.
  2. Open System SettingsRegion  Language
  3. Switch to the Text Entry tab.
  4. Click the + button to add at least two more keyboard layouts.
  5. Log out and log back in.
  6. Try to use the (new) default Super+Space keyboard shortcut to switch 
between keyboard layouts.

  What happens
  ---
  Usually, Super+Space is ignored. It worked for me once on login but every 
other time I tested it didn't work.
  It works fine in GNOME Shell but not in Unity.

  gsettings reset org.gnome.settings-daemon.plugins.media-keys 
switch-input-source
  seems to be enough to nudge Unity into respecting the Super+Space keyboard 
shortcut.

  My guess is that Unity is too aggressive in binding the Super key to
  itself.

  Workaround
  -
  Shift+Super+Space, the keyboard shortcut to switch backward between keyboard 
layouts works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jul 16 00:28:27 2013
  InstallationDate: Installed on 2013-06-14 (31 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

2015-05-21 Thread Ivo van der Wijk

I have exactly the same problem on my Dell XPS 13 laptop (14.04). It
seems to happen after the screen locks / turns off.

However, it seems to happen with one specific screen - I've been able to
normaly use standard full HD external screens, but once I use my
Samsung Syncmaster T240 screen, the bug appears. It might be related to
its odd resolution: 1920x1200.

I'm using unity 7.2.4 and the problem still persists.

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

Title:
  Windows change Monitor/Desktop after screen lock

Status in Unity:
  Fix Released
Status in Unity 7.1 series:
  Fix Released
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I run a dual monitor configuration, with one portrait and one
  landscape.

  I nearly always have multiple applications open in multiple windows
  across both monitors and all virtual desktops.

  When I lock the screen and then unlock, my application windows will
  move from their original position.

  Sometimes they are in completely random positions;

  Other times they seem to get the monitors confused, and rather than
  being in the top half of the portrait monitor they are on the top half
  of the landscape monitor;

  Sometimes it is only a new desktop, but the monitor position is the
  same;

  Sometimes it is the same desktop, but on the other monitor.

  Description:  Ubuntu 13.10
  Release:  13.10

  What I expect to happen: When I unlock my computer, all the windows
  are in the same position on the same monitor and desktop as I left
  them.

  What actually happens: When I unlock my computer, some or all of the
  windows have been changed to a random position on a random monitor
  and/or desktop.

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

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

[Touch-packages] [Bug 1457398] [NEW] systemd immediately unmounts manually mounted directories

2015-05-21 Thread Kirill Tkhai

Public bug reported:

Hi,

I've installed Ubuntu Vivid in OpenVZ container and observing strange
systemd behaviour.

Every time I do bind mount systemd immideately umounts it. Bind mount is on 
root partition
which is block device /dev/ploopXXX.

I've found the similar BUG about block device in Gentoo:

https://bugs.gentoo.org/show_bug.cgi?id=541402

They fixed the problem by the patch (see in the BUG^^^).

Also, there is BUG in mainstream:

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

I can reproduce the BUG with 100% probability and confirm it.
What's about backporting Gentoo's fix to Vivid?

Regards,
Kirill

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

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

Title:
  systemd immediately unmounts manually mounted directories

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I've installed Ubuntu Vivid in OpenVZ container and observing strange
  systemd behaviour.

  Every time I do bind mount systemd immideately umounts it. Bind mount is on 
root partition
  which is block device /dev/ploopXXX.

  I've found the similar BUG about block device in Gentoo:

  https://bugs.gentoo.org/show_bug.cgi?id=541402

  They fixed the problem by the patch (see in the BUG^^^).

  Also, there is BUG in mainstream:

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

  I can reproduce the BUG with 100% probability and confirm it.
  What's about backporting Gentoo's fix to Vivid?

  Regards,
  Kirill

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

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

[Touch-packages] [Bug 1373070] Re: full fix for disconnected path (paths)

2015-05-21 Thread Simon Déziel

To add one more data point, my Trusty server using the Utopic HWE kernel
also exhibits the problem:

May 21 12:27:28 xeon kernel: [95104.918686] audit: type=1400
audit(1432225648.230:57): apparmor=DENIED operation=sendmsg
info=Failed name lookup - disconnected path error=-13
profile=/usr/sbin/rsyslogd name=dev/log pid=3444 comm=logger
requested_mask=r denied_mask=r fsuid=0 ouid=0

$ apt-cache policy apparmor linux-image-3.16.0-38-generic rsyslog
apparmor:
  Installed: 2.8.95~2430-0ubuntu5.2
  Candidate: 2.8.95~2430-0ubuntu5.2
  Version table:
 *** 2.8.95~2430-0ubuntu5.2 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 2.8.95~2430-0ubuntu5.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 2.8.95~2430-0ubuntu5 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
linux-image-3.16.0-38-generic:
  Installed: 3.16.0-38.52~14.04.1
  Candidate: 3.16.0-38.52~14.04.1
  Version table:
 *** 3.16.0-38.52~14.04.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
rsyslog:
  Installed: 7.4.4-1ubuntu2.6
  Candidate: 7.4.4-1ubuntu2.6
  Version table:
 *** 7.4.4-1ubuntu2.6 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 7.4.4-1ubuntu2.3 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 7.4.4-1ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

Title:
  full fix for disconnected path (paths)

Status in cups package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  With the apparmor 3 RC1 upload, there is an incomplete bug fix for
  disconnected paths. This bug is to track that work.

  This denial may be related:
  Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 
audit(1411485050.722:2862): apparmor=DENIED operation=sendmsg info=Failed 
name lookup - disconnected path error=-13 profile=/usr/sbin/rsyslogd 
name=dev/log pid=7011 comm=logger requested_mask=r denied_mask=r 
fsuid=0 ouid=0

  This is related to bug 1375410

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

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

[Touch-packages] [Bug 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed

2015-05-21 Thread Zsombor Egri

If the warning disappears with 1.1 import then we're in trouble. It
should be displayed with 1.1 as well. It should be displayed till Theme
is used instead of theme. So if 1.3 import uses Theme, it will show a
warning.

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

Title:
  Theme.createStyleComponent deprecation useless warnings are displayed

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

Bug description:
  Take that example

  import QtQuick 2.0
  import Ubuntu.Components 0.1

  Item {
  Button {
  text: click
  }
  }

  run it on wily, you get those warnings

  QML Button: Theme.createStyleComponent() is deprecated. Use
  ThemeSettings instead.

  the warning is not helpful, it warns about a standard component issue
  (so something in the responsability of the uitk team, not the code
  writer), lists the issue on something you are not using (what is
  Theme.createStyleComponent() that's not used in the code example?),
  it's just confusing...

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

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

[Touch-packages] [Bug 1183738] Re: removed

2015-05-21 Thread removed

** Summary changed:

- libxml2 can not coexist with libxml2-i386 on 64-bit systems
+ removed

** Description changed:

- In Ubuntu 13.04 (64-bit), libxml2-i386 can not be installed in the same
- time with libxml2(-amd64), though some packages (for example, skype,
- wine) depend on libxml2-i386. As much software depends on libxml2-amd64
- (such as KDE), it is impossible to install wine, skype, etc. in 64-bit
- system using KDE.
+ removed

** Package changed: libxml2 (Ubuntu) = ubuntu

** Information type changed from Public to Private

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

Title:
  removed

Status in Ubuntu:
  Invalid

Bug description:
  removed

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

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

[Touch-packages] [Bug 1455408] Re: Recent call not cleared from indicator

2015-05-21 Thread Gustavo Pichorim Boiko

** Branch linked: lp:~boiko/telephony-service/clear_call_notifications

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

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

Title:
  Recent call not cleared from indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 42
  device name: arale
  channel: ubuntu-touch/tangxi/devel-proposed
  last update: 2015-05-15 04:19:20
  version version: 42
  version device: 
1e1b1cebe8900f5b62bed050a5c23a7765e62600d394cba528169d257e6ab36c
  version custom: 
8274419d06b4da1424e7f7339ff2f8276b38951951d8900e148a4fdfce8fba0d

  Steps to reproduce:
  1.Make a call from another device to this DUT, but don't answer it
  2.Hang up the call from remote end
  3.Swipe down on the Notification indicator, make sure the Notification 
indicator opens and shows the missed call
  4.Switch to Phone app to check the missed call
  Launcher/System Settings---Phone--Recent(Swip up from bottom)--Missed
  5.Tap on the missed call body 
  6.The missed call will shown in Dialer
  7.Back to check the state of Notifications indicator 

  Expected results:
  The missed call should not be displayed in Notifications indicator anymore

  Actual results:
  The missed call will not disappear in Notifications indicator unless tap on 
call back or send message or clear all

  Additional information:
  This issue could also be reproduced on Krillin r276

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

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

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

2015-05-21 Thread Steve Langasek

** Changed in: upstart (Ubuntu Utopic)
   Status: New = Won't Fix

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

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  New
Status in upstart source package in Wily:
  Fix Released
Status in upstart package in Ubuntu RTM:
  Fix Released

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

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

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

[Touch-packages] [Bug 1453285] Re: Emergency numbers for France (15, 17 and 18) are not available in emergency mode

** Tags added: emergency

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

Title:
  Emergency numbers for France (15, 17 and 18) are not available in
  emergency mode

Status in ofono package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  Incomplete

Bug description:
  Emergency numbers for France (15, 17 and 18) are not available in emergency 
mode.
  Dial button is inactive after these numbers are input.

  For information, emergency number for Europe (112) is available !! 
  This number (112) is used for europeans who are not in their country. 
  Example : a french who is located in Germany.

  In fact, a French who is located in France should call 15, 17 or 18 !!! 
  That's why I consider it as a bug, because it doesn't work.because

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

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

[Touch-packages] [Bug 1449594] Re: messaging app missing some messages and showing duplicates

** Changed in: canonical-devices-system-image
   Status: Confirmed = Fix Released

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

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

Title:
  messaging app missing some messages and showing duplicates

Status in the base for Ubuntu mobile products:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in messaging-app source package in Vivid:
  New

Bug description:
  Found this on arale r185

  Open a message thread for User1
  Lock the phone
  Send 4 sms messages from another phone to User1 (one, two, three, 
four)
  Unlock the phone

  Expected results:
  - message thread for User1  should show one, two, three, 'four
  - messaging indicator should be cleared

  Actual results:
  - message thread shows two, two, three, four
  - messaging indicator shows one still in the indicator

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

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

[Touch-packages] [Bug 1265602] Re: [PATCH] Please fix libjsoncpp Ubuntu packages (fixes minetest game crash when browsing Public Serverlist)

2015-05-21 Thread Markus Koschany

Fixed in Ubuntu 15.04

** Changed in: libjsoncpp (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: minetest (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  [PATCH] Please fix libjsoncpp Ubuntu packages (fixes minetest game
  crash when browsing Public Serverlist)

Status in libjsoncpp package in Ubuntu:
  Fix Released
Status in minetest package in Ubuntu:
  Fix Released
Status in libjsoncpp package in Debian:
  Fix Released

Bug description:
  Minetest package is buggy in Ubuntu Trusty and Saucy (crashes when selecting 
Client-Public Serverlist and doesn't work Mods-Online mod repository) and 
outdated - new minetest 0.4.9 was released few days ago.
  0.4.9 release contains some improvements and bugfixes.
  It would be nice if new Minetest 0.4.9 packages wouldn't crash when selecting 
Client-Public Serverlist and show no error when pressing Mods-Online mod 
repository in startup screen.

  0.4.8 → 0.4.9 New Features
  Logistic changes
  SQLite rollback (Mario Barrera  ShadowNinja)
  Implement HTTPFetch (kahrl)
  Replace SimpleThread with JThread (sapier) 
  Visual changes
  Shaders rework (RealBadAngel)
  Add configurable font shadow (xyz)
  Directional fog + horizon colors (Taoki) 
  Other things
  Implement modstore search tab and version picker (sapier) 

  Bug Fixes
   Fix line_of_sight() (sapier)
   Fix modstore/favourites hang by adding asynchronous Lua (sapier)
   Fix LevelDB maps (sfan5)
   Fix Lua mapgen override param handling (kwolekr)
   Fix leak and possible segfault in minetest.set_mapgen_params (kwolekr)
   Fix segfault in indev cave generation due to uninitialized variable (kwolekr)
   Check if width, height or start index of a list[] is negative (PilzAdam)
   Fix single character formspec field labels (BlockMen)
   Handle Lua errors in on_generate callbacks instead of throwing SIGABRT 
(kwolekr)
   Update mapgen params in ServerMap after Mapgen init (kwolekr) 

  Modding-related Changes
   Add area parameters back to calc_lighting() and set_lighting() (kwolekr)
   Add get_light_data() and set_light_data() to LuaVoxelManip (kwolekr)
   Add minetest.swap_node (Novatux)
   Assume a selection box for fences (0gb.us)
   Decoration: Add schematic Y-slice probability support (kwolekr)
   Add sneak and sneak_glitch in set_physics_override() (PilzAdam)
   Use a table in set_physics_override() (PilzAdam)
   Add 'on_prejoinplayer' callback (kaeza)
   Make line_of_sight return blocking node position (stujones11)
   Remove support for optdepends.txt (ShadowNinja)
   Add map feature generation notify Lua API (kwolekr) 

  See http://dev.minetest.net/Changelog

  Also I'm pasting terminal output after 0.4.8+repack2-3 crash when selecting 
Client-Public Serverlist:
  (crashes only official Ubuntu/Debian packages, but deb packages from 
https://launchpad.net/~minetestdevs/+archive/stable works fine)
  baltix@ubuntu:~$ minetest
  Irrlicht Engine version 1.8.0
  Linux 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64
  Using renderer: OpenGL 3.0
  Mesa DRI Intel(R) Haswell Server : Intel Open Source Technology Center
  OpenGL driver version is 1.2 or better.
  GLSL version: 1.3
  Loaded texture: /usr/share/games/minetest/games/minetest_game/menu/header.png
  Loaded texture: /usr/share/games/minetest/games/minetest_game/menu/icon.png

  19:42:47: ERROR[main]: MAINMENU ERROR: LuaError: C++ exception
  19:42:48: ERROR[main]: == ERROR FROM LUA ===
  19:42:48: ERROR[main]: Failed to load and run script from 
  19:42:48: ERROR[main]: /usr/share/games/minetest/builtin/mainmenu.lua:
  19:42:48: ERROR[main]: C++ exception
  19:42:48: ERROR[main]: === END OF ERROR FROM LUA 
  19:42:48: ERROR[main]: GUIEngine: unable to load builtin menu

  In thread 7f9f3eadc7c0:
  /build/buildd/minetest-0.4.8+repack2/src/guiEngine.cpp:199: 
GUIEngine::GUIEngine(irr::IrrlichtDevice*, irr::gui::IGUIElement*, 
IMenuManager*, irr::scene::ISceneManager*, MainMenuData*, bool): Assertion 
'no future without mainmenu == 0' failed.
  Debug stacks:
  DEBUG STACK FOR THREAD 7f9f3eadc7c0:
  #0  int main(int, char**)
  Aborted (core dumped)
  baltix@ubuntu:~$

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

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

[Touch-packages] [Bug 1304447] Re: apport-bug crashing on server install

2015-05-21 Thread Brad Figg

My running of the QRT apparmor tests is now passing on Trusty.

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

Title:
  apport-bug crashing on server install

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [impact]

  This bug prevents apport from reporting apparmor bugs on systems with
  non-UTF-8 characters showing up in syslog (the kernel reporting raw
  information from hardware is a common culprit).

  [steps to reproduce]

  1) on a system with non-UTF-8 characters in syslog, run 'apport -p apparmor 
-f'
 if the bug has been addressed, this should generate a report as
 expected instead of causing apport to crash.

  [regression potential]

  The change in the patch for this bug solely modifies the apparmor
  apport hook. It could potentially introduce more breakage there (but
  couldn't affect apparmor mediation); also the lp:qa-regression-testign
  test-apparmor.py attempts to exercise the apport hook, and this is
  exercised in as part of every linux kernel update by the kernel team
  (who frequently hit this issue due to the quirkiness of some of
  their hardware).

  [original description]

  jenkins@dagmar:~$ sudo apport-bug apparmor --save testlib.apport

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .ERROR: hook /usr/share/apport/package-hooks/source_apparmor.py crashed:
  Traceback (most recent call last):
    File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File /usr/lib/python3/dist-packages/apport/report.py, line 202, in 
_run_hook
  symb['add_info'](report)
    File /usr/share/apport/package-hooks/source_apparmor.py, line 48, in 
add_info
  report['KernLog'] = recent_kernlog(sec_re)
    File /usr/share/apport/package-hooks/source_apparmor.py, line 24, in 
recent_kernlog
  for line in open(file):
    File /usr/lib/python3.4/codecs.py, line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 6574: 
invalid continuation byte

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

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

[Touch-packages] [Bug 1444883] Re: Emergency numbers for China (110, 119) are not available in emergency mode

** Tags added: emergency

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

Title:
  Emergency numbers for China (110,119) are not available in emergency
  mode

Status in the base for Ubuntu mobile products:
  New
Status in ofono package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  New

Bug description:
  arale device, r177, ubuntu-touch/vivid-proposed

  Steps
  1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on 
Emergency Call)
  2. try input 911, 112 == OK
  2. try input 110, 119 == Dial button is inactive after number is input

  Expect
  Allow these numbers in emergency mode

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

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

[Touch-packages] [Bug 1449598] Re: messages not getting cleared from messaging indicator

for tracking ...

** 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 = In Progress

** Changed in: canonical-devices-system-image
Milestone: None = ww22-2015

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

Title:
  messages not getting cleared from messaging indicator

Status in the base for Ubuntu mobile products:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  New
Status in messaging-app source package in Vivid:
  New

Bug description:
  on arale r185

  Not sure exact steps to reproduce, but sometimes when reading a
  message in the messaging app it still remains in the messaging menu.
  It does not get cleared as it should.

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

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

[Touch-packages] [Bug 1304447] Re: apport-bug crashing on server install

2015-05-21 Thread Steve Beattie

Thanks, Brad. Marking verification-done.

** Tags added: verification-done

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

Title:
  apport-bug crashing on server install

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [impact]

  This bug prevents apport from reporting apparmor bugs on systems with
  non-UTF-8 characters showing up in syslog (the kernel reporting raw
  information from hardware is a common culprit).

  [steps to reproduce]

  1) on a system with non-UTF-8 characters in syslog, run 'apport -p apparmor 
-f'
 if the bug has been addressed, this should generate a report as
 expected instead of causing apport to crash.

  [regression potential]

  The change in the patch for this bug solely modifies the apparmor
  apport hook. It could potentially introduce more breakage there (but
  couldn't affect apparmor mediation); also the lp:qa-regression-testign
  test-apparmor.py attempts to exercise the apport hook, and this is
  exercised in as part of every linux kernel update by the kernel team
  (who frequently hit this issue due to the quirkiness of some of
  their hardware).

  [original description]

  jenkins@dagmar:~$ sudo apport-bug apparmor --save testlib.apport

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .ERROR: hook /usr/share/apport/package-hooks/source_apparmor.py crashed:
  Traceback (most recent call last):
    File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File /usr/lib/python3/dist-packages/apport/report.py, line 202, in 
_run_hook
  symb['add_info'](report)
    File /usr/share/apport/package-hooks/source_apparmor.py, line 48, in 
add_info
  report['KernLog'] = recent_kernlog(sec_re)
    File /usr/share/apport/package-hooks/source_apparmor.py, line 24, in 
recent_kernlog
  for line in open(file):
    File /usr/lib/python3.4/codecs.py, line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 6574: 
invalid continuation byte

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

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

[Touch-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen

2015-05-21 Thread Ammar Ahmad

Still unsure how to produce a backtrace...

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

Title:
  Unity/compiz crashes when locking screen

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

Bug description:
  Since a recent update (around April 29th), sometimes (approximately once a 
day) when I lock my computer screen (CTRL+L or using system menu) the computer 
freeze for a while (2 to 30 seconds) before showing the login screen.
  Then when I try to unlock the screen I need to enter my password twice (with 
no error message after the first try).
  Once logged in, all applications are closed. Uptime is still running (since 
no reboot) and services too (with no interruption).

  Looking at the apport.log file (see attached) it seems that when I try
  to lock the screen, compiz crashes.

  I've attached the compiz crash file too (_usr_bin_compiz.1000.crash)
  but without the 100Mo data of base64 core dumb…

  
  I'm using Ubuntu 14.04 AMD64.
  Graphics drivers: nvidia-331.113 (tested)

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

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

[Touch-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen

2015-05-21 Thread Ammar Ahmad

Still unsure how to produce a backtrace...
Can anyone tell how to downgrade to previous versions?

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

Title:
  Unity/compiz crashes when locking screen

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

Bug description:
  Since a recent update (around April 29th), sometimes (approximately once a 
day) when I lock my computer screen (CTRL+L or using system menu) the computer 
freeze for a while (2 to 30 seconds) before showing the login screen.
  Then when I try to unlock the screen I need to enter my password twice (with 
no error message after the first try).
  Once logged in, all applications are closed. Uptime is still running (since 
no reboot) and services too (with no interruption).

  Looking at the apport.log file (see attached) it seems that when I try
  to lock the screen, compiz crashes.

  I've attached the compiz crash file too (_usr_bin_compiz.1000.crash)
  but without the 100Mo data of base64 core dumb…

  
  I'm using Ubuntu 14.04 AMD64.
  Graphics drivers: nvidia-331.113 (tested)

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

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

[Touch-packages] [Bug 1457170] Re: Usage of cmake-extras is out of date

2015-05-21 Thread Rodney Dawes

** Changed in: unity-scope-click (Ubuntu)
   Status: New = In Progress

** Changed in: unity-scope-click (Ubuntu)
   Importance: Undecided = High

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

Title:
  Usage of cmake-extras is out of date

Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  The API of cmake-extras' EnableCoverageReport changed from 0.3 to 0.4,
  from an enable_coverage variable to using the coverage build type. The
  usage within unity-scope-click needs to be updated to 0.4 to be useful
  in vivid overlay and wily.

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

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

[Touch-packages] [Bug 1457357] Re: Don't hard code the date format of event card

The branch should fix it (and I tested it to fix the issue), the
gallery-app just needs landing at some point.

** Changed in: gallery-app (Ubuntu)
 Assignee: Timo Jyrinki (timo-jyrinki) = (unassigned)

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

Title:
  Don't hard code the date format of event card

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  Hard-coding the date format to MMM  causes problems when the
  month name is too long, see screenshot.

  Note MMM should be abbreviated, but at least for Finnish it's not and
  it's even conjugated making it even longer. So it's probably also a Qt
  (translation) bug but flexibility here would help.

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

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

[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container

This bug was fixed in the package systemd - 219-10ubuntu1

---
systemd (219-10ubuntu1) wily; urgency=medium

  * Merge with Debian experimental branch. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
  script.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also run ifup in the background during boot,
  to avoid blocking network.target. (LP: #1425376)
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- systemctl: Don't forward telinit u to upstart. This works around
  upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
  that changes to point to systemd during the upgrade. This avoids running
  systemd during a dist-upgrade. (LP: #1430479)
- Drop hwdb-update dependency from udev-trigger.service, which got
  introduced in v219-stable. This causes udev and plymouth to start too
  late and isn't really needed in Ubuntu yet as we don't support stateless
  systems yet and handle hwdb.bin updates through dpkg triggers. This can
  be dropped again with initramfs-tools 0.117.
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor dep to the Ubuntu version where it moved to /lib.
- Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
- Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

systemd (219-10) experimental; urgency=medium

  * Fix assertion crash with empty Exec*= paths. (LP: #1454173)
  * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch
and Avoid-reloading-services-when-shutting-down.patch: This was fixed more
robustly in invoke-rc.d and service now, see #777113.
  * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down.
  * Fix tentative state of devices which are not in /dev (mostly in
containers), and avoid overzealous cleanup unmounting of mounts from them.
(LP: #102)
  * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls.
  * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long
obsolete, CD ejection with the hardware button works properly without it.
  * Re-enable-journal-forwarding-to-syslog.patch: Update patch description,
journal.conf.d/ exists now.
  * journal: Gracefully handle failure to bind to audit socket, which is known
to fail in namespaces (containers) with current kernels. Also
conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ.
(LP: #1457054)
  * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping
of unit names, reduces the delta, and will make it easier to get a common
solution for integrating ifup.d/ scripts with networkd.
  * When booting with quiet, run the initramfs' udevd with notice log
level. (LP: #1432171)
  * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in
a

[Touch-packages] [Bug 1444402] Re: LXC with r/w sys and udev keeps trying to unmount bind mounts

This bug was fixed in the package systemd - 219-10ubuntu1

---
systemd (219-10ubuntu1) wily; urgency=medium

  * Merge with Debian experimental branch. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
  script.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also run ifup in the background during boot,
  to avoid blocking network.target. (LP: #1425376)
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- systemctl: Don't forward telinit u to upstart. This works around
  upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
  that changes to point to systemd during the upgrade. This avoids running
  systemd during a dist-upgrade. (LP: #1430479)
- Drop hwdb-update dependency from udev-trigger.service, which got
  introduced in v219-stable. This causes udev and plymouth to start too
  late and isn't really needed in Ubuntu yet as we don't support stateless
  systems yet and handle hwdb.bin updates through dpkg triggers. This can
  be dropped again with initramfs-tools 0.117.
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor dep to the Ubuntu version where it moved to /lib.
- Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
- Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

systemd (219-10) experimental; urgency=medium

  * Fix assertion crash with empty Exec*= paths. (LP: #1454173)
  * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch
and Avoid-reloading-services-when-shutting-down.patch: This was fixed more
robustly in invoke-rc.d and service now, see #777113.
  * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down.
  * Fix tentative state of devices which are not in /dev (mostly in
containers), and avoid overzealous cleanup unmounting of mounts from them.
(LP: #102)
  * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls.
  * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long
obsolete, CD ejection with the hardware button works properly without it.
  * Re-enable-journal-forwarding-to-syslog.patch: Update patch description,
journal.conf.d/ exists now.
  * journal: Gracefully handle failure to bind to audit socket, which is known
to fail in namespaces (containers) with current kernels. Also
conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ.
(LP: #1457054)
  * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping
of unit names, reduces the delta, and will make it easier to get a common
solution for integrating ifup.d/ scripts with networkd.
  * When booting with quiet, run the initramfs' udevd with notice log
level. (LP: #1432171)
  * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in
a

[Touch-packages] [Bug 1432171] Re: [udev] Shows starting version 219 boot message even with quiet

This bug was fixed in the package systemd - 219-10ubuntu1

---
systemd (219-10ubuntu1) wily; urgency=medium

  * Merge with Debian experimental branch. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
  script.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also run ifup in the background during boot,
  to avoid blocking network.target. (LP: #1425376)
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- systemctl: Don't forward telinit u to upstart. This works around
  upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
  that changes to point to systemd during the upgrade. This avoids running
  systemd during a dist-upgrade. (LP: #1430479)
- Drop hwdb-update dependency from udev-trigger.service, which got
  introduced in v219-stable. This causes udev and plymouth to start too
  late and isn't really needed in Ubuntu yet as we don't support stateless
  systems yet and handle hwdb.bin updates through dpkg triggers. This can
  be dropped again with initramfs-tools 0.117.
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor dep to the Ubuntu version where it moved to /lib.
- Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
- Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

systemd (219-10) experimental; urgency=medium

  * Fix assertion crash with empty Exec*= paths. (LP: #1454173)
  * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch
and Avoid-reloading-services-when-shutting-down.patch: This was fixed more
robustly in invoke-rc.d and service now, see #777113.
  * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down.
  * Fix tentative state of devices which are not in /dev (mostly in
containers), and avoid overzealous cleanup unmounting of mounts from them.
(LP: #102)
  * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls.
  * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long
obsolete, CD ejection with the hardware button works properly without it.
  * Re-enable-journal-forwarding-to-syslog.patch: Update patch description,
journal.conf.d/ exists now.
  * journal: Gracefully handle failure to bind to audit socket, which is known
to fail in namespaces (containers) with current kernels. Also
conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ.
(LP: #1457054)
  * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping
of unit names, reduces the delta, and will make it easier to get a common
solution for integrating ifup.d/ scripts with networkd.
  * When booting with quiet, run the initramfs' udevd with notice log
level. (LP: #1432171)
  * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in
a

[Touch-packages] [Bug 1317449]

2015-05-21 Thread Caulier-gilles-9

*** Bug 347786 has been marked as a duplicate of this bug. ***

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in digikam package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Fix Released
Status in digikam source package in Trusty:
  Confirmed
Status in sqlite3 source package in Trusty:
  Confirmed
Status in digikam source package in Utopic:
  Fix Released
Status in sqlite3 source package in Utopic:
  Fix Released

Bug description:
  Please update sqlite to a version  3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions  3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3  3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

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

[Touch-packages] [Bug 1454173] Re: Assertion crash with ExecStart=- /path

This bug was fixed in the package systemd - 219-10ubuntu1

---
systemd (219-10ubuntu1) wily; urgency=medium

  * Merge with Debian experimental branch. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
  script.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also run ifup in the background during boot,
  to avoid blocking network.target. (LP: #1425376)
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- systemctl: Don't forward telinit u to upstart. This works around
  upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
  that changes to point to systemd during the upgrade. This avoids running
  systemd during a dist-upgrade. (LP: #1430479)
- Drop hwdb-update dependency from udev-trigger.service, which got
  introduced in v219-stable. This causes udev and plymouth to start too
  late and isn't really needed in Ubuntu yet as we don't support stateless
  systems yet and handle hwdb.bin updates through dpkg triggers. This can
  be dropped again with initramfs-tools 0.117.
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor dep to the Ubuntu version where it moved to /lib.
- Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
- Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

systemd (219-10) experimental; urgency=medium

  * Fix assertion crash with empty Exec*= paths. (LP: #1454173)
  * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch
and Avoid-reloading-services-when-shutting-down.patch: This was fixed more
robustly in invoke-rc.d and service now, see #777113.
  * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down.
  * Fix tentative state of devices which are not in /dev (mostly in
containers), and avoid overzealous cleanup unmounting of mounts from them.
(LP: #102)
  * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls.
  * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long
obsolete, CD ejection with the hardware button works properly without it.
  * Re-enable-journal-forwarding-to-syslog.patch: Update patch description,
journal.conf.d/ exists now.
  * journal: Gracefully handle failure to bind to audit socket, which is known
to fail in namespaces (containers) with current kernels. Also
conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ.
(LP: #1457054)
  * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping
of unit names, reduces the delta, and will make it easier to get a common
solution for integrating ifup.d/ scripts with networkd.
  * When booting with quiet, run the initramfs' udevd with notice log
level. (LP: #1432171)
  * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in
a

[Touch-packages] [Bug 1298842] Re: pulseaudio crashed with SIGABRT in pa_xmalloc()

2015-05-21 Thread David Henningsson

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Committed = Fix Released

** Also affects: pulseaudio (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  pulseaudio crashed with SIGABRT in pa_xmalloc()

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Trusty:
  New

Bug description:
  1. Powered up laptop from a powered off state
  2. Logged in
  3. Was presented with A system error has occurred
  4. Later notice that No PulseAudio daemon running, or not running as session 
daemon.

  I cannot control the volume, since no pulseaudio daemon is running
  $ pacmd does not work due to 4

  Trying to start pulseaudio gives me

  $ pulseaudio
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: pa_pid_file_create() failed.

  Trying to kill it yields

  $ pulseaudio -k
  E: [pulseaudio] main.c: Failed to kill daemon: No such file or directory

  I have no idea what I am doing:

  $ sudo pulseaudio -k
  [sudo] password for jonas:
  E: [pulseaudio] core-util.c: Home directory not accessible: Permission denied
  E: [pulseaudio] main.c: Failed to kill daemon: Success

  jonas@jonas-xps:~$ pulseaudio -k
  E: [pulseaudio] main.c: Failed to kill daemon: No such file or directory

  jonas@jonas-xps:~$ pulseaudio
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  E: [pulseaudio] module-device-restore.c: Failed to parse module arguments
  E: [pulseaudio] module.c: Failed to load module module-device-restore 
(argument: restore_device=false): initialization failed.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.
  E: [pulseaudio] xmalloc.c: Assertion 'size  0' failed at pulse/xmalloc.c:62, 
function pa_xmalloc(). Aborting.
  Aborted (core dumped)

  Happens due to 
  load-module module-device-restore restore_device=false

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Mar 28 09:17:13 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2013-08-27 (212 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_xmalloc () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_module_unload_all () from /usr/lib/libpulsecore-4.0.so
   main ()
  Title: pulseaudio crashed with SIGABRT in pa_xmalloc()
  UpgradeStatus: Upgraded to trusty on 2014-03-20 (7 days ago)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/15/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2014-03-27T13:17:10.652148

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

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

[Touch-packages] [Bug 1457357] Re: Don't hard code the date format of event card

** Changed in: gallery-app (Ubuntu)
 Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki)

** Branch linked: lp:~timo-jyrinki/gallery-
app/allow_translating_date_strings

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

Title:
  Don't hard code the date format of event card

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  Hard-coding the date format to MMM  causes problems when the
  month name is too long, see screenshot.

  Note MMM should be abbreviated, but at least for Finnish it's not and
  it's even conjugated making it even longer. So it's probably also a Qt
  (translation) bug but flexibility here would help.

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

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

[Touch-packages] [Bug 1457468] Re: Text selection is partially broken when textarea is partially out of view

2015-05-21 Thread Andrea Bernabei

My proposal is:
We need a way to make sure that the dragging cursor is always *on screen*.
What we can do is:
1) scroll the inner textarea flickable;
2) while (!cursorIsOnScreen) { go up in the hierarchy and look for another 
flickable and scroll that as much as possible to try bring the cursor into the 
view.  } There may be N flickables along the way, in that case we'll 
potentially scroll N flickables, if only scrolling some isn't enough.

HOWEVER:
This is just a solution. For instance, it doesn't take into account the cases 
where:
- The app developer uses something else than a flickable, like a custom 
scrolling component
- The app developer creates a form page which doesn't have any scrollable 
behaviour which would account for devices where content of the form doesn't fit 
in the view. In that case, I think it's app dev's fault as he hasn't designed 
the app properly. But we may think about a way to help them...


** Description changed:

  Description:
  
  In some cases, text selection doesn't work properly, in particular it's
  not possible to drag the selection handles all the way to the bottom (or
  the top) if the top (or bottom) of the TextArea is outside of the view.
+ 
+ This bug is partially overlapping with
+ https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1200371
+ but they're not the same thing.
  
  I have been thinking for a few minutes about what those cases are, and I
  came up with the following list:
  
  - If the TextArea is taller than the view, then one part of it will be
  out of screen for sure. Let's suppose it's the top side. In that case,
  the user wouldn't be able, starting the drag from *within* the view, to
  reach the text which is *outside* of the view. This happens, for
  instance, in any app which includes a text editor. Once the text fills
  more than one page, the user won't be able to select text starting from
  anywhere inside the current view, and ending anything outside of the
  view. This is probably a very common usecase, together with the second
  one.
  
  - If the TextArea is inside a Flickable and that Flickable is scrolled
  in a way that partially hides the TextArea. This happens whenever an app
  has, for instance, a listview which holds many field of some kind of
  forms the user has to fill in. The user fills the visible fields, then
  scroll down, thus potentially partially hiding (or partially bringing
  into the view) on of the fields.
  
  - If the TextArea is inside a Flickable, which is inside other
  Flickables, and they're scrolled in a way that the TextArea is only
  partilly into the view. This is the generic case (even though probably
  not the most common one).
  
  I'll write my solution proposal in a comment.

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

Title:
  Text selection is partially broken when textarea is partially out of
  view

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

Bug description:
  Description:

  In some cases, text selection doesn't work properly, in particular
  it's not possible to drag the selection handles all the way to the
  bottom (or the top) if the top (or bottom) of the TextArea is outside
  of the view.

  This bug is partially overlapping with
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1200371 but they're not the same thing.

  I have been thinking for a few minutes about what those cases are, and
  I came up with the following list:

  - If the TextArea is taller than the view, then one part of it will be
  out of screen for sure. Let's suppose it's the top side. In that case,
  the user wouldn't be able, starting the drag from *within* the view,
  to reach the text which is *outside* of the view. This happens, for
  instance, in any app which includes a text editor. Once the text fills
  more than one page, the user won't be able to select text starting
  from anywhere inside the current view, and ending anything outside of
  the view. This is probably a very common usecase, together with the
  second one.

  - If the TextArea is inside a Flickable and that Flickable is scrolled
  in a way that partially hides the TextArea. This happens whenever an
  app has, for instance, a listview which holds many field of some kind
  of forms the user has to fill in. The user fills the visible fields,
  then scroll down, thus potentially partially hiding (or partially
  bringing into the view) on of the fields.

  - If the TextArea is inside a Flickable, which is inside other
  Flickables, and they're scrolled in a way that the TextArea is only
  partilly into the view. This is the generic case (even though probably
  not the most common one).

  I'll write my solution proposal in a comment.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1457468] [NEW] Text selection is partially broken when textarea is partially out of view

2015-05-21 Thread Andrea Bernabei

Public bug reported:

Description:

In some cases, text selection doesn't work properly, in particular it's
not possible to drag the selection handles all the way to the bottom (or
the top) if the top (or bottom) of the TextArea is outside of the view.

This bug is partially overlapping with
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1200371
but they're not the same thing.

I have been thinking for a few minutes about what those cases are, and I
came up with the following list:

- If the TextArea is taller than the view, then one part of it will be
out of screen for sure. Let's suppose it's the top side. In that case,
the user wouldn't be able, starting the drag from *within* the view, to
reach the text which is *outside* of the view. This happens, for
instance, in any app which includes a text editor. Once the text fills
more than one page, the user won't be able to select text starting from
anywhere inside the current view, and ending anything outside of the
view. This is probably a very common usecase, together with the second
one.

- If the TextArea is inside a Flickable and that Flickable is scrolled
in a way that partially hides the TextArea. This happens whenever an app
has, for instance, a listview which holds many field of some kind of
forms the user has to fill in. The user fills the visible fields, then
scroll down, thus potentially partially hiding (or partially bringing
into the view) on of the fields.

- If the TextArea is inside a Flickable, which is inside other
Flickables, and they're scrolled in a way that the TextArea is only
partilly into the view. This is the generic case (even though probably
not the most common one).

I'll write my solution proposal in a comment.

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

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

Title:
  Text selection is partially broken when textarea is partially out of
  view

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

Bug description:
  Description:

  In some cases, text selection doesn't work properly, in particular
  it's not possible to drag the selection handles all the way to the
  bottom (or the top) if the top (or bottom) of the TextArea is outside
  of the view.

  This bug is partially overlapping with
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1200371 but they're not the same thing.

  I have been thinking for a few minutes about what those cases are, and
  I came up with the following list:

  - If the TextArea is taller than the view, then one part of it will be
  out of screen for sure. Let's suppose it's the top side. In that case,
  the user wouldn't be able, starting the drag from *within* the view,
  to reach the text which is *outside* of the view. This happens, for
  instance, in any app which includes a text editor. Once the text fills
  more than one page, the user won't be able to select text starting
  from anywhere inside the current view, and ending anything outside of
  the view. This is probably a very common usecase, together with the
  second one.

  - If the TextArea is inside a Flickable and that Flickable is scrolled
  in a way that partially hides the TextArea. This happens whenever an
  app has, for instance, a listview which holds many field of some kind
  of forms the user has to fill in. The user fills the visible fields,
  then scroll down, thus potentially partially hiding (or partially
  bringing into the view) on of the fields.

  - If the TextArea is inside a Flickable, which is inside other
  Flickables, and they're scrolled in a way that the TextArea is only
  partilly into the view. This is the generic case (even though probably
  not the most common one).

  I'll write my solution proposal in a comment.

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

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

[Touch-packages] [Bug 1457474] [NEW] Remove qtscript from ubuntu-touch

Public bug reported:

Qt Script is on outdated JavaScript Core engine that was only used by Qt
WebKit. Both are now deprecated by upstream, Qt Script is not directly
used by any app and Qt Script too should go like Qt WebKit earlier.

** Affects: ubuntu-touch-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Branch linked: lp:~timo-jyrinki/ubuntu-seeds/ubuntu-
touch.wily_remove_qtscript

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

Title:
  Remove qtscript from ubuntu-touch

Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  Qt Script is on outdated JavaScript Core engine that was only used by
  Qt WebKit. Both are now deprecated by upstream, Qt Script is not
  directly used by any app and Qt Script too should go like Qt WebKit
  earlier.

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

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

[Touch-packages] [Bug 1457054] Re: journal is broken in unprivileged LXC and nspawn containers

This bug was fixed in the package systemd - 219-10ubuntu1

---
systemd (219-10ubuntu1) wily; urgency=medium

  * Merge with Debian experimental branch. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
  with wait-for-root. Will get applicable to Debian once Debian gets
  wait-for-root in initramfs-tools.
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to lvm2 which is handled with udev rules in Ubuntu.
- Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
  script.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for auto class. We don't
  really support allow-hotplug in Ubuntu at the moment, so we need to
  deal with auto devices appearing after /etc/init.d/networking start
  already ran. (LP: #1374521) Also run ifup in the background during boot,
  to avoid blocking network.target. (LP: #1425376)
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- systemctl: Don't forward telinit u to upstart. This works around
  upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
  that changes to point to systemd during the upgrade. This avoids running
  systemd during a dist-upgrade. (LP: #1430479)
- Drop hwdb-update dependency from udev-trigger.service, which got
  introduced in v219-stable. This causes udev and plymouth to start too
  late and isn't really needed in Ubuntu yet as we don't support stateless
  systems yet and handle hwdb.bin updates through dpkg triggers. This can
  be dropped again with initramfs-tools 0.117.
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Lower libappamor dep to the Ubuntu version where it moved to /lib.
- Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
- Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)
- Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
  This currently fails when being triggered by Jenkins, but is totally
  unreproducible when running this manually on the exact same machine.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.

systemd (219-10) experimental; urgency=medium

  * Fix assertion crash with empty Exec*= paths. (LP: #1454173)
  * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch
and Avoid-reloading-services-when-shutting-down.patch: This was fixed more
robustly in invoke-rc.d and service now, see #777113.
  * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down.
  * Fix tentative state of devices which are not in /dev (mostly in
containers), and avoid overzealous cleanup unmounting of mounts from them.
(LP: #102)
  * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls.
  * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long
obsolete, CD ejection with the hardware button works properly without it.
  * Re-enable-journal-forwarding-to-syslog.patch: Update patch description,
journal.conf.d/ exists now.
  * journal: Gracefully handle failure to bind to audit socket, which is known
to fail in namespaces (containers) with current kernels. Also
conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ.
(LP: #1457054)
  * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping
of unit names, reduces the delta, and will make it easier to get a common
solution for integrating ifup.d/ scripts with networkd.
  * When booting with quiet, run the initramfs' udevd with notice log
level. (LP: #1432171)
  * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in
a

[Touch-packages] [Bug 1456112] Re: Phone doesn't use WiFi DNS when also connected to cell

2015-05-21 Thread Mathieu Trudel-Lapierre

Could you attach /var/log/syslog from the phone when it's connected to
both wifi and 3G? We should be able to know from there whether it
includes all the nameservers it should.

From there, it's up to whichever responds faster among all the
nameservers, which will be used.

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

Title:
  Phone doesn't use WiFi DNS when also connected to cell

Status in the base for Ubuntu mobile products:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Apologies if this is covered elsewhere but I couldn't find it and
  wasn't sure what package would cover it so opted for system-settings.
  It is a fairly specific bug given not everyone will be using BT wifi,
  but probably the issue will arise with other ISPs.

  When I turn on wifi at home, my phone connects to the Hub fine but Web
  access is limited because the phone continues to use the DNS settings
  from the cell network (I think). I get an error from BT about using
  external DNS rather than those it supplies (required for the child
  filter). I haven't tried disabling the filters yet but I could I
  suppose.

  If I turn on flight mode and then re-enable wifi everything works fine
  but then I don't get phone calls, etc. of course.

  Turing off flight mode breaks stuff again.

  The phone is a BQ Aquaris E4.5 Ubuntu Edition running Ubuntu 14.10
  (r22) Image Part 20150508 Ubuntu Utopic Unicorn (Development branch)
  armhf(20150508-031218), Device Image part 20150505-db7b5bd, Device
  build description KRILIN01A-S14A_BQ_L100EN_1022_150508.

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

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

[Touch-packages] [Bug 1453812] Re: System freeze when using LibreOffice Writer

2015-05-21 Thread vmagnin

I have updated the BIOS:
$ sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
786G3 v03.57
07/15/2013

But the bug still occurs. LibreOffice can still freeze totally the
system.

** Changed in: xorg (Ubuntu)
   Status: Incomplete = New

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

Title:
  System freeze when using LibreOffice Writer

Status in xorg package in Ubuntu:
  New

Bug description:
  LibreOffice Writer is freezing the system after a few minutes (Ubuntu
  15.04, libreoffice-writer 4.4.2-0ubuntu1): the only possible action is
  moving the mouse pointer on the screen. Impossible to connect to a tty
  session to kill Xorg. A physical reboot is necessary. Note that I used
  LibreOffice Calc without problem.

  The problem has been encountered also under Fedora 21:
  http://forums.fedora-fr.org/viewtopic.php?id=63428
  The solution proposed on this french forum is to replace the nouveau driver 
by the nvidia proprietary driver (340.76).
  It works for me.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  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
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:063a]
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP Z400 Workstation
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Tags:  vivid ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/06/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G3 v03.07
  dmi.board.asset.tag: CZC0195Y06
  dmi.board.name: 0B4Ch
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: D
  dmi.chassis.asset.tag: CZC0195Y06
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G3v03.07:bd04/06/2010:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0B4Ch:rvrD:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z400 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Wed May 20 08:19:58 2015
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1029114] Re: With autohide and the HUD enabled the launcher can appear at incorrect times

** Description changed:

[ Impact ]

When the Launcher is suddenly revealed when it's not intended to can
cause confusion and a poor user experience.

[ Test Case ]

1. Turn on launcher auto hide
2. Display the HUD (tap Alt)
3. Move the mouse to the left side of the screen (as if you are showing the
launcher)
4. Note the launcher is not displayed
5. Now hide the HUD (either tap Alt or select the X in the top left corner)
6. Observe the Launcher is not revealed.

[ Regression Potential ]

None observed.
+
+ Debdiff of the SRU is found here:
+
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

What Happened:
1) Turn on launcher auto hide
2) Display the HUD (tap Alt)
3) Move the mouse to the left side of the screen (as if you are showing the
launcher)
4) Note the launcher is not displayed
5) Now hide the HUD (either tap Alt or select the X in the top left corner)
6) Note that the launcher is now displayed, after the HUD closes.

What I expected to happen:
- I expected that the launcher is not displayed at step 6.

I expected for the launcher to not be displayed at step 6 because the
user could have the HUD displayed for a long period of time then decide
that they don't need the HUD. The launcher is then suddenly revealed to
them as they moved their cursor to the left side of the screen a few
minutes a ago. This could then confuse the user to why the launcher has
appeared when all they did was close the HUD.

Hope this can be fixed soon.

Andy

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview]
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
CompizPlugins:
[core,composite,opengl,decor,vpswitch,compiztoolbox,snap,resize,move,grid,imgpng,mousepoll,place,unitymtgrabhandles,wall,gnomecompat,session,regex,resizeinfo,animation,expo,fade,scale,ezoom,workarounds,unityshell]
CrashDB: unity
Date: Wed Jul 25 21:19:17 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
With autohide and the HUD enabled the launcher can appear at incorrect
times

Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Status in unity source package in Trusty:
In Progress

Bug description:
[ Impact ]

When the Launcher is suddenly revealed when it's not intended to can
cause confusion and a poor user experience.

[ Test Case ]

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

What I expected to happen:
- I expected that the launcher is not displayed at step 6.

I expected for the launcher to not be displayed at step 6 because the
user could have the HUD displayed for a long period of time then
decide that they don't need the HUD. The launcher is then suddenly
revealed to them as they moved their cursor to the left side of the
screen a few minutes a ago. This could then confuse the user to why
the launcher has appeared when all they did was close the HUD.

Hope this can be fixed soon.

Andy

[Touch-packages] [Bug 932486] Re: showing quicklist from launcher keynav mode focuses last application

** Description changed:

[ Impact ]

Poor user experience due to the app window not being focused as
expected.

[ Test Case ]

0. Have at least one application window open
1. Enter launcher keynav mode with Alt+F1
2. Select a launcher icon with the Up or Down keys.
3. Show the quicklist by pressing Right.
4. Collapse the quicklist by pressing Left.
5. Observe that the app window never has focus during the above steps.

[ Regression Potential ]

None observed.
+
+ Debdiff of the SRU is found here:
+
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

To reproduce:

0) Have at least one application window open
1) Enter launcher keynav mode with Alt+F1

* Note that when entering keynav mode, the application loses focus. THe
triangle to the right of it's launcher icon is no longer drawn, and the
window title is not displayed in the panel.

2) Select a launcher icon with the Up or Down keys.
3) Show the quicklist by pressing Right.

* Note that the application becomes active again - it's window title is
drawn to the panel, and the triangle to the right of the launcher icon
is drawn again.

4) Collapse the quicklist by pressing Left.

* The app loses focus again.

This seems like inconsistent behavior to me... either the app should
never lose focus when we enter keynav mode, or should not be activated
when we show a quicklist.

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

Title:
showing quicklist from launcher keynav mode focuses last application

Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Status in unity source package in Trusty:
In Progress

Bug description:
[ Impact ]

Poor user experience due to the app window not being focused as
expected.

[ Test Case ]

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

To reproduce:

0) Have at least one application window open
1) Enter launcher keynav mode with Alt+F1

* Note that when entering keynav mode, the application loses focus.
THe triangle to the right of it's launcher icon is no longer drawn,
and the window title is not displayed in the panel.

2) Select a launcher icon with the Up or Down keys.
3) Show the quicklist by pressing Right.

* Note that the application becomes active again - it's window title
is drawn to the panel, and the triangle to the right of the launcher
icon is drawn again.

4) Collapse the quicklist by pressing Left.

* The app loses focus again.

This seems like inconsistent behavior to me... either the app should
never lose focus when we enter keynav mode, or should not be activated
when we show a quicklist.

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

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

[Touch-packages] [Bug 926979] Re: compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool const) from unity::dash::DashView::AnalyseLensURI(std::string const) from unity::dash::DashView::

** Description changed:

  [ Impact ]
  
  Certain cases when clicking on Dash items may cause a crash.
  
  [ Test Case ]
  
  It's not entirely  clear how the crash is triggered, but no crash should
  be observed when clicking on Dash entries.
  
  [ Regression Potential ]
  
  The change is small and no regressions should be observed.
+ 
+ Debdiff of the SRU is found here:
+ 
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff
  
  -
  
  Original Description:
  
  Clicked dash, Internet applications.
  
  Opened a new bug as the others appear to suggest a fix is released for
  those bugs.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.0.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Sun Feb  5 14:51:39 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7eff5ff51d10 _ZN3nux8PropertyIbEaSERKb+32: mov
0x18(%rdi),%rdi
   PC (0x7eff5ff51d10) ok
   source 0x18(%rdi) (0x03f0) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   nux::Propertybool::operator=(bool const) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::AnalyseLensURI(std::string const) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::OnActivateRequest(_GVariant*) () from 
/usr/lib/compiz/libunityshell.so
   unity::UBusManager::OnCallback(_GVariant*, void*) () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=()
  UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo 
usrp video

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

Title:
  compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool
  const) from unity::dash::DashView::AnalyseLensURI(std::string const)
  from unity::dash::DashView::OnActivateRequest(_GVariant*)

Status in Unity:
  Fix Committed
Status in Unity 5.0 series:
  Triaged
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.0 series:
  Invalid
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [ Impact ]

  Certain cases when clicking on Dash items may cause a crash.

  [ Test Case ]

  It's not entirely  clear how the crash is triggered, but no crash
  should be observed when clicking on Dash entries.

  [ Regression Potential ]

  The change is small and no regressions should be observed.

  Debdiff of the SRU is found here:
  
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

  -

  Original Description:

  Clicked dash, Internet applications.

  Opened a new bug as the others appear to suggest a fix is released for
  those bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.0.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Sun Feb  5 14:51:39 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7eff5ff51d10 _ZN3nux8PropertyIbEaSERKb+32: mov
0x18(%rdi),%rdi
   PC (0x7eff5ff51d10) ok
   source 0x18(%rdi) (0x03f0) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   nux::Propertybool::operator=(bool const) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::AnalyseLensURI(std::string const) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::OnActivateRequest(_GVariant*) () from 
/usr/lib/compiz/libunityshell.so
   unity::UBusManager::OnCallback(_GVariant*, void*) () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=()
  UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo 
usrp video

To manage notifications about this bug go to:

[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes

2015-05-21 Thread Toni Leino

I'm sorry, trying to send attachment through this pages gives error
:ERR_ACCESS_DENIED after post comment. I tried to write to some text to
comment field and description.

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

Title:
  Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes

Status in Ubuntu One Infrastructure:
  New
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  After two last updates (I remember second one was also a kernel
  update) my Ubuntu has started sudden crashing, either desktop view
  freezes, sometimes sound which was played goes to fast circuit.
  Sometimes it crashes to full terminal screen, reporting kernel panic
  mode. I'm sorry I dont know how to find these crash reports from my
  Ubuntu, hope you can advice me. After crash, only thing possible is to
  reset my laptop manually.

  Ubuntu has also started to inform internal failure with powerd, and
  asks to report them to developers. I think I have send that report
  three times now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions

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

[Touch-packages] [Bug 1268097] Re: [System settings] Can't set user-supplied ring tone

2015-05-21 Thread Martin Wildam

Iam also on the bq aquaris and I tried downloading an mp3 ringtone with
uDropCabin hoping it offers me to open the file with an application that
can set it as ringtone. Usually when playing music on Android, i* etc
devices you have always an option to set current music as a ringtone.

I even tried via contacts to choose a ringtone but it seems there is
even no chance to set a separate ringtone for different people.

Essential features missing here in my opinion.

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

Title:
  [System settings] Can't set user-supplied ring tone

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Triaged
Status in content-hub package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  AFAICS I can't set a custom ring tone without using a writable image.
  (http://askubuntu.com/questions/372759/ringtones-in-ubuntu-touch)

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

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

[Touch-packages] [Bug 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash

** Description changed:

[ Impact ]

Users of the on-screen keyboard cannot properly use the Dash and the on-
screen keyboard at the same time.

[ Test Case ]

1. Install and start the on-screen keyboard Onboard.
2. Open the Dash.
3. Ensure you can interact with Onboard as you would expect.

[ Regression Potential ]

None observed.
+
+ Debdiff of the SRU is found here:
+
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

Hi,

Some recent update of broke the default on-screen Onboard to work
properly on dash.

In fact, Onboard is shown in dash, as if it was located under dash. It
is particularly visible, when the dash is maximized and covers the whole
screen. However, if I drag Onboard to position it under an icon in dash
and I click on the icon, the corresponding application is not started;
the click goes down to Onboard, which types the letter of the Onboard
key placed at the position of the click.

So, in a few words: dash draws Onboard as if it was covered by dash, but
Onboard behaves as if it is located over dash.

Having a vivid backup from about one month ago, we were able to
determine that the regression seem to have happened because of the
update of libunity-core and the related packages somewhere between one
month ago and today. In fact, the problem appeared in the test after
updating the following packages and versions to the version shipping
currently in the repositories.

libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1
libcairo-gobject2 1.13.0~20140204-0ubuntu1
libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1
libcairo2 1.13.0~20140204-0ubuntu1
libcairo2-dev 1.13.0~20140204-0ubuntu1
unity 7.3.1+15.04.20141128-0ubuntu1
unity-schemas 7.3.1+15.04.20141128-0ubuntu1
unity-services 7.3.1+15.04.20141128-0ubuntu1

Cheers

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

Title:
Regression: Default on-screen keyboard Onboard not properly above dash

Status in Unity:
Fix Released
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Status in unity source package in Trusty:
In Progress

Bug description:
[ Impact ]

Users of the on-screen keyboard cannot properly use the Dash and the
on-screen keyboard at the same time.

[ Test Case ]

1. Install and start the on-screen keyboard Onboard.
2. Open the Dash.
3. Ensure you can interact with Onboard as you would expect.

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

Hi,

Some recent update of broke the default on-screen Onboard to work
properly on dash.

In fact, Onboard is shown in dash, as if it was located under dash. It
is particularly visible, when the dash is maximized and covers the
whole screen. However, if I drag Onboard to position it under an icon
in dash and I click on the icon, the corresponding application is not
started; the click goes down to Onboard, which types the letter of the
Onboard key placed at the position of the click.

So, in a few words: dash draws Onboard as if it was covered by dash,
but Onboard behaves as if it is located over dash.

Cheers

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

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

[Touch-packages] [Bug 886478] Re: New Alt + tab switcher doesn't follow system font

Attached is the debdiff for the SRU.

** Patch added: unity.7.2.5.debdiff

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

** Description changed:

[ Impact ]

Users who switch the system font and then use Alt+Tab will see a jarring
effect when the Ubuntu font is displayed. This can also lead to not
fully supported language issues.

[ Test Case ]

1. Switch the system font to something else besides Ubuntu.
2. Use Alt+Tab.
3. Observe any fonts displayed in Alt+Tab follow the system font.

[ Regression Potential ]

None observed.
+
+ Debdiff of the SRU is found here:
+
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

In my laptop, I have to change from default ubuntu font to droid font
because the default one doesn't fully support vietnamese. Let it sit
there will make the overall system feel awkward. And now, while the
whole system is in droid, only the switcher is still using the ubuntu
font. Plz make the switcher follow the system font or at least, make a
way to configure its appearance.

--
Desired solution:

- Alt+tab switcher should use the system font
- This change should result in ZERO change to the appearance of the font in
Alt+Tab on a fresh installation of Ubuntu.

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

Title:
New Alt + tab switcher doesn't follow system font

Status in Ayatana Design:
Fix Committed
Status in Unity:
Fix Released
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Status in unity source package in Trusty:
In Progress

Bug description:
[ Impact ]

Users who switch the system font and then use Alt+Tab will see a
jarring effect when the Ubuntu font is displayed. This can also lead
to not fully supported language issues.

[ Test Case ]

1. Switch the system font to something else besides Ubuntu.
2. Use Alt+Tab.
3. Observe any fonts displayed in Alt+Tab follow the system font.

[ Regression Potential ]

None observed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

Original Description:

--
Desired solution:

- Alt+tab switcher should use the system font
- This change should result in ZERO change to the appearance of the font in
Alt+Tab on a fresh installation of Ubuntu.

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

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

[Touch-packages] [Bug 1322265] Re: No success/failure feedback when doing ratings/reviews

Would appreciate input from deisgn here in what we need to do.

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  No success/failure feedback when doing ratings/reviews

Status in Ubuntu UX bugs:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  When entering text into review field the status of the send button
  does not change meaning it does not indicate it would be enabled.
  However, tabbing the button is possible. When doing so, review text
  disappears as expected but there is no feedback whether it was
  successfully send to server or not. In fact, it seems it wasn't as the
  review doesn't show up when relaunching the preview.

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

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

[Touch-packages] [Bug 1448259] Re: Systemd does not send SIGTERM first on shutdown

2015-05-21 Thread Bug Watch Updater

** Changed in: systemd (Debian)
   Status: Fix Committed = Fix Released

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

Title:
  Systemd does not send SIGTERM first on shutdown

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Vivid:
  Fix Released
Status in systemd package in Debian:
  Fix Released
Status in systemd package in Fedora:
  Unknown

Bug description:
  It has been normal that applications first get the SIGTERM signal
  before SIGKILL on shutdown/reboot in order to successfully finish any
  pending tasks. Now it seem this logic has been changed to something
  else, causing problems to mosh and many others:

  https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982

  SIGTERM  suggestion can be seen here:

  http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8

  I created this error report to find out the correct way for
  applications to fix this problem or to create one fix to systemd,
  bringing back the old BSD shutdown functionality.

  This report is for Ubuntu 15.04.

  SRU TEST CASE:
   - Open a terminal, enter some commands, then run reboot.
   - After a reboot, chances are very high that your bash history does not 
contain your most recently typed commands
   - With the updated package, the bash history should be intact.

  REGRESSION POTENTIAL:
   - The original commit was applied because of an inherent race condition with 
cgroup's release_agent -- in rare corner cases an nspawn container (probably 
also LXC) can miss them. In that case it's possible that you instead get a 90s 
timeout on the unit that is shutting down. But this does not mean data loss, 
just a rare shutdown hang from containers (for the record, I never actually saw 
that hanging with LXC), so I think it's a good trade-off.

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

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

[Touch-packages] [Bug 1436095] Re: AP test failure: unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click

** Description changed:

  [ Impact ]
  
  Failed Autopilot tests are not good.
  
  [ Test Case ]
  
  1. Run 'autopilot run 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click'
  2. Run 'autopilot run 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click'
  3. Observe that the tests don't fail.
  
  [ Regression Potential ]
  
  None observed.
+ 
+ Debdiff of the SRU is found here:
+ 
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff
  
  -
  
  Original Description:
  
  The following two AP tests consistently ERROR during regular Unity
  testing.
  
  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
  --
  Empty attachments:
    /var/log/syslog
  
  unity-log: {{{WARN  2015-03-24 13:43:02 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
  
  Traceback (most recent call last):
    File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line 
128, in test_scaled_window_closes_on_middle_click
  self.assertWindowIsScaledEquals(target_xid, False)
    File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
    File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
    File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
    File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py, 
line 113, in match
  wait_fun(self.matcher, self.timeout)
    File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py, 
line 129, in _callable_wait_for
  new_value = refresh_fn()
    File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line 
67, in lambda
  refresh_fn = lambda: xid in [w.xid for w in 
self.unity.screen.scaled_windows]
    File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py, 
line 520, in __getattr__
  self.refresh_state()
    File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py, 
line 474, in refresh_state
  _, new_state = self.get_new_state()
    File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py, 
line 564, in get_new_state
  raise StateNotFoundError(self.__class__.__name__, id=self.id)
  StateNotFoundError: Object not found with name 'Window' and properties {'id': 
148832}.
  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
  --
  Empty attachments:
    /var/log/syslog
  
  unity-log: {{{WARN  2015-03-24 14:00:34 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
  
  Traceback (most recent call last):
    File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line 
148, in test_scaled_window_closes_on_close_button_click
  self.assertWindowIsScaledEquals(target_xid, False)
    File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
    File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
    File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
    File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py, 
line 113, in match
  wait_fun(self.matcher, self.timeout)
    File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py, 
line 129, in _callable_wait_for
  new_value = refresh_fn()
    File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line 
67, in lambda
  refresh_fn = lambda: xid in [w.xid for w in 
self.unity.screen.scaled_windows]
    File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py, 
line 520, in __getattr__
  self.refresh_state()
    File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py, 
line 474, in refresh_state
  _, new_state = self.get_new_state()
    File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py, 
line 564, in get_new_state
  raise StateNotFoundError(self.__class__.__name__, id=self.id)
  StateNotFoundError: Object not found with name 'Window' and properties {'id': 
224517}.
  ==

[Touch-packages] [Bug 1308265] Re: First password letter not registered in lockscreen if screen off

** Description changed:

  [ Impact ]
  
  Not having the first character registered when trying to unlock the
  lockscreen can most definitely lead to frustration and thus, poor user
  experience.
  
  [ Test Case ]
  
  1. Lock the screen and let the monitor blank as well.
  2. Try unlocking the screen by typing your password.
  3. Observe lockscreen unlocks.
  
  [ Regression Potential ]
  
  None observed.
+ 
+ Debdiff of the SRU is found here:
+ 
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff
  
  -
  
  Original Description:
  
  With the new lockscreen, if my screen is off, I just start typing, every
  time my password is too short. It looks like the first key only triggers
  the screen on and does not go to the input field.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  First password letter not registered in lockscreen if screen off

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [ Impact ]

  Not having the first character registered when trying to unlock the
  lockscreen can most definitely lead to frustration and thus, poor user
  experience.

  [ Test Case ]

  1. Lock the screen and let the monitor blank as well.
  2. Try unlocking the screen by typing your password.
  3. Observe lockscreen unlocks.

  [ Regression Potential ]

  None observed.

  Debdiff of the SRU is found here:
  
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

  -

  Original Description:

  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1246891] Re: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher

** Description changed:

  [ Impact ]
  
  Users the use Launcher keynav mode may end up with a Launcher that is
  not displayed correctly, leaving a poor user experience.
  
  [ Test Case ]
  
  1. Make sure there are enough icons in the Launcher to cause the Launcher to 
fold.
  2. Press Alt+F1
  3. Press right-key
  4. Press left-key
  5. Observe the Launcher is not folder while still in keynav mode.
  
  [ Regression Potential ]
  
  None observed.
  
+ Debdiff of the SRU is found here:
+ 
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff
+ 
  -
  
  Original Description:
- 
  
  1) Press Alt+F1
  2) Press right-key
  3) Press left-key
  
  Expected result:
  3) The launcher goes back to keynav mode and unfolds completely.

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

Title:
  Going back from quicklist to launcher in key-nav mode doesn't unfold
  the launcher

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [ Impact ]

  Users the use Launcher keynav mode may end up with a Launcher that is
  not displayed correctly, leaving a poor user experience.

  [ Test Case ]

  1. Make sure there are enough icons in the Launcher to cause the Launcher to 
fold.
  2. Press Alt+F1
  3. Press right-key
  4. Press left-key
  5. Observe the Launcher is not folder while still in keynav mode.

  [ Regression Potential ]

  None observed.

  Debdiff of the SRU is found here:
  
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

  -

  Original Description:

  1) Press Alt+F1
  2) Press right-key
  3) Press left-key

  Expected result:
  3) The launcher goes back to keynav mode and unfolds completely.

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

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

[Touch-packages] [Bug 1313597] Re: Shortcut overlay cannot be closed by clicking the close button in 14.04

** Description changed:

[ Impact ]

Due to an input handling race, the first time users log into Unity on
their system, the shortcut overlay may not close when clicking the X
in the corner. This leads to a poor user experience.

[ Test Case ]

1. Remove ~/.config/unity/first_run.stamp.
2. Log into Unity.
3. Shortcut hints overlay should be shown.
4. Click on X in the corner.

[ Regression Potential ]

This is a workaround for a race, so some users may never see the race to
begin with. That said, no regression should be observed as in worse
case, the shortcut hints still cannot be closed.

+ Debdiff of the SRU is found here:
+
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff
+
---

Original Description:

In 14.04, the shortcut overlay would pop-out automatically on first boot.
Although there is a close button on the top-left corner, it cannot be closed
by clicking it.

(it could be dismissed by the super key, or open a new window)

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

Title:
Shortcut overlay cannot be closed by clicking the close button in
14.04

Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Status in unity source package in Trusty:
In Progress

Bug description:
[ Impact ]

Due to an input handling race, the first time users log into Unity on
their system, the shortcut overlay may not close when clicking the X
in the corner. This leads to a poor user experience.

[ Test Case ]

1. Remove ~/.config/unity/first_run.stamp.
2. Log into Unity.
3. Shortcut hints overlay should be shown.
4. Click on X in the corner.

[ Regression Potential ]

This is a workaround for a race, so some users may never see the race
to begin with. That said, no regression should be observed as in
worse case, the shortcut hints still cannot be closed.

Debdiff of the SRU is found here:

https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff

---

Original Description:

In 14.04, the shortcut overlay would pop-out automatically on first boot.
Although there is a close button on the top-left corner, it cannot be closed
by clicking it.

(it could be dismissed by the super key, or open a new window)

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

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

[Touch-packages] [Bug 1368688] Re: Inconsistence between /etc/init and /etc/init.d files

2015-05-21 Thread John Center

This just bit us, also.  We migrated from Solaris to Ubuntu 14.04 for
our dhcp server.  Please fix!

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

Title:
  Inconsistence between /etc/init and /etc/init.d files

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with 
do-release-upgrade) I found a strange behavior in /var/log/messages from 
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
  ~~
  dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
  dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
  DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
  DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
  DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
  DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
  ~~

  Futher investigation show that there was actually two dhcpd processes:
  ~~
  dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
  /usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
  ~~

  The first one was executed from /etc/init/isc-dhcp-server.conf and second 
from /etc/init.d/isc-dhcp-server.
  Looking inside init/isc-dhcp-server.conf I found:
  ~~
  respawn
  script
     . /etc/default/isc-dhcp-server
    ..
   exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES
  ~~

  As you can see path to PID file is hardcoded.

  But in init.d/isc-dhcp-server startup script:
  ~~
  # try to read pid file name from config file, with fallback to 
/var/run/dhcpd.pid
  if [ -z $DHCPD_PID ]; then
  DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*(.*)[ 
\t]*;.*$/\1/p'  $DHCPD_CONF 2/dev/null | head -n 1)
  fi
  DHCPD_PID=${DHCPD_PID:-/var/run/dhcpd.pid}
    ..
  case $1 in
  start)
  test_config
  log_daemon_msg Starting $DESC $NAME
  start-stop-daemon --start --quiet --pidfile $DHCPD_PID \
  --exec /usr/sbin/dhcpd -- \
  -q $OPTIONS -cf $DHCPD_CONF -pf $DHCPD_PID 
$INTERFACES
  ~~

  
  So obivous is to either change init script to NOT use hardcoded path to PID 
file and use $DHCP_PID (from /etc/default/isc-dhcp-server, which is sourced 
inside this script), or at least change it to default one: /var/run/dhcpd.pid

  OR

  change init.d script to fallback to /run/dhcp-server/dhcpd.pid
  instead of /var/run/dhcpd.pid

  P.S. /var/run is a link to /run

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

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

[Touch-packages] [Bug 1276334] Re: Indicators are killed when unity8 stops under unity7 desktop

Does this still happen? I can't reproduce it anymore

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Incomplete

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

Title:
  Indicators are killed when unity8 stops under unity7 desktop

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  When running unity8 from the desktop and quitting it again, all
  indicators will be killed. I have to manually start them for them to
  show up in unity7 again.

  Not a huge problem, but would be nice if this could be fixed. Thanks!

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

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

[Touch-packages] [Bug 932486] Re: showing quicklist from launcher keynav mode focuses last application

** Description changed:

  [ Impact ]
  
  Poor user experience due to the app window not being focused as
  expected.
  
  [ Test Case ]
  
  0. Have at least one application window open
  1. Enter launcher keynav mode with Alt+F1
  2. Select a launcher icon with the Up or Down keys.
  3. Show the quicklist by pressing Right.
  4. Collapse the quicklist by pressing Left.
- 5. Observe that the app window has focus.
+ 5. Observe that the app window never has focus during the above steps.
  
  [ Regression Potential ]
  
  None observed.
  
  
  
  Original Description:
  
  To reproduce:
  
  0) Have at least one application window open
  1) Enter launcher keynav mode with Alt+F1
  
   * Note that when entering keynav mode, the application loses focus. THe
  triangle to the right of it's launcher icon is no longer drawn, and the
  window title is not displayed in the panel.
  
  2) Select a launcher icon with the Up or Down keys.
  3) Show the quicklist by pressing Right.
  
   * Note that the application becomes active again - it's window title is
  drawn to the panel, and the triangle to the right of the launcher icon
  is drawn again.
  
  4) Collapse the quicklist by pressing Left.
  
   * The app loses focus again.
  
  This seems like inconsistent behavior to me... either the app should
  never lose focus when we enter keynav mode, or should not be activated
  when we show a quicklist.

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

Title:
  showing quicklist from launcher keynav mode focuses last application

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [ Impact ]

  Poor user experience due to the app window not being focused as
  expected.

  [ Test Case ]

  0. Have at least one application window open
  1. Enter launcher keynav mode with Alt+F1
  2. Select a launcher icon with the Up or Down keys.
  3. Show the quicklist by pressing Right.
  4. Collapse the quicklist by pressing Left.
  5. Observe that the app window never has focus during the above steps.

  [ Regression Potential ]

  None observed.

  

  Original Description:

  To reproduce:

  0) Have at least one application window open
  1) Enter launcher keynav mode with Alt+F1

   * Note that when entering keynav mode, the application loses focus.
  THe triangle to the right of it's launcher icon is no longer drawn,
  and the window title is not displayed in the panel.

  2) Select a launcher icon with the Up or Down keys.
  3) Show the quicklist by pressing Right.

   * Note that the application becomes active again - it's window title
  is drawn to the panel, and the triangle to the right of the launcher
  icon is drawn again.

  4) Collapse the quicklist by pressing Left.

   * The app loses focus again.

  This seems like inconsistent behavior to me... either the app should
  never lose focus when we enter keynav mode, or should not be activated
  when we show a quicklist.

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

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

[Touch-packages] [Bug 1449394] Re: Crash 854d2ed5e61bf3647f46bb17bb41958c97c4f58d

2015-05-21 Thread Bryan Quigley

Customer Confirmed fixed in both 12.04 and 14.04.

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

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

Title:
  Crash 854d2ed5e61bf3647f46bb17bb41958c97c4f58d

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Committed
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]The apt version 1.0.1ubuntu2.7 from trusty-proposed has a
  regression for some users:

  
   ConfigValueInSubTree → pkgDepCache → → MarkInstall → pkgDepCache → → 
MarkInstall → pkgDepCache → → MarkInstall → doAutoInstall:

  #0  __strcmp_ssse3 () at ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:241
  No locals.
  #1  0xb7656e25 in ConfigValueInSubTree (SubTree=SubTree@entry=0xb771edc3 
APT::Never-MarkAuto-Sections, needle=0x0) at depcache.cc:59
  Opts = 0x99bec98
  #2  0xb765d3d6 in pkgDepCache::MarkInstall (this=0x99c1738, Pkg=..., 
AutoInst=AutoInst@entry=true, Depth=2, FromUser=FromUser@entry=false, 
ForceImportantDeps=false) at depcache.cc:1228
  

  Errors Bucket
  -
  https://errors.ubuntu.com/problem/854d2ed5e61bf3647f46bb17bb41958c97c4f58d

  [Test Case]
  Install deb package that has no section in instVersion, see if program 
crashes.

  [Regression Potential]
  Adds an additional check to if statement to ensure InstVer-Section != 0.

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

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

[Touch-packages] [Bug 1456281] Re: Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en

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

** Changed in: indicator-datetime (Ubuntu Vivid)
   Status: New = Confirmed

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

Title:
  Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime source package in Vivid:
  Confirmed

Bug description:
  This ticket is to track a missing alarm issue that seems to have
  started showing up between May 15 and 18th.

  in #unity-api, mzanetti reports that alarms on a ubuntu-touch/rc-
  proposed/bq-aquaris.en are not showing up at the right time; rather,
  they're skewed by timezone. He's in UTC+2 and set a 6:30 alarm that
  didn't go off until 8:30.

  Alesage in Orlando is also reporting missing alarms when he tests on
  arale.

  When I test on a fresh flash of ubuntu-touch/rc-proposed/bq-aquaris.en
  (r9) I'm seeing the same behavior rerported by mzanetti. What's really
  odd though is when I apt-get source that version of indicator-datetime
  and run it myself, things work correctly.

  Alarms also working correctly on mako 15.10 r199.

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

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

[Touch-packages] [Bug 1398945] Re: Alarms are not set on manta devices

2015-05-21 Thread Charles Kerr

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

** This bug has been marked a duplicate of bug 1456281
   Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en

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

Title:
  Alarms are not set on manta devices

Status in qtorganizer5-eds package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Open the clock app
  2. Allow location service
  3. Swipe up from the bottom of the screen
  4. tap on the plus
  5. set an alarm for a few minutes time

  EXPECTED:
  I expect to see the alarm notification move to the datetime-indicator and the 
alarm to go off

  ACTUAL:
  No icon appears in the indicator and no alarms go off.

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

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

[Touch-packages] [Bug 1452239] Re: root escalation with fs.suid_dumpable=2

2015-05-21 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  root escalation with fs.suid_dumpable=2

Status in Apport crash detection/reporting:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Utopic:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Committed

Bug description:
  Sander Bos discovered that Apport enabled a user to perform a root
  escalation since it now configures fs.suid_dumpable=2.

  Here's a brief description of the issue:
  1- A regular user can trigger a coredump with /proc/$PID/stat as root:root 
simply by doing chmod u-r
  2- The root-owned coredump will them be written in the CWD, which in the PoC 
is /etc/logrotate.d
  3- logrotate will gladly skip parts of the coredump it doesn't understand and 
will successfully run the parts it does

  I've set a CRD of 2015-05-21 (original proposal: 2015-05-12) for the
  publication of this issue.

  I have assigned CVE-2015-1324 to this issue.

  We can either:

  1- Disable fs.suid_dumpable=2
  2- Stop creating core dump files when they are to be created as root
  3- Create root-owned core dump files in a well-known location

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

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

[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes

2015-05-21 Thread Toni Leino

I think you have seen my screenshot already. I'm trying to send the
files tomorrow.

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

Title:
  Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes

Status in Ubuntu One Infrastructure:
  New
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  After two last updates (I remember second one was also a kernel
  update) my Ubuntu has started sudden crashing, either desktop view
  freezes, sometimes sound which was played goes to fast circuit.
  Sometimes it crashes to full terminal screen, reporting kernel panic
  mode. I'm sorry I dont know how to find these crash reports from my
  Ubuntu, hope you can advice me. After crash, only thing possible is to
  reset my laptop manually.

  Ubuntu has also started to inform internal failure with powerd, and
  asks to report them to developers. I think I have send that report
  three times now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions

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

[Touch-packages] [Bug 1258588] Re: unity8.upstart uses bashism

It works fine in dash, bash and zsh

Do you know of any shell that doesn't support this syntax?

Which shell does upstart decide to use?

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Incomplete

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

Title:
  unity8.upstart uses bashism

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  unity8 upstart job appears to be using bashism [1]

  https://wiki.ubuntu.com/DashAsBinSh#A.24.7B7D

  Please review and fix appropriately.

  Offending line:
  30: exec ${BINARY:-unity8} $ARGS

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

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

[Touch-packages] [Bug 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable

2015-05-21 Thread Natalia Bidart

From IRC:

16:20  nessita jsalisbury, just wanted to sync about the bisect we're
doing for LP: #1201528, since I'm now in 3.8.13.1 and audio died with
the underrun error. So I re-read all the comments and noticed that in
commnet #39
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/comments/39)
I reproduced the issue with kernel 3.8.0-27-generic

16:21  nessita I'm now installing latest 3.7 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ which is 3.7.10 and see
if audio breaks, will report in the bug

So, in summary:

Kernel 3.8.13.1 - AUDIO BREAKS

Kernel 3.7.10 - audio does not break

Will try other versions of 3.8.

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

Title:
  [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in alsa-driver source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This is a fresh upgrade to raring. During the weekend, I updated from
  precise to quantal, and from there to raring. I did not use sound
  while the system was in quantal, so no idea if the bug was present
  there as well.

  The symptom is:

  * after some period of sound usage, playback stops working

  What I mean with sound usage is:

  I tried having a meeting with: mumble, skype, and google hangout, and
  in all three cases, audio input/outout will work just fine for ~5
  minutes, and the playback just dies (people tell me they keep
  listening to me, so mic works fine).

  The only way to solve this is by rebooting. After one of the reboots,
  I was able to play a 20 minute video with mplayer with no further
  issue. Then opened skype and after ~3-5 minute talk, audio playback
  died again.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nessita2627 F pulseaudio
  Date: Mon Jul 15 14:40:20 2013
  InstallationDate: Installed on 2011-12-20 (572 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   O p e r a t i o n   n o t   p e r m i t t 
e d
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: None of the above
  Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem
  UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago)
  dmi.bios.date: 08/05/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WG
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE57269-404
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr:
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nessita   13188 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b
  InstallationDate: Installed on 2014-05-11 (366 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid vivid vivid vivid
  Uname: Linux 3.19.0-16-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855
  dmi.board.asset.tag: Base

[Touch-packages] [Bug 1284704] Re: Tabbar in Dash: tapping empty part causes weird tab switch

There's no tabbar in the header anymore

** Changed in: unity8 (Ubuntu)
   Status: Triaged = 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/1284704

Title:
  Tabbar in Dash: tapping empty part causes weird tab switch

Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Need tablet or desktop to test this. I have 4 lenses installed: Home,
  Music, Applications, Videos.

  In the header, tap the Home to show the list of all tab names - this
  list should not overflow to reproduce the bug. Now tap about 2 cm to
  the right of the  arrow, where there is nothing to tap on. For me,
  when I do that, I get a haptic feedback, and the Home text animates
  around weirdly.

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

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

[Touch-packages] [Bug 1457398] Re: systemd immediately unmounts manually mounted directories