[Touch-packages] [Bug 1595177] Re: [SRU] Update apt/xenial to 1.2.14

[Bruno Nova]

I've updated apt to 1.2.14 and it seems to be working OK.
I ran a dist-upgrade after several days without updating, and all is well.

Bash autocompletion is also more complete now (LP: #1598384 and LP:
#1573547).

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

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

Title:
  [SRU] Update apt/xenial to 1.2.14

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  (This is a template for now, so I can close the bug in the 1.2.14
  upload)

  [Impact]
  We intend to upload APT 1.2.14 to xenial under the new "micro upstream 
release" policy.

  Apart from fixing bug 1573547, it also updates translations fixes the
  following other bugs:

  [[1.2.13]]

  Segmentation fault fixes:
  * fail instead of segfault on unreadable config files (Closes: 824503)

  Fixes for 3rd party programs using libapt and C++ locale API:
  * prevent C++ locale number formatting in text APIs (Closes: #825396)

  Fix for hurd (not really affecting us here, but upstream):
  * apt-key: change to / before find to satisfy its CWD needs.
    Thanks to Samuel Thibault for 'finding' the culprit! (Closes: 826043)

  Leak fixes:
  * do not hang on piped input in PipedFileFdPrivate
  * don't leak an FD in lz4 (de)compression
  * don't leak FD in AutoProxyDetect command return parsing

  [[1.2.14]]
  Regression fix from 1.2.13:
    * do not error if auto-detect-proxy cmd has no output (Closes: 827713)
  Huge apt-ftparchive performance regression fix from 1.1:
    * Reinstate caching of file hashes in apt-ftparchive (Closes: #806924)
  Tiny bug fixes, about 2 lines each:
    * source: if download is skipped, don't try to unpack
    * ensure filesize of deb is included in the hashes list

  [Test case]
  The releases follow new upstream micro release rule and thus are assumed to 
be tested by our integration test suite. There are two exceptions which cannot 
be tested:

  * prevent C++ locale number formatting in text APIs
  * apt-key: change to / before find to satisfy its CWD needs

  The first has no affected code in the archive (but maybe 3rd party
  code), the second only affects hurd.

  [Regression Potential]
  Very low. The release has been tested by a thorough integration test suite on 
Travis CI, Debian autopkgtests, and has been in Debian unstable since 
2016-06-22.

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

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

[Touch-packages] [Bug 1598384] Re: [Wishlist] apt command: add more subcommands to autocomplete, help and manpage

[Bruno Nova]

Great! Thanks for the explanation and for the link!

I think this bug can now be marked as invalid, or as a duplicate of Bug
#1573547.

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

Title:
  [Wishlist] apt command: add more subcommands to autocomplete, help and
  manpage

Status in apt package in Ubuntu:
  Opinion

Bug description:
  It seems has a lot more subcommands than those listed in the manpage or the 
help message.
  For example, "download", "policy", "changelog" and "dist-upgrade" all work, 
and they aren't listed.
  Maybe apt supports all subcommands from apt-get and apt-cache?

  However those subcommands aren't listed in the manpage or the help message.
  They also don't have autocomplete, which makes using them a pain, and makes 
me use apt-get and apt-cache instead.

  It would be great if all those subcommand were listed in the manpage
  and help message, and if there was autocomplete for them!

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

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

[Touch-packages] [Bug 1598384] [NEW] [Wishlist] apt command: add more subcommands to autocomplete, help and manpage

[Bruno Nova]

Public bug reported:

It seems has a lot more subcommands than those listed in the manpage or the 
help message.
For example, "download", "policy", "changelog" and "dist-upgrade" all work, and 
they aren't listed.
Maybe apt supports all subcommands from apt-get and apt-cache?

However those subcommands aren't listed in the manpage or the help message.
They also don't have autocomplete, which makes using them a pain, and makes me 
use apt-get and apt-cache instead.

It would be great if all those subcommand were listed in the manpage and
help message, and if there was autocomplete for them!

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

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

Title:
  [Wishlist] apt command: add more subcommands to autocomplete, help and
  manpage

Status in apt package in Ubuntu:
  New

Bug description:
  It seems has a lot more subcommands than those listed in the manpage or the 
help message.
  For example, "download", "policy", "changelog" and "dist-upgrade" all work, 
and they aren't listed.
  Maybe apt supports all subcommands from apt-get and apt-cache?

  However those subcommands aren't listed in the manpage or the help message.
  They also don't have autocomplete, which makes using them a pain, and makes 
me use apt-get and apt-cache instead.

  It would be great if all those subcommand were listed in the manpage
  and help message, and if there was autocomplete for them!

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Bruno Nova]

Thank you people! My printer now works perfectly!

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1593407] Re: Guest session cannot run snaps

[Bruno Nova]

Yes, I know. I was referring to LightDM's guest session AppArmor profile.
I'll edit the description.

I only linked the bug to snapd to make it known to Snappy developers, and 
because the bug affects it.
The actual fix probably has to be made in that LightDM profile. So, sooner or 
later, the status for snapd should be changed to Invalid.

** Description changed:

  I'm using Ubuntu 16.04.
  
  The guest session cannot execute snaps, because of a permission error.
- The AppArmor profile is not allowing access to /snap and other needed files 
and folders.
+ The LightDM's guest session AppArmor profile is not allowing access to /snap 
and other needed files and folders.

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

Title:
  Guest session cannot run snaps

Status in lightdm package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04.

  The guest session cannot execute snaps, because of a permission error.
  The LightDM's guest session AppArmor profile is not allowing access to /snap 
and other needed files and folders.

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

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

[Touch-packages] [Bug 1593407] [NEW] Guest session cannot run snaps

[Bruno Nova]

Public bug reported:

I'm using Ubuntu 16.04.

The guest session cannot execute snaps, because of a permission error.
The AppArmor profile is not allowing access to /snap and other needed files and 
folders.

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

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


** Tags: xenial

** Also affects: snapd (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/1593407

Title:
  Guest session cannot run snaps

Status in lightdm package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04.

  The guest session cannot execute snaps, because of a permission error.
  The AppArmor profile is not allowing access to /snap and other needed files 
and folders.

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

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

[Touch-packages] [Bug 1574792] Re: sound devices disappear from sound settings

[Bruno Nova]

It seems my issue may be due to Firejail.
Here's a bug report in Firejail: https://github.com/netblue30/firejail/issues/69
There's also this one in Launchpad: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1572493

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

Title:
  sound devices disappear from sound settings

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound devices disappear from the sound settings however sound is still 
working.
  pulseaudio --kill pulse audio --start restore them back to the sound 
settings. In rear cases, it cannot be started "daemon startup failed".
  This can happen at any time without a reason, also sometimes happen when 
plugging headphones or connecting bluetooth speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 01:02:04 2016
  InstallationDate: Installed on 2016-04-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.0-6588-g4acd8ea-dirty
  dmi.board.name: Peppy
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr4.0-6588-g4acd8ea-dirty:bd09/04/2014:svnGOOGLE:pnPeppy:pvr1.0:rvnGOOGLE:rnPeppy:rvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime doesn't list in-progress events

[Bruno Nova]

This wasn't fixed in 16.04 and 14.04 yet, right?

By the way, for those interested, I already uploaded a "fixed" version
for 16.04 to my PPA I mentioned before.

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

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

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

[Touch-packages] [Bug 1574792] Re: sound devices disappear from sound settings

[Bruno Nova]

This is happening several times per day and is becoming annoying (I lose
sound).

"pulseaudio --kill" fixes the sound ("pulseaudio --start" is not
needed).

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

Title:
  sound devices disappear from sound settings

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound devices disappear from the sound settings however sound is still 
working.
  pulseaudio --kill pulse audio --start restore them back to the sound 
settings. In rear cases, it cannot be started "daemon startup failed".
  This can happen at any time without a reason, also sometimes happen when 
plugging headphones or connecting bluetooth speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 01:02:04 2016
  InstallationDate: Installed on 2016-04-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.0-6588-g4acd8ea-dirty
  dmi.board.name: Peppy
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr4.0-6588-g4acd8ea-dirty:bd09/04/2014:svnGOOGLE:pnPeppy:pvr1.0:rvnGOOGLE:rnPeppy:rvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1574792] Re: sound devices disappear from sound settings

[Bruno Nova]

I'm seeing the same thing.

Every once in a while, the sound devices disappear from the sound settings.
However, for me the sound usually stops working, and then when I open VLC, it 
throws sound errors.

This bug seems to be important.

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

Title:
  sound devices disappear from sound settings

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound devices disappear from the sound settings however sound is still 
working.
  pulseaudio --kill pulse audio --start restore them back to the sound 
settings. In rear cases, it cannot be started "daemon startup failed".
  This can happen at any time without a reason, also sometimes happen when 
plugging headphones or connecting bluetooth speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 01:02:04 2016
  InstallationDate: Installed on 2016-04-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.0-6588-g4acd8ea-dirty
  dmi.board.name: Peppy
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr4.0-6588-g4acd8ea-dirty:bd09/04/2014:svnGOOGLE:pnPeppy:pvr1.0:rvnGOOGLE:rnPeppy:rvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Bruno Nova]

The printer-driver-escpr package also works for my Epson Stylus SX425W
printer.


However, I must say that installing the driver for this printer in 16.04 was 
not user-friendly at all.

The "wizard" for adding and installing the printer didn't present this package 
as a possible driver to install.
The only options were epson-nx420 (which fails to silently install due to the 
missing lsb package), and another one which didn't seem to include the driver I 
needed (I may be wrong).

Also, this package has a LOT LESS "Printer Options" than the epson-nx420
driver.

I had to install this package manually.
I only found it because of this bug report (and Google).

These drivers need to be easier to install, and the "wizard" needs to be more 
robust.
(The guys at the Epson repository should probably also do something about the 
"lsb" dependency, since this probably also affects Debian.)

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Confirmed
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1398180] Re: Error when adding/removing key in KDE version

[Bruno Nova]

That took a while.

If I'm not mistaken, I found this bug while trying to fix another bug in the 
GTK version and decided to test the KDE version in VirtualBox. I then checked 
the code to see where the bug probably was.
That's why I didn't use ubuntu-bug.

I'm using Unity, not KDE, and I have no idea if this bug still exists. And, 
after more that 1 year, I'm still the only one marked as affected.
Maybe it would be better to leave this bug "Incomplete" until it automatically 
turns "Invalid", unless someone else using KDE tests this bug.

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

Title:
  Error when adding/removing key in KDE version

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Discovered this bug in 14.04.

  In the KDE version of software-properties, when I add or remove a key, an 
error about the key being invalid is displayed.
  However, it seems that the key is actually added/removed (checked with 
apt-key).

  The respective methods in softwareproperties/SoftwareProperties.py call the 
KeysModified() method.
  Apparently, this method doesn't exist in the KDE version, causing an 
exception which makes the add/remove methods return False.
  This is the cause of this bug.

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

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

[Touch-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Bruno Nova]

@mniess Great! :)

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

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

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

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

[Touch-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Bruno Nova]

I tested the ibus packages (version 1.5.5-1ubuntu3.2) in a Ubuntu
14.04.3 Live session inside VirtualBox.

Before upgrading the packages, the command:
$ gsettings get org.freedesktop.ibus.general use-system-keoard-layout
returned "false".
After upgrading, it returns "true". "ibus-setup" also displays that the setting 
is enabled.

This setting at "true" should mean the issue is fixed.
But testing if this really fixes "Wrong keyboard layout active after booting" 
is difficult since the bug is very random, and in my computer I already set 
that setting to "true" manually.

I'll mark this as verification-done.
But other people should test this as well (I am the one who sent the fix).
If the fix doesn't work for you, please set the bug as verification-failed (but 
try rebooting first).

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

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

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

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

[Touch-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Bruno Nova]

** Branch linked: lp:~brunonova/ubuntu/trusty/ibus/lp1240198_2

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

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Confirmed
Status in ibus source package in Trusty:
  Triaged

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

I updated the software-properties packages to 0.92.37.5 from trusty-
proposed.

