[Touch-packages] [Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0

2014-12-16 Thread Steffen Neumann
Affected here too after creating a new key in ~/.ssh, this is 14.04 with
all updates as of today.

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

Title:
  SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't
  use key auth without SSH_AUTH_SOCK=0

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I expect that when using key based authentication I do $ssh user@0.0.0.0 I 
expect to be asked for the key password.  Instead I get Agent admitted failure 
to sign using the key.
  Permission denied (publickey).

  Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for
  the key password.

  What should happen is that I should not have to specify
  SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Oct 11 07:19:08 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-08 (33 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1402962] Re: qtpim fails to build against Qt 5.4.0 on i386 and arm64

2014-12-16 Thread Timo Jyrinki
Correction: I built qtpim both in a 3-arch PPA (armhf i386 amd64) and
6-arch PPA (additionally powerpc arm64 ppc64el), and interestingly the
same problem happens on arm64 too:
https://launchpadlibrarian.net/192757969/buildlog_ubuntu-vivid-arm64
.qtpim-opensource-
src_5.0~git20140515~29475884-0ubuntu6~vivid1~test1_FAILEDTOBUILD.txt.gz

arm64 and i386 don't have much anything in common, but at least the
problem does not happen on just one architecture.

** Summary changed:

- qtpim fails to build against Qt 5.4.0 on i386
+ qtpim fails to build against Qt 5.4.0 on i386 and arm64

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

Title:
  qtpim fails to build against Qt 5.4.0 on i386 and arm64

Status in qtpim-opensource-src package in Ubuntu:
  New

Bug description:
  qtpim seems to fail to build against Qt 5.4.0 on i386. It succeeds on
  all other arches.

  ---
  In file included from qorganizerrecurrencerule.cpp:42:0:
  qorganizerrecurrencerule.h:153:1: error: expected constructor, destructor, or 
type conversion before 'Q_DECLARE_METATYPE'
   
Q_DECLARE_METATYPE(QSetQTORGANIZER_PREPEND_NAMESPACE(QOrganizerRecurrenceRule))
   ^
  ---

  The whole build log: https://launchpadlibrarian.net/192757256
  /buildlog_ubuntu-vivid-i386.qtpim-opensource-
  src_5.0~git20140515~29475884-0ubuntu6~vivid1~test1_FAILEDTOBUILD.txt.gz

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

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

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


[Touch-packages] [Bug 1319146] Re: new installation of 14.04LTS, no panel or launcher

2014-12-16 Thread Andrea Azzarone
Run the command on Unity:

ps aux | grep nautilus

and

gsettings get org.gnome.desktop.background show-desktop-icons

and post the output of both.

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

Title:
  new installation of 14.04LTS, no panel or launcher

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  In reference to bug # 2304568, lost launcher and panel in 14.04LTS
  Beta2,

  I ended up sending the motherboard for repairs.  This has been
  repaired and installed as of today.  I also installed a brand new
  120GB SSD upon which I installed a newly downloaded version od
  14.04LTS.  I kept my /home on another drive, but for that it is
  essentially a new installation.  System started, asked for password
  and at that time the panel was visible with date, time and the
  shutdown button.  After entering password system came up without
  launcher and also without panel.  I changed density on the screen just
  incase launcher was off the screen, no luck.

  This now has become a serious problem, as I cannot acces any of the
  files on my hard diks, nor can I use this system for any work.

  I also do not know how I can send any bug info other than this
  description, I have no access to Terminal, only all settings is
  available and all icons do their job when requested.

  I would really appreciate it if this were looked in quickly.
  ---
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2014-05-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. B85-HD3
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=6a5180e0-a20b-4d2e-8d18-f6b95e329bd7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Tags:  trusty trusty trusty ubuntu
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B85-HD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May 13 13:38:58 2014
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Touch-packages] [Bug 1161317] Re: gvfsd-http could handle high traffic better

2014-12-16 Thread Andrea Azzarone
*** This bug is a duplicate of bug 760344 ***
https://bugs.launchpad.net/bugs/760344

** This bug has been marked a duplicate of bug 760344
   gvfsd-http not closing tcp connections

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

Title:
  gvfsd-http could handle high traffic better

Status in Unity:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in gvfs source package in Saucy:
  Won't Fix
Status in unity source package in Saucy:
  Invalid

Bug description:
  Running the new unity-scopes ppa it's easy to make gvfsd-http increase
  memory usage and keep a stack of open connections, we should make sure
  we don't leak memory/fds there

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

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


[Touch-packages] [Bug 1395661] Re: Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

2014-12-16 Thread Timo Jyrinki
Harald looked at the problem a bit:
 sitter Mirv: ah, fwiw, I think I found the cause of the broken pch 
http://paste.ubuntu.com/9537448/ for some reason that doesn't get reported with 
the 3 million arguments used in the build normally
 sitter also for good measure I was unable to find any other build log 
anywhere on the internet that also used pch for Qt5WebKitWidgets, perhaps the 
problem is that suddenly it started to precompile for us ^^

Looking at 5.3.2 logs, pch does not seem to be enabled with qtwebkit
over there.

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

Title:
  Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  There's a problem with Qt WebKit (5.4.0 beta) failing to build against
  Qt 5.4.0 beta on amd64: https://launchpadlibrarian.net/190809157
  /buildlog_ubuntu-vivid-amd64.qtwebkit-opensource-src_5.4.0~beta-
  0ubuntu1~vivid1~test1_FAILEDTOBUILD.txt.gz and on powerpc:
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-005/+build/6649444/+files
  /buildlog_ubuntu-vivid-powerpc.qtwebkit-opensource-
  src_5.4.0-0ubuntu1%7Evivid1%7Etest2_FAILEDTOBUILD.txt.gz

  It seems to be related to pre-compiled headers. Qttools requires
  qtwebkit for the documentation. In the test PPA I've disabled qttools'
  qtwebkit requirement in order to have more amd64 builds done in
  general.

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

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

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


[Touch-packages] [Bug 1376250] Re: i-network says Unknown or No SIM on N4 (mako), can't unlock the SIM

2014-12-16 Thread Antti Kaijanmäki
seems to have been an ofono issue.

** Changed in: indicator-network
   Status: Incomplete = Invalid

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  i-network says Unknown or No SIM on N4 (mako), can't unlock the
  SIM

Status in Network Menu:
  Invalid
Status in indicator-network package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu RTM:
  Triaged

Bug description:
  noticed that i-network is broken on mako. Sometimes after reboot the
  indicator says the modem state is either Unknown or No Sim even
  though the SIM is present.

  for now the workarounds are:

  If developer mode is not enabled:
   - reboot the phone until you can enter the PIN

  if developer mode is enabled:
  $ adb shell
  $ restart indicator-network

  # system-image-cli -i
  current build number: 264
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-10-01 11:13:57
  version version: 264
  version ubuntu: 20141001
  version device: 20140929.1
  version custom: mako-0.6

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

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


[Touch-packages] [Bug 1081022] Re: logging.SysLogHandler doesn't close UNIX socket when connection failed

2014-12-16 Thread James Page
Looks like this is not actually fixed release - setting back to new.

** Changed in: python2.7 (Ubuntu Precise)
   Status: Fix Released = New

** Changed in: python2.7 (Ubuntu Precise)
   Importance: Undecided = High

** Tags added: mos

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

Title:
  logging.SysLogHandler doesn't close UNIX socket when connection failed

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Precise:
  New

Bug description:
  Python logging SysLogHandler to log into SysLog doesn't close UNIX-socket
  when connection failed. This bug is solved on the Python Issue Tracker at
  http://bugs.python.org/issue15179 and affects python package with version
  2.7.3-0ubuntu2 at Ubuntu 12.04 LTS.

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

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


[Touch-packages] [Bug 538673] Re: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down

2014-12-16 Thread Usul_
Same thing here. Ubuntu Gnome 14.10 64 bit on an Asus P301LA notebook with 4 GB 
RAM. 
After login in gnome shell the system is very unresponsive for many minutes. 
After a while, usually, tracker-miner crashes and the systems goes back to 
normal behaviour.
Apport says: tracker-extract crashed with SIGABRT in g_malloc0().

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

Title:
  tracker-extract seems to briefly consume 1.5GB memory and slow
  computer right down

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: tracker

  In normal operation of computer, very occasionally computer suddenly
  slows right down for about 45 seconds - mousepointer is very slow to
  respond to movement, and windows are too slow to respond to clicks.

  This has been hard to identify the cause because the computer is so
  slow to respond it's hard to get system monitor opened to see the
  offending process.  Anyway I've finally managed to view system-monitor
  within the 45 seconds, and it seems to be tracker-extract program
  that is responsible, that was consuming over 1.5GB of RAM on my
  machine.  It was hard to see though because the 45 seconds finished
  almost as soon as I'd viewed it, so it very quickly disappeared from
  the top of the process list when ranked by memory usage.

  So is tracker-extract the offending process?  Can it be made a
  little less hungry of Memory (+ CPU) please?

  I'm using Ubuntu 9.10 (karmic) 64 bit version on a 2.9GB machine.

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

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


[Touch-packages] [Bug 1245951] Re: Wrong oFono property used for data technology indication

2014-12-16 Thread Antti Kaijanmäki
I went through the barajas bugs, but can't find a clear dup. John, could
you attach a bug number?

The only situation when the Technology and the Bearer properties differ
is when the mobile broadband connection speed is limited by the operator
to be _lower_ than the cellular networks normal technology; voice might
go through 3G but mobile data is limited to 2G. So the user gets a lower
internet connection speed than actually reported by the indicator.

Then on the other hand, even though if the user has an actual 3G or even
4G mobile broadband connection the actual data transfer speeds sometimes
drop to the equivalent levels of 2G connections depending on the loads
on the carrier network, so the whole icon is more or less a hint of the
ideal connection speeds you _might_ get. Sadly for the customers there
are no  definitive requirements for the carriers on minimum throughput.

Anyway, that is a real bug, but there should be no surprises for the
user in terms of billing. Hence Medium.

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

Title:
  Wrong oFono property used for data technology indication

Status in the base for Ubuntu mobile products:
  New
