date:20151112

Hello Bin, or anyone else affected,

Accepted modemmanager into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.0.0-2ubuntu1.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]
   
   * None

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

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

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

  Could we backport this patch  into trusty? Thanks!

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

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

[Touch-packages] [Bug 1515784] [NEW] UHD resolution not found when logging in, can select after login

2015-11-12 Thread Johan Van de Wauw

Public bug reported:

Hi,

After updating from vivid to wily I noticed my screen no longer boots in
UHD resolution. I can set the resolution during the session, but on next
login it returns back to full hd. This is a regression from vivid, where
the resolution worked without problem.

This happens with different window managers.

In cinnamon I get an additional error, which is solved by removing
.config/monitors.xml

none of the selected modes were compatible with the possible modes:
Trying modes for CRTC 63
CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 64
CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 65
CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 66
CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

I'm willing to invest some time in trying to find a solution.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: X-Cinnamon
Date: Thu Nov 12 22:42:35 2015
DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
InstallationDate: Installed on 2011-09-07 (1527 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
MachineType: MSI MS-7846
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
dmi.bios.date: 09/24/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V18.1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-E35 (MS-7846)
dmi.board.vendor: MSI
dmi.board.version: 3.0
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.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7846
dmi.product.version: 3.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Nov 12 22:41:25 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputLogitech USB Receiver KEYBOARD, id 10
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug resolution ubuntu wily

** Description changed:

  Hi,
  
  After updating from vivid to wily I noticed my screen no longer boots in
- UHD resolution. I can set the resolution during the setting, but on next
+ UHD resolution. I can set the resolution during the session, but on next
  login it returns back to full hd. This is a regression from vivid, where
  the resolution worked without problem.
  
  This happens with

[Touch-packages] [Bug 1506753] Re: keyboard does pop up not after update to r26

We opened bug #1515712 but it is probably the same root cause. If so,
there is a race at startup that causes the backend server to lock up so
the focus events don't get seen. In that case though a reboot should fix
it, although it may take more than one per comment #3 as it is just by
chance when it does or doesn't enter this state.

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

Title:
  keyboard does pop up not after update to r26

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

Bug description:
  Ubuntu bq 4.5. Checked with browser, dekko, calendar and system
  settings (changing the pin). Turned the phone off and on.  No change.

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

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

[Touch-packages] [Bug 1515712] Re: maliit-server becomes deadlocked

Adding qt as qdbus seems suepect
see bug #1421009 and perhaps https://bugreports.qt.io/browse/QTBUG-48410 and 
https://bugreports.qt.io/browse/QTBUG-44836

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

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

Title:
  maliit-server becomes deadlocked

Status in Canonical System Image:
  Confirmed
Status in maliit-framework package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  on krillin, rc-proposed 175

  I'm experiencing keyboard not popping up on any application. Can't
  remember if this was after a reboot or if it was working for a while
  and then stopped. I believe it's after a reboot.

  Upon inspection, it appears maliit-server process is deadlocked (see
  thread dump below). Also, there is no log in .cache/upstart/maliit-
  server.log only old logs maliit-server.log.1.gz etc, which leads me to
  believe this problem happens after reboot.

  Seems that some QNetwork initialization is happening and this is
  causing an issue (see Threads 3, 2, and 1). We should figure out why
  we are even doing any network stuff at all, as we probably shouldn't
  be.

  (gdb) t a a bt

  Thread 14 (Thread 0xb2cc2440 (LWP 2844)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb3d03cdc in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #2  0xb3d04c96 in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #3  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #5  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 13 (Thread 0xb2197440 (LWP 3128)):
  #0  0xb435a840 in ?? ()
  #1  0xb436e29c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 12 (Thread 0xb240fb40 (LWP 3129)):
  #0  0xb5c61836 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  #1  0xb5c618a4 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 11 (Thread 0xb1976440 (LWP 3130)):
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 10 (Thread 0xb1176440 (LWP 3131)):
  ---Type  to continue, or q  to quit---
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 9 (Thread 0xb0697440 (LWP 3143)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 8 (Thread 0xafcff440 (LWP 3144)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 7 (Thread 0xaeaff440 (LWP 3146)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 6 (Thread 0xae1ff440 (LWP 3148)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 5 (Thread 0xacb49440 (LWP 3167)):
  #0  0xb66e1132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  ---Type  to continue, or q  to quit---
  #1  0xb3b62312 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #2  0xb3b642ea in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #3  0xb3b6484a in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #4  0xb3b4d678 in core::dbus::Bus::run() () from 
/usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #5  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #7  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 4 (Thread 0xac349440 (LWP 3169)):
  #0  0xb66da4e2 in poll ()

[Touch-packages] [Bug 1400856] Re: GLib-GObject-CRITICAL

2015-11-12 Thread Toan

I compile glib library from source and I learn that if optimization (-Os -O1 or 
-O2) was turned on during compilation, particularly when compiling 
gobject/gobject.c from glib, can lead to many strange behaviors and errors.


If for somehow, you can try to recompile glib without optimation and see if the 
error goes away.  thanks

TP

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

Title:
  GLib-GObject-CRITICAL

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  screen blinks or something like that and i get error

  (anjuta:30976): GLib-GObject-CRITICAL **: g_object_ref: assertion
  'object->ref_count > 0' failed

  (anjuta:30976): GLib-GObject-CRITICAL **: g_object_unref: assertion
  'object->ref_count > 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-0 2.40.2-0ubuntu1
  Uname: Linux 3.18.0-031800-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Dec  9 21:08:48 2014
  InstallationDate: Installed on 2014-12-01 (8 days ago)
  InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1400856/+subscriptions

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

[Touch-packages] [Bug 1514016] Re: travamentos

2015-11-12 Thread Tyler Hicks

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1514016/+attachment/4514553/+files/JournalErrors.txt

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

Title:
  travamentos

Status in xorg package in Ubuntu:
  New

Bug description:
  meu desktope trava muinto e deixa jogos lentos

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov  6 23:03:53 2015
  DistUpgraded: 2015-11-06 22:19:41,686 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2033]
  InstallationDate: Installed on 2015-11-06 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  MachineType: Positivo Informatica SA H14CU01
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro priority=low locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-11-07 (0 days ago)
  dmi.bios.date: 12/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02.U
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H14CU01
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: SIM
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Informatica SA
  dmi.chassis.version: SIM
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02.U:bd12/03/2013:svnPositivoInformaticaSA:pnH14CU01:pvr1.02.U_SIM:rvnPositivoInformaticaSA:rnH14CU01:rvrSIM:cvnPositivoInformaticaSA:ct10:cvrSIM:
  dmi.product.name: H14CU01
  dmi.product.version: 1.02.U_SIM
  dmi.sys.vendor: Positivo Informatica SA
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov  6 22:21:12 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 901 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1515677] Re: default sim not selected when opening message from indicator

2015-11-12 Thread Bill Filler

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

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

** Changed in: canonical-devices-system-image
   Status: Confirmed => 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/1515677

Title:
  default sim not selected when opening message from indicator

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

Bug description:
  on latest rc-proposed r175 on krillin

  Make sure messaging app is closed and you have a default sim to send
  messages on in settings

  1) send message to phone
  2) open the message by clicking on the notification or opening from the 
messaging menu
  3) messaging app launched and the message thread is displayed

  expected results:
  SIM selector in header should be selected with default sim choosen in settings

  actual result:
  No selection in SIM selector

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

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

[Touch-packages] [Bug 1505241] Re: Phone does not suspend

@Julia yes there could be a bug still on BQ

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

Title:
  Phone does not suspend

Status in Canonical System Image:
  Invalid
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar 
behavior
  According to the logs they are not able to suspend due to active wakeup 
sources.
  (I am running a BT test kernel on the MX4 3.10.35+)

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

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

[Touch-packages] [Bug 1498751] Re: Please sync libxml2 2.9.2+zdfsg1-4 (main) from Debian unstable

2015-11-12 Thread Marc Deslauriers

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

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

Title:
  Please sync libxml2 2.9.2+zdfsg1-4 (main) from Debian unstable

Status in libxml2 package in Ubuntu:
  Fix Released

Bug description:
  Please sync libxml2 2.9.2+zdfsg1-4 (main) from Debian unstable, it is
  an updated version from maintainer that has includes fixes for
  problems addressed in Ubuntu delta, with more bug fixes from the same
  upstream release version.

   libxml2 (2.9.2+zdfsg1-4) unstable; urgency=medium
   .
 * Revert everything in N'ACKed NMU revert to 2.9.1.
   - Resolving regression, Closes: #754424
   - Drop the following NMU, not needed in 2.9.2, Closes: #781232
   - Drop not approved patch for GNOME #746048
 * Revert icu dbg drop, but don't hardcode version,
   thanks Matthias Klose , Closes: #798642
 * Cherry pick upstream post release patches:
   - Fix for regression triggered by CVE-2014-3660, Closes: #768089
   - Fix for the spurious ID already defined error, Closes: #766884
   - Fix for CVE-2015-1819, Closes: #782782
   - Fix for GNOME #744980, Closes: #783010
   - Several fixes for memory related issues.

  -- Aron Xu  Tue, 22 Sep 2015 16:31:48 +0800

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

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

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

Remaining apps will get out over the next couple weeks

** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => ww02-2016

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

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  Fix Committed
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  In Progress
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  Fix Committed
Status in Ubuntu Weather App:
  In Progress
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in gallery-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Committed
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
 Ubuntu.Components 1.3
 Ubuntu.Components.ListItems 1.3
 Ubuntu.Components.Pickers 1.3
 Ubuntu.Components.Popups 1.3
 Ubuntu.Components.Styles 1.3
 Ubuntu.Components.Themes 1.3
 Ubuntu.Components.Themes.Ambiance 1.3
 Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
 Ubuntu.Layouts 1.0
 Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

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

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

[Touch-packages] [Bug 1510221] Re: Reordering of tracks is disabled until we have moveSource(from, to)

** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => ww02-2016

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

Title:
  Reordering of tracks is disabled until we have moveSource(from, to)

Status in Canonical System Image:
  In Progress
Status in media-hub package in Ubuntu:
  Fix Committed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Committed
Status in qtubuntu-media package in Ubuntu:
  Fix Committed
Status in media-hub package in Ubuntu RTM:
  Fix Committed
Status in qtmultimedia-opensource-src package in Ubuntu RTM:
  Fix Committed
Status in qtubuntu-media package in Ubuntu RTM:
  Fix Committed

Bug description:
  Reordering of tracks is disabled until we have moveSource(from, to)

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

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

[Touch-packages] [Bug 1515734] Re: header not resizing properly after showing Recents view

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

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

Title:
  header not resizing properly after showing Recents view

Status in dialer-app package in Ubuntu:
  New

Bug description:
  rc-proposed on krillin build 175

  The header is too big after you first view the Recents page, it does
  not properly resize to it's initial height.

  Steps to reproduce:
  1) Launch dialer
  2) Verify header does not contain extra white space lines
  3) pull up recents page from bottom edge
  4) make a phone call or go back to main view

  Expected results:
  header should resize to initial size without extra white space

  Actual results:
  header stays same size as it was in Recents page with extra white space (see 
attachments)

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

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

[Touch-packages] [Bug 1515734] Re: header not resizing properly after showing Recents view

2015-11-12 Thread Gustavo Pichorim Boiko

** Changed in: dialer-app (Ubuntu)
 Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko)

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  header not resizing properly after showing Recents view

Status in dialer-app package in Ubuntu:
  New

Bug description:
  rc-proposed on krillin build 175

  The header is too big after you first view the Recents page, it does
  not properly resize to it's initial height.

  Steps to reproduce:
  1) Launch dialer
  2) Verify header does not contain extra white space lines
  3) pull up recents page from bottom edge
  4) make a phone call or go back to main view

  Expected results:
  header should resize to initial size without extra white space

  Actual results:
  header stays same size as it was in Recents page with extra white space (see 
attachments)

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

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

[Touch-packages] [Bug 1511029] Re: Audio gets confused when playing from source after playing from playlist

** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => ww02-2016

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

Title:
  Audio gets confused when playing from source after playing from
  playlist

Status in Canonical System Image:
  In Progress
Status in media-hub package in Ubuntu:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  In Progress
Status in media-hub package in Ubuntu RTM:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  Can be reproduced with the code from http://paste.ubuntu.com/13008980/

  How to reproduce:
   1. Press the red area
   2. Listen to song1.mp3 play
   3. Press the blue area
   4. Notice how song 1 is playing instead of song 2

  Note this only happens on the phone, on the desktop all is good.

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

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

[Touch-packages] [Bug 1514183] Re: distutils : file "bdist_rpm.py" allows Shell injection in "name"

2015-11-12 Thread Tyler Hicks

Hi Bernd - Thanks for the bug report! While I think that this is
something that should be fixed upstream, I don't feel like it is a
security issue.

By running `python setup.py ...`, you're already trusting that setup.py
is not malicious. It could execute xmessage directly.