The bug is fixed!
I opened my own PGP key (I already have the VLC's key) in gedit and dragged 
everything into the authentication list. I was asked for polkit authorization 
and then the key was successfully added.

** 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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1383289

Title:
  Dropping a key into the list of keys fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Dragging a key into Software & Updates' authentication tab does
  nothing.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  3. Open the PGP key file you downloaded with a text editor.
  4. Select all of the text (Ctrl+A) and drag it into the list in the
 Authentication tab of Software & Updates.

 If the bug is fixed: admin authentication is requested. Authenticate,
 and then the key should be listed.
 If not: nothing happens, or an error is displayed.

  [Regression Potential]

  This feature isn't working, so I suppose there is not regression
  potential.

  [Original Report]

  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

I added a comment to the merge request.

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Regression Potential]

  If the fix is not correct, I suppose it could potentially break the
  "import key" feature even more, so it wouldn't work even in "normal"
  paths.

  [Original Report]

  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
    _("Error importing selected file"),
    _("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 183729] Re: compat: utmp not cleared on tty logout

[Bruno Nova]

Are you sure this is fixed?
I'm seeing this exact bug in Trusty. Logging out of a TTY doesn't lower the 
number of users in uptime, w, etc.

Now, Vivid switched to systemd, so if the bug is really in upstart, it may not 
be worth wasting time here.
But, Trusty is an LTS... so, I don't know.

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

Title:
  compat: utmp not cleared on tty logout

Status in upstart :
  Fix Released
Status in kdebase-workspace package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart package in Fedora:
  In Progress

Bug description:
  Log into tty1, then tty2 and then log out of both.  Now run a w
  command and you should see something similar to the following;

  mac@tootoo:~/source/procps-3.2.7/proc$ w
   10:39:09 up 33 days, 23:11,  4 users,  load average: 1.31, 0.62, 0.39
  USER TTY  FROM  LOGIN@   IDLE   JCPU   PCPU WHAT
  mac tty7 :0   11Jan08  4:34m  7:24m 36.02s 
x-session-manager
  mac pts/1:0.0 08:540.00s  0.19s  0.00s w

  It shows that 4 users are logged in.  Obviously this is wrong.  I
  wrote a small C utility to hack out what w and uptime get as
  information from utmp.

  
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char *argv[])
  {
struct utmp *utmpstruct;
struct utmp entry;

//system("echo before adding entry:;who");

setutent();
//pututline(&entry);
while ((utmpstruct = getutent())){
  if ((utmpstruct->ut_type == USER_PROCESS) && (utmpstruct->ut_name[0] 
!= '\0'))
  printf(utmpstruct->ut_line);
  printf("\t");
  printf("%d",utmpstruct->ut_pid);
  printf("\n");
}
endutent();
return 0;
  }

  You'll get an output like this

  mac@tootoo:~$ ./a.out 
  0
  50
  4305
  4306
  tty214989
  4312
  tty14313
  4314
  tty730255
  0
  pts/1   9712
  0
  0
  0
  0
  0
  20929
  14914
  15034

  However, running the following , to try to find the pid for the tty1
  process, gives;

  mac@tootoo:~/source/procps-3.2.7/proc$ ps aux | grep 4313
  mac 15524  0.0  0.0   2988   768 pts/1R+   10:42   0:00 grep 4313
  mac@tootoo:~/source/procps-3.2.7/proc$ 

  This is obviously wrong, utmp still has the old process id's
  associated as being logged in.

  Running the following gives the new tty pid

  mac@tootoo:~/source/procps-3.2.7/proc$ ps aux | grep tty1
  root 14914  0.0  0.0   1692   516 tty1 Ss+  10:33   0:00 /sbin/getty 
38400 tty1
  mac 15605  0.0  0.0   2988   764 pts/1R+   10:44   0:00 grep tty1
  mac@tootoo:~/source/procps-3.2.7/proc$ 

  There is now a new pid for tty1

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

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime doesn't list in-progress events

[Bruno Nova]

In the meantime while this is not officially fixed, I have uploaded a fixed 
version of the package to a PPA.
The PPA is here: 
https://launchpad.net/~brunonova/+archive/ubuntu/indicator-datetime

The difference between the official version is just the patch that attached to 
this bug, plus the necessary changes to the debian/ files.
I uploaded packages for Trusty and Vivid, but only tested Trusty.

Also, Ubuntu developers: the package is still using the 1.0 source
format? Why not 3.0 (quilt)?

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

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

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

[Touch-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Bruno Nova]

When I was asking if it fixed the issue, I was referring to the
"affected users".

The bug was marked "verification-done" in comment #71 by FM33.
However, e later said in comment #74: "Reproduced again this morning (...)".
Comment #75 also says: "This problem has reappeared yesterday (...)".
They didn't remove the verification tag, so I set it to "verification-needed".
I'm now changing it to "verification-failed". If I misinterpreted the comments, 
please change it back.

