[Touch-packages] [Bug 195280] Re: libglut3 not needed for ubuntu-desktop

2014-09-06 Thread Mathew Hodson 
ubuntu-desktop doesn't depend on freeglut3 since at least trusty.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  libglut3 not needed for ubuntu-desktop

Status in “ubuntu-meta” package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-desktop depends on freeglut3. I can't find any programs that
  are installed by default that need freeglut.

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

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

[Touch-packages] [Bug 235327] Re: ubuntu-desktop recommends linux-headers-generic

2014-09-06 Thread Mathew Hodson 
ubuntu-desktop does not recommend linux-headers-generic since at least
trusty.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  ubuntu-desktop recommends linux-headers-generic

Status in “ubuntu-meta” package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-desktop should not recommend linux-headers-generic, since not everyone 
use that kernel.
  For instance, since I run ubuntu inside a vmware virtual machine, I use the 
linux-virtual kernel instead of the linux-generic kernel. So for me the 
linux-headers-generic package is useless, and should be substituted with the 
linux-headers-virtual package.
  I think ubuntu-desktop should recommend ONE among linux-headers-* packages 
(which could be for instance linux-headers-generic, linux-headers-virtual, 
linux-headers-server, linux-headers-xen and so on...)
  In other words, installing either of these packages should satisfy the 
ubuntu-desktop recommendation.

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

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

[Touch-packages] [Bug 387284] Re: Please downgrade gnome-terminal from a dependency to a recommendation

2014-09-06 Thread Mathew Hodson 
ubuntu-desktop only recommends gnome-terminal since at least trusty.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Please downgrade gnome-terminal from a dependency to a recommendation

Status in “ubuntu-meta” package in Ubuntu:
  Fix Released

Bug description:
  Pleaes downgrfade gnome-termina from a dependency to a recommendation.
  There are a couple other libgnome terminals available, and those users
  who are particular about terminals tend to be very much so, to the
  point of only wanting one terminal application present in the menus.
  Given that using a terminal is ideally not a core component of the
  Ubuntu Desktop experience, users ought be provided with the same
  flexibilitity provided with games, web browsers, media players, or
  similar vertical solutions.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Jun 15 21:38:57 2009
  DistroRelease: Ubuntu 9.10
  Package: ubuntu-desktop 1.143
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
  SourcePackage: ubuntu-meta
  Uname: Linux 2.6.30-8-generic i686

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

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

[Touch-packages] [Bug 262506] Re: The description of the package 'ubuntu-desktop' is grossly missleading

2014-09-06 Thread Mathew Hodson 
The description is different now.

This package depends on all of the packages in the Ubuntu desktop
system.

It is also used to help ensure proper upgrades, so it is recommended
that it not be removed.

Combined with comment #1, I think that satisfies this bug.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  The description of the package 'ubuntu-desktop' is grossly missleading

Status in “ubuntu-meta” package in Ubuntu:
  Fix Released

Bug description:
  [Ubuntu 8.04.1]
  Synaptic says: The Ubuntu desktop system: The DEB program package 
'ubuntu-desktop' depends on all of the packages in the Ubuntu desktop system. 
It is also used to help ensure proper upgrades. So it is recommended that it 
not be removed.
  This is grossly misleading to users who do not know much about this package.
  Replace the first sentence with: The DEB program package 'ubuntu-desktop' 
comprises solely dependency relations to packages in the Ubuntu desktop system.
  Replace the third sentence with: So it is recommended that you re-install it 
before you start an upgrade of your operating system.
  (Readers should be aware that the installation of certain packages 
de-installs ubuntu-desktop. For example, tpb.)

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

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

[Touch-packages] [Bug 122039] Re: ubuntu-desktop should not depend on xsane or espeak

2014-09-06 Thread Mathew Hodson 
None of the packages mentioned in this bug are dependencies of ubuntu-
desktop since at least trusty.

** Summary changed:

- Unnecessary packages in ubuntu-desktop dependencies?
+ ubuntu-desktop should not depend on xsane or espeak

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  ubuntu-desktop should not depend on xsane or espeak

Status in “ubuntu-meta” package in Ubuntu:
  Fix Released

Bug description:
  *** Please do not add new package names to this bug when you think
  ubuntu-desktop shouldn't depend on them. File a new bug instead. This
  has been a public service announcement. ***

  Hello! This is an exploratory bug report. It is based on Gutsy,
  which I'm using right now, but probably applies to the older versions
  too.

  I've just noticed ubuntu-desktop depends on the xsane and espeak
  packages. These two are packages I have never, ever used, and I
  suspect this is true for the vast majority of users.

  I understand out-of-the-box compatibility with scanners and screen-
  readers are desirable qualities for Ubuntu, but isn't there another
  way? Perhaps putting them as Recommends dependencies would work;
  espeak could be part of an ubuntu-accessibility package, installed
  by default, and xsane could maybe be automatically-installed when a
  scanner is detected.

  The problem is that unnecessary packages not only occupy space, but
  can cause problems too (I've recently have trouble with the GIMP,
  which I use only on digital-camera pictures, not starting up, and
  xsane is the suspect; yes, I know it's a development release, and I
  can handle it, but still). And removing them is a problem, too,
  because (useful) additions to ubuntu-desktop will not be noticed.

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

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

[Touch-packages] [Bug 1365755] Re: keyboard input method system not available from keyboard configuration in gnome-control-center

2014-09-06 Thread Mathew Hodson 
** Package changed: ubuntu-meta (Ubuntu) = gnome-control-center
(Ubuntu)

** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  keyboard input method system not available from keyboard configuration
  in gnome-control-center

Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “language-selector” package in Ubuntu:
  Confirmed
Status in “unity-control-center” package in Ubuntu:
  Confirmed

Bug description:
  The setting for the keyboard input system is not available in the only
  place where it should be set. It is only available instead in the
  separate application gnome-language-selector which has an icon in the
  gnome-control-center but is labeled as Language Support.

  This caused pain to me and a lot of other users because of the
  installation and default activation of iBus in 14.04. (​see #1365752).
  It took me a long time to find that the setting is in gnome-language-
  selector, and I've discovered just now, filing this bug, that there is
  a way to access it from the control center. 30 minutes ago I would
  have titled the bug just keyboard input method not available in
  control center.

  - Language Support should deal with the selection of a language. Setting 
the behaviour of the keyboard here is inappropriate.
  - Keyboard should deal with the configuration of the keyboard. A setting 
that changes the behaviour of the keyboard such as the input method should be 
available here.

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

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

[Touch-packages] [Bug 589518] Re: Error activating XKB configuration

2014-09-06 Thread Mathew Hodson 
*** This bug is a duplicate of bug 524406 ***
https://bugs.launchpad.net/bugs/524406

** Package changed: ubuntu-meta (Ubuntu) = libxklavier (Ubuntu)

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

Title:
  Error activating XKB configuration

Status in “libxklavier” package in Ubuntu:
  New

Bug description:
  On login to ubuntu-desktop this appears:

  Error activating XKB configuration
  It can happen under various circumstances:
  - a bug in libxklavier library
  - a bug in X server (xkbcomp, xmodmap utilities)
  - X server with incompatible libxkbfile implementation

  X server version data:
  The X.Org Foundation
  10706000

  If you report this situation as a bug, please include:
  - The result of xprop -root | grep XKB
  - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd

  
  Here is the requested information:
  zie@zulubuntu ~ % xprop -root | grep XKB
  _XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105, us, mac, 
lv3:ralt_switch
  _XKB_RULES_NAMES(STRING) = evdev, pc105, us, mac, lv3:ralt_switch

  zie@zulubuntu ~ %  gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
   layouts = []
   options = [lv3 lv3:ralt_switch]
   model = macbook78

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: ubuntu-desktop 1.197
  ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: wl nvidia
  Architecture: amd64
  Date: Thu Jun  3 20:48:50 2010
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubuntu-meta

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

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

[Touch-packages] [Bug 1366277] [NEW] After restarting incorrect time is displayed

2014-09-06 Thread Gaurav Sahu 
Public bug reported:

Every time i shutdown my system and later i start i found that incorrect
time is being displayed. so i need to change it manually. again when i
shutdown and start my system same problem happens.

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

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

Title:
  After restarting incorrect time is displayed

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Every time i shutdown my system and later i start i found that
  incorrect time is being displayed. so i need to change it manually.
  again when i shutdown and start my system same problem happens.

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

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

[Touch-packages] [Bug 1366206] Re: Graphical desktop not starting from livesession

2014-09-06 Thread Elfy 
** Description changed:

  Boot live session - choose Try
+ 
+ Same issue with at least Ubuntu and Xubuntu
  
  No desktop, black screen - change to vt1 - run loginctl show-seat seat0
  gives CanGraphical=no
  
  run startx and desktop boots
  
  this is in a vm on a machine using nvidia card and 331-updates
  
  appears similar to lp:1365336
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.343
  Date: Fri Sep  5 21:40:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Graphical desktop not starting from livesession

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Boot live session - choose Try

  Same issue with at least Ubuntu and Xubuntu

  No desktop, black screen - change to vt1 - run loginctl show-seat
  seat0 gives CanGraphical=no

  run startx and desktop boots

  this is in a vm on a machine using nvidia card and 331-updates

  appears similar to lp:1365336

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.343
  Date: Fri Sep  5 21:40:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1308169] Re: apport-bug on .crash file does not send report

2014-09-06 Thread Matthias Andree 
** Tags added: regression-release

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

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

Title:
  apport-bug on .crash file does not send report

Status in “apport” package in Ubuntu:
  Confirmed

Bug description:
  When giving apport-bug a .crash file and telling it to send the
  report, it writes an empty .upload file, but does not appear to send
  the report:

  ryan@feh:~$ sudo apport-bug /var/crash/_usr_lib_squid3_pinger.0.crash

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (63.2 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s
  ryan@feh:~$ ls -lsa /var/crash/_usr_lib_squid3_pinger.0.*
  64 -rw-r- 1 root root 63854 Apr 15 10:33 
/var/crash/_usr_lib_squid3_pinger.0.crash
   0 -rw-r--r-- 1 root root 0 Apr 15 10:44 
/var/crash/_usr_lib_squid3_pinger.0.upload
  ryan@feh:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportLog:
   ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: called for pid 10115, 
signal 11, core limit 0
   ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: executable: 
/usr/lib/squid3/pinger (command line (pinger))
   ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: wrote report 
/var/crash/_usr_lib_squid3_pinger.0.crash
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:0:0:16086:2014-04-12 19:58:08.832940604 -0700:2014-04-13 
03:55:12.546230475 -0700:/var/crash/_usr_lib_mailman_bin_list_lists.0.crash
   640:0:0:63854:2014-04-15 10:33:06.036259174 -0700:2014-04-15 
10:36:21.278098132 -0700:/var/crash/_usr_lib_squid3_pinger.0.crash
   644:0:0:0:2014-04-15 10:36:23.354031253 -0700:2014-04-15 10:36:23.354031253 
-0700:/var/crash/_usr_lib_squid3_pinger.0.upload
   640:33:33:982302:2014-04-12 19:47:16.481460672 -0700:2014-04-13 
03:55:12.478232672 -0700:/var/crash/_usr_bin_php5.33.crash
   640:0:0:42350107:2014-04-15 05:24:07.978228219 -0700:2014-04-15 
05:23:28.267508485 -0700:/var/crash/_usr_sbin_apache2.0.crash
  Date: Tue Apr 15 10:40:38 2014
  InstallationDate: Installed on 2012-04-17 (728 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Beta amd64 
(20120415)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-04-13 (2 days ago)

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

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

[Touch-packages] [Bug 1310316] Re: Text scaling factor changing unexpectedly

2014-09-06 Thread herbaman 
This also affects or maybe affected me. I think the problem appears
because the x server does not set the right dpi value - and for some
reason the text-scale factor keeps to be reseted from time to time,
maybe because of an update.

I manually set the correct dpi value of my screen (122dpi) in 
/etc/lightdm/lightdm.conf with adding this line:
xserver-command=X -dpi 122

and restartet the x-server. 
Xorg.0.log now says: [  3033.310] (++) intel(0): DPI set to (122, 122) - this 
was (96, 96) before 
The Text-scale factor has been set to a usable value after that.

Maybe some of you can try this as well (with your individual dpi
settings for your monitor) to see if this really fixes the problem.

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

Title:
  Text scaling factor changing unexpectedly

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have a MacBook pro with a Retina display. I have set the Scale for
  menu and title bars  setting (into Settings  Displays) to 1.5 to
  make the UI looks good on my screen. That works very well. But
  sometimes, usually after logging, all the fonts of the UI become much
  bigger.

  When that happen I open unity tweat tool and notice that the text
  scaling factor changed to 2.25. If I reset it to 1 the all the fonts
  go back to normal.

  The problem does not happen all the time. I would say it happen one
  time out of three logging. It may also happen when installing
  applications from the software center. I have yet to find a procedure
  to reproduce it all the times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 20 18:21:02 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00f2]
  InstallationDate: Installed on 2014-04-19 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac 
(20140417)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=3d5a4115-5e15-4eca-bd1c-0bee2543a1cb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Apr 20 18:04:05 2014
  xserver.configfile: default
  xserver.errors: open

[Touch-packages] [Bug 1366280] [NEW] ubuntu-desktop should recommend activity-log-manager instead of activity-log-manager-control-center

2014-09-06 Thread Mathew Hodson 
Public bug reported:

activity-log-manager-control-center is a transitional package, so
ubuntu-desktop shouldn't recommend it.

It should recommend activity-log-manager instead, which is the single
dependency of activity-log-manager-control-center.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-desktop 1.325
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep  6 03:45:03 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-11-01 (674 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago)

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

Title:
  ubuntu-desktop should recommend activity-log-manager instead of
  activity-log-manager-control-center

Status in “ubuntu-meta” package in Ubuntu:
  New

Bug description:
  activity-log-manager-control-center is a transitional package, so
  ubuntu-desktop shouldn't recommend it.

  It should recommend activity-log-manager instead, which is the single
  dependency of activity-log-manager-control-center.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop 1.325
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep  6 03:45:03 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-01 (674 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago)

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

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

[Touch-packages] [Bug 1366278] Re: upowerd crashed with SIGSEGV in strlen()

2014-09-06 Thread Apport retracing service 
*** This bug is a duplicate of bug 1334827 ***
https://bugs.launchpad.net/bugs/1334827

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1366278/+attachment/4196916/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1366278/+attachment/4196918/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1366278/+attachment/4196919/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1366278/+attachment/4196920/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1366278/+attachment/4196921/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1366278/+attachment/4196922/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1366278/+attachment/4196923/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1334827

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  upowerd crashed with SIGSEGV in strlen()

Status in “upower” package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: upower 0.9.23-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep  2 18:06:10 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-03-04 (185 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7fdad0bd84fa strlen+42:movdqu (%rax),%xmm12
   PC (0x7fdad0bd84fa) ok
   source (%rax) (0x) not located in a known VMA region (needed 
readable region)!
   destination %xmm12 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   __GI___strdup (s=0x0) at strdup.c:41
   plist_new_string () from /usr/lib/x86_64-linux-gnu/libplist.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
   lockdownd_client_new_with_handshake () from 
/usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
  Title: upowerd crashed with SIGSEGV in strlen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1366206] Re: Graphical desktop not starting from livesession

2014-09-06 Thread Elfy 
** Description changed:

  Boot live session - choose Try
  
- Same issue with at least Ubuntu and Xubuntu
+ Same issue with at least Xubuntu,Ubuntu and Lubuntu
  
  No desktop, black screen - change to vt1 - run loginctl show-seat seat0
  gives CanGraphical=no
  
  run startx and desktop boots
  
  this is in a vm on a machine using nvidia card and 331-updates
  
  appears similar to lp:1365336
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.343
  Date: Fri Sep  5 21:40:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Graphical desktop not starting from livesession

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Boot live session - choose Try

  Same issue with at least Xubuntu,Ubuntu and Lubuntu

  No desktop, black screen - change to vt1 - run loginctl show-seat
  seat0 gives CanGraphical=no

  run startx and desktop boots

  this is in a vm on a machine using nvidia card and 331-updates

  appears similar to lp:1365336

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.343
  Date: Fri Sep  5 21:40:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1332444] Re: CH Pedals are not working in 14.04

2014-09-06 Thread michael 
This morning my CH Pedals were dead (like so often) and:
sudo lsusb -v
didn't help but I remembered to use:

echo '3-3' |sudo tee /sys/bus/usb/drivers/usb/unbind

to unbind for Metro Last Light. Need that as MLL keeps spinning
and thinks my joystick to be some sort of controller.
So I did:

echo '3-3' |sudo tee /sys/bus/usb/drivers/usb/unbind
sudo lsusb -v
echo '3-3' |sudo tee /sys/bus/usb/drivers/usb/bind

any voilà my Pedals work. wub.png  Probably the lsusb in between
is not needed and I'll try next time without.

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

Title:
  CH Pedals are not working in 14.04

Status in systemd:
  Fix Released
Status in “linux” package in Ubuntu:
  Confirmed
Status in “systemd” package in Ubuntu:
  Fix Committed

Bug description:
  Summary:
   - The joystick evdev device for the pedals doesn't get proper permissions 
(in udev/systemd)
   - The pedal evdev device sometimes doesn't generate evdev events (linux)

  
  -- 

  I've created a rule in lib/udev/rules.d as 99-xplane.rules:
  # CH PRO PEDALS USB
  KERNEL==event*, ATTRS{idProduct}==00f2, ATTRS{idVendor}==068e, 
MODE=0666

  and even do at every x-plane start:
  cd /dev/input
  sudo setfacl --modify u:michael:rw- --modify g::rw- --modify o::rw- *

  but still my CH Pedals are often not working. (sometimes yes but not
  always)

  --
  michael@michael-ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  michael@michael-ubuntu:~$

  
  michael@michael-ubuntu:~$ apt-cache policy udev
  udev:
    Installed: 204-5ubuntu20.2
    Candidate: 204-5ubuntu20.2
    Version table:
   *** 204-5ubuntu20.2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   204-5ubuntu20 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  michael@michael-ubuntu:~$

  I expect my CH pedals to work out of the box like on Windows.
  But even with the above they only work sometimes.-

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 20 09:46:31 2014
  InstallationDate: Installed on 2014-04-19 (61 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=2c43c000-7e14-4304-9dd6-e10fe2810f92 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  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.:bvr1405:bd08/19/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1586 F pulseaudio
   /dev/snd/controlC0:  michael1586 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=82d28a0c-f533-4a45-80f0-6aab843a37b5
  InstallationDate: Installed on 2014-04-19 (110 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia
  Package: systemd
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=2c43c000-7e14-4304-9dd6-e10fe2810f92 ro
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890

[Touch-packages] [Bug 1360582] Re: Can't manually install clicks Signature verification error since #205

2014-09-06 Thread Colin Watson 
** Also affects: qtcreator-plugin-ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
   Status: New = In Progress

** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
   Importance: Undecided = High

** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
 Assignee: (unassigned) = Michael Vogt (mvo)

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

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

** Changed in: click (Ubuntu)
 Assignee: (unassigned) = Michael Vogt (mvo)

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

Title:
  Can't manually install clicks Signature verification error since
  #205

Status in PackageKit:
  Confirmed
Status in “click” package in Ubuntu:
  In Progress
Status in “phablet-tools” package in Ubuntu:
  Confirmed
Status in “qtcreator-plugin-ubuntu” package in Ubuntu:
  In Progress

Bug description:
  See mailing list thread at https://lists.launchpad.net/ubuntu-
  phone/msg09607.html

  Since image #205 I can't install click packages using click-buddy 
  pkcon install-local. Changed click-buddy to use  adb $ADBOPTS shell
  click install --user=$DEVICE_USER --allow-unauthenticated /tmp/$click
  which worked for me, but dunno if that's the right thing to do.

  alan@deep-thought:~/phablet/code/coreapps⟫ adb push 
com.ubuntu.music_1.3.597_all.click /tmp
  2560 KB/s (401406 bytes in 0.153s)

  alan@deep-thought:~/phablet/code/coreapps⟫ phablet-shell
  start: Job is already running: ssh
  /home/alan/.ssh/known_hosts updated.
  Original contents retained as /home/alan/.ssh/known_hosts.old
  9 KB/s (399 bytes in 0.040s)
  Warning: Permanently added '[localhost]:' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako 
armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Aug 22 23:53:19 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ pkcon install-local 
/tmp/com.ubuntu.music_1.3.597_all.click 
  Installing files  [=] 
  Finished  [=] 
  Installing files  [=] 
  Waiting for authentication[=] 
  Starting  [=] 
  Finished  [=] 
  Fatal error: /tmp/com.ubuntu.music_1.3.597_all.click failed to install.
  Cannot install /tmp/com.ubuntu.music_1.3.597_all.click: Signature 
verification error: debsig: Origin Signature check failed. This deb might not 
be signed.

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

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

[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup

2014-09-06 Thread Bernard Decock 
And log-file when the reader is ok

** Attachment added: LogCardReaderOK.txt
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4196928/+files/LogCardReaderOK.txt

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

Title:
  System crash when Vasco-card-reader is plugged in at powerup

Status in “pcsc-lite” package in Ubuntu:
  New

Bug description:
  I'm using VASCO Data Security International Digipass 905 SmartCard Reader 
which is working fine. However if the device is plugged in at power-up, the 
device isn't handled well. Although the device is in the ilisted usb-devices, 
pcsc-scan doesn't find the device at all (Which is normal as the green-led is 
going out after the kernel starts). If one tries to remove the card-reader,
  a system-crash happens. After that the pcscd-service seems to be halted :
  pcsc_scan
  PC/SC device scanner
  V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
  Compiled with PC/SC lite version: 1.8.10
  SCardEstablishContext: Service not available.

  One can recover from this problem by
  1. Unplugging the reader
  2. Manually starting the service again by sudo service pcscd start 
  3. Plugging back the reader in (green led stays on, red led goes on when a 
card is put in)

  The bug is not related to a 64-bit architecture as it happens also
  with 32-bit machines.

  Info about the device
  Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 
905 SmartCard Reader
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x1a44 VASCO Data Security International
idProduct  0x0001 Digipass 905 SmartCard Reader
bcdDevice1.02
iManufacturer   1 
iProduct2 
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   93
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass11 Chip/SmartCard
bInterfaceSubClass  0 
bInterfaceProtocol  0 
iInterface  0 
ChipCard Interface Descriptor:
  bLength54
  bDescriptorType33
  bcdCCID  1.00
  nMaxSlotIndex   0
  bVoltageSupport 3  5.0V 3.0V 
  dwProtocols 3  T=0 T=1
  dwDefaultClock   3700
  dwMaxiumumClock  3700
  bNumClockSupported  1
  dwDataRate   9946 bps
  dwMaxDataRate  318280 bps
  bNumDataRatesSupp. 53
  dwMaxIFSD 254
  dwSyncProtocols  0007  2-wire 3-wire I2C
  dwMechanical  
  dwFeatures   000404BE
Auto configuration based on ATR
Auto activation on insert
Auto voltage selection
Auto clock change
Auto baud rate change
Auto PPS made by CCID
Auto IFSD exchange
Short and extended APDU level exchange
  dwMaxCCIDMsgLen   272
  bClassGetResponseecho
  bClassEnvelope   echo
  wlcdLayout   none
  bPINSupport 0 
  bMaxCCIDBusySlots   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0004  1x 4 bytes
  bInterval  32
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0010  1x 16 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN

[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup

2014-09-06 Thread Bernard Decock 
Thank you Ludovic for your quick response.

I generated to log-files,
logcardrea...@powerup.txt in case it goes wrong (only when the card-reader is 
plugged in while the computer is starting-up or rebooting

LogCardReaderOK.txt after the crash - removed the reader and sudo
service pcscd start

/usr/sbin/pcscd --version
pcsc-lite version 1.8.10.
Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com.
Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr.
Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr.
Report bugs to mus...@lists.musclecard.com.
Enabled features: Linux x86_64-pc-linux-gnu serial usb libudev 
usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd 
configdir=/etc/reader.conf.d

pcsc_scan (when the reader is ok)
PC/SC device scanner
V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
Compiled with PC/SC lite version: 1.8.10
Using reader plug'n play mechanism
Scanning present readers...
0: VASCO DP905v1.1 00 00

Sat Sep  6 10:18:48 2014
Reader 0: VASCO DP905v1.1 00 00
  Card state: Card removed, 

apt-cache policy pcscd
pcscd:
  Geïnstalleerd: 1.8.10-1ubuntu1
  Kandidaat: 1.8.10-1ubuntu1
  Versietabel:
 *** 1.8.10-1ubuntu1 0
500 http://be.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
100 /var/lib/dpkg/status

Middleware = eid-mw
low-level support for Belgian Electronic Identity Card
apt-cache policy eid-mw
eid-mw:
  Geïnstalleerd: 4.0.6r1620-0trusty1
  Kandidaat: 4.0.6r1620-0trusty1
  Versietabel:
 *** 4.0.6r1620-0trusty1 0
500 http://files.eid.belgium.be/debian/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
 


** Attachment added: logcardrea...@powerup.txt
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4196927/+files/LogCardReader%40Powerup.txt

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

Title:
  System crash when Vasco-card-reader is plugged in at powerup

Status in “pcsc-lite” package in Ubuntu:
  New

Bug description:
  I'm using VASCO Data Security International Digipass 905 SmartCard Reader 
which is working fine. However if the device is plugged in at power-up, the 
device isn't handled well. Although the device is in the ilisted usb-devices, 
pcsc-scan doesn't find the device at all (Which is normal as the green-led is 
going out after the kernel starts). If one tries to remove the card-reader,
  a system-crash happens. After that the pcscd-service seems to be halted :
  pcsc_scan
  PC/SC device scanner
  V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
  Compiled with PC/SC lite version: 1.8.10
  SCardEstablishContext: Service not available.

  One can recover from this problem by
  1. Unplugging the reader
  2. Manually starting the service again by sudo service pcscd start 
  3. Plugging back the reader in (green led stays on, red led goes on when a 
card is put in)

  The bug is not related to a 64-bit architecture as it happens also
  with 32-bit machines.

  Info about the device
  Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 
905 SmartCard Reader
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x1a44 VASCO Data Security International
idProduct  0x0001 Digipass 905 SmartCard Reader
bcdDevice1.02
iManufacturer   1 
iProduct2 
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   93
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass11 Chip/SmartCard
bInterfaceSubClass  0 
bInterfaceProtocol  0 
iInterface  0 
ChipCard Interface Descriptor:
  bLength54
  bDescriptorType33
  bcdCCID  1.00
  nMaxSlotIndex   0
  bVoltageSupport 3  5.0V 3.0V 
  dwProtocols 3  T=0 T=1
  dwDefaultClock   3700
  dwMaxiumumClock  3700
  bNumClockSupported  1
  dwDataRate   9946 bps
  dwMaxDataRate  318280 bps

[Touch-packages] [Bug 589394] Re: replace w3m with lynx

2014-09-06 Thread Mathew Hodson 
The mentioned bug was fixed and ubuntu-standard doesn't depend or
recommend w3m, so I don't think this bug is relevant anymore.

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

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

Title:
  replace w3m with lynx

Status in “ubuntu-meta” package in Ubuntu:
  Opinion

Bug description:
  Binary package hint: ubuntu-standard

  Considering bug 589203 and bug 523229 - would it be worth to switch to
  lynx (or another browser that doesn't have that issue for that matter)
  ?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: w3m 0.5.2-4
  ProcVersionSignature: Ubuntu 2.6.34-5.13-generic 2.6.34
  Uname: Linux 2.6.34-5-generic x86_64
  Architecture: amd64
  Date: Thu Jun  3 22:52:33 2010
  InstallationMedia: Kubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US.UTF-8
  SourcePackage: w3m

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

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

[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop

2014-09-06 Thread dino99 
utopic + lightdm 1.11.8 + nvidia-331 (newest): black screen (nvidia-331
has a nvidia-prime error, so the 'nouveau' fallback is used)

utopic + gdm boots well with 'nouveau' only

nvidia-331 report lp:1366284

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

Title:
  Lightdm update=No desktop

Status in “fglrx-installer” package in Ubuntu:
  In Progress
Status in “fglrx-installer-updates” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released

Bug description:
  Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me
  with no desktop on normal boot.

  Machine boots directly to tty1.

  Logged in at tty1 and then startx leads to a desktop that requires
  password to start properly and with themes unapplied.

  Password required to reboot machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  4 08:20:14 2014
  InstallationDate: Installed on 2014-07-17 (48 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1365875] Re: mail notification displayed even when phone locked

2014-09-06 Thread Sebastien Bacher 
** Also affects: unity8
   Importance: Undecided
   Status: New

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

Title:
  mail notification displayed even when phone locked

Status in The Unity 8 shell:
  New
Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  I had just woken up the phone (screen was displaying the welcome
  greeter) but had not yet unlocked the device (I have set a pin code)
  when a mail notification appeared on screen that divulged the sender.

  This is a privacy issue.

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

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

[Touch-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful

2014-09-06 Thread Sebastien Bacher 
** Also affects: indicator-transfer
   Importance: Undecided
   Status: New

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

Title:
  [Indicators] replace the text Empty! with something more useful

Status in Transfer Indicator:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Triaged
Status in “indicator-messages” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  when clearing the menu on this indicator (and others), the text
  Empty! is displayed. Can we please remove that and put something
  more useful there. It looks bad. Need advise from design..

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

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

[Touch-packages] [Bug 1366288] [NEW] Clicking on system image update notification doesn't open settings

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using the rtm-17 image on krillin, when system updates are available the
indicator-messages includes an entry stating that you can click to open
the ui, but clicking doesn't to anything

** Affects: unity8
 Importance: Undecided
 Status: New

** Package changed: unity8 (Ubuntu) = unity8

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

Title:
  Clicking on system image update notification doesn't open settings

Status in The Unity 8 shell:
  New

Bug description:
  Using the rtm-17 image on krillin, when system updates are available
  the indicator-messages includes an entry stating that you can click to
  open the ui, but clicking doesn't to anything

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

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

[Touch-packages] [Bug 1364199] Re: Unable to change the refresh rate of the monitor

2014-09-06 Thread Renan Araujo Rischiotto 
** Description changed:

  The xrandr does not work with the proprietary NVIDIA drivers, and in
  Unity and NVIDIA X Server Settings there is no option to change the
  refresh rate of the monitor.
  
  Ubuntu 14.04.1
  Xorg 1.15.1
  Driver 331.38
  
  sudo lspci -c display output:
  
  renan@ubuntu:~$ sudo lshw -C display
  [sudo] password for renan:
    *-display
     description: VGA compatible controller
     product: GT218 [GeForce 8400 GS Rev. 3]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:04:00.0
     version: a2
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
     configuration: driver=nvidia latency=0
     resources: irq:45 memory:fd00-fdff memory:e000-efff 
memory:de00-dfff ioport:ec00(size=128) memory:fe00-fe07
  renan@ubuntu:~$
  
  Question:
  
  https://answers.launchpad.net/ubuntu/+source/xorg/+question/254081
  
- Theads on Ubuntu forums (without solution):
+ Theads on Ubuntu forums:
  
  http://ubuntuforums.org/showthread.php?t=2241692
  http://ubuntuforums.org/showthread.php?t=2242124

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

Title:
  Unable to change the refresh rate of the monitor

Status in “xorg” package in Ubuntu:
  New

Bug description:
  The xrandr does not work with the proprietary NVIDIA drivers, and in
  Unity and NVIDIA X Server Settings there is no option to change the
  refresh rate of the monitor.

  Ubuntu 14.04.1
  Xorg 1.15.1
  Driver 331.38

  sudo lspci -c display output:

  renan@ubuntu:~$ sudo lshw -C display
  [sudo] password for renan:
    *-display
     description: VGA compatible controller
     product: GT218 [GeForce 8400 GS Rev. 3]
     vendor: NVIDIA Corporation
     physical id: 0
     bus info: pci@:04:00.0
     version: a2
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
     configuration: driver=nvidia latency=0
     resources: irq:45 memory:fd00-fdff memory:e000-efff 
memory:de00-dfff ioport:ec00(size=128) memory:fe00-fe07
  renan@ubuntu:~$

  Question:

  https://answers.launchpad.net/ubuntu/+source/xorg/+question/254081

  Theads on Ubuntu forums:

  http://ubuntuforums.org/showthread.php?t=2241692
  http://ubuntuforums.org/showthread.php?t=2242124

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

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

[Touch-packages] [Bug 1359486] Re: [PPA] Use LibreOffice Dialogs setting is ignored in KDE

2014-09-06 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: qt4-x11 (Ubuntu)
   Status: New = Confirmed

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

Title:
  [PPA] Use LibreOffice Dialogs setting is ignored in KDE

Status in LibreOffice Productivity Suite:
  Won't Fix
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “qt4-x11” package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 14.04 (KDE Desktop Environment)

  Packages from this ppa:
  https://launchpad.net/~libreoffice

  Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages 
as of about 1 hour ago)
  or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog.

  LibreOffice uses it's native filepicker/save dialogs, regardless of
  whether the config option Use LibreOffice Dialogs is ticked or not.

  This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu
  security repository.

  Related Bugs:
  https://bugreports.qt-project.org/browse/QTBUG-38585
  https://bugreports.qt-project.org/browse/QTBUG-34614

  According to the LO team, both these bugs have patches that address
  the automatic disabling of Qt dialogs at runtime (if buggy Qt is
  detected.)

  
  Initial report/discussion on LO bugtracker (now closed) here: 
https://bugs.freedesktop.org/show_bug.cgi?id=82598

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+subscriptions

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

[Touch-packages] [Bug 909523] Re: Bluetooth on MacBook Pro 8, 3 Doesn't Work without OSX

2014-09-06 Thread madbiologist 
** Description changed:

  This bug is kind of hard to describe, but can basically be summed up
  like this:
  
-  * Bluetooth support on a 2011 8,3 MacBook Pro running Ubuntu 8,3 is
+  * Bluetooth support on a 2011 8.3 MacBook Pro running Ubuntu 11.10 is
  flaky at best and unusuable at worst.
  
  When I booted up into Ubuntu for the first time, I was pleasantly
  surprised to see that it found my Bluetooth chip and even seemed to be
  working with it.
  
  Then I actually tried connecting devices.
  
  Essentially, `hcitool scan` and `hidd --search` both cannot find ANY
  devices. I've yet to actually see it report a detected device
  consistently. ONCE, I saw it report my Nexus One, but then another scan
  and it was gone.
  
  Devices can only be connected if one boots into OSX first, pairs the
  device, then boots into Ubuntu and attempts to pair the device. Even
  after doing so, commandline tools won't show the device in scanmode,
  only the `bluetooth-applet` and `blueman-manager` show them. After
  connection, I've noticed that I've had inconsistent success with my S305
  bluetooth headphones, where on another computer with a USB dongle, it
  just works. Sometimes, they won't establish the connection right away
  and go into pairing mode. Sometimes they'll connect fairly immediately,
  but not be able to be set to A2DP rather than HLS mode. Sometimes
  they'll work but have choppy audio, sometimes not.
  
  There are a lot of other weird things like this such as touchpad
  sensitivity, screen brightness, and more which all require to be managed
  from OSX. This leads me to believe that Apple is doing some weird
  firmware-level or maybe EFI-level system management. This is super
  weird; configuration should be per OS, not per machine.  Has anyone
  heard of their doing these strange things?
  
  I'm willing to do anything, even including remote SSH access to my
  computer, to help the Ubuntu team resolve this bug. I bought my MacBook
  to run Ubuntu and can't wait to see this stuff work :)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: bluetooth 4.96-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed Dec 28 15:06:07 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Apple Inc. MacBookPro8,3
  PackageArchitecture: all
  ProcEnviron:
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic 
root=UUID=a25736d1-ccdd-401e-ba56-4cf4f01b1053 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to oneiric on 2011-12-28 (0 days ago)
  dmi.bios.date: 09/28/11
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B22.1109281426
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-942459F5819B171B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942459F5819B171B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B22.1109281426:bd09/28/11:svnAppleInc.:pnMacBookPro8,3:pvr1.0:rvnAppleInc.:rnMac-942459F5819B171B:rvrMacBookPro8,3:cvnAppleInc.:ct10:cvrMac-942459F5819B171B:
  dmi.product.name: MacBookPro8,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
-  hci0:Type: BR/EDR  Bus: USB
-   BD Address: 60:C5:47:9B:34:09  ACL MTU: 1021:8  SCO MTU: 64:1
-   UP RUNNING PSCAN ISCAN 
-   RX bytes:353334 acl:2127 sco:5322 events:5470 errors:0
-   TX bytes:3037466 acl:4780 sco:5285 commands:558 errors:0
+  hci0:Type: BR/EDR  Bus: USB
+   BD Address: 60:C5:47:9B:34:09  ACL MTU: 1021:8  SCO MTU: 64:1
+   UP RUNNING PSCAN ISCAN
+   RX bytes:353334 acl:2127 sco:5322 events:5470 errors:0
+   TX bytes:3037466 acl:4780 sco:5285 commands:558 errors:0

** Summary changed:

- Bluetooth on MacBook Pro 8,3 Doesn't Work without OSX
+ Bluetooth on MacBook Pro 8.3 Doesn't Work without OSX

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

Title:
  Bluetooth on MacBook Pro 8.3 Doesn't Work without OSX

Status in “bluez” package in Ubuntu:
  New

Bug description:
  This bug is kind of hard to describe, but can basically be summed up
  like this:

   * Bluetooth support on a 2011 8.3 MacBook Pro running Ubuntu 11.10 is
  flaky at best and unusuable at worst.

  When I booted up into Ubuntu for the first time, I was pleasantly
  surprised to see that it found my Bluetooth chip and even seemed to be
  working with it.

  Then I actually tried connecting devices.

  Essentially, `hcitool scan` and `hidd --search` both cannot find

[Touch-packages] [Bug 531208]

2014-09-06 Thread Ruslan 
There's a project (created by me) which tries to work around this
limitation of X by providing a daemon-like app intercepting Ctrl+Shift+U
and allowing to enter UTF-32 character codes:

https://gitorious.org/ucode/ucode/

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

Title:
  Need way to insert arbitrary unicode characters in Kubuntu

Status in X.Org X server:
  Confirmed
Status in “xorg” package in Ubuntu:
  Won't Fix

Bug description:
  KDE, Qt, and Xorg are in disagreement about who should implement ISO 14755, 
which would facilitate the input of arbitrary unicode characters. This is the 
original KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=103788

  It was pushed upstream to Qt:
  http://bugreports.qt.nokia.com/browse/QTBUG-8

  From there it was pushed further upstream to Xorg:
  https://bugs.freedesktop.org/show_bug.cgi?id=26747

  Xorg pushes the bug downstream, back to either Qt or KDE to implement,
  just as Gnome implemented the fix themselves. An Xorg developer who
  does not want to be named says that if KDE won't implement it then my
  distro should. So here I file that request.

  Note that in KDE 3 one could use the Kcharselect applet to enter arbitrary 
unicode characters, however that has been disabled in KDE 4:
  https://bugs.kde.org/show_bug.cgi?id=190776

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

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

[Touch-packages] [Bug 1363910] [NEW] GTK2 theme not loaded from ~/.local/share/themes

2014-09-06 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

In Xubuntu 13.10 I was able to load themes from ~/.local/share/themes.

In Xubuntu 14.04 I can still load the GTK3 theme, but not the GTK2
theme.

Workaround:
Load the themes from ~/.themes.

Downside:
Cluttered home directory.

How to reproduce:
1. Download a theme and put in in ~/.themes.
2. Open settings manager and a GTK3 app. (I used gedit.)
3. Apply the downloaded theme.
So far everything should work.

4.  Move the downloaded theme to ~/.local/share/themes.
5. Apply another theme and reapply the downloaded one.
At this point only the GTK2 theme is loaded.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xfce4 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Sep  1 11:12:59 2014
SourcePackage: xfce4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty xubuntu
-- 
GTK2 theme not loaded from ~/.local/share/themes
https://bugs.launchpad.net/bugs/1363910
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+2.0 in Ubuntu.

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

[Touch-packages] [Bug 1363910] Re: GTK2 theme not loaded from ~/.local/share/themes

2014-09-06 Thread Thaddäus Tintenfisch 
That’s happening because GTK2 cannot read the Theme RC file from
“~/.local/share/themes/” location.

http://worldofgnome.org/gtk-theme-ing-issue-in-gnome-3-10/

** Package changed: xfce4 (Ubuntu) = gtk+2.0 (Ubuntu)

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

Title:
  GTK2 theme not loaded from ~/.local/share/themes

Status in “gtk+2.0” package in Ubuntu:
  New

Bug description:
  In Xubuntu 13.10 I was able to load themes from ~/.local/share/themes.

  In Xubuntu 14.04 I can still load the GTK3 theme, but not the GTK2
  theme.

  Workaround:
  Load the themes from ~/.themes.

  Downside:
  Cluttered home directory.

  How to reproduce:
  1. Download a theme and put in in ~/.themes.
  2. Open settings manager and a GTK3 app. (I used gedit.)
  3. Apply the downloaded theme.
  So far everything should work.

  4.  Move the downloaded theme to ~/.local/share/themes.
  5. Apply another theme and reapply the downloaded one.
  At this point only the GTK2 theme is loaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xfce4 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Sep  1 11:12:59 2014
  SourcePackage: xfce4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1251735] Re: avahi-cups-reload triggered twice

2014-09-06 Thread Martin Polden 
Happens in 14.04.1 LTS for me:

$ grep avahi /var/log/boot.log
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues 
are populated[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues 
are populated[fail]

Package avahi-daemon is installed, but cups is not.

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

Title:
  avahi-cups-reload triggered twice

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  $ grep avahi /var/log/boot.log 
   * Starting Reload cups, upon starting avahi-daemon to make sure remote 
queues are populated
   [ OK ]
   * Starting Reload cups, upon starting avahi-daemon to make sure remote 
queues are populated
   [fail]

  The /etc/init/avahi-cups-reload.conf script seems to be triggered
  twice in the boot process.

  Apparently I'm not the only one having this.

  See bug #1158686. I'm not the only one having this. I did not see any 
printing problem, but it's ugly in the boot process.
  According to bug  #1158686  comment 21, an upstart expert should look at 
that, so I'm asking you guys.

  I upgraded from 13.04, but it may affect every new install.

  Thanks in advance,
  Marc

  Ubuntu 13.10
  upstart version 1.10-0ubuntu7

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

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

[Touch-packages] [Bug 1366288] Re: Clicking on system image update notification doesn't open settings

2014-09-06 Thread Michał Sawicz 
Indeed, it does when you tap on the cog in top right corner...

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

** No longer affects: unity8

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Also affects: ubuntu-settings-components (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/1366288

Title:
  Clicking on system image update notification doesn't open settings

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using the rtm-17 image on krillin, when system updates are available
  the indicator-messages includes an entry stating that you can click to
  open the ui, but clicking doesn't to anything

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

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

[Touch-packages] [Bug 1366288] Re: Clicking on system image update notification doesn't open settings

2014-09-06 Thread Michał Sawicz 
Not sure what the desired solution is, adding ubuntu-ux for feedback.

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

Title:
  Clicking on system image update notification doesn't open settings

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using the rtm-17 image on krillin, when system updates are available
  the indicator-messages includes an entry stating that you can click to
  open the ui, but clicking doesn't to anything

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

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

[Touch-packages] [Bug 1366288] Re: Clicking on system image update notification doesn't open settings

2014-09-06 Thread Sebastien Bacher 
I don't have a notification at the moment, but I think the system update
ones don't have the top right cog icon (I couldn't find any corner/icon
reacting to taps). That works for e.g sms though

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

Title:
  Clicking on system image update notification doesn't open settings

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using the rtm-17 image on krillin, when system updates are available
  the indicator-messages includes an entry stating that you can click to
  open the ui, but clicking doesn't to anything

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

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

[Touch-packages] [Bug 1366314] [NEW] security issue? auto suggest seems to copy credentials into clipboard

2014-09-06 Thread Alexander Sack 
Public bug reported:

on todays image (krillin rtm-proposed r21) with ONLY auto suggest
language option on I get:

13:57  asac 1. kill terminal
13:57  asac 2. open terminal and enter pin
13:57  asac 3. click in terminal pastes my pin :)

obviously not good for security. Think might be bad.

Seems its not getting to dictionary at least:

13:58  asac 4. /me uses backspace to delete
13:58  asac 5. type ls
13:58  asac 6. type first digit of pin - does not suggest my pin

This doesn't happen if I turn auto suggestion off. Not sure if the paste
is what doesn't happen or the clipboarding doesn't happen. Surely
important to check out and know for sure.

We should check other credential prompts too: pin lock screen, sim pin
etc.

Haven't tried, but I assume UITK password fields and browser dont have
that, but might be worth checking.

Thanks!

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Critical
 Status: New


** Tags: rtm14

** Description changed:

- on todays image (krillin rtm-proposed r21)
+ on todays image (krillin rtm-proposed r21) with ONLY auto suggest
+ language option on I get:
  
- 13:57  asac 1. kill terminal 
+ 13:57  asac 1. kill terminal
  13:57  asac 2. open terminal and enter pin
  13:57  asac 3. click in terminal pastes my pin :)
  
  obviously not good for security. Think might be bad.
  
  Seems its not getting to dictionary at least:
  
  13:58  asac 4. /me uses backspace to delete
  13:58  asac 5. type ls
  13:58  asac 6. type first digit of pin - does not suggest my pin
  
- we should check other credential prompts too: pin lock screen, sim pin
+ This doesn't happen if I turn auto suggestion off. Not sure if the paste
+ is what doesn't happen or the clipboarding doesn't happen. Surely
+ important to check out and know for sure.
+ 
+ We should check other credential prompts too: pin lock screen, sim pin
  etc.
  
  Haven't tried, but I assume UITK password fields and browser dont have
  that, but might be worth checking.
  
  Thanks!

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided = Critical

** Tags added: rtm14

** Summary changed:

- auto suggest seems to copy credentials into clipboard
+ security issue? auto suggest seems to copy credentials into clipboard

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

Title:
  security issue? auto suggest seems to copy credentials into clipboard

Status in “ubuntu-keyboard” package in Ubuntu:
  New

Bug description:
  on todays image (krillin rtm-proposed r21) with ONLY auto suggest
  language option on I get:

  13:57  asac 1. kill terminal
  13:57  asac 2. open terminal and enter pin
  13:57  asac 3. click in terminal pastes my pin :)

  obviously not good for security. Think might be bad.

  Seems its not getting to dictionary at least:

  13:58  asac 4. /me uses backspace to delete
  13:58  asac 5. type ls
  13:58  asac 6. type first digit of pin - does not suggest my pin

  This doesn't happen if I turn auto suggestion off. Not sure if the
  paste is what doesn't happen or the clipboarding doesn't happen.
  Surely important to check out and know for sure.

  We should check other credential prompts too: pin lock screen, sim pin
  etc.

  Haven't tried, but I assume UITK password fields and browser dont have
  that, but might be worth checking.

  Thanks!

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

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

Re: [Touch-packages] [Bug 1366288] Re: Clicking on system image update notification doesn't open settings

2014-09-06 Thread Michał Sawicz 
 I don't have a notification at the moment, but I think the system update
 ones don't have the top right cog icon (I couldn't find any corner/icon
 reacting to taps). That works for e.g sms though

I had one (actually... more than one) before replying and checked that 
it's there and works.

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

Title:
  Clicking on system image update notification doesn't open settings

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using the rtm-17 image on krillin, when system updates are available
  the indicator-messages includes an entry stating that you can click to
  open the ui, but clicking doesn't to anything

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

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

[Touch-packages] [Bug 1366288] Re: Clicking on system image update notification doesn't open settings

2014-09-06 Thread Sebastien Bacher 
ok, I guess I just overlooked it then ... (the icons on the left are
bigger and I probably tried to tap on those), in any case not
obvious/matching the description

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

Title:
  Clicking on system image update notification doesn't open settings

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using the rtm-17 image on krillin, when system updates are available
  the indicator-messages includes an entry stating that you can click to
  open the ui, but clicking doesn't to anything

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

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

[Touch-packages] [Bug 1352784] Re: GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled.

2014-09-06 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New = Confirmed

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

Title:
  GPS indicator does not disappear when location services disabled, but
  bluetooth indicator does disappear when disabled.

Status in “indicator-location” package in Ubuntu:
  Confirmed

Bug description:
  There is inconsistency between the bluetooth indicator and the
  location indication. Currently (image #171):

  - if location+GPS are disabled, the indicator persists.
  - if bluetooth is disabled, it disappaears.

  Which behaviour is correct?

  Further, even if the location indicator behaviour is correct, surely
  we should consider greying out the indicator so that the user can
  see at a glance that that indicator is disabled?

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

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

[Touch-packages] [Bug 1336715] Re: switch-items in indicators sometimes get out of sync

2014-09-06 Thread Sebastien Bacher 
** Changed in: unity8 (Ubuntu)
   Status: Incomplete = 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/1336715

Title:
  switch-items in indicators sometimes get out of sync

Status in Indicator Location:
  New
Status in Network Menu:
  Confirmed
Status in The Unity 8 shell:
  Incomplete
Status in “unity8” package in Ubuntu:
  New

Bug description:
  I noticed when testing flightmode with indicator-network that the
  switch items sometimes get out of sync from what GActions states on
  dbus are and stop updating their states when action states on dbus
  change.

  This seems to happen randomly and I have no procedure to reproduce
  reliably.

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

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

[Touch-packages] [Bug 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware

2014-09-06 Thread Doug McMahon 
** Also affects: nouveau
   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/1357746

Title:
  Compiz  fails to load with xserver-xorg-video-intel
  2:2.99.914-1~exp1ubuntu1 on some Intel hardware

Status in Compiz:
  Invalid
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Seen here with Haswell (Mobile)
  Logs into a session with
  black desktop
  no unity panel
  a non functional launcher

  Nothing can be done in the session except go to a tty

  If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then
  all is well  compiz loads as expected

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0
  Uname: Linux 3.16.0-8-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Aug 16 12:29:42 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140813)
  MachineType: LENOVO 20217
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-8-generic.efi.signed 
root=UUID=1696b1d2-76dc-4df4-bafc-65f8cd743e53 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Aug 16 12:28:54 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 729
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu9

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

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

[Touch-packages] [Bug 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware

2014-09-06 Thread Doug McMahon 
If I either blacklist nouveau or remove the xserver-xorg-video-nouveau package 
then everything works as expected with the current xserver-xorg-video-intel 
package.
This also *seems* to make restarts  shutdowns more reliable  makes going to a 
tty not be liable to cause some sort of looping kernel panic (happens about 40% 
of the time with nouveau package installed  not blacklisted

So choices here on Haswell Mobile - 
Downgrade xserver-xorg-video-intel
Blacklist nouveau
Remove xserver-xorg-video-nouveau

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

Title:
  Compiz  fails to load with xserver-xorg-video-intel
  2:2.99.914-1~exp1ubuntu1 on some Intel hardware

Status in Compiz:
  Invalid
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  Seen here with Haswell (Mobile)
  Logs into a session with
  black desktop
  no unity panel
  a non functional launcher

  Nothing can be done in the session except go to a tty

  If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then
  all is well  compiz loads as expected

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0
  Uname: Linux 3.16.0-8-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Aug 16 12:29:42 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2014-08-16 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140813)
  MachineType: LENOVO 20217
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-8-generic.efi.signed 
root=UUID=1696b1d2-76dc-4df4-bafc-65f8cd743e53 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Aug 16 12:28:54 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 729
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu9

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

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

[Touch-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful

2014-09-06 Thread Jim Hodapp 
Indicator messages should use something contextual such as No current
messages. Providing the more specific context will make this much more
obvious what this indicator is used for, especially to the first time
user.

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

Title:
  [Indicators] replace the text Empty! with something more useful

Status in Transfer Indicator:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Triaged
Status in “indicator-messages” package in Ubuntu:
  Confirmed
Status in “indicator-transfer” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  when clearing the menu on this indicator (and others), the text
  Empty! is displayed. Can we please remove that and put something
  more useful there. It looks bad. Need advise from design..

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

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

[Touch-packages] [Bug 1366332] [NEW] Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg

2014-09-06 Thread Patryk 
Public bug reported:

Ubuntu 14.04
apt 1.0.1ubuntu2.1

'apt-get update' has started showing several warnings like the
following, even though the keys are present:

W: GPG error: http://extras.ubuntu.com trusty Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
16126D3A3E5C1192
W: GPG error: http://archive.canonical.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://qgis.org trusty InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
030561BEDD45F6C3
W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
W: GPG error: http://archive.ubuntu.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com trusty-updates Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com trusty-security Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

sudo apt-key clean didn't help

The only ultimate solution was to remove all the keys from
/etc/apt/trusted.gpg.d and run

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys KEY

for each key that was missing.


Here is a reference bug for 13.10 
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1263540

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


** Tags: apt gpg

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg

Status in “apt” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04
  apt 1.0.1ubuntu2.1

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://extras.ubuntu.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 16126D3A3E5C1192
  W: GPG error: http://archive.canonical.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://qgis.org trusty InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
030561BEDD45F6C3
  W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
  W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
  W: GPG error: http://archive.ubuntu.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://archive.ubuntu.com trusty-updates Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://archive.ubuntu.com trusty-security Release: The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  sudo apt-key clean didn't help

  The only ultimate solution was to remove all the keys from
  /etc/apt/trusted.gpg.d and run

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys KEY

  for each key that was missing.


  Here is a reference bug for 13.10 
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1263540

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

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

[Touch-packages] [Bug 1259444] Re: package libhardware-dev - one word missing in description

2014-09-06 Thread Pascal De Vuyst 
https://translations.launchpad.net/ddtp-ubuntu/utopic/+pots/ddtp-ubuntu-
main/fr/7072/+translate

** Changed in: ddtp-ubuntu
   Status: Triaged = Fix Released

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

Title:
  package libhardware-dev - one word missing in description

Status in Package Descriptions for Ubuntu (to make translation easy):
  Fix Released
Status in “libhybris” package in Ubuntu:
  Fix Released

Bug description:
  Package: libhardware-dev
  Version: 0.1.0+git20131207+e452e83-0ubuntu12

  Hi,

  One word is missing in the package description:
  Contains the development files the Android libhardware HAL...

  == Contains the development files for the Android libhardware HAL

  Gisèle

  https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-
  ubuntu-main/fr/+translate?start=7607

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

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

[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup

2014-09-06 Thread Ludovic Rousseau 
LogCardReader%40Powerup.txt indicates that the device is not responding 
correctly:
0024 - 00 65 00 00 00 00 00 00 00 00 00 
05000412 ccid_usb.c:751:WriteUSB() write failed (1/4): -7 Resource temporarily 
unavailable

-7 is LIBUSB_ERROR_TIMEOUT
So the device is not visible at the PC/SC level. I have no idea what is 
happening. I suspect a reader firmware bug.

I do not see the pcscd crash in this log. Can you run pcscd inside gdb?
$ gdb /usr/sbin/pcscd
(gdb) set args -dfa
(gdb) run
remove the reader do make pcscd crash
(gdb) backtrace

Then send me the complete gdb trace.
Thanks

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

Title:
  System crash when Vasco-card-reader is plugged in at powerup

Status in “pcsc-lite” package in Ubuntu:
  New

Bug description:
  I'm using VASCO Data Security International Digipass 905 SmartCard Reader 
which is working fine. However if the device is plugged in at power-up, the 
device isn't handled well. Although the device is in the ilisted usb-devices, 
pcsc-scan doesn't find the device at all (Which is normal as the green-led is 
going out after the kernel starts). If one tries to remove the card-reader,
  a system-crash happens. After that the pcscd-service seems to be halted :
  pcsc_scan
  PC/SC device scanner
  V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
  Compiled with PC/SC lite version: 1.8.10
  SCardEstablishContext: Service not available.

  One can recover from this problem by
  1. Unplugging the reader
  2. Manually starting the service again by sudo service pcscd start 
  3. Plugging back the reader in (green led stays on, red led goes on when a 
card is put in)

  The bug is not related to a 64-bit architecture as it happens also
  with 32-bit machines.

  Info about the device
  Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 
905 SmartCard Reader
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x1a44 VASCO Data Security International
idProduct  0x0001 Digipass 905 SmartCard Reader
bcdDevice1.02
iManufacturer   1 
iProduct2 
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   93
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass11 Chip/SmartCard
bInterfaceSubClass  0 
bInterfaceProtocol  0 
iInterface  0 
ChipCard Interface Descriptor:
  bLength54
  bDescriptorType33
  bcdCCID  1.00
  nMaxSlotIndex   0
  bVoltageSupport 3  5.0V 3.0V 
  dwProtocols 3  T=0 T=1
  dwDefaultClock   3700
  dwMaxiumumClock  3700
  bNumClockSupported  1
  dwDataRate   9946 bps
  dwMaxDataRate  318280 bps
  bNumDataRatesSupp. 53
  dwMaxIFSD 254
  dwSyncProtocols  0007  2-wire 3-wire I2C
  dwMechanical  
  dwFeatures   000404BE
Auto configuration based on ATR
Auto activation on insert
Auto voltage selection
Auto clock change
Auto baud rate change
Auto PPS made by CCID
Auto IFSD exchange
Short and extended APDU level exchange
  dwMaxCCIDMsgLen   272
  bClassGetResponseecho
  bClassEnvelope   echo
  wlcdLayout   none
  bPINSupport 0 
  bMaxCCIDBusySlots   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0004  1x 4 bytes
  bInterval  32
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2

[Touch-packages] [Bug 1269017] Re: Emojis not fully supported which results in blank received SMS messages

2014-09-06 Thread Sebastien Bacher 
is bug #1137630 a duplicate?

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

Title:
  Emojis not fully supported which results in blank received SMS
  messages

Status in Messaging App:
  Confirmed
Status in “messaging-app” package in Ubuntu:
  Triaged
Status in “ofono” package in Ubuntu:
  Fix Released

Bug description:
  Android allows for adding emojis[1] to SMS messages. I'm told that iOS
  users are able to see these emojis. Our messaging app should also
  support displaying emojis.

  emojis appear to not requires MMS since when using Google Hangouts in
  the new android, when you add an emoji the hangouts app says 'Sent now
  via SMS'. Two things need to happen:

  1. need to be able to correctly receive SMS messages with arbitrary
  emojis. Currently, on image 120, an SMS with a known emoji, eg, a
  smiley face, will display correctly when it is and is not accompanied
  with text. However, an SMS with an unknown emoji (eg, with a pinata)
  will show up as a blank SMS, even when the SMS has text. At a minimum,
  the text of the message should always be shown, perhaps with an
  'unknown emoji' placeholder

  2. need to be able to send SMS messages with emojis

  [1]http://en.wikipedia.org/wiki/Emoji

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

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

[Touch-packages] [Bug 1366314] Re: security issue? auto suggest seems to copy credentials into clipboard

2014-09-06 Thread Marc Deslauriers 
** Information type changed from Public to Public Security

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

Title:
  security issue? auto suggest seems to copy credentials into clipboard

Status in “ubuntu-keyboard” package in Ubuntu:
  New

Bug description:
  on todays image (krillin rtm-proposed r21) with ONLY auto suggest
  language option on I get:

  13:57  asac 1. kill terminal
  13:57  asac 2. open terminal and enter pin
  13:57  asac 3. click in terminal pastes my pin :)

  obviously not good for security. Think might be bad.

  Seems its not getting to dictionary at least:

  13:58  asac 4. /me uses backspace to delete
  13:58  asac 5. type ls
  13:58  asac 6. type first digit of pin - does not suggest my pin

  This doesn't happen if I turn auto suggestion off. Not sure if the
  paste is what doesn't happen or the clipboarding doesn't happen.
  Surely important to check out and know for sure.

  We should check other credential prompts too: pin lock screen, sim pin
  etc.

  Haven't tried, but I assume UITK password fields and browser dont have
  that, but might be worth checking.

  Thanks!

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

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

[Touch-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality

2014-09-06 Thread Nekhelesh Ramananthan 
** Changed in: ubuntu-clock-app
   Status: Triaged = In Progress

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

Title:
  Implement Alarm Snooze functionality

Status in Clock application for Ubuntu devices:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  -  Background Info -
  Currently the snap notification shown when an alarm is triggered shows the 
buttons Ok and Show which both does the same thing which is to dismiss the 
alarm.  Since Snap notifications require a minimum of 2 buttons, the only 
choice is to implement the Snooze functionality and replace the Show button 
with Snooze.

  However Snooze was decided to be implemented as part of the SDK
  Alarms API which is worked on by zsombor. As per the blueprint at [1],
  the snooze functionality was to be implemented in revision 0.2 (post-
  RTM).  However we require a solution to the above issue before RTM.

  - Proposed Solution -
  It was decided after discussing with Mirco Mueller, Giorgio Venturi and 
Daniela Ferrai to implement the Snooze functionality as a workaround in the 
Indicator-datetime by dismissing the notification and showing it again after 
the snooze duration. The full design spec is described below.

  1. Provide a settings option in dbus to set the snooze duration that
  the clock app can expose in the settings page to allow the user to
  choose the snooze duration. This is shown in [2]. The snooze duration
  options will be 2, 4, 5 and 10 minutes.

  2. On pressing the Ok button in the snap notification, the alarm
  will be dismissed permanently for the day.

  3. If the user pressed Snooze, then indicator-datetime should
  dismiss the snap notification and show it again after the snooze
  duration. This process will be repeated until the alarm timeout
  defined by the user in the clock app settings. By default that timeout
  is 30 minutes.

  This will require a Go/No-Go decision from Charles Kerr regarding the
  implementation in indicator-datetime since as mentioned above this
  will be a workaround and workaround are not permanent solutions.

  [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api
  [2] 
https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024

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

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

[Touch-packages] [Bug 1364828] Re: neutron unable to create veth devices on utopic

2014-09-06 Thread Bug Watch Updater 
** Changed in: iproute2 (Debian)
   Status: New = Fix Released

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

Title:
  neutron unable to create veth devices on utopic

Status in “iproute2” package in Ubuntu:
  Fix Released
Status in “neutron” package in Ubuntu:
  Fix Released
Status in “iproute2” source package in Utopic:
  Fix Released
Status in “neutron” source package in Utopic:
  Fix Released
Status in “iproute2” package in Debian:
  Fix Released

Bug description:
  Deploying OpenStack Juno on Utopic results in a non-functional cloud
  (at least with neutron).

  On gateway and compute nodes, neutron can't create veth devices AFAICT
  resulting in missing interfaces etc.. and generally broken instance
  connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: neutron-common 1:2014.2~b2-0ubuntu1
  ProcVersionSignature: User Name 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  Date: Wed Sep  3 08:39:35 2014
  Ec2AMI: ami-005d
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.medium
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  PackageArchitecture: all
  SourcePackage: neutron
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.neutron.api.paste.ini: [deleted]
  modified.conffile..etc.neutron.fwaas.driver.ini: [deleted]
  modified.conffile..etc.neutron.l3.agent.ini: [deleted]
  modified.conffile..etc.neutron.neutron.conf: [deleted]
  modified.conffile..etc.neutron.policy.json: [deleted]
  modified.conffile..etc.neutron.rootwrap.conf: [deleted]
  modified.conffile..etc.neutron.rootwrap.d.debug.filters: [deleted]
  modified.conffile..etc.neutron.rootwrap.d.iptables.firewall.filters: [deleted]
  modified.conffile..etc.neutron.rootwrap.d.l3.filters: [deleted]
  modified.conffile..etc.neutron.rootwrap.d.vpnaas.filters: [deleted]
  modified.conffile..etc.neutron.vpn.agent.ini: [deleted]
  modified.conffile..etc.sudoers.d.neutron.sudoers: [deleted]
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  Ec2AMI: ami-005d
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: neutron
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-11-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-11-generic N/A
   linux-backports-modules-3.16.0-11-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic ec2-images
  Uname: Linux 3.16.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2014.1.2:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2014.1.2
  dmi.sys.vendor: OpenStack Foundation

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

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

[Touch-packages] [Bug 1366206] Re: Graphical desktop not starting from livesession

2014-09-06 Thread Elfy 
Appears to only affect a virtual machine.

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

Title:
  Graphical desktop not starting from livesession

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Boot live session - choose Try

  Same issue with at least Xubuntu,Ubuntu and Lubuntu

  No desktop, black screen - change to vt1 - run loginctl show-seat
  seat0 gives CanGraphical=no

  run startx and desktop boots

  this is in a vm on a machine using nvidia card and 331-updates

  appears similar to lp:1365336

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.343
  Date: Fri Sep  5 21:40:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 886481] Re: cannot print after upgrade from natty to oneiric

2014-09-06 Thread Pascal De Vuyst 
Old bug, Ubuntu 11.10 no longer supported.
Please open bug on supported release.

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

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

Title:
  cannot print after upgrade from natty to oneiric

Status in “cups” package in Ubuntu:
  Invalid

Bug description:
  cannot print after upgrade from natty to oneiric

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: cups 1.5.0-8ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Nov  5 09:37:55 2011
  MachineType: Dell Inc. Latitude D630
  Papersize: a4
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: root=UUID=4d92d0f2-fd56-438f-9952-f1e80de75c56 ro quiet 
splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (20 days ago)
  dmi.bios.date: 01/04/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd01/04/2010:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1066612] Re: skype [AOA150, Realtek ALC268, Mic, Internal] No sound at all

2014-09-06 Thread madbiologist 
This is fixed in kernel 3.8. Ubuntu 14.04 Trusty Tahr is using the
3.13 kernel.

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1107477

** Changed in: alsa-driver (Ubuntu)
   Status: New = Fix Released

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

Title:
  skype [AOA150, Realtek ALC268, Mic, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Fix Released

Bug description:
  acer aspireOne AOA150 - internal mic not works with skype. If you open
  the pulse audio sound settings - go to the tab configuration - set
  the sound to disabled and then to analoge stereo dublex again, the
  internal mic works for 3-5 seconds and then stops like to turn of a
  button.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicholas   1305 F xfce4-volumed
nicholas   1317 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5854 irq 45'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,1025015b,00100101'
 Controls  : 15
 Simple ctrls  : 8
  Date: Mon Oct 15 02:04:02 2012
  InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful
  Symptom_Card: Ενσωματωμένος ήχος - HDA Intel
  Symptom_DevicesInUse:
   1305  1317  nicholas  F xfce4-volumed
nicholas  F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Intel successful
  Symptom_Type: No sound at all
  Title: [AOA150, Realtek ALC268, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3114
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3114:bd05/09/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1366345] [NEW] Send button ellipisized in some locales

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using rtm-17, the sms send message is ellipsized in french, showing as 
Env... instead of Envoyer. 
The width seems to be calculated for the english wording, there is enough space 
to show e.g Envoyer and still have enough space in the entry for useful 
content

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

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

Title:
  Send button ellipisized in some locales

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm-17, the sms send message is ellipsized in french, showing as 
Env... instead of Envoyer. 
  The width seems to be calculated for the english wording, there is enough 
space to show e.g Envoyer and still have enough space in the entry for useful 
content

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

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

[Touch-packages] [Bug 1366349] [NEW] Contact entry missing when rotating

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using rtm 17
- open the new message screen by pulling the bottom action widget
- notice that there is a add contacts entry at the top of the screen
- rotate the device in landscape

- the contact entry is missing from the u.i

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

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

Title:
  Contact entry missing when rotating

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm 17
  - open the new message screen by pulling the bottom action widget
  - notice that there is a add contacts entry at the top of the screen
  - rotate the device in landscape

  - the contact entry is missing from the u.i

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

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

[Touch-packages] [Bug 1366350] [NEW] the add contact clue is ellipsized when not needed

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using rtm 17, on krillin, in french, open the new message screen by
pulling the bottom action widget

- the entry add the top has a clue  Ajouter des conta…   with space
on the right for at least 6 more chars, the correct french label is 
Ajouter des contacts… , it could be displayed correctly

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

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

Title:
  the add contact clue is ellipsized when not needed

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm 17, on krillin, in french, open the new message screen by
  pulling the bottom action widget

  - the entry add the top has a clue  Ajouter des conta…   with space
  on the right for at least 6 more chars, the correct french label is 
  Ajouter des contacts… , it could be displayed correctly

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

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

[Touch-packages] [Bug 990032] Re: Dual monitor sticky edges are still enabled when turned off in display manager and Launcher placement is All Displays

2014-09-06 Thread Janek Warchoł 
@johnlea: well, there is one problematic case: if the launcher is set to
autohide and it's placed only on one screen, edges shouldn't be sticky.

For example, i have autohidden launcher on the left edge of my laptop
screen (with an external display positioned to the right of the laptop,
see attached).  There should be no sticky edges in this situation, but
for me the edge is sticky when travelling leftwards - and it's driving
me nuts!!

** Attachment added: display-conf.png
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/990032/+attachment/4197181/+files/display-conf.png

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

Title:
  Dual monitor sticky edges are still enabled when turned off in display
  manager and Launcher placement is All Displays

Status in Ayatana Design:
  Fix Released
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  See also: bug 987787

  Release: Ubuntu 12.04 LTS
  Unity Version: 5.10.0-0ubuntu6
  Expected: Sticky edges turns off when the switch is set to Off
  Actual: Sticky edges remains on regardless of switch position

  I've got two dual monitors running as an extended desktop.  By default
  the Launcher placement property is set to All Displays and sticky
  edges is set to On.

  I like having the launcher on both desktops, but sticky edges is
  driving me nuts.  So, naturally, I turned off sticky edges and left
  the launcher on all displays.  Unfortunately, it seems that the On/Off
  switch for sticky edges serves no purpose when Launcher Placement is
  set to All Displays.

  The option to disable sticky edges in this scenario should be allowed,
  or at the very least the On/Off switch should be disabled and forced
  to On as to not confuse the user.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu6
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,move,unitymtgrabhandles,snap,regex,resize,gnomecompat,animation,place,session,vpswitch,workarounds,grid,mousepoll,expo,wall,ezoom,fade,scale,unityshell]
  Date: Fri Apr 27 14:07:34 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/990032/+subscriptions

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

[Touch-packages] [Bug 882321] Re: ONDA MW503HSA 3g usb modem not working, with open blocked by driver for more than 7 seconds warning

2014-09-06 Thread madbiologist 
Is this fixed in Ubuntu 14.04 Trusty Tahr?

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

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

Title:
  ONDA MW503HSA 3g usb modem not working, with open blocked by driver
  for more than 7 seconds warning

Status in “modemmanager” package in Ubuntu:
  Incomplete

Bug description:
  The same 3g key worked in Natty and Maverick.
  Only appearent difference in the syslog in Oneiric is the open blocked by 
driver for more than 7 seconds! warning.
  Judging from a Fedora users' forum discussion it seems like it's the latest 
version of modemmanager causing this issue on similar hardware:
  
http://www.fedoraonline.it/modules/newbb/viewtopic.php?viewmode=flattopic_id=16200forum=41

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: modemmanager 0.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Oct 27 01:02:22 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1366350] Re: the add contact clue is ellipsized when not needed

2014-09-06 Thread Sebastien Bacher 
The issue is in src/qml/MultiRecipientInput.qml:145, the code has a

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

Title:
  the add contact clue is ellipsized when not needed

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm 17, on krillin, in french, open the new message screen by
  pulling the bottom action widget

  - the entry add the top has a clue  Ajouter des conta…   with space
  on the right for at least 6 more chars, the correct french label is 
  Ajouter des contacts… , it could be displayed correctly

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

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

[Touch-packages] [Bug 1366350] Re: the add contact clue is ellipsized when not needed

2014-09-06 Thread Sebastien Bacher 
has a FIXME saying the size should be variable, it's currently fixed to
gu(20), commenting the width workarounds the issue and makes the U.I
still looks right, does that force value need to be there?

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

Title:
  the add contact clue is ellipsized when not needed

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm 17, on krillin, in french, open the new message screen by
  pulling the bottom action widget

  - the entry add the top has a clue  Ajouter des conta…   with space
  on the right for at least 6 more chars, the correct french label is 
  Ajouter des contacts… , it could be displayed correctly

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

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

[Touch-packages] [Bug 1366355] [NEW] getty allows to move cursor using arrow keys

2014-09-06 Thread hon 
Public bug reported:

util-linux version: 2.20.1-1ubuntu3.1
Switch to tty. Press any arrow key. Cursor has been moved. You may type and 
replace labels or write own text.
getty should not allow move cursor out of login field.

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  getty allows to move cursor using arrow keys

Status in “util-linux” package in Ubuntu:
  New

Bug description:
  util-linux version: 2.20.1-1ubuntu3.1
  Switch to tty. Press any arrow key. Cursor has been moved. You may type and 
replace labels or write own text.
  getty should not allow move cursor out of login field.

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

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

[Touch-packages] [Bug 1366356] [NEW] the bug when loading it says error missing file

2014-09-06 Thread Cris R. Laresma 
Public bug reported:

during loading theres a problem it says error missing file clikc to
continue

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
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: Sun Sep  7 00:18:46 2014
DistUpgraded: 2014-08-22 07:13:20,302 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:2400]
InstallationDate: Installed on 2012-11-12 (663 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423)
MachineType: CLEVO CO. W24xCZ
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=2e0045c6-833e-4cc3-83c2-62cbba1def82 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-08-21 (15 days ago)
dmi.bios.date: 08/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W24xCZ
dmi.board.vendor: CLEVO CO.
dmi.board.version: V3.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/30/2012:svnCLEVOCO.:pnW24xCZ:pvrNotApplicable:rvnCLEVOCO.:rnW24xCZ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: W24xCZ
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sun Sep  7 00:08:40 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 901 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  the bug when loading it says error missing file

Status in “xorg” package in Ubuntu:
  New

Bug description:
  during loading theres a problem it says error missing file clikc to
  continue

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  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: Sun Sep  7 00:18:46 2014
  DistUpgraded: 2014-08-22 07:13:20,302 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:2400]
  InstallationDate: Installed on 2012-11-12 (663 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MachineType: CLEVO CO. W24xCZ
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=2e0045c6-833e-4cc3-83c2-62cbba1def82 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-08-21 (15 days ago)
  dmi.bios.date: 08/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W24xCZ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag

[Touch-packages] [Bug 1366355] Re: getty allows to move cursor using arrow keys

2014-09-06 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: util-linux (Ubuntu)
   Status: New = Confirmed

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

Title:
  getty allows to move cursor using arrow keys

Status in “util-linux” package in Ubuntu:
  Confirmed

Bug description:
  util-linux version: 2.20.1-1ubuntu3.1
  Switch to tty. Press any arrow key. Cursor has been moved. You may type and 
replace labels or write own text.
  getty should not allow move cursor out of login field.

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

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

[Touch-packages] [Bug 1366358] [NEW] Display am/pm next to 24 hours values

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using rtm-17 in french locale, the messages list displays 24 hours marks
on the right, but it appends am/pm next to those (e.g 19:31 pm), the
am/pm shouldn't be displayed when the locale use 24 hours

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

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

Title:
  Display am/pm next to 24 hours values

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm-17 in french locale, the messages list displays 24 hours
  marks on the right, but it appends am/pm next to those (e.g 19:31
  pm), the am/pm shouldn't be displayed when the locale use 24 hours

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

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

[Touch-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality

2014-09-06 Thread Launchpad Bug Tracker 
** Branch linked: lp:~nik90/ubuntu-clock-app/implement-snooze-settings

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

Title:
  Implement Alarm Snooze functionality

Status in Clock application for Ubuntu devices:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  -  Background Info -
  Currently the snap notification shown when an alarm is triggered shows the 
buttons Ok and Show which both does the same thing which is to dismiss the 
alarm.  Since Snap notifications require a minimum of 2 buttons, the only 
choice is to implement the Snooze functionality and replace the Show button 
with Snooze.

  However Snooze was decided to be implemented as part of the SDK
  Alarms API which is worked on by zsombor. As per the blueprint at [1],
  the snooze functionality was to be implemented in revision 0.2 (post-
  RTM).  However we require a solution to the above issue before RTM.

  - Proposed Solution -
  It was decided after discussing with Mirco Mueller, Giorgio Venturi and 
Daniela Ferrai to implement the Snooze functionality as a workaround in the 
Indicator-datetime by dismissing the notification and showing it again after 
the snooze duration. The full design spec is described below.

  1. Provide a settings option in dbus to set the snooze duration that
  the clock app can expose in the settings page to allow the user to
  choose the snooze duration. This is shown in [2]. The snooze duration
  options will be 2, 4, 5 and 10 minutes.

  2. On pressing the Ok button in the snap notification, the alarm
  will be dismissed permanently for the day.

  3. If the user pressed Snooze, then indicator-datetime should
  dismiss the snap notification and show it again after the snooze
  duration. This process will be repeated until the alarm timeout
  defined by the user in the clock app settings. By default that timeout
  is 30 minutes.

  This will require a Go/No-Go decision from Charles Kerr regarding the
  implementation in indicator-datetime since as mentioned above this
  will be a workaround and workaround are not permanent solutions.

  [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api
  [2] 
https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024

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

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

[Touch-packages] [Bug 1366364] [NEW] Count sms that failed to be sent as sent on the greeter

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using rtm 17 on krillin, after having some failed message sending (e.g
tried to send a contact info and a photo on a phone without data plan),
the lock screen animation displays a count including those messages,
that seems wrong

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

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

Title:
  Count sms that failed to be sent as sent on the greeter

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm 17 on krillin, after having some failed message sending (e.g
  tried to send a contact info and a photo on a phone without data
  plan), the lock screen animation displays a count including those
  messages, that seems wrong

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

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

[Touch-packages] [Bug 1366367] [NEW] Doesn't explain why messages failed to be send

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using rtm 17 on krillin

Trying to send a contact info or a picture from a photo without data
plan leads to an error, that might be expected but it would be nice to
give a clue in the U.I when the message failed to be sent

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

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

Title:
  Doesn't explain why messages failed to be send

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Using rtm 17 on krillin

  Trying to send a contact info or a picture from a photo without data
  plan leads to an error, that might be expected but it would be nice to
  give a clue in the U.I when the message failed to be sent

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

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

[Touch-packages] [Bug 1366373] [NEW] Interface to add new contacts from messaging is not obvious

2014-09-06 Thread Sebastien Bacher 
Public bug reported:

Using rtm 17
- open the messaging application
- click on a message from somebody not in your contact
- click on the top right new contact icon

- the contacts application is open, it has a new contact line at the
bottom but it's not obvious that is going to copy the number you
selected, the item rather looks like it's not create a new contact from
scratch, not to add the messaging one

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

** Summary changed:

- Interface to add new contacts not obvious
+ Interface to add new contacts from messaging is not obvious

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

Title:
  Interface to add new contacts from messaging is not obvious

Status in “address-book-app” package in Ubuntu:
  New

Bug description:
  Using rtm 17
  - open the messaging application
  - click on a message from somebody not in your contact
  - click on the top right new contact icon

  - the contacts application is open, it has a new contact line at
  the bottom but it's not obvious that is going to copy the number you
  selected, the item rather looks like it's not create a new contact
  from scratch, not to add the messaging one

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

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

[Touch-packages] [Bug 1366206] Re: Graphical desktop not starting from livesession

2014-09-06 Thread Elfy 
Booted usb to hardware and installed - not present there at all.

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

Title:
  Graphical desktop not starting from livesession

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Boot live session - choose Try

  Same issue with at least Xubuntu,Ubuntu and Lubuntu

  No desktop, black screen - change to vt1 - run loginctl show-seat
  seat0 gives CanGraphical=no

  run startx and desktop boots

  this is in a vm on a machine using nvidia card and 331-updates

  appears similar to lp:1365336

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.343
  Date: Fri Sep  5 21:40:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1366380] Re: telepathy-mission-control is trying to open weird files on startup

2014-09-06 Thread Piotr Gołębiewski 
More about this bug http://askubuntu.com/questions/490690/how-to-fix-
apparmor-denied-for-telepathy-mission-control-5-under-ubuntu-14-04

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

Title:
  telepathy-mission-control is trying to open weird files on startup

Status in “telepathy-mission-control-5” package in Ubuntu:
  New

Bug description:
  Upon startup I'm getting a notice that an error occured. When I check
  the syslog I see errors like:

  Sep  6 19:57:22 Earth kernel: [   86.045357] type=1400 
audit(1410026242.433:76): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462
 pid=3007 comm=mission-control requested_mask=rw denied_mask=rw 
fsuid=1000 ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.045707] type=1400 
audit(1410026242.433:77): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.050493] type=1400 
audit(1410026242.437:78): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F64636F6E662F75736572
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.108894] type=1400 
audit(1410026242.497:79): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000

  According to http://askubuntu.com/questions/410808/what-is-reason-for-
  apparmor-denied-operation-open, telepathy-mission-control-5 is trying
  to open a file it has no access to.

  However, the name part is completely rubbish. How can check what
  file telepathy is actually trying to open? How do I fix that?

  I am on Ubuntu 14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1366380/+subscriptions

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