Do you know if there are any other ways to trigger the problematic
popen() call that doesn't require executing the Python script that has
the malicious program name?

Have you reported this issue to upstream Python?

** Changed in: python2.7 (Ubuntu)
   Status: New => Incomplete

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

Title:
  distutils : file "bdist_rpm.py"  allows Shell injection in "name"

Status in python2.7 package in Ubuntu:
  Incomplete

Bug description:
  File :
  /usr/lib/python2.7/distutils/command/bdist_rpm.py

  Line 358 :
  This line in the code uses the depreached os.popen command, should be 
replaced with subprocess.Popen() :

  out = os.popen(q_cmd)

  Exploit demo :
  
  1) Download the setup.py script wich i attached
  2) Create a test folder an put the setup.py script in this folder
  3) cd  to the test folder
  4) python setup.py bdist_rpm
  5) A xmessage window pops up as a proof of concept

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libpython2.7-stdlib 2.7.10-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  8 13:47:34 2015
  InstallationDate: Installed on 2015-10-22 (16 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1514183/+subscriptions

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

[Touch-packages] [Bug 1515675] Re: Keypad view not properly formatted when on live call

2015-11-12 Thread Bill Filler

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

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

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

Title:
  Keypad view not properly formatted when on live call

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

Bug description:
  latest rc-proposed

  1) Make a phone call
  2) after call connected, press the keypad icon

  Expected results:
  - contact name should stay in header
  - all action buttons should still be visible

  Actual results:
  - contact name disapears from header
  - keypad buttons overlap the action buttons

  see attached picture

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

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

[Touch-packages] [Bug 1515734] Re: header not resizing properly after showing Recents view

2015-11-12 Thread Bill Filler

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

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

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

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

Title:
  header not resizing properly after showing Recents view

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

Bug description:
  rc-proposed on krillin build 175

  The header is too big after you first view the Recents page, it does
  not properly resize to it's initial height.

  Steps to reproduce:
  1) Launch dialer
  2) Verify header does not contain extra white space lines
  3) pull up recents page from bottom edge
  4) make a phone call or go back to main view

  Expected results:
  header should resize to initial size without extra white space

  Actual results:
  header stays same size as it was in Recents page with extra white space (see 
attachments)

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

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

[Touch-packages] [Bug 1507484] Re: Window Graphics Corrupted for Skype

2015-11-12 Thread Alex N.

Christopher M. Penalver (penalvch) , thanks for the info, will do.
Currently, this is fixed for me on Ubuntu (default) session.

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

Title:
  Window Graphics Corrupted for Skype

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After update to pre-release ubuntu 15.10, skype window graphics is
  corrupted. Resizing and moving the window do not help. Till now, skype
  is the only application having this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda5: clean, 654139/11739136 files, 12149761/46937856 blocks
  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: Mon Oct 19 09:52:18 2015
  DistUpgraded: 2015-10-18 22:05:24,442 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-30-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ca]
  InstallationDate: Installed on 2014-11-03 (349 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=4b8a3a17-f006-45f8-b65f-397b75c1d209 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-10-18 (0 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05PTPV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn05PTPV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Oct 18 22:05:47 2015
  xserver.configfile: default
  xserver.errors: intel(0): sna_mode_check: invalid state found on pipe 1, 
disabling CRTC:25
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8300 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9

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

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

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

2015-11-12 Thread Tony Espy

** Also affects: buteo-syncfw (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: buteo-syncfw (Ubuntu)

** Also affects: buteo-syncfw (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

** Also affects: maliit-framework (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: sync-monitor (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

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

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  New
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

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

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

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

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

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

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

[Touch-packages] [Bug 1283426] Re: nautilus crashed with SIGSEGV in build_file_list_from_uris()

** Bug watch added: GNOME Bug Tracker #757298
   https://bugzilla.gnome.org/show_bug.cgi?id=757298

** Changed in: nautilus
   Importance: Medium => Unknown

** Changed in: nautilus
   Status: Invalid => Unknown

** Changed in: nautilus
 Remote watch: GNOME Bug Tracker #756303 => GNOME Bug Tracker #757298

** Bug watch removed: GNOME Bug Tracker #756303
   https://bugzilla.gnome.org/show_bug.cgi?id=756303

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

Title:
  nautilus crashed with SIGSEGV in build_file_list_from_uris()

Status in Nautilus:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Wily:
  Fix Committed

Bug description:
  I was trying to copy a file out of a VMware Player virtual Windows 7
  guest runnning in a window to nautilus, drag-and-dropping. The reverse
  operation (From nautilus to virtual machine's desktop) is executed
  fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 22 13:16:46 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-02-15 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x7f36910aa0b9:mov(%rdi),%rdi
   PC (0x7f36910aa0b9) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1515712] Re: maliit-server becomes deadlocked

** 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 => Confirmed

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  maliit-server becomes deadlocked

Status in Canonical System Image:
  Confirmed
Status in maliit-framework package in Ubuntu:
  New

Bug description:
  on krillin, rc-proposed 175

  I'm experiencing keyboard not popping up on any application. Can't
  remember if this was after a reboot or if it was working for a while
  and then stopped. I believe it's after a reboot.

  Upon inspection, it appears maliit-server process is deadlocked (see
  thread dump below). Also, there is no log in .cache/upstart/maliit-
  server.log only old logs maliit-server.log.1.gz etc, which leads me to
  believe this problem happens after reboot.

  Seems that some QNetwork initialization is happening and this is
  causing an issue (see Threads 3, 2, and 1). We should figure out why
  we are even doing any network stuff at all, as we probably shouldn't
  be.

  (gdb) t a a bt

  Thread 14 (Thread 0xb2cc2440 (LWP 2844)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb3d03cdc in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #2  0xb3d04c96 in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #3  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #5  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 13 (Thread 0xb2197440 (LWP 3128)):
  #0  0xb435a840 in ?? ()
  #1  0xb436e29c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 12 (Thread 0xb240fb40 (LWP 3129)):
  #0  0xb5c61836 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  #1  0xb5c618a4 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 11 (Thread 0xb1976440 (LWP 3130)):
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 10 (Thread 0xb1176440 (LWP 3131)):
  ---Type  to continue, or q  to quit---
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 9 (Thread 0xb0697440 (LWP 3143)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 8 (Thread 0xafcff440 (LWP 3144)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 7 (Thread 0xaeaff440 (LWP 3146)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 6 (Thread 0xae1ff440 (LWP 3148)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 5 (Thread 0xacb49440 (LWP 3167)):
  #0  0xb66e1132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  ---Type  to continue, or q  to quit---
  #1  0xb3b62312 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #2  0xb3b642ea in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #3  0xb3b6484a in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #4  0xb3b4d678 in core::dbus::Bus::run() () from 
/usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #5  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #7  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous

[Touch-packages] [Bug 1385292] Re: can't rename files in nautilus

2015-11-12 Thread Михаил

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

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

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

Title:
  can't rename files in nautilus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false

2015-11-12 Thread Jamie Strandboge

Thanks Lorn, and just so I'm clear-- I don't think that QtNetwork/etc
should be modified if it doesn't make sense for it in the general case.

All I'm getting at is untrusted apps shouldn't be able to control
interfaces and start a connection as you mentioned, let alone get
privileged info out of network manager. These untrusted apps simply need
to know if they are online or not and maybe some other details that
connectivity-api can provide. How they get that information I don't
particularly care so long as they don't get this privileged access.

It seems clear that QtBearer is written with the traditional
session/policykit trust model, which is fine, but it doesn't align with
the app store trust model where apps are untrusted by the system and
session, so perhaps your idea makes sense. I'll let others work out the
details of what needs to change and how.

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

Title:
  QNetworkSession::isOpen() always returns false

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print "all is well".
  On a vivid phone however, it'll print "network session not open..."

  This used to work fine at least back in utopic images.

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

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

[Touch-packages] [Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports

** No longer affects: whoopsie-daisy (Ubuntu Wily)

** No longer affects: whoopsie-daisy (Ubuntu Vivid)

** No longer affects: whoopsie-daisy (Ubuntu Trusty)

** No longer affects: whoopsie-daisy (Ubuntu)

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

Title:
  whoopsie does not upload UnreportableReason field in crash reports

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Precise:
  Invalid
Status in whoopsie-daisy source package in Precise:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in whoopsie source package in Vivid:
  Fix Committed
Status in whoopsie source package in Wily:
  Fix Committed

Bug description:
  Test Case
  -
  1) Edit a .crash file to have an UnreportableReason key and value e.g.
 UnreportableReason: Your system is weird.
  2) sudo service whoopsie stop
  3) start whoopsie pointing to errors.staging.ubuntu.com e.g.
 sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com 
APPORT_REPORT_DIR=/var/crash/ whoopsie -f
  4) Put said .crash file in /var/crash/
  5) Put a corresponding .upload file in /var/crash/
  6) Observe whoopsie uploading the .crash file from the whoopsie log
 [16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8
  7) go to errors.staging.ubuntu.com/oops/$OOPS_ID
  8) verify the UnreportableReason appears there e.g.:
 https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8

  
  In src/whoopsie.c we can see the following:

  /* We would only want this to see how many bugs would otherwise go
   * unreported: */
  "UnreportableReason",

  The comment isn't exactly true.  apport uses the UnreportableReason
  key to include the following information:

    "You have some obsolete package versions installed."

  It'd be useful if this information was sent to the Error Tracker so
  that we can decide not to ask for a core dump from these crash
  reports. The "obsolete package versions" check is done by checking to
  see if the most recent available version of the package is installed,
  so if someone does not have -updates enabled then that pocket is not
  checked and "obsolete package versions" will not be present. This is
  desirable because the retracers will check to see if the package
  version is available from any pocket.

  So if we send UnreportableReason to the Error Tracker we can stop
  asking for core dumps and retracing crashes that will fail to retrace.

  However, the value for UnreportableReason is translated so this may
  not end up helping much.

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

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

[Touch-packages] [Bug 1441847] Re: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

** Changed in: llvm-toolchain-3.6 (Ubuntu Trusty)
   Importance: Undecided => High

** No longer affects: libdrm (Ubuntu)

** No longer affects: llvm-toolchain-3.6 (Ubuntu)

** No longer affects: xtrans (Ubuntu)

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

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

Title:
  Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

Status in libdrm source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.6 source package in Trusty:
  Fix Released
Status in xtrans source package in Trusty:
  Fix Released

Bug description:
  The vivid X11 stack backport needs libdrm and xtrans backported to
  trusty.

  libdrm 2.4.56-1 -> 2.4.60-2 important changes:
  - new SI & CIK pci-ids (radeon)
  - SKL pci-ids (intel)
  - tegra support

  xtrans 1.3.4-1 -> 1.3.5-1 changes
  - a bunch of const fixes
  - a new Listen function which the X server wants to allow -nolisten tcp by 
default
  http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz

  llvm-toolchain-3.6 is new for trusty, needed by mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/libdrm/+bug/1441847/+subscriptions

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

[Touch-packages] [Bug 1289433] Re: "No accounts" doesn't use the list placeholder font style

** Branch linked: lp:~mardy/ubuntu-system-settings-online-
accounts/placeholder-1289433

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

Title:
  "No accounts" doesn't use the list placeholder font style

Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in webapps-sprint:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Trusty r188

  1. Flash the phone or remove any existing online accounts.
  2. Go to System Settings > "Accounts".

  What you see: "No accounts" in the normal label font style.

  What you should see: "No accounts" in the standard list placeholder
  font style, large and semi-transparent.

  : "If you have none,
  the list of accounts should have 'No accounts' placeholder text..."

  Exactly the same style should be used for "Software is up to date" in
  the Updates screen. If that style is not implemented in the toolkit,
  that should be done first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1289433/+subscriptions

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

[Touch-packages] [Bug 1492769] Re: OSK should be closed before removing page from PageStack

2015-11-12 Thread Zsombor Egri

OSK is removed by the Qt's TextInput or TextEdit components losing
focus. Those lose focus also when the component is deleted or made
invisible. As OSK and the UI are running in separate threads, it is
obvious that you will receive the signal after the page has been closed.

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

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

Title:
  OSK should be closed before removing page from PageStack

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

Bug description:
  Hello, I think I have found a bug from PageStack component, see

  https://bugs.launchpad.net/my-webapp-group/+bug/1490493

  I have produced a small app where the bug can be easily reproduced

  https://code.launchpad.net/~matti-rintanikkola-d/+junk/radial-buttom-
  edge-bug

  Reproduce fault: 
  1) Open "Page2" page from Root page by clicking radial action icon "Home"
  2) click website title/url field in order to open keyboard view
  3) without closing the keyboard turn back to the main view
  4) the main view will be opened without radial actions edge button

  Analysis: The visibility of the main view radial edge button is
  toggled by using the connection

  Connections {
  target: Qt.inputMethod
  onVisibleChanged: nav.visible = !nav.visible
  }

  If you do not close the keyboard when turning back to the Root page
  from "Page2" page the main view became visible before the signal
  onVisibleChanged is fired and when it will be fired the radial edge
  button becomes invisible.

  Solution?: Before removing the page from pageStack it should be
  ensured that the keyboard is not visible. Maybe this could be achieved
  simply by adding a function call Qt.inputMethod.hide() before removing
  the page from pageStack.

  Regards,

  Matti

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

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

[Touch-packages] [Bug 1510876] [NEW] Update to 3.18.2

You have been subscribed to a public bug:

That's being worked on, a first version is available in the desktop team
ppa and in the packaging vcs, the Mir backend still needs updating

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Status: Fix Released


** Tags: upgrade-software-version
-- 
Update to 3.18.2
https://bugs.launchpad.net/bugs/1510876
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1508945] Re: "Couldn't load weather data, please try later again!" with Qt 5.5.1