Status in Network Menu:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  Image: Touch #100 ( aka v1.0 ).

  The current indicator-network code uses the ofono's
  NetworkRegistration interface's Technology property to determine
  which mobile data connection icon to display on the status bar.

  The code currently compares the value of Technology to:

   - gsm -- this causes 2G ( or a tortoise ) to be displayed

   - umts -- this causes 3G to be displayed

   - edge -- this causes E to be displayed

   - hspa -- this causes H to be displayed

   - lte -- valid, but currently not supported in the ofono/rilmodem
  driver ( LTE isn't yet 100% supported )

  The code instead should be examining ofono's ConnectionManager
  interface's Bearer property.   This is not currently being set by
  the ofono/rilmodem code ( see bug #1245954 for more details ).

  The valid values of the Bearer property ( with associated icons in
  parentheses ) are: none, gprs ( 2G ), edge ( E ), umts ( 3G ),
  hsupa/hsdpa/hspa ( H ), and lte ( L ).  oFono doesn't
  currently support reporting HSPA+, whereas RIL does, so if have the
  need for differentiating between HSPA and HSPA+, then we'll need to
  patch ofono so that the value hspap is valid for Bearer.

   -

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

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


[Touch-packages] [Bug 1395661] Re: Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

2014-12-16 Thread Harald Sitter
patch attached selectively disabling pch on amd64 and powerpc

** Patch added: disablepch.patch
   
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1395661/+attachment/4282005/+files/disablepch.patch

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

Title:
  Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  There's a problem with Qt WebKit (5.4.0 beta) failing to build against
  Qt 5.4.0 beta on amd64: https://launchpadlibrarian.net/190809157
  /buildlog_ubuntu-vivid-amd64.qtwebkit-opensource-src_5.4.0~beta-
  0ubuntu1~vivid1~test1_FAILEDTOBUILD.txt.gz and on powerpc:
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-005/+build/6649444/+files
  /buildlog_ubuntu-vivid-powerpc.qtwebkit-opensource-
  src_5.4.0-0ubuntu1%7Evivid1%7Etest2_FAILEDTOBUILD.txt.gz

  It seems to be related to pre-compiled headers. Qttools requires
  qtwebkit for the documentation. In the test PPA I've disabled qttools'
  qtwebkit requirement in order to have more amd64 builds done in
  general.

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

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

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


[Touch-packages] [Bug 1081022] Re: logging.SysLogHandler doesn't close UNIX socket when connection failed

2014-12-16 Thread James Page
** Description changed:

+ [Impact]
+ Restarting rsyslog causing logging from python based daemons to lockup.
+ 
+ [Test Case]
+ == script
+ #!/usr/bin/env python
+ 
+ import eventlet
+ from logging.handlers import SysLogHandler
+ import time
+ import logging
+ 
+ eventlet.patcher.monkey_patch(all=False, socket=True)
+ 
+ logger = logging.getLogger('log')
+ logger.addHandler(SysLogHandler('/dev/log'))
+ 
+ while True:
+ print send a message to logger
+ logger.error(syslog test)
+ time.sleep(1)
+ ==
+ sudo service rsyslog stop (send a message to logger log messages will just 
stop)
+ 
+ [Regression Potential]
+ The proposed fix is in all py2.7 versions  12.04 right now and is not 
causing problems.
+ 
+ [Original Bug Report]
  Python logging SysLogHandler to log into SysLog doesn't close UNIX-socket
  when connection failed. This bug is solved on the Python Issue Tracker at
  http://bugs.python.org/issue15179 and affects python package with version
  2.7.3-0ubuntu2 at Ubuntu 12.04 LTS.

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

Title:
  logging.SysLogHandler doesn't close UNIX socket when connection failed

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Precise:
  New

Bug description:
  [Impact]
  Restarting rsyslog causing logging from python based daemons to lockup.

  [Test Case]
  sudo apt-get install python-eventlet
  == run this script script
  #!/usr/bin/env python

  import eventlet
  from logging.handlers import SysLogHandler
  import time
  import logging

  eventlet.patcher.monkey_patch(all=False, socket=True)

  logger = logging.getLogger('log')
  logger.addHandler(SysLogHandler('/dev/log'))

  while True:
  print send a message to logger
  logger.error(syslog test)
  time.sleep(1)
  ==
  sudo service rsyslog stop
  sudo service rsyslog start
  (send a message to logger log messages will just stop)

  [Regression Potential]
  The proposed fix is in all py2.7 versions  12.04 right now and is not 
causing problems.

  [Original Bug Report]
  Python logging SysLogHandler to log into SysLog doesn't close UNIX-socket
  when connection failed. This bug is solved on the Python Issue Tracker at
  http://bugs.python.org/issue15179 and affects python package with version
  2.7.3-0ubuntu2 at Ubuntu 12.04 LTS.

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

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


[Touch-packages] [Bug 1081022] Re: logging.SysLogHandler doesn't close UNIX socket when connection failed

2014-12-16 Thread James Page
** Description changed:

  [Impact]
  Restarting rsyslog causing logging from python based daemons to lockup.
  
  [Test Case]
- == script
+ sudo apt-get install python-eventlet
+ == run this script script
  #!/usr/bin/env python
  
  import eventlet
  from logging.handlers import SysLogHandler
  import time
  import logging
  
  eventlet.patcher.monkey_patch(all=False, socket=True)
  
  logger = logging.getLogger('log')
  logger.addHandler(SysLogHandler('/dev/log'))
  
  while True:
- print send a message to logger
- logger.error(syslog test)
- time.sleep(1)
+ print send a message to logger
+ logger.error(syslog test)
+ time.sleep(1)
  ==
- sudo service rsyslog stop (send a message to logger log messages will just 
stop)
+ sudo service rsyslog stop
+ sudo service rsyslog start
+ (send a message to logger log messages will just stop)
  
  [Regression Potential]
  The proposed fix is in all py2.7 versions  12.04 right now and is not 
causing problems.
  
  [Original Bug Report]
  Python logging SysLogHandler to log into SysLog doesn't close UNIX-socket
  when connection failed. This bug is solved on the Python Issue Tracker at
  http://bugs.python.org/issue15179 and affects python package with version
  2.7.3-0ubuntu2 at Ubuntu 12.04 LTS.

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

Title:
  logging.SysLogHandler doesn't close UNIX socket when connection failed

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Precise:
  New

Bug description:
  [Impact]
  Restarting rsyslog causing logging from python based daemons to lockup.

  [Test Case]
  sudo apt-get install python-eventlet
  == run this script script
  #!/usr/bin/env python

  import eventlet
  from logging.handlers import SysLogHandler
  import time
  import logging

  eventlet.patcher.monkey_patch(all=False, socket=True)

  logger = logging.getLogger('log')
  logger.addHandler(SysLogHandler('/dev/log'))

  while True:
  print send a message to logger
  logger.error(syslog test)
  time.sleep(1)
  ==
  sudo service rsyslog stop
  sudo service rsyslog start
  (send a message to logger log messages will just stop)

  [Regression Potential]
  The proposed fix is in all py2.7 versions  12.04 right now and is not 
causing problems.

  [Original Bug Report]
  Python logging SysLogHandler to log into SysLog doesn't close UNIX-socket
  when connection failed. This bug is solved on the Python Issue Tracker at
  http://bugs.python.org/issue15179 and affects python package with version
  2.7.3-0ubuntu2 at Ubuntu 12.04 LTS.

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

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


[Touch-packages] [Bug 1389273] Re: Track app sales per partner

2014-12-16 Thread Launchpad Bug Tracker
** Branch linked: lp:~stolowski/unity-scopes-api/remote-scopes-partner-
id-rtm

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

Title:
  Track app sales per partner

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Pay UI:
  Fix Committed
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu RTM:
  New
Status in unity-scopes-shell package in Ubuntu RTM:
  Triaged

Bug description:
  We need to track what app sales come from which partner, by sending
  the partner string when performing a purchase.

  For documentation on what the server expects, see:
  https://wiki.ubuntu.com/AppStore/Interfaces/Purchases#purchases

  The code for each partner needs to be specified in the OEM image.

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

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


[Touch-packages] [Bug 1402993] [NEW] Webapps e.g. Facebook, Google+, Twitter, etc. doesn't work

2014-12-16 Thread Muntasim Ul Haque
Public bug reported:

Unity Webapps for Facbook, Google+, LinkedIn, Reddit, etc. and the likes don't 
work in Ubuntu 14.10 Unity. But it did work fine with Ubuntu 14.04.
Every time I access any of these webapps-intended-sites e.g. Facebook, twitter, 
etc., it asks for Would you like to install nameofthesite for extra 
feature It should've worked the first time I pressed yes button. But it 
didn't. This feature is broken in Utpoic whereas it works just fine for Trusty. 
Fix this.
No online accounts/social networking or whatevr-you -named-it lens/scope 
doesn't appear in Unity Dash. It does appear once I press 'yes' in Trusty but 
not for Utpoic.

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

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

Title:
  Webapps e.g. Facebook, Google+, Twitter, etc. doesn't work

Status in unity package in Ubuntu:
  New

Bug description:
  Unity Webapps for Facbook, Google+, LinkedIn, Reddit, etc. and the likes 
don't work in Ubuntu 14.10 Unity. But it did work fine with Ubuntu 14.04.
  Every time I access any of these webapps-intended-sites e.g. Facebook, 
twitter, etc., it asks for Would you like to install nameofthesite for extra 
feature It should've worked the first time I pressed yes button. But it 
didn't. This feature is broken in Utpoic whereas it works just fine for Trusty. 
Fix this.
  No online accounts/social networking or whatevr-you -named-it lens/scope 
doesn't appear in Unity Dash. It does appear once I press 'yes' in Trusty but 
not for Utpoic.

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

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


[Touch-packages] [Bug 1403005] [NEW] New ListItem TypeError

2014-12-16 Thread Tim Peeters
Public bug reported:

When I run tests/resources/listitems/ListItemTest.qml, the SECOND time I
swipe the Another standalone listitem, to reveal the trailing actions,
I get a TypeError. All following times that I do this swipe I get the
same error (only the first time I don't get it). The same thing happens
with leading actions.

tim@ubuntu:~/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems$ qmlscene 
ListItemTest.qml
file:///home/tim/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems/ListItemTest.qml:107:
 TypeError: Cannot read property of null

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Assignee: Zsombor Egri (zsombi)
 Status: New


** Tags: 1.2 listitem

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) = Zsombor Egri (zsombi)

** Description changed:

- When I run ListITemTest, the SECOND time I swipe the Another standalone
- listitem, to reveal the trailing actions, I get a TypeError. All
- following times that I do this swipe I get the same error (only the
- first time I don't get it). The same thing happens with leading actions.
+ When I run tests/resources/listitems/ListItemTest.qml, the SECOND time I
+ swipe the Another standalone listitem, to reveal the trailing actions,
+ I get a TypeError. All following times that I do this swipe I get the
+ same error (only the first time I don't get it). The same thing happens
+ with leading actions.
  
- tim@ubuntu:~/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems$ 
qmlscene ListItemTest.qml 
+ tim@ubuntu:~/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems$ 
qmlscene ListItemTest.qml
  
file:///home/tim/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems/ListItemTest.qml:107:
 TypeError: Cannot read property of null

** Tags added: 1.2 listitem

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

Title:
  New ListItem TypeError

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

Bug description:
  When I run tests/resources/listitems/ListItemTest.qml, the SECOND time
  I swipe the Another standalone listitem, to reveal the trailing
  actions, I get a TypeError. All following times that I do this swipe I
  get the same error (only the first time I don't get it). The same
  thing happens with leading actions.

  tim@ubuntu:~/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems$ 
qmlscene ListItemTest.qml
  
file:///home/tim/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems/ListItemTest.qml:107:
 TypeError: Cannot read property of null

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

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


[Touch-packages] [Bug 1365874] Re: Ubuntu 14.04 does not support ext4 metadata checksumming

2014-12-16 Thread Daniel Mehrmann
** Branch linked: lp:~daniel-mehrmann/e2fsprogs/maint

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

Title:
  Ubuntu 14.04 does not support ext4 metadata checksumming

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  In the Trusty release notes Metadata checksumming is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  rantBTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  /rant

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

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


[Touch-packages] [Bug 1403005] Re: New ListItem TypeError

2014-12-16 Thread Tim Peeters
I get it for the first list item in the list (the green one that says
8PX/unit) also. All other list items do not print this warning when
swiping in the actions.

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

Title:
  New ListItem TypeError

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

Bug description:
  When I run tests/resources/listitems/ListItemTest.qml, the SECOND time
  I swipe the Another standalone listitem, to reveal the trailing
  actions, I get a TypeError. All following times that I do this swipe I
  get the same error (only the first time I don't get it). The same
  thing happens with leading actions.

  tim@ubuntu:~/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems$ 
qmlscene ListItemTest.qml
  
file:///home/tim/dev/ubuntu-ui-toolkit/staging/tests/resources/listitems/ListItemTest.qml:107:
 TypeError: Cannot read property of null

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

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


[Touch-packages] [Bug 1245951] Re: Wrong oFono property used for data technology indication

2014-12-16 Thread John McAleely
Users pay for particular grades of service. This bug is that the user
sees a 3G service they are paying for when in fact they are getting 2G.
That might be good for operator PR, but it is bad for ubuntu phone's
credibility.

If you feel the two dupes listed are not dupes, please comment there,
and we can separately discuss them.

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

Title:
  Wrong oFono property used for data technology indication

Status in the base for Ubuntu mobile products:
  New
Status in Network Menu:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  Image: Touch #100 ( aka v1.0 ).

  The current indicator-network code uses the ofono's
  NetworkRegistration interface's Technology property to determine
  which mobile data connection icon to display on the status bar.

  The code currently compares the value of Technology to:

   - gsm -- this causes 2G ( or a tortoise ) to be displayed

   - umts -- this causes 3G to be displayed

   - edge -- this causes E to be displayed

   - hspa -- this causes H to be displayed

   - lte -- valid, but currently not supported in the ofono/rilmodem
  driver ( LTE isn't yet 100% supported )

  The code instead should be examining ofono's ConnectionManager
  interface's Bearer property.   This is not currently being set by
  the ofono/rilmodem code ( see bug #1245954 for more details ).

  The valid values of the Bearer property ( with associated icons in
  parentheses ) are: none, gprs ( 2G ), edge ( E ), umts ( 3G ),
  hsupa/hsdpa/hspa ( H ), and lte ( L ).  oFono doesn't
  currently support reporting HSPA+, whereas RIL does, so if have the
  need for differentiating between HSPA and HSPA+, then we'll need to
  patch ofono so that the value hspap is valid for Bearer.

   -

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

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


[Touch-packages] [Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales

2014-12-16 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Incomplete = Confirmed

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

Title:
  libgtk2 immodules has cedilla disabled in en locales

Status in GNOME Control Center:
  Confirmed
Status in GTK+ GUI Toolkit:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Invalid
Status in gnome-control-center package in Fedora:
  Fix Released

Bug description:
  Binary package hint: libgtk2.0-0

  philsf@philsf-laptop:~$ lsb_release -rd
  Description:  Ubuntu 8.04
  Release:  8.04

  philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0
  libgtk2.0-0:
Installed: 2.12.9-3ubuntu3

  One can't use dead keys to input a c+cedilla in en_US (probably other
  en_* locales). I had this on Gutsy. Now in Hardy, I thought I should
  report, since it's annoying, and the fix is documented.

  Steps to reproduce: 
  - enable deadkeys
  - Open gnome-terminal (or firefox) and enter ' + c 

  What you should get: ç
  What you do get: ć 

  Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ):

  
  Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and 
include :en in the cedilla line

  6c6
   cedilla Cedilla gtk20 /usr/share/locale 
az:ca:co:fr:gv:oc:pt:sq:tr:wa 
  ---
   cedilla Cedilla gtk20 /usr/share/locale 
az:ca:co:fr:gv:oc:pt:sq:tr:wa:en

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/228077/+subscriptions

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


[Touch-packages] [Bug 1395661] Re: Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

2014-12-16 Thread Timo Jyrinki
** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtwebkit-
opensource-src

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

Title:
  Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  There's a problem with Qt WebKit (5.4.0 beta) failing to build against
  Qt 5.4.0 beta on amd64: https://launchpadlibrarian.net/190809157
  /buildlog_ubuntu-vivid-amd64.qtwebkit-opensource-src_5.4.0~beta-
  0ubuntu1~vivid1~test1_FAILEDTOBUILD.txt.gz and on powerpc:
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-005/+build/6649444/+files
  /buildlog_ubuntu-vivid-powerpc.qtwebkit-opensource-
  src_5.4.0-0ubuntu1%7Evivid1%7Etest2_FAILEDTOBUILD.txt.gz

  It seems to be related to pre-compiled headers. Qttools requires
  qtwebkit for the documentation. In the test PPA I've disabled qttools'
  qtwebkit requirement in order to have more amd64 builds done in
  general.

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

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

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


[Touch-packages] [Bug 1366014] Re: [indicators] In a Dual SIM phone, There is no way to know which of the two SIMs is being used for cellular data.

2014-12-16 Thread Antti Kaijanmäki
Just as a reminder, this bug also causes the indicator to always show
SIM 1 mobile broadband icon, even though SIM 2 would be in use for
mobile broadband.

** Description changed:

  Pulled as separate task from bug #1350739, per comment #6:
  
  * There is no way to know which of the two SIMs is being used for
  cellular data. Also, it looks like the displayed indicator mixes data
  from different slots: when I have a connection on the secondary slot
  using EDGE, I see an icon with an H some times, and with an E (the
  right one) some times. The H is probably taking from the technology in
  the primary slot, which is not attached.
+ 
+ Also, related to this one: mobile broadband data connection speed is
+ right now always coming from SIM 1, even if SIM 2 is the one used for
+ mobile broadband.

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

Title:
  [indicators] In a Dual SIM phone, There is no way to know which of the
  two SIMs is being used for cellular data.

Status in Network Menu:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Triaged
Status in indicator-network source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  Triaged

Bug description:
  Pulled as separate task from bug #1350739, per comment #6:

  * There is no way to know which of the two SIMs is being used for
  cellular data. Also, it looks like the displayed indicator mixes data
  from different slots: when I have a connection on the secondary slot
  using EDGE, I see an icon with an H some times, and with an E (the
  right one) some times. The H is probably taking from the technology in
  the primary slot, which is not attached.

  Also, related to this one: mobile broadband data connection speed is
  right now always coming from SIM 1, even if SIM 2 is the one used for
  mobile broadband.

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

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


[Touch-packages] [Bug 1387328] Re: apport-gtk: clicking on the details tree jumps the scroll position to top

2014-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.15-0ubuntu3

---
apport (2.15-0ubuntu3) vivid; urgency=medium

  * Merge further test robustification and translation updates from trunk.
 -- Martin Pitt martin.p...@ubuntu.com   Tue, 16 Dec 2014 11:01:20 +0100

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

Title:
  apport-gtk: clicking on the details tree jumps the scroll position to
  top

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  1. Wait for a crash or run apport-bug /var/crash/something.crash
  2. Click Show Details
  3. Scroll down the tree view until you see something interesting like 
Stacktrace
  4. Click 'Stacktrace' to expand it

  What happens:
  - tree view gets focus, 1st (i.e. topmost) item in it gets selected and 
scrolled into view

  What I expect:
  - tree view gets focus, the 'Stacktrace'  item gets selected and view is not 
scrolled away from what I was interested in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apport-gtk 2.14.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 29 21:10:33 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (826 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (5 days ago)

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

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


[Touch-packages] [Bug 1387835] Re: When a dump is not collected, due to lack of memory, the reason should be in the log

2014-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.15-0ubuntu3

---
apport (2.15-0ubuntu3) vivid; urgency=medium

  * Merge further test robustification and translation updates from trunk.
 -- Martin Pitt martin.p...@ubuntu.com   Tue, 16 Dec 2014 11:01:20 +0100

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

Title:
  When a dump is not collected, due to lack of memory, the reason should
  be in the log

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Using utopic, when there is not enough available memory on the system
  the gdb dump is not collected. It would useful to have the reason
  stated in the log

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

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


[Touch-packages] [Bug 1245951] Re: Wrong oFono property used for data technology indication

2014-12-16 Thread Antti Kaijanmäki
Checked the duplicates. Both are actually duplicates of a different bug 
#1366014.
Updated them accordingly.

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

Title:
  Wrong oFono property used for data technology indication

Status in the base for Ubuntu mobile products:
  New
Status in Network Menu:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  Image: Touch #100 ( aka v1.0 ).

  The current indicator-network code uses the ofono's
  NetworkRegistration interface's Technology property to determine
  which mobile data connection icon to display on the status bar.

  The code currently compares the value of Technology to:

   - gsm -- this causes 2G ( or a tortoise ) to be displayed

   - umts -- this causes 3G to be displayed

   - edge -- this causes E to be displayed

   - hspa -- this causes H to be displayed

   - lte -- valid, but currently not supported in the ofono/rilmodem
  driver ( LTE isn't yet 100% supported )

  The code instead should be examining ofono's ConnectionManager
  interface's Bearer property.   This is not currently being set by
  the ofono/rilmodem code ( see bug #1245954 for more details ).

  The valid values of the Bearer property ( with associated icons in
  parentheses ) are: none, gprs ( 2G ), edge ( E ), umts ( 3G ),
  hsupa/hsdpa/hspa ( H ), and lte ( L ).  oFono doesn't
  currently support reporting HSPA+, whereas RIL does, so if have the
  need for differentiating between HSPA and HSPA+, then we'll need to
  patch ofono so that the value hspap is valid for Bearer.

   -

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

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


[Touch-packages] [Bug 1396672] Re: GPS data is only added with valid altitude which means it only works with full gps

2014-12-16 Thread Florian Boucault
** Changed in: camera-app
   Status: In Progress = Fix Released

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

Title:
  GPS data is only added with valid altitude which means it only works
  with full gps

Status in Camera App:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. open the camera app
  2. Swipe up from the bottom
  3. Select gps
  4. toggle it on
  5. Wait 7 seconds
  6. Take a photo
  7. Open here maps
  8. Wait till there is no blue halo around the location icon
  9. No swipe back to the camera app and take another photo
  10. compare the properties of the 2 photos in EOG and check the data tag

  EXPECTED:
  I expect both to have gps data

  ACTUAL:
  Only the image taken after a full gps fix has data

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

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


[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card

2014-12-16 Thread Florian Boucault
** Changed in: camera-app
   Status: In Progress = Fix Released

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

Title:
  Support storing and viewing photos on an SD card

Status in Camera App:
  Fix Released
Status in the base for Ubuntu mobile products:
  In Progress
Status in Gallery App:
  In Progress
Status in camera-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  In Progress
Status in camera-app package in Ubuntu RTM:
  In Progress
Status in ciborium package in Ubuntu RTM:
  New
Status in gallery-app package in Ubuntu RTM:
  In Progress

Bug description:
  If an SD card is present we will use it as extended storage for the device.
  The camera and gallery apps need to be able to access this storage.

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

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


[Touch-packages] [Bug 1402350] Re: Powering on the printer does not activate the related usb port

2014-12-16 Thread John Johansen
writing to the journal socket should be added to an abstraction the same
as writing to /dev/log

** Also affects: apparmor (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1402350

Title:
  allow writing to systemd journal sockets

Status in apparmor package in Ubuntu:
  Triaged
Status in cups package in Ubuntu:
  Won't Fix

Bug description:
  Using a desktop with vivid i386 and a USB connected HP Photosmart C4585: - 
Sending a print job does not activate the USB port.
  - Once logged into gnome-shell an icon is in the systray for a few seconds 
then disappears.

  WORKAROUND: Unplug/plug the USB cord, reload the print job, and choose
  the printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
  Uname: Linux 3.18.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CupsErrorLog:

  CurrentDesktop: GNOME
  Date: Sun Dec 14 08:54:53 2014
  KernLog:

  Lpstat:
   device for Photosmart-C4500-series: 
usb://HP/Photosmart%20C4500%20series?serial=CN87JD4109057Kinterface=1
   device for Photosmart_C4500: 
hp:/usb/Photosmart_C4500_series?serial=CN87JD4109057K
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Photosmart_C4500.ppd', 
'/etc/cups/ppd/Photosmart-C4500-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Photosmart_C4500.ppd: Permission denied
   grep: /etc/cups/ppd/Photosmart-C4500-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-7-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1368140] Re: add guide lines overlay option

2014-12-16 Thread Florian Boucault
** Changed in: camera-app
   Status: In Progress = Fix Released

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

Title:
  add guide lines overlay option

Status in Camera App:
  Fix Released
Status in the base for Ubuntu mobile products:
  In Progress
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  Both iOS and Android cameras have an option to overlay 2 evenly-spaced
  vertical and 2 evenly-spaced horizonal white guide lines.

  These are a very useful alignment aid when composing a shot.

  For details: http://en.wikipedia.org/wiki/Rule_of_thirds

  Bonus points if we could have a  Fibonacci spiral option too :-) :
  http://en.wikipedia.org/wiki/Golden_spiral

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

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


[Touch-packages] [Bug 1402350] Re: Powering on the printer does not activate the related usb port

2014-12-16 Thread Martin Pitt
Indeed I think we should fix that in /etc/apparmor.d/abstractions/base:
That's the location that allows programs to write to /dev/log, so we
sohuld also allow writing to /run/systemd/journal/{socket,dev-log}.
Under systemd, /dev/log is just a symlink to /run/systemd/journal/dev-
log, and /socket is the native journal protocol.

** Changed in: cups (Ubuntu)
   Status: Incomplete = Won't Fix

** Changed in: apparmor (Ubuntu)
   Status: New = Triaged

** Summary changed:

- Powering on the printer does not activate the related usb port
+ allow writing to systemd journal sockets

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

Title:
  allow writing to systemd journal sockets

Status in apparmor package in Ubuntu:
  Triaged
Status in cups package in Ubuntu:
  Won't Fix

Bug description:
  Using a desktop with vivid i386 and a USB connected HP Photosmart C4585: - 
Sending a print job does not activate the USB port.
  - Once logged into gnome-shell an icon is in the systray for a few seconds 
then disappears.

  WORKAROUND: Unplug/plug the USB cord, reload the print job, and choose
  the printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
  Uname: Linux 3.18.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CupsErrorLog:

  CurrentDesktop: GNOME
  Date: Sun Dec 14 08:54:53 2014
  KernLog:

  Lpstat:
   device for Photosmart-C4500-series: 
usb://HP/Photosmart%20C4500%20series?serial=CN87JD4109057Kinterface=1
   device for Photosmart_C4500: 
hp:/usb/Photosmart_C4500_series?serial=CN87JD4109057K
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Photosmart_C4500.ppd', 
'/etc/cups/ppd/Photosmart-C4500-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Photosmart_C4500.ppd: Permission denied
   grep: /etc/cups/ppd/Photosmart-C4500-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-7-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1398447] Re: The time displays wrong when recording video over 60 minutes

2014-12-16 Thread Florian Boucault
** Changed in: camera-app
   Status: In Progress = Fix Released

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

Title:
  The time displays wrong when recording video over 60 minutes

Status in Camera App:
  Fix Released
Status in the base for Ubuntu mobile products:
  In Progress
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  [Procedures]
  1. open the camera app and record a video over 60 minutes.

  [Expect results]
  the time display as 01:00:00
  [Actual results]
  the time restarts from 00:00

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

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


[Touch-packages] [Bug 1173071] Re: Some windows are empty

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
12.04 or 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Some windows are empty

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Some windows in Ubuntu 13.04 are empty. For example, it is the
  Changing Desktop Background window. Or Account Settings of ICQ account
  plugin. Hotot window too. See attached screenshots

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr 26 11:05:18 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.6, 3.8.0-19-generic, x86_64: installed
   nvidia-304, 304.88, 3.8.0-19-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3981]
   NVIDIA Corporation GF108M [GeForce GT 555M] [10de:0deb] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-04-25 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: LENOVO 20091
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=8b720dfe-ddcb-45ae-92d9-fc85bafd993b ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 47CN32WW(V2.10)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnLENOVO:bvr47CN32WW(V2.10):bd01/04/2012:svnLENOVO:pn20091:pvrLenovoIdeaPadY570:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: 20091
  dmi.product.version: Lenovo IdeaPad Y570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Thu Apr 25 22:12:35 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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


[Touch-packages] [Bug 1171255] Re: Can't click indicators with second monitor plugged in

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
12.04 or 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Can't click indicators with second monitor plugged in

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When I plug my laptop into my TV via HDMI, I can no longer click most
  of the indicators on the laptop side. I can click the volume, date,
  and power cog, but everything to the left of that has no effect. On
  the TV's side I can click all the indicators. Running fully updated
  ubuntu 13.04 with unity, the laptop has intel HD4000 graphics. The
  laptop screen is at 1366x768 and the TV at 1080p.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Apr 21 18:38:41 2013
  InstallationDate: Installed on 2013-04-17 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130416)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1170747] Re: Unity gets slower after waking up from suspension

2014-12-16 Thread Andrea Azzarone
** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Unity gets slower after waking up from suspension

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  My VGA is AMD ATI Mobility Radeon HD 5400. Unity's animations and it's 
behaviour gets extremely slow after waking up from suspension.  I can't state 
when it exactly happens, but I'm experiencing this, few minutes after waking up 
from suspension. Well, it even doesn't happen everytime. Ocationally it happen 
when I execute unity command in Terminal.
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.04.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: wl fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr 19 20:57:12 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-16-generic, x86_64: installed
   fglrx, 9.010, 3.8.0-16-generic, x86_64: installed
   virtualbox, 4.2.10, 3.8.0-16-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 
Series] [1002:68e0] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0447]
  InstallationDate: Installed on 2013-04-04 (15 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1)
  MachineType: Dell Inc. Inspiron N5010
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic 
root=UUID=3394d4bf-1684-412f-9942-e402b46031c2 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 03C6YH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/10/2010:svnDellInc.:pnInspironN5010:pvrA04:rvnDellInc.:rn03C6YH:rvrA04:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.04.05-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1

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

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


[Touch-packages] [Bug 1170536] Re: regression, 4/18 updates broke ATI multi monitor

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
12.04 or 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  regression, 4/18 updates broke ATI multi monitor

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  The updates for Raring that came down on 4/18 completely broke my ATI
  multi-monitor support. Dropping back to mirrored mode is functioning.

  I have three monitors, two are indentical and one is a slightly
  smaller resolution. If I break mirroring unity or compiz (not sure
  which) is failing to start.  I get the same effect for two monitors (I
  tried unplugging each of the secondary monitors).

  Don't think this is an x/opengl problem since I can get displays. I
  just can't get any menus or window decorations.

  Does this help?
  [   68.080288] show_signal_msg: 57 callbacks suppressed
  [   68.080292] compiz[2615]: segfault at 60a3d5f ip 7f896922d223 sp 
7fff331f0b20 error 4 in libgobject-2.0.so.0.3600.0[7f89691fb000+4d000]

  automatic bug reporting is broken because the desktop is not coming
  up.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 18 22:23:31 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.2.12, 3.8.0-18-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Redwood PRO [Radeon HD 5570] 
[1002:68d9] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:6872]
  InstallationDate: Installed on 2013-04-03 (16 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402)
  MachineType: Hewlett-Packard HPE-480t
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic 
root=UUID=04c65aa3-0917-4b9e-9dec-9631d7eb465a ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: N/A
  dmi.board.name: 2A86
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.04E01
  dmi.chassis.asset.tag: 2MD0470HR2
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.10:bd09/16/2010:svnHewlett-Packard:pnHPE-480t:pvr:rvnPEGATRONCORPORATION:rn2A86:rvr1.04E01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: HPE-480t
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Thu Apr 18 21:54:54 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Receiver KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputASUS USB2.0 Webcam   KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1169548] Re: Workspace Switcher should directly display the selected one

2014-12-16 Thread Andrea Azzarone
** Changed in: unity
   Status: New = Opinion

** Changed in: unity (Ubuntu)
   Status: New = Opinion

** Changed in: unity
   Importance: Undecided = Wishlist

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

Title:
  Workspace Switcher should directly display the selected one

Status in Unity:
  Opinion
Status in unity package in Ubuntu:
  Opinion

Bug description:
  The actual Workspace Switcher icon , when a workspace is clicked (aka 
1/2/3/...), call  display the activated workspaces; then a second  click is 
needed to display the desired workplace.
  As the WW icon is already displaying the (4) workspaces, it should be easier 
to have a one click shot to get the selected workspace. Maybe a configurable 
choice with unity-tweak-tool is also desirable.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.15-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Apr 16 14:28:55 2013
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1165860] Re: [Raring] Launcher shows disk icons for non removable media

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
12.04 or 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  [Raring] Launcher shows disk icons for non removable media

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  In current raring, icons are displayed in the launcher for system FAT
  partitions which are on the internal hard-disk.

  See attached image.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.05.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Apr  7 19:48:44 2013
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  InstallationDate: Installed on 2013-03-23 (15 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-04-02 (5 days ago)

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

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


[Touch-packages] [Bug 1167747] Re: when launcher autohides it leaves an impenetrable stripe behind

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
12.04 or 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  when launcher autohides it leaves an impenetrable stripe behind

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When the launcher autohides it leaves behind a stripe which obscures
  the upper left portion of any open window.  Sometimes the stripe
  splits in two vertically when you move a window to the very far left
  or past the left edge of the screen.

  This is 13.04 development release of around April 6 2013

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.05.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.9.2-0ubuntu5
  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: Thu Apr 11 09:17:20 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be2] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84a9]
  InstallationDate: Installed on 2013-04-06 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130402.1)
  MachineType: ASUSTeK COMPUTER INC. 1025CE
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic 
root=UUID=0e8764be-5c6e-4b66-9156-c40d602d2e37 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1025C.1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 1025C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1025C.1001:bd04/16/2012:svnASUSTeKCOMPUTERINC.:pn1025CE:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
  dmi.product.name: 1025CE
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.9~daily13.04.05-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Thu Apr 11 08:00:01 2013
  xserver.configfile: default
  xserver.errors: Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu4
  xserver.video_driver: modesetting

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

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