[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup

2014-09-06 Thread Bernard Decock 
Hi,

I fear that that the backtrace will be rather disappointing, as the gdb
doesn't find any symbols for the pcscd-binary. Now the odd thing is, if
you start the gdb if you then remove the card-reader for the first time,
it doesn't crash. It is only the second time when the read is removed
that the application crashes. As there are no symbols, you get only the
addresses in the backtrace. If the gdb starts its notifies me that
already another instance of pcscd is running.

If you look at the green led of the reader, it goes out just before
ubuntu-login-screen pops up. If you remove the reader and plug the
reader back in, the green led goes on for a second or two and then goes
back out.



** Attachment added: LogGdbVascoReader.txt
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4197264/+files/LogGdbVascoReader.txt

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

Title:
  System crash when Vasco-card-reader is plugged in at powerup

Status in “pcsc-lite” package in Ubuntu:
  New

Bug description:
  I'm using VASCO Data Security International Digipass 905 SmartCard Reader 
which is working fine. However if the device is plugged in at power-up, the 
device isn't handled well. Although the device is in the ilisted usb-devices, 
pcsc-scan doesn't find the device at all (Which is normal as the green-led is 
going out after the kernel starts). If one tries to remove the card-reader,
  a system-crash happens. After that the pcscd-service seems to be halted :
  pcsc_scan
  PC/SC device scanner
  V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
  Compiled with PC/SC lite version: 1.8.10
  SCardEstablishContext: Service not available.

  One can recover from this problem by
  1. Unplugging the reader
  2. Manually starting the service again by sudo service pcscd start 
  3. Plugging back the reader in (green led stays on, red led goes on when a 
card is put in)

  The bug is not related to a 64-bit architecture as it happens also
  with 32-bit machines.

  Info about the device
  Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 