2015-11-12 Thread Timo Jyrinki

This affects also Shorts app.

The common thing between them is using XMLHttpRequest. The attached QML
(a modified simple QML app in SDK) always returns 0 on the patched vivid
overlay Qt (silo 032) or Qt 5.5.1 (silo 012), on the phone (not on
desktop).

However, even though I said it wouldn't be apparmor related, I do not
get the problem with this test app if running the Main.qml from the
command line. I do get when running it via SDK (which installs the
.click). So maybe it's confinement related after all. I do get apparmor
warnings both with or without the PPA.

** Attachment added: "Main.qml"
   
https://bugs.launchpad.net/ubuntu-weather-app/+bug/1508945/+attachment/4517450/+files/Main.qml

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

Title:
  "Couldn't load weather data, please try later again!" with Qt 5.5.1

Status in Ubuntu Weather App:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The weather data cannot be seemingly loaded with Qt 5.5.1.

  More information about Qt 5.5 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1501300] Re: Wily (15.10) this package got not compiled with __cxx11 support

2015-11-12 Thread Matthias Goldhoorn

The package needs to be build with gcc5.2 to have the correct (dualabi)
symbols in the library.

Therefore the back port to 15.10 is definitely needed! Otherwise 3th
parity libs cannot link against the clang compiler (what we definitely
need)

In generall all librarys on a dualabi system (>=gcc5.2) should be compilet with 
a dualabi compiler. 
By enforcing this the system becomes consistend and fully compiletime safe 
against c++11.
Mixing pre-dual abi's and and compiled user application can cause a invalid 
binary.

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

Title:
  Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Fix Released

Bug description:
  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  
  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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

[Touch-packages] [Bug 1276808] Re: new API that allows to know what the current mode is (desktop, phone, tablet)

2015-11-12 Thread Zsombor Egri

As long as it will be back ported to Qt 5.4 I'm OK with it. Otherwise we
need an API of our own till we migrate to Qt 5.6.

** Tags added: convergence

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

Title:
  new API that allows to know what the current mode is (desktop, phone,
  tablet)

Status in Ubuntu HTML5 UI SDK:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  https://docs.google.com/a/canonical.com/document/d
  /1TvvPAxJbxqvCvWhwkdkt15G-BY-neyYfmxXlg9FInUo/edit?disco=AKLL3f4#

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

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

[Touch-packages] [Bug 1477363] Re: onDestruction is never called in the QML component

2015-11-12 Thread XiaoGuo, Liu

But the same code on desktop has the output.

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

Title:
  onDestruction is never called in the QML component

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

Bug description:
  I have created a very simple application, and I want to capture the
  onDestruction event. However, it is never called on a phone, but it is
  called on the desktop. On the page,
  http://developer.ubuntu.com/api/apps/qml/sdk-15.04/Qt.labs.settings.Settings/,
  it is used to save the state of the application.

Page {
  title: i18n.tr("ondestruction")

  Column {
  spacing: units.gu(1)
  anchors {
  margins: units.gu(2)
  fill: parent
  }

  Label {
  id: label
  objectName: "label"

  text: i18n.tr("Hello..")
  }

  Button {
  objectName: "button"
  width: parent.width

  text: i18n.tr("Tap me!")

  onClicked: {
  label.text = i18n.tr("..world!")
  }
  }
  }

  Component.onDestruction: {
  console.log("ondestruction")
  }
  }

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

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

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

2015-11-12 Thread Daniel d'Andrada

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

This is bug 1474319, which we fixed a while ago.

** This bug has been marked a duplicate of bug 1474319
   app spread only shows shadows of apps, no content

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

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

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

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

  Thanks for your hard work,

  Regards

  Dave H

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

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

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

2015-11-12 Thread Bartosz Kosiorek

Unfortunately we cannot fix that in Timer. When we are set new alarm for 9.00 
AM, the alarm will ring at 9.00 AM local time.
Example:
1. Let's say we would like to set Timer for 15 minutes and local time 9.00 AM 
Timezone +0
2. From Timer, we are setting up alarm for 9.15 AM Timezone +0
3. Now we are changing time zone to -1, so the local time will be 8.00 AM 
Timezone -1
4. Alarm will be the same, so 9.15 AM Timezone -1

Current result:
  - Alarm/Timer will start ringing for 1 hour and 15 minutes

Expected result:
  - Alarm/Timer should  start ringing always after 15 minutes, and should not 
be dependent from timezone

For timer we would like to ring in absolute time (UTC), not dependent from time 
zone.
Maybe there is some way to setup alarm in UTC?
If yes, I would love to implement that in Timer.

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

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

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

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

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

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

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

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

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

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

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

2015-11-12 Thread Martin Pitt

Many thanks Serge for figuring that out!

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

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

Status in lxc package in Ubuntu:
  Fix Committed

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

sudo lxc-start -n adt-xenial -F

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

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

  Welcome to Ubuntu 16.04!

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

  During that time, I get the following errors:

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

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

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

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

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

2015-11-12 Thread Serge Hallyn

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

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

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

Status in lxc package in Ubuntu:
  Fix Committed

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

sudo lxc-start -n adt-xenial -F

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

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

  Welcome to Ubuntu 16.04!

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

  During that time, I get the following errors:

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

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

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

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

[Touch-packages] [Bug 1477363] Re: onDestruction is never called in the QML component

2015-11-12 Thread Zsombor Egri

In your example, the Page is declared as an instance. When you close the
application, the elements will be destroyed silently, without having
their attached Component.onDestruction called.

When you use a Page declared in the way you reported in a PageStack or
AdaptivePageLayout, the Page will not be destroyed by these components
as it has not been created by the PageStack/AdaptivePagelayout. So you
won't get the onDestruction triggered either. In order to have that
coming, you need to declare your page as component and add that to the
PageStack/AdaptivePageLayout, or in a separate QML document and use
that.


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

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

Title:
  onDestruction is never called in the QML component

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

Bug description:
  I have created a very simple application, and I want to capture the
  onDestruction event. However, it is never called on a phone, but it is
  called on the desktop. On the page,
  http://developer.ubuntu.com/api/apps/qml/sdk-15.04/Qt.labs.settings.Settings/,
  it is used to save the state of the application.

Page {
  title: i18n.tr("ondestruction")

  Column {
  spacing: units.gu(1)
  anchors {
  margins: units.gu(2)
  fill: parent
  }

  Label {
  id: label
  objectName: "label"

  text: i18n.tr("Hello..")
  }

  Button {
  objectName: "button"
  width: parent.width

  text: i18n.tr("Tap me!")

  onClicked: {
  label.text = i18n.tr("..world!")
  }
  }
  }

  Component.onDestruction: {
  console.log("ondestruction")
  }
  }

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

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

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

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

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

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

  All machine involved are running trusty:

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

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515512] [NEW] upower.service fails with core dumps

2015-11-12 Thread Thomas

Public bug reported:

The upower service is crashing at startup.


Nov 12 09:15:49 next systemd[1]: Starting Daemon for power management...
Nov 12 09:15:49 next systemd[1]: Started Daemon for power management.
Nov 12 09:15:51 next usbmuxd[16099]: [09:15:51.475][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/c7ccdf3c1bfcdca6e52320fb51f1fe238a1
31ca3.plist': No such file or directory
Nov 12 09:15:52 next kernel: [ 5456.001802] traps: upowerd[6635] general 
protection ip:7f8b785d31cb sp:7ffd6259bbc0 error:0 in libc-2.21.so[7f8b785540
00+1c]
Nov 12 09:15:52 next systemd[1]: upower.service: Main process exited, 
code=dumped, status=11/SEGV
Nov 12 09:15:52 next systemd[1]: upower.service: Unit entered failed state.
Nov 12 09:15:52 next systemd[1]: upower.service: Failed with result 'core-dump'.
Nov 12 09:15:52 next systemd[1]: upower.service: Service hold-off time over, 
scheduling restart.
Nov 12 09:15:52 next systemd[1]: Stopped Daemon for power management.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: upower 0.99.3-1build2
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Thu Nov 12 09:14:36 2015
InstallationDate: Installed on 2012-10-15 (1122 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121014)
SourcePackage: upower
UpgradeStatus: Upgraded to wily on 2015-11-02 (9 days ago)

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


** Tags: amd64 apport-bug wily

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

Title:
  upower.service fails with core dumps

Status in upower package in Ubuntu:
  New

Bug description:
  The upower service is crashing at startup.

  
  Nov 12 09:15:49 next systemd[1]: Starting Daemon for power management...
  Nov 12 09:15:49 next systemd[1]: Started Daemon for power management.
  Nov 12 09:15:51 next usbmuxd[16099]: [09:15:51.475][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/c7ccdf3c1bfcdca6e52320fb51f1fe238a1
  31ca3.plist': No such file or directory
  Nov 12 09:15:52 next kernel: [ 5456.001802] traps: upowerd[6635] general 
protection ip:7f8b785d31cb sp:7ffd6259bbc0 error:0 in libc-2.21.so[7f8b785540
  00+1c]
  Nov 12 09:15:52 next systemd[1]: upower.service: Main process exited, 
code=dumped, status=11/SEGV
  Nov 12 09:15:52 next systemd[1]: upower.service: Unit entered failed state.
  Nov 12 09:15:52 next systemd[1]: upower.service: Failed with result 
'core-dump'.
  Nov 12 09:15:52 next systemd[1]: upower.service: Service hold-off time over, 
scheduling restart.
  Nov 12 09:15:52 next systemd[1]: Stopped Daemon for power management.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: upower 0.99.3-1build2
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Thu Nov 12 09:14:36 2015
  InstallationDate: Installed on 2012-10-15 (1122 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121014)
  SourcePackage: upower
  UpgradeStatus: Upgraded to wily on 2015-11-02 (9 days ago)

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

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

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

2015-11-12 Thread Michi Henning

"Fred, thanks for getting bad to us!"

Bloody auto-correct. My apologies, that should have read "... getting
back to us!"

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

Title:
  No thumbnails generated for OGG audio

Status in music-app package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  New

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

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

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

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

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

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

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

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

The modemmanager trusty SRU has been sponsored, thanks Mathieu
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1_text=modemmanager

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  In Progress
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]
   
   * None

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

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

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

  Could we backport this patch  into trusty? Thanks!

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

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

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

(n-m as well)

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  In Progress
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]
   
   * None

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

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

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

  Could we backport this patch  into trusty? Thanks!

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

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

[Touch-packages] [Bug 1289433] Re: "No accounts" doesn't use the list placeholder font style

2015-11-12 Thread Alberto Mardegan

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-system-settings-online-accounts
   Status: Confirmed => In Progress

** Changed in: ubuntu-system-settings-online-accounts
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** Changed in: webapps-sprint
Milestone: None => sprint-16

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: webapps-sprint
   Importance: Undecided => Low

** Changed in: webapps-sprint
   Status: New => In Progress

** Changed in: webapps-sprint
   Importance: Low => Medium

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

Title:
  "No accounts" doesn't use the list placeholder font style

Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in webapps-sprint:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Trusty r188

  1. Flash the phone or remove any existing online accounts.
  2. Go to System Settings > "Accounts".

  What you see: "No accounts" in the normal label font style.

  What you should see: "No accounts" in the standard list placeholder
  font style, large and semi-transparent.

  : "If you have none,
  the list of accounts should have 'No accounts' placeholder text..."

  Exactly the same style should be used for "Software is up to date" in
  the Updates screen. If that style is not implemented in the toolkit,
  that should be done first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1289433/+subscriptions

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

[Touch-packages] [Bug 1501300] Re: Wily (15.10) this package got not compiled with __cxx11 support

debdiff to backport if you want to SRU the change
http://anonscm.debian.org/viewvc/pkg-llvm/llvm-toolchain/branches/3.4/debian/rules?r1=1456=1610

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

Title:
  Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Fix Released

Bug description:
  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  
  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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

[Touch-packages] [Bug 1508945] Re: "Couldn't load weather data, please try later again!" with Qt 5.5.1

2015-11-12 Thread Timo Jyrinki