[Touch-packages] [Bug 1390423] Re: Front camera controls includes Flash type selection even though this is not supported

2014-12-16 Thread Florian Boucault
** Changed in: camera-app
 Assignee: (unassigned) = Ugo Riboni (uriboni)

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

Title:
  Front camera controls includes Flash type selection even though this
  is not supported

Status in Camera App:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

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

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

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


[Touch-packages] [Bug 1172901] Re: Windows controls fail

2014-12-16 Thread Andrea Azzarone
** Changed in: unity
   Status: Incomplete = Invalid

** Changed in: unity (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  Windows controls fail

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 13.04
  Release:  13.04
  linux:
Installed: (none)
Candidate: 3.8.0.19.35
Version table:
   3.8.0.19.35 0
  500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages

  Just installed 13.04.  Windows controls not working.  Some element in
  the desktop is not listening to the kill, down and expand buttons.
  Since these are normally programmed to be interrupts and not ignored,
  what more can be said?

  Work around is to use other controls.  Something to be said for
  redundancy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2513 F pulseaudio
   /dev/snd/controlC1:  john   2513 F pulseaudio
   /dev/snd/controlC0:  john   2513 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [   16.694718] input: gspca_zc3xx as 
/devices/pci:00/:00:12.0/usb3/3-1/input/input11
   [   16.695058] usbcore: registered new interface driver gspca_zc3xx
   [   16.706058] usbcore: registered new interface driver snd-usb-audio
   [   19.990042] init: plymouth-stop pre-start process (2084) terminated with 
status 1
   [   53.301083] EXT4-fs (sdb7): mounted filesystem with ordered data mode. 
Opts: (null)
  Date: Thu Apr 25 16:40:35 2013
  HibernationDevice: RESUME=UUID=18e38748-057c-4a1a-a952-3ca0ec32d097
  InstallationDate: Installed on 2012-10-22 (184 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA78LM-S2H
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=2c4c6961-8d74-4706-8d27-4c2226abc128 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)
  dmi.bios.date: 04/16/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-MA78LM-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd04/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78LM-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78LM-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA78LM-S2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1402666] Re: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] Playback problem

