[Touch-packages] [Bug 2059742] Re: Gdebi : unable to resize details window

[Coeur Noir]

Changing gdebi.ui in /usr/share/gdebi
as suggested above does the trick in 22.04.

May anyone check in 24.04 ?

** Attachment added: "Resizable window !"
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/2059742/+attachment/5767493/+files/2204_gdebi_after_new_ui.png

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

Title:
  Gdebi : unable to resize details window

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 24.04

  For years now, it's very uncomfortable to (try to ) use gdebi because
  the « details » window can't be resized.

  Attached is a funny example where there are 480 packages to remove and
  9 to install, but the « details box » can only show 2 lines at once
  out of the list…

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2059742] Re: Gdebi : unable to resize details window

[Coeur Noir]

See also :

Same kind of readability issues in « Users and Groups ( provided by 
gnome-system-tools )
see https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1978245

which looks using the same kind of graphical toolkit.

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

Title:
  Gdebi : unable to resize details window

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 24.04

  For years now, it's very uncomfortable to (try to ) use gdebi because
  the « details » window can't be resized.

  Attached is a funny example where there are 480 packages to remove and
  9 to install, but the « details box » can only show 2 lines at once
  out of the list…

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2059742] Re: Gdebi : unable to resize details window

[Coeur Noir]

Maybe this might help ( from duplicate 1581425 )
http://bazaar.launchpad.net/~chamfay/gdebi/trunk/view/head:/data/gdebi.ui
comment #3

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

Title:
  Gdebi : unable to resize details window

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 24.04

  For years now, it's very uncomfortable to (try to ) use gdebi because
  the « details » window can't be resized.

  Attached is a funny example where there are 480 packages to remove and
  9 to install, but the « details box » can only show 2 lines at once
  out of the list…

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2059742] Re: Gdebi : unable to resize details window

[Coeur Noir]

Since actual replacement for snap-store is unable to deal with local .deb 
package,
a ( comfortable and reliable ) graphical utility for such a task is much needed.

** Description changed:

  Hi,
  
  Ubuntu 24.04
  
- For years now, it's very uncomfortable to (try) to use gdebi because the
- « details » window can't be resized.
+ For years now, it's very uncomfortable to (try to ) use gdebi because
+ the « details » window can't be resized.
  
- Attached is a funny example where there 480 packages to remove,
- but the « details » can only show 2 lines of the list…
+ Attached is a funny example where there are 480 packages to remove and 9
+ to install, but the « details box » can only show 2 lines at once out of
+ the list…
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  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 gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/2059742

Title:
  Gdebi : unable to resize details window

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 24.04

  For years now, it's very uncomfortable to (try to ) use gdebi because
  the « details » window can't be resized.

  Attached is a funny example where there are 480 packages to remove and
  9 to install, but the « details box » can only show 2 lines at once
  out of the list…

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1767700] Re: gdebi puts output all on one line

[Coeur Noir]

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

** This bug has been marked a duplicate of bug 2059742
   Gdebi : unable to resize details window

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

Title:
  gdebi puts output all on one line

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  In many cases, gdebi puts its output all on one line, which makes it
  impossible to follow, I'm pretty sure that the package installer
  delimits lines with only a , while is what's needed.

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


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

[Touch-packages] [Bug 1427638] Re: Extra package box does not expand with its window, rendering its contents unreadable

[Coeur Noir]

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

** This bug has been marked a duplicate of bug 2059742
   Gdebi : unable to resize details window

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

Title:
  Extra package box does not expand with its window, rendering its
  contents unreadable

Status in gdebi package in Ubuntu:
  Expired

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 14.10 with lubuntu-desktop
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  0.9.5.4
  3) What you expected to happen
  Look at attached screenshot:
  Window containing focused string "libjpeg62:i386"  should be 
resizable/adjustable to display more than 1 string  (automatically? manually?)
  4) What happened instead
  It's not resizable automatically nor I'm able to resize it to display more 
than 1 string

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


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

[Touch-packages] [Bug 2059742] Re: Gdebi : unable to resize details window

[Coeur Noir]

** Description changed:

  Hi,
  
  Ubuntu 24.04
  
  For years now, it's very uncomfortable to (try) to use gdebi because the
  « details » window can't be resized.
  
  Attached is a funny example where there 480 packages to remove,
- but the « details » can only 2 lines of the list…
+ but the « details » can only show 2 lines of the list…
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
-  LANG=fr_FR.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

** Attachment added: "gdebi only show two lines out of the missing dependencies"
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/2059742/+attachment/5767492/+files/2404_gdebi_dep.png

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

Title:
  Gdebi : unable to resize details window

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 24.04

  For years now, it's very uncomfortable to (try) to use gdebi because
  the « details » window can't be resized.

  Attached is a funny example where there 480 packages to remove,
  but the « details » can only show 2 lines of the list…

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1524053] Re: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line.

[Coeur Noir]

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

** This bug has been marked a duplicate of bug 2059742
   Gdebi : unable to resize details window

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

Title:
  Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu
  Session than a line.

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I've tried both Ubuntu Minimal+XFCE & Xubuntu 16.04
  This gravely affect of XFCE, Openbox session on Ubuntu 16.04.
  However this doesn't happen on Xubuntu 16.04 Session at all it shows 
dependencies list normally
  But on XFCE, Openbox session it only shows a line.

  We need more tester to  confirm other session as well such as:
  Unity, Ubuntu, KDE, Kubuntu, lxde, lxde, Lubuntu, Edubuntu, Mythbuntu,
  To confirm if it's only affect on non-Ubuntu flavor Sessions.
  or are they affect to all Sessions Except Xubuntu Session?

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


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

[Touch-packages] [Bug 1578396] Re: missing dependencies are not listed

[Coeur Noir]

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

** This bug is no longer a duplicate of bug 1524053
   Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session 
than a line.
** This bug has been marked a duplicate of bug 2059742
   Gdebi : unable to resize details window

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.
  

  2016-09-24 : other example here 
https://forum.ubuntu-fr.org/viewtopic.php?pid=21595751#p21595751
  

  2017-01-24 : See comment #3 from Faissal Chamekh on duplicate 1581425
  modify gdebi.ui mostly solves this issue in ubuntu 16.04 w/ unity.

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


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

[Touch-packages] [Bug 1581425] Re: gdebi details window don't show packages

[Coeur Noir]

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

** This bug is no longer a duplicate of bug 1524053
   Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session 
than a line.
** This bug has been marked a duplicate of bug 2059742
   Gdebi : unable to resize details window

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

Title:
  gdebi details window don't show packages

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm using gdebi (gtk GUI)
  and when i install some package and show the 'detail' window, i don't see any 
packages, may by some widget doesn't expand properly.

  System: Ubuntu Gnome 16.04 64bits

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


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

[Touch-packages] [Bug 2059742] [NEW] Gdebi : unable to resize details window

[Coeur Noir]

Public bug reported:

Hi,

Ubuntu 24.04

For years now, it's very uncomfortable to (try) to use gdebi because the
« details » window can't be resized.

Attached is a funny example where there 480 packages to remove,
but the « details » can only 2 lines of the list…

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdebi 0.9.5.7+nmu7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 29 02:43:00 2024
InstallationDate: Installed on 2024-03-28 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble wayland-session

** Attachment added: "2 lines only but more needed"
   
https://bugs.launchpad.net/bugs/2059742/+attachment/5760390/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202024-03-29%2002-42-22.png

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

Title:
  Gdebi : unable to resize details window

Status in gdebi package in Ubuntu:
  New

Bug description:
  Hi,

  Ubuntu 24.04

  For years now, it's very uncomfortable to (try) to use gdebi because
  the « details » window can't be resized.

  Attached is a funny example where there 480 packages to remove,
  but the « details » can only 2 lines of the list…

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdebi 0.9.5.7+nmu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 02:43:00 2024
  InstallationDate: Installed on 2024-03-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Coeur Noir]

Ubuntu 24.04 installed today.

Firefox autonomous archive downloaded from
https://www.mozilla.org/fr/firefox/all/#product-desktop-release

And « ooops… » in any tab,

terminal says :

[Parent 5931, IPC I/O Parent] WARNING: process 6020 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6026 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6036 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6084 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6099 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6110 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6119 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6128 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6143 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6147 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 5931, IPC I/O Parent] WARNING: process 6150 exited on signal 11: file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265

…firefox as a snap looks to run fine but I have many bwrap processes that use 
100% cpu to the point of over-heating.
Is it related ?
See picture of monitor → https://i.ibb.co/BZCfNjJ/2404-bwrap.png

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Confirmed
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission 

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Coeur Noir]

THANK YOU !

…Ricoh Aficio now prints in colour by default, from Ubuntu 22.04, what a
relief !

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Fix Released
Status in okular package in Ubuntu:
  Invalid
Status in cups source package in Jammy:
  Fix Released
Status in cups source package in Lunar:
  Fix Released

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

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


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

[Touch-packages] [Bug 2027979] Re: won't warn neither prevent usage of « risky » characters in labels

[Coeur Noir]

Ok, ok, amen, so be it.

If it's ok in fstab, if bash always expands correctly then you're right,
don't change anything if it would bring more annoyance than ease of
life.

Title is « won't warn neither prevent usage of « risky » characters in labels »
Nothing else.