@Aron (or someone else), please recheck my merge request 
(https://code.launchpad.net/~brunonova/ubuntu/trusty/ibus/lp1240198/+merge/241742).
The commit in trusty-proposed is missing the important change in 
"debian/ibus.install". Please add that change to trusty-proposed, adapting it 
if necessary.

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

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

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Fix Released
Status in indicator-keyboard package in Ubuntu:
  Won't Fix
Status in ibus source package in Trusty:
  Fix Committed
Status in indicator-keyboard source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

** Branch linked: lp:~brunonova/software-properties/lp1381050_2

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Regression Potential]

  If the fix is not correct, I suppose it could potentially break the
  "import key" feature even more, so it wouldn't work even in "normal"
  paths.

  [Original Report]

  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
    _("Error importing selected file"),
    _("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

I updated to -proposed and tested but, unfortunately, the bug isn't fixed!
The other bug is fixed, though.

Adding a key in "/home/$USER/Transferências" didn't work. Nothing happened 
after authenticating as admin.
However, if I run software-properties-dbus manually (by executing "sudo python3 
/usr/lib/software-properties/software-properties-dbus"), it works.

After further investigation, I would say that software-properties-dbus is 
started in the C locale (non UTF-8), making it fail in paths with special 
characters.
I checked the file "/proc/$software-properties-dbus-PID/environ", and it's 
almost empty. It only contains the variables DBUS_STARTER_ADDRESS and 
DBUS_STARTER_BUS_TYPE, but no locale related variables.

@Michael, that's probably why I said that the fix with your changes worked 
(https://code.launchpad.net/~brunonova/software-properties/lp1381050/+merge/238873/comments/613431).
It seems that your simplification doesn't work after all. :)

@Michael, check the diff here: 
https://code.launchpad.net/~brunonova/software-properties/lp1381050/+merge/238873
Adding that line fixes this bug, I've checked it now.
Do you want to make this change yourself, or shall I do it?

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

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Regression Potential]

  If the fix is not correct, I suppose it could potentially break the
  "import key" feature even more, so it wouldn't work even in "normal"
  paths.

  [Original Report]

  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
    _("Error importing selected file"),
    _("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~tou

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

However, this update doesn't fix the other bug (#1381050) unfortunately,
so this shouldn't be uploaded to trusty-updates!

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

Title:
  Dropping a key into the list of keys fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Dragging a key into Software & Updates' authentication tab does
  nothing.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  3. Open the PGP key file you downloaded with a text editor.
  4. Select all of the text (Ctrl+A) and drag it into the list in the
 Authentication tab of Software & Updates.

 If the bug is fixed: admin authentication is requested. Authenticate,
 and then the key should be listed.
 If not: nothing happens, or an error is displayed.

  [Regression Potential]

  This feature isn't working, so I suppose there is not regression
  potential.

  [Original Report]

  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

I updated software-properties' installed binary packages to the version in 
-proposed, and now dragging a key into the list of keys work.
This fixes this bug!

** 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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1383289

Title:
  Dropping a key into the list of keys fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Dragging a key into Software & Updates' authentication tab does
  nothing.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  3. Open the PGP key file you downloaded with a text editor.
  4. Select all of the text (Ctrl+A) and drag it into the list in the
 Authentication tab of Software & Updates.

 If the bug is fixed: admin authentication is requested. Authenticate,
 and then the key should be listed.
 If not: nothing happens, or an error is displayed.

  [Regression Potential]

  This feature isn't working, so I suppose there is not regression
  potential.

  [Original Report]

  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

** Description changed:

+ [Impact]
+ 
+ Importing a key that is in a path that contains special characters (like
+ "/home/$USER/Transferências") fails silently.
+ 
+ [Test Case]
+ 
+ 1. Download a PGP key for a Debian repository (for example, the VideoLAN
+team's key: download.videolan.org/pub/debian/videolan-apt.asc)
+ 2. Move the key file to a folder that contains special characters, or rename
+the file to contain them (example: VídeoLAN.asc).
+ 3. Open "Software & Updates" from the Dash, then select the Authentication
+tab.
+ 4. Press the "Import Key File..." button and then choose the key file.
+Admin authentication should then be requested, so authenticate yourself.
+ 
+If the bug is fixed: the key should now appear in the list of keys.
+If not: the key was not added.
+ 
+ [Regression Potential]
+ 
+ If the fix is not correct, I suppose it could potentially break the
+ "import key" feature even more, so it wouldn't work even in "normal"
+ paths.
+ 
+ [Original Report]
+ 
  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.
  
  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.
  
  The problem is that, in softwareproperties/gtk/SoftwarePropertiesGtk.py
  in method SoftwarePropertiesGtk.add_key_clicked() at around line 952:
  
- if res == Gtk.ResponseType.ACCEPT:
- try:
- if not self.backend.AddKey(chooser.get_filename()):
- error(self.window_main,
-   _("Error importing selected file"),
-   _("The selected file may not be a GPG key file "
- "or it might be corrupt."))
- except dbus.DBusException as e:
- if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
- logging.error("Authentication canceled, changes have not 
been saved")
+ if res == Gtk.ResponseType.ACCEPT:
+ try:
+ if not self.backend.AddKey(chooser.get_filename()):
+ error(self.window_main,
+   _("Error importing selected file"),
+   _("The selected file may not be a GPG key file "
+ "or it might be corrupt."))
+ except dbus.DBusException as e:
+ if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
+ logging.error("Authentication canceled, changes have not 
been saved")
  
  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).
  
  Another issue is that the error isn't reported to the user, and it
  should be.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  In Progress

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Reg

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

** Description changed:

+ [Impact]
+ 
+ Dragging a key into Software & Updates' authentication tab does nothing.
+ 
+ [Test Case]
+ 
+ 1. Download a PGP key for a Debian repository (for example, the VideoLAN
+team's key: download.videolan.org/pub/debian/videolan-apt.asc)
+ 2. Open "Software & Updates" from the Dash, then select the Authentication
+tab.
+ 3. Open the PGP key file you downloaded with a text editor.
+ 4. Select all of the text (Ctrl+A) and drag it into the list in the
+Authentication tab of Software & Updates.
+ 
+If the bug is fixed: admin authentication is requested. Authenticate,
+and then the key should be listed.
+If not: nothing happens, or an error is displayed.
+ 
+ [Regression Potential]
+ 
+ This feature isn't working, so I suppose there is not regression
+ potential.
+ 
+ [Original Report]
+ 
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug report
  appears), throwing an exception:
  
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Dropping a key into the list of keys fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  In Progress

Bug description:
  [Impact]

  Dragging a key into Software & Updates' authentication tab does
  nothing.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  3. Open the PGP key file you downloaded with a text editor.
  4. Select all of the text (Ctrl+A) and drag it into the list in the
 Authentication tab of Software & Updates.

 If the bug is fixed: admin authentication is requested. Authenticate,
 and then the key should be listed.
 If not: nothing happens, or an error is displayed.

  [Regression Potential]

  This feature isn't working, so I suppose there is not regression
  potential.

  [Original Report]

  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Bruno Nova]

Has the proposed package fixed the issue or not?
FM33 reported in comment #71 that it fixed it, but in comment #74 he says that 
it wasn't fixed after all, I think.

I haven't tested it, but I don't think the proposed package will fix the issue.
>From the diffs, it's missing one important change from my merge request: the 
>line added to "debian/ibus.install" that makes the file 
>"data/dconf/10_ibus.gschema.override" be installed, which is the file that 
>fixes this. Unless there's something else going on.
Could an Ubuntu developer look into this?

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

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Fix Released
Status in indicator-keyboard package in Ubuntu:
  Won't Fix
Status in ibus source package in Trusty:
  Fix Committed
Status in indicator-keyboard source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

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

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

[Touch-packages] [Bug 984916] Re: Java Swing applications do not work with appmenu

[Bruno Nova]

Jayatana is now in the official repositories, right?
So, shouldn't this bug be marked as fixed?

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

Title:
  Java Swing applications do not work with appmenu

Status in Application menu module for GTK+:
  Confirmed
Status in DBus Menu:
  Confirmed
Status in libdbusmenu package in Ubuntu:
  Confirmed

Bug description:
  Bug #618587 tracks integration of appmenu with SWT, but there appears
  to be nothing filed about integration with javax.swing.JMenuBar
  (mentioned at the bottom of bug #659931).

  Expected (at least ideal) behavior: when running Unity and giving
  focus to a JFrame with a JMenuBar, the menu bar is not displayed
  inside the frame, but corresponding menus are displayed in the global
  Unity menu.

  Actual behavior on 11.10: the menu bar is displayed inside the frame,
  and appmenu is empty.

  For comparison, the Mac OS X JRE automatically displays Swing menus in
  the native location. libjava-gnome-java is perhaps the place to put in
  such a fix; assuming the JRE itself is not modified, an application
  wishing to take advantage of the fix would probably need to try to
  load /usr/share/java/gtk.jar and (if present) call a simple "register"
  method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-gtk/+bug/984916/+subscriptions

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime doesn't list in-progress events

[Bruno Nova]

Hi, I checked the updated specification (didn't read everything, but I
think it's good). It will require more changes in the code than just the
patch I provided. :)

But, in the meantime, could the change in the patch be applied and backported 
to Trusty and Vivid?
I applied the patch to my system, and it's working fine, but I would prefer to 
not have to do it.

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

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

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

[Touch-packages] [Bug 1301401] Re: Remove chat support from Windows Live provider

[Bruno Nova]

I think this bug is fixed now, at least for Ubuntu Online Accounts and Empathy.
Check Bug #1432613.

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

Title:
  Remove chat support from Windows Live provider

Status in Chat app, and Telepathy user interface:
  Fix Released
Status in empathy package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  From upstream bug report:

  Microsoft has had been planning to drop Windows Live Messenger in favour of
  Skype for quite some time now. See:
   - http://www.bbc.com/news/technology-20222998
   -
  
http://arstechnica.com/information-technology/2013/01/microsoft-messenger-service-not-going-anywhere-just-yet/

  
--

  eduar@envy4:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  eduar@envy4:~$ apt-cache policy empathy
  empathy:
    Instalados: 3.8.6-0ubuntu7
    Candidato:  3.8.6-0ubuntu7
    Tabla de versión:
   *** 3.8.6-0ubuntu7 0
  500 http://co.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  eduar@envy4:~$ apt-cache policy telepathy-gabble
  telepathy-gabble:
    Instalados: 0.18.2-1
    Candidato:  0.18.2-1
    Tabla de versión:
   *** 0.18.2-1 0
  500 http://co.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Hello all. I'm trying to setup my Windows Live account (@outlook.com)
  in Empathy. It used to work OK on Ubuntu 12.04.4 64 bits. However, in
  14.04 it doesn't works. When I add an account, it asks me for my
  username and password, I give it permissions to access my data, and
  the account is shown OK on the "Online accounts" window. However, when
  I go Online, Empathy shows a wheel in the middle, just turning around,
  but nothing else happens. After a while, it gives me a red error
  message "x...@outlook.com Network error"

  I have the debug in pastebin: http://pastebin.com/8vQdM4Pg

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: empathy 3.8.6-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  2 08:41:58 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-30 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1393523] Re: Windows title bar controls are still active in Expo/Spread mode

[Bruno Nova]

** Summary changed:

- Dragging windows in Expo mode occasionally results in weird behavior
+ Windows title bar controls are still active in Expo/Spread mode

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

Title:
  Windows title bar controls are still active in Expo/Spread mode

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

Bug description:
  There are some times where dragging windows in Expo mode doesn't work or 
results in weird behaviors.
  Sometimes, when dragging a window, the drag fails midway and then clicking 
anywhere on the screen does nothing (even when clicking in the Expo button, 
needing to press Super+S to exit Expo mode).

  I have also noticed that, when moving the cursor around in Expo mode, the 
close/minimize/maximize buttons of the windows would sometimes highlight and 
the locally integrated menus would be displayed.
  This seems to occur in the current workspace (the one where I was before 
entering Expo mode) when I move the cursor over where the buttons or menu are 
when out of the Expo mode.

  To reproduce that:
  * Open a window (terminal, nautilus, or anything else)
  * Move the window to the center (to make the next step easier)
  * Move the mouse cursor to a few pixels to the left of the close button of 
the window
  * Open Expo mode by pressing Super+S
  * Now start moving the cursor slowly to the right and see if the buttons (and 
menu) of the window are highlighted
  * When one of the buttons is highlighted, click. The action of that button 
will be performed (and it shouldn't) and Expo mode will exit to that workspace

  This may be the cause of the problem.

  I have also reproduced this in the guest session and in a 14.04.1
  virtual machine (not updated).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Nov 17 18:56:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (35 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid)

[Bruno Nova]

Small correction to the patch (for Trusty, maybe it also works in newer 
releases).
The condition should be "begin < a.end" instead of "begin <= a.end", or else 
all-day events would also be displayed when the next day is selected.

I also tested events that span multiple days, and it works correctly. The 
ongoing events for today are correctly displayed.
The calendar, however, only highlights (in bold) the first day of multiple-days 
events, which is another small bug.

** Patch added: "upcoming-after-end.patch"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+attachment/4395112/+files/upcoming-after-end.patch

** Patch removed: "upcoming-after-end.patch"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+attachment/4393197/+files/upcoming-after-end.patch

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

Title:
  Indicator-datetime still doesn't list all events for today's date
  (Trusty/Utopic/Vivid)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

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

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid)

[Bruno Nova]

Here's a simple patch for Trusty. It may also work in newer releases.
I've made a very short test but it seemed to work. Still, more testing is 
advisable!

The patch makes the list of upcoming events display, for today, the events that 
END before the current time, instead of the ones that START before it.
That means all-day events and ongoing events will now be displayed.

I think this is the best behavior. This is also the behavior of the Android 
calendar/agenda widget according to my tests, for example.
Today's all-day events should definitely be displayed! Displaying ongoing 
events is more debatable, but I still think they should be displayed.
If these events were not being displayed because the list only displays 5 
events at most, just increase the limit! Actually, that limit should be 
increased anyway (unless there's a bigger problem).

Related and possibly duplicate bug: #1329048

** Patch added: "upcoming-after-end.patch"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+attachment/4393197/+files/upcoming-after-end.patch

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

Title:
  Indicator-datetime still doesn't list all events for today's date
  (Trusty/Utopic/Vivid)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

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

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid)

[Bruno Nova]

I'm also affected by this issue in Trusty.
I think that, for today, the indicator should list the events that END after 
the current time, instead of the ones that START after it.

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

Title:
  Indicator-datetime still doesn't list all events for today's date
  (Trusty/Utopic/Vivid)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

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

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

[Touch-packages] [Bug 1061852] Re: Unity Application Lens slow to load

[Bruno Nova]

Your startup entry ended in "applications/"? That's probably why it
wasn't working.

The command I wrote in comment #1 was cut in two lines automatically by 
Launchpad. The "scopes.scope commands.scope" line was also part of the command.
That command corresponds to the "Exec=" line in the .desktop file.

So, the last workaround is not loading more scopes, you just didn't
understand that the other line in my previous comment was also part of
the command, which is totally understandable. Thanks Launchpad! :)

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

Title:
  Unity Application Lens slow to load

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

Bug description:
  WHAT HAPPENS
  --
  Log into the system
  Launch the dash with the 'window' key
  Start typing 'chr'...

  I see my files appearing in the search results
  The application lens results appear ~10 - 15 seconds later

  WHAT IS DESIRABLE
  ---
  The application lens results appear immediately

  
  Most users would login into the system and launch a web browser
  Optimal unity experience demands that their browser or mail client shows up 
in the dash instantaneously

  Also this behaviour has worsened recently (after upgrade to 12.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.16.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,resize,commands,place,regex,move,grid,session,snap,vpswitch,imgpng,gnomecompat,mousepoll,put,animation,compiztoolbox,expo,wall,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell]
  Date: Fri Oct  5 01:13:34 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1061852] Re: Unity Application Lens slow to load

[Bruno Nova]

For those still facing this issue, here is the workaround that I'm using.
It's based on my previous comment:

I've added the command "/usr/bin/unity-scope-loader 
applications/applications.scope applications/scopes.scope commands.scope" to 
the auto-start programs, with a delay (30 seconds in my case).
The applications scope used to take 10+ seconds to load for me, now it takes 
3-5 seconds.

I've attached a ".desktop" file.
If you want to use this workaround, download the file and move it to 
"~/.config/autostart".
The command starts after a delay of 20 seconds by default (after login). If you 
want to change it, open the file with the text editor (open the text editor, 
then drag the file into the editor) and change the "X-GNOME-Autostart-Delay" 
field.
You may also want to open the auto-start configuration program from the Dash to 
check if it was really added and is enabled.

** Attachment added: "preload-dash.desktop"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1061852/+attachment/4383306/+files/preload-dash.desktop

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

Title:
  Unity Application Lens slow to load

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

Bug description:
  WHAT HAPPENS
  --
  Log into the system
  Launch the dash with the 'window' key
  Start typing 'chr'...

  I see my files appearing in the search results
  The application lens results appear ~10 - 15 seconds later

  WHAT IS DESIRABLE
  ---
  The application lens results appear immediately

  
  Most users would login into the system and launch a web browser
  Optimal unity experience demands that their browser or mail client shows up 
in the dash instantaneously

  Also this behaviour has worsened recently (after upgrade to 12.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.16.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,resize,commands,place,regex,move,grid,session,snap,vpswitch,imgpng,gnomecompat,mousepoll,put,animation,compiztoolbox,expo,wall,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell]
  Date: Fri Oct  5 01:13:34 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

** Branch linked: lp:~brunonova/ubuntu/trusty/software-
properties/lp1381050_lp1383289

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

Title:
  Dropping a key into the list of keys fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1076976] Re: When Unity is loaded, expo exits to the workspace being pointed at (not the one highlighted)

[Bruno Nova]

@Andrea, no, I can't reproduce it in Trusty anymore (also checked a Utopic VM).
It seems to have been fixed. Maybe you should mark it as "Fixed Released"?

Offtopic: Andrea, could you, or anyone else, check bug #1393523 (also
about Expo) and possibly triage it?

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

Title:
  When Unity is loaded, expo exits to the workspace being pointed at
  (not the one highlighted)

Status in Ayatana Design:
  Triaged
Status in Unity:
  Incomplete
Status in Unity 6.0 series:
  Won't Fix
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Since I upgraded to quantal I encounter the following issue:
  - press Super+S to quickly find the relevant workspace I want to go,
  - realize I'm in the right one
  - press Super+S again to come back to the normal display

  Oops, the workspace is switched to where the mouse pointer is.

  This happens only when pressing Super+S twice. If instead I press
  escape or navigate with direction keys and press return or click to
  the target workspace (obviously ;), I'm switched to the correct
  workspace.

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

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

[Touch-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Bruno Nova]

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

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

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Fix Released
Status in indicator-keyboard package in Ubuntu:
  Won't Fix
Status in ibus source package in Trusty:
  Fix Committed
Status in indicator-keyboard source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

** Changed in: software-properties (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Dropping a key into the list of keys fails

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Bruno Nova]

According to the previous comments, the fix for Trusty is apparently not 
working.
So the verification-done tag should probably be replaced by verification-failed!