Applying my patch
https://launchpadlibrarian.net/219307454/apparmor_allow_qnetworksession_isopen.patch
from bug #1404188 to the test app would fix the issue, if allowed in. It
seems with Qt 5.5 it'd now be a requirement.

And true, now that I tested it again, the same applies to weather app.
So my previous attempt at running weather app unconfined was not
actually successful.

** Also affects: apparmor-easyprof-ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  "Couldn't load weather data, please try later again!" with Qt 5.5.1

Status in Ubuntu Weather App:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The weather data cannot be seemingly loaded with Qt 5.5.1.

  More information about Qt 5.5 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1501300] Re: Wily (15.10) this package got not compiled with __cxx11 support

oh, right, thanks for the details

-16 from Debian has been synced to current Ubuntu
https://launchpad.net/ubuntu/+source/llvm-toolchain-3.4/1:3.4.2-16

Unsure what to do about 15.10, the current package is built with gcc 4.9
and I'm unsure what's the impact of building with gcc5 and if that's
fine for a SRU

** Changed in: llvm-toolchain-3.4 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Fix Released

Bug description:
  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  
  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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

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

2015-11-12 Thread Shih-Yuan Lee

Thanks a lot.

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  In Progress
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]
   
   * None

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

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

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

  Could we backport this patch  into trusty? Thanks!

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

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

[Touch-packages] [Bug 1513024] Re: Display-server randomly crashing in Ubuntu 15.10 after upgrade

2015-11-12 Thread Andreas

Errors in dmesg right from two crashes (only a short time apart):

[13809.068337] nouveau E[   PIBUS][:02:00.0] HUB0: 0x6013d4 0x5700 
(0x1b708200)
[13809.068364] nouveau E[   PIBUS][:02:00.0] GPC0: 0x4188ac 0x0001 
(0x1b70822e)
[13809.068428] nouveau E[   PIBUS][:02:00.0] HUB0: 0x10ecc0 0x 
(0x1970822c)

[13843.556600] nouveau E[   PIBUS][:02:00.0] HUB0: 0x6013d4 0x5700 
(0x1b708200)
[13843.556627] nouveau E[   PIBUS][:02:00.0] GPC0: 0x4188ac 0x0001 
(0x1b70822e)
[13843.556692] nouveau E[   PIBUS][:02:00.0] HUB0: 0x10ecc0 0x 
(0x1970822c)

The addresses seem to stay the same between crashes.

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

Title:
  Display-server randomly crashing in Ubuntu 15.10 after upgrade

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On: Ubuntu 15.10

  After some random amount of time (at first correlated with actions
  such as switching between screens, max-/minimising windows, but now
  also sometimes not), the display server seems to die completely,
  restarting after a few seconds to dump me at the login screen.

  Getting errors like:

  $ dmesg
  ...
  [  239.809761] WARNING: CPU: 0 PID: 1879 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 
i915_gem_track_fb+0x129/0x140 [i915]()
  [  239.809762] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits))
  [  239.809763] Modules linked in:
  [  239.809765]  rfcomm msr acpi_call(OE) pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) openafs(POE) binfmt_misc bnep btusb btrtl btbcm 
btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
v4l2_common videodev media arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel iwlmvm aes_x86_64 lrw gf128mul glue_helper mac80211 ablk_helper 
cryptd joydev input_leds snd_seq_midi serio_raw snd_seq_midi_event 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi thinkpad_acpi 
snd_rawmidi nvram iwlwifi snd_seq snd_hda_intel rtsx_pci_ms memstick 
snd_hda_codec lpc_ich cfg80211 snd_hda_core snd_hwdep snd_pcm mei_me 
ie31200_edac mei snd_seq_device edac_core shpchp snd_timer snd soundcore
  [  239.809798]  ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 mac_hid xt_hl ip6t_rt 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 
rtsx_pci_sdmmc nouveau i915 mxm_wmi ttm e1000e i2c_algo_bit psmouse ahci 
drm_kms_helper libahci ptp rtsx_pci pps_core drm wmi video
  [  239.809822] CPU: 0 PID: 1879 Comm: Xorg Tainted: P   OE   
4.2.0-16-generic #19-Ubuntu
  [  239.809824] Hardware name: LENOVO 20AWS37E00/20AWS37E00, BIOS GLET77WW 
(2.31 ) 01/27/2015
  [  239.809825]   2aa5ef7b 8800a922fac8 
817e8c09
  [  239.809827]   8800a922fb20 8800a922fb08 
8107b3c6
  [  239.809829]  880425a47840 0010 8804256a 
8804256a
  [  239.809831] Call Trace:
  [  239.809836]  [] dump_stack+0x45/0x57
  [  239.809841]  [] warn_slowpath_common+0x86/0xc0
  [  239.809843]  [] warn_slowpath_fmt+0x55/0x70
  [  239.809853]  [] i915_gem_track_fb+0x129/0x140 [i915]
  [  239.809868]  [] intel_prepare_plane_fb+0xe7/0x1a0 [i915]
  [  239.809874]  [] 
drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper]
  [  239.809887]  [] ? drm_atomic_check_only+0x215/0x540 [drm]
  [  239.809901]  [] intel_atomic_commit+0x42/0x100 [i915]
  [  239.809910]  [] drm_atomic_commit+0x37/0x60 [drm]
  [  239.809915]  [] 
drm_atomic_helper_plane_set_property+0x87/0xc0 [drm_kms_helper]
  [  239.809922]  [] ? _object_find+0x69/0xa0 [drm]
  [  239.809930]  [] drm_mode_plane_set_obj_prop+0x2d/0x90 
[drm]
  [  239.809939]  [] 
drm_mode_obj_set_property_ioctl+0x1c6/0x270 [drm]
  [  239.809944]  [] drm_ioctl+0x125/0x610 [drm]
  [  239.809947]  [] ? fsnotify+0x316/0x4a0
  [  239.809954]  [] ? 
drm_mode_obj_get_properties_ioctl+0xa0/0xa0 [drm]
  [  239.809957]  [] do_vfs_ioctl+0x295/0x480
  [  239.809959]  [] ? __sb_end_write+0x35/0x70
  [  239.809961]  [] ? vfs_write+0x15a/0x1a0
  [  239.809963]  [] SyS_ioctl+0x79/0x90
  [  239.809966]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  239.809967] ---[ end trace d4f1687d97169580 ]---
  [  240.634359] nouveau E[   PIBUS][:02:00.0] HUB0: 0x6013d4 0x5704 
(0x1c708200)
  [  240.634368] nouveau E[   PIBUS][:02:00.0] GPC0: 0x4188ac 0x0001 
(0x1c70822e)

  where the latter part also appears in the error log after xserver
  crashed, briefly visible before

[Touch-packages] [Bug 1510876] Re: Update to 3.18.2

https://launchpad.net/ubuntu/+source/gtk+3.0

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

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

Title:
  Update to 3.18.2

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  That's being worked on, a first version is available in the desktop
  team ppa and in the packaging vcs, the Mir backend still needs
  updating

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1510876/+subscriptions

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

[Touch-packages] [Bug 1508564] Re: cross binutils don't include the system search paths

2015-11-12 Thread Matthias Klose

all cross ld versions now include the system search paths.


** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1508564

Title:
  cross binutils don't include the system search paths

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Wily:
  Fix Committed

Bug description:
  e.g.

  $ powerpc64le-linux-gnu-ld --verbose |grep SEARCH_DIR
  SEARCH_DIR("/usr/powerpc64le-linux-gnu/lib64le"); 
SEARCH_DIR("/usr/powerpc64le-linux-gnu/lib");

  that should read (like in vivid):
  $ powerpc64le-linux-gnu-ld --verbose |grep SEARCH_DIR
  SEARCH_DIR("=/usr/powerpc64le-linux-gnu/lib64le"); 
SEARCH_DIR("=/usr/local/lib64le"); SEARCH_DIR("=/lib64le"); 
SEARCH_DIR("=/usr/lib64le"); SEARCH_DIR("=/usr/powerpc64le-linux-gnu/lib"); 
SEARCH_DIR("=/usr/local/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/usr/local/lib"); SEARCH_DIR("=/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/usr/lib");

  Acceptance criteria: all cross ld versions include the system search
  paths.

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

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

[Touch-packages] [Bug 1488788] Re: The picture still contains location information even when the location tagging is off

2015-11-12 Thread Allan LeSage

Confirmed in preparation for OTA8 FWIW, krillin rc-proposed 175.

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

Title:
  The picture still contains location information even when the location
  tagging is off

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 109
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-30 02:57:15
  version version: 109
  version ubuntu: 20150825.1
  version device: 20150821-736d127
  version custom: 20150821-887-33-32-vivid

  Steps:
  1.Disable geotagging 
  2.Take a picture
  3.Transfer to desktop
  4.(install exiftool) Run "exiftool -gpslatitude -gpslongitude "

  Expectation:
  Verify that the picture doesn't contain location information

  Actual result:
  After step 4, there is still location information shows up in the terminal

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

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

[Touch-packages] [Bug 1515816] [NEW] selected SIM hard for some people to see

2015-11-12 Thread Selene Scriven

Public bug reported:

To indicate which SIM slot is active, the messaging-app changes the SIM
label from black-on-white to dark-red-on-white.  For red-colorblind
people, this highlight makes no significant difference.  Studies
estimate that this affects about 8% of the male population and about
0.5% of the female population.

Could the visual change be made slightly more noticeable?  Perhaps only
underline the active slot, or render the active slot in a bold font, or
maybe change the color to something with higher contrast compared to the
inactive slot?

A screenshot is attached.  The top row shows no SIM selected, while the
second row shows SIM 2 selected.  To red-colorblind people, they look
nearly identical.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Attachment added: "sim-selected.png"
   
https://bugs.launchpad.net/bugs/1515816/+attachment/4517904/+files/sim-selected.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/1515816

Title:
  selected SIM hard for some people to see

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  To indicate which SIM slot is active, the messaging-app changes the
  SIM label from black-on-white to dark-red-on-white.  For red-
  colorblind people, this highlight makes no significant difference.
  Studies estimate that this affects about 8% of the male population and
  about 0.5% of the female population.

  Could the visual change be made slightly more noticeable?  Perhaps
  only underline the active slot, or render the active slot in a bold
  font, or maybe change the color to something with higher contrast
  compared to the inactive slot?

  A screenshot is attached.  The top row shows no SIM selected, while
  the second row shows SIM 2 selected.  To red-colorblind people, they
  look nearly identical.

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

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

[Touch-packages] [Bug 1515569] Re: /lib/systemd/systemd-logind:7:siphash24_compress:base_bucket_hash:hashmap_put:add_object_vtable_internal:manager_startup

The stacktrace looks rather uninformative and that is likely due to the
apport bug looking up -dbg symbol packages Martin and I fixed last week.
I've submitted and RT to have the production verions of the Error
Tracker retracers updated, after which this crash may move to a
different bucket.

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

Title:
  /lib/systemd/systemd-
  
logind:7:siphash24_compress:base_bucket_hash:hashmap_put:add_object_vtable_internal:manager_startup

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  227-2ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/40601234918498089c81001cd7b6a7f06bf12fe7
  contains more details.

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

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

[Touch-packages] [Bug 1515818] [NEW] apparmor profile has a typo

2015-11-12 Thread John Johansen

Public bug reported:

apparmor reports the following denial

Nov  4 06:36:31 ortho2 kernel: [  155.310264] audit: type=1400
audit(1446647791.742:151): apparmor="DENIED" operation="signal"
profile="/usr/lib/NetworkManager/nm-dhcp-helper" pid=3056 comm="kill"
requested_mask="send" denied_mask="send" signal=term
peer="/sbin/dhclient"

this is due to a typo in the /usr/lib/NetworkManager/nm-dhcp-helper
profile.

The attached patch will fix the problem

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "dhclient.patch"
   
https://bugs.launchpad.net/bugs/1515818/+attachment/4517905/+files/dhclient.patch

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

Title:
  apparmor profile has a typo

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  apparmor reports the following denial

  Nov  4 06:36:31 ortho2 kernel: [  155.310264] audit: type=1400
  audit(1446647791.742:151): apparmor="DENIED" operation="signal"
  profile="/usr/lib/NetworkManager/nm-dhcp-helper" pid=3056 comm="kill"
  requested_mask="send" denied_mask="send" signal=term
  peer="/sbin/dhclient"

  this is due to a typo in the /usr/lib/NetworkManager/nm-dhcp-helper
  profile.

  The attached patch will fix the problem

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

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

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

nimu, what will be most helpful is if you returned your packages to the
ones from the Ubuntu repositories (i.e. remove the PPA packages), then
added the PPA, then updated one package at a time from that PPA to find
out which package precisely is the one that addressed this issue.

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

Title:
  Xorg crash (probably on window resize)

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

[Touch-packages] [Bug 1499556] Re: Computer Reboots Instead of Halting

Ed Novak, the latest mainline kernel is 4.3 (not 4.3-rcX).

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

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

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