2014-12-16 Thread David Chatterton
Regrettably, my suggestion that this bug report be closed is premature.

On switching on the laptop from cold this morning, I found that there
was nothing listed in the Systems Settings  Sound pane.

I chose to shut down and start up again. This time, I found the
Speakers, Built-in Audio listed but with the HDMI options shown.

I did a restart and found the same situation. However, I decided to plug
in a pair of headphones in an attempt to kick-start the system. This
brought up the panel asking to identify the type of headset. The
headphones appeared in the listing and the Test Sound button enabled me
to test the left and right channels for output. I then clicked on the
Speakers and found that the HDMI options had been replaced by the Test
Sound button. However, the left and right channel test sounds came
through the headphones and not through the speakers, even though the
speakers were highlighted. I then removed the headphones. Their menu
item disappeared and I was able to use the Test Sound button to get
sound from the speakers.

The point about this bug report is that the system does not function as
well as one could reasonably expect. I have a number of people who are
interested in moving away from the MS Windows environment and are
looking to me for a recommendation. Although Dell appear to manufacture
an excellent laptop in the form of the XPS 13, Dell still only supply it
with Ubuntu 12.04 LTS and include proprietary drivers for the Intel AC
7260 WiFi and Bluetooth chip. I believe that I have moved on
significantly by upgrading to 14.10 and using the latest v3.18 kernel
(as well as dispensing with the Dell-supplied drivers). I have great
expectations for 15.04 when it appears. However, I would not expect any
support from Dell for what I have done so far.  Until I can get the
laptop to perform reliably without intervention, my advice to those
wishing to move away from Windows is to bite the bullet and invest in an
Apple MacBook Pro running OS X 10.10.1. One can still run FOSS
applications such as LibreOffice and GIMP on the Mac but it is a pity
that Ubuntu has not yet arrived at the Mac's level of functionality,
although I hope that, by continuing to submit my bug reports, I can
contribute to Ubuntu's development.

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

Title:
  [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  If an HDMI monitor is plugged into the video out and the Videos app is
  started, the Systems Settings  Sound  Output shows only the
  Speakers, Built-in Audio in the Play sound through listing. The HDMI
  option is not presented.

  The workaround is to open the VLC app which lists the Built-in Stereo (HDMI) 
option under its Audio  Audio Devices menu.
   
  When a video is started in VLC, having selected the HDMI option, the sound 
plays through the monitor speakers. The HDMI / Display Port , Built-in Audio 
item then appears in the Play sound through window, even though the selection 
highlight remains on Speakers. The sound output can be switched between either 
output by highlighting the chosen option.

  If VLC is closed and Videos is restarted, the sound now plays through
  the previously selected HDMI item and can be switched between the
  monitor and the laptop's speakers.

  What I regard as a bug is the failure of the HDMI option to appear in
  the Play sound through listing as soon as an HDMI monitor is plugged
  into the Display Port output. Obviously, VLC has the means to add this
  item but the Videos app does not seem to be able to do this by itself.

  In contrast, as soon as a previously paired set of Bluetooth headphone
  are turned on, the Headset does appear as a menu item in the listing.
  I would reasonably expect the plugging in of an HDMI monitor into the
  Display Port to automatically add this item as well as its affects on
  the Screen Display pane of Systems Settings.

  Note: the laptop is running Ubuntu 14.10 and the Linux kernel has
  recently been upgraded to v3.18 (Vivid).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.18.0-031800-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   david  2242 F...m pulseaudio
   /dev/snd/controlC1:  david  2242 F pulseaudio
   /dev/snd/controlC0:  david  2242 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Dec 15 13:13:47 2014
  InstallationDate: Installed on 2014-12-11 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  

[Touch-packages] [Bug 1394244] Re: pycurl gives 'gnutls_handshake() warning: The server name sent was not recognized', curl on command line and wget work with same URL

2014-12-16 Thread Till Kamppeter
Jeff, can you check whether this is perhaps caused by the server change
and whether perhaps the server needs a fix instead of pycurl?

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

Title:
  pycurl gives 'gnutls_handshake() warning: The server name sent was not
  recognized', curl on command line and wget work with same URL

Status in pycurl package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in pycurl source package in Trusty:
  New
Status in system-config-printer source package in Trusty:
  In Progress
Status in pycurl source package in Utopic:
  New
Status in system-config-printer source package in Utopic:
  In Progress

Bug description:
  From a Python program (system-config-printer) I need to access an
  https URL (on OpenPrinting) assuring that the answer really comes from
  OpenPrinting and not from an attacker. This serves for automatically
  downloading and installing driver packages for detected and locally
  unsupported printers.

  A typical URL sent by system-config-printer to find driver packages
  for a detected printer is

  
https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL
  :EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;

  The https://...; allows for checking whether the answer really comes
  from OpenPrinting. It is no problem accessing this URL with a browser
  or by the command line:

  curl
  
'https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL
  :EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;'

  wget
  
'https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL
  :EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;'

  In all cases I get an XML data set in a reasonable amount of time (so
  server performance is OK). The XML data set tells about a driver
  package from Epson with all info to download it and to establish
  automatic updates via the facilities of the distro. RPM- and DEB-based
  distros with 32-bit or 64-bit Intel architectures are supported.

  system-config-printer is written completely in Python and uses the
  pycurl library to call the URL with verification that the
  communication is done with the actual OpenPrinting server. This does
  not work any more. If I run the following simple Python code it fails:

  --
  import pycurl
  def collect_data(result):
 print(result)
 return len(result)

  curl = pycurl.Curl()
  curl.setopt(pycurl.SSL_VERIFYPEER, 1)
  curl.setopt(pycurl.SSL_VERIFYHOST, 2)
  curl.setopt(pycurl.WRITEFUNCTION, collect_data)
  curl.setopt(pycurl.URL, 
'https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL:EP-805A%20Series;DES:EPSON%20EP-805A%20Series;CLS:PRINTER;')
  status = curl.perform()
  repr(status)
  quit()
  --

  You can paste the lines into a text editor to get a Python program or
  run python or python3 (Python version seems not to matter) and
  paste the bunch of lines to the prompt.

  The result is always the same, the status = curl.perform() line
  gives:

  Traceback (most recent call last):
File stdin, line 1, in module
  pycurl.error: (51, 'gnutls_handshake() warning: The server name sent was not 
recognized')

  For me it looks like that something has changed, as formerly this
  Python code worked correctly.

  If I change https://...; to http://...; all works correctly and I
  get the XML data, but then there is no verification any more that the
  communication is really done with OpenPrinting.

  See also

  http://stackoverflow.com/questions/568247/pycurl-fails-but-curl-from-
  bash-works-in-ubuntu

  This all looks like a bug in pycurl.

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

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


[Touch-packages] [Bug 1163877] Re: Black screen on log out

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this bug on
12.04 or 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Black screen on log out

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.04, clean install. Notebook HP Pavilion dv6000
  NVidia Graphics, nvidia-304-updates driver

  After log out, notebook screen becomes black. If there is a second
  monitor, it works, showing login interface. Mouse can be moved outside
  the screen, but there is no image in main screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.04.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  NonfreeKernelModules: wl nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.84  Wed Feb 27 05:03:32 PST 
2013
   GCC version:  versão do gcc 4.7.2 (Ubuntu/Linaro 4.7.2-22ubuntu4)
  .tmp.unity.support.test.0:

  ApportVersion: 2.9.2-0ubuntu5
  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: Wed Apr  3 08:33:11 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-13-generic, i686: installed
   bcmwl, 6.20.155.1+bdcom, 3.8.0-14-generic, i686: installed
   nvidia-304-updates, 304.84, 3.8.0-14-generic, i686: installed
   virtualbox, 4.2.10, 3.8.0-14-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation C67 [GeForce 7150M / nForce 630M] [10de:0531] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30cf]
  InstallationDate: Installed on 2013-03-23 (11 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130322)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic 
root=UUID=3f5dba1f-191b-4bd6-a67a-f2d031435939 ro nomodeset locale=pt_BR quiet 
splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.name: 30CF
  dmi.board.vendor: Quanta
  dmi.board.version: 85.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd03/22/2011:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CF:rvr85.26:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.9~daily13.03.29-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Wed Apr  3 08:25:37 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

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

  xserver.version: 2:1.13.3-0ubuntu4

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

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


[Touch-packages] [Bug 1076934] Re: Duplicated menu items

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
14.04 or 14.10 (or 12.04)?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Duplicated menu items

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Menu items are duplicated, running in Unity and in full screen mode.
  Checked other apps, no duplication found.

  unity  6.10.0-0ubun amd64

  Only noticed this yesterday, got an update of Unity related packages a
  day before and as far as I can remember this is the first restart
  after that - could be related somehow?

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: geany 1.22+dfsg-2
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov  9 11:35:26 2012
  InstallationDate: Installed on 2012-07-23 (108 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: geany
  UpgradeStatus: Upgraded to quantal on 2012-10-25 (14 days ago)

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

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


[Touch-packages] [Bug 1082658] Re: apport keeps crashing when i try to file a bug on Unity

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Is this still a problem for you?

** Changed in: unity
   Status: New = Incomplete

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

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

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

Title:
  apport keeps crashing when i try to file a bug on Unity

Status in Unity:
  Incomplete
Status in apport package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  everytime i try to report bug using ubuntu-bug on Unity i get the
  following output:

  gnomefreak@Development:~$ ubuntu-bug unity
  Traceback (most recent call last):
File /usr/share/apport/apport-gtk, line 588, in module
  app.run_argv()
File /usr/lib/python3/dist-packages/apport/ui.py, line 637, in run_argv
  return self.run_report_bug()
File /usr/lib/python3/dist-packages/apport/ui.py, line 439, in 
run_report_bug
  self.collect_info(symptom_script)
File /usr/lib/python3/dist-packages/apport/ui.py, line 990, in 
collect_info
  icthread.exc_raise()
File /usr/lib/python3/dist-packages/apport/REThread.py, line 63, in 
exc_raise
  raise self._exception[1].with_traceback(self._exception[2])
File /usr/lib/python3/dist-packages/apport/REThread.py, line 33, in run
  self._retval = self.__target(*self.__args, **self.__kwargs)
File /usr/lib/python3/dist-packages/apport/ui.py, line 87, in 
thread_collect_info
  report.add_package_info(package)
File /usr/lib/python3/dist-packages/apport/report.py, line 310, in 
add_package_info
  dep, v, self._customized_package_suffix(dep))
File /usr/lib/python3/dist-packages/apport/report.py, line 244, in 
_customized_package_suffix
  mod = packaging.get_modified_files(package)
File /usr/lib/python3/dist-packages/apport/packaging_impl.py, line 256, 
in get_modified_files
  s = os.stat('/' + words[-1].decode('UTF-8'))
  UnicodeEncodeError: 'ascii' codec can't encode character '\xed' in position 
40: ordinal not in range(128)

  
  I had no issues filing this bug. I also tried to report bug on gnome to test 
apport and it also worked

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apport 2.6.2-0ubuntu5
  ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
  Uname: Linux 3.7.0-3-generic i686
  ApportLog:
   
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: i386
  CrashReports:
   640:1000:122:10613:2012-11-24 08:29:45.195778846 -0500:2012-11-24 
08:29:46.195778846 -0500:/var/crash/_usr_bin_apport-bug.1000.crash
   600:111:122:0:2012-11-23 00:44:02.383962339 -0500:2012-11-14 
10:29:12.061995836 
-0500:/var/crash/_usr_lib_ubuntuone-client_ubuntuone-syncdaemon.1000.uploaded
  Date: Sat Nov 24 08:34:37 2012
  InstallationDate: Installed on 2012-07-24 (123 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120331)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=C
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to raring on 2012-07-24 (123 days ago)
  --- 
  ApportLog:
   
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: i386
  CrashReports:
   640:1000:122:10613:2012-11-24 08:29:45.195778846 -0500:2012-11-24 
08:29:46.195778846 -0500:/var/crash/_usr_bin_apport-bug.1000.crash
   600:111:122:0:2012-11-23 00:44:02.383962339 -0500:2012-11-14 
10:29:12.061995836 
-0500:/var/crash/_usr_lib_ubuntuone-client_ubuntuone-syncdaemon.1000.uploaded
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2012-07-24 (128 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120331)
  MarkForUpload: True
  Package: apport 2.6.2-0ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=C
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Tags: third-party-packages raring running-unity
  Uname: Linux 3.7.0-4-generic i686
  UpgradeStatus: Upgraded to raring on 2012-07-24 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1082149] Re: CmakeList.txt is calling wrong version numbers for compiz and translation function is wrong

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Due to the nature of this bug I'm
going to close it.

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  CmakeList.txt is calling wrong version numbers for compiz and
  translation function is wrong

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  bzr branch lp:unity

  sudo apt-get build-deps unity 
  (which is not calling all the Right dependenceys )

  mkdir ~/unity/build/

  cd ~/unity/build

  cmake ../ -DCMAKE_INSTALL_PREFIX:PATH=/usr

  fails out because the translation bool statement is not correct 
  so I fixed that then tried to run cmake again and learned that all the compiz 