905 SmartCard Reader
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x1a44 VASCO Data Security International
idProduct  0x0001 Digipass 905 SmartCard Reader
bcdDevice1.02
iManufacturer   1 
iProduct2 
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   93
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass11 Chip/SmartCard
bInterfaceSubClass  0 
bInterfaceProtocol  0 
iInterface  0 
ChipCard Interface Descriptor:
  bLength54
  bDescriptorType33
  bcdCCID  1.00
  nMaxSlotIndex   0
  bVoltageSupport 3  5.0V 3.0V 
  dwProtocols 3  T=0 T=1
  dwDefaultClock   3700
  dwMaxiumumClock  3700
  bNumClockSupported  1
  dwDataRate   9946 bps
  dwMaxDataRate  318280 bps
  bNumDataRatesSupp. 53
  dwMaxIFSD 254
  dwSyncProtocols  0007  2-wire 3-wire I2C
  dwMechanical  
  dwFeatures   000404BE
Auto configuration based on ATR
Auto activation on insert
Auto voltage selection
Auto clock change
Auto baud rate change
Auto PPS made by CCID
Auto IFSD exchange
Short and extended APDU level exchange
  dwMaxCCIDMsgLen   272
  bClassGetResponseecho
  bClassEnvelope   echo
  wlcdLayout   none
  bPINSupport 0 
  bMaxCCIDBusySlots   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None