I had tested the fix in a virtual machine, but I noticed that 
use-system-keyboard-layout was still false after installing it (reported by 
ibus-setup and gsettings).
As I commented in the merge request 
(https://code.launchpad.net/~brunonova/ubuntu/trusty/ibus/lp1240198/+merge/241742),
 the line I added to "debian/ibus.install" is missing from the fix. That line 
installs the file gschema override that sets use-system-keyboard-layout=true.
If the fix is indeed not working, this is probably the reason why it's failing.

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

Title:
  [SRU]Wrong keyboard layout active after booting into desktop

Status in ibus package in Ubuntu:
  Fix Released
Status in indicator-keyboard package in Ubuntu:
  Won't Fix
Status in ibus source package in Trusty:
  Fix Committed
Status in indicator-keyboard source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

  When first boot into Unity desktop, English keyboard layout is active
  while all other parts of the system language settings are set to
  another language (e.g. German).

  The bug is properly addressed in newer upstream releases in Vivid, but
  the changes is too intrusive and not suitable for being back ported in
  SRU. And changing the default to use system keyboard layout solves the
  problem.

  [Test Case]

  1. Set the system language to something other than English, e.g. German.
  2. Create a new user, log in to the Unity desktop of the new user.
  3. Check the keyboard layout, it should be German instead of English.

  [Regression Potential]

  Since this changes the default value of the keyboard layout settings
  by using system defined as default, it avoids using ibus's built-in
  keyboard layout related functionality, so that this could be a
  regression for users rely on this certain behavior (e.g. use English
  keyboard while want to keep the system language settings to German),
  but such behavior is not expected for normal usage.

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

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

[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

[Bruno Nova]

I've tested the trusty-proposed update in a VirtualBox virtual machine
(version 7.2.4+14.04.20141217-0ubuntu1).

The update fixes the issue.
Now when I press Super+W, type something until only 1 window is shown (filter) 
and select the window, the title bars of all of the maximized windows are 
correctly merged with the top bar.
It also works when the windows are spread through multiple workspaces and I use 
Super+Shift+W to view all of the windows.
And it works both with the global menu and with locally integrated menus.

** 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/1316265

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

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 ]

  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  [ Test Case ]

  (1) Open one or more Terminals, place one in maximized mode (eg. by using 
control-super-up or clicking the embiggen button).
  (2) use super-W to enter the spread mode
  (3) select the maximized terminal window
  (4) lookee lookee, separate title bars without the fix!

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce a
  new crash or hangup.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream
  Unity where it has been a part of the Ubuntu "Vivid Vervet" dev
  release for some time now and has demonstrated no regressions.

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

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

[Touch-packages] [Bug 1403293] Re: Unity Dash can't understand "logout", "reboot", or "shutdown"

[Bruno Nova]

It used to be possible to do this via the HUD (see Bug #1165420), but
not anymore.

I agree with making these options available from the Dash (the
"Hibernate" option could give some trouble because hibernation is
disabled by default; maybe, when disabled, it could open the Help
document on how to enable it?).

The best place for these options would probably be in a new "System commands" 
scope (or in the "Alt+F2" scope, if it was accessible from the "Home" scope and 
from the normal Dash with the Super key).
But, for now (Unity 7), I agree with putting some ".desktop" files in the 
Applications scope, and leaving a "better" solution for Unity 8.

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

Title:
  Unity Dash can't understand "logout", "reboot", or "shutdown"

Status in Unity:
  Triaged
Status in Unity Applications Lens:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug proposes the additional surfacing of power-management and
  session actions directly within the Dash:

    - Reboot ("restart" is another good alias for this)
    - Shutdown (other intuitive aliases: "shut down", "turn off")
    - logout (aliases: "log out", "log off" and "logoff")
    - Suspend/hibernate
    - Lock
    - Switch User

  Currently these user-initiated actions are presented via the Devices
  (cog/gear-icon-menu), and can be accessed via the keyboard using
  either:

    1. [Alt]+[F10] [Left] [Up/Down] [Enter]
    2. [Alt] "Shutdown"/"Log out" [Up/Down] [Enter]
    3. [Ctrl]+[Alt]+[Del] [Enter]  ("Log off" only)
    4. [Ctrl]+[Alt]+[t] "sudo reboot" [Enter]

  (Note that "Restart"/"Reboot" can not be accessed directly via 1-3).

  These methods are less likely to be found by the user than surfacing these 
actions additionally within the Dash.  This would help in cases where a 
mouse/pointer is no longer available, such as "mouse-cursor did not appear 
after logging in to the Unity Desktop"
    https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

  This would also assist with "ctrl-alt-delete doesn't provide a reboot option"
    https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289

  It is proposed by surfacing these options in the Unity Dash, that
  finding the actions would be more intuitive, and would make the Dash
  feel more complete as the defacto first-point-of-call for user
  initiated actions.

  Implementation possibilities:

    1. Hard-code special-case actions into the Dash (requires Design review, 
code and ship acceptance)
    2. Implement as Dash plugin (requires code and ship acceptance)
    3. Install additional .desktop listing the Name, Icon and Aliases in 
/usr/share/applications/*.desktop (can be provided by a separate optional 
package, only requires ship acceptance)

  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1

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

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

[Touch-packages] [Bug 1398180] [NEW] Error when adding/removing key in KDE version

[Bruno Nova]

Public bug reported:

Discovered this bug in 14.04.

In the KDE version of software-properties, when I add or remove a key, an error 
about the key being invalid is displayed.
However, it seems that the key is actually added/removed (checked with apt-key).

The respective methods in softwareproperties/SoftwareProperties.py call the 
KeysModified() method.
Apparently, this method doesn't exist in the KDE version, causing an exception 
which makes the add/remove methods return False.
This is the cause of this bug.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: trusty

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

Title:
  Error when adding/removing key in KDE version

Status in software-properties package in Ubuntu:
  New

Bug description:
  Discovered this bug in 14.04.

  In the KDE version of software-properties, when I add or remove a key, an 
error about the key being invalid is displayed.
  However, it seems that the key is actually added/removed (checked with 
apt-key).

  The respective methods in softwareproperties/SoftwareProperties.py call the 
KeysModified() method.
  Apparently, this method doesn't exist in the KDE version, causing an 
exception which makes the add/remove methods return False.
  This is the cause of this bug.

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

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

[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

[Bruno Nova]

Great! I hope these fixes will be backported to Trusty and Utopic!

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

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

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

Bug description:
  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  Try this out using Terminal.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon May  5 14:48:01 2014
  InstallationDate: Installed on 2013-09-08 (239 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130424)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago)

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

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

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

[Bruno Nova]

Also affected in 14.04. This bug should be of high importance.
This bug was fixed in Debian in version 1.1~exp4, but the version in sid is 
1.0.9.3, so I think we will have to wait bit yet.

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

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

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10
  apt  0.9.9.1~ubuntu3

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

  W: GPG error: http://us.archive.ubuntu.com saucy Release: The
  following signatures couldn't be verified because the public key is
  not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  'apt-key list' shows the keys in question in its output...

  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  ...and its output begins with the following:

  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-
  manager.gpg': resource limit

  I see the same gpg message when I manually update/remove/add the keys
  in question. E.g.:

  $ sudo apt-key update
  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': 
resource limit
  gpg: keyblock resource 
`/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit
  gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key 
" not changed
  gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key 
" not changed
  gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) 
" not changed
  gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) 
" not changed
  gpg: Total number processed: 4
  gpg:  unchanged: 4

  I asked about the "resource limit" message on the gnupg-users mailing list...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html
  Based on Werner Koch's (the dev) answer...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html
  ...the secure apt related programs might be making gpg use more than the 
maximum number of keyrings that it can handle.

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

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

[Touch-packages] [Bug 1393523] Re: Dragging windows in Expo mode occasionally results in weird behavior

[Bruno Nova]

This bug occurred again now, but this time Super+S didn't close Expo mode.
The "window drag action" got stuck in Expo mode, and every time I pressed the 
Super key, the window moved to to cursor position.
I had to run "sudo restart lightdm" from a virtual console to restart the 
session.

This should be of high importance! Could a developer check (triage) this
bug?

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

Title:
  Dragging windows in Expo mode occasionally results in weird behavior

Status in compiz package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  There are some times where dragging windows in Expo mode doesn't work or 
results in weird behaviors.
  Sometimes, when dragging a window, the drag fails midway and then clicking 
anywhere on the screen does nothing (even when clicking in the Expo button, 
needing to press Super+S to exit Expo mode).

  I have also noticed that, when moving the cursor around in Expo mode, the 
close/minimize/maximize buttons of the windows would sometimes highlight and 
the locally integrated menus would be displayed.
  This seems to occur in the current workspace (the one where I was before 
entering Expo mode) when I move the cursor over where the buttons or menu are 
when out of the Expo mode.

  To reproduce that:
  * Open a window (terminal, nautilus, or anything else)
  * Move the window to the center (to make the next step easier)
  * Move the mouse cursor to a few pixels to the left of the close button of 
the window
  * Open Expo mode by pressing Super+S
  * Now start moving the cursor slowly to the right and see if the buttons (and 
menu) of the window are highlighted
  * When one of the buttons is highlighted, click. The action of that button 
will be performed (and it shouldn't) and Expo mode will exit to that workspace

  This may be the cause of the problem.

  I have also reproduced this in the guest session and in a 14.04.1
  virtual machine (not updated).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Nov 17 18:56:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (35 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Bruno Nova]

The problem here is that the Ubuntu developers decided that "when you
click the file manager icon, your home folder should open". So, when the
trash (or a device) is open, clicking the file manager icon opens a new
window with the home folder. Even Mark Shuttleworth said that's the
intended behavior:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/769515/comments/3

This traded one usability problem by another!
When only the trash in open, for example, the file manager icon is also 
highlighted, and Unity indicates with two arrows that the file manager is open 
and focused. Also, the windows is minimized/restored to/from that icon.
If this behavior is to be kept, these issues should be fixed because they are 
very misleading.

Or just revert the behavior!
If you put the cursor over the file manager icon, the tooltip says "Files", not 
"Home Folder". So, why would the user expect that this icon is used only to 
open the home folder?

My vote goes to reverting this behavior (someone provided a patch already).
Just my humble opinion.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/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 1396553] [NEW] No rating and 0 reviews shown for all applications in the dash

[Bruno Nova]

Public bug reported:

When viewing the preview of any application in the dash (installed or not) by 
right-clicking it, the displayed number of reviews is always 0 (zero) and the 
rating is always empty.
This used to work in previous Ubuntu versions.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Nov 26 11:08:57 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-13 (43 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  No rating and 0 reviews shown for all applications in the dash

Status in “unity” package in Ubuntu:
  New

Bug description:
  When viewing the preview of any application in the dash (installed or not) by 
right-clicking it, the displayed number of reviews is always 0 (zero) and the 
rating is always empty.
  This used to work in previous Ubuntu versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Nov 26 11:08:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (43 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1393523] [NEW] Dragging windows in Expo mode occasionally results in weird behavior

[Bruno Nova]

Public bug reported:

There are some times where dragging windows in Expo mode doesn't work or 
results in weird behaviors.
Sometimes, when dragging a window, the drag fails midway and then clicking 
anywhere on the screen does nothing (even when clicking in the Expo button, 
needing to press Super+S to exit Expo mode).

I have also noticed that, when moving the cursor around in Expo mode, the 
close/minimize/maximize buttons of the windows would sometimes highlight and 
the locally integrated menus would be displayed.
This seems to occur in the current workspace (the one where I was before 
entering Expo mode) when I move the cursor over where the buttons or menu are 
when out of the Expo mode.

To reproduce that:
* Open a window (terminal, nautilus, or anything else)
* Move the window to the center (to make the next step easier)
* Move the mouse cursor to a few pixels to the left of the close button of the 
window
* Open Expo mode by pressing Super+S
* Now start moving the cursor slowly to the right and see if the buttons (and 
menu) of the window are highlighted
* When one of the buttons is highlighted, click. The action of that button will 
be performed (and it shouldn't) and Expo mode will exit to that workspace

This may be the cause of the problem.

I have also reproduced this in the guest session and in a 14.04.1
virtual machine (not updated).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Nov 17 18:56:18 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-13 (35 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug trusty

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

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

Title:
  Dragging windows in Expo mode occasionally results in weird behavior

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

Bug description:
  There are some times where dragging windows in Expo mode doesn't work or 
results in weird behaviors.
  Sometimes, when dragging a window, the drag fails midway and then clicking 
anywhere on the screen does nothing (even when clicking in the Expo button, 
needing to press Super+S to exit Expo mode).

  I have also noticed that, when moving the cursor around in Expo mode, the 
close/minimize/maximize buttons of the windows would sometimes highlight and 
the locally integrated menus would be displayed.
  This seems to occur in the current workspace (the one where I was before 
entering Expo mode) when I move the cursor over where the buttons or menu are 
when out of the Expo mode.

  To reproduce that:
  * Open a window (terminal, nautilus, or anything else)
  * Move the window to the center (to make the next step easier)
  * Move the mouse cursor to a few pixels to the left of the close button of 
the window
  * Open Expo mode by pressing Super+S
  * Now start moving the cursor slowly to the right and see if the buttons (and 
menu) of the window are highlighted
  * When one of the buttons is highlighted, click. The action of that button 
will be performed (and it shouldn't) and Expo mode will exit to that workspace

  This may be the cause of the problem.

  I have also reproduced this in the guest session and in a 14.04.1
  virtual machine (not updated).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Nov 17 18:56:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (35 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1076976] Re: When Unity is loaded, expo exits to the workspace being pointed at (not the one highlighted)

[Bruno Nova]

I was affected by this bug until Saucy.
But I'm not affected by it in Trusty (I have not checked Utopic).
Maybe it's fixed now?

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

Title:
  When Unity is loaded, expo exits to the workspace being pointed at
  (not the one highlighted)

Status in Ayatana Design:
  Triaged
Status in Unity:
  Triaged
Status in Unity 6.0 series:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Since I upgraded to quantal I encounter the following issue:
  - press Super+S to quickly find the relevant workspace I want to go,
  - realize I'm in the right one
  - press Super+S again to come back to the normal display

  Oops, the workspace is switched to where the mouse pointer is.

  This happens only when pressing Super+S twice. If instead I press
  escape or navigate with direction keys and press return or click to
  the target workspace (obviously ;), I'm switched to the correct
  workspace.

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

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Bruno Nova]

** Branch linked: lp:~brunonova/ubuntu/trusty/ibus/lp1240198

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Bruno Nova]

** Branch unlinked: lp:~brunonova/ubuntu/vivid/ibus/lp1240198

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Bruno Nova]

** Branch linked: lp:~brunonova/ubuntu/vivid/ibus/lp1240198

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Bruno Nova]

To apply the fix (setting use-system-keyboard-layout=true) system-wide:

1. As root, create the file
/usr/share/glib-2.0/schemas/30_ibus.gschema.override with the contents:

[org.freedesktop.ibus.general]
use-system-keyboard-layout=true

2. Then run: sudo glib-compile-schemas /usr/share/glib-2.0/schemas/

This should set the default value of use-system-keyboard-layout to true, which 
should fix the issue.
But I'm not sure if it actually fixes it (dconf is confusing).

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 1297234] Re: Live session set wrong keyboard layout and time zone

[Bruno Nova]

@ernie, I think the bug you're referring is this one: Bug LP: #1240198

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

Title:
  Live session set wrong keyboard layout and time zone

Status in “console-setup” package in Ubuntu:
  Expired
Status in “ibus” package in Ubuntu:
  Expired
Status in “ubiquity” package in Ubuntu:
  Confirmed
Status in “console-setup” source package in Trusty:
  Invalid
Status in “ibus” source package in Trusty:
  Invalid
Status in “ubiquity” source package in Trusty:
  Invalid

Bug description:
  When I boot the Ubuntu Studio 14.04 beta 2 testing it will start with
  keyboard set to English US and time zone as UTC. Usually I believe
  this would be localized to my Swedish keyboard and CET.

  ubuntu-studio@ubuntu-studio:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ubuntu-studio@ubuntu-studio:~$ apt-cache policy keyboard-configuration
  keyboard-configuration:
Installed: 1.70ubuntu8
Candidate: 1.70ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CurrentDesktop: XFCE
  Date: Tue Mar 25 11:33:44 2014
  LiveMediaBuild: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Beta i386 (20140325)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1301401] Re: Remove chat support from Windows Live provider

[Bruno Nova]

OK, it seems that the last MSN servers are finally being shutdown.
MSN stopped working for me in Pidgin today.

So I guess it's time to remove Windows Live from Pidgin, Empathy and Online 
Accounts.
Unless there's a way to make it work again (through Skype servers or something, 
but it's probably not possible and not worth the effort).

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

Title:
  Remove chat support from Windows Live provider

Status in Chat app, and Telepathy user interface:
  Fix Released
Status in “empathy” package in Ubuntu:
  Confirmed
Status in “gnome-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  From upstream bug report:

  Microsoft has had been planning to drop Windows Live Messenger in favour of
  Skype for quite some time now. See:
   - http://www.bbc.com/news/technology-20222998
   -
  
http://arstechnica.com/information-technology/2013/01/microsoft-messenger-service-not-going-anywhere-just-yet/

  
--

  eduar@envy4:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  eduar@envy4:~$ apt-cache policy empathy
  empathy:
    Instalados: 3.8.6-0ubuntu7
    Candidato:  3.8.6-0ubuntu7
    Tabla de versión:
   *** 3.8.6-0ubuntu7 0
  500 http://co.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  eduar@envy4:~$ apt-cache policy telepathy-gabble
  telepathy-gabble:
    Instalados: 0.18.2-1
    Candidato:  0.18.2-1
    Tabla de versión:
   *** 0.18.2-1 0
  500 http://co.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Hello all. I'm trying to setup my Windows Live account (@outlook.com)
  in Empathy. It used to work OK on Ubuntu 12.04.4 64 bits. However, in
  14.04 it doesn't works. When I add an account, it asks me for my
  username and password, I give it permissions to access my data, and
  the account is shown OK on the "Online accounts" window. However, when
  I go Online, Empathy shows a wheel in the middle, just turning around,
  but nothing else happens. After a while, it gives me a red error
  message "x...@outlook.com Network error"

  I have the debug in pastebin: http://pastebin.com/8vQdM4Pg

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: empathy 3.8.6-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  2 08:41:58 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-30 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

[Bruno Nova]

@Stephen, it also affects English when workspaces are enabled (and horizontal 
resolution is 1024).
But yes, I think a new bug should be filed (the size problem in other languages 
could also be mentioned there).

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

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

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

[Bruno Nova]

Like I said, the horizontal size of the overlay does depend on the current 
language.
In Portuguese (my native language), the texts are longer and the overlay 
doesn't fit (even with workspaces disabled), but in English it fits.

I think 1024x768 should be the minimum supported resolution by the overlay (in 
English, at least).
Maybe you should report a new bug (asking the overlay to be made smaller 
horizontally)?

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

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

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

[Bruno Nova]

You're right!
With an horizontal resolution of 1024, the overlay is not display.
I took a screenshot of the overlay to see how it would look in 1024x768, and it 
doesn't fit horizontally, even with workspaces disabled.
Also, the horizontal size probably depends on the used language (the texts may 
be longer/shorter in other languages).

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

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

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1297234] Re: Live session set wrong keyboard layout and time zone

[Bruno Nova]

This issue does exist in Trusty (probably in Utopic as well).
It didn't exist a few versions ago (I don't remember which one introduced the 
bug).

If I boot from the Live USB (created using "dd"), select another language 
(Portuguese, for example) then "Try Ubuntu", the live session has English 
keyboard layout, UTC time and almost all text in English (some things in 
Portuguese).
The text being in English is OK, but the keyboard layout and timezone not being 
what I selected is not OK.

And, as mentioned in comment #7, when the boot process reaches the
"purple screen with some icons at the bottom" (like this: http://pix
.toile-libre.org/upload/original/1347445119.png), if I press some key
and then select Portuguese from there and "Try Ubuntu", the live session
will have the correct keyboard layout (not sure about the timezone).

So, there's a bug somewhere.

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

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

Title:
  Live session set wrong keyboard layout and time zone

Status in “console-setup” package in Ubuntu:
  Expired
Status in “ibus” package in Ubuntu:
  Expired
Status in “ubiquity” package in Ubuntu:
  Confirmed
Status in “console-setup” source package in Trusty:
  Invalid
Status in “ibus” source package in Trusty:
  Invalid
Status in “ubiquity” source package in Trusty:
  Invalid

Bug description:
  When I boot the Ubuntu Studio 14.04 beta 2 testing it will start with
  keyboard set to English US and time zone as UTC. Usually I believe
  this would be localized to my Swedish keyboard and CET.

  ubuntu-studio@ubuntu-studio:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ubuntu-studio@ubuntu-studio:~$ apt-cache policy keyboard-configuration
  keyboard-configuration:
Installed: 1.70ubuntu8
Candidate: 1.70ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CurrentDesktop: XFCE
  Date: Tue Mar 25 11:33:44 2014
  LiveMediaBuild: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Beta i386 (20140325)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Bruno Nova]

* Does this bug affect Utopic users that fresh installed it (not
upgraded from a previous release)?

* For users facing this bug, a simple fix is, as others mentioned, to run 
"ibus-setup", go to the "Advanced tab" and enable "Use system keyboard layout".
It works for me.

* I attached a patch that changes the default value of 
/desktop/ibus/general/use-system-keyboard-layout to true, which should fix the 
issue.
But, after compiling and installing the ibus package myself, running 
"ibus-setup" throws an error and doesn't start:
(ibus-setup:2680): GLib-GIO-ERROR **: Settings schema 
'org.freedesktop.ibus.general.xkblayoutconfig' is not installed
I have no idea why. I haven't tried compiling without the patch.
So, if this patch is considered, it should be carefully tested. And I also 
don't know if this could affect other desktop environments negatively.
But the main idea of the patch is setting that dconf setting to true.

* This bug should be added to the 14.04 release notes. (Can/should I
edit it myself?)

** Patch added: "use-system-keyboard-layout.patch"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1240198/+attachment/4247484/+files/use-system-keyboard-layout.patch

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 1281802] Re: /usr/local/games is after /usr/games in the default PATH (instead of before)

[Bruno Nova]

Here's a patch for this "bug".

** Patch added: "correct_path.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1281802/+attachment/4241710/+files/correct_path.patch

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

Title:
  /usr/local/games is after /usr/games in the default PATH (instead of
  before)

Status in “pam” package in Ubuntu:
  New

Bug description:
  I'm reporting this bug after asking this question in Ask Ubuntu:
  http://askubuntu.com/questions/422605/why-is-usr-local-games-after-
  usr-games-in-the-default-path

  The default value of the PATH environment variable in Ubuntu is: 
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  (the lightdm part may or may not be there)

  /usr/local/games appears after /usr/games instead of before.
  This seems to be a mistake. I think /usr/local/games should appear before 
/usr/games, more so considering that the other two "local" directories appear 
before the non-local ones.

  This default PATH seems to come from /etc/environment, and this file is 
created by libpam-module's postint script (the answer to the Ask Ubuntu 
question explains this).
  This is specific to Ubuntu. Debian apparently has the directories in the 
correct order.

  I'm using Ubuntu 13.10, but I think this "problem" already existed
  before.

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

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

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

[Bruno Nova]

Is anyone still facing this issue?
If not, I think this should be marked as Fixed.

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

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

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

Ok, I think I got it. I'm going to link a branch that solves this soon.

** Branch linked: lp:~brunonova/software-properties/lp1383289

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

Oh, before that there's another error:

Traceback (most recent call last):
  File 
"/home/bruno/src/software-properties/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 760, in on_auth_drag_data_received
if not self.add_key_from_data(keydata):
  File 
"/home/bruno/src/software-properties/software-properties/softwareproperties/SoftwareProperties.py",
 line 815, in add_key_from_data
tmp.write(keydata.encode())
AttributeError: 'bytes' object has no attribute 'encode'

Just replace:
tmp.write(keydata.encode())
with:
tmp.write(keydata)
because keydata is already "bytes" at that point.

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

'SelectionData' has indeed no 'data' attribute. But it has a 'get_data()' 
method.
So, "selection.data.strip()" should be renamed to 
"selection.get_data().strip()" in 
softwareproperties/gtk/SoftwarePropertiesGtk.py (there are 2 occurrences).
Don't know if the bug exists in the KDE version.

But that doesn't fix everything. It will then throw these errors:
gpg: no writable keyring found: eof
gpg: error reading `/tmp/tmpcszfsj3q': general error
gpg: import from `/tmp/tmpcszfsj3q' failed: general error

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383289] Re: Dropping a key into the list of keys fails

[Bruno Nova]

** Summary changed:

- Dropping a key file into the list of keys fails
+ Dropping a key into the list of keys fails

** Description changed:

- When I drag a key file and drop it into the list of keys in the
+ When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug report
  appears), throwing an exception:
  
  Traceback (most recent call last):
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
- keydata = selection.data.strip()
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
+ keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

Reported that other bug I mentioned in Bug #1383289.

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_("Error importing selected file"),
_("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383289] [NEW] Dropping a key into the list of keys fails

[Bruno Nova]

Public bug reported:

When I drag a key text/file and drop it into the list of keys in the
"Authentication" list, it fails silently (sometimes an apport bug report
appears), throwing an exception:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
keydata = selection.data.strip()
AttributeError: 'SelectionData' object has no attribute 'data'

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: software-properties-gtk 0.92.37.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 20 14:01:10 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-13 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  "Authentication" list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

** Branch linked: lp:~brunonova/software-properties/lp1381050

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_("Error importing selected file"),
_("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

** Branch linked: lp:~brunonova/software-properties/lp1381050

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_("Error importing selected file"),
_("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

I finally found the cause of the problem!
It seems that the DBus service (or the whole DBus) is not running in a UTF-8 
locale, thus causing errors in UTF-8 strings.

The workaround is to edit softwareproperties/SoftwareProperties.py and add:
path = path.encode('utf-8')
in method "def add_key(self, path)" around line 800 before the line:
if not os.path.exists(path):

This encoding issue may be causing problems in other parts of the
program, and other programs.


Meanwhile, I found another bug:
Dragging and dropping a key file to the list doesn't work, raising an exception:
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 759, in on_auth_drag_data_received
keydata = selection.data.strip()
AttributeError: 'SelectionData' object has no attribute 'data'

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_("Error importing selected file"),
_("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

Here's a traceback of the exception:

org.freedesktop.DBus.Python.UnicodeEncodeError: Traceback (most recent call 
last):
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 707, in 
_message_cb
retval = candidate_method(self, *args, **keywords)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py",
 line 288, in AddKey
return self.add_key(path)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
800, in add_key
if not os.path.exists(path):
  File "/usr/lib/python3.4/genericpath.py", line 19, in exists
os.stat(path)
UnicodeEncodeError: 'ascii' codec can't encode character '\xea' in position 20: 
ordinal not in range(128)

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_("Error importing selected file"),
_("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1381050] [NEW] "Import Key File" fails when the path of the file has special characters

[Bruno Nova]

Public bug reported:

The "Import Key File..." button in the "Authentication" tab fails
silently when the path of the selected key file includes special
characters.

I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is named 
"/home/$USER/Transferências" here.
Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

The problem is that, in softwareproperties/gtk/SoftwarePropertiesGtk.py
in method SoftwarePropertiesGtk.add_key_clicked() at around line 952:

if res == Gtk.ResponseType.ACCEPT:
try:
if not self.backend.AddKey(chooser.get_filename()):
error(self.window_main,
  _("Error importing selected file"),
  _("The selected file may not be a GPG key file "
"or it might be corrupt."))
except dbus.DBusException as e:
if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
logging.error("Authentication canceled, changes have not 
been saved")

"self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
This is probably a side effect of switching from Python 2 to 3 (and 'bytes' now 
being used in network communications where 'str' was previously used).

Another issue is that the error isn't reported to the user, and it
should be.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: software-properties-gtk 0.92.37.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 14 13:22:21 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-13 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_("Error importing selected file"),
_("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open

[Bruno Nova]

The warning is shown when another user is logged in graphically (via
lightdm).

But what about when the other user is logged in a virtual console (Alt+F1) or 
via SSH, RDP, etc?
>From what I've seen, the warning isn't shown in these cases.

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

Title:
  [UIFe] The system shutdowns when multiple accounts are open

Status in Ayatana Design:
  Fix Committed
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  Confirmed
Status in “systemd” source package in Trusty:
  Invalid
Status in “unity” source package in Trusty:
  Fix Released
Status in “unity-greeter” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Other users logged into a system may loose work if another user shuts
  down/reboots a system.  Data loss is not a Good Thing.

  [Test Case]

  Steps to reproduce:

  1) Create a second account in the system
  2) While the first account is open, open a session with the second one
  3) Try to shutdown the system

  Expected results:
  The system logs out instead of shutting down (ideally with a warning on why 
it did that)

  Actual results:
  The system shutdowns and unsaved data on session1 is lost

  [ Regression Potential]

  None.

  --
  Desired resolution:

  - Add a warning message informing the user that other users are logged in and 
then shutting down will also close their sessions as proposed in the mockup 
attached to comment #12
  - The warning message should be "Other users are currently logged in to this 
computer, shutting down now will also close these other sessions"

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

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

[Touch-packages] [Bug 1296420] Re: Pulseaudio makes kde stall for a few seconds during startup

[Bruno Nova]

Damn, I didn't know linking a remote bug would import all of its
comments. That's actually nice!

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

Title:
  Pulseaudio makes kde stall for a few seconds during startup

Status in PulseAudio sound server:
  Fix Released
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Quote from this post. :
  
http://linuxadvantage.blogspot.dk/2013/01/kde-rather-slow-to-start-pulseaudio.html

  On many distributions delivering KDE, since version 4.2, I have often
  found incomprehensibles slowness between login step and the time the
  desktop is fully loaded and usable.

  Indeed, we can see unfold normally the KDE's "splashscreen" and the
  desktop appears but in the systray, all the icons are not loaded and
  it is not possible to run a program until the startup sound is heard.
  This is long seconds (10 or 15 for me) where nothing happens (no
  visible disk access).

  After answering on this thread [1] , I opened a bug in KDE and it
  appears that the culprit is PulseAudio.

  Indeed, it seems that PulseAudio package for KDE brings 2 startup
  files instead of one: "pulseaudio.desktop" and "pulseaudio-
  kde.desktop"

  This often generates a delay to load the desktop caused by the program
  that is trying to start twice.

  Note that this is not systematic, I guess in some cases, the correct
  file is launched before the bad and in this case, there isn't any
  delays.

  The solution: Just simply delete the unwanted file to retreive a fast loading 
time. This is valid for all distributions.
  - Open a console as root
  - Go to the directory /etc/xdg/autostart
  - Check that you have two files "pulseaudio.desktop" and 
"pulseaudio-kde.desktop" in this directory.
  - Delete the file "pulseaudio.desktop" (or rename it to 
"pulseaudio.desktop.disable" if you prefer to keep it)
  - Reboot normally there shouldn't be more delay now caused by PulseAudio to 
logon

  
  [1]  https://bugs.kde.org/show_bug.cgi?id=312560

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
   /dev/snd/controlC0:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Mar 23 22:22:58 2014
  InstallationDate: Installed on 2013-12-24 (89 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1296420] Re: Pulseaudio makes kde stall for a few seconds during startup

[Bruno Nova]

I found an upstream bug report: 
https://bugs.freedesktop.org/show_bug.cgi?id=58758
It's from 2013 and is marked as fixed.
The reporter was suggesting that "pulseaudio.desktop should have 
NotShowIn=KDE;", which is what the patch I uploaded does and what several 
people also suggested.
But the actual fix is different.

>From what I understood, the problem is that the startup scripts communicate 
>with avahi synchronously, but "Avahi basically only makes blocking D-Bus 
>calls", so this may cause a delay due to a timeout.
The fix makes these communications asynchronous.
Could this also affects other desktop environments?

Here is the commit that fixes this: 
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=5ae5dee75eb70ff81414bd64b4ea41e6b8db7599
Here is another commit that mentioned "avahi" in the commit log: 
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=37e73e10be9e42544a4cc160ff85ccada2cc9aa9
There may be other relevant commits.

I think Pulse Audio 5 has this problem fixed, but Ubuntu still uses version 4.
Even Utopic uses version 4, even though Debian testing and sid are already on 5.
So, that fix has to be backported for Ubuntu.

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

** Also affects: pulseaudio via
   https://bugs.freedesktop.org/show_bug.cgi?id=58758
   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/1296420

Title:
  Pulseaudio makes kde stall for a few seconds during startup

Status in PulseAudio sound server:
  Unknown
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Quote from this post. :
  
http://linuxadvantage.blogspot.dk/2013/01/kde-rather-slow-to-start-pulseaudio.html

  On many distributions delivering KDE, since version 4.2, I have often
  found incomprehensibles slowness between login step and the time the
  desktop is fully loaded and usable.

  Indeed, we can see unfold normally the KDE's "splashscreen" and the
  desktop appears but in the systray, all the icons are not loaded and
  it is not possible to run a program until the startup sound is heard.
  This is long seconds (10 or 15 for me) where nothing happens (no
  visible disk access).

  After answering on this thread [1] , I opened a bug in KDE and it
  appears that the culprit is PulseAudio.

  Indeed, it seems that PulseAudio package for KDE brings 2 startup
  files instead of one: "pulseaudio.desktop" and "pulseaudio-
  kde.desktop"

  This often generates a delay to load the desktop caused by the program
  that is trying to start twice.

  Note that this is not systematic, I guess in some cases, the correct
  file is launched before the bad and in this case, there isn't any
  delays.

  The solution: Just simply delete the unwanted file to retreive a fast loading 
time. This is valid for all distributions.
  - Open a console as root
  - Go to the directory /etc/xdg/autostart
  - Check that you have two files "pulseaudio.desktop" and 
"pulseaudio-kde.desktop" in this directory.
  - Delete the file "pulseaudio.desktop" (or rename it to 
"pulseaudio.desktop.disable" if you prefer to keep it)
  - Reboot normally there shouldn't be more delay now caused by PulseAudio to 
logon

  
  [1]  https://bugs.kde.org/show_bug.cgi?id=312560

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
   /dev/snd/controlC0:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Mar 23 22:22:58 2014
  InstallationDate: Installed on 2013-12-24 (89 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing 

[Touch-packages] [Bug 1296420] Re: Pulseaudio makes kde stall for a few seconds during startup

[Bruno Nova]

I fail at copy-paste... Sorry, here's the correct path.

@sgh, I'll check that later, but I can only do that in Virtualbox.

** Patch added: "dont-delay-kde-start.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1296420/+attachment/4230013/+files/dont-delay-kde-start.patch

** Patch removed: "dont-delay-kde-start.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1296420/+attachment/4229944/+files/dont-delay-kde-start.patch

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

Title:
  Pulseaudio makes kde stall for a few seconds during startup

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Quote from this post. :
  
http://linuxadvantage.blogspot.dk/2013/01/kde-rather-slow-to-start-pulseaudio.html

  On many distributions delivering KDE, since version 4.2, I have often
  found incomprehensibles slowness between login step and the time the
  desktop is fully loaded and usable.

  Indeed, we can see unfold normally the KDE's "splashscreen" and the
  desktop appears but in the systray, all the icons are not loaded and
  it is not possible to run a program until the startup sound is heard.
  This is long seconds (10 or 15 for me) where nothing happens (no
  visible disk access).

  After answering on this thread [1] , I opened a bug in KDE and it
  appears that the culprit is PulseAudio.

  Indeed, it seems that PulseAudio package for KDE brings 2 startup
  files instead of one: "pulseaudio.desktop" and "pulseaudio-
  kde.desktop"

  This often generates a delay to load the desktop caused by the program
  that is trying to start twice.

  Note that this is not systematic, I guess in some cases, the correct
  file is launched before the bad and in this case, there isn't any
  delays.

  The solution: Just simply delete the unwanted file to retreive a fast loading 
time. This is valid for all distributions.
  - Open a console as root
  - Go to the directory /etc/xdg/autostart
  - Check that you have two files "pulseaudio.desktop" and 
"pulseaudio-kde.desktop" in this directory.
  - Delete the file "pulseaudio.desktop" (or rename it to 
"pulseaudio.desktop.disable" if you prefer to keep it)
  - Reboot normally there shouldn't be more delay now caused by PulseAudio to 
logon

  
  [1]  https://bugs.kde.org/show_bug.cgi?id=312560

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
   /dev/snd/controlC0:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Mar 23 22:22:58 2014
  InstallationDate: Installed on 2013-12-24 (89 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1296420] Re: Pulseaudio makes kde stall for a few seconds during startup

[Bruno Nova]

This patch disables /etc/xdg/autostart/pulseaudio.desktop from auto-
starting in KDE.

This was mentioned in https://bugs.kde.org/show_bug.cgi?id=312560#9 , and seems 
to resolve the delay.
I have no idea if this can cause any regressions, but I didn't find any in my 
short tests in Virtualbox.

** Bug watch added: KDE Bug Tracking System #312560
   https://bugs.kde.org/show_bug.cgi?id=312560

** Patch added: "dont-delay-kde-start.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1296420/+attachment/4229944/+files/dont-delay-kde-start.patch

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

Title:
  Pulseaudio makes kde stall for a few seconds during startup

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Quote from this post. :
  
http://linuxadvantage.blogspot.dk/2013/01/kde-rather-slow-to-start-pulseaudio.html

  On many distributions delivering KDE, since version 4.2, I have often
  found incomprehensibles slowness between login step and the time the
  desktop is fully loaded and usable.

  Indeed, we can see unfold normally the KDE's "splashscreen" and the
  desktop appears but in the systray, all the icons are not loaded and
  it is not possible to run a program until the startup sound is heard.
  This is long seconds (10 or 15 for me) where nothing happens (no
  visible disk access).

  After answering on this thread [1] , I opened a bug in KDE and it
  appears that the culprit is PulseAudio.

  Indeed, it seems that PulseAudio package for KDE brings 2 startup
  files instead of one: "pulseaudio.desktop" and "pulseaudio-
  kde.desktop"

  This often generates a delay to load the desktop caused by the program
  that is trying to start twice.

  Note that this is not systematic, I guess in some cases, the correct
  file is launched before the bad and in this case, there isn't any
  delays.

  The solution: Just simply delete the unwanted file to retreive a fast loading 
time. This is valid for all distributions.
  - Open a console as root
  - Go to the directory /etc/xdg/autostart
  - Check that you have two files "pulseaudio.desktop" and 
"pulseaudio-kde.desktop" in this directory.
  - Delete the file "pulseaudio.desktop" (or rename it to 
"pulseaudio.desktop.disable" if you prefer to keep it)
  - Reboot normally there shouldn't be more delay now caused by PulseAudio to 
logon

  
  [1]  https://bugs.kde.org/show_bug.cgi?id=312560

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
   /dev/snd/controlC0:  sgh2336 F pulseaudio
sgh2796 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Mar 23 22:22:58 2014
  InstallationDate: Installed on 2013-12-24 (89 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1379474] Re: unity://running-apps position in launcher ignored during startup

[Bruno Nova]

** Description changed:

  IN SHORT:
  
  The position of unity://running-apps in the dconf setting
  /com/canonical/unity/launcher/favorites is being ignored during startup
  (login).
- 
  
  DETAILED INFORMATION:
  
  I will explain this using an example, which makes it easier to explain
  and understand.
  
  Suppose that I have Nautilus and Firefox (+ workspaces and devices) pinned to 
the Unity launcher, in that order.
  When I open, for example, gedit, its icon appears below Firefox.
  "dconf read /com/canonical/unity/launcher/favorites" returns:
-   ['application://nautilus.desktop', 'application://firefox.desktop', 
'unity://running-apps', 'unity://expo-icon', 'unity://devices']
+   ['application://nautilus.desktop', 'application://firefox.desktop', 
'unity://running-apps', 'unity://expo-icon', 'unity://devices']
  
  If I move Firefox's icon to below gedit (not pinned), any new applications 
that I open that are not pinned appear above Firefox's icon, even after closing 
gedit.
  "dconf read /com/canonical/unity/launcher/favorites" now returns:
-   ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']
+   ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']
  
  'unity://running-apps' represents the applications that are not pinned,
  and defines where those applications should appear in the launcher. At
  least that's what it looks like.
  
  The problem is that, after restarting the session or rebooting, 
'unity://running-apps' is ignored, and apps that are not pinned appear below 
the last "application://..." icon, even if it's the last one.
  But "dconf read /com/canonical/unity/launcher/favorites" still returns:
-   ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']
+   ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']
  
+ The "favorites" are also maintained in gsettings:
+ "gsettings get com.canonical.Unity.Launcher favorites" returns the same 
results above.
  
  IMPACT:
  
  Because of this bug, users cannot pin applications to the "bottom" of
  the launcher, as unpinned apps will always appear below the last pinned
  application.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Oct  9 19:14:09 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-17 (114 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  unity://running-apps position in launcher ignored during startup

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

Bug description:
  IN SHORT:

  The position of unity://running-apps in the dconf setting
  /com/canonical/unity/launcher/favorites is being ignored during
  startup (login).

  DETAILED INFORMATION:

  I will explain this using an example, which makes it easier to explain
  and understand.

  Suppose that I have Nautilus and Firefox (+ workspaces and devices) pinned to 
the Unity launcher, in that order.
  When I open, for example, gedit, its icon appears below Firefox.
  "dconf read /com/canonical/unity/launcher/favorites" returns:
    ['application://nautilus.desktop', 'application://firefox.desktop', 
'unity://running-apps', 'unity://expo-icon', 'unity://devices']

  If I move Firefox's icon to below gedit (not pinned), any new applications 
that I open that are not pinned appear above Firefox's icon, even after closing 
gedit.
  "dconf read /com/canonical/unity/launcher/favorites" now returns:
    ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']

  'unity://running-apps' represents the applications that are not
  pinned, and defines where those applications should appear in the
  launcher. At least that's what it looks like.

  The problem is that, after restarting the session or rebooting, 
'unity://running-apps' is ignored, and apps that are not pinned appear below 
the last "application://..." icon, even if it's the last one.
  But "dconf read /com/canonical/unity/launcher/favorites" still returns:
    ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://device

[Touch-packages] [Bug 1379474] Re: unity://running-apps position in launcher ignored during startup

[Bruno Nova]

** Also affects: unity
   Importance: Undecided
   Status: New

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

Title:
  unity://running-apps position in launcher ignored during startup

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

Bug description:
  IN SHORT:

  The position of unity://running-apps in the dconf setting
  /com/canonical/unity/launcher/favorites is being ignored during
  startup (login).

  DETAILED INFORMATION:

  I will explain this using an example, which makes it easier to explain
  and understand.

  Suppose that I have Nautilus and Firefox (+ workspaces and devices) pinned to 
the Unity launcher, in that order.
  When I open, for example, gedit, its icon appears below Firefox.
  "dconf read /com/canonical/unity/launcher/favorites" returns:
    ['application://nautilus.desktop', 'application://firefox.desktop', 
'unity://running-apps', 'unity://expo-icon', 'unity://devices']

  If I move Firefox's icon to below gedit (not pinned), any new applications 
that I open that are not pinned appear above Firefox's icon, even after closing 
gedit.
  "dconf read /com/canonical/unity/launcher/favorites" now returns:
    ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']

  'unity://running-apps' represents the applications that are not
  pinned, and defines where those applications should appear in the
  launcher. At least that's what it looks like.

  The problem is that, after restarting the session or rebooting, 
'unity://running-apps' is ignored, and apps that are not pinned appear below 
the last "application://..." icon, even if it's the last one.
  But "dconf read /com/canonical/unity/launcher/favorites" still returns:
    ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']

  The "favorites" are also maintained in gsettings:
  "gsettings get com.canonical.Unity.Launcher favorites" returns the same 
results above.

  IMPACT:

  Because of this bug, users cannot pin applications to the "bottom" of
  the launcher, as unpinned apps will always appear below the last
  pinned application.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Oct  9 19:14:09 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-17 (114 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1379474] [NEW] unity://running-apps position in launcher ignored during startup

[Bruno Nova]

Public bug reported:

IN SHORT:

The position of unity://running-apps in the dconf setting
/com/canonical/unity/launcher/favorites is being ignored during startup
(login).


DETAILED INFORMATION:

I will explain this using an example, which makes it easier to explain
and understand.

Suppose that I have Nautilus and Firefox (+ workspaces and devices) pinned to 
the Unity launcher, in that order.
When I open, for example, gedit, its icon appears below Firefox.
"dconf read /com/canonical/unity/launcher/favorites" returns:
  ['application://nautilus.desktop', 'application://firefox.desktop', 
'unity://running-apps', 'unity://expo-icon', 'unity://devices']

If I move Firefox's icon to below gedit (not pinned), any new applications that 
I open that are not pinned appear above Firefox's icon, even after closing 
gedit.
"dconf read /com/canonical/unity/launcher/favorites" now returns:
  ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']

'unity://running-apps' represents the applications that are not pinned,
and defines where those applications should appear in the launcher. At
least that's what it looks like.

The problem is that, after restarting the session or rebooting, 
'unity://running-apps' is ignored, and apps that are not pinned appear below 
the last "application://..." icon, even if it's the last one.
But "dconf read /com/canonical/unity/launcher/favorites" still returns:
  ['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']


IMPACT:

Because of this bug, users cannot pin applications to the "bottom" of
the launcher, as unpinned apps will always appear below the last pinned
application.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu Oct  9 19:14:09 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-06-17 (114 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  unity://running-apps position in launcher ignored during startup

Status in “unity” package in Ubuntu:
  New

Bug description:
  IN SHORT:

  The position of unity://running-apps in the dconf setting
  /com/canonical/unity/launcher/favorites is being ignored during
  startup (login).

  
  DETAILED INFORMATION:

  I will explain this using an example, which makes it easier to explain
  and understand.

  Suppose that I have Nautilus and Firefox (+ workspaces and devices) pinned to 
the Unity launcher, in that order.
  When I open, for example, gedit, its icon appears below Firefox.
  "dconf read /com/canonical/unity/launcher/favorites" returns:
['application://nautilus.desktop', 'application://firefox.desktop', 
'unity://running-apps', 'unity://expo-icon', 'unity://devices']

  If I move Firefox's icon to below gedit (not pinned), any new applications 
that I open that are not pinned appear above Firefox's icon, even after closing 
gedit.
  "dconf read /com/canonical/unity/launcher/favorites" now returns:
['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']

  'unity://running-apps' represents the applications that are not
  pinned, and defines where those applications should appear in the
  launcher. At least that's what it looks like.

  The problem is that, after restarting the session or rebooting, 
'unity://running-apps' is ignored, and apps that are not pinned appear below 
the last "application://..." icon, even if it's the last one.
  But "dconf read /com/canonical/unity/launcher/favorites" still returns:
['application://nautilus.desktop', 'unity://running-apps', 
'unity://expo-icon', 'unity://devices', 'application://firefox.desktop']

  
  IMPACT:

  Because of this bug, users cannot pin applications to the "bottom" of
  the launcher, as unpinned apps will always appear below the last
  pinned application.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/

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

[Bruno Nova]

Wait, it's not fixed for me after all.

What happened is that I had Nautilus opened in another workspace, and this made 
it seem that the issue was fixed.
If no Nautilus windows were open before, the issue still occurs.

-- 
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 “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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[Bruno Nova]

It also seems to be fixed for me in Trusty!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/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 “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 1349387] Re: server settings are inaccessible

[Bruno Nova]

** Tags added: regression-update trusty

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

Title:
  server settings are inaccessible

Status in “cups” package in Ubuntu:
  Confirmed
Status in “system-config-printer” package in Ubuntu:
  Invalid

Bug description:
  When trying to access server settings  via gnome gui in trusty I get a
  cups server error: "There was an HTTP error: Not found."

  Adding/removing printers with the gui works fine. The server settings
  are accessible via a web browser and the web interface.

  system-config-printer --debug (when calling the settings menu entry):
  Connected as user kiran
  Authentication pass: 1
  Authentication: password callback set
  PolicyKit call to FileGet did not work: dbus.String(u'Not Found')
  Authentication pass: 2
  Forbidden: False
  Authentication: Try as root
  Connected as user root
  Authentication pass: 3
  Forbidden: False
  Authentication: giving up

  cups access.log:
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -

  cups error.log:
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] No authentication data provided.
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username=""
  D [28/Jul/2014:13:41:23 +0200] [Client 16] WWW-Authenticate: Basic 
realm="CUPS", trc="y"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Authorized as root using PeerCred
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username="root"
  I [28/Jul/2014:13:41:23 +0200] [Client 16] Files/directories such as 
"/etc/cups/cupsd.conf" must be world-readable.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing because Keep-Alive disabled
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not i

[Touch-packages] [Bug 1349387] Re: server settings are inaccessible

[Bruno Nova]

The update was to fix CVE-2014-3537 (as mentioned above).
But that fix is incomplete: CVE-2014-5029 (not fixed in Ubuntu yet: 
http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-5029.html)

CUPS developers know of this regression: https://cups.org/str.php?L4461
There's also a fix in that bug report, already shipped for Debian, and another 
patch which was just added.
So this will be fixed, eventually.

@Marc Deslauriers, I subscribed you so that you are aware of this bug
report in Launchpad (even though you already are aware of the
regression).

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

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

Title:
  server settings are inaccessible

Status in “cups” package in Ubuntu:
  Confirmed
Status in “system-config-printer” package in Ubuntu:
  Invalid

Bug description:
  When trying to access server settings  via gnome gui in trusty I get a
  cups server error: "There was an HTTP error: Not found."

  Adding/removing printers with the gui works fine. The server settings
  are accessible via a web browser and the web interface.

  system-config-printer --debug (when calling the settings menu entry):
  Connected as user kiran
  Authentication pass: 1
  Authentication: password callback set
  PolicyKit call to FileGet did not work: dbus.String(u'Not Found')
  Authentication pass: 2
  Forbidden: False
  Authentication: Try as root
  Connected as user root
  Authentication pass: 3
  Forbidden: False
  Authentication: giving up

  cups access.log:
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -

  cups error.log:
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] No authentication data provided.
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username=""
  D [28/Jul/2014:13:41:23 +0200] [Client 16] WWW-Authenticate: Basic 
realm="CUPS", trc="y"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState

[Touch-packages] [Bug 1349387] Re: server settings are inaccessible

[Bruno Nova]

** Changed in: system-config-printer (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  server settings are inaccessible

Status in “cups” package in Ubuntu:
  Confirmed
Status in “system-config-printer” package in Ubuntu:
  Invalid

Bug description:
  When trying to access server settings  via gnome gui in trusty I get a
  cups server error: "There was an HTTP error: Not found."

  Adding/removing printers with the gui works fine. The server settings
  are accessible via a web browser and the web interface.

  system-config-printer --debug (when calling the settings menu entry):
  Connected as user kiran
  Authentication pass: 1
  Authentication: password callback set
  PolicyKit call to FileGet did not work: dbus.String(u'Not Found')
  Authentication pass: 2
  Forbidden: False
  Authentication: Try as root
  Connected as user root
  Authentication pass: 3
  Forbidden: False
  Authentication: giving up

  cups access.log:
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -

  cups error.log:
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] No authentication data provided.
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username=""
  D [28/Jul/2014:13:41:23 +0200] [Client 16] WWW-Authenticate: Basic 
realm="CUPS", trc="y"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Authorized as root using PeerCred
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username="root"
  I [28/Jul/2014:13:41:23 +0200] [Client 16] Files/directories such as 
"/etc/cups/cupsd.conf" must be world-readable.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing because Keep-Alive disabled
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [

[Touch-packages] [Bug 1349387] Re: server settings are inaccessible

[Bruno Nova]

It seems the check for the world-readable permission was added in the
latest security update.

"apt-get source cups", then open
cups-1.7.2/debian/patches/CVE-2014-3537.patch and look at these lines:

+ /*
+  * Similarly, if the file/directory does not have world read permissions, do
+  * not allow access...
+  */
+
+  if (!status && !(filestats->st_mode & S_IROTH))
+  {
+cupsdLogMessage(CUPSD_LOG_INFO, "[Client %d] Files/directories such as 
\"%s\" must be world-readable.", con->http.fd, filename);
+return (NULL);
+  }

That looks familiar.
The permissions of all CUPS files (especially the ones mentioned in the 
previous comment) should be revised. The world-readable bit may be missing in 
those files.
Also need to see why the permissions of /etc/cups/cupsd.conf are reverted when 
they are changed in the GUI and fix that.

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

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

Title:
  server settings are inaccessible

Status in “cups” package in Ubuntu:
  Confirmed
Status in “system-config-printer” package in Ubuntu:
  Confirmed

Bug description:
  When trying to access server settings  via gnome gui in trusty I get a
  cups server error: "There was an HTTP error: Not found."

  Adding/removing printers with the gui works fine. The server settings
  are accessible via a web browser and the web interface.

  system-config-printer --debug (when calling the settings menu entry):
  Connected as user kiran
  Authentication pass: 1
  Authentication: password callback set
  PolicyKit call to FileGet did not work: dbus.String(u'Not Found')
  Authentication pass: 2
  Forbidden: False
  Authentication: Try as root
  Connected as user root
  Authentication pass: 3
  Forbidden: False
  Authentication: giving up

  cups access.log:
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -

  cups error.log:
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] No authentication data provided.
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username=""
  D [28/Jul/2014:13:41:23 +0200] [Client 16] WWW-Authenticate: Basic 
realm="CUPS", trc="y"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domai

[Touch-packages] [Bug 1349387] Re: server settings are inaccessible

[Bruno Nova]

I think I found the cause of the problem! It's a permissions issue.

I enabled "LogLevel debug2" in /etc/cups/cupsd.conf, then opened error log with 
"tail -f /var/log/cups/error_log".
When I access, for example, the error log in the browser 
(http://localhost:631/admin/log/error_log), these interesting messages are 
printed:

I [22/Aug/2014:14:11:19 +0100] [Client 15] Files/directories such as 
"/var/log/cups/error_log" must be world-readable.
d [22/Aug/2014:14:11:19 +0100] [Client 15] cupsdSendError code=404, 
auth_type=0
D [22/Aug/2014:14:11:19 +0100] [Client 15] Closing because Keep-Alive 
disabled
D [22/Aug/2014:14:11:19 +0100] [Client 15] Closing connection.

And, indeed, the /var/log/cups/error_log file is not world-readable. In fact, 
the permissions are: -rw-r- root adm
If I run:

sudo chmod o+r /var/log/cups/error_log

then try to access the logs again, it works.

When trying to access the server settings through system-config-printer, the 
same messages are printed, but for the /etc/cups/cupsd.conf file.
Its permissions are: -rw-r- root lp

Running the chmod for that file fixes the issue, and lets you access the
server settings... until the OK button in that dialog is pressed. Then
the permissions are reverted and the problem appears again! That's why
the problem didn't occur in the first time.

Therefore, the problem is in cups, not in system-config-printer!
Changing the permissions (and not reverting them) would fix the problem, but I 
don't know what are the security implications.

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

Title:
  server settings are inaccessible

Status in “cups” package in Ubuntu:
  Confirmed
Status in “system-config-printer” package in Ubuntu:
  Confirmed

Bug description:
  When trying to access server settings  via gnome gui in trusty I get a
  cups server error: "There was an HTTP error: Not found."

  Adding/removing printers with the gui works fine. The server settings
  are accessible via a web browser and the web interface.

  system-config-printer --debug (when calling the settings menu entry):
  Connected as user kiran
  Authentication pass: 1
  Authentication: password callback set
  PolicyKit call to FileGet did not work: dbus.String(u'Not Found')
  Authentication pass: 2
  Forbidden: False
  Authentication: Try as root
  Connected as user root
  Authentication pass: 3
  Forbidden: False
  Authentication: giving up

  cups access.log:
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -

  cups error.log:
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] No authentication data provided.
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username=""
  D [28/Jul/2014:13:41:23 +0200] [Client 16] WWW-Authenticate: Basic 
realm="CUPS", trc="y"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canc

[Touch-packages] [Bug 1349387] Re: server settings are inaccessible

[Bruno Nova]

I've been trying to debug system-config-printer with pdb to find the bug.
In cupspk.py, line 118:

pk_retval = pk_function(*pk_args)

where FileGet is called (remote call?) to CUPS (when the configure menu
is pressed) with:

pk_args = ('/admin/conf/cupsd.conf', '/tmp/somefile')

it returns "Not Found".

If I go to "localhost:361/admin/conf/cupsd.conf" in Firefox, it also returns 
"Not Found".
Actually, if I try to access the logs from the CUPS Administration page in 
Firefox it also returns "Not Found".

So the bug is probably in CUPS.
Although it is strange that the 1st time that the Configure option is accessed, 
it worked.

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

Title:
  server settings are inaccessible

Status in “cups” package in Ubuntu:
  Confirmed
Status in “system-config-printer” package in Ubuntu:
  Confirmed

Bug description:
  When trying to access server settings  via gnome gui in trusty I get a
  cups server error: "There was an HTTP error: Not found."

  Adding/removing printers with the gui works fine. The server settings
  are accessible via a web browser and the web interface.

  system-config-printer --debug (when calling the settings menu entry):
  Connected as user kiran
  Authentication pass: 1
  Authentication: password callback set
  PolicyKit call to FileGet did not work: dbus.String(u'Not Found')
  Authentication pass: 2
  Forbidden: False
  Authentication: Try as root
  Connected as user root
  Authentication pass: 3
  Forbidden: False
  Authentication: giving up

  cups access.log:
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -

  cups error.log:
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] No authentication data provided.
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username=""
  D [28/Jul/2014:13:41:23 +0200] [Client 16] WWW-Authenticate: Basic 