libs are also not the righ versioning numbers thous causing Cmake to error out. 
so I am going to fix that But I have a feeling that even though I will fix that 
I am sure that the build is going to fail due to mis match of libs 

  we will see what happenes

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
  Uname: Linux 3.7.0-2-generic i686
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Nov 22 14:32:23 2012
  InstallationDate: Installed on 2012-11-22 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121121)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1082714] Re: HighContrast WM theme requires log out and log in to take effect

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
12.04 or 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  HighContrast WM theme requires log out and log in to take effect

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1. Open System SettingsAppearance
  2. Set the theme to HighContrast

  What happens
  ---
  The window theme (where the app's title bar, minimize, maximize, and close 
buttons are when not maximized) doesn't change. Even running unity --replace 
doesn't change the window theme. It takes logging out and logging back in for 
the HighContrast window theme to take effect.

  gnome-accessibility-themes 3.6.3 includes a new window theme for the
  HighContrast theme. The current window theme is stored in gsettings
  org.gnome.desktop.wm.preferences

  Changing the theme to Ambiance, Radiance, or Adwaita (Adwaita is
  included in gnome-themes-standard) changes the window theme without
  delay. It's only HighContrast that isn't working right.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
  Uname: Linux 3.7.0-3-generic x86_64
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Nov 23 12:01:07 2012
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins

2014-12-16 Thread Didier Roche
Also, can you ask to drop Recommends: dleyna-server to a suggests? Keep
me posted on the outcome of the split that was discussed (I agree with
Tim on the plugin split), then please, reassign the bug to me :)

** Changed in: grilo-plugins (Ubuntu)
   Status: New = Incomplete

** Changed in: grilo-plugins (Ubuntu)
 Assignee: Didier Roche (didrocks) = (unassigned)

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

Title:
  [MIR] grilo-plugins

Status in grilo-plugins package in Ubuntu:
  Incomplete

Bug description:
  Availability: In universe, builds on all archs

  Rational: grilo-plugins is now a dependency of totem and is hard to
  patch out. See lp:1393067

  Security: No known CVEs

  Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are
  feature requests. Active debian maintainer. Has watch file. Tests are
  run during build.

  UI standards: The package is translated upstream.

  Dependencies: All deps in main

  Standards compliance: No issues

  Maintenance: Actively maintained in debian. ubuntu-gnome team will
  subscribe in ubuntu.

  Background info: Grilo is a framework focused on making media
  discovery and browsing easy for application developers. This package
  contains it's plugins, including the tracker one, which is now needed
  by totem

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

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


[Touch-packages] [Bug 1084616] Re: Incorrectly rendered workspace switcher (shows blue)

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Incorrectly rendered workspace switcher (shows blue)

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  On a multi-monitor setup I am noticing when I use the Workspace
  Switcher I see the desktops on the right monitor (left: external
  screen, right: laptop screen) rendered incorrectly with a blue strip.
  See the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
  Uname: Linux 3.7.0-3-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Thu Nov 29 08:59:57 2012
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21cf]
  InstallationDate: Installed on 2012-11-24 (5 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121123)
  MachineType: LENOVO 4239CTO
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic 
root=UUID=5fac2c6e-90ff-4e5a-a7d2-e4f1250e3039 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
  version.libdrm2: libdrm2 2.4.40-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.13-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.4-0ubuntu1
  xserver.bootTime: Wed Nov 28 10:33:08 2012
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.0-0ubuntu8
  xserver.video_driver: intel

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

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


[Touch-packages] [Bug 1381583] Re: [Gallery] imported pictures should show in Event for today

2014-12-16 Thread Jean-Baptiste Lallement
During the verification of this fix, the gallery-app crashed while
importing a picture from flicker [1] .
(https://errors.ubuntu.com/oops/11ff2804-8516-11e4-8a59-fa163e5bb1a2)

[1]
https://www.flickr.com/photos/chaoticmind75/15844554777/in/set-72157626146319517

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

Title:
  [Gallery] imported pictures should show in Event for today

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Gallery App:
  In Progress
Status in Ubuntu UX bugs:
  Triaged
Status in gallery-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu RTM:
  In Progress

Bug description:
  When pictures are imported into the gallery, via content-hub, we
  should always display them in the Event for the current day. Right
  now, the picture is played in the Event that corresponds to the
  metadata creation date which is very confusing because after the
  picture is imported you can't find it easily.

  Arthur and I discussed modifiying one of the standard exif tags (like
  DateTime, but don't modify CreationDate) with the current date of
  import as the gallery already sorts by a series of tags. Another
  solution would be to add a custom tag like (importDate) and change the
  sort to use that if it exists before falling back to other tags.

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

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


[Touch-packages] [Bug 1083163] Re: from dash cannot launch two consecutive times the searched items

2014-12-16 Thread Andrea Azzarone
** Changed in: unity
   Status: New = Invalid

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

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

Title:
  from dash cannot launch two consecutive times the searched items

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Release of Ubuntu: 13.04
  Package Version: 6.12.0-0ubuntu4
  Expected Results: it launch all the times
  Actual Results: it launch only the first time

  TESTCASE:

  - Open Dash and type 'writer' to search L.O. writer
  - Press enter to start L.O. writer
  - Once started, close L.O. writer
  - Open dash and press enter, it won't relaunch L.O. writer

  ProblemType: BugDistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
  Uname: Linux 3.7.0-3-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Nov 26 14:41:40 2012
  DistUpgraded: 2012-10-13 10:00:57,140 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.2.4, 3.7.0-2-generic, x86_64: installed
   vboxhost, 4.2.4, 3.7.0-3-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
     Subsystem: Giga-byte Technology Device [1458:d000]
  InstallationDate: Installed on 2012-10-12 (44 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20121011)
  MachineType: Gigabyte Technology Co., Ltd. H55M-S2H
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic 
root=UUID=874a505d-d121-4029-b543-ef8ce5fb9498 ro quiet splash 
vt.handoff=7SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2012-10-13 (44 days ago)
  dmi.bios.date: 08/20/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: H55M-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55M-S2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.40-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.13-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.4-0ubuntu1
  xserver.bootTime: Mon Nov 26 09:03:28 2012
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input  USB Keyboard   KEYBOARD, id 8
   input  USB Keyboard   KEYBOARD, id 9
   inputPIXART USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.0-0ubuntu8
  xserver.video_driver: intel

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

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


[Touch-packages] [Bug 1087766] Re: unity does not create thumbnails

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no loger supported. Can you still reproduce this on
14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  unity does not create thumbnails

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1. Download pic
  2. Search it through dash
  3. No thumbnails are generated

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily12.12.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8
  Uname: Linux 3.7.0-5-generic x86_64
  ApportVersion: 2.6.3-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Dec  7 16:23:47 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-07 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121207)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1084780] Re: Switcher text transiently rendered at incorrect position

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this on
14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Switcher text transiently rendered at incorrect position

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When the alt-tab switcher accordions an icon there seems to be a
  transient (~.5s) mis-positioning of the title text when you select the
  icon.

  The attached video demonstrates this - watch the Sublime Text title.
  When the icon has been accordioned before selection the text shifts
  ~1px to the right after ~.5s; when the icon has not been accordioned,
  the text is consistently positioned correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Uname: Linux 3.7.0-4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Fri Nov 30 09:53:26 2012
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.7.0-3-generic, x86_64: installed
   virtualbox, 4.1.22, 3.7.0-4-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04c1]
   Advanced Micro Devices [AMD] nee ATI Whistler [AMD Radeon HD 6600M Series] 
[1002:6741] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04c1]
  InstallationDate: Installed on 2012-06-16 (165 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120521)
  MachineType: Dell Inc. Dell System Inspiron N4110
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.7.0-4-generic 
root=UUID=29e6204e-f505-41b5-b312-b6257ee24e9e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Q4E343
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rnQ4E343:rvrX01:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Inspiron N4110
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.40-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.0.1-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.13-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.4-0ubuntu1
  xserver.bootTime: Fri Nov 30 08:39:02 2012
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.0-0ubuntu8
  xserver.video_driver: intel

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

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


[Touch-packages] [Bug 1090006] Re: Dash home gives bogus results when there are no matches for a search string

2014-12-16 Thread Andrea Azzarone
I cannot reproduce this bug on 14.10. Seems to work fine with new smart
scopes. Can you still reproduce this?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Dash home gives bogus results when there are no matches for a search
  string

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1) Open the Dash
  2) Search for a nonsense string like lkadjflkajdlfjald

  You'll notice that the only results are a full set of Files 
  Folders as if I had not searched at all.  But these files and folders
  should not appear at all, as if they matched my search.

  Instead, I'd expect an error message of some such, as I get when
  search on one of the other lenses and no results appear.

  This may be a bug in the files lens instead of unity, I wasn't sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily12.12.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-6.14-generic 3.7.0
  Uname: Linux 3.7.0-6-generic i686
  ApportVersion: 2.7-0ubuntu2
  Architecture: i386
  CheckboxSubmission: 9a284f3f6b4f7829abbe27ad9573a709
  CheckboxSystem: 3935143777c965daaa64b51f0134f712
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Dec 13 10:57:35 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-04-22 (601 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110422)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1083039] Re: Can't install apps from dash while package manager is busy

2014-12-16 Thread Andrea Azzarone
I cannot reproduce this on 14.04. Closing the bug because Ubuntu 13.04
is no longer supported.

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Can't install apps from dash while package manager is busy

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Today I was updating my package list with apt-get update and then
  running a dist-upgrade while I was also wanting to instlal chromium by
  searching in the dash, right-clicking and installing the package.
  There was no installation and no feedback that the installation could
  not happen at the current time - this gives a sub-optimal experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
  Uname: Linux 3.7.0-3-generic i686
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Nov 25 19:20:43 2012
  InstallationDate: Installed on 2012-11-24 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121123)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1092884] Re: unity launcher locks windows when minimized - cannot reopen them

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 is no longer supported. Can you still reproduce this bug on
14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  unity launcher locks windows when minimized - cannot reopen them

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When I minimize a window to the side panel in will not unminimize (or
  open) when I click with the mouse.

  I unistalled nvidia-current and installed nouveau-firmware but to no
  avail.

  This taking place on a GEForce 210/218 nvidia card.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily12.12.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic i686
  ApportVersion: 2.7-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,move,put,wobbly,mousepoll,regex,cube,text,resize,place,animation,ring,rotate,scale,expo,ezoom,unityshell]
  Date: Fri Dec 21 07:16:08 2012
  InstallationDate: Installed on 2011-10-13 (434 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1097322] Re: Duplicate entries in the launcher

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Can you
still reproduce this problem on 14.04 or 14.10?


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

** Changed in: unity
   Status: New = Incomplete

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

Title:
  Duplicate entries in the launcher

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  After opening mumble, I now have 2 mumble icons on the launcher. It
  was locked to the launcher and the new entry seemed to be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily12.12.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Tue Jan  8 12:57:17 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fba0]
  InstallationDate: Installed on 2013-01-01 (7 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121231)
  MachineType: TOSHIBA Satellite U845W
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-7-generic 
root=UUID=9b2bd4f3-86c7-4779-ad24-789858696826 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.20:bd07/27/2012:svnTOSHIBA:pnSatelliteU845W:pvrPSU5RU-00Q003:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite U845W
  dmi.product.version: PSU5RU-00Q003
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.9~daily12.12.05-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.40-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0.902-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.16-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu1
  xserver.bootTime: Mon Jan  7 18:45:18 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.0.902-0ubuntu1
  xserver.video_driver: intel

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

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


[Touch-packages] [Bug 1126221] Re: Switching from multiple to one screen causes windows to go missing

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Also
I'm pretty sure we've already fixed this (cannot find the duplicate
right now). Please reopen if you can still reproduce this.

** Changed in: unity
   Status: New = Incomplete

** Changed in: unity (Ubuntu)
   Status: New = Invalid

** Changed in: unity
   Status: Incomplete = Invalid

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

Title:
  Switching from multiple to one screen causes windows to go missing

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  For this you need a machine with multiple displays.

  Setup your desktop with a single workspace (the now default of 13.04?)
  Enable multiple monitors, side by side.
  Open a window on one monitor (such as nautilus) and another on the other 
monitor
  Use the display control panel to switch off one of the monitors.

  Observe that one of the windows is now lost offscreen. It appears in
  the alt-tab list, but you can't make it appear on screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.02.14-0ubuntu1 [origin: 
LP-PPA-ubuntu-unity-daily-build]
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell]
  CrashDB: unity
  Date: Fri Feb 15 13:16:40 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-29 (230 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-01-18 (27 days ago)

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

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


[Touch-packages] [Bug 1118308] Re: Unity graphical errors with fglrx drivers

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Can you
still reproduce this problem on 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Unity graphical errors with fglrx drivers

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 13.04 there are some graphical errors in Unity by using fglrx 
drivers from Ubuntu official repositories.
  See attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Thu Feb  7 13:19:28 2013
  InstallationDate: Installed on 2013-02-05 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130205)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1111757] Re: dragging tab to unity launcher is recognized as dragging file

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Also I
cannot reproduce this on 14.04+. I'm going to close the bug. Please
reopen if you are still affected by this issue.

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  dragging tab to unity launcher is recognized as dragging file

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Drag tab from terminal
  2. Drop it in launcher
  3. Nautilus is highlighted even after dropping

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.01.25.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  ApportVersion: 2.8-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Jan 31 19:42:33 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-07 (55 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121207)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1149495] Re: Dash home application icon is different from app-lens icon

2014-12-16 Thread Andrea Azzarone
** Changed in: unity
   Status: New = Opinion

** Changed in: unity (Ubuntu)
   Status: Triaged = Opinion

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