[Touch-packages] [Bug 1365752] Re: ubuntu-desktop depends on iBus, which is totally broken

2014-09-06 Thread Mathew Hodson 
** Tags added: trusty

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

Title:
  ubuntu-desktop depends on iBus, which is totally broken

Status in “ubuntu-meta” package in Ubuntu:
  New

Bug description:
  Upgrading from Ubuntu 12.04 to 14.04 the package iBus has been
  installed in the system and activated by default. This has caused an
  amount of pain because it has completely broken the input method
  (symptoms: no en-uk keyboard available composite not working, backtick
  to be pressed twice). The problems are reported in a number of places;
  I've read somewhere I can't remember that Unity has some form of
  workaround against ibus but I don't use Unity (using Awesome on some
  systems, lubuntu on another one) and other windows managers are
  affected.

  Even disabling ibus (which has to be done via gnome-language-selector,
  instead of the keyboard panel in gnome-control-center, which is an
  usability problem that deserves its own bug report) the ibus processes
  keep on running. Probably this has no consequence but still there is
  no reason to have unwanted running processes. I have no idea where do
  these processes start, but I clearly have the idea that they shouldn't
  be running where not necessary.

  Uninstalling ibus is not straightforward because the ubuntu-desktop
  package depends on it. The dependency the core package ubuntu-desktop
  on ibus is excessive for a package that is 1) unneeded by many users
  and 2) broken for many users.

  The best solution to date is to:

  ibus exit
  sudo mv /usr/lib/ibus{,.bak}
  sudo mv /usr/bin/ibus{,.bak}

  Please remove the dependency of ubuntu-desktop on ibus and avoid
  installing it for european languages.

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

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

