[Touch-packages] [Bug 1374222] Re: path for policy files changed

[Seth Arnold]

Looks like we may need to adjust apparmor policy lines too. I wonder
what motivated the path change.

** Information type changed from Private Security to Public Security

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

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

Title:
  path for policy files changed

Status in “apparmor” package in Ubuntu:
  New
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909
  and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917

  The path checked by Ubuntu's chromium-browser package for policy files
  has changed.  This results in administrator mandated settings not
  being applied, which should be considered a security vulnerability.

  In previous versions of the package, policy files were read from: 
/etc/chromium-browser/policies
  In the new version of the package, it is reading policy files from: 
/etc/chromium/policies

  The new package version has dropped the following line from its debian/rules 
file:
  sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \
  $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc

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

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

[Touch-packages] [Bug 1374222] Re: path for policy files changed

[Jamin W. Collins]

It's not called out specifically in the change log.  The existing
entries in the change log are very concerning for the 12.04 LTS update:

chromium-browser (37.0.2062.120-0ubuntu0.12.04.1~pkg917) precise-
security; urgency=medium

  * Release to stage

chromium-browser (37.0.2062.120-0ubuntu1) UNRELEASED; urgency=low

  * Upstream release 37.0.2062.120:
- CVE-2014-3178: Use-after-free in rendering. Credit to miaubiz.
- CVE-2014-3179: Various fixes from internal audits, fuzzing and other
  initiatives.
  * debian/rules: Simplify and rearrange.
  * debian/rules, debian/known_gyp_flags: Keep better track of known GYP flags,
so we can fail when something changes unexpectedly.
  * debian/rules: Fix up patch-translations rule.

Why are changes being made to debian/rules to Simplify and rearrange
in an LTS update?  That's just inviting problems like this.  In looking
at a side-by-side diff (via meld), it appears that the removal of this
line may have been of victim of the referenced rearranging.  I attempted
to find the packaging source repository, but the one referenced in LP
appears to be out dated and did not see a reference to the current one
(if there is a public one).

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3178

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3179

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

Title:
  path for policy files changed

Status in “apparmor” package in Ubuntu:
  New
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909
  and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917

  The path checked by Ubuntu's chromium-browser package for policy files
  has changed.  This results in administrator mandated settings not
  being applied, which should be considered a security vulnerability.

  In previous versions of the package, policy files were read from: 
/etc/chromium-browser/policies
  In the new version of the package, it is reading policy files from: 
/etc/chromium/policies

  The new package version has dropped the following line from its debian/rules 
file:
  sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \
  $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc

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

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

[Touch-packages] [Bug 1374222] Re: path for policy files changed

[Seth Arnold]

Browsers are special. We certainly don't have the resources to fix only
security issues found in the browsers as we do with most other packages.
We package what upstream produces and this is far from the first thing
they've moved: the name of the sandbox executable has changed three or
four times since I've been paying attention and I wouldn't be surprised
if they change it again in the future. Overall, the benefits of shipping
recent browsers with recent features and recent fixes works out for the
best but it doesn't fit the traditional LTS mold well.

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

Title:
  path for policy files changed

Status in “apparmor” package in Ubuntu:
  New
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909
  and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917

  The path checked by Ubuntu's chromium-browser package for policy files
  has changed.  This results in administrator mandated settings not
  being applied, which should be considered a security vulnerability.

  In previous versions of the package, policy files were read from: 
/etc/chromium-browser/policies
  In the new version of the package, it is reading policy files from: 
/etc/chromium/policies

  The new package version has dropped the following line from its debian/rules 
file:
  sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \
  $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc

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

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

[Touch-packages] [Bug 1374222] Re: path for policy files changed

[Jamin W. Collins]

Are the debian/rules changes from upstream? Near as I can tell, upstream
does not have a debian directory in its source tree:

https://chromium.googlesource.com/chromium/src.git/+/37.0.2062.120

Or are you referring to a different upstream?

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

Title:
  path for policy files changed

Status in “apparmor” package in Ubuntu:
  New
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909
  and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917

  The path checked by Ubuntu's chromium-browser package for policy files
  has changed.  This results in administrator mandated settings not
  being applied, which should be considered a security vulnerability.

  In previous versions of the package, policy files were read from: 
/etc/chromium-browser/policies
  In the new version of the package, it is reading policy files from: 
/etc/chromium/policies

  The new package version has dropped the following line from its debian/rules 
file:
  sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \
  $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc

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

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

[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[Matthew Hall]

This bug has been open two years and it's still occurring. I've noticed
it during development of an open-source network security sensor I'm
planning to publish in the next few weeks:

{ source: dns, port_id: 0, direction: 1, self: 0, length:
76, eth_type: 2048, smac: 50:e5:49:36:0a:db, dmac:
78:96:84:71:ea:c0, sip: 192.168.1.5, dip: 192.168.1.254,
ip_protocol: 17, ttl: 0, l4_length: 42, icmp_type: 255,
icmp_code: 255, sport: 37657, dport: 53, dns_name:
daisy.ubuntu.com. }

It's a little unbelievable it's been open this long with no concrete
plan taking shape.

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in “glib2.0” package in Ubuntu:
  Invalid
Status in “network-manager” package in Ubuntu:
  In Progress
Status in “whoopsie” package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

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

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

[Touch-packages] [Bug 1373781] Re: bash incomplete fix for CVE-2014-6271

[Spyros]

Thank you for the reply Marc  Simon.
Unfortunately this isn't due to a leftover file.

spyros@prod01:~# env X='() { (a)=\' bash -c echo date; cat echo
bash: X: line 1: syntax error near unexpected token `='
bash: X: line 1: `'
bash: error importing function definition for `X'
Fri Sep 26 12:14:15 PDT 2014
spyros@prod01:~# rm echo
spyros@prod01:~# env X='() { (a)=\' bash -c echo date; cat echo
bash: X: line 1: syntax error near unexpected token `='
bash: X: line 1: `'
bash: error importing function definition for `X'
Fri Sep 26 12:15:24 PDT 2014

The only difference between the working and non-working version that
I spot, is the -i argument to env, but I'm not sure why/how the empty
environment would affect this.

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

Title:
  bash incomplete fix for CVE-2014-6271

Status in “bash” package in Ubuntu:
  Fix Released
Status in “bash” source package in Lucid:
  Fix Released
Status in “bash” source package in Precise:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released
Status in “bash” source package in Utopic:
  Fix Released

Bug description:
  The fixes for CVE-2014-6271 do NOT work! Security vuln, but should be
  public, this is known already.

  Ubuntu 14.04 LTS: bash 4.3-7ubuntu1.1
  Ubuntu 12.04 LTS: bash 4.2-2ubuntu2.2
  Ubuntu 10.04 LTS: bash 4.1-2ubuntu3.1

  Testcase:
  rm -f echo  env -i  X='() { (a)=\' bash -c 'echo id'; cat echo

  expected output:
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  id

  actual output:
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  uid=0(root) gid=0(root) groups=0(root)

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

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

[Touch-packages] [Bug 1374707] [NEW] package wget 1.15-1ubuntu1 failed to install/upgrade: cannot compute MD5 hash for file '/etc/wgetrc': failed to read (Input/output error)

[Thib]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: wget 1.15-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
Date: Fri Sep 26 16:51:39 2014
DuplicateSignature: package:wget:1.15-1ubuntu1:cannot compute MD5 hash for file 
'/etc/wgetrc': failed to read (Input/output error)
ErrorMessage: cannot compute MD5 hash for file '/etc/wgetrc': failed to read 
(Input/output error)
InstallationDate: Installed on 2012-01-19 (981 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
SourcePackage: wget
Title: package wget 1.15-1ubuntu1 failed to install/upgrade: cannot compute MD5 
hash for file '/etc/wgetrc': failed to read (Input/output error)
UpgradeStatus: Upgraded to trusty on 2014-09-27 (0 days ago)
mtime.conffile..etc.wgetrc: 2011-05-17T22:17:24

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


** Tags: apport-package dist-upgrade i386 trusty

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

Title:
  package wget 1.15-1ubuntu1 failed to install/upgrade: cannot compute
  MD5 hash for file '/etc/wgetrc': failed to read (Input/output error)

Status in “wget” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: wget 1.15-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  Date: Fri Sep 26 16:51:39 2014
  DuplicateSignature: package:wget:1.15-1ubuntu1:cannot compute MD5 hash for 
file '/etc/wgetrc': failed to read (Input/output error)
  ErrorMessage: cannot compute MD5 hash for file '/etc/wgetrc': failed to read 
(Input/output error)
  InstallationDate: Installed on 2012-01-19 (981 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  SourcePackage: wget
  Title: package wget 1.15-1ubuntu1 failed to install/upgrade: cannot compute 
MD5 hash for file '/etc/wgetrc': failed to read (Input/output error)
  UpgradeStatus: Upgraded to trusty on 2014-09-27 (0 days ago)
  mtime.conffile..etc.wgetrc: 2011-05-17T22:17:24

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

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

[Touch-packages] [Bug 1374707] Re: package wget 1.15-1ubuntu1 failed to install/upgrade: cannot compute MD5 hash for file '/etc/wgetrc': failed to read (Input/output error)

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package wget 1.15-1ubuntu1 failed to install/upgrade: cannot compute
  MD5 hash for file '/etc/wgetrc': failed to read (Input/output error)

Status in “wget” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: wget 1.15-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  Date: Fri Sep 26 16:51:39 2014
  DuplicateSignature: package:wget:1.15-1ubuntu1:cannot compute MD5 hash for 
file '/etc/wgetrc': failed to read (Input/output error)
  ErrorMessage: cannot compute MD5 hash for file '/etc/wgetrc': failed to read 
(Input/output error)
  InstallationDate: Installed on 2012-01-19 (981 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  SourcePackage: wget
  Title: package wget 1.15-1ubuntu1 failed to install/upgrade: cannot compute 
MD5 hash for file '/etc/wgetrc': failed to read (Input/output error)
  UpgradeStatus: Upgraded to trusty on 2014-09-27 (0 days ago)
  mtime.conffile..etc.wgetrc: 2011-05-17T22:17:24

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

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

[Touch-packages] [Bug 1365977] [NEW] Ubuntu Store front is not translated into Norwegian

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Opening the Ubuntu Store using a Norwegian locale gives me English
labels on everything. On the second level (in an app, e.g.), most items
are translated.

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rtm-i18n
-- 
Ubuntu Store front is not translated into Norwegian
https://bugs.launchpad.net/bugs/1365977
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity-scope-click 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 1374375] Re: CVE-2014-7186: bash crashed with SIGSEGV in list_reverse()

[Marc Deslauriers]

This is now fixed:
http://www.ubuntu.com/usn/usn-2364-1/

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

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

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

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

Title:
  CVE-2014-7186: bash crashed with SIGSEGV in list_reverse()

Status in “bash” package in Ubuntu:
  Fix Committed
Status in “bash” source package in Lucid:
  Fix Released
Status in “bash” source package in Precise:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released
Status in “bash” source package in Utopic:
  Fix Committed

Bug description:
  Reproduced with

  bash -c 'true EOF EOF EOF EOF EOF EOF EOF EOF EOF
  EOF EOF EOF EOF EOF EOF EOF EOF EOF'

  http://seclists.org/oss-sec/2014/q3/712

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: bash 4.3-9ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 26 05:42:50 2014
  EcryptfsInUse: Yes
  ExecutablePath: /bin/bash
  InstallationDate: Installed on 2014-08-22 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140730)
  ProcCmdline: bash -c true\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ 
EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF
  SegvAnalysis:
   Segfault happened at: 0x46cfc3 list_reverse+19:mov(%rax),%rdx
   PC (0x0046cfc3) ok
   source (%rax) (0x3c3c20464f453c3c) not located in a known VMA region 
(needed readable region)!
   destination %rdx ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bash
  StacktraceTop:
   list_reverse ()
   clean_simple_command ()
   yyparse ()
   parse_command ()
   parse_and_execute ()
  Title: bash crashed with SIGSEGV in list_reverse()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  modified.conffile..etc.bash.bashrc: [modified]
  mtime.conffile..etc.bash.bashrc: 2014-03-27T19:05:55

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

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

[Touch-packages] [Bug 1365977] Re: Ubuntu Store front is not translated into Norwegian

[Sebastien Bacher]

** Project changed: ubuntu-translations = unity-scope-click (Ubuntu)

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

Title:
  Ubuntu Store front is not translated into Norwegian

Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  Opening the Ubuntu Store using a Norwegian locale gives me English
  labels on everything. On the second level (in an app, e.g.), most
  items are translated.

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

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

[Touch-packages] [Bug 1350506] Re: No phone numbers message needs to be marked for translation

[Sebastien Bacher]

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

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

Title:
  No phone numbers message needs to be marked for translation

Status in Address Book App:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in “address-book-app” package in Ubuntu:
  Fix Released

Bug description:
  The No phone numbers message that appears when a contact has no
  numbers set needs to be marked for translation

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

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

[Touch-packages] [Bug 1374714] Re: After my Ubuntu is started my USB mouse sometime doesn't work

[Werner Gerritsen]

** Attachment added: the Xorg.0.log
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1374714/+attachment/4217000/+files/Xorg.0.log

** Description changed:

- 
  Hi
  
  After my Ubuntu is started (already on the logging screen) my USB mouse
- sometime doesn't work at alla and sometime it does work just as normal.
+ sometime doesn't work at all and sometime it does work just as normal.
  
- In the case it doesn't work: 
+ In the case it doesn't work:
  - plug-out and plug-in the USB mouse doesn't help. I see that the lights from 
the mouse is short time turned on but after that the lights switches off. I 
seems for me as if the USB channel is not reacting correcly...
  - also other USB devices doesn't work
  
- In the case it does work: 
+ In the case it does work:
  - complet normal functionality, never expirienced that when it work it stop 
to working during ubuntu is running.
  - other USB devices working as expected.
  
  My USB mouse is a ASUS Product
  M/N MOBKUL
  ASUS P/N 0K100-00020
  PEGA P/N 0411-000J0AS
  S/N AUT1332001745
  Branded with EPUBLIC OF GAMERS (R.O.G.)
  
  I don't believe that the mechanism of the mouse is from interesting for
  this bug report.
  
  I have Ubuntu 14.04.1 LTS
  
  Best Regards
  Werner
  
- 
- btw I have created this bug report with the xdiagnose - Report an Xorg Bug 
and at the end the following error message  GLib-CRITICAL **: 
g_slice_set_config: assertion 'sys_page_size == 0' failed is in the terminal 
window where I have start it.
+ btw I have created this bug report with the xdiagnose - Report an Xorg
+ Bug and at the end the following error message  GLib-CRITICAL **:
+ g_slice_set_config: assertion 'sys_page_size == 0' failed is in the
+ terminal window where I have start it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
-  GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
+  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)
  .proc.driver.nvidia.warnings.fbdev:
-  Your system is not currently configured to drive a VGA console
-  on the primary VGA device. The NVIDIA Linux graphics driver
-  requires the use of a text-mode VGA console. Use of other console
-  drivers including, but not limited to, vesafb, may result in
-  corruption and stability problems, and is not supported.
+  Your system is not currently configured to drive a VGA console
+  on the primary VGA device. The NVIDIA Linux graphics driver
+  requires the use of a text-mode VGA console. Use of other console
+  drivers including, but not limited to, vesafb, may result in
+  corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 27 11:30:34 2014
  DistUpgraded: 2014-05-22 21:29:07,402 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:213e]
+  NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:213e]
  InstallationDate: Installed on 2014-01-12 (257 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. G750JX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=38e51521-23e2-4a85-8aad-b63484675685 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-22 (127 days ago)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G750JX.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G750JX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer

[Michael Blennerhassett]

This isn't fixed for me on utopic, can anyone else confirm?

What does fix this for me is the patch I wrote for evolution-data-server
over at LP: #1373908

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins 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:
  Fix Released
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
Status in “account-plugins” source package in Trusty:
  Fix Released
Status in “evolution-data-server” source package in Trusty:
  Fix Committed
Status in “signon-plugin-oauth2” source package in Trusty:
  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 1374714] [NEW] After my Ubuntu is started my USB mouse sometime doesn't work