realm="CUPS", trc="y"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusy

[Touch-packages] [Bug 1349387] Re: server settings are inaccessible

[Bruno Nova]

I discovered this problems as well today.

The first time I went (today) to the server settings to enable sharing, it 
worked fine.
After that, I was unable to open it again, always seeing the reported error. 
Even after a reboot.
Fortunately, the web interface was still working (open "http://localhost:631"; 
in the web browser).

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

Title:
  server settings are inaccessible

Status in “cups” package in Ubuntu:
  Confirmed
Status in “system-config-printer” package in Ubuntu:
  Confirmed

Bug description:
  When trying to access server settings  via gnome gui in trusty I get a
  cups server error: "There was an HTTP error: Not found."

  Adding/removing printers with the gui works fine. The server settings
  are accessible via a web browser and the web interface.

  system-config-printer --debug (when calling the settings menu entry):
  Connected as user kiran
  Authentication pass: 1
  Authentication: password callback set
  PolicyKit call to FileGet did not work: dbus.String(u'Not Found')
  Authentication pass: 2
  Forbidden: False
  Authentication: Try as root
  Connected as user root
  Authentication pass: 3
  Forbidden: False
  Authentication: giving up

  cups access.log:
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - - [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 401 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -
  localhost - root [28/Jul/2014:13:40:42 +0200] "GET /admin/conf/cupsd.conf 
HTTP/1.1" 404 0 - -

  cups error.log:
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 15] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:22 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:22 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] No authentication data provided.
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username=""
  D [28/Jul/2014:13:41:23 +0200] [Client 16] WWW-Authenticate: Basic 