Title:
  Computer Reboots Instead of Halting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Ubuntu 14.04 LTS, everytime I try to shutdown my system reboots instead. 
I have tried a variety of shutdown methods including:
  sudo init 0
  sudo shutdown -P now
  sudo shutdown now
  sudo shutdown -h now
  sudo shutdown -H now
  sudo shutdown -HP now
  (all previous variants with "now" replaced with "1")
  shutting down via the KDE menu (clicking the menu, clicking 'leave' section, 
clicking shutdown in the dialog box).

  The system hard shuts down if I hold the power button for 5 seconds.

  I have attached a zip of my entire /var/log directory.

  ---
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: kubuntu
  DkmsStatus: fglrx-core, 15.200, 3.16.0-50-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation Device [1849:9832]
  InstallationDate: Installed on 2015-08-21 (53 days ago)
  InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150219.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: fglrx
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic 
root=UUID=13cf69b2-83fd-4907-ba34-fa3e24e8294a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
  Tags:  trusty kubuntu
  Uname: Linux 3.16.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: QC5000-ITX/PH
  dmi.board.vendor: ASRock
  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.:bvrP1.00:bd10/27/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQC5000-ITX/PH:rvr: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 N/A
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 13 20:01:14 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
  xserver.video_driver: fglrx

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

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

[Touch-packages] [Bug 1507298] Re: [wily] user-mounted FUSE filesystems won't unmount

I also tested this in Wily and was able to unmount a directory mounted
via sshfs.

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

Title:
  [wily] user-mounted FUSE filesystems won't unmount

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Wily:
  Incomplete
Status in util-linux package in Gentoo Linux:
  Unknown

Bug description:
  Steps to reproduce:
  1) mount any user-mounted FUSE filesystem: sshfs, mp3fs, achivemount, 
ntfs-3g, ...
  2) try to umount it using $ fusermount -u 
  3) observe the fail, claiming it wasn't found in /etc/mtab

  Observed with util-linux 2.26.2-6ubuntu3

  The bug on the gentoo bugtracker:
  https://bugs.gentoo.org/show_bug.cgi?id=435540

  There I've found a link to the in-upstream patch:
  
http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=4be900c51d371a7a41495e4eca2d29fc77c20c7c

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

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

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

2015-11-12 Thread Phillip Susi

This is weird.. I see no reason why the rule shouldn't work as is, and
it works fine for me without any modifications...

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

Title:
  LVM filesystems not mounted at boot

Status in lvm2 package in Ubuntu:
  Confirmed

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

  lvm vgscan
  lvm vgchange -a y

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

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

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

[Touch-packages] [Bug 1507298] Re: [wily] user-mounted FUSE filesystems won't unmount

This seems fixed in Wily too, as the changes in
https://git.kernel.org/cgit/utils/util-linux/util-
linux.git/commit/?id=4be900c51d371a7a41495e4eca2d29fc77c20c7c exist in
the wily version of the package.

https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/util-
linux/wily/view/head:/libmount/src/context_mount.c#L175

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

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

Title:
  [wily] user-mounted FUSE filesystems won't unmount

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Wily:
  Incomplete
Status in util-linux package in Gentoo Linux:
  Unknown

Bug description:
  Steps to reproduce:
  1) mount any user-mounted FUSE filesystem: sshfs, mp3fs, achivemount, 
ntfs-3g, ...
  2) try to umount it using $ fusermount -u 
  3) observe the fail, claiming it wasn't found in /etc/mtab

  Observed with util-linux 2.26.2-6ubuntu3

  The bug on the gentoo bugtracker:
  https://bugs.gentoo.org/show_bug.cgi?id=435540

  There I've found a link to the in-upstream patch:
  
http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=4be900c51d371a7a41495e4eca2d29fc77c20c7c

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

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

[Touch-packages] [Bug 1513528] Re: /usr/bin/software-properties-gtk:KeyError:getitem:getitem:show_drivers:set_driver_action_status:getitem

The traceback:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1375, in show_drivers
self.set_driver_action_status()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1398, in set_driver_action_status
pkg = self.apt_cache[pkg_name]
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 205, in __getitem__
raise KeyError('The cache has no package named %r' % key)
KeyError: "The cache has no package named 'xserver-xorg-video-nouveau'"

** Tags added: rls-x-incoming

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

Title:
  /usr/bin/software-properties-
  
gtk:KeyError:__getitem__:__getitem__:show_drivers:set_driver_action_status:__getitem__

Status in software-properties package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports

Valiantly verified via Vivid.

https://errors.staging.ubuntu.com/oops/a3ee54aa-8994-11e5-b0b0-fa163e1893a8

** Tags added: verification-done-vivid

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

Title:
  whoopsie does not upload UnreportableReason field in crash reports

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Precise:
  Invalid
Status in whoopsie-daisy source package in Precise:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in whoopsie source package in Vivid:
  Fix Committed
Status in whoopsie source package in Wily:
  Fix Committed

Bug description:
  Test Case
  -
  1) Edit a .crash file to have an UnreportableReason key and value e.g.
 UnreportableReason: Your system is weird.
  2) sudo service whoopsie stop
  3) start whoopsie pointing to errors.staging.ubuntu.com e.g.
 sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com 
APPORT_REPORT_DIR=/var/crash/ whoopsie -f
  4) Put said .crash file in /var/crash/
  5) Put a corresponding .upload file in /var/crash/
  6) Observe whoopsie uploading the .crash file from the whoopsie log
 [16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8
  7) go to errors.staging.ubuntu.com/oops/$OOPS_ID
  8) verify the UnreportableReason appears there e.g.:
 https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8

  
  In src/whoopsie.c we can see the following:

  /* We would only want this to see how many bugs would otherwise go
   * unreported: */
  "UnreportableReason",

  The comment isn't exactly true.  apport uses the UnreportableReason
  key to include the following information:

    "You have some obsolete package versions installed."

  It'd be useful if this information was sent to the Error Tracker so
  that we can decide not to ask for a core dump from these crash
  reports. The "obsolete package versions" check is done by checking to
  see if the most recent available version of the package is installed,
  so if someone does not have -updates enabled then that pocket is not
  checked and "obsolete package versions" will not be present. This is
  desirable because the retracers will check to see if the package
  version is available from any pocket.

  So if we send UnreportableReason to the Error Tracker we can stop
  asking for core dumps and retracing crashes that will fail to retrace.

  However, the value for UnreportableReason is translated so this may
  not end up helping much.

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

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

[Touch-packages] [Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports

Timely testing in Trusty.

https://errors.staging.ubuntu.com/oops/67e35180-8995-11e5-a417-fa163e1893a8

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

Title:
  whoopsie does not upload UnreportableReason field in crash reports

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Precise:
  Invalid
Status in whoopsie-daisy source package in Precise:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in whoopsie source package in Vivid:
  Fix Committed
Status in whoopsie source package in Wily:
  Fix Committed

Bug description:
  Test Case
  -
  1) Edit a .crash file to have an UnreportableReason key and value e.g.
 UnreportableReason: Your system is weird.
  2) sudo service whoopsie stop
  3) start whoopsie pointing to errors.staging.ubuntu.com e.g.
 sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com 
APPORT_REPORT_DIR=/var/crash/ whoopsie -f
  4) Put said .crash file in /var/crash/
  5) Put a corresponding .upload file in /var/crash/
  6) Observe whoopsie uploading the .crash file from the whoopsie log
 [16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8
  7) go to errors.staging.ubuntu.com/oops/$OOPS_ID
  8) verify the UnreportableReason appears there e.g.:
 https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8

  
  In src/whoopsie.c we can see the following:

  /* We would only want this to see how many bugs would otherwise go
   * unreported: */
  "UnreportableReason",

  The comment isn't exactly true.  apport uses the UnreportableReason
  key to include the following information:

    "You have some obsolete package versions installed."

  It'd be useful if this information was sent to the Error Tracker so
  that we can decide not to ask for a core dump from these crash
  reports. The "obsolete package versions" check is done by checking to
  see if the most recent available version of the package is installed,
  so if someone does not have -updates enabled then that pocket is not
  checked and "obsolete package versions" will not be present. This is
  desirable because the retracers will check to see if the package
  version is available from any pocket.

  So if we send UnreportableReason to the Error Tracker we can stop
  asking for core dumps and retracing crashes that will fail to retrace.

  However, the value for UnreportableReason is translated so this may
  not end up helping much.

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

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

[Touch-packages] [Bug 1515755] [NEW] Sync gpgme1.0 1.6.0-1 (main) from Debian unstable (main)

2015-11-12 Thread Jackson Doak

Public bug reported:

Please sync gpgme1.0 1.6.0-1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Merge from debian unstable. Remaining changes:
- debian/rules: Switch back to using /usr/bin/gpg and add back gnupg
  build dependency, as we don't install gnupg2 by default.
- debian/control: Depends on "gnupg | gnupg2" rather than gnupg2,
  default to the old version since the new one depends on gpg-agent,
  pinentry-gtk2, and a bunch of other packages we don't need/want in
  the default installation
The default install now includes both gnupg2 and pinentry-gtk3

Changelog entries since current xenial version 1.5.5-3ubuntu1:

gpgme1.0 (1.6.0-1) unstable; urgency=medium

  * New upstream release.

 -- Daniel Kahn Gillmor   Thu, 17 Sep 2015
03:40:48 -0400

** Affects: gpgme1.0 (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: gpgme1.0 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync gpgme1.0 1.6.0-1 (main) from Debian unstable (main)

Status in gpgme1.0 package in Ubuntu:
  New

Bug description:
  Please sync gpgme1.0 1.6.0-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge from debian unstable. Remaining changes:
  - debian/rules: Switch back to using /usr/bin/gpg and add back gnupg
build dependency, as we don't install gnupg2 by default.
  - debian/control: Depends on "gnupg | gnupg2" rather than gnupg2,
default to the old version since the new one depends on gpg-agent,
pinentry-gtk2, and a bunch of other packages we don't need/want in
the default installation
  The default install now includes both gnupg2 and pinentry-gtk3

  Changelog entries since current xenial version 1.5.5-3ubuntu1:

  gpgme1.0 (1.6.0-1) unstable; urgency=medium

* New upstream release.

   -- Daniel Kahn Gillmor   Thu, 17 Sep 2015
  03:40:48 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1515755/+subscriptions

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

[Touch-packages] [Bug 1514183] Re: distutils : file "bdist_rpm.py" allows Shell injection in "name"

2015-11-12 Thread Bernd Dietzel

Hello Tyler,
i only used the setup script because the distutils.core.setup() function takes 
such a large number of arguments, so its more easy to read than in one single 
line of code.

No, i haven't  reported this issue to upstream.

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

Title:
  distutils : file "bdist_rpm.py"  allows Shell injection in "name"

Status in python2.7 package in Ubuntu:
  Incomplete

Bug description:
  File :
  /usr/lib/python2.7/distutils/command/bdist_rpm.py

  Line 358 :
  This line in the code uses the depreached os.popen command, should be 
replaced with subprocess.Popen() :

  out = os.popen(q_cmd)

  Exploit demo :
  
  1) Download the setup.py script wich i attached
  2) Create a test folder an put the setup.py script in this folder
  3) cd  to the test folder
  4) python setup.py bdist_rpm
  5) A xmessage window pops up as a proof of concept

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libpython2.7-stdlib 2.7.10-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  8 13:47:34 2015
  InstallationDate: Installed on 2015-10-22 (16 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1514183/+subscriptions

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

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

I don't see any SRU information regarding how to test the network-
manager change use-the-gateway-from-ModemManager.patch. Could this
please be added to the description so that we can accept network-manager
into -proposed? Thanks!

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

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]
   
   * None

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

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

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

  Could we backport this patch  into trusty? Thanks!

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

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

[Touch-packages] [Bug 1379421] Re: [messaing-app] shouldn't rotate into landscape mode as causes issues with compose and main view

2015-11-12 Thread Allan LeSage

While running OTA8 manual tests, finding that rotation works well but
leaves some layout decisions to be made--specifically there's an ugly
overlay on krillin, will attach screenie.

I'm hijacking this bug for discussion as I see recent activity here,
please feel free to re-open elsewhere (or to re-title this bug as
appropriate).

** Attachment added: "screenshot20151112_235324191.png"

https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1379421/+attachment/4517899/+files/screenshot20151112_235324191.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/1379421

Title:
[messaing-app] shouldn't rotate into landscape mode as causes issues
with compose and main view

Status in Ubuntu UX:
Fix Committed
Status in messaging-app package in Ubuntu:
Confirmed

Bug description:
Build r93

The messaging app rotates to make it easier to type and read messaging
threads. However, this causes issues in the compose and main views.
If you rotate the app into landscape mode on the landing view, there is no
way to carry out a bottom edge swipe to compose a new message.
In the compose view, the landscape mode doesn't show the header. This one is
needed, to add ppl to the recipient list.