Accented letters in partition label seem ( nowadays ) a problem with
latest Ubuntu installer - as reported by geole on the forum ( am just
quoting here as I was unable to do anything with the latest Ubuntu
installer by my side, so can't confirm myself. )

No backpedaling from me - your bad reading because you jumped on
accented letters while I always was worrying about the « special / risky
» characters and insisted twice on that matter.

« Why should we print some kind of nanny-state, "naughty, naughty! you did 
something that might confuse a less clueful user!!" warning »
Because that's how you catch attention on a topic and eventually teach someone 
how to do better, for self and others.

Anyway thank you for your answers and explanations which justify why e2label 
needs no change.
Labels can't be an issue if I understand correctly. 

( oot : foolproof is the first translation I've found for « à toute
épreuve » ; bulletproof ? )

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

Title:
  won't warn neither prevent usage of « risky » characters in labels

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  if naming or renaming an EXT volume,

  e2label lets you use any character, including / or * or $ ( and
  probably others, like accented letters é è à )

  I'd expect at least a warning if such are to be found in a label name.

  Or better, it should not be possible to use those in label names.

  Example :

  a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
  a@p:~$

  a@p:~$ sudo e2label /dev/sdb12
  /Ti$*
  a@p:~$

  a@p:~$ lsblk -fe7 | grep sdb12
  └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
  a@p:~$

  coming from https://forum.ubuntu-
  fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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


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

[Touch-packages] [Bug 2027979] Re: won't warn neither prevent usage of « risky » characters in labels

[Coeur Noir]

A warning if « special » characters are used in labels might be a first
step in the right direction.

Once again accented letters and diacritics are not the problem here
but characters that might get « translated » as « functions » such as / \ * and 
few others.

Only those.

Space character is rather well managed by auto-completion in most CLI.
Mostly.

It's not least common denominator but only the few characters that could be « 
risky ».
All other characters remain possible.

And it's not only about « uneducated user », it's just safer for
everyone by making labels more robust and « foolproof ».

But hey am just the stupid user ( sheep ) and you are the upstream maintainer ( 
god ).
You could make e2label smarter but you can't make users smarter after all…
So be it ?

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

Title:
  won't warn neither prevent usage of « risky » characters in labels

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  if naming or renaming an EXT volume,

  e2label lets you use any character, including / or * or $ ( and
  probably others, like accented letters é è à )

  I'd expect at least a warning if such are to be found in a label name.

  Or better, it should not be possible to use those in label names.

  Example :

  a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
  a@p:~$

  a@p:~$ sudo e2label /dev/sdb12
  /Ti$*
  a@p:~$

  a@p:~$ lsblk -fe7 | grep sdb12
  └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
  a@p:~$

  coming from https://forum.ubuntu-
  fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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


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

[Touch-packages] [Bug 2027979] Re: won't warn neither prevent usage of « risky » characters in labels

[Coeur Noir]

You misread the case here, Theodore.
It's not a problem of language - accented letters and diacritics are used in 
many languages and might be used in labels.

Sorry for me just being a stupid downstream user. Such names with «
special » characters in are a flawed design as they have high potential
for confusion ( both for human and system. )

As in your example

foo\$bar → becomes → 'foo\x24bar' → not exactly the same form, which
might not be expected by uneducated user. And ( legitimately ) escaped
but not usable « as is » in all context.



In fact, there's nothing wrong with using any of these characters in
file system labels.

Of course, there's something wrong about using *some* of those characters / \ 
space * $ #
Accented letters are not the issue ( except with new Ubuntu installer… )

What will be the output of

cd /path/to/{ any label containing / or * or $ or spaces in its name }

if { label name } is not escaped ?

To prevent user from any later confusion, e2label should at least gives
a warning if « special » characters are used inside a label.

And my opinion is that e2label should strictly prevent using those « special » 
characters inside label.
While those can be « managed » with escaping, « names » in paths should never 
create confusion, so avoiding by default / or $ or * sound safer to me.

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

Title:
  won't warn neither prevent usage of « risky » characters in labels

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  if naming or renaming an EXT volume,

  e2label lets you use any character, including / or * or $ ( and
  probably others, like accented letters é è à )

  I'd expect at least a warning if such are to be found in a label name.

  Or better, it should not be possible to use those in label names.

  Example :

  a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
  a@p:~$

  a@p:~$ sudo e2label /dev/sdb12
  /Ti$*
  a@p:~$

  a@p:~$ lsblk -fe7 | grep sdb12
  └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
  a@p:~$

  coming from https://forum.ubuntu-
  fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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


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

[Touch-packages] [Bug 2027979] Re: won't warn neither prevent usage of « risky » characters in labels

[Coeur Noir]

« Hence, this feature request should not be considered a security
feature »

Nobody said it was a security feature.

But I surely think it's inappropriate that an utility allows to create «
flawed » labels.

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

Title:
  won't warn neither prevent usage of « risky » characters in labels

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  if naming or renaming an EXT volume,

  e2label lets you use any character, including / or * or $ ( and
  probably others, like accented letters é è à )

  I'd expect at least a warning if such are to be found in a label name.

  Or better, it should not be possible to use those in label names.

  Example :

  a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
  a@p:~$

  a@p:~$ sudo e2label /dev/sdb12
  /Ti$*
  a@p:~$

  a@p:~$ lsblk -fe7 | grep sdb12
  └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
  a@p:~$

  coming from https://forum.ubuntu-
  fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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


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

[Touch-packages] [Bug 2027979] Re: won't warn neither prevent usage of « risky » characters in labels

[Coeur Noir]

** Description changed:

  Hi,
  
  if naming or renaming an EXT volume,
  
  e2label lets you use any character, including / or * or $ ( and probably
- others )
+ others, like accented letters é è à )
  
  I'd expect at least a warning if such are to be found in a label name.
  
  Or better, it should not be possible to use those in label names.
  
- 
  Example :
  
  a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
- a@p:~$ 
+ a@p:~$
  
  a@p:~$ sudo e2label /dev/sdb12
  /Ti$*
- a@p:~$ 
+ a@p:~$
  
  a@p:~$ lsblk -fe7 | grep sdb12
- └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
- a@p:~$ 
+ └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
+ a@p:~$
  
  coming from https://forum.ubuntu-
  fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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

Title:
  won't warn neither prevent usage of « risky » characters in labels

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Hi,

  if naming or renaming an EXT volume,

  e2label lets you use any character, including / or * or $ ( and
  probably others, like accented letters é è à )

  I'd expect at least a warning if such are to be found in a label name.

  Or better, it should not be possible to use those in label names.

  Example :

  a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
  a@p:~$

  a@p:~$ sudo e2label /dev/sdb12
  /Ti$*
  a@p:~$

  a@p:~$ lsblk -fe7 | grep sdb12
  └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
  a@p:~$

  coming from https://forum.ubuntu-
  fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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


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

[Touch-packages] [Bug 2027979] [NEW] won't warn neither prevent usage of « risky » characters in labels

[Coeur Noir]

Public bug reported:

Hi,

if naming or renaming an EXT volume,

e2label lets you use any character, including / or * or $ ( and probably
others )

I'd expect at least a warning if such are to be found in a label name.

Or better, it should not be possible to use those in label names.


Example :

a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
a@p:~$ 

a@p:~$ sudo e2label /dev/sdb12
/Ti$*
a@p:~$ 

a@p:~$ lsblk -fe7 | grep sdb12
└─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
a@p:~$ 

coming from https://forum.ubuntu-
fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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

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

Title:
  won't warn neither prevent usage of « risky » characters in labels

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Hi,

  if naming or renaming an EXT volume,

  e2label lets you use any character, including / or * or $ ( and
  probably others )

  I'd expect at least a warning if such are to be found in a label name.

  Or better, it should not be possible to use those in label names.

  
  Example :

  a@p:~$ sudo e2label /dev/sdb12 /Ti\$*
  a@p:~$ 

  a@p:~$ sudo e2label /dev/sdb12
  /Ti$*
  a@p:~$ 

  a@p:~$ lsblk -fe7 | grep sdb12
  └─sdb12   ext4  1.0   /Ti$* 
f583e9b0-f1de-438f-8da8-c1e070407628
  a@p:~$ 

  coming from https://forum.ubuntu-
  fr.org/viewtopic.php?pid=22692892#p22692892 ( french )

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Coeur Noir]

…yes please, sru emergency, ubuntu 20.04 LTS variants reach EOL.

It's been more than a year now color printing is out of order in some
context.

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Coeur Noir]

Has this been fixed in 22.04 LTS ?

I'd like to use that version of Ubuntu at my work place where color
printing is needed…

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Coeur Noir]

A workaround suggested by a CUPS developer is to issue the command:

lpadmin -p PRINTER -o print-color-mode-default=color


Is this a permanent workaround or shall I have to issue that command each time 
printing needed ?

( the latter is not practicable in my context - many users, many
machines… )

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Coeur Noir]

Is this fixed in 22.10 ? Will it be fixed in 22.04 LTS ?

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Touch-packages] [Bug 1910913] Re: Deprecating gdebi

[Coeur Noir]

https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053 ?

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

Title:
  Deprecating gdebi

Status in gdebi package in Ubuntu:
  Invalid

Bug description:
  Purpose of gdebi is to allow installing packages from a file. However,
  it's been 6 years since apt supported installation from a file¹. Let's
  make it easier on both maintainers and the people who have to
  install/use `gdebi` and then may need to search nuances, like passing
  options to dpkg.

  As far as I read gdebi man page, its functional seems fully covered by
  apt. The only thing I'm a bit in doubts about is the `root` option.
  But from my reading of docs, it seems that `gdebi --root=/foo
  myfile.deb` would be analogous to `apt install -o Dpkg::Options::="--
  root=/foo" ./myfile.deb`.

  So, my suggesttion: installing gdebi on currently supported releases
  should print a deprecation notice that explains how a user can install
  local files with `apt` instead. Then eventually remove gdebi from
  repositories.

  I tried contacting maintainers of gdebi to ask whether it's worth
  adding a deprecation notice, but haven't found any ways to do that,
  and so I went straight to creating a report here.

  1: https://mvogt.wordpress.com/2015/11/30/apt-1-1-released/

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


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

[Touch-packages] [Bug 1524053] Re: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line.

[Coeur Noir]

Soon 7 years later, no improvement ?

On 22.04 the part of window showing needed dependencies won't resize,
only 3~4 lines displayed.

Same kind of readability issues in « Users and Groups ( provided by 
gnome-system-tools )
see https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1978245

** Attachment added: "gdebi window that does not resize accordingly to its 
content."
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053/+attachment/5620446/+files/gdebi.png

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

Title:
  Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu
  Session than a line.

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I've tried both Ubuntu Minimal+XFCE & Xubuntu 16.04
  This gravely affect of XFCE, Openbox session on Ubuntu 16.04.
  However this doesn't happen on Xubuntu 16.04 Session at all it shows 
dependencies list normally
  But on XFCE, Openbox session it only shows a line.

  We need more tester to  confirm other session as well such as:
  Unity, Ubuntu, KDE, Kubuntu, lxde, lxde, Lubuntu, Edubuntu, Mythbuntu,
  To confirm if it's only affect on non-Ubuntu flavor Sessions.
  or are they affect to all Sessions Except Xubuntu Session?

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


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

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Coeur Noir]

Hi.

It's not « limited » to pdf.

It's a regression as it used to work out of the box before 22.04.

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[Coeur Noir]