[Werner Gerritsen]

Public bug reported:

Hi

After my Ubuntu is started (already on the logging screen) my USB mouse
sometime doesn't work at all and sometime it does work just as normal.

In the case it doesn't work:
- plug-out and plug-in the USB mouse doesn't help. I see that the lights from 
the mouse is short time turned on but after that the lights switches off. I 
seems for me as if the USB channel is not reacting correcly...
- also other USB devices doesn't work

In the case it does work:
- complet normal functionality, never expirienced that when it work it stop to 
working during ubuntu is running.
- other USB devices working as expected.

My USB mouse is a ASUS Product
M/N MOBKUL
ASUS P/N 0K100-00020
PEGA P/N 0411-000J0AS
S/N AUT1332001745
Branded with EPUBLIC OF GAMERS (R.O.G.)

I don't believe that the mechanism of the mouse is from interesting for
this bug report.

I have Ubuntu 14.04.1 LTS

Best Regards
Werner

btw I have created this bug report with the xdiagnose - Report an Xorg
Bug and at the end the following error message  GLib-CRITICAL **:
g_slice_set_config: assertion 'sys_page_size == 0' failed is in the
terminal window where I have start it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Sep 27 11:30:34 2014
DistUpgraded: 2014-05-22 21:29:07,402 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:213e]
InstallationDate: Installed on 2014-01-12 (257 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. G750JX
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=38e51521-23e2-4a85-8aad-b63484675685 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-05-22 (127 days ago)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G750JX.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G750JX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG750JX.208:bd08/19/2013:svnASUSTeKCOMPUTERINC.:pnG750JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G750JX
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Sep 27 09:17:30 2014
xserver.configfile: default
xserver.errors:
 Failed to load module nouveau (module does not exist, 0)
 Failed to load module nouveau (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.15.1-0ubuntu2.1

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


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

** Attachment added: output of dmesg
   

[Touch-packages] [Bug 1374716] [NEW] Feature request: Allow restricting apt-cache search to search installed packages only

[Jarno Suni]

Public bug reported:

Currently, apt-cache has option --installed, but it works only with
depends and rdepends, not with search.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.4.1
ProcVersionSignature: Ubuntu 3.13.0-36.63-lowlatency 3.13.11.6
Uname: Linux 3.13.0-36-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Sep 27 12:43:14 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (6 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Feature request: Allow restricting apt-cache search to search
  installed packages only

Status in “apt” package in Ubuntu:
  New

Bug description:
  Currently, apt-cache has option --installed, but it works only with
  depends and rdepends, not with search.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.4.1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-lowlatency 3.13.11.6
  Uname: Linux 3.13.0-36-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 27 12:43:14 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (6 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 204536] Re: sound volume always resets to 100% after reboot

[soul_departed]

Facing the same problem. I'm using an USB sound card from Siberia.

mukit@lifebook:~$ cat /proc/asound/cards 
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xf160 irq 45
 1 [Device ]: USB-Audio - USB PnP Sound Device
  C-Media Electronics Inc. USB PnP Sound Device at 
usb-:00:1d.0-1.1, full spe
mukit@lifebook:~$ uname -a
Linux lifebook 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  sound volume always resets to 100% after reboot

Status in One Hundred Papercuts:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Fix Released

Bug description:
  Every time I reboot I get the sound volume back to 100%, but the sound
  works fine apart from this. It's just *very* annoying to have to reset
  the volume every time I boot the PC. I set the volume from the volume
  icon in the system tray. I have two sound cards installed on my system
  (one on the motherboard and a SB Audigy), but I'm using only the
  Audigy. Another thing is that the mixer applet often incorrectly shows
  volume as muted when it's not.

  I'm using the hardy beta (hardy-desktop-amd64) from march 19th 2008.

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

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

[Touch-packages] [Bug 1374721] [NEW] ibus-daemon uses 100% CPU when using gnome-calculator

[Michael Blennerhassett]

Public bug reported:

Steps to reproduce:

1. Open gnome-calculator
2. Enter 3*7
3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ibus 1.5.8-2ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep 27 20:32:05 2014
InstallationDate: Installed on 2014-09-03 (24 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  ibus-daemon uses 100% CPU when using gnome-calculator

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Open gnome-calculator
  2. Enter 3*7
  3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 27 20:32:05 2014
  InstallationDate: Installed on 2014-09-03 (24 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1374733] [NEW] System Settings disappearing along with sudo apt-get remove pulseaudio

[TEN]

Public bug reported:

Removing pulseaudio wipes out most entries from System Settings (as well
as its sidebar icon) on Ubuntu 14.04 LTS.

The following lets me suspect pulseaudio's dependencies are too broad,
giving rise to an overzealous removal:

grep remove /var/log/dpkg.log2014-09-27 12:18:58 startup packages remove
2014-09-27 12:18:58 remove xul-ext-webaccounts:amd64 0.5-0ubuntu2 none
2014-09-27 12:18:59 remove webaccounts-extension-common:amd64 0.5-0ubuntu2 
none
2014-09-27 12:19:00 remove unity-control-center-signon:amd64 
0.1.7~+14.04.20140211.2-0ubuntu4 none
2014-09-27 12:19:01 remove ubuntu-desktop:amd64 1.325 none
2014-09-27 12:19:02 remove libcanberra-pulse:amd64 0.30-0ubuntu3 none
2014-09-27 12:19:02 remove pulseaudio-module-x11:amd64 1:4.0-0ubuntu11 none
2014-09-27 12:19:03 remove pulseaudio-module-bluetooth:amd64 1:4.0-0ubuntu11 
none
2014-09-27 12:19:05 remove unity-control-center:amd64 
14.04.3+14.04.20140604-0ubuntu1 none
2014-09-27 12:19:06 remove indicator-sound:amd64 
12.10.2+14.04.20140401-0ubuntu1 none
2014-09-27 12:19:06 remove pulseaudio:amd64 1:4.0-0ubuntu11 none

Users most likely will neither be aware of that log nor able to
reinstall the required packages (and icons) for recovery.

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

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

Title:
  System Settings disappearing along with sudo apt-get remove pulseaudio

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  Removing pulseaudio wipes out most entries from System Settings (as
  well as its sidebar icon) on Ubuntu 14.04 LTS.

  The following lets me suspect pulseaudio's dependencies are too broad,
  giving rise to an overzealous removal:

  grep remove /var/log/dpkg.log2014-09-27 12:18:58 startup packages remove
  2014-09-27 12:18:58 remove xul-ext-webaccounts:amd64 0.5-0ubuntu2 none
  2014-09-27 12:18:59 remove webaccounts-extension-common:amd64 0.5-0ubuntu2 
none
  2014-09-27 12:19:00 remove unity-control-center-signon:amd64 
0.1.7~+14.04.20140211.2-0ubuntu4 none
  2014-09-27 12:19:01 remove ubuntu-desktop:amd64 1.325 none
  2014-09-27 12:19:02 remove libcanberra-pulse:amd64 0.30-0ubuntu3 none
  2014-09-27 12:19:02 remove pulseaudio-module-x11:amd64 1:4.0-0ubuntu11 none
  2014-09-27 12:19:03 remove pulseaudio-module-bluetooth:amd64 1:4.0-0ubuntu11 
none
  2014-09-27 12:19:05 remove unity-control-center:amd64 
14.04.3+14.04.20140604-0ubuntu1 none
  2014-09-27 12:19:06 remove indicator-sound:amd64 
12.10.2+14.04.20140401-0ubuntu1 none
  2014-09-27 12:19:06 remove pulseaudio:amd64 1:4.0-0ubuntu11 none

  Users most likely will neither be aware of that log nor able to
  reinstall the required packages (and icons) for recovery.

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

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

[Touch-packages] [Bug 1330239] Re: Activated service 'org.freedesktop.ModemManager1' failed: Cannot launch daemon, file not found or permissions invalid showed in syslog in Ubuntu 14.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Activated service 'org.freedesktop.ModemManager1' failed: Cannot
  launch daemon, file not found or permissions invalid showed in syslog
  in Ubuntu 14.04

Status in “modemmanager” package in Ubuntu:
  Confirmed

Bug description:
  as bug summary
  `
  dbus[pid]: [system] Activating service name='org.freedesktop.ModemManager1' 
(using servicehelper)
  dbus[pid]: [system] Activated service 'org.freedesktop.ModemManager1' failed: 
Cannot launch daemon, file not found or permissions invalid
  `
  appears every 2 minutes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: modemmanager 1.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-lowlatency 3.13.11.2
  Uname: Linux 3.13.0-29-lowlatency i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Mon Jun 16 01:50:38 2014
  InstallationDate: Installed on 2013-03-08 (463 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (57 days ago)
  upstart.modemmanager.override: manual

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

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

[Touch-packages] [Bug 1374650] Re: cannot make dbus connections inside a shell started via adb shell

[Oliver Grawert]

seemingly a bug in adbd, it does not process the shell invoked by adb
shell as login shell (and thus does not parse /etc/profile)

** Also affects: android-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: android-tools (Ubuntu)
   Importance: Undecided = Critical

** Changed in: android-tools (Ubuntu)
 Assignee: (unassigned) = Oliver Grawert (ogra)

** Changed in: android-tools (Ubuntu)
   Status: New = Confirmed

** Changed in: ubuntu-touch-session (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  cannot make dbus connections inside a shell started via adb shell

Status in “android-tools” package in Ubuntu:
  Confirmed
Status in “ubuntu-touch-session” package in Ubuntu:
  Invalid

Bug description:
  For example launching media-player inside such a shell:

  /usr/bin/mediaplayer-app
  file:///home/phablet/Videos/BigBuckBunny_320x180.mp4 --fullscreen
  --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop

  Results in: http://pastebin.ubuntu.com/8436397/

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

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

[Touch-packages] [Bug 1247396] Re: Laptop built-in keyboard is not working after ubuntu 13.10 upgrade and using kernel 3.11.0-12-generic

[Michael Dunetas]

That worked for me to.

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

Title:
  Laptop built-in keyboard is not working after ubuntu 13.10 upgrade and
  using kernel 3.11.0-12-generic

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  I have an LG S1 Express Dual laptop and after upgrading to ubuntu
  13.10 my keyboard stopped working when the default kernel is used
  (3.11.0-12-generic). Even the ESC key does not work during the boot
  phase to see the booting messages. Basically I can't do anything, I
  get stuck in the login screen. If I choose the old kernel
  3.8.0-31-generic, it works without any problem.

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

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

[Touch-packages] [Bug 1374750] [NEW] Cannot create chroot in 14.04

[Alberto Mardegan]

Public bug reported:

In Trusty, on an amd64 system, running sudo click chroot -a amd64 -f
ubuntu-sdk-14.04 create terminates with:

Reading state information... Done
Note, selecting 'libc6-dev' instead of 'libc-dev'
E: Unable to locate package g++-x86_64-linux-gnu
E: Couldn't find any package by regex 'g++-x86_64-linux-gnu'
E: Unable to locate package pkg-config-x86_64-linux-gnu
Command returned 100: schroot -u root -c source:click-ubuntu-sdk-14.04-amd64 -- 
/finish.sh

I'm adding the full logs as an attachment.

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

** Attachment added: Full log
   https://bugs.launchpad.net/bugs/1374750/+attachment/4217162/+files/click.log

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

Title:
  Cannot create chroot in 14.04

Status in “click” package in Ubuntu:
  New

Bug description:
  In Trusty, on an amd64 system, running sudo click chroot -a amd64 -f
  ubuntu-sdk-14.04 create terminates with:

  Reading state information... Done
  Note, selecting 'libc6-dev' instead of 'libc-dev'
  E: Unable to locate package g++-x86_64-linux-gnu
  E: Couldn't find any package by regex 'g++-x86_64-linux-gnu'
  E: Unable to locate package pkg-config-x86_64-linux-gnu
  Command returned 100: schroot -u root -c source:click-ubuntu-sdk-14.04-amd64 
-- /finish.sh

  I'm adding the full logs as an attachment.

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

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

[Touch-packages] [Bug 1357371] Re: denial for RequestName and bind on org.freedesktop.Application

[Jamie Strandboge]

Based on that, I think I will simply deny this since this is not the
method apps should be communicating with each other under confinement.

** Summary changed:

- qtwebkit-based webapps denial for RequestName and bind on 
org.freedesktop.Application
+ denial for RequestName and bind on org.freedesktop.Application

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

Title:
  denial for RequestName and bind on org.freedesktop.Application

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

Bug description:
  This is bug #1342129, but for qtwebkit. This bug doesn't appear to
  affect the general functionality of the webapp.

  Test case:
  1. install r193 (or later) in the emulator
  2. install Pixel Runner from the store
  3. Open Pixel Runner

  The app starts (but with a blank screen, see bug #1357375) and the following 
apparmor denial can be observed:
  Aug 15 13:17:04 ubuntu-phablet dbus[1575]: apparmor=DENIED 
operation=dbus_method_call  bus=session path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=RequestName mask=send 
name=org.freedesktop.DBus pid=3292 
profile=com.ubuntu.developer.ogra.pixel-runner_pixel-runner_0.1 
peer_profile=unconfined

  As it happens, we can add a rule for this that is safe:
  dbus (send)
   bus=session
   interface=org.freedesktop.DBus
   path=/org/freedesktop/DBus
   member=RequestName,

  However, after adding the above rule to /var/lib/apparmor/profiles/*pixel*, 
running 'sudo apparmor_parser -r /var/lib/apparmor/profiles/*pixel*', and 
starting the app, we get a new denial:
  Aug 15 13:18:47 ubuntu-phablet dbus[1575]: apparmor=DENIED 
operation=dbus_bind  bus=session name=org.freedesktop.Application 
mask=bind pid=3774 
profile=com.ubuntu.developer.ogra.pixel-runner_pixel-runner_0.1

  If add add the following rule (which is not safe), there are no more denials:
  dbus (bind)
   bus=session
   name=org.freedesktop.Application,

  This denial is the same as in bug #1342129 and we can't safely add
  policy for it (see other bug for reasons why).

  Not sure if this is in webbrowser-app or qtwebkit, please reassign as
  necessary.

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

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

[Touch-packages] [Bug 1374650] Re: cannot make dbus connections inside a shell started via adb shell

[Launchpad Bug Tracker]

This bug was fixed in the package android-tools -
4.2.2+git20130218-3ubuntu36

---
android-tools (4.2.2+git20130218-3ubuntu36) utopic; urgency=medium

  * fix shell environment for interactive adb shell sessions (LP: #1374650)
  * drop check for username matches password (LP: #1371048)
 -- Oliver Grawert o...@ubuntu.com   Sat, 27 Sep 2014 09:35:31 +

** Changed in: android-tools (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-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/1374650

Title:
  cannot make dbus connections inside a shell started via adb shell

Status in “android-tools” package in Ubuntu:
  Fix Released
Status in “ubuntu-touch-session” package in Ubuntu:
  Invalid

Bug description:
  For example launching media-player inside such a shell:

  /usr/bin/mediaplayer-app
  file:///home/phablet/Videos/BigBuckBunny_320x180.mp4 --fullscreen
  --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop

  Results in: http://pastebin.ubuntu.com/8436397/

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

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

[Touch-packages] [Bug 1371048] Re: phone believed to enforce undocumented password policy

[Launchpad Bug Tracker]

This bug was fixed in the package android-tools -
4.2.2+git20130218-3ubuntu36

---
android-tools (4.2.2+git20130218-3ubuntu36) utopic; urgency=medium

  * fix shell environment for interactive adb shell sessions (LP: #1374650)
  * drop check for username matches password (LP: #1371048)
 -- Oliver Grawert o...@ubuntu.com   Sat, 27 Sep 2014 09:35:31 +

** Changed in: android-tools (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  phone believed to enforce undocumented password policy

Status in “android-tools” package in Ubuntu:
  Fix Released

Bug description:
  Per conversation on IRC with ogra.

  The phone will reject passwords which match the username.

  Fine and dandy, but isn't password security the responsibilty of other
  entities and code. Rejecting just this insecure password, hard-coded,
  seems a bit odd.

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

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

[Touch-packages] [Bug 1363421] Re: Unity Doesn't Start on 14.10 System

[Cliff Carson]

I went back and put the 14.04 level modules from xserver-xorg-video-
intel back onto the Unity 14.10 system.  There was no difference, still
no Unity launcher or Ubuntu banner.

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

Title:
  Unity Doesn't Start on 14.10 System

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

Bug description:
  Been having problems getting any 14.10 build (Gnome and Unity) to boot
  on this desktop.  Submitting problem report on Unity since seems
  easist to document.  I downloaded the Ubuntu 14.10 daily build dated
  8/29/14 and went through the install process without any problem.
  After completion of the install, doing the first boot of the system,
  and the login screen my desktop background is displayed with desktop
  ICONs.   There is no Ubuntu banner at the top of the screen or any
  Unity launch bar on the left.  My only option was to ctl-alt-f1 and
  build/save a bug report which I using to report under the working
  14.04 system on this same desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sat Aug 30 08:28:02 2014
  InstallationDate: Installed on 2014-08-29 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140829)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1374375] Re: CVE-2014-7186: bash crashed with SIGSEGV in list_reverse()

[Marc Deslauriers]

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

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

Title:
  CVE-2014-7186: bash crashed with SIGSEGV in list_reverse()

Status in “bash” package in Ubuntu:
  Fix Released
Status in “bash” source package in Lucid:
  Fix Released
Status in “bash” source package in Precise:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released
Status in “bash” source package in Utopic:
  Fix Released

Bug description:
  Reproduced with

  bash -c 'true EOF EOF EOF EOF EOF EOF EOF EOF EOF
  EOF EOF EOF EOF EOF EOF EOF EOF EOF'

  http://seclists.org/oss-sec/2014/q3/712

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: bash 4.3-9ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 26 05:42:50 2014
  EcryptfsInUse: Yes
  ExecutablePath: /bin/bash
  InstallationDate: Installed on 2014-08-22 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140730)
  ProcCmdline: bash -c true\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ 
EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF\ EOF
  SegvAnalysis:
   Segfault happened at: 0x46cfc3 list_reverse+19:mov(%rax),%rdx
   PC (0x0046cfc3) ok
   source (%rax) (0x3c3c20464f453c3c) not located in a known VMA region 
(needed readable region)!
   destination %rdx ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bash
  StacktraceTop:
   list_reverse ()
   clean_simple_command ()
   yyparse ()
   parse_command ()
   parse_and_execute ()
  Title: bash crashed with SIGSEGV in list_reverse()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  modified.conffile..etc.bash.bashrc: [modified]
  mtime.conffile..etc.bash.bashrc: 2014-03-27T19:05:55

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

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

[Touch-packages] [Bug 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***

[Jim Hodapp]

** Tags added: touch-2014-10-23

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': double free or corruption (fasttop): ADDR ***

Status in “gstreamer” package in Ubuntu:
  Confirmed
Status in “mediascanner2” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.104+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56
  contains more details.

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

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

[Touch-packages] [Bug 1374778] [NEW] Can't click at every item with greeter-show-manual-login

[Michael Korn]

Public bug reported:

When using greeter-show-manual-login=true some entries of the loginscreen are 
not clickable.
A concrete example: the loginscreen items are:
- User 1
- User 2
- Login (arbitrary Username can be typed) 
- Guest Session

When User 2 is the active item I can click at every other item. When I click 
at Guest Session, Guest Session will be the active item. Now a click at 
Login is without any effect (User 1 and User 2 are still clickable).
With other computers and different users sometimes more then one item isn't 
clickable. Sometimes no other item can be selected with the mouse, I have to 
use the keyboard!

I can reproduce this problem with 4 different desktop computers and 2
different notebooks. I noticed this problem with Ubuntu 12.04, 12.10,
13.04, 13.10 and 14.04. Same problem with and without LDAP-connection.

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

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

Title:
  Can't click at every item with greeter-show-manual-login

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  When using greeter-show-manual-login=true some entries of the loginscreen are 
not clickable.
  A concrete example: the loginscreen items are:
  - User 1
  - User 2
  - Login (arbitrary Username can be typed) 
  - Guest Session

  When User 2 is the active item I can click at every other item. When I 
click at Guest Session, Guest Session will be the active item. Now a click 
at Login is without any effect (User 1 and User 2 are still clickable).
  With other computers and different users sometimes more then one item isn't 
clickable. Sometimes no other item can be selected with the mouse, I have to 
use the keyboard!

  I can reproduce this problem with 4 different desktop computers and 2
  different notebooks. I noticed this problem with Ubuntu 12.04, 12.10,
  13.04, 13.10 and 14.04. Same problem with and without LDAP-connection.

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

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

[Touch-packages] [Bug 1374002] Re: After installing nvidia binary drivers lightdm does not start after reboot

[Launchpad Bug Tracker]

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

** Changed in: lightdm (Ubuntu)
   Status: New = Confirmed

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

Title:
  After installing nvidia binary drivers lightdm does not start after
  reboot

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Could be a duplicate of bug #873495 which has not, yet, gone past
  triaged status. But it has not been updated since last year and this
  just happened to me trying 14.10 (Utopic).

  Before installing the binary drivers, the nouveau driver was in use
  and lightdm started automatically. But then would crash the whole
  system somehow related to fading in popup menues. But that is another
  problem. Since the binary drivers are installed the system only boots
  into text mode. But is more stable after manually starting lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.9-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Sep 25 17:00:53 2014
  InstallationDate: Installed on 2014-09-25 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923)
  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/1374002/+subscriptions

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

[Touch-packages] [Bug 1374782] [NEW] OpenVPN doesnt ask for pkcs12 password

[Franz]

Public bug reported:

Hi All,

today I have upgraded my Kubuntu client to Utopic, 
and now OpenVPN doesen't ask me for my pkcs12 password

I start it via init.d script as root

  root@client:~# /etc/init.d/openvpn start CLIENT1
  * Starting virtual private network daemon(s)...
  *   Starting VPN 'CLIENT1'
  Timed out

and in the processlist I found, the systemd-ask-password ask for fhe password
but there is no popup or other password ask dialog

  8523 ?Sl 0:17  \_ /usr/bin/konsole
  8526 pts/0Ss 0:00  |   \_ /bin/bash
  9142 pts/0S  0:00  |   |   \_ sudo -i
  9143 pts/0S  0:00  |   |   \_ -bash
  18807 pts/0S+ 0:00  |   |   \_ /bin/sh -e 
/etc/init.d/openvpn start CLIENT1
  18830 pts/0S+ 0:00  |   |   \_ /usr/sbin/openvpn 
--writepid /run/openvpn/CLIENT1.pid --daemon ovpn-CLIENT1 --status 
/run/openvpn/CLIENT1.statu
  18831 pts/0S+ 0:00  |   |   \_ 
/bin/systemd-ask-password Enter Private Key Password:

It worked unter Ubuntu Trusty and bevor!

What is wrong?


OS Infos:
  Distributor ID: Ubuntu
  Description:Ubuntu Utopic Unicorn (development branch)
  Release:14.10
  Codename:   utopic

  ii  openvpn  2.3.2-9ubuntu1  amd64
   virtual private network daemon
  ii  systemd  208-8ubuntu4amd64
   system and service manager

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
Date: Sat Sep 27 17:12:04 2014
ExecutablePath: /bin/systemd-ask-password
ProcEnviron:
 
SourcePackage: systemd
UpgradeStatus: Upgraded to utopic on 2014-09-27 (0 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  OpenVPN doesnt ask for pkcs12 password

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hi All,

  today I have upgraded my Kubuntu client to Utopic, 
  and now OpenVPN doesen't ask me for my pkcs12 password

  I start it via init.d script as root

root@client:~# /etc/init.d/openvpn start CLIENT1
* Starting virtual private network daemon(s)...
*   Starting VPN 'CLIENT1'
Timed out

  and in the processlist I found, the systemd-ask-password ask for fhe 
password
  but there is no popup or other password ask dialog

8523 ?Sl 0:17  \_ /usr/bin/konsole
8526 pts/0Ss 0:00  |   \_ /bin/bash
9142 pts/0S  0:00  |   |   \_ sudo -i
9143 pts/0S  0:00  |   |   \_ -bash
18807 pts/0S+ 0:00  |   |   \_ /bin/sh -e 
/etc/init.d/openvpn start CLIENT1
18830 pts/0S+ 0:00  |   |   \_ 
/usr/sbin/openvpn --writepid /run/openvpn/CLIENT1.pid --daemon ovpn-CLIENT1 
--status /run/openvpn/CLIENT1.statu
18831 pts/0S+ 0:00  |   |   \_ 
/bin/systemd-ask-password Enter Private Key Password:

  It worked unter Ubuntu Trusty and bevor!

  What is wrong?

  
  OS Infos:
Distributor ID: Ubuntu
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
Codename:   utopic

ii  openvpn  2.3.2-9ubuntu1  amd64  
 virtual private network daemon
ii  systemd  208-8ubuntu4amd64  
 system and service manager

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Sat Sep 27 17:12:04 2014
  ExecutablePath: /bin/systemd-ask-password
  ProcEnviron:
   
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-09-27 (0 days ago)

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

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

[Touch-packages] [Bug 1374785] [NEW] Screen-saver fade-to-black does not cover entire screen on HiDPI

[Anthony S]

Public bug reported:

Display summary: 3840x2160 display with 2x UI scaling

The fade-to-black which occurs prior to the screen shutting off only
covers the top left quarter of the screen.

When scaling is set to 1x, the entire screen fades to black.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
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: Sat Sep 27 11:37:13 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed
 bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed
 nvidia-331-updates, 331.38, 3.13.0-35-generic, x86_64: installed
 nvidia-331-updates, 331.38, 3.13.0-36-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3978]
InstallationDate: Installed on 2014-09-19 (7 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: LENOVO 20378
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=f869a790-cf94-4a68-a435-9ebdc95b4166 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ECN30WW(V1.13)
dmi.board.asset.tag: 31900058WIN
dmi.board.name: Lenovo Y50-70
dmi.board.vendor: LENOVO
dmi.board.version: 31900058WIN
dmi.chassis.asset.tag: 31900058WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Y50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN30WW(V1.13):bd07/16/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70:
dmi.product.name: 20378
dmi.product.version: Lenovo Y50-70
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
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.1
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: Sat Sep 27 10:15:35 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   18514 
 vendor SDC
xserver.version: 2:1.15.1-0ubuntu2.1

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


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

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

Title:
  Screen-saver fade-to-black does not cover entire screen on HiDPI

Status in “unity” package in Ubuntu:
  New

Bug description:
  Display summary: 3840x2160 display with 2x UI scaling

  The fade-to-black which occurs prior to the screen shutting off only
  covers the top left quarter of the screen.

  When scaling is set to 1x, the entire screen fades to black.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  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: Sat Sep 27 11:37:13 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-35-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-36-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA 

[Touch-packages] [Bug 1374778] Re: Can't click at every item with greeter-show-manual-login

[Gunnar Hjalmarsson]

** Package changed: lightdm (Ubuntu) = unity-greeter (Ubuntu)

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

Title:
  Can't click at every item with greeter-show-manual-login

Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  When using greeter-show-manual-login=true some entries of the loginscreen are 
not clickable.
  A concrete example: the loginscreen items are:
  - User 1
  - User 2
  - Login (arbitrary Username can be typed) 
  - Guest Session

  When User 2 is the active item I can click at every other item. When I 
click at Guest Session, Guest Session will be the active item. Now a click 
at Login is without any effect (User 1 and User 2 are still clickable).
  With other computers and different users sometimes more then one item isn't 
clickable. Sometimes no other item can be selected with the mouse, I have to 
use the keyboard!

  I can reproduce this problem with 4 different desktop computers and 2
  different notebooks. I noticed this problem with Ubuntu 12.04, 12.10,
  13.04, 13.10 and 14.04. Same problem with and without LDAP-connection.

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

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

[Touch-packages] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

[mangouste06]

Found [1] here a workaround :

run chrome with :

   LIBGL_DRI3_DISABLE=1 google-chrome

makes webgl come back.


[1]:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435

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

Title:
  Chrome causes segfault in i965_dri.so

Status in Chromium Browser:
  Unknown
Status in “mesa” package in Ubuntu:
  Confirmed
Status in Debian GNU/Linux:
  New

Bug description:
  Running chrome 38.0.2125.66-1 on Ubuntu 14.10, on Lenovo X230

  When I start a new instance of chrome, it cannot enable WebGL. I have
  reported that bug separately to chrome at
  https://code.google.com/p/chromium/issues/detail?id=416207

  I suspect the cause of the bug is in mesa, as dmesg contains evidence
  of a segfault:

  [31979.398090] chrome[24013]: segfault at 20 ip 7fbbd5ca5d83 sp 
7fffd7669ab0 error 4 in i965_dri.so[7fbbd59c4000+50a000]
  [31979.585606] chrome[24104]: segfault at 20 ip 7f7550c26d83 sp 
7fff970b4630 error 4 in i965_dri.so[7f7550945000+50a000]
  [31979.737378] chrome[24117]: segfault at 20 ip 7ffd06e45d83 sp 
7fffc989f440 error 4 in i965_dri.so[7ffd06b64000+50a000]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dri 10.2.6-1ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Sep 20 11:17:41 2014
  DistUpgraded: 2014-09-02 14:59:08,481 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21fa]
  MachineType: LENOVO 23301B9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-16-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet crashkernel=384M-:128M 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to utopic on 2014-09-02 (17 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23301B9
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn23301B9:pvrThinkPadX230:rvnLENOVO:rn23301B9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23301B9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Sep 19 15:45:16 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4204 
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1371834/+subscriptions

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

[Touch-packages] [Bug 1310260] Re: Pulseaudio fails to detect card (probably due to hybrid graphics)

[Letik]

Still same problem with ArcLinux ! 
https://bbs.archlinux.org/viewtopic.php?id=187542
The fix worked !

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

Title:
  Pulseaudio fails to detect card (probably due to hybrid graphics)

Status in “alsa-driver” package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I wanted to install Trusty on my Elitebook 850 G1 with hybrid graphics (Intel 
/ AMD) but pulseaudio goes nuts on me as soon as I try to play any music / 
sound, try to change volume, etc.
  I've tried it with Ubuntu, Kubuntu and now with Xubuntu with the same result 
everytime.

  My guess is that pulseaudio has problems with the AMD GPU and it's sound 
processor being switched off automatically as enabled by Kernel 3.13 (formerly 
achieved by adding the radeon.runpm=1 kernel parameter)
  (http://lists.freedesktop.org/archives/dri-devel/2013-September/045650.html)

  root@HP-EliteBook-850-G1:~# cat /sys/kernel/debug/vgaswitcheroo/switch
  0:IGD:+:Pwr::00:02.0
  1:DIS: :DynOff::03:00.0
  2:DIS-Audio: :Off::03:00.1

  As you can see, the AMD GPU has been turned off automatically. Pulseaudio, 
the (X)Ubuntu volume applet and KMix on the other hand list it as still 
available.
  Based on that I asume pulseaudio tries to access a switched-off device and 
fails.

  I've followed the steps listed
  here: https://wiki.ubuntu.com/DebuggingSoundProblems
  and
  here: https://wiki.ubuntu.com/PulseAudio/Log

  I'll attach the logs right away. (pulseverbose1.log and my dmesg
  output)

  Pusleverbose is full of messages like this one:
  (   0.013|   0.000) I: [pulseaudio] alsa-util.c: Error opening PCM device 
hw:0: No such file or directory

  This output of dmesg also caught my attention:
  [  354.927935] HDMI ATI/AMD: no speaker allocation for ELD
  [  357.695010] hda-intel :03:00.1: Disabling via VGA-switcheroo

  One thing I noticed using Kubuntu is that after pulseaudio becomes 
unresponsive the taskmanager lists 4 pulseaudio processes two of which are 
active on harddrive (Aktiv auf Festplatte). Those two processes cannot be 
killed even as root.
  Currently being on Xubuntu the same thing is true, although it lists only one 
process in the taskmanager that cannot be killed.

  I hope you can help me.

  Best regards,
  Paul

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sun Apr 20 13:47:09 2014
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP EliteBook 850 G1, IDT 92HD91BXX, Speaker, Internal] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.08
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.54
  dmi.chassis.asset.tag: CNU345BY96
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.08:bd02/19/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3008CC10003:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.version: A3008CC10003
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1312107] Re: Minimised applications show briefly before lock and after unlock (again)

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Minimised applications show briefly before lock and after unlock
  (again)

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

Bug description:
  [Impact]
  With the new locking scheme in unity7, minimized applications appear briefly 
after unlocking
  Here is a video showing the problem: 
https://www.dropbox.com/s/ai5r2krtgbo93im/2014-04-24%2009.51.52.mp4

  [Test case]
  1. Open some applications (in my case psensor and steam)
  2. Minimize them
  3. Press CTRL+ALT+L or Super+L to lock the screen
  The minimized windows should never briefly popup before the screen locks.

  4. Unlock screen
  The minimized windows should never re-appear and then re-minimize.

  The minimized applications must stay minimised through the lock/unlock
  process.

  [Regression Potential]
  Nothing known


  There is another bug about this but it is marked as fixed.. so I guess
  the problem wasn't fixed after all? #1291402

  ProblemType: BugDistroRelease: 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
  .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: Thu Apr 24 12:41:24 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21cf]
  InstallationDate: Installed on 2014-03-26 (28 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140325.1)
  MachineType: LENOVO 42433ZG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=c3c7f36f-ca42-443e-819f-5553fe3d040a ro quiet splash 
vt.handoff=7SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42433ZG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn42433ZG:pvrThinkPadT520:rvnLENOVO:rn42433ZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42433ZG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  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.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: Tue Apr 15 12:18:55 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1415
   vendor SAM
  xserver.version: 2:1.15.1-0ubuntu1

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

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

[Touch-packages] [Bug 1320051] Re: Shutdown dialog should not allow to lock a session if it's not allowed by settings

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Shutdown dialog should not allow to lock a session if it's not allowed
  by settings

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

Bug description:
  [Test case]
  1. Disable lockscreen with:
  gsettings set org.gnome.desktop.lockdown disable-lock-screen true
  2. When pressing the power button or requesting a logout, unity should not 
show the lock
 options in the shutdown dialog

  [Regression potential]
  Lock button might not be shown to other users as well, but this is very 
unlikely to happen.

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

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

[Touch-packages] [Bug 1306211] Re: Trying to lock screen in a guest session leads to an unusable session

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Trying to lock screen in a guest session leads to an unusable session

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

Bug description:
  [Impact]
  Screen is dimed and woken up in a loop when trying to lock a guest session

  [Test case]
  - log into a guest session
  - pick logout
  - misclick and hit lock
  - Nothing should happen

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

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

[Touch-packages] [Bug 1374825] [NEW] VDPAU does not work in libav on Utopic

[Michael Marley]

Public bug reported:

After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support
has stopped working in all applications that use libav.  In mplayer2, it
prints Cannot find codec 'h264_vdpau' in libavcodec... and in VLC I
get [7f909958] vdpau_avcodec generic error: decoder profile not
supported: 6.

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

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

Title:
  VDPAU does not work in libav on Utopic

Status in “libav” package in Ubuntu:
  New

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec...
  and in VLC I get [7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6.

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

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

[Touch-packages] [Bug 1276373] Re: invalid cross-device link

[Chris Croome]

Using the image-based system updates results in any additional packages
that have been added needing to be reinstalled (for example screen to
enable more than one terminal sessions to use used at the same time).
This isn't optimial for people who want to use teminal based
applications, I realise that people like this are not the key audience
for Ubuntu Touch but is some consideration of users of this nature
possible?

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

Title:
  invalid cross-device link

Status in “lxc-android-config” package in Ubuntu:
  Won't Fix

Bug description:
  Manually updated my gnexus via APT. Not sure if I broke something or
  if it is a problem with the package but I got the following problem:

  Preparing to unpack .../lxc-android-config_0.135_all.deb ...
  Leaving 'diversion of 
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy to 
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy.orig by 
lxc-android-config'
  Unpacking lxc-android-config (0.135) over (0.126) ...
  dpkg: error processing archive 
/var/cache/apt/archives/lxc-android-config_0.135_all.deb (--unpack):
   unable to make backup link of `./lib/udev/rules.d/70-android.rules' before 
installing new version: Invalid cross-device link
  Errors were encountered while processing:
   /var/cache/apt/archives/lxc-android-config_0.135_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Now, I can only boot to Ubuntu via recovery mode and not to Android
  anymore (had a dual boot). However, I am not sure if the latter is
  related to this problem.

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

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

[Touch-packages] [Bug 1339629] Re: Dash Previews don't scale correctly when the scale factor changes

[Mateusz Stachowski]

The previews scale correctly hovewer it seems that overlay scrollbars
are not working. I can't scroll the descriptions using them but mouse
scroll wheel works.

Also the overlay scrollbars work when scaling is set to value ranging
from 0.5 to 1.38. They stop working for me from 1.5 and up to 2.

I also don't have a HiDPI monitor so I only checked on regular one 16:9
1920x1080.

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

Title:
  Dash Previews don't scale correctly when the scale factor changes

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

Bug description:
  [Impact]
  When scaling is set to a value different to 1.0 and the user performs a dash 
search and right clicks a result, the Preview is always rendered with scale 
factor 1.0.

  [Test case]
  1. From Unity Control Center - Displays - Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, [search something], right click over a result
  3. The preview items should respect the previously set monitor scaling

  [Regression potential]
  This is a big change that involved lots of changes in the unity dash code, 
although we
  didn't notice any regression due to this change. At the contrary we improved 
a lot the old code we worked on. Although it's still possible that some 
component of the dash previews might be hidden/distorted or not shown as it 
used to be.

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

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

[Touch-packages] [Bug 1340394] Re: Overlay borders aren't scaled to match monitor DPI scaling

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Overlay borders aren't scaled to match monitor DPI scaling

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

Bug description:
  [Impact]
  The dash or Hud borders aren't scaled to match the current settings

  [Test case]
  1. From Unity Control Center - Displays - Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash first, then the Hud
  3. The borders ribbon should be scaled to respect the current monitor scaling 
factor

  [Regression potential]
  Textures aren't properly shown around the unity overlays

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

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

[Touch-packages] [Bug 1340171] Re: Dash filters don't scale up/down to match the current monitor scale factor

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Dash filters don't scale up/down to match the current monitor scale
  factor

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

Bug description:
  [Impact]
  Dash filters does not respect the configured monitor scaling

  [Test case]
  1. From Unity Control Center - Displays - Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, expand the filters on the right
  3. The filter buttons and texts should respect the current monitor scaling, 
in each scope

  [Regression potential]
  The change mostly consisted in making the old sizes to be always multiplied 
for the scaling factor, then nothing should change when multiplying by 1.
  Although there might still be visual regressions in the dash search and 
filters widgets.

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

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

[Touch-packages] [Bug 1340992] Re: It's not possible to scroll over the dash overlay scrollbars as it happens in gtk applications

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  It's not possible to scroll over the dash overlay scrollbars as it
  happens in gtk applications

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

Bug description:
  [Impact]
  Scrolling over the scrollbars thumbs makes the thumb to disappear instead 
that apply the scroll to its view.

  [Test case]
  1. Open the dash, expand the search results so that scroll bars show
  2. Move the mouse over the scrollbar to make the thumb to show, and hover it
  3. Scroll over the scrollbars thumb and, and the related scrolled view should
     be properly scrolled up/down.

  [Regression potential]
  Nothing known

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

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

[Touch-packages] [Bug 1340477] Re: The HUD doesn't support scaling on HiDPI monitors

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  The HUD doesn't support scaling on HiDPI monitors

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

Bug description:
  [Impact]
  The HUD is not scaled on HiDPI monitors

  [Test case]
  1. From Unity Control Center - Displays - Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the Hud
  3. Both the view, the text and the search results should be properly scaled to
 match current monitor scaling factor

  [Regression potential]
  Very low, but the hud might have visual issues (nothing found so far)

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

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

[Touch-packages] [Bug 1340996] Re: Overlay scrollbars doesn't scale to match the current DPI settings

[Mateusz Stachowski]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Overlay scrollbars doesn't scale to match the current DPI settings

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

Bug description:
  [Impact]
  Dash scrollbars do not respect the configured monitor scaling

  [Test case]
  1. From Unity Control Center - Displays - Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, expand the results so that the scrollbars show
  3. Hover a scrollbar and the overlay scrollbar thumb should appear
  4. Both the scrollbar and the thumb should be scaled matching the current DPI 
settings
 for the monitor the dash is in

  The same should happen in previews.

  [Regression potential]
  Very low. A possibility might be missing scrollbars somewhere in the dash.

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

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

[Touch-packages] [Bug 1340996] Re: Overlay scrollbars doesn't scale to match the current DPI settings

[Mateusz Stachowski]

Everything scales correctly hovewer as I already mentioned in Bug
#1339629 dragging or clicking overlay scrollbars stops working when I
have set scale factor to values beetwen 1.5 and 2.

I can scroll them with mouse wheel but dragging or clicking on them
doesn't work.

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

Title:
  Overlay scrollbars doesn't scale to match the current DPI settings

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

Bug description:
  [Impact]
  Dash scrollbars do not respect the configured monitor scaling

  [Test case]
  1. From Unity Control Center - Displays - Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, expand the results so that the scrollbars show
  3. Hover a scrollbar and the overlay scrollbar thumb should appear
  4. Both the scrollbar and the thumb should be scaled matching the current DPI 
settings
 for the monitor the dash is in

  The same should happen in previews.

  [Regression potential]
  Very low. A possibility might be missing scrollbars somewhere in the dash.

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

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

[Touch-packages] [Bug 1365977] Re: Ubuntu Store front is not translated into Norwegian

[Alejandro J. Cura]

Can you please attach a screenshot?
I'd like to understand if it's the translated labels shown by the scope or the 
departments and highlight text that comes from the webservices.

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

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

Title:
  Ubuntu Store front is not translated into Norwegian

Status in “unity-scope-click” package in Ubuntu:
  Incomplete

Bug description:
  Opening the Ubuntu Store using a Norwegian locale gives me English
  labels on everything. On the second level (in an app, e.g.), most
  items are translated.

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

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

[Touch-packages] [Bug 1374833] Re: tracker-extract crashed with signal 5 in g_malloc()

[Apport retracing service]

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

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 #1366116, 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/1374833/+attachment/4217520/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1374833/+attachment/4217522/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1374833/+attachment/4217523/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1374833/+attachment/4217524/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1374833/+attachment/4217525/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1374833/+attachment/4217526/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1374833/+attachment/4217527/+files/ThreadStacktrace.txt

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

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

Title:
  tracker-extract crashed with signal 5 in g_malloc()

Status in “tracker” package in Ubuntu:
  New

Bug description:
  gilles@gilles-EP31-DS3L:~$ apt-cache policy tracker
  tracker:
Installé : 1.0.4-0ubuntu1
Candidat : 1.0.4-0ubuntu1
   Table de version :
   *** 1.0.4-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status
  gilles@gilles-EP31-DS3L:~$ lsb_release -rd
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: tracker-extract 1.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Sep 27 15:42:26 2014
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2014-04-05 (174 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 
(20140326.1)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   tracker_extract_get_metadata () from 
/usr/lib/x86_64-linux-gnu/tracker-1.0/extract-modules/libextract-gif.so
   ?? ()
   ?? ()
   ?? ()
  Title: tracker-extract crashed with signal 5 in g_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1365977] Re: Ubuntu Store front is not translated into Norwegian

[Alejandro J. Cura]

Nevermind, just changed the lang on my nexus, and was able to reproduce.
All of the untranslated text comes from webservices, so this bug is about 
completing the translations of those in the servers.
I'll assign the bug to software-center-agent, where I understand these strings 
reside.

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

** Also affects: software-center-agent
   Importance: Undecided
   Status: New

** Changed in: software-center-agent
   Importance: Undecided = High

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

Title:
  Ubuntu Store front is not translated into Norwegian

Status in Online service used by software center:
  New
Status in “unity-scope-click” package in Ubuntu:
  Invalid

Bug description:
  Opening the Ubuntu Store using a Norwegian locale gives me English
  labels on everything. On the second level (in an app, e.g.), most
  items are translated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-center-agent/+bug/1365977/+subscriptions

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

[Touch-packages] [Bug 1339629] Re: Dash Previews don't scale correctly when the scale factor changes

[Mateusz Stachowski]

In my comment I meant that dragging or clicking overlay scrollbars
doesn't work for me when scaling factor is set to values ranging from
1.5 to 2.

However I can scroll the descriptions using mouse scroll wheel over the
overlay scrollbars.

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

Title:
  Dash Previews don't scale correctly when the scale factor changes

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

Bug description:
  [Impact]
  When scaling is set to a value different to 1.0 and the user performs a dash 
search and right clicks a result, the Preview is always rendered with scale 
factor 1.0.

  [Test case]
  1. From Unity Control Center - Displays - Change the monitor scaling to 
somewhat
 different from 1.0 (might be both bigger and smaller, your choice).
  2. Open the dash, [search something], right click over a result
  3. The preview items should respect the previously set monitor scaling

  [Regression potential]
  This is a big change that involved lots of changes in the unity dash code, 
although we
  didn't notice any regression due to this change. At the contrary we improved 
a lot the old code we worked on. Although it's still possible that some 
component of the dash previews might be hidden/distorted or not shown as it 
used to be.

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

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

[Touch-packages] [Bug 1353951] Re: gnome online accounts require autentication on startup

[Mathew Hodson]

Setting tag based on comment #17.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  gnome online accounts require autentication on startup

Status in Evolution Data Server:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “gnome-online-accounts” package in Ubuntu:
  Invalid
Status in “evolution-data-server” source package in Trusty:
  Fix Committed
Status in “gnome-online-accounts” source package in Trusty:
  Invalid

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]
  1) open gnome-online-accounts
  2) click + and add a google account
  3) enter user name and password
  4) confirm permissions for gnome
  5) Black window pops up and asks for google password, but does not accept the 
correct password.
  Google Contacts are not available in Gnome or Thunderbird

  [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).


  

  Gnome online accounts requires autentication on startup, but even typing the 
correct password in the box, the program says the password is wrong. By the way 
evolution and other programs work well with online accounts. I'm using 
Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour.
  Just to be clear: online-accounts works well, just at startup it opens an 
administration window where it requires to insert the password for my google 
accounts; if I type the correct password it says that the password is wrong, 
the only way to close the window is to click on discard and then all works 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+subscriptions

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

[Touch-packages] [Bug 1374207] Re: CVE-2014-7169 fix not effective on trusty

[Mathew Hodson]

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

** This bug has been marked a duplicate of bug 1373781
   bash incomplete fix for CVE-2014-6271

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

Title:
  CVE-2014-7169 fix not effective on trusty

Status in “bash” package in Ubuntu:
  Invalid
Status in “bash” source package in Lucid:
  Fix Released
Status in “bash” source package in Precise:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released
Status in “bash” source package in Utopic:
  Invalid

Bug description:
  I can reproduce the testcase from 1373781 with bash 4.3-7ubuntu1.2 on
  trusty.  The patch did NOT fix it, unfortunately.

  rtucker@racer-x:~$ rm -f echo  env -i X='() { (a)=\' bash -c 'echo id'; 
cat echo
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  uid=1000(rtucker) gid=1000(rtucker) 
groups=1000(rtucker),4(adm),6(disk),24(cdrom),27(sudo),30(dip),46(plugdev),112(lpadmin),119(sambashare)
  rtucker@racer-x:~$ bash --version
  GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  rtucker@racer-x:~$ apt-cache policy bash
  bash:
Installed: 4.3-7ubuntu1.2
Candidate: 4.3-7ubuntu1.2
Version table:
   *** 4.3-7ubuntu1.2 0
  500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages

  
  precise does seem fixed, however:

  rtucker@barleywine:~$ rm -f echo  env -i X='() { (a)=\' bash -c 'echo id'; 
cat echo
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  id
  cat: echo: No such file or directory
  rtucker@barleywine:~$ bash --version
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2011 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  rtucker@barleywine:~$ apt-cache policy bash
  bash:
Installed: 4.2-2ubuntu2.3
Candidate: 4.2-2ubuntu2.3
Version table:
   *** 4.2-2ubuntu2.3 0
  500 http://mirrors.linode.com/ubuntu/ precise-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ precise-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.2-2ubuntu2 0
  500 http://mirrors.linode.com/ubuntu/ precise/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

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

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

[Touch-packages] [Bug 1374825] Re: VDPAU does not work in libav on Utopic

[Michael Marley]

This seems to be due to an API change in libav.  They dropped the old
API for using VDPAU decoding, which broke every application that uses
VDPAU through libav.  https://libav.org/releases/libav-10.5.release

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

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

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

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

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

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

Title:
  VDPAU does not work in libav on Utopic

Status in “libav” package in Ubuntu:
  Invalid
Status in “mplayer” package in Ubuntu:
  New
Status in “mplayer2” package in Ubuntu:
  New
Status in “mpv” package in Ubuntu:
  New
Status in “vlc” package in Ubuntu:
  New

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec...
  and in VLC I get [7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6.

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

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

[Touch-packages] [Bug 1374207] Re: CVE-2014-7169 fix not effective on trusty

[Mathew Hodson]

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

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7169

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

Title:
  CVE-2014-7169 fix not effective on trusty

Status in “bash” package in Ubuntu:
  Invalid
Status in “bash” source package in Lucid:
  Fix Released
Status in “bash” source package in Precise:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released
Status in “bash” source package in Utopic:
  Invalid

Bug description:
  I can reproduce the testcase from 1373781 with bash 4.3-7ubuntu1.2 on
  trusty.  The patch did NOT fix it, unfortunately.

  rtucker@racer-x:~$ rm -f echo  env -i X='() { (a)=\' bash -c 'echo id'; 
cat echo
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  uid=1000(rtucker) gid=1000(rtucker) 
groups=1000(rtucker),4(adm),6(disk),24(cdrom),27(sudo),30(dip),46(plugdev),112(lpadmin),119(sambashare)
  rtucker@racer-x:~$ bash --version
  GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  rtucker@racer-x:~$ apt-cache policy bash
  bash:
Installed: 4.3-7ubuntu1.2
Candidate: 4.3-7ubuntu1.2
Version table:
   *** 4.3-7ubuntu1.2 0
  500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages

  
  precise does seem fixed, however:

  rtucker@barleywine:~$ rm -f echo  env -i X='() { (a)=\' bash -c 'echo id'; 
cat echo
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  id
  cat: echo: No such file or directory
  rtucker@barleywine:~$ bash --version
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2011 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  rtucker@barleywine:~$ apt-cache policy bash
  bash:
Installed: 4.2-2ubuntu2.3
Candidate: 4.2-2ubuntu2.3
Version table:
   *** 4.2-2ubuntu2.3 0
  500 http://mirrors.linode.com/ubuntu/ precise-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ precise-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.2-2ubuntu2 0
  500 http://mirrors.linode.com/ubuntu/ precise/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

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

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

[Touch-packages] [Bug 1302955] Re: upstart user session leaks all the dbus events it receives

[Launchpad Bug Tracker]

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

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

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

Title:
  upstart user session leaks all the dbus events it receives

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

Bug description:
  Easiest way to see this:
  0. Make sure there is a user session job with a dbus rule (eg 
unity-greeter-session-broadcast)
  1. Install and run system-load-indicator (indicator-multiload)
  2. Set the update interval to 100ms
  3. Now watch the memory use of init --user increase by 100kb per second
  4. Also open up upstart-monitor to see all the dbus messages being sent

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  5 18:17:40 2014
  InstallationDate: Installed on 2013-06-22 (287 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-12-05 (120 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

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

[Touch-packages] [Bug 1373781] Re: bash incomplete fix for CVE-2014-6271

[Mathew Hodson]

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-6271

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

Title:
  bash incomplete fix for CVE-2014-6271

Status in “bash” package in Ubuntu:
  Fix Released
Status in “bash” source package in Lucid:
  Fix Released
Status in “bash” source package in Precise:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released
Status in “bash” source package in Utopic:
  Fix Released

Bug description:
  The fixes for CVE-2014-6271 do NOT work! Security vuln, but should be
  public, this is known already.

  Ubuntu 14.04 LTS: bash 4.3-7ubuntu1.1
  Ubuntu 12.04 LTS: bash 4.2-2ubuntu2.2
  Ubuntu 10.04 LTS: bash 4.1-2ubuntu3.1

  Testcase:
  rm -f echo  env -i  X='() { (a)=\' bash -c 'echo id'; cat echo

  expected output:
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  id

  actual output:
  bash: X: line 1: syntax error near unexpected token `='
  bash: X: line 1: `'
  bash: error importing function definition for `X'
  uid=0(root) gid=0(root) groups=0(root)

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

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

[Touch-packages] [Bug 1374825] Re: VDPAU does not work in libav on Utopic

[Rémi Denis-Courmont]

[7f909958] vdpau_avcodec generic error: decoder profile not
supported: 6 means that:

1) your libavcodec installation does support VDPAU properly, and
2 ) your VDPAU driver does not support H.264 decoding at all (or reports 
incorrect capabilities).

Closing as invalid.

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

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

Title:
  VDPAU does not work in libav on Utopic

Status in “libav” package in Ubuntu:
  Invalid
Status in “mplayer” package in Ubuntu:
  New
Status in “mplayer2” package in Ubuntu:
  New
Status in “mpv” package in Ubuntu:
  New
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec...
  and in VLC I get [7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6.

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

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

[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Launchpad Bug Tracker]

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

** Changed in: upower (Ubuntu)
   Status: New = Confirmed

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 service_client_free+25:   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source (%esi) (0x302e) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  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/1305699/+subscriptions

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

[Touch-packages] [Bug 1174098] Re: blockdev doesn't work as reported with loop devices

[Ketil]

Proposed package works for me, and I confirmed again that the version I
had before upgrading had the same issue. From apt-get output:

Unpacking util-linux (2.20.1-5.1ubuntu20.2) over (2.20.1-5.1ubuntu20.1)
...

I don't see where I can change verification-needed to verification-done,
however. Hopefully someone else can take care of that.

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

Title:
  blockdev doesn't work as reported with loop devices

Status in “util-linux” package in Ubuntu:
  Fix Released
Status in “util-linux” source package in Trusty:
  Fix Committed
Status in “util-linux” source package in Utopic:
  Fix Released

Bug description:
  SRU Justification:
  [Impact]
  blockdev won't work correctly with loopback devices.

  [Test Case]
  1) Create and mount a loop back device on /dev/loop0
  2) Run:
  $ sudo blockdev --report /dev/loop0
  This should work without an ioctl error.

  [Regression Potential]
  This patch is backported from an upstream release commit 569d1dac.
  Its already in utopic, and the patch modifies the program to no longer use an 
invalid ioctl call.

  --

  According to blockdev's manual:

     --report
    Print a report for the specified device. It is possible to  give
    multiple  devices. If none is given, all devices which appear in
    /proc/partitions are shown. Note that the partition StartSec  is
    in 512-byte sectors.

  However, I'm running Ubuntu installed with wubi, so my root dev is on
  a loopback device. Here's my /proc/partitions:

  major minor  #blocks  name

     70   30457856 loop0
     71   31457280 loop1
     80  732574584 sda
     81   26214400 sda1
     82  307263488 sda2
     83  1 sda3
     85  399092736 sda5

  So according to the manual, all these devices should be printed with
  blockdev --report. But they are not, the loop devices are excluded:

  $ sudo blockdev --report
  [sudo] password for user:
  RORA   SSZ   BSZ   StartSecSize   Device
  rw   256   512  4096  0750156374016   /dev/sda
  rw   256   512  4096   2048 26843545600   /dev/sda1
  rw   256   512  4096   52430848314637811712   /dev/sda2
  rw   256   512  1024  6669578241024   /dev/sda3
  rw   256   512  4096  666959872408670961664   /dev/sda5
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-5.1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Sun Apr 28 23:48:07 2013
  InstallationDate: Installed on 2012-04-12 (381 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to quantal on 2012-11-15 (164 days ago)

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

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

[Touch-packages] [Bug 1373645] Re: Logitech wireless mouse periodically loses correct click behaviour

[Christopher M. Penalver]

Darren Long, thank you for reporting this and helping make Ubuntu better. As 
per http://www.asus.com/Motherboards/Z87IPRO/HelpDesk_Download/ an update to 
your BIOS is available (0907). If you update to this following 
https://help.ubuntu.com/community/BiosUpdate does it change anything?  If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Once the BIOS is updated, then please mark this report Status New.

Thank you for your understanding.

** Tags added: bios-outdated-0907

** Changed in: xorg (Ubuntu)
   Importance: Undecided = Low

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

** Description changed:

- I have reported this bug as a result of responses to my post on Bug
- #1371853.  I first noticed this issue on Friday 19th September 2014.
- 
- My logitech cordless mouse suddenly started behaving very oddly in
- 14.04..  The machine had been running for over a week , but without much
- use for that working week (Mon-Fri) until I plugged in my new X-Box 360
- controller and attempted to configure my TV as a 2nd screen for a gaming
- session.
- 
- I then found that, at some times, mouse clicks didn't seem to be
- registering with the system as expected. Switching virtual desktops
- backwards and forwards seemed to restore some ability to click with
- results, but this would bring only temporary relief. I didn't see
- anything noteworthy in the dmesg output.
+ I first noticed on Friday 19th September 2014 in 14.04 my Logitech
+ cordless mouse I then found that, at some times, mouse clicks didn't
+ seem to be registering with the system as expected. Switching virtual
+ desktops backwards and forwards seemed to restore some ability to click
+ with results, but this would bring only temporary relief.
  
  The same symptoms were observed using either my desktop monitor, the TV
- or both in a dual screen configuration.  The problem survived
- disconnection of the USB wireless receiver and power cycling of the
- mouse, and also across reboots.
+ or both in a dual screen configuration. The problem survived
+ disconnection of the USB wireless receiver, power cycling of the mouse,
+ and across reboots.
  
  At one point I noticed that the mouse focus seemed to have become
  incoherent, in that left clicking in the search window in Firefox
  produced a text insertion caret there, but keyboard text appeared in the
  console that had previously had mouse focus.
  
- I soon found that a wired USB mouse worked OK, googled for clues for a
- few days and then found Bug #1371853 which prompted me to file
- something.
- 
- I have been using 14.04 for some months now without any related issues.
- This machine is normally in fairly heavy daily use, but during the
- weekdays Monday 15th Sept 2014 through to Friday 19th Semptember 2014
- had only had light use during which I might have not have noticed this
- issue.  I definitely didn't experience it before plugging in the
- XBOX-360 controller for the first time on Friday 19th and noticed it
- within a few minutes of that.
- 
- I have since confirmed that disconnecting the XBOX-360 controller
- doesn't stop the issue once it has started.  I have also confirmed that
- the issue can still arise after rebooting with the XBOX-360 controller
- disconnected.  Whether the XBOX-360 controller is at all relevant or
- not, I do not know.
- 
- For now, I have adopted the wired USB mouse workaround.
+ WORKAROUND: Use a wired mouse.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
-  GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
+  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)
  .proc.driver.nvidia.warnings.fbdev:
-  Your system is not currently configured to drive a VGA console
-  on the primary VGA device. The NVIDIA Linux graphics driver
-  requires the use of a text-mode VGA console. Use of other console
-  drivers including, but not limited to, vesafb, may result in
-  corruption and stability problems, and is not supported.
+  Your system is not currently configured to drive a VGA console
+  on the primary VGA device. 

[Touch-packages] [Bug 1374863] [NEW] wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04

[paolode]

Public bug reported:

wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for
many users using intel wifi card (as described in thid thread:
http://forum.ubuntu-it.org/viewtopic.php?p=4587552), maybe a
driver/kernel issue.

slved via:
sudo modprobe -rv iwl3945
sudo modprobe -v iwl3945 swcrypto=1
cat /etc/hosts
sudo rmmod iwl3945
sudo modprobe iwl3945

Intel signaled a previous problem of compatibility between driver and
some kernels.

I updated recently from ubuntu 12.04 to xubuntu 14.04.  the problem
didn't existed when I updated via 'update-manager -d', but appeared when
I reinstalled new xubuntu from live dvd.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7 [modified: usr/bin/nm-online 
usr/bin/nm-tool usr/bin/nmcli usr/lib/NetworkManager/nm-avahi-autoipd.action 
usr/lib/NetworkManager/nm-dhcp-client.action 
usr/lib/NetworkManager/nm-dispatcher.action usr/sbin/NetworkManager]
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.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Sep 27 23:47:32 2014
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-09-12 (15 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
IpRoute:
 default via 192.168.1.254 dev wlan0  proto static 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.128  metric 9
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID   TYPE  
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
 Connessione via cavo 1b4fb3004-8943-4f93-818b-eaa081e97aa6   
802-3-ethernet1411820971   sab 27 set 2014 14:29:31 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/1
 FASTWEB-1-zMohBACjWHjtfad5a9fd-124b-49d1-a0e1-11f0f0b17f67   
802-11-wireless   1411854271   sab 27 set 2014 23:44:31 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


** Tags: amd64 apport-bug trusty

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

Title:
  wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for
  many users using intel wifi card (as described in thid thread:
  http://forum.ubuntu-it.org/viewtopic.php?p=4587552), maybe a
  driver/kernel issue.

  slved via:
  sudo modprobe -rv iwl3945
  sudo modprobe -v iwl3945 swcrypto=1
  cat /etc/hosts
  sudo rmmod iwl3945
  sudo modprobe iwl3945

  Intel signaled a previous problem of compatibility between driver and
  some kernels.

  I updated recently from ubuntu 12.04 to xubuntu 14.04.  the problem
  didn't existed when I updated via 'update-manager -d', but appeared
  when I reinstalled new xubuntu from live dvd.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7 [modified: usr/bin/nm-online 
usr/bin/nm-tool usr/bin/nmcli usr/lib/NetworkManager/nm-avahi-autoipd.action 
usr/lib/NetworkManager/nm-dhcp-client.action 
usr/lib/NetworkManager/nm-dispatcher.action usr/sbin/NetworkManager]
  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.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 27 23:47:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-09-12 (15 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.128  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   

[Touch-packages] [Bug 1374864] [NEW] wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for many users using intel wifi card (as described in thid thread: http://forum.ubuntu-it.org/vie

[paolode]

Public bug reported:

wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for many 
users using intel wifi card (as described in thid thread:  
http://forum.ubuntu-it.org/viewtopic.php?p=4587552), maybe a driver/kernel 
issue.
about every half an hour the connection is lost and I have to reset both pc and 
router.

slved via:
sudo modprobe -rv iwl3945
sudo modprobe -v iwl3945 swcrypto=1
cat /etc/hosts
sudo rmmod iwl3945
sudo modprobe iwl3945

Intel signaled a previous problem of compatibility between driver and
some kernels.

I updated recently from ubuntu 12.04 to xubuntu 14.04.  the problem
didn't existed when I updated via 'update-manager -d', but appeared when
I reinstalled new xubuntu from live dvd.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7 [modified: usr/bin/nm-online 
usr/bin/nm-tool usr/bin/nmcli usr/lib/NetworkManager/nm-avahi-autoipd.action 
usr/lib/NetworkManager/nm-dhcp-client.action 
usr/lib/NetworkManager/nm-dispatcher.action usr/sbin/NetworkManager]
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.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Sep 27 23:47:32 2014
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-09-12 (15 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
IpRoute:
 default via 192.168.1.254 dev wlan0  proto static 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.128  metric 9
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID   TYPE  
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
 Connessione via cavo 1b4fb3004-8943-4f93-818b-eaa081e97aa6   
802-3-ethernet1411820971   sab 27 set 2014 14:29:31 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/1
 FASTWEB-1-zMohBACjWHjtfad5a9fd-124b-49d1-a0e1-11f0f0b17f67   
802-11-wireless   1411854271   sab 27 set 2014 23:44:31 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


** Tags: amd64 apport-bug trusty

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

Title:
  wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for
  many users using intel wifi card (as described in thid thread:
  http://forum.ubuntu-it.org/viewtopic.php?p=4587552), maybe a
  driver/kernel issue.

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for many 
users using intel wifi card (as described in thid thread:  
http://forum.ubuntu-it.org/viewtopic.php?p=4587552), maybe a driver/kernel 
issue.
  about every half an hour the connection is lost and I have to reset both pc 
and router.

  slved via:
  sudo modprobe -rv iwl3945
  sudo modprobe -v iwl3945 swcrypto=1
  cat /etc/hosts
  sudo rmmod iwl3945
  sudo modprobe iwl3945

  Intel signaled a previous problem of compatibility between driver and
  some kernels.

  I updated recently from ubuntu 12.04 to xubuntu 14.04.  the problem
  didn't existed when I updated via 'update-manager -d', but appeared
  when I reinstalled new xubuntu from live dvd.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7 [modified: usr/bin/nm-online 
usr/bin/nm-tool usr/bin/nmcli usr/lib/NetworkManager/nm-avahi-autoipd.action 
usr/lib/NetworkManager/nm-dhcp-client.action 
usr/lib/NetworkManager/nm-dispatcher.action usr/sbin/NetworkManager]
  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.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 27 23:47:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-09-12 (15 days ago)
  

[Touch-packages] [Bug 1374864] Re: wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for many users using intel wifi card (as described in thid thread: http://forum.ubuntu-it.org/viewt

[paolode]

the wifi connection gets lost every half an hour

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

Title:
  wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for
  many users using intel wifi card (as described in thid thread:
  http://forum.ubuntu-it.org/viewtopic.php?p=4587552), maybe a
  driver/kernel issue.

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  wifi becomes unstable upgrading from ubuntu 12.04 to ubuntu 14.04 for many 
users using intel wifi card (as described in thid thread:  
http://forum.ubuntu-it.org/viewtopic.php?p=4587552), maybe a driver/kernel 
issue.
  about every half an hour the connection is lost and I have to reset both pc 
and router.

  slved via:
  sudo modprobe -rv iwl3945
  sudo modprobe -v iwl3945 swcrypto=1
  cat /etc/hosts
  sudo rmmod iwl3945
  sudo modprobe iwl3945

  Intel signaled a previous problem of compatibility between driver and
  some kernels.

  I updated recently from ubuntu 12.04 to xubuntu 14.04.  the problem
  didn't existed when I updated via 'update-manager -d', but appeared
  when I reinstalled new xubuntu from live dvd.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7 [modified: usr/bin/nm-online 
usr/bin/nm-tool usr/bin/nmcli usr/lib/NetworkManager/nm-avahi-autoipd.action 
usr/lib/NetworkManager/nm-dhcp-client.action 
usr/lib/NetworkManager/nm-dispatcher.action usr/sbin/NetworkManager]
  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.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 27 23:47:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-09-12 (15 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.128  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Connessione via cavo 1b4fb3004-8943-4f93-818b-eaa081e97aa6   
802-3-ethernet1411820971   sab 27 set 2014 14:29:31 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/1
   FASTWEB-1-zMohBACjWHjtfad5a9fd-124b-49d1-a0e1-11f0f0b17f67   
802-11-wireless   1411854271   sab 27 set 2014 23:44:31 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[Alberto Salvia Novella]

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided = High

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

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in Nautilus:
  New
Status in Unity:
  Triaged
Status in “bamf” package in Ubuntu:
  Triaged
Status in “gnome-shell” package in Ubuntu:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

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

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

[Touch-packages] [Bug 1315446] Re: Clicking on Files doesn't bring up open Nautilus window

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Clicking on Files doesn't bring up open Nautilus window

Status in “nautilus” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  If I have my external hard drive open in a Nautilus window and focus a
  different window, clicking on Files opens a new Home Folder window,
  instead of focussing the background EHDD window.

  If it is relevant, I have Files pinned to the sidebar. This doesn't
  happen if the first window is on the internal drive.

  Reproduction:
   - Open external hard drive in Nautilus window.
   - Focus/click on a non-Nautilus window
   - Click the Files icon in sidebar.

  Expected behaviour:
   - EHDD window brought to focus

  Actual behaviour:
   - New Home Folder window opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 16:30:48 2014
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']
  InstallationDate: Installed on 2014-04-19 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1313132] Re: Nautilus, Ubuntu 14.04 64 bit, Nautilus opens another window instead to use that window which is allready open

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Nautilus,Ubuntu 14.04 64 bit, Nautilus opens another window instead to
  use that window which is allready open

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Hey Ubuntu Team

  i Use Ubuntu 14.04 64 bit and my problem is if i open nautilus from
  Unity  and minimize + maximize

  nautilus within my home directory but if i minimize  maximize nautilus
  during i´ another partion it opens

  second  nautilus window instead to use the nautilus windows which is
  allready open/minimize + maximize

  1.Nautilus works fine if you want to use minimize or maximize  or get
  nautilus back to foreground

  2.Nautilus/file version is 3.10.1

  3.what i expect was if maximize nautilus/files again

  3.no  matter where that´s only open one window instead a seconde one

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 26 16:37:02 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2014-04-24 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1295794] Re: nautilus opens a new window if clicked on its unity icon even when another nautilus window is open with ntfs drive folder open

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  nautilus opens a new window if clicked on its unity icon even when
  another nautilus window is open with ntfs drive folder open

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I could not make the title shorter and clearer, please forgive.

  How to reproduce this bug:

  On a freshly booted system running Ubuntu 14.04 having unity as its
  desktop-manager and having at least one NTFS partition on its internal
  hard disk, do the following:

  1) Open a nautilus window and mount an NTFS partition and keep any of the 
folders on the NTFS partition open in this window.
  2) Now open any other application(I opened firefox) and then go back to the 
nautilus window by pressing on nautilus' unity icon(which should have a small 
arrow to the left of the nautilus icon, indicating it is already open). Do not 
use Alt+Tab to go back to nautilus- this works fine.

  3) This will open a new nautilus window with the home folder(or
  whichever is the default path to open when a new nautilus window is
  opened) and bring the originally opened folder on the NTFS partition.

  What I expected to happen?

  Clicking on an already opened nautilus window will open(bring to
  foreground) the folder on the NTFS partition.

  What actually happened?

  A new window with my home folder as its default opening path, opened,
  giving me two nautilus windows opened.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  Codename: trusty

  
   apt-cache policy nautilus
  nautilus:
Installed: 1:3.10.1-0ubuntu8
Candidate: 1:3.10.1-0ubuntu8
Version table:
   *** 1:3.10.1-0ubuntu8 0
  500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-03-17 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  Package: unity 7.1.2+14.04.20140320.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Tags:  trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1263754] Re: Files in Launcher opens new window instead of restoring minimized trash

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Files in Launcher opens new window instead of restoring minimized
  trash

Status in “unity” package in Ubuntu:
  New

Bug description:
  I could reproduce this bug on my two computers with 13.10

  I'm not sure if this problem is related to Nautilus or the Launcher.

  Instructions :

  1. Open the Trash via the Launcher

   Comment : the active arrow in the Launcher appears on Files
  instead of Trash

  2. Minimize the window

   Comment : hmm, if I want to make it reappear, which of the two
  icons should I click?

  3. a) Clicking the Files icon, which is shown as active, opens a new
  Files window

   b) Clicking the trash icon, which is shown as inactive, opens the
  Trash

  What is expected?

   1. The Trash icon, not the Files icon, should be shown as active

  OR

   2. The Files icon, which is shown as active, should restore the
  Trash window instead of opening a new Home window

  Further information

   1. I could replicate the same bug by opening Nautilus and going
  to the trash in step 1

   2. Although I haven't tried it, I remember to have experienced a
  similar bug with the folder of an external storage (e.g. USB key)

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

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

[Touch-packages] [Bug 1189102] Re: Nautilus is left behind the opened window as if the app haven't been started

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Nautilus is left behind the opened window as if the app haven't been
  started

Status in “unity” package in Ubuntu:
  New

Bug description:
  I dropped a folder on the VLC icon in the Unity launcher. VLC started
  and the audio files in the folder started playing. However, if you
  click the Nautilus launcher icon in that moment, the program is
  started again as if it hasn't been started before. If you minimize all
  the other windows (the VLC one and the new Nautilus one), you'll find
  out that the first Nautilus window (with the folder which contained
  the audio files) is actually there.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  Date: Sun Jun  9 11:26:44 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'1437x899+65+24'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'218'
  InstallationDate: Installed on 2013-06-04 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1228595] Re: Launcher opens a new window if nautilus was opened on a mount position

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Launcher opens a new window if nautilus was opened on a mount position

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I'm running ubuntu 13.04.

  Steps to reproduce the bug:
  - Open nautilus
  - Navigate to a mounted filesystem (e.g. a NTFS partition or a USB drive)
  - Open another program at fullscreen (hiding nautilus)
  - Click on nautilus icon on Launcher to restore previous opened nautilus 
window

  What happens:
  - A new nautilus window opens

  What should happen:
  - Previous opened windows reappears.

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

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

[Touch-packages] [Bug 1239713] Re: When I click on files icon in unity launcher, new nautilus window open but minimized window doesn't restore

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  When I click on files icon in unity launcher, new nautilus window open
  but minimized window doesn't restore

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  First I open nautilus by clicking Files icon in unity launcher. Then I
  minimize it by clicking minimize button in title bar. Then, as I
  mentioned in summery, When I click on files icon in unity launcher,
  new nautilus window open but minimized window doesn't restore. And
  then I click files icon again. Then two windows appear as overview.
  (with close button) It doesn't happen every time.

  Im using Ubutnu 13.04, 32bit version. (update regularly)
  unity:
    Installed: 7.0.0daily13.06.19~13.04-0ubuntu1
    Candidate: 7.0.0daily13.06.19~13.04-0ubuntu1
    Version table:
   *** 7.0.0daily13.06.19~13.04-0ubuntu1 0
  500 http://lk.archive.ubuntu.com/ubuntu/ raring-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   7.0.0daily13.04.18~13.04-0ubuntu1 0
  500 http://lk.archive.ubuntu.com/ubuntu/ raring/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Oct 14 19:26:24 2013
  InstallationDate: Installed on 2013-08-15 (60 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MarkForUpload: True
  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/1239713/+subscriptions

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

[Touch-packages] [Bug 1188564] Re: Launcher doesn't restore Files window properly

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Launcher doesn't restore Files window properly

Status in “unity” package in Ubuntu:
  New

Bug description:
  When I minimize Files after navigating to a location on a mounted
  (non-root) filesystem, I can't restore it by clicking its icon on the
  Launcher. Instead, a new Files window comes up. I can still access all
  the windows through Alt + Tab.

  Steps to reproduce:
  1. Open Files
  2. Navigate to a mounted filesystem (a pendrive, for example)
  3. Minimize Files
  4. Click Files icon on the Launcher

  What should happen:
  Files window should get restored

  What happens:
  A new Files window comes up, the other is still open, but inaccessible 
through Launcher

  I've recorder a video showing the bug:
  https://www.youtube.com/watch?v=l4eviPA84t8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun  7 12:13:46 2013
  InstallationDate: Installed on 2013-05-24 (13 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  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/1188564/+subscriptions

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

[Touch-packages] [Bug 1184414] Re: Opening Nautilus via Launcher opens another Window

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Opening Nautilus via Launcher opens another Window

Status in “unity” package in Ubuntu:
  New

Bug description:
  When I try to open the current Nautilus Window using the File Manager
  after selecting a folder outside of the Home Folder it will open
  another Window instead of using the current one. I have made a video
  explaining the odd behavior easier:

  http://www.youtube.com/watch?v=0J9aE1zh7No

  Ubuntu 13.04 64 Bit

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.23  Thu May 16 19:36:02 
PDT 2013
   GCC version:  gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May 26 15:41:04 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Device [19da:2227]
  InstallationDate: Installed on 2013-04-28 (28 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-generic 
root=UUID=1fcf3513-f7b6-4c1c-94c7-033a920ad6ee ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DBZ6810H.86A.0043.2012.0615.2054
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DZ68DB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG27985-104
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDBZ6810H.86A.0043.2012.0615.2054:bd06/15/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ68DB:rvrAAG27985-104:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.45+git20130516.acfbf394-0ubuntu0sarvatt~raring
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.2.0~git20130521.b2938156-0ubuntu0sarvatt~raring
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.2.0~git20130521.b2938156-0ubuntu0sarvatt~raring
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.1.99+git20130315.3e5350be-0ubuntu0sarvatt
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.21.7+git20130521.abe85add-0ubuntu0sarvatt~raring
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7+git20130516.bf72ae1f-0ubuntu0sarvatt~raring
  xserver.bootTime: Sat May 25 00:10:15 2013
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring

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

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

[Touch-packages] [Bug 1185921] Re: Unity Launcher opens new window if current window is from a partition other than the root's partition

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Unity Launcher opens new window if current window is from a partition
  other than the root's partition

Status in “unity” package in Ubuntu:
  New

Bug description:
  If a folder from a removable media is currently open in Files,
  clicking Files in Unity Launcher opens Home in a new window instead of
  just bringing up the current folder.

  Expected: if a window is currently open in Files, bring it to focus
  instead of opening home folder in a new window.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu May 30 19:39:20 2013
  InstallationDate: Installed on 2013-01-22 (128 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-05-02 (27 days ago)

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

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

[Touch-packages] [Bug 1228588] Re: unity makes confusion when trying to focus partitions' folders

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  unity makes confusion when trying to focus partitions' folders

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce
  version 1:workspaces disabled
  Open gedit
  Click on a partition icon on the launcher
  You see nautilus windows appears, a white arrow appears alongside of Files 
icon and both the icon of the volume you clicked on and the File's one have a 
backlight.
  Focus gedit
  I see the white arrow is alongside of the Files icon, so if I want to focus 
the partition's folder I should click on it. I do it
  Expected result
  Unity focuses the partition's folder
  What happens instead
  Damn! It opens a new File window in my home folder, but if I click on the 
partition icon it works... ok, I can get used to it, even if it's a bit 
confusing...

  
  version 2:workspaces enabled
  Click on a partition icon on the launcher
  You see nautilus windows appears, a white arrow appears alongside of Files 
icon and both the icon of the volume you clicked on and the File's one have a 
backlight.
  Switch to another workspace
  I want to focus the partition's folder in the other workspace, as in the 
previous case I see the arrow alongside File's icon and I click on it
  Expected result
  Unity switches to the correct workspace and focuses the partition's folder
  What happens:
  It opens a new File's window in my home folder. Ok ok, I have to click on the 
partition's icon. I do it.
  Expected result #2
  Unity switches to the correct workspace and focuses the partition's folder
  What happens #2
  What!? The File icon wiggles and its edge becomes illuminated? Nothing else? 
Do I really have to manually switch to the correct workspace and then click on 
the correct icon? I can't realize a convenient way to focus the window on the 
other workspace without doing it manually (which is not comfortable)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130920-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Sep 21 13:58:02 2013
  InstallationDate: Installed on 2013-06-20 (93 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  SystemImageInfo: Error: [Errno 2] File o directory non esistente: 
'system-image-cli'
  UpgradeStatus: Upgraded to saucy on 2013-07-23 (60 days ago)

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

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

[Touch-packages] [Bug 1239766] Re: nautilus unity launcher opens a new window instead of bringing up the old one.

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  nautilus unity launcher opens a new window instead of bringing up the
  old one.

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Nautilus / Files unity panel's launcher icon opens a brand new window
  when the already opened window is hidden/not activated or minimized
  instead of bringing the old inactive/minimized window to front/active.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 14 17:32:29 2013
  DistUpgraded: 2013-09-29 08:50:42,822 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.2.16, 3.11.0-11-generic, x86_64: installed
   virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed
   virtualbox, 4.2.16, 3.11.0-9-generic, x86_64: installed
   virtualbox, 4.2.16, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
  InstallationDate: Installed on 2013-04-23 (173 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420)
  MachineType: ASUSTeK Computer Inc. UL30A
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=20adce5a-5384-4f57-8041-642feefdfd76 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to saucy on 2013-09-29 (15 days ago)
  dmi.bios.date: 08/20/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UL30A
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd08/20/2009:svnASUSTeKComputerInc.:pnUL30A:pvr1.0:rvnASUSTeKComputerInc.:rnUL30A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UL30A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Oct 13 20:17:04 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4140 
   vendor AUO
  xserver.version: 2:1.14.3-3ubuntu1

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

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

[Touch-packages] [Bug 1176104] Re: Nautilus launcher opens 2 windows before getting focusing on the current open one

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Nautilus launcher opens 2 windows before getting focusing on the
  current open one

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  If Nautilus is open on a location that is not '~' , when clicking the
  launcher on the unity laucher bar it opens '~' when it should focus on
  the already opened window.

  When 2 windows are open, it will focus on the last used one instead of
  launching a new Nautilus instance.

  This is a bit confusing. Why does it open a new Nautilus instance when
  I have 1 aready open? Why does it not open a new instance when I have
  2?

  Description:

  Nautilus opens a 2nd instance when the location of the first instance is not 
the user's home, will focus on the already opened instance if it is.
  Nautilus does not reproduce the same behaviour if there are already 2 
instances open, it will focus on the last used instance instead, no matter the 
current location of any of the instances.

  Desired behaviour:

  If a Nautilus instance is already running it should focus on that
  instance no matter the current location that instance is at the moment
  you click the launcher or open the last focused (used) Nautilus
  window. Fifefox does not open a new window if the current tab is not
  the default home page does it? It just opens the one you are already
  using. Why would Nautilus do it then? If I need another Nautilus
  window I can right click and select a quick shortcut to a location.

  Description:  Ubuntu 13.04
  Release:  13.04

  unity:
Installed: 7.0.0daily13.04.18~13.04-0ubuntu1
Candidate: 7.0.0daily13.04.18~13.04-0ubuntu1
Version table:
   *** 7.0.0daily13.04.18~13.04-0ubuntu1 0
  500 http://nl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri May  3 18:19:15 2013
  InstallationDate: Installed on 2013-05-02 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  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/1176104/+subscriptions

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

[Touch-packages] [Bug 1168771] Re: Clicking a previously opened Files window in Unity launcher causes another window to open

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Clicking a previously opened Files window in Unity launcher causes
  another window to open

Status in “unity” package in Ubuntu:
  New

Bug description:
  This behaviour started when I upgraded to 13.04 beta.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.04.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
  Uname: Linux 3.8.0-10-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Apr 13 17:35:31 2013
  InstallationDate: Installed on 2012-10-19 (176 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-03-06 (38 days ago)

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

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

[Touch-packages] [Bug 1163041] Re: Inconsistent behaviour with minimized Trash windows

[Alberto Salvia Novella]

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

** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Inconsistent behaviour with minimized Trash windows

Status in Ayatana Design:
  Invalid
Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Now with a fix for LP: #753938 being merged into raring, this presents
  a new usability challenge to users.

  The issue:
  When you open a trash window from the launcher and minimize it, it gets 
minimized into the Nautilus icon.
  However, a user would then expect to get the window back by clicking the icon 
where the window minimized into in the first place,
  in this case, the Nautilus icon in the launcher.
  Instead, it opens a new Nautilus window.
  The issue here is that trash windows and every other Nautilus window are only 
seperated logically from each other, but not visually.

  The fix:
  When minimizing the trash window, instead of minimizing into the Nautilus 
icon, it should minimize the window into the trash icon in the launcher.
  I'm purely talking about the minimize animation and triangle next to the 
trash icon here.

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

  unity:
    Installiert:   6.12.0daily13.04.01-0ubuntu1
    Installationskandidat: 6.12.0daily13.04.01-0ubuntu1
    Versionstabelle:
   *** 6.12.0daily13.04.01-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.04.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Apr  2 00:23:51 2013
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1173145] Re: Files (Nautilus) windows opens twice when I click on launcher icon

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 1163041
   Inconsistent behaviour with minimized Trash windows
** This bug has been marked a duplicate of bug 1170647
   Clicking on Nautilus’ launcher icon opens new window instead of restoring 
the minimized one when browsing external drives/locations

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

Title:
  Files (Nautilus) windows opens twice when I click on launcher icon

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
   Description: Ubuntu 13.04
   Release: 13.04

  apt-cache policy unity
  unity:
Installed: 7.0.0daily13.04.18~13.04-0ubuntu1
Candidate: 7.0.0daily13.04.18~13.04-0ubuntu1
Version table:
   *** 7.0.0daily13.04.18~13.04-0ubuntu1 0
  500 http://gr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  When I have an open Files (Nautilus) window in the background clicking
  its icon from the launcher to bring it forward, it open an other
  window...

  I've made a video to help you better understand the problem... 
http://www.youtube.com/watch?v=lLNM-AQLBh4
  The behavior is not deterministic!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr 26 14:18:28 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.10, 3.8.0-19-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:ff50]
 Subsystem: Toshiba America Info Systems Device [1179:ff50]
  InstallationDate: Installed on 2013-04-25 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: TOSHIBA PORTEGE M800
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic 
root=UUID=f28bf536-d3a5-4c5b-866e-a19a9de20fb8 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V5.00
  dmi.board.name: PORTEGE M800
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.00:bd10/26/2010:svnTOSHIBA:pnPORTEGEM800:pvrPPM81E-00L00VGE:rvnTOSHIBA:rnPORTEGEM800:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: PORTEGE M800
  dmi.product.version: PPM81E-00L00VGE
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Fri Apr 26 13:16:19 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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

[Touch-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi

[Julian Alarcon]

Hi!

Maybe this can be a workaround:
https://answers.launchpad.net/ubuntu/+question/239371

=
Try:

echo options iwlwifi 11n_disable=1 bt_coex_active=0 power_save=0
auto_agg=0 swcrypto=1 | sudo tee /etc/modprobe.d/iwlwifi.conf 
/dev/null

As one big command. Reboot to test.
=


I also made a change to enable A2DP in my headset. Before, when I switched to 
A2DP it didn't worked.


=
This worked for me:

1) Open /etc/bluetooth/audio.conf

gksudo gedit /etc/bluetooth/audio.conf

2) find Enable =... under [General] and delete Socket fron the list

[General]
Enable = 

3) Add this line:

Disable = Socket

4) Save

5) Restart the bluetooth service

sudo service bluetooth restart

6) Restar pulseaudio for good measure.

pulseaudio -k 
pulseaudio -D

7) Cross Your Fingers and try.

=


Now I can use my Sony SHB50 on Ubuntu with good sound (A2DP) and my WiFi is 
working fine.

My laptop is a Dell 3450

This is my Wifi Card:
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow 
Peak] (rev 34)

This is how PulseAudio detected my bluetooth device:

pacmd list-cards

index: 2
name: bluez_card.94_CE_2C_F8_51_45
driver: module-bluetooth-device.c
owner module: 24
properties:
device.description = SBH50
device.string = 94:CE:2C:F8:51:45
device.api = bluez
device.class = sound
device.bus = bluetooth
device.form_factor = headset
bluez.path = /org/bluez/542/hci0/dev_94_CE_2C_F8_51_45
bluez.class = 0x240404
bluez.name = SBH50
device.icon_name = audio-headset-bluetooth
device.intended_roles = phone
profiles:
hsp: Telefonía Duplex (HSP/HFP) (priority 20, available: 
unknown)
a2dp: Reproducción de Alta Fidelidad (A2DP) (priority 10, 
available: yes)
off: Apagado (priority 0, available: yes)
active profile: a2dp
sinks:
bluez_sink.94_CE_2C_F8_51_45/#4: SBH50
sources:
bluez_sink.94_CE_2C_F8_51_45.monitor/#7: Monitor of SBH50
ports:
headset-output: Auriculares (priority 0, latency offset 0 usec, 
available: yes)
properties:

headset-input: Auriculares (priority 0, latency offset 0 usec, 
available: unknown)
properties:

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

Title:
  Bluetooth does not coexist with WiFi

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  On my system bluetooth and wifi are unusable together. I have a built-
  in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi
  transfers slow to a halt whenever there is BT traffic.

  For example, if I play a music file from another machine through the
  network using a BT headset, only the first few seconds of the file
  will play until the player runs out of buffered data. No further data
  is downloaded. Web pages also do not download, and I even lose
  connection to AP from time to time.

  At the same time, it looks like AFH is trying to work. If I monitor
  the value returned by 'hcitool afh', it changes. But this seems to
  have little effect on connection quality.

  Is this a problem with my hardware, or the AFH implementation? Is
  there a way to force bluetooth to not use the channels in use by WiFi?

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

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

[Touch-packages] [Bug 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)

[Julian Alarcon]

Maybe this is realated to this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725610

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

** Also affects: pulseaudio (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725610
   Importance: Unknown
   Status: Unknown

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

Title:
  Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and
  14.04 (trusty)

Status in Bluez Utilities:
  New
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Debian:
  Unknown

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will show in the PulseAudio mixer
  * After connecting the external speaker to the audio sink, I can also see the 
device in the Play sound through listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose Audio Profile from the context 
menu and try to select High Fidelity Playback (A2DP) as the new profile, I 
get an error message stating failed to change profile to a2dp

  I've already added Enable=Socket in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

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

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

[Touch-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[Alberto Salvia Novella]

** Description changed:

- Sometimes left clicking the nautilus launcher icon doesn't bring up a
- minimized nautilus window. Instead of restoring the window a new
- instance of nautilus is showing up.
+ ***
+  ISSUE 
+ ***
  
- Steps to reproduce:
+ HOW TO REPRODUCE
  
- 1. Open a nautilus window by clicking on the launcher icon.
- 2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
- 3. Minimize the nautilus window.
- 4. Try to bring up that window again by clicking the launcher icon.
+ 1. Connect a removable media to the computer.
+ 2. On the launcher, click on the Files icon.
+ 3. On the left sidebar, click on the removable media icon or the trash.
+ 4. Minimize the window.
+ 5. Click on the Files icon.
  
- What happens:
  
- 1. A new instance (window) of nautilus is opened.
- 2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.
+ EXPECTED BEHAVIOUR
  
- What schould happen:
+ - The Files window to be maximized.
  
- If a nautilus window is already open and minimized clicking the launcher
- icon should bring up that window. This was the behavior of nautilus
- windows in Ubuntu 12.10 (quantal).
  
- Ubuntu 13.04 Raring Ringtail (development branch)
- nautilus 3.6.3-0ubuntu16
- unity 7.0.0daily13.04.18~13.04-0ubuntu1
+ REAL BEHAVIOUR
+ 
+ - A new window is opened.
+ 
+ 
+ RELEVANT DETAILS
+ 
+ - The only way to navigate between windows at this momment is to use the
+ control + tabulation key combination.
+ 
+ 
+ **
+  SOLUTION 
+ **
+ 
+ WORK-AROUND
+ 
+ - On the launcher, left click on the Files icon and select the unlock
+ from Launcher option.
+ 
+ 
+ FIX
+ 
+ - The launcher icon for Files to be treated the same way as if it was
+ unlocked.
+ 
+ 
+ REGRESSION POTENTIAL
+ 
+ - This is a regression from the fix of bug #753938, so this has to be patched 
in a way it fixes both issues.
+ - The proposed fix already does; sacrificing the fact that every time you 
click on the Files icon it won't send the user to its home folder but to the 
latest opened Files window, what was what Unity developers suggested as 
behaviour to the Files icon in the Launched.
+ 
+ 
+ 
+  TECHNICAL INFO 
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
-  b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
-  b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
+  b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
+  b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

** No longer affects: gnome-shell (Ubuntu)

** Summary changed:

- Clicking on Nautilus’ launcher icon opens new window instead of restoring the 
minimized one when browsing external drives/locations
+ After minimizing an external location, clicking on the Files icon on the 
Launcher doesn't restore the minimized window, but opens a new one

** No longer affects: nautilus (Ubuntu)

** No longer affects: bamf (Ubuntu)

** Project changed: nautilus = hundredpapercuts

** No longer affects: hundredpapercuts

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

Title:
  After minimizing an external location, clicking on the Files icon on
  the Launcher doesn't restore the minimized window, but opens a new one

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

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the Files icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the Files icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - The only way to navigate between windows at this moment is to use
  the control + tabulation key combination.

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the Files icon and select the
  unlock from Launcher option.

  FIX

  - The launcher icon for Files to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the Files icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

[Touch-packages] [Bug 1170647] Re: After minimizing an external location, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one

[Alberto Salvia Novella]

It's a usability issue that doesn't limit the functionality of a core
package.

** Description changed:

  ***
-  ISSUE 
+  ISSUE
  ***
  
  HOW TO REPRODUCE
  
  1. Connect a removable media to the computer.
  2. On the launcher, click on the Files icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the Files icon.
  
- 
  EXPECTED BEHAVIOUR
  
  - The Files window to be maximized.
- 
  
  REAL BEHAVIOUR
  
  - A new window is opened.
  
- 
  RELEVANT DETAILS
  
- - The only way to navigate between windows at this momment is to use the
+ - The only way to navigate between windows at this moment is to use the
  control + tabulation key combination.
  
- 
  **
-  SOLUTION 
+  SOLUTION
  **
  
  WORK-AROUND
  
  - On the launcher, left click on the Files icon and select the unlock
  from Launcher option.
  
- 
  FIX
  
  - The launcher icon for Files to be treated the same way as if it was
  unlocked.
  
- 
  REGRESSION POTENTIAL
  
- - This is a regression from the fix of bug #753938, so this has to be patched 
in a way it fixes both issues.
- - The proposed fix already does; sacrificing the fact that every time you 
click on the Files icon it won't send the user to its home folder but to the 
latest opened Files window, what was what Unity developers suggested as 
behaviour to the Files icon in the Launched.
- 
+ - Clicking on the Files icon won't send the user to its home folder,
+ but to the latest opened Files window.
  
  
-  TECHNICAL INFO 
+  TECHNICAL INFO
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

** Tags added: utopic

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: unity (Ubuntu)
   Importance: High = Medium

** Changed in: hundredpapercuts
   Importance: Undecided = Medium

** Changed in: hundredpapercuts
   Status: New = Triaged

** Summary changed:

- After minimizing an external location, clicking on the Files icon on the 
Launcher doesn't restore the minimized window, but opens a new one
+ After minimizing an external media, clicking on the Files icon on the 
Launcher doesn't restore the minimized window, but opens a new one

** Description changed:

  ***
   ISSUE
  ***
  
  HOW TO REPRODUCE
  
  1. Connect a removable media to the computer.
  2. On the launcher, click on the Files icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the Files icon.
  
  EXPECTED BEHAVIOUR
  
  - The Files window to be maximized.
  
  REAL BEHAVIOUR
  
  - A new window is opened.
  
  RELEVANT DETAILS
  
  - The only way to navigate between windows at this moment is to use the
- control + tabulation key combination.
+ control + tabulation key combination, or to click again on the Files
+ icon so windows are exposed.
  
  **
   SOLUTION
  **
  
  WORK-AROUND
  
  - On the launcher, left click on the Files icon and select the unlock
  from Launcher option.
  
  FIX
  
  - The launcher icon for Files to be treated the same way as if it was
  unlocked.
  
  REGRESSION POTENTIAL
  
  - Clicking on the Files icon won't send the user to its home folder,
  but to the latest opened Files window.
  
  
   TECHNICAL INFO
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

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

Title:
  After minimizing an external media, clicking on the Files icon on
  the Launcher doesn't restore the minimized 

[Touch-packages] [Bug 1103833] Re: Wine's icon and description appears for all Windows applications

[Sebastian Thürrschmidt]

Sorry, I forgot to mention that for my workaround (see previous comment)
to function you need shortcut.exe from
http://optimumx.com/downloads.html#Shortcut somewhere in your Wine path
(like windows/system32). This little tool allows you to create, modify
or query Windows shell links (shortcuts) from the command-line. It's
been a useful addition to my Wine toolbox for so long that I forgot it's
not part of Wine itself. It should be (but with a less clumsy DOSish
syntax).

My apologies for the noise.

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

Title:
  Wine's icon and description appears for all Windows applications

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Confirmed
Status in Wine:
  Unknown
Status in “unity” package in Ubuntu:
  Triaged
Status in “wine” package in Ubuntu:
  Triaged

Bug description:
  If I start an application using Crossover (or Wine), the application will 
always be the Wine Logo instead of the application logo. This is the same 
independent of the application being run or using Wine instead of Crossover.
  That makes sense if the application has no logo, but it gets confusing 
running multiple Microsoft Office programs - and all of them have the same logo.
  The hint text for the icon is also Wine Windows Program Loader instead of 
Document 1 - Microsoft Word as it should be.
  Unity does not seem to allow Wine/Crossover to use application icons and 
title text.

  I have confirmed that this issue does NOT occur in Gnome Classic, and
  is only a Unity flaw.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Jan 23 23:37:43 2013
  InstallationDate: Installed on 2012-10-21 (94 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1170647] Re: After minimizing an external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one

[Charles Profitt]

I have the issue in both 14.04 and 14.10. While I find it annoying and
counter intuitive it is easy to work around.

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

Title:
  After minimizing an external media, clicking on the Files icon on
  the Launcher doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the Files icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the Files icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - The only way to navigate between windows at this moment is to use
  the control + tabulation key combination, or to click again on the
  Files icon so windows are exposed.

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the Files icon and select the
  unlock from Launcher option.

  FIX

  - The launcher icon for Files to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the Files icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

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

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

[Touch-packages] [Bug 1170647] Re: After minimizing an external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one

[Alberto Salvia Novella]

The root problem of this bug is at the design level:

Unity developers thought users would understand better the Files icon
as the place where their personal files are located, rather than the
files manager itself. But, since this icon also needed to command the
files manager, this design created both a duality in functionality and
confusion in how the user shall understand the icon; as its meaning
changes depending on the situation.

So the fix is simply to make the icon mean the files manager under every
circumstance, not the user's home folder: to make the icon behave
equally as when it isn't locked into the launcher.

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

Title:
  After minimizing an external media, clicking on the Files icon on
  the Launcher doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the Files icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the Files icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - The only way to navigate between windows at this moment is to use
  the control + tabulation key combination, or to click again on the
  Files icon so windows are exposed.

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the Files icon and select the
  unlock from Launcher option.

  FIX

  - The launcher icon for Files to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the Files icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

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

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

[Touch-packages] [Bug 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)

[Bug Watch Updater]

** Changed in: pulseaudio (Debian)
   Status: Unknown = Fix Released

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

Title:
  Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and
  14.04 (trusty)

Status in Bluez Utilities:
  New
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will show in the PulseAudio mixer
  * After connecting the external speaker to the audio sink, I can also see the 
device in the Play sound through listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose Audio Profile from the context 
menu and try to select High Fidelity Playback (A2DP) as the new profile, I 
get an error message stating failed to change profile to a2dp

  I've already added Enable=Socket in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

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

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

[Touch-packages] [Bug 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

[Raymond]

seem you are not using latest alsa driver

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=f1e762ddc8035f803d15f8c524151bf788482ec2


Simple mixer control 'Input Source',0
  Capabilities: cenum
  Items: 'Front Mic' 'Rear Mic' 'Line'
  Item0: 'Rear Mic'
Simple mixer control 'Input Source',1
  Capabilities: cenum
  Items: 'Front Mic' 'Rear Mic' 'Line'
  Item0: 'Rear Mic'
Simple mixer control 'Loopback Mixing',0
  Capabilities: enum
  Items: 'Disabled' 'Enabled'
  Item0: 'Disabled'


Node 0x1e [Audio Selector] wcaps 0x300501: Stereo
  Power states:  D0 D1 D2 D3
  Power: setting=D0, actual=D0
  Connection: 6
 0x2c 0x2b* 0x2a 0x29 0x28 0x21


most via codecs able to record the playing signal by select stereo mix ( node 
0x21) 


Node 0x21 [Audio Mixer] wcaps 0x20050b: Stereo Amp-In
  Control: name=Front Mic Playback Volume, index=0, device=0
ControlAmp: chs=3, dir=In, idx=3, ofs=0
  Control: name=Front Mic Playback Switch, index=0, device=0
ControlAmp: chs=3, dir=In, idx=3, ofs=0
  Control: name=Rear Mic Playback Volume, index=0, device=0
ControlAmp: chs=3, dir=In, idx=1, ofs=0
  Control: name=Rear Mic Playback Switch, index=0, device=0
ControlAmp: chs=3, dir=In, idx=1, ofs=0
  Control: name=Line Playback Volume, index=0, device=0
ControlAmp: chs=3, dir=In, idx=2, ofs=0
  Control: name=Line Playback Switch, index=0, device=0
ControlAmp: chs=3, dir=In, idx=2, ofs=0
  Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x80 0x80] [0x1f 0x1f] [0x81 0x81] [0x80 0x80] [0x80 0x80]
  Power states:  D0 D1 D2 D3
  Power: setting=D0, actual=D0
  Connection: 5
 0x2c 0x2b 0x2a 0x29 0x28
  In-driver Connection: 6
 0x2c 0x2b 0x2a 0x29 0x28 0x08


node 0x08 is the audio output

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

Title:
  [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  The problem is that the microphone is not detected after a reboot.  As
  a result, some applications cannot get sound from the microphone.

  The Input tab of the Sound window lists no device.

  I have a workround which is to disconnect and then connect the
  microphone after I have logged in.

  Interestingly, the audacity application can access the microphone when
  the system says that the device does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  5 00:12:39 2014
  InstallationDate: Installed on 2011-07-29 (1133 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No sound at all
  Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1328744] Re: Trusty: x264 not built with lavf or ffms support

[truant]

I mean seriously ubuntu, wtf is going on with the crippled
x264/ffmpeg/libavcodec/etc in 14.04?

Literally all my video processing scripts are broken now.

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

Title:
  Trusty: x264 not built with lavf or ffms support

Status in “x264” package in Ubuntu:
  Confirmed

Bug description:
  The current x264 in Trusty (version 2:0.142.2389+git956c8d8-2) is not
  build with lavf or ffms support:

  djcj: ~ $ x264 --help
  x264 core:142 r2389 956c8d8
  Syntax: x264 [options] -o outfile infile

  Infile can be raw (in which case resolution is required),
or YUV4MPEG (*.y4m),
or Avisynth if compiled with support (yes).
or libav* formats if compiled with lavf support (no) or ffms support (no).

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

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

[Touch-packages] [Bug 1317449] Re: sqlite3 version 3.8.2 breaks digikam

[Chris Samuel]

I applied the patch that b3nmore mentions in comment #126 to sqlite3
from Trusty and built my own packages which I installed but sadly
Digikam still crashes with that applied. :-(

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

Title:
  sqlite3 version 3.8.2 breaks digikam

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

Bug description:
  Please update sqlite to a version  3.8.2.

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

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

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

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

[Touch-packages] [Bug 1374898] [NEW] Vim has 32-bitlimits; annoying on really large files and 64-bit machine

[Kevin O'Gorman]

Public bug reported:

I have a program that I'm debugging.  It generates enormous log files
which I need to peruse.  I use vim as the tool of choice ordinarily, but
vim stops loading the text when it reaches line 2147483647.  That sounds
familiar.

It gives no hint of what's wrong, so I tried several times.  Then I
noticed the line number of the last line it would show.

This makes vim useless for the purpose.
I regard the limit as an implementation limit which I hope you will extend.  I 
regard the failure to report as a bug which ought to be fixed.  I hope you 
agree.

Requests:
 - On a 64-bit machine it would be nice if that were a 64-bit long long.
 - On any machine it would be nice if vim noticed it had failed and reported 
that fact.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vim-gtk 2:7.4.052-1ubuntu3
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.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Sep 27 19:56:34 2014
InstallationDate: Installed on 2014-08-11 (47 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Vim has 32-bitlimits; annoying on really large files and 64-bit
  machine

Status in “vim” package in Ubuntu:
  New

Bug description:
  I have a program that I'm debugging.  It generates enormous log files
  which I need to peruse.  I use vim as the tool of choice ordinarily,
  but vim stops loading the text when it reaches line 2147483647.  That
  sounds familiar.

  It gives no hint of what's wrong, so I tried several times.  Then I
  noticed the line number of the last line it would show.

  This makes vim useless for the purpose.
  I regard the limit as an implementation limit which I hope you will extend.  
I regard the failure to report as a bug which ought to be fixed.  I hope you 
agree.

  Requests:
   - On a 64-bit machine it would be nice if that were a 64-bit long long.
   - On any machine it would be nice if vim noticed it had failed and reported 
that fact.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: vim-gtk 2:7.4.052-1ubuntu3
  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.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 27 19:56:34 2014
  InstallationDate: Installed on 2014-08-11 (47 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140723)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1365769] Re: [pulseaudio-discuss] [V4 PATCH] module-switch-on-connect: add an argument for conditionally connecting

[Raymond]

 
  
   On a machine without fixed connecting audio devices like internal
   microphone or internal speaker, and when there is no external audio
   devices plugging in, the default source/sink is
alsa_input/alsa_output
   and there is no input devices/output devices listed in the gnome
   sound-setting.

 https://launchpadlibrarian.net/184055917/PulseList.txt

 Seem line in is active port when all ports are not available
 Pulseaudio won't switch away from line in but gnome won't show line in
since it is not plugged

 ports:
 analog-input-microphone-front: Front Microphone (priority 8500, latency
offset 0 usec, available: no)
 properties:
 device.icon_name = audio-input-microphone
 analog-input-microphone-rear: Rear Microphone (priority 8200, latency
offset 0 usec, available: no)
 properties:
 device.icon_name = audio-input-microphone
 analog-input-linein: Line In (priority 8100, latency offset 0 usec,
available: no)
 properties:

 active port: analog-input-linein

 Yes, in this situation, the default-source-active_port-available=no, if
you use this module and pass only_from_unavailable=yes, when connect
bluetooth headset, the default source will automatically switch to
bluez-source.

 In this situation, if you plug something in the line-in jack, the
default-source-active_port-available=yes, and if you pass
only_from_unavailable=yes, the default source will not switch.

 https://launchpadlibrarian.net/184417469/alsa2.txt



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

Ports:
analog-output: Analog Output (priority: 9900)
analog-output-speaker: Speakers (priority: 1)
analog-output-headphones: Headphones (priority: 9000, not available)
Active Port: analog-output-headphones

Even pulseaudio may neglect the Jack state of line out and line in

Select unplugged line out and line in as active port when headphone or Mic
Jack is unplugged

But active port cannot be an unavailable headphone

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

Title:
  [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  The problem is that the microphone is not detected after a reboot.  As
  a result, some applications cannot get sound from the microphone.

  The Input tab of the Sound window lists no device.

  I have a workround which is to disconnect and then connect the
  microphone after I have logged in.

  Interestingly, the audacity application can access the microphone when
  the system says that the device does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  5 00:12:39 2014
  InstallationDate: Installed on 2011-07-29 (1133 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No sound at all
  Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

[Raymond]

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

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

Title:
  [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  The problem is that the microphone is not detected after a reboot.  As
  a result, some applications cannot get sound from the microphone.

  The Input tab of the Sound window lists no device.

  I have a workround which is to disconnect and then connect the
  microphone after I have logged in.

  Interestingly, the audacity application can access the microphone when
  the system says that the device does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  5 00:12:39 2014
  InstallationDate: Installed on 2011-07-29 (1133 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No sound at all
  Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1317449] Re: sqlite3 version 3.8.2 breaks digikam

[Chris Samuel]

I can confirm that Tim Edwards suggestion of installing the sqlite3
packages from Utopic in comment #117 does indeed seem to resolve this
issue.

Before Digikam could crash every few minutes whilst cycling through
photos with just normal viewing.

After Digikam does not crash.

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

Title:
  sqlite3 version 3.8.2 breaks digikam

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

Bug description:
  Please update sqlite to a version  3.8.2.

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

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

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

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

[Touch-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*

[eris23]

Affects Xubuntu 14.10 amd64 when launching ubuntu-tweak.

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

Title:
   Couldn't connect to accessibility bus: Failed to connect to socket
  /tmp/dbus-*

Status in Assistive Technology Service Provider Interface:
  New
Status in “at-spi2-core” package in Ubuntu:
  Confirmed
Status in “at-spi2-core” package in Debian:
  Confirmed

Bug description:
  Since a few days, xsession-errors is fullfilled by that kind of
  errors:

  ** (nautilus:22621): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection
  refused

  ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused

  Similar errors are reported all over the net, but Debian have tried to fix it 
already:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517

  But some other devs seems to blame an atk-bridge:
  https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA

  And some others suggest a dbus/gdbus race; the good thing is that
  seems not disturbing that much the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  Date: Fri Jun 21 08:35:40 2013
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions

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

[Touch-packages] [Bug 1328183] Re: User-Agent string results in poor UX on web

[Shuduo Sang]

I have tried to override UA with user-agent-override: Mozilla/5.0 
custom-user-agent-string (unlike AnyOtheBrowser)
in the webapp-properties.json file as David Barth suggests. First problem is 
'click build .' command do not package webapp-properties.json into click 
package as result. Then I manually copy it into the place of installed 
application directory of /opt. But the UA string I get from http://myhttp.info 
is still original mobile version.

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

Title:
  User-Agent string results in poor UX on web

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

Bug description:
  The User-Agent string for the browser is similar enough to the Android
  browser User-Agent, that it creates a poor experience when browsing
  the web on an Ubuntu phone. An inordinately large number of web sites
  persistently advertise to install our app instead of providing the
  best web experience; an app which cannot be installed.

  This is exacerbated by the pervasiveness of webapps on Ubuntu phone,
  which simply embed the mobile web site with webapp-container, and
  still result in seeing such advertisements, despite the fact that the
  app on Ubuntu is already installed, and the Android apps being
  advertised are simply not installable.

  Having all the big web sites telling users of Ubuntu that they should
  be using Android instead, is not very good for the user experience at
  all.

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

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

[Touch-packages] [Bug 1308667] Re: indicator incoming can be taken out of action from the welcome screen

[Launchpad Bug Tracker]

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

** Changed in: unity8 (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  indicator incoming can be taken out of action from the welcome screen

Status in “telephony-service” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Expired

Bug description:
  PREREQUISITE:
  2 phones

  STEPS:
  1. On the Ubuntu Touch Phone (Phone A) add the other phone (Phone B) as a 
contact
  2. Put Phone A to sleep
  3. Send an sms from Phone B to Phone A
  4. Notice that it very briefly displays SMS from +0123445678999 instead of 
the contact deatials.
  5. Hit the notification for the Incoming SMS
  6. Send another message now and you get no Blue icon, No notification, No Ping

  2 things might be happening here from what I can tell so far:
  1. The indicator dies and is in the midst of a restart when the second text 
comes through (no crash log for indicators just one of the only things I can 
think of)
  2. Something is broken in the interaction of the sms system (Possibly 
relating to The QT bug)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.85+14.04.20140415.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: armhf
  Date: Wed Apr 16 18:06:06 2014
  InstallationDate: Installed on 2014-04-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140416.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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