realm="CUPS", trc="y"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] HTTP_STATE_WAITING Closing on EOF
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Closing connection.
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Accepted from localhost (Domain)
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Waiting for request.
  D [28/Jul/2014:13:41:23 +0200] cupsd is not idle any more, canceling shutdown.
  D [28/Jul/2014:13:41:23 +0200] [Client 16] GET /admin/conf/cupsd.conf HTTP/1.1
  D [28/Jul/2014:13:41:23 +0200] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
  D [28/Jul/2014:13:41:23 +0200] [Client 16] Authorized as root using PeerCred
  D [28/Jul/2014:13:41:23 +0200] cupsdIsAuthorized: username="root"
  I [28/Jul/2014:13:41:23 +0200] [Client 16] Files/directories such as 
"/etc/cups/cupsd.conf" must be world-read

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

[Bruno Nova]

Maybe what I mentioned above (unrelated to this bug) is due to the fix
to Bug #1170508. So, forget what I asked.

Just to repeat what I wrote 2 comments above: this bug is fixed for me.

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

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

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

[Bruno Nova]

On another completely unrelated note, when I disable dash blur in Unity Tweak, 
the shortcuts overlay, alt-tab, and shutdown dialogs all lose transparency in 
14.04. This didn't happen in 13.10.
Anyone else noticed this? (Sorry for asking this here)

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

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

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