Recommendation: The ideal case is that we would have a custom header
for landscape views because the current one in portrait mode is too
large for certain devices. This needs further investigation from
design and probably SDK. Plus there is still the issue of the bottom
edge swipe in landscape, which needs to be addressed by Unity.
Therefor it would be best to remove this feature for the RTM release.

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

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

[Touch-packages] [Bug 1509005] Re: [regression] mir-client-platform-mesa-dev pkg-config file dropped

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu Wily)
   Importance: Undecided => High

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

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

** Tags removed: regression
** Tags added: regression-release wily

** Changed in: mesa (Ubuntu Wily)
Milestone: None => wily-updates

** Changed in: mir (Ubuntu)
Milestone: wily-updates => None

** Changed in: xorg-server (Ubuntu Wily)
Milestone: None => wily-updates

** Tags added: ftbfs

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

Title:
  [regression] mir-client-platform-mesa-dev pkg-config file dropped

Status in Mir:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Released
Status in mesa source package in Wily:
  Confirmed
Status in mir source package in Wily:
  Confirmed
Status in xorg-server source package in Wily:
  Fix Committed

Bug description:
  the mir-client-platform-mesa-dev pkg-config file was dropped in wily,
  leading to build errors for such optional packages like mesa and xorg-
  server.

  Even if you have a feature freeze exception, you shouldn't break
  existing API's after feature freeze.

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

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

[Touch-packages] [Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports

Worked with-in Wily.

https://errors.staging.ubuntu.com/oops/0aa73368-8997-11e5-b0b0-fa163e1893a8

** Tags removed: verification-done-vivid 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1382233

Title:
  whoopsie does not upload UnreportableReason field in crash reports

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Precise:
  Invalid
Status in whoopsie-daisy source package in Precise:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in whoopsie source package in Vivid:
  Fix Committed
Status in whoopsie source package in Wily:
  Fix Committed

Bug description:
  Test Case
  -
  1) Edit a .crash file to have an UnreportableReason key and value e.g.
 UnreportableReason: Your system is weird.
  2) sudo service whoopsie stop
  3) start whoopsie pointing to errors.staging.ubuntu.com e.g.
 sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com 
APPORT_REPORT_DIR=/var/crash/ whoopsie -f
  4) Put said .crash file in /var/crash/
  5) Put a corresponding .upload file in /var/crash/
  6) Observe whoopsie uploading the .crash file from the whoopsie log
 [16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8
  7) go to errors.staging.ubuntu.com/oops/$OOPS_ID
  8) verify the UnreportableReason appears there e.g.:
 https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8

  
  In src/whoopsie.c we can see the following:

  /* We would only want this to see how many bugs would otherwise go
   * unreported: */
  "UnreportableReason",

  The comment isn't exactly true.  apport uses the UnreportableReason
  key to include the following information:

    "You have some obsolete package versions installed."

  It'd be useful if this information was sent to the Error Tracker so
  that we can decide not to ask for a core dump from these crash
  reports. The "obsolete package versions" check is done by checking to
  see if the most recent available version of the package is installed,
  so if someone does not have -updates enabled then that pocket is not
  checked and "obsolete package versions" will not be present. This is
  desirable because the retracers will check to see if the package
  version is available from any pocket.

  So if we send UnreportableReason to the Error Tracker we can stop
  asking for core dumps and retracing crashes that will fail to retrace.

  However, the value for UnreportableReason is translated so this may
  not end up helping much.

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

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

[Touch-packages] [Bug 1515821] [NEW] Recurring Evolution events not shown as coming events in clock's menu

2015-11-12 Thread Gunnar Hjalmarsson

Public bug reported:

In Evolution you can make an appointment recur according to a specified
scheme. As from wily, only the first instance of such a recurring event
is shown in the clock menu.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: wily

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

Title:
  Recurring Evolution events not shown as coming events in clock's menu

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  In Evolution you can make an appointment recur according to a
  specified scheme. As from wily, only the first instance of such a
  recurring event is shown in the clock menu.

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

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

[Touch-packages] [Bug 1514102] Re: Intermittent graphics corruption

Ian Bruntlett:

>"BTW, the PC in question was originally running (32 bit) Windows XP. As
we are experiencing problem with graphics when running 64 bit software,
perhaps I should install Lubuntu 15.10 i386 and see if that works?"

While you are welcome to do that as a test (as the release and
architecture are supported downstream via the L/Ubuntu Community), it
wouldn't be recommended to use a i386 architecture going forward as it
is deprecated upstream.

Despite this, Could you please test the latest upstream kernel available
from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this
report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

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

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

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

Title:
  Intermittent graphics corruption

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every so often the screen would be corrupted with horizontal lines of
  junk.

  WORKAROUND: Add to /etc/default/grub GRUB_CMDLINE_LINUX nomodeset:
  sudo update-grub
  reboot

  Now the system will only allow VGA 640x480 graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Nov  7 18:44:01 2015
  InstallationDate: Installed on 2015-11-07 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515793] [NEW] pythonX.Y autopkg tests failing

2015-11-12 Thread Matthias Klose

Public bug reported:

despite the fix for pythonX.Y packages as in
http://launchpadlibrarian.net/226135394/python3.5_3.5.0-3_3.5.0-3ubuntu1.diff.gz

pythonX.Y autopkg tests are still failing.

** Affects: python
 Importance: Unknown
 Status: Unknown

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: New

** Affects: python3.4 (Ubuntu)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: New

** Affects: python3.5 (Ubuntu)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: New

** Changed in: python2.7 (Ubuntu)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Also affects: python3.4 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python3.5 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python3.4 (Ubuntu)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: python3.5 (Ubuntu)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Bug watch added: Python Roundup #25613
   http://bugs.python.org/issue25613

** Also affects: python via
   http://bugs.python.org/issue25613
   Importance: Unknown
   Status: Unknown

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

Title:
  pythonX.Y autopkg tests failing

Status in Python:
  Unknown
Status in python2.7 package in Ubuntu:
  New
Status in python3.4 package in Ubuntu:
  New
Status in python3.5 package in Ubuntu:
  New

Bug description:
  despite the fix for pythonX.Y packages as in
  
http://launchpadlibrarian.net/226135394/python3.5_3.5.0-3_3.5.0-3ubuntu1.diff.gz

  pythonX.Y autopkg tests are still failing.

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

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

[Touch-packages] [Bug 1283426] Re: nautilus crashed with SIGSEGV in build_file_list_from_uris()

2015-11-12 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Unknown => Fix Released

** Changed in: nautilus
   Importance: Unknown => Medium

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

Title:
  nautilus crashed with SIGSEGV in build_file_list_from_uris()

Status in Nautilus:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Wily:
  Fix Committed