Seems fixed in or not affecting other distributions :

https://ubuntuforums.org/showthread.php?t=2476796=3=14104102#post14104102

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[Coeur Noir]

Some dmesg outputs from same machine running 20.04 and 22.04 :

## 20.04 ##

django@ASGARD:~$ dmesg | grep -Ei "ata4|sector|mtd"
[0.668757] ata4: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a280 
irq 29
[0.985537] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[0.986510] ata4.00: ATA-8: Hitachi HDS721010CLA332, JP4OA3MA, max UDMA/133
[0.986812] ata4.00: ATA Identify Device Log not supported
[0.986815] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[0.990241] ata4.00: ATA Identify Device Log not supported
[0.990245] ata4.00: configured for UDMA/133
[0.990254] ata3.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 32), AA

django@ASGARD:~$ dmesg | grep -Ei "erro|warn|fail"
[0.461495] RAS: Correctable Errors collector initialized.
[0.637675] ACPI Warning: SystemIO range 
0x1828-0x182F conflicts with OpRegion 
0x1800-0x187F (\PMIO) (20210730/utaddress-204)
[0.637701] ACPI Warning: SystemIO range 
0x1C40-0x1C4F conflicts with OpRegion 
0x1C00-0x1FFF (\GPR) (20210730/utaddress-204)
[0.637717] ACPI Warning: SystemIO range 
0x1C30-0x1C3F conflicts with OpRegion 
0x1C00-0x1C3F (\GPRL) (20210730/utaddress-204)
[0.637723] ACPI Warning: SystemIO range 
0x1C30-0x1C3F conflicts with OpRegion 
0x1C00-0x1FFF (\GPR) (20210730/utaddress-204)
[0.637741] ACPI Warning: SystemIO range 
0x1C00-0x1C2F conflicts with OpRegion 
0x1C00-0x1C3F (\GPRL) (20210730/utaddress-204)
[0.637746] ACPI Warning: SystemIO range 
0x1C00-0x1C2F conflicts with OpRegion 
0x1C00-0x1FFF (\GPR) (20210730/utaddress-204)
[0.987186] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
[0.988437] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to 
previous error (AE_NOT_FOUND) (20210730/psparse-529)
[0.991691] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
[0.994698] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to 
previous error (AE_NOT_FOUND) (20210730/psparse-529)
[5.955272] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro. Quota mode: 
none.

## 22.04 ##

django@ASGARD:~$ sudo dmesg | grep -Ei "ata4|sector|mtd"
[sudo] Mot de passe de django : 
[0.749555] ata4: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a280 
irq 29
[1.063160] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[1.064160] ata4.00: ATA-8: Hitachi HDS721010CLA332, JP4OA3MA, max UDMA/133
[1.064490] ata4.00: ATA Identify Device Log not supported
[1.064502] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[1.065584] ata3.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 
32), AA
[1.065959] ata4.00: ATA Identify Device Log not supported
[1.065962] ata4.00: configured for UDMA/133
[5.500484] systemd[1]: Starting Load Kernel Module mtdpstore...
[5.509953] mtd device must be supplied (device name is empty)
[6.096722] mtd device must be supplied (device name is empty)
[   35.920387] ata4.00: exception Emask 0x10 SAct 0x4000 SErr 0x489 action 
0xe frozen
[   35.920394] ata4.00: irq_stat 0x0c400040, interface fatal error, connection 
status changed
[   35.920395] ata4: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
[   35.920398] ata4.00: failed command: READ FPDMA QUEUED
[   35.920399] ata4.00: cmd 60/b8:70:00:a2:df/00:00:5b:00:00/40 tag 14 ncq dma 
94208 in
[   35.920415] ata4.00: status: { DRDY }
[   35.920418] ata4: hard resetting link
[   39.236175] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   39.237909] ata4.00: ATA Identify Device Log not supported
[   39.239613] ata4.00: ATA Identify Device Log not supported
[   39.239625] ata4.00: configured for UDMA/133
[   39.239679] blk_update_request: I/O error, dev sdb, sector 
1541382656 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[   39.239721] ata4: EH complete

django@ASGARD:~$ sudo dmesg | grep -Ei "erro|warn|fail"
[0.539349] RAS: Correctable Errors collector initialized.
[0.718130] ACPI Warning: SystemIO range 
0x1828-0x182F conflicts with OpRegion 
0x1800-0x187F (\PMIO) (20210730/utaddress-204)
[0.718821] ACPI Warning: SystemIO range 
0x1C40-0x1C4F conflicts with OpRegion 
0x1C00-0x1FFF (\GPR) (20210730/utaddress-204)
[0.718830] ACPI Warning: SystemIO range 
0x1C30-0x1C3F conflicts with OpRegion 
0x1C00-0x1C3F (\GPRL) (20210730/utaddress-204)
[0.718835] ACPI Warning: SystemIO 

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[Coeur Noir]

Same message here on « regular » Ubuntu 22.04 installed in legacy mode
on an UEFI capable bios.

No nvme/M2 here - system on SSD + data on HDD.

See attached file for dmesg it's line 941 at [6.780126]

Wonder if « failed » messages regarding sdb later at lines 980 and
following [   35.056956] are anyhow related ?


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+attachment/5603717/+files/dmesg.txt

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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

[Touch-packages] [Bug 1910913] Re: Deprecating gdebi

[Coeur Noir]

Are you suggesting an only CLI path to install .deb ?

Ok, nowadays right click on a .deb might open gnome-software and the
likes but those « stores » are much heavier to run and somehow less
informative regarding the action of installing just one .deb ( missing
dependencies… )

gdebi is / was a graphical enough utility for that purpose, but… see
picture attached.


** Attachment added: "window won't resize according to its content."
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1910913/+attachment/5596167/+files/gdebi.png

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

Title:
  Deprecating gdebi

Status in gdebi package in Ubuntu:
  New

Bug description:
  Purpose of gdebi is to allow installing packages from a file. However,
  it's been 6 years since apt supported installation from a file¹. Let's
  make it easier on both maintainers and the people who have to
  install/use `gdebi` and then may need to search nuances, like passing
  options to dpkg.

  As far as I read gdebi man page, its functional seems fully covered by
  apt. The only thing I'm a bit in doubts about is the `root` option.
  But from my reading of docs, it seems that `gdebi --root=/foo
  myfile.deb` would be analogous to `apt install -o Dpkg::Options::="--
  root=/foo" ./myfile.deb`.

  So, my suggesttion: installing gdebi on currently supported releases
  should print a deprecation notice that explains how a user can install
  local files with `apt` instead. Then eventually remove gdebi from
  repositories.

  I tried contacting maintainers of gdebi to ask whether it's worth
  adding a deprecation notice, but haven't found any ways to do that,
  and so I went straight to creating a report here.

  1: https://mvogt.wordpress.com/2015/11/30/apt-1-1-released/

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


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