[Bruno Nova]

Oh look, it has been fixed! At least for me.
The shortcuts overlay is now working in my laptop with 1336x768 resolution, 
Ubuntu 14.04, both with workspaces enabled and disabled!

Anyone else with the latest updates installed confirms this on 14.04?

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

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

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1061852] Re: Unity Application Lens slow to load

[Bruno Nova]

This is still a problem in 14.04.
It takes a long time for the applications to appear in the dash, when it should 
be instantaneous.

I have noticed that, after login, if I open the Alt+F2 scope (commands scope?), 
it seem that the applications/commands appear faster there.
After that, opening the Dash with the Super key is fast.

According to "ps aux", the command that is executed when the Alt+F2 scope is 
opened appears to be:
/usr/bin/unity-scope-loader applications/applications.scope 
applications/scopes.scope commands.scope
If I execute this command in a terminal after login, then wait some seconds and 
open the Dash, the applications show a lot faster (under 2 seconds if the hard 
drive is not busy).

So, a workaround could be to add that command to the startup applications.
I'm using this now (I added a delay of 30 seconds), and it seems to work.
It crashed after the first reboot, though, but it didn't happen again.

As said in #8, I think the applications lens (and the other local ones?)
should be preloaded at startup (in a way that doesn't slow down the
boot/login process).

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