Title:
  Dash home application icon is different from app-lens icon

Status in Unity:
  Opinion
Status in unity package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 13.04 daily builds, application icon in dash home which shows 
recently used applications is the old app icon while app-lens icon is updated 
to a new one, an A with a progressbar (see the screenshot attached).
  The home application icon should be the same.

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

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


[Touch-packages] [Bug 1135745] Re: Clicking on firefox button causes unity freeze

2014-12-16 Thread Andrea Azzarone
Closing the bug due to comment #3.

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Clicking on firefox button causes unity freeze

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  On a fresh boot, clicking on the Firefox link on the sidebar in Unity
  causes Ubuntu to freeze completely. No response to anything other than
  ctrl-alt-shift-prntscr-b R-E-I-S-U all show no response. Tested in
  Gnome shell where it works fine. Using Ubuntu Tweak to clear cache has
  occasionally relieved the issue and starting from terminal with -safe-
  mode sometimes works, following which Firefox will launch as normal.
  Returned to Unity after using Firefox in Gnome-shell and freezes
  again. Running 13.04 up to date as of 1pm GMT 28/2/2013.

  I had this problem in 12.04 for some time, installing the AMD website
  FGLRX driver seemed to relieve that issue but I cannot install the AMD
  driver successfully in 13.04 as the dkms module will not build. What I
  don't understand is why Firefox should be the only application to
  exhibit this behaviour.

  Things to note:
  Have set Firefox cache to 0
  Machine is running behind transparent proxy (Squid on 12.04 server).
  Have checked file system several times.
  Have not noticed any SATA issues logged relating to this drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 19.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  AddonCompatCheckDisabled: False
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paul   2786 F pulseaudio
   /dev/snd/controlC1:  paul   2786 F pulseaudio
   /dev/snd/controlC0:  paul   2786 F pulseaudio
  BuildID: 20130226114953
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: Unavailable
  Date: Thu Feb 28 13:21:04 2013
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: LastPass - supp...@lastpass.com
  InstallationDate: Installed on 2012-09-17 (164 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  IpRoute:
   default via 10.0.0.3 dev eth0  proto static 
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.110  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MarkForUpload: True
  PrefSources:
   prefs.js
   [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js
   
[Profile]/extensions/{3e0e7d2a-070f-4a47-b019-91fe5385ba79}/defaults/preferences/defaults.js
   
[Profile]/extensions/{E0B8C461-F8FB-49b4-8373-FE32E9252800}/defaults/preferences/defaults.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=19.0/20130226114953
  RelatedPackageVersions:
   totem-mozilla 3.6.3-0ubuntu3
   gnome-shell   3.6.3.1-0ubuntu3
   rhythmbox-mozilla 2.98-0ubuntu3
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to raring on 2013-02-11 (17 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1152703] Re: compiz

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Can you
still reproduce this problem on 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  compiz

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Compiz Freeze when the last window is called to minimize, but when I
  call ALT+TAB Unity back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar  8 15:10:23 2013
  DistUpgraded: 2013-03-01 23:06:42,708 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:056d]
  InstallationDate: Installed on 2012-09-01 (188 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120405)
  MachineType: Dell Inc. Vostro 3560
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic 
root=UUID=b10ed516-fe7f-470c-98be-ec3c3e7eea0d ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-03-02 (6 days ago)
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0955JJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/17/2012:svnDellInc.:pnVostro3560:pvrA07:rvnDellInc.:rn0955JJ:rvrA00:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Vostro 3560
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.03.06-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3

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

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


[Touch-packages] [Bug 1132216] Re: Unity panel's location is noisy after wake up

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Can you
still reproduce this problem on 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Unity panel's location is noisy after wake up

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Unity panel's location is noisy after wake up. Autohide option is
  enabled. Panel works as excepted .

  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04

  unity version: 6.12.0daily13.02.19.1-0ubuntu1 0
  unity-common version: 6.12.0daily13.02.19.1-0ubuntu1 0
  unity-services version: unity-6.12.0daily13.02.19.1-0ubuntu1 0

  1. Suspend PC
  2. Wake up PC
  3. login

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity-services 6.12.0daily13.02.19.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.32  Mon Jan 14 14:41:13 
PST 2013
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-21ubuntu3)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-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
  Date: Sat Feb 23 18:17:34 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-310, 310.32, 3.8.0-6-generic, x86_64: installed
   nvidia-310, 310.32, 3.8.0-7-generic, x86_64: installed
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology Device [10b0:1401]
  InstallationDate: Installed on 2013-02-19 (3 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7379
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic 
root=UUID=9e8ed7e3-6f77-45b8-a680-11ba9095e006 ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V7.3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7379
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV7.3:bd11/13/2007:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7379:pvr2.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7379:rvr2.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr2.0:
  dmi.product.name: MS-7379
  dmi.product.version: 2.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Sat Feb 23 15:25:57 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL DELL USB Keyboard KEYBOARD, id 8
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 9
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.13.2-0ubuntu2

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

-- 

[Touch-packages] [Bug 1131861] Re: on screen keyboard does not come up when clicking the search bar of the dash

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Can you
still reproduce this problem on 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  on screen keyboard does not come up when clicking the search bar of
  the dash

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  The on screen keyboard does not come up on Nexus 7 afterfresh install
  with 20130222 image. when clicked onthe dash search box

  
  Steps:

  1. Use ubuntu-nexus7-installer to install latest raring image
  2. Click on the dash and then on the search box. 
  3. It could noticed that the virtual keyboard does not come up.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.02.19.1-0ubuntu1
  Uname: Linux 3.1.10-9-nexus7 armv7l
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: armhf
  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 Feb 22 17:10:30 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   
  InstallationDate: Installed on 2013-02-22 (0 days ago)
  InstallationMedia: Ubuntu Raring Ringtail (development branch) - armhf 
(20130222-15:11)
  Lspci:
   
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 mem=1022M@2048M 
android.commchip=0 vmalloc=512M androidboot.serialno=015d210982380a15 
video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport 
usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 
tegra_fbmem=8195200@0xabe01000 core_edp_mv=0 audio_codec=rt5640 
board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=30535679 
androidboot.bootloader=4.18 androidboot.baseband=unknown root=/dev/mmcblk0p9 ro 
console=tty0 access=m2 quiet splash
  ProcModules: zram 8348 4 - Live 0x (C)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Fri Feb 22 16:57:33 2013
  xserver.configfile: None
  xserver.devices:
   inputgpio-keysKEYBOARD, id 6
   inputelan-touchscreen TOUCHSCREEN, id 7
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-1  
LVDS-1
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: tegra

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

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


[Touch-packages] [Bug 1142322] Re: Version mismatch

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Due to
the nature of this bug I'm going to close it.

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Version mismatch

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  There is a version mismatch between the Unity package number and the
  version number reported by Unity.

  root@raring:~# apt-cache policy unity
  unity:
Installed: 6.12.0daily13.03.01-0ubuntu1
Candidate: 6.12.0daily13.03.01-0ubuntu1
Version table:
   *** 6.12.0daily13.03.01-0ubuntu1 0
  500 http://uk.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status
  root@raring:~# 
  root@raring:~# 
  root@raring:~# unity --version
  unity 6.6.0

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.03.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic x86_64
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Mar  3 15:10:16 2013
  InstallationDate: Installed on 2013-02-26 (4 days ago)
  InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 
(20121017.2)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-02-26 (4 days ago)

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

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


[Touch-packages] [Bug 1153247] Re: UNITY, arent able to close maxmised windows because the buttons wont show.

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Can you
still reproduce this problem on 14.04 or 14.10?

** Changed in: unity
   Status: New = Invalid

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

** Changed in: unity
   Status: Invalid = Won't Fix

** Changed in: unity
   Status: Won't Fix = Incomplete

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

Title:
  UNITY, arent able to close maxmised windows because the buttons wont
  show.

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  look in the screenshot, my mouse was at that point i marked, but the
  buttons wont show, this happaned in 13.04 when playing a bit with the
  settings of unity (only using built in functions), also ive installed
  cinnamon and gnome3

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

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


[Touch-packages] [Bug 1144631] Re: windows decoration buttons on the right side in raring

2014-12-16 Thread Andrea Azzarone
Ubuntu 13.04 has reached end of life and is no longer supported. Can you
still reproduce this problem on 14.04 or 14.10?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  windows decoration buttons on the right side in raring

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 13.04, window decoration buttons are on the rigth
  side of the titlebar even thought  the dconf-editor  org  gnome 
  desktop  wm  preferences  button_layout is
  close,minimize,maximize:.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.03.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
  Uname: Linux 3.8.0-9-generic i686
  ApportVersion: 2.9-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Mar  4 16:31:37 2013
  EcryptfsInUse: Yes
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-02-14 (18 days ago)

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

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


[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins

2014-12-16 Thread Didier Roche
finished to check up the packaging and code source, so apart from the
comments above, that will be a +1 for me.

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

Title:
  [MIR] grilo-plugins

Status in grilo-plugins package in Ubuntu:
  Incomplete

Bug description:
  Availability: In universe, builds on all archs

  Rational: grilo-plugins is now a dependency of totem and is hard to
  patch out. See lp:1393067

  Security: No known CVEs

  Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are
  feature requests. Active debian maintainer. Has watch file. Tests are
  run during build.

  UI standards: The package is translated upstream.

  Dependencies: All deps in main

  Standards compliance: No issues

  Maintenance: Actively maintained in debian. ubuntu-gnome team will
  subscribe in ubuntu.

  Background info: Grilo is a framework focused on making media
  discovery and browsing easy for application developers. This package
  contains it's plugins, including the tracker one, which is now needed
  by totem

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

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


[Touch-packages] [Bug 1394208] Re: Unity8 unable to find the dash, which is also running in the background

2014-12-16 Thread Gerry Boland
This bug is in our list for land for next RTM release, should happen
soon

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

Title:
  Unity8 unable to find the dash, which is also running in the
  background

Status in the base for Ubuntu mobile products:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu RTM:
  Triaged
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 165
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-11-19 00:20:27
  version version: 165
  version ubuntu: 20141118.1
  version device: 20141106-572f18d
  version custom: 20141118-439-21-159

  After doing a reboot, Unity8 started fine but the dash looked like it
  failed to start (see the attached pic). After checking for
  unity8-dash, it's actually running in the background, just that unity8
  is unable to find it.

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

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


[Touch-packages] [Bug 774290] Re: Can't switch to top-left workspace using keyboard

2014-12-16 Thread Andrea Azzarone
Ubuntu 11.04 (and 13.04) has reached end of life and is no longer
supported. Can you still reproduce this bug on a supported Ubuntu
release (12.04, 14.04, 14.10)?

** Changed in: compiz
   Status: Confirmed = Incomplete

** Changed in: unity
   Status: Confirmed = Incomplete

** Changed in: compiz (Ubuntu)
   Status: Triaged = Incomplete

** Changed in: unity (Ubuntu)
   Status: Triaged = Incomplete

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

Title:
  Can't switch to top-left workspace using keyboard

Status in Compiz:
  Incomplete
Status in Unity:
  Incomplete
Status in compiz package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: unity

  I can switch from top right to left bottom workspace, by pressing
  CTRL+ALT+DOWN+RIGHT. I can do the same to the right bottom, left
  bottom and right top, but no to the left top. When I am in the right
  bottom workspace, and I press CTRL+ALT+UP+LEFT, nothing happens (or it
  goes left or top sometimes).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.10-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.DIN.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Sat Apr 30 20:15:33 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA 
controller])
 Subsystem: ATI Technologies Inc Device [1002:0502]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: Gigabyte Technology Co., Ltd. EP35-DS3L
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic 
root=UUID=1c4098a8-56b8-4d58-af2d-7ecc388c9876 ro quiet splash vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  ProcVersionSignature__: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Renderer: Unknown
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: EP35-DS3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/02/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP35-DS3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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


[Touch-packages] [Bug 1108064] Re: HUD messes up application's Alt key bindings

2014-12-16 Thread Pete Woods
HUD itself has nothing to do with keyboard shortcuts. All the user
interaction is part of the unity project.