[Touch-packages] [Bug 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.

[Coeur Noir]

disk space is cheap → this becomes an infuriating answer. Is cheap where ? For 
who ?
Whatever price it is, one might want to use it for something else than log ( on 
a desktop pc ).

Here
https://answers.launchpad.net/ubuntu/+source/systemd/+question/691873 is
another example of what may happen. Less than 4GB but above 10% of
remaining space. This led to system complaining about storage.

Shouldn't this « journal » be set by default to free space automatically
on desktop computer ?

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

Title:
  systemd journals take up a lot of space, and it's not obvious how much
  is used, and what the upper limit is.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After running Bionic for 3 months, I had 2.6 GB of journals.

  I would not expect from a normal desktop user that they should have to
  run commands like `sudo journalctl --vacuum-time=10d`.

  I would nominate this command as a sane default to have running at
  each reboot to ensure that logs do not exceed 500 MB:

  sudo journalctl --vacuum-size=500M

  Supposedly, a server should by default retain more logs, so perhaps
  this should be implemented through a configuration package "systemd-
  configuration-desktop" as a dependency of the ubuntu-desktop meta
  package?

  
  . as it turns out, it's hard to see how much disk space is used, and what 
the upper limit is, even when it is set and respected by default.

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

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

[Touch-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages

[Coeur Noir]

Not fixed in Budgie Ubuntu, where file-roller gets launched instead of
software.

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Fix Released
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

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

[Touch-packages] [Bug 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.

[Coeur Noir]

For reference, another example : https://discourse.ubuntubudgie.org/t
/journalctl-takes-much-storage-has-no-config/3927

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

Title:
  systemd journals take up a lot of space, and it's not obvious how much
  is used, and what the upper limit is.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After running Bionic for 3 months, I had 2.6 GB of journals.

  I would not expect from a normal desktop user that they should have to
  run commands like `sudo journalctl --vacuum-time=10d`.

  I would nominate this command as a sane default to have running at
  each reboot to ensure that logs do not exceed 500 MB:

  sudo journalctl --vacuum-size=500M

  Supposedly, a server should by default retain more logs, so perhaps
  this should be implemented through a configuration package "systemd-
  configuration-desktop" as a dependency of the ubuntu-desktop meta
  package?

  
  . as it turns out, it's hard to see how much disk space is used, and what 
the upper limit is, even when it is set and respected by default.

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

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

[Touch-packages] [Bug 1883457] Re: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.

[Coeur Noir]

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

** No longer affects: thumbnailer (Ubuntu)

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

Title:
  Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.

Status in gimp package in Ubuntu:
  New

Bug description:
  Hi,

  On Ubuntu ( Budgie ) 20.04 when using Gimp as a snap, you’ll see
  thumbnails for .xcf files only « inside » Gimp and nowhere else (
  Nemo, Nautilus, gThumb… )

  I did a messy workaround for .xcf thumbnails to appear anywhere
  expected : I put all of my user’s thumbnails into
  ~/snap/gimp/common/.cache/thumbnails/ and now ~/.cache/thumbnails/ is
  a symlink targeting the first.

  You’d agree it’s absolutely a bad idea to store all of an user’s
  thumbnails into a particular subfolder of a particular snap.

  How tell my session to look for thumbnails not only in
  ~/.cache/thumbnails/ but also in any thumbnails folder inside ~/snap/
  ?

  For references :
  ⋅ 
https://askubuntu.com/questions/1250031/gimp-snap-and-thumbnails-for-xcf-files
  ⋅ 
https://discourse.ubuntubudgie.org/t/gimp-as-a-snap-no-thumbnails-for-xcf-files-in-nemo-gthumb/3799
  ⋅ 
https://forum.snapcraft.io/t/gimp-and-thumbnails-for-xcf-files/18131/3?u=coeur-noir
  ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2053949

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

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

[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

[Coeur Noir]

Oooh sadness ! My flickering problem is back since those recent updates
from official regular repositories :

coeur-noir@asgard:~$ dpkg -l | grep mesa
ii  libegl-mesa0:amd64  19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the EGL API -- Mesa vendor 
library
ii  libegl1-mesa:amd64  19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  libgl1-mesa-dri:amd64   19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-dri:i38619.2.1-1ubuntu1~18.04.1 
i386 free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-glx:amd64   19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  libgl1-mesa-glx:i38619.2.1-1ubuntu1~18.04.1 
i386 transitional dummy package
ii  libglapi-mesa:amd64 19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the GL API -- shared library
ii  libglapi-mesa:i386  19.2.1-1ubuntu1~18.04.1 
i386 free implementation of the GL API -- shared library
ii  libgles2-mesa:amd64 19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  libglu1-mesa:amd64  9.0.0-2.1build1 
amd64Mesa OpenGL utility library (GLU)
ii  libglu1-mesa:i386   9.0.0-2.1build1 
i386 Mesa OpenGL utility library (GLU)
ii  libglx-mesa0:amd64  19.2.1-1ubuntu1~18.04.1 
amd64free implementation of the OpenGL API -- GLX vendor 
library
ii  libglx-mesa0:i386   19.2.1-1ubuntu1~18.04.1 
i386 free implementation of the OpenGL API -- GLX vendor 
library
ii  libosmesa6:amd6419.2.1-1ubuntu1~18.04.1 
amd64Mesa Off-screen rendering extension
ii  libosmesa6:i386 19.2.1-1ubuntu1~18.04.1 
i386 Mesa Off-screen rendering extension
ii  libwayland-egl1-mesa:amd64  19.2.1-1ubuntu1~18.04.1 
amd64transitional dummy package
ii  mesa-utils  8.4.0-1 
amd64Miscellaneous Mesa GL utilities
ii  mesa-utils-extra8.4.0-1 
amd64Miscellaneous Mesa utilies (opengles, egl)
ii  mesa-va-drivers:amd64   19.2.1-1ubuntu1~18.04.1 
amd64Mesa VA-API video acceleration drivers
ii  mesa-vdpau-drivers:amd6419.2.1-1ubuntu1~18.04.1 
amd64Mesa VDPAU video acceleration drivers
ii  mesa-vulkan-drivers:amd64   19.2.1-1ubuntu1~18.04.1 
amd64Mesa Vulkan graphics drivers
coeur-noir@asgard:~$

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in mesa package in Ubuntu:
  Confirmed
Status in supertuxkart package in Ubuntu:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c0000-dffff
  coeur-noir@asgard:~$

  My Ubuntu Bu

[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.

[Coeur Noir]

Just a reminder.

Here is an Unity session on 18.04. Base installation is UBudgie on which
I later add Unity packages.

It's a DE that has some components in common with Gnome.

And since Kikito seems to have the same problem of date-time
localization also in a default gnome session, who reports to ?

** Attachment added: "unity, installed after budgie"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+attachment/5309085/+files/Capture%20du%202019-12-01%2015-45-58.png

** Summary changed:

- Clock : incorrect date format in FR in Unity panel …bionic.
+ Clock : incorrect date format in panel

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

Title:
  Clock : incorrect date format in panel

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Here is Ubuntu 18.04 with Unity session ( I know… )

  System language and regional settings are set to French.

  In regional setting the date reads

  day number month year hour minute…

  which is correct for French.

  But the clock in the Unity panel reads

  day month number year hour minute…

  which looks more English than French order.

  Any config file I might edit to make my clock « more French » ?

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

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

[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

[Coeur Noir]

Ok.

I almost copied/pasted :
https://gitlab.freedesktop.org/mesa/mesa/issues/2011

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #2011
   https://gitlab.freedesktop.org/mesa/mesa/issues/2011

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in mesa package in Ubuntu:
  Confirmed
Status in supertuxkart package in Ubuntu:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c0000-dffff
  coeur-noir@asgard:~$

  My Ubuntu Budgie 18.04 is :
  coeur-noir@asgard:~$ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  coeur-noir@asgard:~$ uname -a
  Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  coeur-noir@asgard:~$ 

  mesa packages are :
  coeur-noir@asgard:~$ dpkg -l | grep mesa
  ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the EGL API -- Mesa vendor 
library
  ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1   
i386 transitional dummy package
  ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the GL API -- shared library
  ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the GL API -- shared library
  ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libglu1-mesa:amd64  9.0.0-2.1build1   
amd64Mesa OpenGL utility library (GLU)
  ii  libglu1-mesa:i386   9.0.0-2.1build1   
i386 Mesa OpenGL utility library (GLU)
  ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- GLX vendor 
library
  ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- GLX vendor 
library
  ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1   
amd64Mesa Off-screen rendering extension
  ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1   
i386 Mesa Off-screen rendering extension
  ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  mesa-utils  8.4.0-1   
amd64Miscellaneous Mesa GL utilities
  ii  mesa-utils-extra8.4.0-1   
amd64Miscellaneous Mesa utilies (opengles, egl)
  ii  mesa-va-drivers:amd64   

[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

[Coeur Noir]

As I feared from trying with Ubuntu 19.10, using
ppa:ubuntu-x-swat/updates on 18.04 did not fix the flickering-shadows
problem.

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in mesa package in Ubuntu:
  Incomplete
Status in supertuxkart package in Ubuntu:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c0000-dffff
  coeur-noir@asgard:~$

  My Ubuntu Budgie 18.04 is :
  coeur-noir@asgard:~$ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  coeur-noir@asgard:~$ uname -a
  Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  coeur-noir@asgard:~$ 

  mesa packages are :
  coeur-noir@asgard:~$ dpkg -l | grep mesa
  ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the EGL API -- Mesa vendor 
library
  ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1   
i386 transitional dummy package
  ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the GL API -- shared library
  ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the GL API -- shared library
  ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libglu1-mesa:amd64  9.0.0-2.1build1   
amd64Mesa OpenGL utility library (GLU)
  ii  libglu1-mesa:i386   9.0.0-2.1build1   
i386 Mesa OpenGL utility library (GLU)
  ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- GLX vendor 
library
  ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- GLX vendor 
library
  ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1   
amd64Mesa Off-screen rendering extension
  ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1   
i386 Mesa Off-screen rendering extension
  ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  mesa-utils  8.4.0-1   
amd64Miscellaneous Mesa GL utilities
  ii  mesa-utils-extra8.4.0-1   
amd64Miscellaneous Mesa utilies (opengles, egl)
  ii  mesa-va-drivers:amd64   19.0.8-0ubuntu0~18.04.1   
amd64Mesa VA

[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

[Coeur Noir]

I'll try that and report, thanks.

Meanwhile I have tried with Ubuntu ( default ) 19.10 and same problem…

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in mesa package in Ubuntu:
  Incomplete
Status in supertuxkart package in Ubuntu:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c0000-dffff
  coeur-noir@asgard:~$

  My Ubuntu Budgie 18.04 is :
  coeur-noir@asgard:~$ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  coeur-noir@asgard:~$ uname -a
  Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  coeur-noir@asgard:~$ 

  mesa packages are :
  coeur-noir@asgard:~$ dpkg -l | grep mesa
  ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the EGL API -- Mesa vendor 
library
  ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1   
i386 transitional dummy package
  ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the GL API -- shared library
  ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the GL API -- shared library
  ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libglu1-mesa:amd64  9.0.0-2.1build1   
amd64Mesa OpenGL utility library (GLU)
  ii  libglu1-mesa:i386   9.0.0-2.1build1   
i386 Mesa OpenGL utility library (GLU)
  ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- GLX vendor 
library
  ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- GLX vendor 
library
  ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1   
amd64Mesa Off-screen rendering extension
  ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1   
i386 Mesa Off-screen rendering extension
  ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  mesa-utils  8.4.0-1   
amd64Miscellaneous Mesa GL utilities
  ii  mesa-utils-extra8.4.0-1   
amd64Miscellaneous Mesa utilies (opengles, egl)
  ii  mesa-va-drivers:amd64   19.0.8-0ubuntu0~18.04.1   
amd64Mesa VA-API video acceleration dr

[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

[Coeur Noir]

Anyway remember I have no flickering shadows problem when booting the
same computer on 16.04.

So it's a regression but how narrow down any culprit ?

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

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

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in Mesa:
  New
Status in xf86-video-intel:
  New
Status in mesa package in Ubuntu:
  New
Status in supertuxkart package in Ubuntu:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c0000-dffff
  coeur-noir@asgard:~$

  My Ubuntu Budgie 18.04 is :
  coeur-noir@asgard:~$ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  coeur-noir@asgard:~$ uname -a
  Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  coeur-noir@asgard:~$ 

  mesa packages are :
  coeur-noir@asgard:~$ dpkg -l | grep mesa
  ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the EGL API -- Mesa vendor 
library
  ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1   
i386 transitional dummy package
  ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the GL API -- shared library
  ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the GL API -- shared library
  ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libglu1-mesa:amd64  9.0.0-2.1build1   
amd64Mesa OpenGL utility library (GLU)
  ii  libglu1-mesa:i386   9.0.0-2.1build1   
i386 Mesa OpenGL utility library (GLU)
  ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- GLX vendor 
library
  ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- GLX vendor 
library
  ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1   
amd64Mesa Off-screen rendering extension
  ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1   
i386 Mesa Off-screen rendering extension
  ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  mesa-utils  8.4.0-1   
amd64Miscellaneous Mesa GL utilities
  ii  mesa-u

[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

[Coeur Noir]

** Also affects: xserver-xorg-video-intel
   Importance: Undecided
   Status: New

** Package changed: mesa (Ubuntu) => mesa

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in Mesa:
  New
Status in xf86-video-intel:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c-d
  coeur-noir@asgard:~$

  My Ubuntu Budgie 18.04 is :
  coeur-noir@asgard:~$ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  coeur-noir@asgard:~$ uname -a
  Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  coeur-noir@asgard:~$ 

  mesa packages are :
  coeur-noir@asgard:~$ dpkg -l | grep mesa
  ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the EGL API -- Mesa vendor 
library
  ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1   
i386 transitional dummy package
  ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the GL API -- shared library
  ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the GL API -- shared library
  ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libglu1-mesa:amd64  9.0.0-2.1build1   
amd64Mesa OpenGL utility library (GLU)
  ii  libglu1-mesa:i386   9.0.0-2.1build1   
i386 Mesa OpenGL utility library (GLU)
  ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- GLX vendor 
library
  ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- GLX vendor 
library
  ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1   
amd64Mesa Off-screen rendering extension
  ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1   
i386 Mesa Off-screen rendering extension
  ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  mesa-utils  8.4.0-1   
amd64Miscellaneous Mesa GL utilities
  ii  mesa-utils-extra8.4.0-1   
amd64Miscellaneous Mesa utilies (opengles, egl)
  ii  mesa-va-drivers:amd64   19.0.8-0ubuntu0~18.04.1   
amd64Mesa VA-API video acceleration drivers
  i

[Touch-packages] [Bug 1841953] [NEW] Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

[Coeur Noir]

Public bug reported:

Hi,

for few weeks now, I've noticed a big change in graphic performance
while playing famous SuperTuxKart on ubuntu bionic :

shadows are flickering, all over the screen, it's a big pain for eyes (
and wonder what would happen for epileptic people ).

My computer is :
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
coeur-noir@asgard:~$ sudo lshw -c video
  *-display 
   description: VGA compatible controller
   produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
   fabriquant: Intel Corporation
   identifiant matériel: 2
   information bus: pci@:00:02.0
   version: 06
   bits: 64 bits
   horloge: 33MHz
   fonctionnalités: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c0000-dffff
coeur-noir@asgard:~$

My Ubuntu Budgie 18.04 is :
coeur-noir@asgard:~$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
coeur-noir@asgard:~$ uname -a
Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
coeur-noir@asgard:~$ 

mesa packages are :
coeur-noir@asgard:~$ dpkg -l | grep mesa
ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the EGL API -- Mesa vendor library
ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 
  i386 free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 
  i386 transitional dummy package
ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the GL API -- shared library
ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1 
  i386 free implementation of the GL API -- shared library
ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  libglu1-mesa:amd64  9.0.0-2.1build1 
  amd64Mesa OpenGL utility library (GLU)
ii  libglu1-mesa:i386   9.0.0-2.1build1 
  i386 Mesa OpenGL utility library (GLU)
ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the OpenGL API -- GLX vendor 
library
ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1 
  i386 free implementation of the OpenGL API -- GLX vendor 
library
ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 
  amd64Mesa Off-screen rendering extension
ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 
  i386 Mesa Off-screen rendering extension
ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  mesa-utils  8.4.0-1 
  amd64Miscellaneous Mesa GL utilities
ii  mesa-utils-extra8.4.0-1 
  amd64Miscellaneous Mesa utilies (opengles, egl)
ii  mesa-va-drivers:amd64   19.0.8-0ubuntu0~18.04.1 
  amd64Mesa VA-API video acceleration drivers
ii  mesa-vdpau-drivers:amd6419.0.8-0ubuntu0~18.04.1 
  amd64Mesa VDPAU video acceleration drivers
coeur-noir@asgard:~$ 

SuperTuxKart version is :
coeur-noir@asgard:~$ dpkg -l | grep supertu
ii  supertuxkart1.0~ubuntu18.04.1   
  amd643D kart racing game
ii  supertuxkart-data   1.0~ubuntu18.04.1   
  all  3D kart racing game (data)
coeur-noir@asgard:~$ 

IMPORTANT NOTE #1 : I 

[Touch-packages] [Bug 1790021] [NEW] Apport warns about perl crashes …many times a day

[Coeur Noir]

Public bug reported:

Hi,

Ubuntu 18.04, I noticed this on Ubuntu-Budgie and Xubuntu ( different
machines / or partitions ) as far I can tell I did not notice it yet on
default-ubuntu :

apport is triggered many times a day because of /usr/bin/perl crashes

I can't see a pattern to trigger that myself.

I don't use myself directly perl…

…I hit continue and presumably sent the bug report.

Attached an example screenshot from Budgie.

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

** Attachment added: "perl crashed with SIGABRT in_dbus_abort()"
   
https://bugs.launchpad.net/bugs/1790021/+attachment/5182835/+files/crash_usr_bin_perl.png

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

Title:
  Apport warns about perl crashes …many times a day

Status in perl package in Ubuntu:
  New

Bug description:
  Hi,

  Ubuntu 18.04, I noticed this on Ubuntu-Budgie and Xubuntu ( different
  machines / or partitions ) as far I can tell I did not notice it yet
  on default-ubuntu :

  apport is triggered many times a day because of /usr/bin/perl crashes

  I can't see a pattern to trigger that myself.

  I don't use myself directly perl…

  …I hit continue and presumably sent the bug report.

  Attached an example screenshot from Budgie.

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

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

[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.

[Coeur Noir]

@kikito you're not under Unity neither under Bionic 18.04 ;-)

But it seems your clock is also à l'Anglaise…

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

Title:
  Clock : incorrect date format in FR in Unity panel …bionic.

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Here is Ubuntu 18.04 with Unity session ( I know… )

  System language and regional settings are set to French.

  In regional setting the date reads

  day number month year hour minute…

  which is correct for French.

  But the clock in the Unity panel reads

  day month number year hour minute…

  which looks more English than French order.

  Any config file I might edit to make my clock « more French » ?

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

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

[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.

[Coeur Noir]

Thank you Khurshid Alam that's exactly what I was looking for !

That does not fix the default clock non-matching the locale clock
settings but it allows to have a customized clock.

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

Title:
  Clock : incorrect date format in FR in Unity panel …bionic.

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Here is Ubuntu 18.04 with Unity session ( I know… )

  System language and regional settings are set to French.

  In regional setting the date reads

  day number month year hour minute…

  which is correct for French.

  But the clock in the Unity panel reads

  day month number year hour minute…

  which looks more English than French order.

  Any config file I might edit to make my clock « more French » ?

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

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

[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.

[Coeur Noir]

coeurnoir-1804@ASGARD:~$ locale
LANG=fr_FR.UTF-8
LANGUAGE=fr_FR:fr_CA:en
LC_CTYPE="fr_FR.UTF-8"
LC_NUMERIC=fr_FR.UTF-8
LC_TIME=fr_FR.UTF-8
LC_COLLATE="fr_FR.UTF-8"
LC_MONETARY=fr_FR.UTF-8
LC_MESSAGES="fr_FR.UTF-8"
LC_PAPER=fr_FR.UTF-8
LC_NAME=fr_FR.UTF-8
LC_ADDRESS=fr_FR.UTF-8
LC_TELEPHONE=fr_FR.UTF-8
LC_MEASUREMENT=fr_FR.UTF-8
LC_IDENTIFICATION=fr_FR.UTF-8
LC_ALL=
coeurnoir-1804@ASGARD:~$ 


** Attachment added: "Illustration of difference between clock format vs clock 
displayed"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1787297/+attachment/5176517/+files/clock_format_and_displayed.png

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

Title:
  Clock : incorrect date format in FR in Unity panel …bionic.

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Here is Ubuntu 18.04 with Unity session ( I know… )

  System language and regional settings are set to French.

  In regional setting the date reads

  day number month year hour minute…

  which is correct for French.

  But the clock in the Unity panel reads

  day month number year hour minute…

  which looks more English than French order.

  Any config file I might edit to make my clock « more French » ?

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

I can also confirm that un-installing dbus-user-session solved the
issue.

Does flatpak always install it / or only some app's ?

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

To illustrate an other side-effect :

coeurnoir@Asgard:~$ deja-dup --backup

** (deja-dup:2774): WARNING **: AssistantOperation.vala:732: Erreur lors
de l'appel de StartServiceByName pour org.freedesktop.secrets :
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate
service 'org.freedesktop.secrets': timed out

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

…flatpak may not be the source problem but it seems to bring something
that helps highlighting the problem… ( I suspect some gnome-related
parameters ).

I assume some other ppa's as well can bring the same problem, maybe by
comparing them we could narrow down a culprit ?

I can also confirm that once the problem surfaces it affects all the
users on the machine ( ubuntu 16.04 unity here ).

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

Is this any useful https://bugzilla.gnome.org/show_bug.cgi?id=784514 ?

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

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

…for a couple of hours then chromium says ( something like ) Error
occurs when trying to open your profile.


** Attachment added: "chromium having problem to open profile"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4908915/+files/Capture%20du%202017-07-04%2001-24-29.png

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

This bug also prevents Deja-dup / duplicity  from working.

Launching manually from terminal

gnome-keyring-daemon

seems to help a little.

When launching chromium password is asked but after that chromium and
any other app's seem to work fine.


** Attachment added: "if of any help ps -fux"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4908906/+files/ps%20-fux

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

Well… now the problem happens on all the users-sessions but the error
message is little different :

alessandra@Asgard:~$ chromium-browser 
Using PPAPI flash.
 --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[5958:5995:0702/224636.598323:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-118233930601834352306

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Coeur Noir]

Affected here on Ubuntu 16.04 Unity.

I noticed it on trying to launch chromium-browser, it takes very long
with errors

coeurnoir@Asgard:~$ chromium-browser 
Using PPAPI flash.
 --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[14639:14687:0702/211518.780149:ERROR:crx_installer.cc(735)] Impossible de 
charger l'icône de l'extension "icons/192.png". 
edcifkpoamnkimdpjiabhfjahoinbpbps

Only one user-session out of 3 on the same machine seems affected for
the moment.

On the affected session I installed yesterday flatpak from
ppa:alexlarsson/flatpak in order to try latest version of pitivi.
Installing pitivi through flatpak asked to connect to gnome3.22 related
stuff … any hint there ? Because chromium get slow right after that
installation.

I did uninstall pitivi through flatpak command, then ppa-purged flatpak
but things did not get better.

Screen-capture by keyboard-shortcut is also very slow ( it finally
happens when chromium stops hanging ).

Same story in french there → https://forum.ubuntu-
fr.org/viewtopic.php?id=2011625

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1690354] [NEW] If default zoom in nautilus set to ≠ 100% icons have different sizes

[Coeur Noir]

Public bug reported:

Hello,

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1687411

Are there any missing icons in the package ? ( for xml and deb files )

Here is what happens if zoom in nautilus is set to ≠ 100% on my Ubuntu 16.04.2
https://launchpadlibrarian.net/317825735/Capture%20du%202017-05-01.png

** Affects: humanity-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
   If default zoom in nautilus set to ≠ 100% icons have different sizes

Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  Hello,

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1687411

  Are there any missing icons in the package ? ( for xml and deb files )

  Here is what happens if zoom in nautilus is set to ≠ 100% on my Ubuntu 16.04.2
  https://launchpadlibrarian.net/317825735/Capture%20du%202017-05-01.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1690354/+subscriptions

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

[Touch-packages] [Bug 1524053] Re: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line.

[Coeur Noir]

See comment #3 from Faissal Chamekh on duplicate 1581425 :

modify gdebi.ui mostly solves this issue in ubuntu 16.04 w/ unity.

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

Title:
  Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu
  Session than a line.

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  I've tried both Ubuntu Minimal+XFCE & Xubuntu 16.04
  This gravely affect of XFCE, Openbox session on Ubuntu 16.04.
  However this doesn't happen on Xubuntu 16.04 Session at all it shows 
dependencies list normally
  But on XFCE, Openbox session it only shows a line.

  We need more tester to  confirm other session as well such as:
  Unity, Ubuntu, KDE, Kubuntu, lxde, lxde, Lubuntu, Edubuntu, Mythbuntu,
  To confirm if it's only affect on non-Ubuntu flavor Sessions.
  or are they affect to all Sessions Except Xubuntu Session?

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

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

[Touch-packages] [Bug 1578396] Re: missing dependencies are not listed

[Coeur Noir]

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

** Description changed:

  Hi,
  
  ubuntu 16.04 here.
  
  Using gdebi I've noticed it does not display the list of missing
  dependencies :
  
  http://hpics.li/6ca144f
  
  but yet works fine.
  
  
  2016-09-24 : other example here 
https://forum.ubuntu-fr.org/viewtopic.php?pid=21595751#p21595751
  
  
- 2017-01-24 Any chance someone has an eye on this annoying
- display problem making gDebi almost unusable ?
+ 2017-01-24 : See comment #3 from Faissal Chamekh on duplicate 1581425
+ modify gdebi.ui mostly solves this issue in ubuntu 16.04 w/ unity.

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.
  

  2016-09-24 : other example here 
https://forum.ubuntu-fr.org/viewtopic.php?pid=21595751#p21595751
  

  2017-01-24 : See comment #3 from Faissal Chamekh on duplicate 1581425
  modify gdebi.ui mostly solves this issue in ubuntu 16.04 w/ unity.

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

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

[Touch-packages] [Bug 1581425] Re: gdebi details window don't show packages

[Coeur Noir]

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

** This bug has been marked a duplicate of bug 1578396
   missing dependencies are not listed

** This bug is no longer a duplicate of bug 1578396
   missing dependencies are not listed
** This bug has been marked a duplicate of bug 1524053
   Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session 
than a line.

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

Title:
  gdebi details window don't show packages

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm using gdebi (gtk GUI)
  and when i install some package and show the 'detail' window, i don't see any 
packages, may by some widget doesn't expand properly.

  System: Ubuntu Gnome 16.04 64bits

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

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

[Touch-packages] [Bug 1578396] Re: missing dependencies are not listed

[Coeur Noir]

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

** This bug has been marked a duplicate of bug 1524053
   Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session 
than a line.

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.
  

  2016-09-24 : other example here 
https://forum.ubuntu-fr.org/viewtopic.php?pid=21595751#p21595751
  

  2017-01-24 Any chance someone has an eye on this annoying
  display problem making gDebi almost unusable ?

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

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

[Touch-packages] [Bug 1578396] Re: missing dependencies are not listed

[Coeur Noir]

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

** Description changed:

  Hi,
  
  ubuntu 16.04 here.
  
  Using gdebi I've noticed it does not display the list of missing
  dependencies :
  
  http://hpics.li/6ca144f
  
  but yet works fine.
  
  
- 2016-09-24 : other example here https://forum.ubuntu-
- fr.org/viewtopic.php?pid=21595751#p21595751
+ 2016-09-24 : other example here 
https://forum.ubuntu-fr.org/viewtopic.php?pid=21595751#p21595751
+ 
+ 
+ 2017-01-24 Any chance someone has an eye on this annoying
+ display problem making gDebi almost unusable ?

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.
  

  2016-09-24 : other example here 
https://forum.ubuntu-fr.org/viewtopic.php?pid=21595751#p21595751
  

  2017-01-24 Any chance someone has an eye on this annoying
  display problem making gDebi almost unusable ?

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

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

[Touch-packages] [Bug 1635426] Re: whoopsie : many messages in dmesg, bug or actual system problem ?

[Coeur Noir]

** Also affects: whoopsie
   Importance: Undecided
   Status: New

** Description changed:

  Hi,
  
  I noticed dmesg shows many messages regarding whoopsie.
  
  Monitor shows whoopsie uses sometimes 18% cpu and 4Go ram, slowing down
  the system.
  
- apport-bug seems to be triggered but can't be sent.
+ apport-bug seems to be triggered but report can't be sent.
  
  Hence the question : is it a bug regarding whoopsie or has my system got
  a problem ?
  
  complete dmesg → http://paste2.org/dIF376Jf
  
  screenshot apport-bug → http://hpics.li/e149ffd
  
  Of course uninstalling whoopsie package no longer shows messages in
  dmesg but might not be the better workaround ;-)
  
  Ubuntu 14.04 - xenial LTSEnablementStack :
  palace4@ANTEC:~$ uname -a
  Linux ANTEC 4.4.0-45-generic #66~14.04.1-Ubuntu SMP Wed Oct 19 15:05:38 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

** Tags added: 14.04 whoopsie

** Tags added: dmesg

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

Title:
  whoopsie : many messages in dmesg, bug or actual system problem ?

Status in Whoopsie:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,

  I noticed dmesg shows many messages regarding whoopsie.

  Monitor shows whoopsie uses sometimes 18% cpu and 4Go ram, slowing
  down the system.

  apport-bug seems to be triggered but report can't be sent.

  Hence the question : is it a bug regarding whoopsie or has my system
  got a problem ?

  complete dmesg → http://paste2.org/dIF376Jf

  screenshot apport-bug → http://hpics.li/e149ffd

  Of course uninstalling whoopsie package no longer shows messages in
  dmesg but might not be the better workaround ;-)

  Ubuntu 14.04 - xenial LTSEnablementStack :
  palace4@ANTEC:~$ uname -a
  Linux ANTEC 4.4.0-45-generic #66~14.04.1-Ubuntu SMP Wed Oct 19 15:05:38 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1635426] [NEW] whoopsie : many messages in dmesg, bug or actual system problem ?

[Coeur Noir]

Public bug reported:

Hi,

I noticed dmesg shows many messages regarding whoopsie.

Monitor shows whoopsie uses sometimes 18% cpu and 4Go ram, slowing down
the system.

apport-bug seems to be triggered but can't be sent.

Hence the question : is it a bug regarding whoopsie or has my system got
a problem ?

complete dmesg → http://paste2.org/dIF376Jf

screenshot apport-bug → http://hpics.li/e149ffd

Of course uninstalling whoopsie package no longer shows messages in
dmesg but might not be the better workaround ;-)

Ubuntu 14.04 - xenial LTSEnablementStack :
palace4@ANTEC:~$ uname -a
Linux ANTEC 4.4.0-45-generic #66~14.04.1-Ubuntu SMP Wed Oct 19 15:05:38 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

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

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

Title:
  whoopsie : many messages in dmesg, bug or actual system problem ?

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,

  I noticed dmesg shows many messages regarding whoopsie.

  Monitor shows whoopsie uses sometimes 18% cpu and 4Go ram, slowing
  down the system.

  apport-bug seems to be triggered but can't be sent.

  Hence the question : is it a bug regarding whoopsie or has my system
  got a problem ?

  complete dmesg → http://paste2.org/dIF376Jf

  screenshot apport-bug → http://hpics.li/e149ffd

  Of course uninstalling whoopsie package no longer shows messages in
  dmesg but might not be the better workaround ;-)

  Ubuntu 14.04 - xenial LTSEnablementStack :
  palace4@ANTEC:~$ uname -a
  Linux ANTEC 4.4.0-45-generic #66~14.04.1-Ubuntu SMP Wed Oct 19 15:05:38 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1578396] Re: missing dependencies are not listed

[Coeur Noir]

** Description changed:

  Hi,
  
  ubuntu 16.04 here.
  
  Using gdebi I've noticed it does not display the list of missing
  dependencies :
  
  http://hpics.li/6ca144f
  
  but yet works fine.
+ 
+ 
+ 2016-09-24 : other example here https://forum.ubuntu-
+ fr.org/viewtopic.php?pid=21595751#p21595751

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.
  

  2016-09-24 : other example here https://forum.ubuntu-
  fr.org/viewtopic.php?pid=21595751#p21595751

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

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

[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads

[Coeur Noir]

And here are some other examples where removing
~/.cache/compizconfig-1
also helped.

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions

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

[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads

[Coeur Noir]

https://forum.ubuntu-fr.org/viewtopic.php?pid=21594335#p21594335

( sorry - why can't we edit comments ? )

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions

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

[Touch-packages] [Bug 1398008] Re: "Caps. Lock" LED keyboard indicator not working

[Coeur Noir]

Still happens in Unity 14.04 & 16.04

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

Title:
  "Caps. Lock" LED keyboard indicator not working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu Trusty running on an Apple MacBook 4,1 (white, early 2008)

  Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014
  x86_64 x86_64 x86_64 GNU/Linux

  "Caps. Lock" keyboard LED indicator remains always off even if the lock its 
activated and working properly when writing.
  This issue doesn't happens when in the session log screen. There it always 
works fine. Issue starts when loggin into my session account.

  I've 2 GB RAM, 4 GB SWAP space, /home and SWAP are encrypted.

  Please let me know if you ned further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec  1 08:58:24 2014
  DistUpgraded: 2014-08-12 15:32:20,840 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00a1]
 Subsystem: Apple Inc. Device [106b:00a1]
  InstallationDate: Installed on 2014-08-12 (110 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Apple Inc. MacBook4,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=bed91342-3e5e-483d-af89-b95cc986250e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-08-12 (110 days ago)
  dmi.bios.date: 02/09/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB41.88Z.00C1.B00.0802091535
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F22788A9
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22788A9
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
  dmi.product.name: MacBook4,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  1 08:25:50 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40031 
   vendor APP
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Touch-packages] [Bug 1013881] Re: Right-Ctrl key broken on French OSS keyboard

[Coeur Noir]

I also noticed actual versions of xkb-data & xkb-data-i18n in Ubuntu
14.04.4/5 broke again right-ctrl-key with french ( alternative )
keyboard.

I've fixed it installing versions from xenial, using dpkg command.

http://packages.ubuntu.com/xenial/xkb-data
http://packages.ubuntu.com/xenial/xkb-data-i18n

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

Title:
  Right-Ctrl key broken on French OSS keyboard

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Precise:
  Fix Released

Bug description:
  Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key 
of the keyboard has ceased to work.
  The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 
2.5-1ubuntu1.2.

  If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xkb-data 2.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu9
  Architecture: amd64
  Date: Sat Jun 16 00:16:09 2012
  Dependencies:
   
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  MachineType: LENOVO 4243E69
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic 
root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7
  SourcePackage: xkeyboard-config
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4243E69
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4243E69
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.19.0-0ubuntu1~xup1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions

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

[Touch-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Coeur Noir]

« After re-installing the unity-lens-applications the dash is working as
expected. » Not entirely as expected since it does not show available
applications to install see #1621106

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in bamf package in Ubuntu:
  In Progress
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in gnome-menus source package in Xenial:
  Fix Released
Status in libunity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  I am running 15.10 development version fully up to date, I installed it a few 
days ago and I have an issue with newly installed applications not appearing in 
the dash when I search for them, they can be started via console but the 
icons/launchers of newly installed applications will only appear in the dash 
after session is restarted.

  [Test case]
  1. Install a new applicaiton (using apt-get or the software center)
  2. Make sure the application is listed in the Unity Dash

  [Possible Regressions]
  Unity fails to list all the applications, not just the newly installed ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)Z

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

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

[Touch-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04

[Coeur Noir]

^e ^i …since yesterday dead keys don't work anymore on my ubuntu …
14.04.5 LTS.

And since yesterday I have problems with accented letters in 14.04 -
same problem I already have on 16.04 here bug #1599516

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

Title:
  Compose and dead keys stopped working with XIM after upgrade to 16.04

Status in firefox package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, entering characters using dead keys and
  using the Compose key stopped working in Gnome Terminal, acting like
  they are normal (non-dead) keys.

  Other applications, even those who use the same libvte (e.g. ROXTerm),
  don't have this issue.

  This happens with both the "Belgian" and "English international with
  AltGr dead keys" layouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  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: Fri Apr 22 20:45:33 2016
  InstallationDate: Installed on 2013-12-16 (857 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1584509] Re: hybrid CDs/DVDs not mounted in xenial

[Coeur Noir]

Or even easier maybe, install 16.04 packages for util-linux and libblkid1 from
- http://packages.ubuntu.com/xenial/util-linux
- http://packages.ubuntu.com/xenial/libblkid1

?

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

Title:
  hybrid CDs/DVDs not mounted in xenial

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released

Bug description:
  * Impact
  some CDs are not listed in the desktop UIs

  * Test case
  under unity7 insert a video DVD in your drive, you should get prompted about 
it and have the device listed in the launcher/nautilus

  * Regression potential
  check that devices keep being correctly listed/mounted

  

  This bug affects both the X64 and X32 bit versions of the latest
  ubuntu 16.04 it does not occur with ubuntu 15.10 or earlier.  The
  problem is when a known good CD-R is placed in the drive, it is not
  mounted automatically.  However, if it is a bootable CD-R and you
  select the boot option of the BIOS it will function normally.

  Also, When a blank CD-R is inserted into the drive, it is mounted
  automatically, but disk creation software reports an erroneous amount
  of free space available.  Such as 247 MB or 512 MB when the disk is a
  700 MB disk.  However, if you proceed to record to the disk, even with
  an ISO image greater than the supposed available capacity, it records
  just fine.

  Other disk types such as DVD, audio, small cd-r work fine.  This only
  seems to affect the larger, full size cd-r's

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  karl   1886 F pulseaudio
   /dev/snd/controlC0:  karl   1886 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 14:38:13 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=03cb5141-d254-414a-950b-2235e068035a
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2016-03-09 (73 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Gateway DX4380G
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=da27bf85-d849-43b8-a8f2-8fdac4f37784 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   14:38:31.725: The udisks-daemon is running (name-owner :1.96).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A1
  dmi.board.name: DX4380G
  dmi.board.vendor: Gateway
  dmi.board.version: 1.02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr:
  dmi.product.name: DX4380G
  dmi.sys.vendor: Gateway

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

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

[Touch-packages] [Bug 1584509] Re: hybrid CDs/DVDs not mounted in xenial

[Coeur Noir]

Hi SoKai, as stated in at top of the page, fix has been released for
Xenial ( lts version ) and I confirm it's solved the problem on my
machine.

There is a quite easy workaround that should also do the trick in 15.10
while waiting for its EoL :

https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1577768/comments/7

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

Title:
  hybrid CDs/DVDs not mounted in xenial

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released

Bug description:
  * Impact
  some CDs are not listed in the desktop UIs

  * Test case
  under unity7 insert a video DVD in your drive, you should get prompted about 
it and have the device listed in the launcher/nautilus

  * Regression potential
  check that devices keep being correctly listed/mounted

  

  This bug affects both the X64 and X32 bit versions of the latest
  ubuntu 16.04 it does not occur with ubuntu 15.10 or earlier.  The
  problem is when a known good CD-R is placed in the drive, it is not
  mounted automatically.  However, if it is a bootable CD-R and you
  select the boot option of the BIOS it will function normally.

  Also, When a blank CD-R is inserted into the drive, it is mounted
  automatically, but disk creation software reports an erroneous amount
  of free space available.  Such as 247 MB or 512 MB when the disk is a
  700 MB disk.  However, if you proceed to record to the disk, even with
  an ISO image greater than the supposed available capacity, it records
  just fine.

  Other disk types such as DVD, audio, small cd-r work fine.  This only
  seems to affect the larger, full size cd-r's

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  karl   1886 F pulseaudio
   /dev/snd/controlC0:  karl   1886 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 14:38:13 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=03cb5141-d254-414a-950b-2235e068035a
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2016-03-09 (73 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Gateway DX4380G
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=da27bf85-d849-43b8-a8f2-8fdac4f37784 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   14:38:31.725: The udisks-daemon is running (name-owner :1.96).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A1
  dmi.board.name: DX4380G
  dmi.board.vendor: Gateway
  dmi.board.version: 1.02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr:
  dmi.product.name: DX4380G
  dmi.sys.vendor: Gateway

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

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

[Touch-packages] [Bug 1578396] Re: missing dependencies are not listed

[Coeur Noir]

I've noticed yesterday the same kind of problem with ubuntu 14.04 :

whatever the size of gdebi's window, the box height where dependencies
are listed doesn't ever change. It keeps the same size and only two
lines of the list are shown yet there are more lines in the list.

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.

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

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

[Touch-packages] [Bug 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Coeur Noir]

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

Hi Bougron,

Wich is the version of libblkid on your system ?

My Ubuntu 16.04 is with 4.4.0-22 generic Kernel and libblkid1
2.27.1-6ubuntu3.1

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

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

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

[Touch-packages] [Bug 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Coeur Noir]

Do you think that « bug » in libblkid can also affect auto-mounting of
external hard drives and usb-stick storages ?

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

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

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

[Touch-packages] [Bug 1578396] [NEW] missing dependencies are not listed

[Coeur Noir]

Public bug reported:

Hi,

ubuntu 16.04 here.

Using gdebi I've noticed it does not display the list of missing
dependencies :

http://hpics.li/6ca144f

but yet works fine.

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

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

Title:
  missing dependencies are not listed

Status in gdebi package in Ubuntu:
  New

Bug description:
  Hi,

  ubuntu 16.04 here.

  Using gdebi I've noticed it does not display the list of missing
  dependencies :

  http://hpics.li/6ca144f

  but yet works fine.

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

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

[Coeur Noir]

Bug still existing in Ubuntu 15.10 → https://forum.ubuntu-
fr.org/viewtopic.php?pid=20947601#p20947601

I also met it with many 14.04 installation - running ibus-setup and
setting "use system keyboard layout" in advanced tab was and still is
the workaround.

-- 
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:
  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 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop

[Coeur Noir]

And not only under Unity environment but also other "flavors" (Lubuntu,
Xubuntu…) and other ubuntu based distro like elementaryOS.

-- 
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:
  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 1390625] Re: mouse cursor gets corrupted

[Coeur Noir]

Well I've read the posts and possible workarounds ;-)

Moreover I've read :

fix commited → fix released on 2015-09-04

so I'd like to know if I should do a full re-install of freya or if
updating is enough ?

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Fix Released
Status in Mesa:
  New
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted

[Coeur Noir]

Not totally fixed :

the "intermediate" state of mouse cursor is wrong - while holding left
click during dragging.


** Attachment added: "photo of screen, not screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-lts-utopic/+bug/1390625/+attachment/4457252/+files/DSC_0062.jpg

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Fix Released
Status in Mesa:
  New
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted

[Coeur Noir]

Another bunch of updates + a reboot later…

intermediate state of mouse of cursor is ok

BUT

once the drag and drop (to move a folder) is done

the "double-cursored-with-a-folder-icon" is back as mouse-cursor…

** Attachment added: "Other Photo"
   
https://bugs.launchpad.net/mesa/+bug/1390625/+attachment/4457265/+files/DSC_0063.jpg

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Fix Released
Status in Mesa:
  New
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted

[Coeur Noir]

and same behaviour with kernel 3.19.0-26.

Fix commited, or fix to be released in the future ?

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Fix Committed
Status in Mesa:
  New
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted

[Coeur Noir]

elementaryOS Freya here and this bug still occurs.

Intel Haswell HD4600

kernel 3.16.0-46

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Fix Committed
Status in Mesa:
  New
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1012081] Re: util-linux needs updating to 2.24.2

[Coeur Noir]

Bug still occurs in Ubuntu 14.04.1  freshly installed and updated.

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

Title:
  util-linux needs updating to 2.24.2

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Raring:
  Won't Fix
Status in util-linux package in Debian:
  Fix Released

Bug description:
  Applications in the default desktop - specifically gnome-disk-utility
  - depend on behaviour only introduced in util-linux 2.21+.
  Specifically if you select Show in user interface in mount options,
  it adds the mount option x-gvfs-show to the mount options in
  /etc/fstab. Mounting of this mount point then fails because the option
  is unrecognised.

  Also reported bug from the other point of view in bug #1011257

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.1.1-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 12 12:38:02 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to quantal on 2012-06-09 (3 days ago)

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

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

[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

[Coeur Noir]

After todays updates I've lost again the volume keys…

…but this time the sgettings commands had no effects to fix it.

Attached is screenshits of today's updates if any relevant ?

** Attachment added: historique logitheque
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302885/+attachment/4299148/+files/Capture%20du%202015-01-15%2013%3A14%3A52.png

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

Title:
  Media keyboard shortcuts not working

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:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

[Coeur Noir]

Sorry - lol - unintended typos ! please read :

gsettings instead of sgettings

and of course

screenshots instead of …

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

Title:
  Media keyboard shortcuts not working

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:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

[Coeur Noir]

I just have had that bug, with volume up and down keys no longer working
after changing some shortcuts through system parameters → keyboard →
shortcuts tab

Solved by :

gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-down
gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up

on Ubuntu 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/1302885

Title:
  Media keyboard shortcuts not working

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

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1284635] Re: IBus does not support certain keyboard layouts

[Coeur Noir]

On a fresh Lubuntu 14.04 install'

Fr_fr is my locale(s)

I aim to use Français(variante) keyboard.

I did choose these during installation from mini.iso with online
updates.

It works as expected most of the time.

But sometimes on the login-greeter screen although FR is mentioned on
the right of the panel it seems I have a US keyboard running - my
password containing @ and : and numbers I'm then lost !

Some other times it's in the expected french variant keyboard, but once
logged into the desktop, it's then US keyboard…

Some other times it all looks as expected but when I try to use remote-
desktop (reminna/vino or -sorry- TeamViewer) to reach that Lubuntu
computer, I have no num-keypad and once again the keyboard looks US
(can't find the @ and €)

And some other times everything work fine !

My clients pc for remote desktop are Ubuntu-Unity, with
Français(variante) keyboards.

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

Title:
  IBus does not support certain keyboard layouts

Status in “ibus” package in Ubuntu:
  Triaged
Status in “ibus” source package in Trusty:
  Triaged

Bug description:
  installed trusty beta1 with keyboard layout set correctly during
  install

  install completes, login to new install - layout as set during install

  once logged in - layout set to US and keyboard layout set during
  install is missing from list

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Feb 25 12:55:56 2014
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  PackageArchitecture: all
  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/ibus/+bug/1284635/+subscriptions

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

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

[Coeur Noir]

I don't use Evolution on my PC's but thunderbird (with add-ons to sync
lighting with google agendas and contacts)

And my thunderbird's still run ok despite of the bug.

I can confirm the bug is still there even after fresh install of ubuntu
14.04.

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Confirmed
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions

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

[Touch-packages] [Bug 1354067] Re: Auto-Login service for GMail accounts gives Applications can no longer access online account error

[Coeur Noir]

I don't use Evolution on my PC's but thunderbird (with add-ons to sync
lighting with google agendas and contacts)

And my thunderbird's still run ok despite of the bug.

I can confirm the bug is still there even after fresh install of ubuntu
14.04.

Even if Calendar + Contacts services are disabled.

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

Title:
  Auto-Login service for GMail accounts gives Applications can no
  longer access online account error

Status in “account-plugins” package in Ubuntu:
  Confirmed
Status in “friends” package in Ubuntu:
  Invalid

Bug description:
  The auto-login service for GMail accounts gives Applications can no
  longer access online accounts error everytime it attempts to connect.
  It also cannot sustain connections for other online services
  (facebook, yahoo, etc.) and requires me to grant access to the
  services again and again. I can confirm my passwords are correct.

  Also, granting access to yahoo mail and facebook works flawlessly, but
  the GMail 'Grant Access' interface is buggy, and just doesn't work.
  On entering password and clicking 'Done' it brings back the same
  screen, as though nothing happened. Over and over again. If you click
  cancel a few times, it brings you back to the screen with the list of
  online accounts, while it attempts to connect to the services, in
  vain. Also, overall the friends service is buggy. It doesn't show me
  notifications from facebook, nor has it synced events from my google
  calenders. I cannot tell you when this problem started exactly,
  neither can i guess what might have caused the problem. If you need
  some log files, please tell me, i'll upload them asap. I don't have
  accounts in many of the services listed there, so i might not be able
  to help you with other services. I really hope there's a solution to
  this, because its always lovely to see a well polished desktop
  environment :)

  I use Ubuntu 14.04 LTS (Trusty Tahr)

  Version of 'friends' package installed:
  0.2.0+14.04.20140217.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: friends-dispatcher 0.2.0+14.04.20140217.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  7 20:47:49 2014
  InstallationDate: Installed on 2014-04-20 (108 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: friends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Coeur Noir]

The workaround does not work for me :

Problem stays, even if calendar service is disabled.

By my side this problem has appeared since I have enabled the double
check process on Google account - where a code is sent by sms to mobile
phone to validate connection. Does it make sense ?

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released

Bug description:
  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions

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

[Touch-packages] [Bug 1354067] Re: Auto-Login service for GMail accounts gives Applications can no longer access online account error

[Coeur Noir]

Problem stays, even if calendar service is disabled.

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

Title:
  Auto-Login service for GMail accounts gives Applications can no
  longer access online account error

Status in “account-plugins” package in Ubuntu:
  Confirmed
Status in “friends” package in Ubuntu:
  Invalid

Bug description:
  The auto-login service for GMail accounts gives Applications can no
  longer access online accounts error everytime it attempts to connect.
  It also cannot sustain connections for other online services
  (facebook, yahoo, etc.) and requires me to grant access to the
  services again and again. I can confirm my passwords are correct.

  Also, granting access to yahoo mail and facebook works flawlessly, but
  the GMail 'Grant Access' interface is buggy, and just doesn't work.
  On entering password and clicking 'Done' it brings back the same
  screen, as though nothing happened. Over and over again. If you click
  cancel a few times, it brings you back to the screen with the list of
  online accounts, while it attempts to connect to the services, in
  vain. Also, overall the friends service is buggy. It doesn't show me
  notifications from facebook, nor has it synced events from my google
  calenders. I cannot tell you when this problem started exactly,
  neither can i guess what might have caused the problem. If you need
  some log files, please tell me, i'll upload them asap. I don't have
  accounts in many of the services listed there, so i might not be able
  to help you with other services. I really hope there's a solution to
  this, because its always lovely to see a well polished desktop
  environment :)

  I use Ubuntu 14.04 LTS (Trusty Tahr)

  Version of 'friends' package installed:
  0.2.0+14.04.20140217.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: friends-dispatcher 0.2.0+14.04.20140217.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  7 20:47:49 2014
  InstallationDate: Installed on 2014-04-20 (108 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: friends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1013881] Re: Right-Ctrl key broken on French OSS keyboard

[Coeur Noir]

@Dominique Meèus : how did you install xkb-data 2.12-1 in Trusty ? I've 
downloaded the .deb from https://packages.debian.org/sid/all/xkb-data/download 
but gdebi says : État : Erreur : n'est plus fourni xkb-data
I've tried through Logithèque which seems to install it (no error message) 
but still no classic right control key even after rebooting.
I'm using keyboard : Français (variante) and the keymap still shows level 5… 
under Right Ctrl key.

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

Title:
  Right-Ctrl key broken on French OSS keyboard

Status in central project for keyboard configuration:
  Fix Released
Status in “xkeyboard-config” package in Ubuntu:
  Fix Released
Status in “xkeyboard-config” source package in Precise:
  Fix Released

Bug description:
  Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key 
of the keyboard has ceased to work.
  The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 
2.5-1ubuntu1.2.

  If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xkb-data 2.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu9
  Architecture: amd64
  Date: Sat Jun 16 00:16:09 2012
  Dependencies:
   
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  MachineType: LENOVO 4243E69
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic 
root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7
  SourcePackage: xkeyboard-config
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4243E69
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4243E69
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.19.0-0ubuntu1~xup1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions

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

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

[Coeur Noir]

Here for me it's exactly the same as Franco #83 :
I am using Trusty since day one, but I started to experience this just 
recently, I guess after 14.04.1 was released… I have a regular Google account, 
too. Firefox keeps me logged in, Online Accounts doesn't. I don't have to 
reboot, on my system the bug is reproducible by turning off and on the Google 
account in the Online Accounts dialog

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released

Bug description:
  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions

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

[Touch-packages] [Bug 1354067] Re: Auto-Login service for GMail accounts gives Applications can no longer access online account error

[Coeur Noir]

I have this problem with gmail account too, since I have enabled the
double check process on Google account - where a code is sent by sms
to mobile phone to validate connection. Does it make sense ?

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

Title:
  Auto-Login service for GMail accounts gives Applications can no
  longer access online account error

Status in “friends” package in Ubuntu:
  Confirmed

Bug description:
  The auto-login service for GMail accounts gives Applications can no
  longer access online accounts error everytime it attempts to connect.
  It also cannot sustain connections for other online services
  (facebook, yahoo, etc.) and requires me to grant access to the
  services again and again. I can confirm my passwords are correct.

  Also, granting access to yahoo mail and facebook works flawlessly, but
  the GMail 'Grant Access' interface is buggy, and just doesn't work.
  On entering password and clicking 'Done' it brings back the same
  screen, as though nothing happened. Over and over again. If you click
  cancel a few times, it brings you back to the screen with the list of
  online accounts, while it attempts to connect to the services, in
  vain. Also, overall the friends service is buggy. It doesn't show me
  notifications from facebook, nor has it synced events from my google
  calenders. I cannot tell you when this problem started exactly,
  neither can i guess what might have caused the problem. If you need
  some log files, please tell me, i'll upload them asap. I don't have
  accounts in many of the services listed there, so i might not be able
  to help you with other services. I really hope there's a solution to
  this, because its always lovely to see a well polished desktop
  environment :)

  I use Ubuntu 14.04 LTS (Trusty Tahr)

  Version of 'friends' package installed:
  0.2.0+14.04.20140217.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: friends-dispatcher 0.2.0+14.04.20140217.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  7 20:47:49 2014
  InstallationDate: Installed on 2014-04-20 (108 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: friends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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