Bug description:
  I was trying to copy a file out of a VMware Player virtual Windows 7
  guest runnning in a window to nautilus, drag-and-dropping. The reverse
  operation (From nautilus to virtual machine's desktop) is executed
  fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 22 13:16:46 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-02-15 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x7f36910aa0b9:mov(%rdi),%rdi
   PC (0x7f36910aa0b9) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

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

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

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

2015-11-12 Thread Tony Espy

I just added tasks for the packages mentioned in comment #65.

Some things learned today:

 - the sub-component of QNetwork that's most likely the cause is called
Bearer Management.  One of it's classes, QNetworkSession includes a
plugin for NetworkManager which creates listeners for new AccessPoint
DBus objects.

 - msyncd ( part of buteo-syncfw ) includes it's own internal
NetworkManager class ( dated from 2010 ) which in turn uses
QNetworkSession.

 - unity8 appears to use QNetworkAccessManager, which uses
QNetworkSession.

 - sync-monitor uses QNetworkConfigurationManager, which is also part of
Bearer Management, and most likely causes a QNetworkSession to be
instantiated.

- maliit-framework is the only puzzle, as it doesn't seem to have any
network code.  It does use QGuiApplication however, which might in turn
hook into the network code.

 - the bulk of the code involved on the Qt side can be found in the
qtbase-opensource-base source package.

 - I'm no expert in QtDBus, but from what I can tell, to listen to a
DBus signal ( which causes a match rule to be created ), you need to
call connect on an instance of a DBusConnection, similar to what you'd
do with a native Qt signal and slot.  Conversely, to remove a signal
watch, you need to call the disconnect() function.

 - The connect to for a new new AccessPoint object can be found in
src/plugins/bearer/networkmanager/networkmanagerservice.cpp in the
funcion
QNetworkManagerInterfaceAccessPoint::QNetworkManagerInterfaceAccessPoint().

 - I don't see any corresponding cleanup code when an access point is
removed ( ie. there's no disconnect() call made to the bus )

That's all I have for now...

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

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

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  New
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

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

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

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

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

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

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

[Touch-packages] [Bug 1514102] Re: Intermittent graphics corruption

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

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

Title:
  Intermittent graphics corruption

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Every so often the screen would be corrupted with horizontal lines of
  junk.

  WORKAROUND: Add to /etc/default/grub GRUB_CMDLINE_LINUX nomodeset:
  sudo update-grub
  reboot

  Now the system will only allow VGA 640x480 graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Nov  7 18:44:01 2015
  InstallationDate: Installed on 2015-11-07 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1507298] Re: [wily] user-mounted FUSE filesystems won't unmount

2015-11-12 Thread Bug Watch Updater

Launchpad has imported 19 comments from the remote bug at
https://bugs.gentoo.org/show_bug.cgi?id=435540.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2012-09-19T19:07:04+00:00 Realnc wrote:

It is not possible to unmount FUSE filesystems as a normal user. I'm not
sure when this broke. It used to work correctly in the past.

For example:

  $ sshfs my.server.hostname: $HOME/mnt

That works.  But unmounting:

  $ umount $HOME/mnt
  umount: /home/realnc/mnt: umount failed: Operation not permitted

Trying with fusermount gives this:

  $ fusermount -u $HOME/mnt
  fusermount: entry for /home/realnc/mnt not found in /etc/mtab

However, /etc/mtab does contain an appropriate entry:

  my.server.hostname: /home/realnc/mnt fuse.sshfs rw,nosuid,nodev 0 0

The same thing also happens with NTFS-3G (which is also a FUSE
filesystem):

  $ mount /windows/D
  $ umount /windows/D
  umount: /windows/D: umount failed: Operation not permitted

This has repercussions on desktop environments as well. In KDE for
example, when I plug in an NTFS USB disk, it gets mounted OK. But it's
impossible to unmount it again from within KDE.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/0

On 2012-09-19T19:07:33+00:00 Realnc wrote:

Created attachment 324318
emerge --info

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/1

On 2012-09-19T19:29:00+00:00 Realnc wrote:

Forgot to mention the versions I tried:

2.8.7
2.9.0
2.9.1
2.9.1-r1

I think it's safe to say that it's not a change in fuse itself that
introduced this bug, but rather a change in some other package, since it
was definitely working OK with 2.9.0 at the time that it was the most
recent version.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/2

On 2012-09-19T20:24:54+00:00 Jrmalaq wrote:

Created attachment 324324
Output of "emerge --info"

I am having a similar problem on my ~amd64 system.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/3

On 2012-09-20T07:07:20+00:00 Helmut Jarausch wrote:

Created attachment 324362
emerge --info

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/4

On 2012-09-20T07:09:22+00:00 Helmut Jarausch wrote:

Same here with several versions of sys-fs/fuse  up to 2.9.1-r1
openssh-6.1_p1

sshfs-fuse 2.4 and sshfs-fuse GIT

IHMO, the severity should be raised to 'major' since it breaks daily 
backup services here.

Helmut.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/5

On 2012-09-20T13:52:00+00:00 Göktürk Yüksek wrote:

Does putting something like this in /etc/fstab help?
  sshfs#my.server.hostname:$HOME /mnt fuse 
rw,user,noauto,fsname=sshfs#my.server.hostname:$HOME,reconnect  0 0

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/6

On 2012-09-20T14:41:28+00:00 Realnc wrote:

(In reply to comment #6)
> Does putting something like this in /etc/fstab help?
>   sshfs#my.server.hostname:$HOME /mnt fuse
> rw,user,noauto,fsname=sshfs#my.server.hostname:$HOME,reconnect  0 0

mount: /etc/fstab: parse error: ignore entry at line 8.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/7

On 2012-09-20T16:04:15+00:00 Helmut Jarausch wrote:

(In reply to comment #6)
> Does putting something like this in /etc/fstab help?
>   sshfs#my.server.hostname:$HOME /mnt fuse
> rw,user,noauto,fsname=sshfs#my.server.hostname:$HOME,reconnect  0 0

With an entry like

sshfs#jarausch@WWW_SV:/srv/www/htdocs   /usr/WWW  fuse
noauto,users,uid=230,gid=100,umask=0  0 0   # ,allow_other

I just get the same error message, i.e.

fusermount: entry for /usr/WWW not found in /etc/mtab

cat /etc/mtab :
jarausch@WWW_SV:/srv/www/htdocs /usr/WWW fuse.sshfs rw,nosuid,nodev,noexec 0 0

Helmut.

Reply at: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1507298/comments/8

On 2012-09-20T16:18:51+00:00 OliFre wrote:

I have a machine at hand that had a folder mounted BEFORE it broke, is
still

[Touch-packages] [Bug 1500918] Re: rc-proposed location is way out in comparison to ota6

2015-11-12 Thread Dave Morley

This seems to be fixed with the recent landing for OTA8

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

Title:
  rc-proposed location is way out in comparison to ota6

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  DESCRIPTION:
  Ota 6 accurately positions me on the wednesfield road in rc-proposed it is 
positioning me in Mount Road this is approximately 11 miles across town.

  STEPS:
  1. install rc-proposed
  2. Open locations or pull down on the nearby scope

  EXPECTED:
  I expect rc-proposed to match ota6

  ACTUAL:
  The positioning is approximately 11 miles out

  https://goo.gl/maps/RZ5K3EzhG262

  VERSIONS:
  current build number: 525
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed
  last update: 2015-09-29 14:44:52
  version version: 525
  version ubuntu: 20150929
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This equates to Image 135 on rc-proposed + custom tarball

  Also is the same on Arale with custom tarball and confirmed on:

  current build number: 124
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-29 15:20:36
  version version: 124
  version ubuntu: 20150929
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

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

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

[Touch-packages] [Bug 1311362] Re: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)

2015-11-12 Thread ML

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

** This bug has been marked a duplicate of bug 1361207
   nvidia-graphics-drivers-* should recommend nvidia-modprobe

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

Title:
  Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  ** Steps to Reproduce: **
  1. Perform a fresh installation of Ubuntu Gnome 14.04 64-bit on a clean PC
  2. Using the "Additional Drivers" application, install latest NVidia driver 
(331)
  3. Reboot
  4. Install latest Darktable (1.4) from Ubuntu's repositories
  5. In Terminal, run "darktable -d opencl"

  ** Actual Result: **
  In Ubuntu Gnome 14.04, using the NVidia 331 driver, Darktable won't run with 
OpenCL support. The following debug output is observed in the terminal:

  [opencl_init] opencl related configuration options:
  [opencl_init]
  [opencl_init] opencl: 1
  [opencl_init] opencl_library: ''
  [opencl_init] opencl_memory_requirement: 768
  [opencl_init] opencl_memory_headroom: 300
  [opencl_init] opencl_device_priority: '*/!0,*/*/*'
  [opencl_init] opencl_size_roundup: 16
  [opencl_init] opencl_async_pixelpipe: 0
  [opencl_init] opencl_synch_cache: 0
  [opencl_init] opencl_number_event_handles: 25
  [opencl_init] opencl_micro_nap: 1000
  [opencl_init] opencl_use_pinned_memory: 0
  [opencl_init] opencl_use_cpu_devices: 0
  [opencl_init] opencl_avoid_atomics: 0
  [opencl_init] opencl_omit_whitebalance: 0
  [opencl_init]
  [opencl_init] trying to load opencl library: ''
  [opencl_init] could not find opencl runtime library 'libOpenCL'
  [opencl_init] no working opencl library found. Continue with opencl disabled
  [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
  [opencl_init] initial status of opencl enabled flag is OFF.
  [pixelpipe_process] [thumbnail] using device -1
  [pixelpipe_process] [thumbnail] using device -1

  ** Expected Result: **
  Software using OpenCL should continue to work as it did in Ubuntu 13.10.

  ** Notes: **
  Graphics card: GeForce GTX 680 (Gigabyte GV-N680OC-2GD)
  Encuontered on Ubuntu Gnome 14.04, 64 bit.
  Likely occurs on regular Ubuntu (not Ubuntu Gnome) as well.
  This issue also occurs when running NVidia 331 Update, NVidia Legacy 304 as 
well as Nouveau.
  This issue did not occur on Ubuntu Gnome 13.10.
  Bug filed in Darktable: 
http://www.darktable.org/redmine/issues/9913#change-24936

  ** Troubleshooting: **
  The following files and directories relating to OpenCL were found on the test 
system:

  locate -i libopencl
  /usr/lib/i386-linux-gnu/libOpenCL.so.1
  /usr/lib/i386-linux-gnu/libOpenCL.so.1.0
  /usr/lib/i386-linux-gnu/libOpenCL.so.1.0.0
  /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
  /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0
  /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0
  /usr/share/doc/nvidia-libopencl1-331
  /usr/share/doc/nvidia-libopencl1-331/changelog.Debian.gz
  /usr/share/doc/nvidia-libopencl1-331/copyright
  /var/cache/apt/archives/nvidia-libopencl1-331_331.38-0ubuntu7_amd64.deb
  /var/lib/dpkg/info/nvidia-libopencl1-331.list
  /var/lib/dpkg/info/nvidia-libopencl1-331.md5sums
  /var/lib/dpkg/info/nvidia-libopencl1-331.postinst
  /var/lib/dpkg/info/nvidia-libopencl1-331.postrm
  /var/lib/dpkg/info/nvidia-libopencl1-331.shlibs

  installed the packages "opencl-headers" and "nvidia-profiler", but that made 
no difference.
  Manually edited /etc/ld.so.conf to include the directories found containing 
the OpenCL libraries (from the list above). Ran ldconfig. No difference.

  Output of clinfo:

  clinfo: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: no version information 
available (required by clinfo)
  E: -30

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Apr 22 17:59:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00

[Touch-packages] [Bug 1515593] [NEW] head.foregroundColor does not affect icons in the header

2015-11-12 Thread Michal Predotka

Public bug reported:

According to the documentation of PageHeadConfiguration ( 
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.PageHeadConfiguration
 ) property "foregroundColor" should change the color of the text and icons. 
Unfortunately it only affects the page title and not icons. Screenshot attached.
Sample code:

import QtQuick 2.4
import Ubuntu.Components 1.3

Page {
id: root_about

title: "Test page"

head.foregroundColor: "red"
head.actions: [
Action {
iconName: "camcorder"
},
Action {
iconName: "info"
}
]
}

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

** Attachment added: "screenshot20151112_120353158.png"
   
https://bugs.launchpad.net/bugs/1515593/+attachment/4517520/+files/screenshot20151112_120353158.png

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

Title:
  head.foregroundColor does not affect icons in the header

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

Bug description:
  According to the documentation of PageHeadConfiguration ( 
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.PageHeadConfiguration
 ) property "foregroundColor" should change the color of the text and icons. 
  Unfortunately it only affects the page title and not icons. Screenshot 
attached.
  Sample code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Page {
  id: root_about

  title: "Test page"

  head.foregroundColor: "red"
  head.actions: [
  Action {
  iconName: "camcorder"
  },
  Action {
  iconName: "info"
  }
  ]
  }

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

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

[Touch-packages] [Bug 1513918] Re: Improve the algorithm for top sites

2015-11-12 Thread Olivier Tilloy

I agree that the current implementation is a bit naïve: top sites are
the first ten sites ordered by decreasing number of visits.

There is also the problem with not being able to undo the removal of a
top site (there’s no UI for that).

Adding an ubuntu-ux task, as we need design input here.

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Improve the algorithm for top sites

Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  It seems that we show pages that have been visited even once up to a
  total of 10. I noticed when removing some pages from top sites that an
  unlimited supply kept the total at 10, but many of these were pages I
  visited once and would never use again.

  It does seem on  first use you would want to show some number of pages
  even if they are only viewed once, but once the user establishes which
  pages they view multiple times those should allow us to ignore single
  visits. Firefox doesn't start to show "tiles" for most visited sites
  for 30 days acc to
  https://blog.mozilla.org/advancingcontent/2014/02/13/more-details-on-
  directory-tiles/

  I was removing sites that did not have thumbnails , unfortunately I
  thin this means they will ever again show up in the top sites. Not
  sure if permanent removal is what is desired, I can see it either way.

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

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

[Touch-packages] [Bug 1515615] [NEW] Disk quotas don't work in LXC containers

2015-11-12 Thread Anton Statutov

Public bug reported:

I'm trying to enable disk quotas in LXC container by adding option to its 
config:
lxc.rootfs.options = usrquota

After booting the container I'm trying to initialize quotas but getting
the following error:

r...@test.lxc:~# quotacheck -gum /
quotacheck: Cannot stat() mounted device /dev/lxc/test: No such file or 
directory
quotacheck: Mountpoint (or device) / not found or has no quota enabled.
quotacheck: Cannot find filesystem to check or filesystem not mounted with 
quota option.


Host OS: Ubuntu 15.04
Guest OS: Ubuntu 14.04.3 LTS

lxc 1.1.2-0ubuntu3.2

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

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

Title:
  Disk quotas don't work in LXC containers

Status in lxc package in Ubuntu:
  New

Bug description:
  I'm trying to enable disk quotas in LXC container by adding option to its 
config:
  lxc.rootfs.options = usrquota

  After booting the container I'm trying to initialize quotas but
  getting the following error:

  r...@test.lxc:~# quotacheck -gum /
  quotacheck: Cannot stat() mounted device /dev/lxc/test: No such file or 
directory
  quotacheck: Mountpoint (or device) / not found or has no quota enabled.
  quotacheck: Cannot find filesystem to check or filesystem not mounted with 
quota option.

  
  Host OS: Ubuntu 15.04
  Guest OS: Ubuntu 14.04.3 LTS

  lxc 1.1.2-0ubuntu3.2

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

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

[Touch-packages] [Bug 1505995] Re: Support HTTPS in webbrowser-app autopilot test suite

2015-11-12 Thread Olivier Tilloy

Bumped the importance to high as the following test is now failing with
oxide 1.11 (to be released soon):

webbrowser_app.tests.test_media_access_permission.TestMediaAccessPermission.test_deny

The message we’re getting from oxide is:

[JS] (:0) getUserMedia() no longer works on insecure origins. To use
this feature, you should consider switching your application to a secure
origin, such as HTTPS. See https://goo.gl/rStTGz for more details.


** Changed in: webbrowser-app (Ubuntu)
   Importance: Medium => High

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

Title:
  Support HTTPS in webbrowser-app autopilot test suite

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  The webbrowser-app autopilot test suite currently uses a test HTTP
  server. In the near future, it will need to gain support for HTTPS for
  some tests (e.g. those that embed getUserMedia() calls in HTML):

  [JS] (:0) getUserMedia() is deprecated on insecure origins, and
  support will be removed in the future. You should consider switching
  your application to a secure origin, such as HTTPS. See
  https://goo.gl/rStTGz for more details.

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

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

[Touch-packages] [Bug 1509423] Re: cupsd on the phone is unable to run sub processes, they all cause "Command not found"

This bug was fixed in the package cups - 2.1.0-6

---
cups (2.1.0-6) unstable; urgency=medium

  [ Till Kamppeter ]
  * Move /usr/lib/cups/daemom/cups-exec from the "cups" binary package to the
"cups-daemon" binary package as it is already needed for basic job
execution and therefore already in the level-1 (minimum) printing stack
(LP: #1509423)

 -- Didier Raboud   Fri, 06 Nov 2015 17:09:44 +0100

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

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

Title:
  cupsd on the phone is unable to run sub processes, they all cause
  "Command not found"

Status in Canonical System Image:
  Invalid
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  I have started to test the printing stack of Ubuntu on the phone.

  I have a Nexus 4 now to test the printing stack on the phone.

  First I have updated the USB-connected phone to the development branch
  of the OS via

  ubuntu-device-flash touch --channel=devel

  with the phone booted into Ubuntu and the screen unlocked.

  After the reboot of the phone I have run

  phablet-config writable-image

  to be able to install packages with apt-get and entered a shell on the
  phone via

  phablet-shell

  In the shell I first installed a level-1 printing stack (See
  https://blueprints.launchpad.net/ubuntu/+spec/client-1305-printing-
  stack-with-mobile-in-mind for the levels):

  sudo apt-get install cups-daemon cups-browsed avahi-daemon

  This makes the following new packages getting installed:

  The following NEW packages will be installed:
avahi-daemon bc bind9-host cups-browsed cups-daemon libavahi-core7
libavahi-glib1 libbind9-90 libcupsmime1 libdaemon0 libdns100 libgeoip1
libisc95 libisccc90 libisccfg90 liblwres90 libpaper1 ssl-cert
  0 upgraded, 18 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,502 kB of archives.
  After this operation, 4,698 kB of additional disk space will be used.

  The installation was hanging on the postinst of CUPS, so I had to open
  a new shell in another terminal and kill the postinst for the
  installation process to finish.

  sudo apt-get install -f

  has re-run the CUPS postinst and this time it finished.

  As the phone apps do not yet have a print dialog I needed a print
  client on the phone, and also some tools for developing and debugging.
  So I have installed cups-client, giving me command line printing and
  print admin commands, as lp, lpstat, lpinfo, lpadmin, ...:

  sudo apt-get install cups-client
  [...]
  The following NEW packages will be installed:
cups-client cups-common libcupsfilters1 libcupsimage2
  0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
  Need to get 368 kB of archives.
  After this operation, 2,810 kB of additional disk space will be used.

  PID 1 on the phone is still Upstart, Upstart is configured to start
  CUPS on-demand, via

  /etc/init/cups.override

  cups.override needs to be corrected, as cupsd does not support the
  "-x" option any more, so I have removed the "-x 30" from the cupsd
  command line. Now cupsd starts when running commands like

  lpstat -r
  lpstat -v
  ...

  After that I did

  sudo start cups-browsed

  to start cups-browsed to get the queues from remote CUPS servers
  locally available (level 1 printing stack).

  lpstat -v

  shows my printers shared on remote CUPS servers now.

  Note that CUPS admin tasks need "sudo" as the "phablet" user is not in
  the "lpadmin" group.

  For the printing tests I do the CUPS logging (in
  /var/log/cups/error_log) in debug mode, running

  sudo cupsctl --debug-logging

  sudo cupsctl

  shows my settings.

  Now I print via

  lp -d printer ~/.bashrc

  CUPS is now supposed to send the job via IPP (Internet Printing
  Protocol) to the remote CUPS server where the printer is actually
  connected to. This it does using a backend, a small helper program, in
  our case /usr/lib/cups/backend/ipps.

  Printing does not work yet:

  1. CUPS reports exit status 127 on the ipps backend call ("command not
  found", the fact that in error_log you see "file too large" is a CUPS
  bug, exit status 127 is "command not found"), but the backend is
  called with its full path, the backend is actually present and
  executable, no libs missing (checked with "ldd"), the backend works
  directly called from the command line.

  2. No name resolution in the local network (avahi problem? avahi-
  daemon is running). Manual call of the backend only works if the host
  name in the device URI is replaced by the corresponding IP address.

  So following command prints:

  DEVICE_URI=ipps://192.168.0.11:631/printers/printer
  CONTENT_TYPE=text/plain /usr/lib/cups/backend/ipps 1 1 1 1 ""
  ~/.bashrc

  Also

  sudo

[Touch-packages] [Bug 1513856] Re: [3.18] 'save changes' dialog button style is wrong

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

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

Title:
  [3.18] 'save changes' dialog button style is wrong

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Using 3.18 on xenial, the buttons in the dialog asking if you want to
  save work when closing gedit look weird, we should fix that

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

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

[Touch-packages] [Bug 1515461] Re: Open menu dropdown is 'compressed' & unintelligible

Doesn't happen with Adwaita, probably something that can be fixed in the
theme

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

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

Title:
  Open menu dropdown is 'compressed' & unintelligible

Status in gedit package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Did not happen with initial upgrade to gedit-3.18 but showed up with some 
subsequent updates of other packages.
  (may be able to track down by manually parsing synaptic's history logs
  Please see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 21:05:08 2015
  InstallationDate: Installed on 2015-10-25 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515551] [NEW] Several laptops unstable with 15.10 kernels

2015-11-12 Thread janl

Public bug reported:

After upgrading my two laptops (HP EliteBook 8470p, Sony Vaio, both
several years old) to 15.10 both started freezing within 12 hours of
booting and the screens started flickering when X did fade-out and fade-
ins.

Booting the HP with the 15.04 kernel (3.19.0-31) makes it stable again.
The sony vaoi was downgraded to 14.04 and is stable there.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Nov 12 11:34:25 2015
InstallationDate: Installed on 2013-11-07 (734 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to wily on 2015-10-26 (16 days ago)

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


** Tags: amd64 apport-bug kubuntu wily

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

Title:
  Several laptops unstable with 15.10 kernels

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading my two laptops (HP EliteBook 8470p, Sony Vaio, both
  several years old) to 15.10 both started freezing within 12 hours of
  booting and the screens started flickering when X did fade-out and
  fade-ins.

  Booting the HP with the 15.04 kernel (3.19.0-31) makes it stable
  again. The sony vaoi was downgraded to 14.04 and is stable there.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 11:34:25 2015
  InstallationDate: Installed on 2013-11-07 (734 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-10-26 (16 days ago)

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

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

[Touch-packages] [Bug 1515561] Re: Windows flash black briefly before being drawn

2015-11-12 Thread Bug Watch Updater

** Changed in: gtk
   Status: Unknown => Confirmed

** Changed in: gtk
   Importance: Unknown => Low

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

Title:
  Windows flash black briefly before being drawn

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Since 3.18, windows flash black for a split second before they are
  drawn. It's visually disruptive.

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

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

[Touch-packages] [Bug 1515569] [NEW] /lib/systemd/systemd-logind:7:siphash24_compress:base_bucket_hash:hashmap_put:add_object_vtable_internal:manager_startup

2015-11-12 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding systemd.  This problem was most recently seen with version
227-2ubuntu1, the problem page at
https://errors.ubuntu.com/problem/40601234918498089c81001cd7b6a7f06bf12fe7
contains more details.

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


** Tags: xenial

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

Title:
  /lib/systemd/systemd-
  
logind:7:siphash24_compress:base_bucket_hash:hashmap_put:add_object_vtable_internal:manager_startup

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  227-2ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/40601234918498089c81001cd7b6a7f06bf12fe7
  contains more details.

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

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

[Touch-packages] [Bug 1514102] Re: Intermittent graphics corruption

Ian Bruntlett, please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

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

Title:
  Intermittent graphics corruption

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Every so often the screen would be corrupted with horizontal lines of
  junk.

  WORKAROUND: Add to /etc/default/grub GRUB_CMDLINE_LINUX nomodeset:
  sudo update-grub
  reboot

  Now the system will only allow VGA 640x480 graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Nov  7 18:44:01 2015
  InstallationDate: Installed on 2015-11-07 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2015-11-12 Thread Michi Henning

** Summary changed:

- Redunt requests for artist art
+ Redundant requests for artist art

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

Title:
  Redundant requests for artist art

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1513856] Re: [3.18] 'save changes' dialog button style is wrong

Maybe we could theme these to look nice instead?

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [3.18] 'save changes' dialog button style is wrong

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Using 3.18 on xenial, the buttons in the dialog asking if you want to
  save work when closing gedit look weird, we should fix that

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

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

[Touch-packages] [Bug 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear

2015-11-12 Thread Alexandros Frantzis

More evidence that this is a problem at a level below either USC or
powerd:

0. Build a test program to use and print out events from ubuntu application 
proximity sensor api (you can use [1] as a starting point, just remove other 
sensors to reduce irrelevant messages).
1. Use "tail -F /var/log/syslog" to follow powerd messages
2. Start a phone call
3. Start the test program (the one built in step (0))
4. Cover/uncover the proximity sensor, note the powerd output in syslog and the 
test program output
5. Continue covering/uncovering, at some point (you need to be patient) powerd 
will stop reacting to proximity events (the screen won't turn on/off). Note how 
at this point (a) there is no powerd output as a response to proximity in 
syslog (b) there *are* kernel message about proximity near/far in syslog (c) 
the test program has also stopped reacting to proximity events (i.e. the sensor 
api has stopped calling the event callback)

The observed behavior strongly indicates that this is a problem at a
layer below powerd. If it was just a powerd issue the test program would
continue responding to proximity events.

Note, however, that I haven't been able to reproduce this problem with
just the test program running. This suggests (but it's just a
speculation at this point) that some additional interaction in powerd
(screen on/off?, suspending?) triggers the problem at the lower levels,
or at least makes the problem more likely to occur.

[1] https://bazaar.launchpad.net/~phablet-team/platform-
api/trunk/view/head:/examples/test_sensors_api.cpp

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

Title:
  Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you
  remove the phone from your ear

Status in Canonical System Image:
  Confirmed
Status in powerd package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I have a problem with my Meizu MX4 (Arale r6). 
  During a call if you remove the phone from your ear, sometimes (not always) 
the screen remains turned off. When you try to push the power button to wake up 
the screen, that starts blinking and it's not possible to hang up. The screen 
remains in that condition even after the end of the call.
  When it keeps blinking I try to hold the button down and in few seconds the 
screen turns black and the phone starts working again. Sometimes, instead, it 
starts working again by itself.

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

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

[Touch-packages] [Bug 1513966] Re: /usr/sbin/NetworkManager:11:nm_device_uses_assumed_connection:_set_state_full:link_timeout_cb:g_timeout_dispatch:g_main_context_dispatch

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  
/usr/sbin/NetworkManager:11:nm_device_uses_assumed_connection:_set_state_full:link_timeout_cb:g_timeout_dispatch:g_main_context_dispatch

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.0.4-0ubuntu6, the problem page at
  https://errors.ubuntu.com/problem/6b985f06e315f8ca002e2f4b462d73123bbb89ff
  contains more details.

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

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

[Touch-packages] [Bug 1515512] Re: upower.service fails with core dumps

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  upower.service fails with core dumps

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  The upower service is crashing at startup.

  
  Nov 12 09:15:49 next systemd[1]: Starting Daemon for power management...
  Nov 12 09:15:49 next systemd[1]: Started Daemon for power management.
  Nov 12 09:15:51 next usbmuxd[16099]: [09:15:51.475][1] 
config_get_device_record: failed to read 
'/var/lib/lockdown/c7ccdf3c1bfcdca6e52320fb51f1fe238a1
  31ca3.plist': No such file or directory
  Nov 12 09:15:52 next kernel: [ 5456.001802] traps: upowerd[6635] general 
protection ip:7f8b785d31cb sp:7ffd6259bbc0 error:0 in libc-2.21.so[7f8b785540
  00+1c]
  Nov 12 09:15:52 next systemd[1]: upower.service: Main process exited, 
code=dumped, status=11/SEGV
  Nov 12 09:15:52 next systemd[1]: upower.service: Unit entered failed state.
  Nov 12 09:15:52 next systemd[1]: upower.service: Failed with result 
'core-dump'.
  Nov 12 09:15:52 next systemd[1]: upower.service: Service hold-off time over, 
scheduling restart.
  Nov 12 09:15:52 next systemd[1]: Stopped Daemon for power management.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: upower 0.99.3-1build2
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Thu Nov 12 09:14:36 2015
  InstallationDate: Installed on 2012-10-15 (1122 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121014)
  SourcePackage: upower
  UpgradeStatus: Upgraded to wily on 2015-11-02 (9 days ago)

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

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

[Touch-packages] [Bug 1515461] Re: Open menu dropdown is 'compressed' & unintelligible

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

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Medium => High

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

Title:
  Open menu dropdown is 'compressed' & unintelligible

Status in gedit package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Did not happen with initial upgrade to gedit-3.18 but showed up with some 
subsequent updates of other packages.
  (may be able to track down by manually parsing synaptic's history logs
  Please see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 21:05:08 2015
  InstallationDate: Installed on 2015-10-25 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1513856] Re: [3.18] 'save changes' dialog button style is wrong

** Tags added: gtk318

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

Title:
  [3.18] 'save changes' dialog button style is wrong

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Using 3.18 on xenial, the buttons in the dialog asking if you want to
  save work when closing gedit look weird, we should fix that

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

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

[Touch-packages] [Bug 1515461] Re: Open menu dropdown is 'compressed' & unintelligible

** Tags added: gtk318

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

Title:
  Open menu dropdown is 'compressed' & unintelligible

Status in gedit package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Did not happen with initial upgrade to gedit-3.18 but showed up with some 
subsequent updates of other packages.
  (may be able to track down by manually parsing synaptic's history logs
  Please see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 21:05:08 2015
  InstallationDate: Installed on 2015-10-25 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515561] [NEW] Windows flash black briefly before being drawn

Public bug reported:

Since 3.18, windows flash black for a split second before they are
drawn. It's visually disruptive.

** Affects: gtk
 Importance: Unknown
 Status: Unknown

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gtk318

** Bug watch added: GNOME Bug Tracker #748498
   https://bugzilla.gnome.org/show_bug.cgi?id=748498

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=748498
   Importance: Unknown
   Status: Unknown

** Tags added: gtk318

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

Title:
  Windows flash black briefly before being drawn

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Since 3.18, windows flash black for a split second before they are
  drawn. It's visually disruptive.

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

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

[Touch-packages] [Bug 1515561] Re: Windows flash black briefly before being drawn

Someone posted a video on the linked bug
https://bugzilla.gnome.org/attachment.cgi?id=302400

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

Title:
  Windows flash black briefly before being drawn

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Since 3.18, windows flash black for a split second before they are
  drawn. It's visually disruptive.

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

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

[Touch-packages] [Bug 1515557] Re: Sidebars have too little padding

** Attachment added: "adwaita"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1515557/+attachment/4517480/+files/chooser-adwaita.png

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Tags added: gtk318

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

Title:
  Sidebars have too little padding

Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  You can see this in either Nautilus or a GtkFileChooserDialog
  (screenshot attached).

  It looks to me that the padding is too small - the items are up
  against the left and top edge. I attached another screenshot under
  Adwaita where they are more spaced out, which looks better to me.

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

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

[Touch-packages] [Bug 1515557] [NEW] Sidebars have too little padding