** Changed in: hud (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  HUD messes up application's Alt key bindings

Status in Unity:
  New
Status in blender package in Ubuntu:
  Confirmed
Status in emacs23 package in Ubuntu:
  Confirmed
Status in fcitx package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in hud package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  If Alt-key is assigned to HUD, Alt key doesn't work correctly in some
  applications.

  For example, Blender doesn't accept Alt key press at all.  See a bug
  report in Blender bug tracker for detail:

  http://projects.blender.org/tracker/?func=detailatid=498aid=33831group_id=9

  When pressing Alt key, Blender receives unnecessary FocusOut and
  FocusIn events, so Blender immediately forgets the Alt key is pressed
  down.  Blender developer was very angry with Unity's such strange
  behavior.

  In Emacs, after select a region, Alt key press sometimes cancels the
  selection unexpectedly, so I can do nothing in the region.

  
  Unity 6.12.0-0ubuntu0.2
  Ubuntu 12.10 amd64

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

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


[Touch-packages] [Bug 1395661] Re: Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

2014-12-16 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  There's a problem with Qt WebKit (5.4.0 beta) failing to build against
  Qt 5.4.0 beta on amd64: https://launchpadlibrarian.net/190809157
  /buildlog_ubuntu-vivid-amd64.qtwebkit-opensource-src_5.4.0~beta-
  0ubuntu1~vivid1~test1_FAILEDTOBUILD.txt.gz and on powerpc:
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-005/+build/6649444/+files
  /buildlog_ubuntu-vivid-powerpc.qtwebkit-opensource-
  src_5.4.0-0ubuntu1%7Evivid1%7Etest2_FAILEDTOBUILD.txt.gz

  It seems to be related to pre-compiled headers. Qttools requires
  qtwebkit for the documentation. In the test PPA I've disabled qttools'
  qtwebkit requirement in order to have more amd64 builds done in
  general.

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

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

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


[Touch-packages] [Bug 1403045] [NEW] Bottom edge doesn't follow finger

2014-12-16 Thread Michael Zanetti
Public bug reported:

* start by quickly pulling up the bottom edge but do not release the finger
* move the finger slowly up and down

= the scopes list does follow the up/down movement, but is way off from
the finger position

expected:

The top edge of the scopes list should stick to the finger's position

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

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

Title:
  Bottom edge doesn't follow finger

Status in unity8 package in Ubuntu:
  New

Bug description:
  * start by quickly pulling up the bottom edge but do not release the finger
  * move the finger slowly up and down

  = the scopes list does follow the up/down movement, but is way off
  from the finger position

  expected:

  The top edge of the scopes list should stick to the finger's position

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

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


[Touch-packages] [Bug 1394208] Re: Unity8 unable to find the dash, which is also running in the background

2014-12-16 Thread XiaoGuo, Liu
May I know roughly when this fix will go to the next RTM release? We are
currently depending on this fix to make an image. Hopefully, it could be
released soon. We will do more testing on it. Thanks!

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

Title:
  Unity8 unable to find the dash, which is also running in the
  background

Status in the base for Ubuntu mobile products:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu RTM:
  Triaged
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 165
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-11-19 00:20:27
  version version: 165
  version ubuntu: 20141118.1
  version device: 20141106-572f18d
  version custom: 20141118-439-21-159

  After doing a reboot, Unity8 started fine but the dash looked like it
  failed to start (see the attached pic). After checking for
  unity8-dash, it's actually running in the background, just that unity8
  is unable to find it.

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

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


[Touch-packages] [Bug 1403048] [NEW] clicking the departments header to collapse the list, flicks to another scope too easily

2014-12-16 Thread Michael Zanetti
Public bug reported:

I often open the departments list, but then close it again by tapping
the list header (currently selected department) again. Unlike the rest
of the menu, it does propagate touch events to the dash behind it and if
the tap does a small horizontal movement, it flicks to another scope.

expected:
The whole departments menu should consume touch events to prevent this from 
happening

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

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

Title:
  clicking the departments header to collapse the list, flicks to
  another scope too easily

Status in unity8 package in Ubuntu:
  New

Bug description:
  I often open the departments list, but then close it again by tapping
  the list header (currently selected department) again. Unlike the rest
  of the menu, it does propagate touch events to the dash behind it and
  if the tap does a small horizontal movement, it flicks to another
  scope.

  expected:
  The whole departments menu should consume touch events to prevent this from 
happening

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

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


[Touch-packages] [Bug 1400468] Re: Phone numbers are stored as formatted strings and are not found when searching

2014-12-16 Thread Renato Araujo Oliveira Filho
** Branch linked: lp:~renatofilho/address-book-app/fix-1400468-rtm

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

Title:
  Phone numbers are stored as formatted strings and are not found when
  searching

Status in Address Book App:
  In Progress
Status in the base for Ubuntu mobile products:
  Confirmed
Status in address-book-app package in Ubuntu:
  Fix Released
Status in address-book-app package in Ubuntu RTM:
  In Progress

Bug description:
  There are several problems:

  Search currently requires the user to enter a space or - character
  to find matching numbers the the contacts and messaging apps.

  Also depending on how the number is entered the formatting is different for 
example:
  19995551212 is stored and displayed as 1 999-555-1212
  whereas 
  9995551212 is displayed as (999) 555-1212

  There is no way for me to specify a formatted number when creating a contact 
so there is no real reason to store it formatted in a way we choose. 
  When editing a number I am presented with it formatted which is somewhat 
confusing, there is no - character available to me. 

  I suggest we store the raw number only and always normalize search
  strings to digits and special characters (like *#) only. The
  presentation should be considered separate from the data

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1400468/+subscriptions

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


[Touch-packages] [Bug 1403050] [NEW] Firefox profile denied messages with google hangouts

2014-12-16 Thread James Westby
Public bug reported:

Hi,

I am using apparmor on trusty, with the firefox profile in enforce mode.

I have just tried hangouts for the first time under the profile, and
there are two DENIED:

Dec 16 12:36:31 superstar kernel: [191033.672376] type=1400
audit(1418733391.061:436): apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,*[^s][^h]} name=/dev/video0
pid=19492 comm=GoogleTalkPlugi requested_mask=r denied_mask=r
fsuid=1000 ouid=0

Which means that it thinks I have no webcam. I don't know if this should be 
allowed or not. I'd prefer to enable
my webcam in a hangout, but I can see an argument for denying this to firefox.

Dec 16 12:36:37 superstar kernel: [191039.824064] type=1400
audit(1418733397.217:440): apparmor=DENIED operation=mknod
profile=/usr/lib/firefox/firefox{,*[^s][^h]} name=/run/shm/google-
nacl-shm--19492.3 pid=19492 comm=GoogleTalkPlugi requested_mask=c
denied_mask=c fsuid=1000 ouid=1000

I assume this is something to do with NaCl. I haven't noticed anything
that is broken by this.

Thanks,

James

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apparmor 2.8.95~2430-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 16 12:58:32 2014
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Firefox profile denied messages with google hangouts

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  I am using apparmor on trusty, with the firefox profile in enforce
  mode.

  I have just tried hangouts for the first time under the profile, and
  there are two DENIED:

  Dec 16 12:36:31 superstar kernel: [191033.672376] type=1400
  audit(1418733391.061:436): apparmor=DENIED operation=open
  profile=/usr/lib/firefox/firefox{,*[^s][^h]} name=/dev/video0
  pid=19492 comm=GoogleTalkPlugi requested_mask=r denied_mask=r
  fsuid=1000 ouid=0

  Which means that it thinks I have no webcam. I don't know if this should be 
allowed or not. I'd prefer to enable
  my webcam in a hangout, but I can see an argument for denying this to firefox.

  Dec 16 12:36:37 superstar kernel: [191039.824064] type=1400
  audit(1418733397.217:440): apparmor=DENIED operation=mknod
  profile=/usr/lib/firefox/firefox{,*[^s][^h]} name=/run/shm/google-
  nacl-shm--19492.3 pid=19492 comm=GoogleTalkPlugi requested_mask=c
  denied_mask=c fsuid=1000 ouid=1000

  I assume this is something to do with NaCl. I haven't noticed anything
  that is broken by this.

  Thanks,

  James

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor 2.8.95~2430-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 12:58:32 2014
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1402763] Re: Multicast traffic not propating correctly over linux bridge

2014-12-16 Thread Launchpad Bug Tracker
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/1402763

Title:
  Multicast traffic not propating correctly over linux bridge

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  There's a lot of supposition in the title of this bug but its
  currently my best guess.

  In this deployment, I have a number of services running in LXC
  containers across multiple physical hosts; each service is clustered
  across three units, all on separate physical hosts, using corosync and
  pacemaker; when using multicast to support cluster communication, I
  occasionally see a container drop out of the cluster and use its
  isolation response (to shutdown all managed services); when using
  unicast I've not yet see this same problem.

  LXC containers are bridged to the main physical network using a linux
  bridge:

eth0 - juju-br0 - vethXXX - | vethXXX |

  All MTU's are standard (1500).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 15 17:20:08 2014
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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

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

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


[Touch-packages] [Bug 1376604] Re: Could not printing from LPT port with Ubuntu

2014-12-16 Thread Till Kamppeter
ubuntuers_medan, can you also do what I have asked you for in comment
#35. Thanks.

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

Title:
  Could not printing from LPT port with Ubuntu

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I have lenovo PC edge 73z, this PC has an LPT port. I've tried to
  install Windows in this PC, and it's printing well from LPT, but whe I
  reinstall it with ubuntu 12.04, 13.04, and 14.04, it would not work.

  When I try to add print, it's detecting my printing such as LQ310 and
  LQ2180, but in Printing Tes steps, it can't printing.

  I've also tried to print with the same print and with the same OS but
  at this time via USB, it working well.

  Please, any one have the solution for me?
  ---
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-05-16 (209 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: LENOVO 10AS005HIA
  Package: cups 1.7.2-0ubuntu1.3
  PackageArchitecture: i386
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=444b6b19-2130-4de3-ba34-a24b9f65fb00 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=444b6b19-2130-4de3-ba34-a24b9f65fb00 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Tags: third-party-packages trusty package-from-proposed
  Uname: Linux 3.13.0-35-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FCKT46AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: NOK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrFCKT46AUS:bd12/16/2013:svnLENOVO:pn10AS005HIA:pvrThinkCentreE73:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10AS005HIA
  dmi.product.version: ThinkCentre E73
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1231478] Re: Automatic scrolling of the preview when the keyboard is shown is broken

2014-12-16 Thread Thomas Strehl
** Changed in: unity8 (Ubuntu)
 Assignee: Diego Sarmentero (diegosarmentero) = Rodney Dawes (dobey)

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

Title:
  Automatic scrolling of the preview when the keyboard is shown is
  broken

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  The component with the focus should be placed above the keyboard, and
  the flickable area should be properly calculated, right now a margin
  is added between the bottom of the flickable area and the keyboard.

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

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


[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk

2014-12-16 Thread Didier Roche
Actually, this is not a systemd behavior but seems to be a syslog one.
1. rm /var/log/syslog
2. reboot
- no log (under systemd or upstart)
3. touch /var/log/syslog
4. chmod syslog:adm /var/log/syslog
5. reboot
- logs availables

The cause is that /var/log is 755 and root:syslog (I wonder why it's in syslog 
group as it's not 775?), and so can't recreate the file.
If I chmod syslog, indeed, /var/log/syslog is created, but with other rights, 
being syslog:syslog instead of syslog:adm.

So, it worths more discussion (retargetting to syslog), pinging Martin
on this.


** Package changed: systemd (Ubuntu) = rsyslog (Ubuntu)

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

Title:
  non persistent logging after cleaning log files on disk

Status in systemd package in Ubuntu:
  New

Bug description:
  Using current vivid with systemd init, I've cleaned the log on disk
  (*.log syslog dmesg) and rebooted my test box, since then it stopped
  logging to syslog.

  journalctl has the log from the current boot but not from previous
  ones

  the behaviour there is a bit confusing, I first though that I would
  get a fresh syslog on next boot and not an auto conversion to use
  journald, then the journal should keep record from previous boots as
  well...

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

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


[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk

2014-12-16 Thread Martin Pitt
rsyslog's postinst seems fine. I have a gut feeling that this is due to
/usr/lib/tmpfiles.d/var.conf changing it back to 0755, the permissions
are wrong there.

** Package changed: rsyslog (Ubuntu) = systemd (Ubuntu)

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

Title:
  non persistent logging after cleaning log files on disk

Status in systemd package in Ubuntu:
  New

Bug description:
  Using current vivid with systemd init, I've cleaned the log on disk
  (*.log syslog dmesg) and rebooted my test box, since then it stopped
  logging to syslog.

  journalctl has the log from the current boot but not from previous
  ones

  the behaviour there is a bit confusing, I first though that I would
  get a fresh syslog on next boot and not an auto conversion to use
  journald, then the journal should keep record from previous boots as
  well...

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

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


[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk

2014-12-16 Thread Martin Pitt
Ah, our rsyslog has a delta, so let's stick a matching tmpfiles.d/
snippet into rsyslog.

** Package changed: systemd (Ubuntu) = rsyslog (Ubuntu)

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

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

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

Title:
  non persistent logging after cleaning log files on disk

Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  Using current vivid with systemd init, I've cleaned the log on disk
  (*.log syslog dmesg) and rebooted my test box, since then it stopped
  logging to syslog.

  journalctl has the log from the current boot but not from previous
  ones

  the behaviour there is a bit confusing, I first though that I would
  get a fresh syslog on next boot and not an auto conversion to use
  journald, then the journal should keep record from previous boots as
  well...

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

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


[Touch-packages] [Bug 943162] Re: libgl1-mesa-dev links libGL.so to mesa/libGL.so which conflicts with nvidia's libGL.

2014-12-16 Thread Denis Bernard
Same issue with libgles1-mesa-dev and libgles2-mesa-dev in 14.04

As a workaround, it is safe to remove the following:

/usr/lib/x86_64-linux-gnu/libGL.so
/usr/lib/x86_64-linux-gnu/libEGL.so
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so
/usr/lib/x86_64-linux-gnu/libGLESv2.so

Then run ldconfig

This only affects programs that try to dlopen() lib*GL*.so instead of
lib*GL*.so.1 (like Factor)

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

Title:
  libgl1-mesa-dev links libGL.so to mesa/libGL.so which conflicts with
  nvidia's libGL.

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  It seems like libgl1-mesa-dev creates the symbolic link
  /usr/lib/x86_64-linux-gnu/libGL.so, pointing to mesa/libGL.so. This
  conflicts with NVidia's libGL.so and ignores the alternative settings.
  For instance, a call to dlopen will load the mesa library instead of
  the nvidia library. This is in particular a problem when using OpenGL
  in dynamic languages such as Python or Common Lisp since they foreign
  function interfaces use something like dlopen.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libgl1-mesa-dev 7.11-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-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  280.13  Wed Jul 27 16:53:56 
PDT 2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,grid,vpswitch,resize,imgpng,snap,regex,animation,workarounds,mousepoll,expo,place,move,gnomecompat,unitymtgrabhandles,wall,ezoom,session,fade,scale,unityshell]
  CompositorRunning: None
  Date: Wed Feb 29 11:13:06 2012
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current-updates, 280.13, 3.0.0-16-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   nVidia Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:827c]
  JockeyStatus:
   xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, 
Not in use)
   xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Disabled, Not in use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Enabled, In use)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=de_DE.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic 
root=UUID=cc3cd9ea-6f90-44c3-a6e8-67758cff1603 ro splash quiet vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M3N78 PRO ACPI BIOS Revision 0801
  dmi.board.name: M3N78 PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N78PROACPIBIOSRevision0801:bd03/27/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78PRO:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1
  version.ia32-libs: ia32-libs 20090808ubuntu26
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1403057] [NEW] lightdm starts with blank screen

2014-12-16 Thread Sezer Yalcin
Public bug reported:

laptop boots fine but with blank screen.
ctrl+alt+f1 switches to terminal 1 with text login

Then doing trl+alt+f7 switches back to login screen with graphics and has no 
issues.
Login and everything else works fine afterwards.

Some mentioned SSD may cause this and I experimented with some delays i
lightdm.conf but didn't change anything.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 16 15:31:24 2014
InstallationDate: Installed on 2012-11-11 (765 days ago)
InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120817.3)
LightdmConfig:
 [SeatDefaults]
 greeter-session=unity-greeter
 user-session=ubuntu
SourcePackage: lightdm
UpgradeStatus: Upgraded to trusty on 2014-10-17 (59 days ago)
mtime.conffile..etc.init.lightdm.conf: 2014-12-16T13:06:43.188021

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


** Tags: amd64 apport-bug trusty

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

Title:
  lightdm starts with blank screen

Status in lightdm package in Ubuntu:
  New

Bug description:
  laptop boots fine but with blank screen.
  ctrl+alt+f1 switches to terminal 1 with text login

  Then doing trl+alt+f7 switches back to login screen with graphics and has no 
issues.
  Login and everything else works fine afterwards.

  Some mentioned SSD may cause this and I experimented with some delays
  i lightdm.conf but didn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 15:31:24 2014
  InstallationDate: Installed on 2012-11-11 (765 days ago)
  InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120817.3)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-10-17 (59 days ago)
  mtime.conffile..etc.init.lightdm.conf: 2014-12-16T13:06:43.188021

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

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