[Touch-packages] [Bug 435968] Re: vlc assert failure: vlc: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:1485: process_command( JumpSS_VTSM): Assertion `0' failed.

2014-09-06 Thread Benjamin Drung 
FTR, commit 7b131b5f202b64708497db1feee95e6570dbeed1 [1] was committed
on 2013-02-21 and part of the upstream release 5.0.0. Therefore this bug
is fixed in Ubuntu 14.10 (utopic) with libdvdnav 5.0.0-1.

[1]
http://git.videolan.org/?p=libdvdnav.git;a=commitdiff;h=7b131b5f202b64708497db1feee95e6570dbeed1

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

Title:
  vlc assert failure: vlc:
  /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:1485: process_command(
  JumpSS_VTSM): Assertion `0' failed.

Status in “libdvdnav” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: vlc

  vlc crashes when open disc is chosen

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: vlc: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:1485: 
process_command: Assertion `0' failed.
  CrashCounter: 1
  Date: Thu Sep 24 17:07:55 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/vlc
  Package: vlc-nox 1.0.1-2ubuntu1
  ProcCmdline: vlc
  ProcEnviron:
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
  Signal: 6
  SourcePackage: vlc
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libc.so.6
   abort () from /lib/tls/i686/cmov/libc.so.6
   __assert_fail () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /usr/lib/libdvdnav.so.4
  Title: vlc assert failure: vlc: 
/build/buildd/libdvdnav-4.1.3/src/vm/vm.c:1485: process_command: Assertion `0' 
failed.
  Uname: Linux 2.6.31-10-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup

2014-09-06 Thread Ludovic Rousseau 
Could you rebuild pcsc-lite and libccid yourself and install them in
/usr/local/ or somewhere else to try to debug the problem?

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

Title:
  System crash when Vasco-card-reader is plugged in at powerup

Status in “pcsc-lite” package in Ubuntu:
  New

Bug description:
  I'm using VASCO Data Security International Digipass 905 SmartCard Reader 
which is working fine. However if the device is plugged in at power-up, the 
device isn't handled well. Although the device is in the ilisted usb-devices, 
pcsc-scan doesn't find the device at all (Which is normal as the green-led is 
going out after the kernel starts). If one tries to remove the card-reader,
  a system-crash happens. After that the pcscd-service seems to be halted :
  pcsc_scan
  PC/SC device scanner
  V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr
  Compiled with PC/SC lite version: 1.8.10
  SCardEstablishContext: Service not available.

  One can recover from this problem by
  1. Unplugging the reader
  2. Manually starting the service again by sudo service pcscd start 
  3. Plugging back the reader in (green led stays on, red led goes on when a 
card is put in)

  The bug is not related to a 64-bit architecture as it happens also
  with 32-bit machines.

  Info about the device
  Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 
905 SmartCard Reader
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x1a44 VASCO Data Security International
idProduct  0x0001 Digipass 905 SmartCard Reader
bcdDevice1.02
iManufacturer   1 
iProduct2 
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   93
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass11 Chip/SmartCard
bInterfaceSubClass  0 
bInterfaceProtocol  0 
iInterface  0 
ChipCard Interface Descriptor:
  bLength54
  bDescriptorType33
  bcdCCID  1.00
  nMaxSlotIndex   0
  bVoltageSupport 3  5.0V 3.0V 
  dwProtocols 3  T=0 T=1
  dwDefaultClock   3700
  dwMaxiumumClock  3700
  bNumClockSupported  1
  dwDataRate   9946 bps
  dwMaxDataRate  318280 bps
  bNumDataRatesSupp. 53
  dwMaxIFSD 254
  dwSyncProtocols  0007  2-wire 3-wire I2C
  dwMechanical  
  dwFeatures   000404BE
Auto configuration based on ATR
Auto activation on insert
Auto voltage selection
Auto clock change
Auto baud rate change
Auto PPS made by CCID
Auto IFSD exchange
Short and extended APDU level exchange
  dwMaxCCIDMsgLen   272
  bClassGetResponseecho
  bClassEnvelope   echo
  wlcdLayout   none
  bPINSupport 0 
  bMaxCCIDBusySlots   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0004  1x 4 bytes
  bInterval  32
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0010  1x 16 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN
  bmAttributes2
Transfer Type

[Touch-packages] [Bug 1296378] Re: Activate VP9 codec in libav

2014-09-06 Thread Oibaf 
@mossroy:
You should be able to also encode in vp9 now in utopic.

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

Title:
  Activate VP9 codec in libav

Status in “libav” package in Ubuntu:
  Fix Released

Bug description:
  avconv -encoders | grep vp gives only :
  V... libvpx   libvpx VP8 (codec vp8)

  It does not give the encoder libvpx-vp9, which seems to be necessary to 
encode with VP9.
  Or maybe I missed something?

  Based on 
http://git.libav.org/?p=libav.git;a=commit;h=9aa053ceded5550b2e538578af383fd89d82364c
 , VP9 is available in libvpx since version 1.3.0 , which is the version libav 
is built with : http://packages.ubuntu.com/trusty/libvpx1
  VP9 is also mentioned in the changelog of the libvpx1 package : 
http://changelogs.ubuntu.com/changelogs/pool/main/libv/libvpx/libvpx_1.3.0-2/changelog

  
  Same issue when trying to read a file with VP9 codec. I tried with 
http://base-n.de/webm/out9.webm
  avplay out9.webm gives :
  [matroska,webm @ 0x7f1a80005be0] Unknown/unsupported AVCodecID V_VP9

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

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

[Touch-packages] [Bug 1365875] Re: mail notification displayed even when phone locked

2014-09-06 Thread James Hunt 
** Information type changed from Public to Public Security

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

Title:
  mail notification displayed even when phone locked

Status in The Unity 8 shell:
  New
Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  I had just woken up the phone (screen was displaying the welcome
  greeter) but had not yet unlocked the device (I have set a pin code)
  when a mail notification appeared on screen that divulged the sender.

  This is a privacy issue.

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

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

[Touch-packages] [Bug 1366388] [NEW] ubuntu-desktop should recommend gnome-mines instead of gnomine

2014-09-06 Thread Mathew Hodson 
Public bug reported:

gnomine is a transitional package, so ubuntu-desktop shouldn't recommend
it.

It should recommend gnome-mines instead, which is the single dependency
of gnomine.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-desktop 1.325
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep  6 15:15:51 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-11-01 (674 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago)

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

Title:
  ubuntu-desktop should recommend gnome-mines instead of gnomine

Status in “ubuntu-meta” package in Ubuntu:
  New

Bug description:
  gnomine is a transitional package, so ubuntu-desktop shouldn't
  recommend it.

  It should recommend gnome-mines instead, which is the single
  dependency of gnomine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop 1.325
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep  6 15:15:51 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-01 (674 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago)

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

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

[Touch-packages] [Bug 1366391] [NEW] re-prompted for already-known password when switching networks

2014-09-06 Thread James Hunt 
Public bug reported:

When I re-connect to a known network, I am prompted for the WPA2
password. However, clicking cancel then successfully connects to this
network!