Title:
  Unity Application Lens slow to load

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

Bug description:
  WHAT HAPPENS
  --
  Log into the system
  Launch the dash with the 'window' key
  Start typing 'chr'...

  I see my files appearing in the search results
  The application lens results appear ~10 - 15 seconds later

  WHAT IS DESIRABLE
  ---
  The application lens results appear immediately

  
  Most users would login into the system and launch a web browser
  Optimal unity experience demands that their browser or mail client shows up 
in the dash instantaneously

  Also this behaviour has worsened recently (after upgrade to 12.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.16.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,resize,commands,place,regex,move,grid,session,snap,vpswitch,imgpng,gnomecompat,mousepoll,put,animation,compiztoolbox,expo,wall,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell]
  Date: Fri Oct  5 01:13:34 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

[Bruno Nova]

Same problem here.

I have seen the same behavior described in #7.
The title bar problem occurs when I use spread (Super+W), type something until 
only 1 window appears, and select it (using either keyboard or mouse).
This breaks the title bar integration with the top panel for all windows (even 
those not maximized, visible when I then try to maximize them) EXCEPT for the 
window that I selected in spread mode.

This happens with both global menu and locally integrated menus.

The fix is easy for me, though. Just open the spread mode (Super+W) and
select any window or press Escape, and the problem is fixed for all
windows.

Also, I've seen the title in the top bar sometimes appear below the
close/minimize/maximize (with locally integrated menus, at least) after
using the spread mode. But it's not very consistent (and it's probably a
different bug).

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

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

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

Bug description:
  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  Try this out using Terminal.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon May  5 14:48:01 2014
  InstallationDate: Installed on 2013-09-08 (239 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130424)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago)

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

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