[Touch-packages] [Bug 1395877] Re: overlay: need to sort out overlayfs backwards compatibility

2014-12-16 Thread Andy Whitcroft
Kernel fixes applied under this bug.

schroot fixes applied under bug #1398523.

casper fixes applied under bug #1401620.

** Changed in: util-linux (Ubuntu)
   Status: In Progress = Invalid

** Changed in: linux (Ubuntu)
Milestone: ubuntu-14.11 = ubuntu-14.12

** Changed in: util-linux (Ubuntu)
Milestone: ubuntu-14.11 = ubuntu-14.12

** Changed in: util-linux (Ubuntu)
Milestone: ubuntu-14.12 = None

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

Title:
  overlay: need to sort out overlayfs backwards compatibility

Status in linux package in Ubuntu:
  Fix Committed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  We have some on disk format issues with overlay (the new upstreamed
  version of overlayfs).  This bug is for tracking work and packages
  affected by this.

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

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


[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk

2014-12-16 Thread Martin Pitt
** Changed in: rsyslog (Ubuntu)
   Importance: Undecided = High

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

** Tags added: systemd-boot

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

Title:
  non persistent logging after cleaning log files on disk

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  Using current vivid with systemd init, I've cleaned the log on disk
  (*.log syslog dmesg) and rebooted my test box, since then it stopped
  logging to syslog.

  journalctl has the log from the current boot but not from previous
  ones

  the behaviour there is a bit confusing, I first though that I would
  get a fresh syslog on next boot and not an auto conversion to use
  journald, then the journal should keep record from previous boots as
  well...

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

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


[Touch-packages] [Bug 1394155] Re: Crash of unity8-dash possible through Today scope

2014-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scopes-shell -
0.5.4+15.04.20141210~rtm-0ubuntu1

---
unity-scopes-shell (0.5.4+15.04.20141210~rtm-0ubuntu1) 14.09; urgency=low

  [ Pete Woods ]
  * Fix today scope crash (LP: #1394155)

  [ Pawel Stolowski ]
  * Read /custom/partner-id value (if present) and pass it with user-
agent hint. (LP: #1389273)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Wed, 10 Dec 2014 
16:46:01 +

** Changed in: unity-scopes-shell (Ubuntu RTM)
   Status: New = Fix Released

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

Title:
  Crash of unity8-dash possible through Today scope

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu RTM:
  Fix Released

Bug description:
  On krillin r165:

  1) Go to the Today scope
  2) Scroll to the bottom
  3) Tap Tell me more...
  4) Scroll to the bottom again
  5) Tap Finished

  Crash!

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

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


[Touch-packages] [Bug 1389273] Re: Track app sales per partner

2014-12-16 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scopes-shell -
0.5.4+15.04.20141210~rtm-0ubuntu1

---
unity-scopes-shell (0.5.4+15.04.20141210~rtm-0ubuntu1) 14.09; urgency=low

  [ Pete Woods ]
  * Fix today scope crash (LP: #1394155)

  [ Pawel Stolowski ]
  * Read /custom/partner-id value (if present) and pass it with user-
agent hint. (LP: #1389273)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Wed, 10 Dec 2014 
16:46:01 +

** Changed in: unity-scopes-shell (Ubuntu RTM)
   Status: Triaged = Fix Released

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

Title:
  Track app sales per partner

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Pay UI:
  Fix Committed
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu RTM:
  New
Status in unity-scopes-shell package in Ubuntu RTM:
  Fix Released

Bug description:
  We need to track what app sales come from which partner, by sending
  the partner string when performing a purchase.

  For documentation on what the server expects, see:
  https://wiki.ubuntu.com/AppStore/Interfaces/Purchases#purchases

  The code for each partner needs to be specified in the OEM image.

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

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


[Touch-packages] [Bug 1402666] Re: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] Playback problem

2014-12-16 Thread David Chatterton
Here we go again!

Whislt playing a video through Videos with the sound playing over the
speakers, I turned on a pair of Bluetooth hadphones. Sure enough, the
headphones' menu item appeared in the Systems Settings  Souund pane. I
needed to hightlight the item to get the sound through the headphones. I
then turned off the headphones. The headphones' menu item disappeared
and the Speakers item was highlighted. However, there was no sound
through the speakers. Even clicking on the menu item failed to produce
any sound.

Plugging a pair of wired headphones caused their menu item to appear but
no sound at all, even after clicking the menu item.

I can only assume that the sound system had crashed!

I did a restart and got the sound working again.

Unfortunately, the system is still unstable.

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

Title:
  [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  If an HDMI monitor is plugged into the video out and the Videos app is
  started, the Systems Settings  Sound  Output shows only the
  Speakers, Built-in Audio in the Play sound through listing. The HDMI
  option is not presented.

  The workaround is to open the VLC app which lists the Built-in Stereo (HDMI) 
option under its Audio  Audio Devices menu.
   
  When a video is started in VLC, having selected the HDMI option, the sound 
plays through the monitor speakers. The HDMI / Display Port , Built-in Audio 
item then appears in the Play sound through window, even though the selection 
highlight remains on Speakers. The sound output can be switched between either 
output by highlighting the chosen option.

  If VLC is closed and Videos is restarted, the sound now plays through
  the previously selected HDMI item and can be switched between the
  monitor and the laptop's speakers.

  What I regard as a bug is the failure of the HDMI option to appear in
  the Play sound through listing as soon as an HDMI monitor is plugged
  into the Display Port output. Obviously, VLC has the means to add this
  item but the Videos app does not seem to be able to do this by itself.

  In contrast, as soon as a previously paired set of Bluetooth headphone
  are turned on, the Headset does appear as a menu item in the listing.
  I would reasonably expect the plugging in of an HDMI monitor into the
  Display Port to automatically add this item as well as its affects on
  the Screen Display pane of Systems Settings.

  Note: the laptop is running Ubuntu 14.10 and the Linux kernel has
  recently been upgraded to v3.18 (Vivid).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.18.0-031800-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   david  2242 F...m pulseaudio
   /dev/snd/controlC1:  david  2242 F pulseaudio
   /dev/snd/controlC0:  david  2242 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Dec 15 13:13:47 2014
  InstallationDate: Installed on 2014-12-11 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: Upgraded to utopic on 2014-12-11 (3 days ago)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1403045] Re: Bottom edge doesn't follow finger

2014-12-16 Thread Albert Astals Cid
** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Albert Astals Cid (aacid)

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

Title:
  Bottom edge doesn't follow finger

Status in unity8 package in Ubuntu:
  New

Bug description:
  * start by quickly pulling up the bottom edge but do not release the finger
  * move the finger slowly up and down

  = the scopes list does follow the up/down movement, but is way off
  from the finger position

  expected:

  The top edge of the scopes list should stick to the finger's position

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

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


[Touch-packages] [Bug 1403048] Re: clicking the departments header to collapse the list, flicks to another scope too easily

2014-12-16 Thread Albert Astals Cid
** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Albert Astals Cid (aacid)

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

Title:
  clicking the departments header to collapse the list, flicks to
  another scope too easily

Status in unity8 package in Ubuntu:
  New

Bug description:
  I often open the departments list, but then close it again by tapping
  the list header (currently selected department) again. Unlike the rest
  of the menu, it does propagate touch events to the dash behind it and
  if the tap does a small horizontal movement, it flicks to another
  scope.

  expected:
  The whole departments menu should consume touch events to prevent this from 
happening

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

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


[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk

2014-12-16 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/rsyslog

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

Title:
  non persistent logging after cleaning log files on disk

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  Using current vivid with systemd init, I've cleaned the log on disk
  (*.log syslog dmesg) and rebooted my test box, since then it stopped
  logging to syslog.

  journalctl has the log from the current boot but not from previous
  ones

  the behaviour there is a bit confusing, I first though that I would
  get a fresh syslog on next boot and not an auto conversion to use
  journald, then the journal should keep record from previous boots as
  well...

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

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


[Touch-packages] [Bug 1394208] Re: Unity8 unable to find the dash, which is also running in the background

2014-12-16 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Importance: High = Critical

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

Title:
  Unity8 unable to find the dash, which is also running in the
  background

Status in the base for Ubuntu mobile products:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu RTM:
  Triaged
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 165
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-11-19 00:20:27
  version version: 165
  version ubuntu: 20141118.1
  version device: 20141106-572f18d
  version custom: 20141118-439-21-159

  After doing a reboot, Unity8 started fine but the dash looked like it
  failed to start (see the attached pic). After checking for
  unity8-dash, it's actually running in the background, just that unity8
  is unable to find it.

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

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


[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk

2014-12-16 Thread Didier Roche
Note that the bug will still be present under upstart, but nothing new,
for reference: http://irclogs.ubuntu.com/2014/12/16/%23ubuntu-
desktop.html#t13:10 :)

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

Title:
  non persistent logging after cleaning log files on disk

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  Using current vivid with systemd init, I've cleaned the log on disk
  (*.log syslog dmesg) and rebooted my test box, since then it stopped
  logging to syslog.

  journalctl has the log from the current boot but not from previous
  ones

  the behaviour there is a bit confusing, I first though that I would
  get a fresh syslog on next boot and not an auto conversion to use
  journald, then the journal should keep record from previous boots as
  well...

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

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


[Touch-packages] [Bug 1319146] Re: new installation of 14.04LTS, no panel or launcher

2014-12-16 Thread ealthuis
ea@vostro:~$ ps aux | grep nautilus
ea3680  0.0  0.0  11744   904 pts/0S+   05:59   0:00 grep 
--color=auto nautilus
ea@vostro:~$ 

ea@vostro:~$ gsettings get org.gnome.desktop.background show-desktop-icons
false
ea@vostro:~$

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

Title:
  new installation of 14.04LTS, no panel or launcher

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  In reference to bug # 2304568, lost launcher and panel in 14.04LTS
  Beta2,

  I ended up sending the motherboard for repairs.  This has been
  repaired and installed as of today.  I also installed a brand new
  120GB SSD upon which I installed a newly downloaded version od
  14.04LTS.  I kept my /home on another drive, but for that it is
  essentially a new installation.  System started, asked for password
  and at that time the panel was visible with date, time and the
  shutdown button.  After entering password system came up without
  launcher and also without panel.  I changed density on the screen just
  incase launcher was off the screen, no luck.

  This now has become a serious problem, as I cannot acces any of the
  files on my hard diks, nor can I use this system for any work.

  I also do not know how I can send any bug info other than this
  description, I have no access to Terminal, only all settings is
  available and all icons do their job when requested.

  I would really appreciate it if this were looked in quickly.
  ---
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2014-05-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. B85-HD3
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=6a5180e0-a20b-4d2e-8d18-f6b95e329bd7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Tags:  trusty trusty trusty ubuntu
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B85-HD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May 13 13:38:58 2014
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Touch-packages] [Bug 1398525] Re: Proximity sensor should not control the screen when using an earphone/headset

2014-12-16 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Confirmed = Fix Released

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

Title:
  Proximity sensor should not control the screen when using an
  earphone/headset

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Telepathy Ofono:
  New
Status in dialer-app package in Ubuntu:
  Fix Released
Status in telepathy-ofono package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu RTM:
  Fix Released
Status in telepathy-ofono package in Ubuntu RTM:
  Fix Released

Bug description:
  Use a wired earphone or headset on a call

  The proximity sensor still turns the screen off

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

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


[Touch-packages] [Bug 1090006] Re: Dash home gives bogus results when there are no matches for a search string

2014-12-16 Thread Michael Terry
Nope, this got fixed, thanks!

** Changed in: unity (Ubuntu)
   Status: Incomplete = Fix Released

** Changed in: unity
   Status: Incomplete = Fix Released

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

Title:
  Dash home gives bogus results when there are no matches for a search
  string

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  1) Open the Dash
  2) Search for a nonsense string like lkadjflkajdlfjald

  You'll notice that the only results are a full set of Files 
  Folders as if I had not searched at all.  But these files and folders
  should not appear at all, as if they matched my search.

  Instead, I'd expect an error message of some such, as I get when
  search on one of the other lenses and no results appear.

  This may be a bug in the files lens instead of unity, I wasn't sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily12.12.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-6.14-generic 3.7.0
  Uname: Linux 3.7.0-6-generic i686
  ApportVersion: 2.7-0ubuntu2
  Architecture: i386
  CheckboxSubmission: 9a284f3f6b4f7829abbe27ad9573a709
  CheckboxSystem: 3935143777c965daaa64b51f0134f712
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Dec 13 10:57:35 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-04-22 (601 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110422)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1382843] Re: uoa publishing on flickr, corrupted double-linked list error

2014-12-16 Thread Chris J Arges
Hello Mike, or anyone else affected,

Accepted libsignon-glib into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/libsignon-
glib/1.10daily13.06.25-0ubuntu3 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!

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

** Also affects: libsignon-glib (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: shotwell (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: libsignon-glib (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** No longer affects: shotwell (Ubuntu Trusty)

** No longer affects: shotwell (Ubuntu Utopic)

** Changed in: libsignon-glib (Ubuntu Trusty)
   Status: New = Fix Committed

** Tags added: verification-needed

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

Title:
  uoa publishing on flickr, corrupted double-linked list error

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in shotwell package in Ubuntu:
  In Progress
Status in libsignon-glib source package in Trusty:
  Fix Committed
Status in libsignon-glib source package in Utopic:
  New

Bug description:
  * Impact
  Trying to upload photos makes shotwell hit a segfault

  * Test case
  Try to publish a photo to an online configured through online-accounts

  * Regression potential
  Check that you can add and use online accounts without issues (in shotwell 
and other unity7 desktop components)

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

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


[Touch-packages] [Bug 1382843] Re: uoa publishing on flickr, corrupted double-linked list error

2014-12-16 Thread Chris J Arges
So I noticed libsignon-glib was uploaded for Trusty, but not Utopic. Can
this fix be uploaded there?

** No longer affects: libsignon-glib (Ubuntu Utopic)

** Also affects: shotwell (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: libsignon-glib (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

Title:
  uoa publishing on flickr, corrupted double-linked list error

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in shotwell package in Ubuntu:
  In Progress
Status in libsignon-glib source package in Trusty:
  Fix Committed
Status in libsignon-glib source package in Utopic:
  New
Status in shotwell source package in Utopic:
  New

Bug description:
  * Impact
  Trying to upload photos makes shotwell hit a segfault

  * Test case
  Try to publish a photo to an online configured through online-accounts

  * Regression potential
  Check that you can add and use online accounts without issues (in shotwell 
and other unity7 desktop components)

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

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


  1   2   3   >