This is only happening for one of my networks. Not currently sure why
since the other main network I use is also WPA2 protected and I'm not
prompted for that networks password. I wonder if the re-prompt only
occurs if the user attempts to connect to a different network to the
first-joined network on boot (can't test atm).

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


** Tags: avengers

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

Title:
  re-prompted for already-known password when switching networks

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  When I re-connect to a known network, I am prompted for the WPA2
  password. However, clicking cancel then successfully connects to this
  network!

  This is only happening for one of my networks. Not currently sure why
  since the other main network I use is also WPA2 protected and I'm not
  prompted for that networks password. I wonder if the re-prompt only
  occurs if the user attempts to connect to a different network to the
  first-joined network on boot (can't test atm).

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

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

[Touch-packages] [Bug 1366393] [NEW] initramfs-tools should depend on kmod instead of module-init-tools

2014-09-06 Thread Mathew Hodson 
Public bug reported:

module-init-tools is a transitional dummy package to transition to kmod,
so initramfs-tools shouldn't depend on it.

It should directly depend on kmod instead. This wouldn't bring in any
new packages or require any code changes, because initramfs-tools
already indirectly depends on kmod.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: initramfs-tools 0.103ubuntu4.2
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep  6 15:25:36 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-11-01 (674 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago)

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

Title:
  initramfs-tools should depend on kmod instead of module-init-tools

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  module-init-tools is a transitional dummy package to transition to
  kmod, so initramfs-tools shouldn't depend on it.

  It should directly depend on kmod instead. This wouldn't bring in any
  new packages or require any code changes, because initramfs-tools
  already indirectly depends on kmod.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep  6 15:25:36 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-01 (674 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago)

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

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

[Touch-packages] [Bug 1296378] Re: Activate VP9 codec in libav

2014-09-06 Thread Mossroy 
That's true : Utopic now ships with libav-tools version 6:11~beta1-2, that is 
able to encode with VP9 codec inside a WebM container.
Great!

For those using Trusty, there are a few ways to encode with VP9 anyway (without 
upgrading to Utopic or running it inside a virtual machine) :
- compile libav 11 beta 1 under Trusty
- use Utopic libraries inside a Docker container
I explained these 2 options in 
http://blog.mossroy.fr/2014/09/03/encoder-des-videos-avec-le-codec-vp9-sur-ubuntu-trusty-en-utilisant-libav-et-docker/
 (in French) , with some generated videos and comparisons with VP8
- it's certainly also possible to upgrade libav with a PPA, but I did not want 
to pollute my OS (some programs that depend on libav might be broken)

Thanks for the upgrade in Utopic

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

Title:
  Activate VP9 codec in libav

Status in “libav” package in Ubuntu:
  Fix Released

Bug description:
  avconv -encoders | grep vp gives only :
  V... libvpx   libvpx VP8 (codec vp8)

  It does not give the encoder libvpx-vp9, which seems to be necessary to 
encode with VP9.
  Or maybe I missed something?

  Based on 
http://git.libav.org/?p=libav.git;a=commit;h=9aa053ceded5550b2e538578af383fd89d82364c
 , VP9 is available in libvpx since version 1.3.0 , which is the version libav 
is built with : http://packages.ubuntu.com/trusty/libvpx1
  VP9 is also mentioned in the changelog of the libvpx1 package : 
http://changelogs.ubuntu.com/changelogs/pool/main/libv/libvpx/libvpx_1.3.0-2/changelog

  
  Same issue when trying to read a file with VP9 codec. I tried with 
http://base-n.de/webm/out9.webm
  avplay out9.webm gives :
  [matroska,webm @ 0x7f1a80005be0] Unknown/unsupported AVCodecID V_VP9

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

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

[Touch-packages] [Bug 1366406] [NEW] Virtualbox capture error webm(vp8)

2014-09-06 Thread Swatch 
Public bug reported:

virtualbox libvpx used to capture video in webm format, in ubuntu the file 
created is corrupt using the relevant library.
Ubuntu 14.04.1
Virtualbox Version: 4.3.14 r95030

Forum virtualbox
https://forums.virtualbox.org/viewtopic.php?f=7t=63487.

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

** Attachment added: I file generated is not correct
   
https://bugs.launchpad.net/bugs/1366406/+attachment/4197396/+files/vlc_virtualbox.png

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

Title:
  Virtualbox capture error webm(vp8)

Status in “libvpx” package in Ubuntu:
  New

Bug description:
  virtualbox libvpx used to capture video in webm format, in ubuntu the file 
created is corrupt using the relevant library.
  Ubuntu 14.04.1
  Virtualbox Version: 4.3.14 r95030

  Forum virtualbox
  https://forums.virtualbox.org/viewtopic.php?f=7t=63487.

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

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

[Touch-packages] [Bug 1366413] [NEW] Android tethering does not work when network manager is running

2014-09-06 Thread Danilo de Andrade Mendes 
Public bug reported:

After lost many hours trying to discover why the USB Tethering of my LG
E615f and my friend's LG E470 android phones, I just realised:

(with cable unplugged)
alex@ubuntu_asus:~$ sudo start network-manager 
network-manager start/running, process 3843
(plugging the cable and start tethering)
alex@ubuntu_asus:~$ ip link
(...)
9: usb0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state 
DOWN qlen 1000
link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff

But, when I try without network-manager
(with cable unplugged)
alex@ubuntu_asus:~$ sudo stop network-manager
network-manager stop/waiting
(plugging again and starting tethering)
alex@ubuntu_asus:~$ ip addr
(...)
10: usb0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff

I tried many times and aways got the same result.
I've found this problem in both raring and Ubuntu 14.04, but only in raring I 
have tested this soluction.

alex@ubuntu_asus:~$ lsb_release -rd
Description:Ubuntu 12.04.4 LTS
Release:12.04
alex@ubuntu_asus:~$ apt-cache policy network-manager
network-manager:
  Installed: 0.9.4.0-0ubuntu4.3
  Candidate: 0.9.8.0-0ubuntu6.1
  Version table:
 0.9.8.0-0ubuntu6.1 0
500 http://old-releases.ubuntu.com/ubuntu/ raring-updates/main amd64 
Packages
 0.9.8.0-0ubuntu6 0
500 http://old-releases.ubuntu.com/ubuntu/ raring/main amd64 Packages
 *** 0.9.4.0-0ubuntu4.3 0
100 /var/lib/dpkg/status

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


** Tags: android carrier tethering usb

** Attachment added: tail from syslog with and without nm running
   https://bugs.launchpad.net/bugs/1366413/+attachment/4197398/+files/out-nm.log

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

Title:
  Android tethering does not work when network manager is running

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  After lost many hours trying to discover why the USB Tethering of my
  LG E615f and my friend's LG E470 android phones, I just realised:

  (with cable unplugged)
  alex@ubuntu_asus:~$ sudo start network-manager 
  network-manager start/running, process 3843
  (plugging the cable and start tethering)
  alex@ubuntu_asus:~$ ip link
  (...)
  9: usb0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state 
DOWN qlen 1000
  link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff

  But, when I try without network-manager
  (with cable unplugged)
  alex@ubuntu_asus:~$ sudo stop network-manager
  network-manager stop/waiting
  (plugging again and starting tethering)
  alex@ubuntu_asus:~$ ip addr
  (...)
  10: usb0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000
  link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff

  I tried many times and aways got the same result.
  I've found this problem in both raring and Ubuntu 14.04, but only in raring I 
have tested this soluction.

  alex@ubuntu_asus:~$ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04
  alex@ubuntu_asus:~$ apt-cache policy network-manager
  network-manager:
Installed: 0.9.4.0-0ubuntu4.3
Candidate: 0.9.8.0-0ubuntu6.1
Version table:
   0.9.8.0-0ubuntu6.1 0
  500 http://old-releases.ubuntu.com/ubuntu/ raring-updates/main amd64 
Packages
   0.9.8.0-0ubuntu6 0
  500 http://old-releases.ubuntu.com/ubuntu/ raring/main amd64 Packages
   *** 0.9.4.0-0ubuntu4.3 0
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1366419] [NEW] [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal soundcard to off

2014-09-06 Thread oneindelijk 
Public bug reported:

There seems to be no easy way to tell the application which soundcard to
choose. Sometimes it works, sometimes it works half, but mostly it
doesn't work.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
Date: Sat Sep  6 16:38:49 2014
InstallationDate: Installed on 2014-07-14 (54 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB failed
Symptom_Card: E-Mu 0404 - E-MU 0404 | USB
Symptom_Type: None of the above
Title: [USB-Audio - E-MU 0404 | USB, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZI Ver. F.0F
dmi.board.name: 3072
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 24.0D
dmi.chassis.asset.tag: CNU9501Y74
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.0F:bd10/20/2009:svnHewlett-Packard:pnHPProBook4510s:pvrF.0F:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4510s
dmi.product.version: F.0F
dmi.sys.vendor: Hewlett-Packard

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

Title:
  [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal
  soundcard to off

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  There seems to be no easy way to tell the application which soundcard
  to choose. Sometimes it works, sometimes it works half, but mostly it
  doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Sat Sep  6 16:38:49 2014
  InstallationDate: Installed on 2014-07-14 (54 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB failed
  Symptom_Card: E-Mu 0404 - E-MU 0404 | USB
  Symptom_Type: None of the above
  Title: [USB-Audio - E-MU 0404 | USB, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.0F
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0D
  dmi.chassis.asset.tag: CNU9501Y74
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.0F:bd10/20/2009:svnHewlett-Packard:pnHPProBook4510s:pvrF.0F:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.0F
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1366418] [NEW] Bluetooth BCM43142A0 doesn’t work

2014-09-06 Thread ghortor 
Public bug reported:

I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
(computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
displayed in the menu bar, if I open the bluetooth UI and switch on,
nothing happens and the result of “hcitool dev” is empty.

I have tried to install the windows driver with ndiswrapper, and the
bluetooth device seems to be detected as an usb bluetooth device but
still not working. I then add the device to the bluetooth usb device and
was able to activate bluetooth in the UI but it does not detect any
other devices (I’ve tested with a smartphone).

The driver I have installed can be found in asus page =
http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
Select Windows OS, then “bluetooth” section, take the Broadcom driver
(should be the first one).

If you extract this archive, you will find a file named “bcbtums-
win8x64-brcm.inf” which I installed using the following command:

ndiswrapper -i bcbtums-win8x64-brcm.inf

Then, the result of “ndiswrapper -l” is:

bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

in usb-devices, I find a device which was not present before
installation (I might have activated btusb before on this paste):

T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=04ca ProdID=2006 Rev=01.12
S:  Manufacturer=Broadcom Corp
S:  Product=BCM43142A0
S:  SerialNumber=B8EE6593D989
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

then, “echo 04ca 2006  /sys/bus/usb/drivers/btusb/new_id”, and I can
switch usb on, but no device will be detected and I’ve found this in the
dmesg:

[2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

which looks pretty much like a “bluetooth not working” message which I
don’t understand in details.

I leave here my full dmesg:

[0.253889] NetLabel:  domain hash size = 128
[0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
[0.253901] NetLabel:  unlabeled traffic allowed by default
[0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[0.255995] Switched to clocksource hpet
[0.260468] AppArmor: AppArmor Filesystem Enabled
[0.260488] pnp: PnP ACPI init
[0.260500] ACPI: bus type PNP registered
[0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
[0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[0.260642] pnp 00:01: [dma 4]
[0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
[0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
[0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
[0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
[0.260927] system 00:04: [io  0x] has been reserved
[0.260928] system 00:04: [io  0x] has been reserved
[0.260930] system 00:04: [io  0x] has been reserved
[0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
[0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
[0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
[0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
[0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
[0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
[0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
[0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
[0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
[0.261059] system 00:07: [io  0x04d0-0x04d1] has been reserved
[0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[0.261089] system 00:08: [io  0x0240-0x0259] has been reserved
[0.261091] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[0.261144] pnp 00:09: Plug and Play ACPI device, IDs FLT0101 SYN0a00 
SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
[0.261179] pnp 00:0a: Plug and Play ACPI device, IDs ATK3001 PNP030b 
(active)
[0.261509] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
[0.261757] system 00:0c: [mem 0xfed1c000-0xfed1] has been reserved
[0.261759] system 00:0c: [mem 0xfed1-0xfed17fff] has been reserved
[0.261761] system 00:0c: [mem 0xfed18000-0xfed18fff] has been reserved
[0.261763] system 00:0c: [mem 0xfed19000-0xfed19fff] has been reserved
[0.261765] system 00:0c: [mem 0xf800-0xfbff] has been reserved
[0.261766] system 00:0c: [mem 0xfed2-0xfed3] has been

[Touch-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer

2014-09-06 Thread Ruben Rocha 
The upstream developers have fixed it

Shouldnt the LTS version be fixed first and get almost all the attention
from developers? Also 12.04.5 has a major flaw if you try to install
virtualbox... the kernel module isnt yet available. Another LTS fail.

Everything is going the wrong way with ubuntu...

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Confirmed
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions

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

[Touch-packages] [Bug 1366426] [NEW] [Super][Alt] is interpreted as [Super] if [Super] is pressed first

2014-09-06 Thread Gauthier Ostervall 
Public bug reported:

If Super is pressed first in a SuperAltkey chord, Alt is
disregarded.

Steps:
- go to Settings-Keyboard-Shortcuts-Launchers
- set the shortcut for Launch calculator to Alt+Super+C (note, here the order 
in which Alt and Super are pressed does not matter)
- press Alt+Super+C (in that order, Alt first). The calculator launches.
- press Super+Alt+C (in that order, Super first). The dash opens with the 
Photos lens.

Tested on two different machines (14.04) and keyboards, and with a
freshly created user.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Sun Sep  7 00:12:12 2014
InstallationDate: Installed on 2014-09-01 (5 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [Super][Alt] is interpreted as [Super] if [Super] is pressed first

Status in “unity” package in Ubuntu:
  New

Bug description:
  If Super is pressed first in a SuperAltkey chord, Alt is
  disregarded.

  Steps:
  - go to Settings-Keyboard-Shortcuts-Launchers
  - set the shortcut for Launch calculator to Alt+Super+C (note, here the 
order in which Alt and Super are pressed does not matter)
  - press Alt+Super+C (in that order, Alt first). The calculator launches.
  - press Super+Alt+C (in that order, Super first). The dash opens with the 
Photos lens.

  Tested on two different machines (14.04) and keyboards, and with a
  freshly created user.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Sep  7 00:12:12 2014
  InstallationDate: Installed on 2014-09-01 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

2014-09-06 Thread Andreas 
Same here.
It happens seldom but it's really annoying.
For me the fix from the duplicate bug comments

gsettings set org.gnome.desktop.input-sources current 0

works fine.

Funny thing: 
Login has german layout (my password wouldnt work otherwise) but the gnome 
shell has already us keyboard, eg [] instaed of öä.
Don't have unity installed.

Its a fresh ubuntu 14.04 gnome install on an ideapad .

System settings have only german an report  german even if have us
layout.

(And everybody who thinks this is only low priority should be forced to
use a strange keyboard layout for more than 1h while working... ;)

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=de_DE.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL=pc105
  XKBLAYOUT=de
  XKBVARIANT=
  XKBOPTIONS=

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 530240] Re: lvextend segfault on logical volume extend

2014-09-06 Thread Bug Watch Updater 
** Changed in: lvm2
   Status: New = Fix Released

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

Title:
  lvextend segfault on logical volume extend

Status in lvm2 - Logical Volume Manager:
  Fix Released
Status in “lvm2” package in Ubuntu:
  New

Bug description:
  Binary package hint: lvm2

  My system is running 2.6.31-20-generic #57-Ubuntu SMP AMD64 (current
  karmic-proposed).

  Below is the series of commands executed on my logical volumes, two of
  them currently open were extended 20GB (prior to file system resize),
  and then I wanted to consume the remaining extends on one of them.

  Prior to executing these commands I removed two other existing volumes
  in the same group order to free up the space.

  My pv's sit on top of a RAID1 md device as shown below, similar to a
  debian report here: http://bugs.debian.org/561931

  
  From dpkg:

  ii lvm22.02.39-0ubuntu11

  From dmesg:

  [13442.816905] lvextend[6576]: segfault at 0 ip 004564eb sp
  7fff6dbc1a60 error 4 in lvm[40+8e000]

  From console:
  root@laptop:/mnt# lvs
LV   VG   Attr   LSize  Origin Snap%  Move Log Copy%  Convert
home raid -wi-ao 20.00G  
virt raid -wi-ao 20.00G  

  root@laptop:/mnt# pvs
PV VG   Fmt  Attr PSize  PFree 
/dev/md1   raid lvm2 a-   82.02G 42.02G

  root@laptop:/mnt# lvextend -L +20G /dev/raid/home 
Extending logical volume home to 40.00 GB
Logical volume home successfully resized

  root@laptop:/mnt# lvextend -L +20G /dev/raid/virt 
Extending logical volume virt to 40.00 GB
Logical volume virt successfully resized

  root@laptop:/mnt# pvs
PV VG   Fmt  Attr PSize  PFree
/dev/md1   raid lvm2 a-   82.02G 2.02G

  root@laptop:/mnt# lvs
LV   VG   Attr   LSize  Origin Snap%  Move Log Copy%  Convert
home raid -wi-ao 40.00G  
virt raid -wi-ao 40.00G

  root@laptop:/mnt# pvs
PV VG   Fmt  Attr PSize  PFree
/dev/md1   raid lvm2 a-   82.02G 2.02G

  root@laptop:/mnt# lvextend -l +100%PVS /dev/raid/home 
  Segmentation fault

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

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

[Touch-packages] [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

2014-09-06 Thread Mr. Jester 
Just to document additional support.  I concur that on a Server install,
PE should disabled by default.  A server doesn't fall into the use case
of needing to protect the privacy of the user.  It is meant to be known,
not obfuscated.

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

Title:
  IPv6 Privacy Extensions enabled on Ubuntu Server by default

Status in “cloud-init” package in Ubuntu:
  Triaged
Status in “procps” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04 LTS and Ubuntu 12.10 server images both ship with the
  IPv6 Privacy Extensions enabled (as defined in RFC 4941[0]). Not only
  are they enabled, but these addresses are preferred over addresses
  obtained using SLAAC. While is may be considered a reasonable default
  on an image being used on a personal computer, it's not something that
  is sane to have enabled by default in a server environment. Having
  this extension enabled can wreak havoc if you are expecting a specific
  IPv6 address when you know the MAC addresses of your systems
  beforehand.

  The file that is responsible for causing this to be defaulted to
  enabled is: /etc/sysctl.d/10-ipv6-privacy.conf. This file appears to
  be part of the procps package (as per the output of 'dpkg -S') and
  contains the following:

  # IPv6 Privacy Extensions (RFC 4941)
  # ---
  # IPv6 typically uses a device's MAC address when choosing an IPv6 address
  # to use in autoconfiguration. Privacy extensions allow using a randomly
  # generated IPv6 address, which increases privacy.
  #
  # Acceptable values:
  #0 - don’t use privacy extensions.
  #1 - generate privacy addresses
  #2 - prefer privacy addresses and use them over the normal addresses.
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2

  In short, IPv6 privacy extensions should not be enabled by default
  when deploying an Ubuntu server image. In a server environment you
  should be able to reliably determine your IPv6 address based on the
  MAC address of the system.

  Thank you for taking the time to look in to this as well as consider
  changing the default behavior of Ubuntu server.

  -Tim Heckman

  [0] http://tools.ietf.org/html/rfc4941

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

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

[Touch-packages] [Bug 1271839] Re: ibus-ui-gtk3 big memory leak

2014-09-06 Thread Stephanus Teggy 
Saw 1.8GB mem usage on 14.04 desktop 64 bit - this might help
http://askubuntu.com/a/490326

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

Title:
  ibus-ui-gtk3 big memory leak

Status in “ibus” package in Ubuntu:
  Expired

Bug description:
  ubuntu 13.10 64bit
  2gb of memory leak

  Also seen on Ubuntu 14.04 64Bit

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

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

[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10

2014-09-06 Thread Anton Blanchard 
(gdb) break /home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c:28
Breakpoint 1 at 0x16e4: file 
/home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c, line 28.

(gdb) run
Starting program: /tmp/foo 
Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated

Breakpoint 1, main () at 
/home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c:28
28int my_array[3] = { 1, 2, 3 };  /* break main */


I wonder if the gdb complaint about the kernel VDSO is causing the test to 
fail. The warning is almost certainly a result of
this kernel patch:


commit 24b659a13866b935eca72748ce725279bd3c4466
Author: Anton Blanchard an...@au1.ibm.com
Date:   Wed Feb 12 17:18:50 2014 +1100

powerpc: Use unstripped VDSO image for more accurate profiling data

We are seeing a lot of hits in the VDSO that are not resolved by perf.
A while(1) gettimeofday() loop shows the issue:

27.64%  [vdso]  [.] 0x060c
22.57%  [vdso]  [.] 0x0628
16.88%  [vdso]  [.] 0x0610
12.39%  [vdso]  [.] __kernel_gettimeofday
 6.09%  [vdso]  [.] 0x05f8
 3.58%  test[.] 0037.plt_call.gettimeofday@@GLIBC_2.18
 2.94%  [vdso]  [.] __kernel_datapage_offset
 2.90%  test[.] main

We are using a stripped VDSO image which means only symbols with
relocation info can be resolved. There isn't a lot of point to
stripping the VDSO, the debug info is only about 1kB:

4680 arch/powerpc/kernel/vdso64/vdso64.so
5815 arch/powerpc/kernel/vdso64/vdso64.so.dbg

By using the unstripped image, we can resolve all the symbols in the
VDSO and the perf profile data looks much better:

76.53%  [vdso]  [.] __do_get_tspec
12.20%  [vdso]  [.] __kernel_gettimeofday
 5.05%  [vdso]  [.] __get_datapage
 3.20%  test[.] main
 2.92%  test[.] 0037.plt_call.gettimeofday@@GLIBC_2.18

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

Title:
  gdb source test suites are failing in Ubuntu14.10

Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  gdb source test suites are failing in Ubuntu14.10
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
  Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
  Then try to build and execute the gdb source test suites as below.

  root@ubuntu:~# apt-get source gdb
  root@ubuntu:~# cd gdb-7.8/
  root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 21 | tee gdblog

  === gdb Summary ===

  # of expected passes25009
  # of unexpected failures287
  # of unexpected successes   2
  # of expected failures  66
  # of unknown successes  1
  # of known failures 59
  # of unresolved testcases   3
  # of untested testcases 19
  # of unsupported tests  100

   
  ---uname output---
  Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 
VM provided by Pavaman and the number of failures curiously increased to 250 
(in comparison to less than 140 on 14.04), which leads me to believe that there 
is something in the environment of Ubuntu 14.10 compromising gdb functionality 
in several testcases.

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

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

[Touch-packages] [Bug 1366419] Re: [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal soundcard to off

2014-09-06 Thread Raymond 
seem no capture controls

pulseaudio don't support 4 channels volume control

http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa
/alsa-mixer.c?id=527078523815587bfd021bc1d10782403e9b3e84

Card hw:1 'USB'/'E-MU Systems, Inc. E-MU 0404 | USB at usb-:00:1d.7-2, high 
speed'
  Mixer name: 'USB Mixer'
  Components: 'USB041e:3f04'
  Controls  : 9
  Simple ctrls  : 5
Simple mixer control 'PCM',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right - Rear Left - Rear Right
  Limits: Playback 0 - 200
  Mono:
  Front Left: Playback 160 [80%] [-20.00dB] [on]
  Front Right: Playback 160 [80%] [-20.00dB] [on]
  Rear Left: Playback 160 [80%] [-20.00dB] [on]
  Rear Right: Playback 160 [80%] [-20.00dB] [on]


Default sink name: 
alsa_output.usb-E-MU_Systems__Inc._E-MU_0404___USB_E-MU-E5-3F04-07D90512-08FE3-STATION_01-00-USB.analog-stereo
Default source name: 
alsa_output.usb-E-MU_Systems__Inc._E-MU_0404___USB_E-MU-E5-3F04-07D90512-08FE3-STATION_01-00-USB.analog-stereo.monitor

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

Title:
  [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal
  soundcard to off

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  There seems to be no easy way to tell the application which soundcard
  to choose. Sometimes it works, sometimes it works half, but mostly it
  doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Sat Sep  6 16:38:49 2014
  InstallationDate: Installed on 2014-07-14 (54 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB failed
  Symptom_Card: E-Mu 0404 - E-MU 0404 | USB
  Symptom_Type: None of the above
  Title: [USB-Audio - E-MU 0404 | USB, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.0F
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0D
  dmi.chassis.asset.tag: CNU9501Y74
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.0F:bd10/20/2009:svnHewlett-Packard:pnHPProBook4510s:pvrF.0F:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.0F
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1286552] Re: No wifi after suspend

2014-09-06 Thread NoOp 
The problem seems to occur after kernel updates. NetworkManager needs to
be restarted ('sudo kill PIDforNetworkManager) after suspend.

uname -r
3.13.0-36-generic
apt-cache policy network-manager
network-manager:
  Installed: 0.9.8.8-0ubuntu7
  Candidate: 0.9.8.8-0ubuntu7
  Version table:
 *** 0.9.8.8-0ubuntu7 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status

*-network
   description: Wireless interface
   product: Centrino Wireless-N 1000 [Condor Peak]
   vendor: Intel Corporation

$ lsmod | grep intel
snd_intel8x0m  18830  0 
snd_ac97_codec130285  3 snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m
snd_hda_intel  56451  3 
snd_hda_codec 192906  3 
snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel
snd_pcm   102099  7 
snd_ac97_codec,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m
snd_page_alloc 18710  5 
snd_pcm,snd_hda_intel,snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m
snd69322  21 
snd_ac97_codec,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_via82xx_modem,snd_seq_device,snd_atiixp_modem,snd_intel8x0m,snd_seq_midi

I've found that killing NetworkManager (note the caps) resolves the
issue and restarts the NetworkManager applet.  I can then select a wifi
network  continue.

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

Title:
  No wifi after suspend

Status in “linux” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  After suspending ubuntu the wifi doesn't work. The solution given here
  (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
  connecting-after-suspend) worked for me but when I have updated my
  Ubuntu now it won't work. I have tried to test mainline kernel but it
  won't to boot with it.

  To reproduce the bug : just suspend the computer and then power it.
  There's no wifi network until you restart the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubuntu-release-upgrader-core 1:0.205.4
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashDB: ubuntu
  Date: Sat Mar  1 15:20:39 2014
  InstallationDate: Installed on 2013-12-30 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 
(20131017)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradi 1503 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
  InstallationDate: Installed on 2013-12-30 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 
(20131017)
  MachineType: Hewlett-Packard HP Compaq 6830s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116.2
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  WifiSyslog: Mar  1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] 
perf samples too long (5002  5000), lowering kernel.perf_event_max_sample_rate 
to 25000
  dmi.bios.date: 03/12/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZD Ver. F.0C
  dmi.board.name: 30E9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 95.1C
  dmi.chassis.asset.tag: CNU91609Y2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6830s
  dmi.product.version: F.0C
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1251054] Re: networking didn't return from suspend

2014-09-06 Thread NoOp 
$ uname -r
3.13.0-36-generic

$ apt-cache policy network-manager
network-manager:
  Installed: 0.9.8.8-0ubuntu7
  Candidate: 0.9.8.8-0ubuntu7
  Version table:
 *** 0.9.8.8-0ubuntu7 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status

*-network
   description: Wireless interface
   product: Centrino Wireless-N 1000 [Condor Peak]
   vendor: Intel Corporation

$ lsmod | grep wifi
iwlwifi   169932  1 iwldvm
cfg80211  484040  3 iwlwifi,mac80211,iwldvm

sudo killall NetworkManager
or
sudo kill PIDofNetworkManager

works for me as well.

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

Title:
  networking didn't return from suspend

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Wireless networking did not work when I resumed from suspend.

  Using the indicator/applet to Enable Networking didn't associate my
  wireless with the AP. Plugging in an Ethernet cable did not bring back
  networking. The hardware rfkill switch did not bring back networking.

  A reboot allowed me to associate as I expected.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2966 F pulseaudio
  Date: Wed Nov 13 15:03:20 2013
  HibernationDevice: RESUME=UUID=81b2976f-2830-4449-9dae-e1d44a43fa78
  InstallationDate: Installed on 2012-10-18 (391 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MachineType: LENOVO 2359CTO
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-11-06 (7 days ago)
  dmi.bios.date: 09/13/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ET62WW (2.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2359CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ET62WW(2.04):bd09/13/2012:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2359CTO
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1366277] Re: After restarting incorrect time is displayed

2014-09-06 Thread Jeffrey Flaker 
Please confirm that your BIOS battery is not the problem.  This is a
typical BIOS battery issue after power off or sometimes after reboot,
the system's time may be incorrect.

The EASIEST way, is to replace the CMOS battery, which is just about
$2USD.  If the clock problem is no longer an issue, it was not a problem
with the software.

To test your system to confirm a CMOS battery problem
Go into BIOS and set the time (not through the operating systems).  Save your 
BIOS settings and reboot.  Allow the OS to load, then do a clean shut down.  
Remove power for a few minutes, then re-apply power and go into BIOS 
again..If the time is not correct, it is likely a battery issue.

Please get bak to us so we can follow up

** Changed in: indicator-datetime (Ubuntu)
   Status: New = Incomplete

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

Title:
  After restarting incorrect time is displayed

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  Every time i shutdown my system and later i start i found that
  incorrect time is being displayed. so i need to change it manually.
  again when i shutdown and start my system same problem happens.

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

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

[Touch-packages] [Bug 1317391] Re: ginn error subscribing to gestures

2014-09-06 Thread hackel 
*** This bug is a duplicate of bug 985121 ***
https://bugs.launchpad.net/bugs/985121

** This bug has been marked a duplicate of bug 985121
   Ginn doesn't subscribe to gestures

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

Title:
  ginn error subscribing to gestures

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  ginn doesn't work. To solve the problem, see
  http://askubuntu.com/questions/57586/how-can-i-disable-arbitrary-
  default-multitouch-gestures-in-unity/90383#90383Answer #9

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu May  8 09:55:24 2014
  InstallationDate: Installed on 2013-10-15 (204 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (20 days ago)

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

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

[Touch-packages] [Bug 1223181]

2014-09-06 Thread Ansgar-radermacher 
(In reply to Daniel Armbrust from comment #31)
 In case people aren't aware, the workaround for this bug is to go to System
 Settings - Appliation Appearance - GTK
 
 And then change the GTK2 theme from 'oxygen-gtk' to something else.
 
 I've been using Clearlooks myself, and it completely eliminates the bug.

Changing the theme also resolved the problem for me. It seems that oxygen is 
severly broken. The bug has been posted in the KDE bugzilla:
https://bugs.kde.org/show_bug.cgi?id=338012

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

Title:
  After upgrading to saucy, eclipse crashes in
  gtk_tree_view_get_background_area+0x8a while debugging

Status in Eclipse:
  Confirmed
Status in GTK+ GUI Toolkit:
  Unknown
Status in “gtk+2.0” package in Ubuntu:
  Confirmed

Bug description:
  to reproduce, I open the Variables view in eclipse and step through
  the application. the eclipse jvm crashes with:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912
  #
  # JRE version: 7.0_21-b11
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode 
linux-amd64 compressed oops)
  # Problematic frame:
  # C  [libgtk-x11-2.0.so.0+0x2202aa]  gtk_tree_view_get_background_area+0x8a
  #
  # Core dump written. Default location: /home/juergen/core or core.11567
  #
  # An error report file with more information is saved as:
  # /home/juergen/hs_err_pid11567.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  This did not happen in ubuntu 13.04.

  using KDE as a desktop (installed ubuntu, installed kde packages)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Tue Sep 10 07:25:17 2013
  InstallationDate: Installed on 2010-11-24 (1020 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago)

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

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

[Touch-packages] [Bug 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging

2014-09-06 Thread Bug Watch Updater 
** Bug watch added: KDE Bug Tracking System #338012
   https://bugs.kde.org/show_bug.cgi?id=338012

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

Title:
  After upgrading to saucy, eclipse crashes in
  gtk_tree_view_get_background_area+0x8a while debugging

Status in Eclipse:
  Confirmed
Status in GTK+ GUI Toolkit:
  Unknown
Status in “gtk+2.0” package in Ubuntu:
  Confirmed

Bug description:
  to reproduce, I open the Variables view in eclipse and step through
  the application. the eclipse jvm crashes with:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912
  #
  # JRE version: 7.0_21-b11
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode 
linux-amd64 compressed oops)
  # Problematic frame:
  # C  [libgtk-x11-2.0.so.0+0x2202aa]  gtk_tree_view_get_background_area+0x8a
  #
  # Core dump written. Default location: /home/juergen/core or core.11567
  #
  # An error report file with more information is saved as:
  # /home/juergen/hs_err_pid11567.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  This did not happen in ubuntu 13.04.

  using KDE as a desktop (installed ubuntu, installed kde packages)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Tue Sep 10 07:25:17 2013
  InstallationDate: Installed on 2010-11-24 (1020 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago)

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

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

[Touch-packages] [Bug 1356743] Re: package libcap2 1:2.22-1ubuntu3 failed to install/upgrade: ErrorMessage: package libcap2 is already installed and configured

2014-09-06 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libcap2 (Ubuntu)
   Status: New = Confirmed

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

Title:
  package libcap2 1:2.22-1ubuntu3 failed to install/upgrade:
  ErrorMessage: package libcap2 is already installed and configured

Status in “libcap2” package in Ubuntu:
  Confirmed

Bug description:
  bug happened while upgrading from 12.04 to 14.04. I was told libcap2 'ne sera 
pas fonctionnel' because it was already installed and configured.
  In the end when starting the computer again it went back to the 12.04 version.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libcap2
  ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51
  Uname: Linux 3.2.0-56-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Wed Aug 13 20:32:54 2014
  ErrorMessage: ErrorMessage: package libcap2 is already installed and 
configured
  MarkForUpload: True
  SourcePackage: libcap2
  Title: package libcap2 1:2.22-1ubuntu3 failed to install/upgrade: 
ErrorMessage: package libcap2 is already installed and configured
  UpgradeStatus: Upgraded to precise on 2014-08-14 (0 days ago)

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

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

[Touch-packages] [Bug 1319490] Re: after install Nvidia-173 driver for trusty black sreen

2014-09-06 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  after install Nvidia-173 driver for trusty black sreen

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  after install Nvidia-173 driver for trusty black sreen

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 14 19:18:28 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:01b9]
  InstallationDate: Installed on 2014-05-12 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: Dell Computer Corporation Dimension 8300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=e5a5dd2c-a210-4eae-8011-361d62ca076b ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A02
  dmi.board.name: 0M2035
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA02:bd07/21/2003:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0M2035:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 8300
  dmi.sys.vendor: Dell Computer Corporation
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  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 N/A
  xserver.bootTime: Wed May 14 18:37:39 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input USB OPTICAL MOUSE   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nouveau (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nouveau (module does not exist, 0)
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: modesetting

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

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

[Touch-packages] [Bug 1366455] [NEW] Sync orc 1:0.4.22-1 (main) from Debian unstable (main)

2014-09-06 Thread Jackson Doak 
Public bug reported:

Please sync orc 1:0.4.22-1 (main) from Debian unstable (main)

Changelog entries since current utopic version 1:0.4.21-1:

orc (1:0.4.22-1) unstable; urgency=medium

  * New upstream bugfix release.

 -- Sebastian Dröge sl...@debian.org  Wed, 27 Aug 2014 12:37:05 +0300

** Affects: orc (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: orc (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  Sync orc 1:0.4.22-1 (main) from Debian unstable (main)

Status in “orc” package in Ubuntu:
  New

Bug description:
  Please sync orc 1:0.4.22-1 (main) from Debian unstable (main)

  Changelog entries since current utopic version 1:0.4.21-1:

  orc (1:0.4.22-1) unstable; urgency=medium

* New upstream bugfix release.

   -- Sebastian Dröge sl...@debian.org  Wed, 27 Aug 2014 12:37:05
  +0300

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

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

[Touch-packages] [Bug 1366459] [NEW] Sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable (main)

2014-09-06 Thread Jackson Doak 
Public bug reported:

Please sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable
(main)

Changelog entries since current utopic version 1.4.0-1:

gst-plugins-base1.0 (1.4.1-1) unstable; urgency=medium

  * New upstream bugfix release.

 -- Sebastian Dröge sl...@debian.org  Wed, 27 Aug 2014 14:32:29 +0300

** Affects: gst-plugins-base1.0 (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: gst-plugins-base1.0 (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  Sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable (main)

Status in “gst-plugins-base1.0” package in Ubuntu:
  New

Bug description:
  Please sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable
  (main)

  Changelog entries since current utopic version 1.4.0-1:

  gst-plugins-base1.0 (1.4.1-1) unstable; urgency=medium

* New upstream bugfix release.

   -- Sebastian Dröge sl...@debian.org  Wed, 27 Aug 2014 14:32:29
  +0300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1366459/+subscriptions

-- 
Mailing list: https://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   >