[Touch-packages] [Bug 1812536] [NEW] logrotate 3.14.0-4ubuntu2 error: /etc/logrotate.conf:7 unknown group 'admn'

2019-01-19 Thread iLogin
Public bug reported:

try to run version on proposed

sudo logrotate -f /etc/logrotate.conf 
[sudo] password for agent: 
error: /etc/logrotate.conf:7 unknown group 'admn'

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

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

Title:
  logrotate 3.14.0-4ubuntu2 error: /etc/logrotate.conf:7 unknown group
  'admn'

Status in logrotate package in Ubuntu:
  New

Bug description:
  try to run version on proposed

  sudo logrotate -f /etc/logrotate.conf 
  [sudo] password for agent: 
  error: /etc/logrotate.conf:7 unknown group 'admn'

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

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


[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-19 Thread Douglas Kosovic
I wasn't able to redirect the stderr from the following line in /etc/ppp
/ip-up.d/usepeerdns (probably because of something pppd is doing) :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

So I modified the cp.c source from the coreutils package and redirected
stderr to a file.

The error message I now see is :


cp: failed to preserve ownership for 
'/run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0': Operation not 
permitted


cp.c is using the lchown() function which is failing with that message.

Looks like only preserving ownership is failing as I tried the following
and it works:

cp --preserve=mode,timestamps "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-
backup.$PPP_IFACE"

The way /run is mounted might be the reason why 'cp -a' and lchown() is failing.
 

Ignore what I said able $? being 0 after the cp -a line. Doing the
following line confirms $? is 1 :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" || echo
ERROR $? >> /tmp/usepeerdns-up.log

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1812529] [NEW] file picker unexpected behavior

2019-01-19 Thread tetsuo29
Public bug reported:

OS: Ubuntu 18.10 x86_64 
Kernel: 4.18.0-13-generic 
DE: GNOME 3.30.1 
WM: GNOME Shell 

Every time I save a file, if I navigate to a different folder than the
one the save dialog appeared with, after I've selected the folder for
saving my file, if I just start typing, my keystrokes don't go into the
filename field even though that is the only field showing for editing
and the file name is highlighted in that field.

What happens instead? A search field magically appears and my keystrokes
start going there. In order to actually edit the file name, I'm required
to click the mouse in the file name field. And, clicking in the file
name field causes the filename to un-highlight, forcing me to press
Ctrl+A to re-highlight (now including the file extension).

This can't be by design can it? I'm not supposed to just retrain myself
to type the filename first and then navigate to the folder I want to
save in, am I?

Even if I was willing to do that, sometimes, I want to click on an
existing filename in a folder and then edit it. This requires navigating
to that folder first. This is worse. Why? Because if I start typing
right after clicking on an existing file it takes 2 clicks to be able to
start editing the filename after clicking an existing file.

I believe I should be able to navigate to a folder and as soon as I
start typing, be editing the file name (it's the only visible field for
editing and it has text highlighted in it like it has the focus).
There's no reason for a search field to appear just because I navigated
to a folder before beginning to edit a file name.

Also, if I click on an existing file, and that name loads in the file
name field, I should be able to immediately start typing to edit. I
should not have to click in the file name edit field 2x in order to be
able to start editing.

If I want to search instead of editing the file name, I should have to
click on a search button or use a keyboard shortcut to do that instead.
That would be the sane, expected way of doing things.

Please, please, fix this.

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

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

Title:
  file picker unexpected behavior

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 18.10 x86_64 
  Kernel: 4.18.0-13-generic 
  DE: GNOME 3.30.1 
  WM: GNOME Shell 

  Every time I save a file, if I navigate to a different folder than the
  one the save dialog appeared with, after I've selected the folder for
  saving my file, if I just start typing, my keystrokes don't go into
  the filename field even though that is the only field showing for
  editing and the file name is highlighted in that field.

  What happens instead? A search field magically appears and my
  keystrokes start going there. In order to actually edit the file name,
  I'm required to click the mouse in the file name field. And, clicking
  in the file name field causes the filename to un-highlight, forcing me
  to press Ctrl+A to re-highlight (now including the file extension).

  This can't be by design can it? I'm not supposed to just retrain
  myself to type the filename first and then navigate to the folder I
  want to save in, am I?

  Even if I was willing to do that, sometimes, I want to click on an
  existing filename in a folder and then edit it. This requires
  navigating to that folder first. This is worse. Why? Because if I
  start typing right after clicking on an existing file it takes 2
  clicks to be able to start editing the filename after clicking an
  existing file.

  I believe I should be able to navigate to a folder and as soon as I
  start typing, be editing the file name (it's the only visible field
  for editing and it has text highlighted in it like it has the focus).
  There's no reason for a search field to appear just because I
  navigated to a folder before beginning to edit a file name.

  Also, if I click on an existing file, and that name loads in the file
  name field, I should be able to immediately start typing to edit. I
  should not have to click in the file name edit field 2x in order to be
  able to start editing.

  If I want to search instead of editing the file name, I should have to
  click on a search button or use a keyboard shortcut to do that
  instead. That would be the sane, expected way of doing things.

  Please, please, fix this.

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

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


[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

2019-01-19 Thread Rainer Rohde
Here's my screencast as well:

https://launchpadlibrarian.net/397451009/Screencast%202018-11-13%2013%3A15%3A31.mp4

Sad that this seems to be an issue since 2016 which continues to exist.

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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


[Touch-packages] [Bug 1810728] Re: cups error - internal server error when adding a printer

2019-01-19 Thread asimsalam
The recent cups update has fixed this issue. Adding the Canon MG-6320
with LPD/DNS-SD was successful and prints jobs correctly.

** Changed in: cups (Ubuntu)
   Status: New => Fix Released

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

Title:
  cups error - internal server error when adding a printer

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  Where
  -
  This is happening on a fresh Linux Mint Tessa whose upstream is bionic
   cat /etc/upstream-release/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"

  What
  
  The upstream package is provided by the upstream bionic
  sudo apt policy cups
  cups:
Installed: 2.2.7-1ubuntu2.2
Candidate: 2.2.7-1ubuntu2.2
Version table:
   *** 2.2.7-1ubuntu2.2 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Problem Synopsis
  
  I have problem(s) printing with adding or printing to both my printers, one 
Dell and the other a Canon.

  The Dell E525 was added automatically but when printing to it the queue 
reports there was a problem with printing and the documents stays 'pending' in 
the queue.
  If I try to add the Canon MG6320 using the auto-detected entry for it, the 
addition fails and produces the error: cups error - internal server error.
  If I add it using the find function with the IP address, adding it succeeds 
but printing to it has the same problem as the Dell.

  This seems to be a regression/bug in cups that should be addressed.

  Please feel free to ask, if you need me to collect more info.

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

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


[Touch-packages] [Bug 1803176] Re: Search in Nautilus does not work correctly when called from other apps

2019-01-19 Thread Fernando
*** This bug is a duplicate of bug 1592177 ***
https://bugs.launchpad.net/bugs/1592177

** This bug has been marked a duplicate of bug 1592177
   Focus drops from search input in GtkFileChooserDialog after first character, 
which stops searching (broken behaviour)

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

Title:
  Search in Nautilus does not work correctly when called from other apps

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When Nautilus is called from another app, e.g., Thunderbird > Attach
  File to email (or Gedit > Save file) the search (via the magnifying
  glass icon in the top right) only allows for 1 character to be
  entered, and then jumps to the bottom right and subsequent characters
  appear there.

  This behavior, of course, messes up the expected search results as the
  search is split into two fields/areas of the panel.

  In contrast, when opening up a Nautilus browser panel directly, any
  search query entered from the magnifying glass icon stays in the text
  entry area as expected, and the search results work well.

  The expectation is that when another app calls Nautilus, the search
  function works as if it does when working directly out of Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 13:05:42 2018
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'"
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2018-10-27 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Touch-packages] [Bug 1803176] Re: Search in Nautilus does not work correctly when called from other apps

2019-01-19 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1592177 ***
https://bugs.launchpad.net/bugs/1592177

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Search in Nautilus does not work correctly when called from other apps

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When Nautilus is called from another app, e.g., Thunderbird > Attach
  File to email (or Gedit > Save file) the search (via the magnifying
  glass icon in the top right) only allows for 1 character to be
  entered, and then jumps to the bottom right and subsequent characters
  appear there.

  This behavior, of course, messes up the expected search results as the
  search is split into two fields/areas of the panel.

  In contrast, when opening up a Nautilus browser panel directly, any
  search query entered from the magnifying glass icon stays in the text
  entry area as expected, and the search results work well.

  The expectation is that when another app calls Nautilus, the search
  function works as if it does when working directly out of Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 13:05:42 2018
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'"
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2018-10-27 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Touch-packages] [Bug 362427] Re: Public key ssh auth doesn't work with my Encrypted Home Directory

2019-01-19 Thread Kip Warner
This looks like this is a problem that affects many but that there
doesn't appear to be any viable solution to. It seems as though the best
we can hope for is to configure sshd to look for the authorized_keys
outside the home directory while it is still unmounted, but all that
does is login to the machine but still leave the home directory
unmounted.

I think likely the only way to solve this was if upstream patched
ecryptfs to some how allow SSH key authentication. I don't know how
difficult that would be to do.

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

Title:
  Public key ssh auth doesn't work with my Encrypted Home Directory

Status in eCryptfs:
  Invalid
Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Spent all night to understand why public key ssh auth doesn't work. It
  seems to me that issue only affects Jaunty. Please have a look at the
  details below.

  So, the configuration is:

  1. Client
  - lsb_release: Ubuntu 8.10 intrepid
  - ssh-client: OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007

  2. Server A
  - lsb_release: Ubuntu 8.04.2 hardy
  - sshd: OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007

  3. Server B
  - lsb_release: Ubuntu 9.04 jaunty
  - sshd: OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007

  Server A and Server B have the same /etc/ssh/sshd_config:
  RSAAuthentication yes
  PubkeyAuthentication yes
  StrictModes no

  I turned StrictModes to "no", but every server has the same
  permissions on user's .ssh folder and .ssh/authorized_keys file.
  authorized_keys is the same on Server A and Server B.

  So, I am able to connect with public key from Client machine to Server
  A, but I can't connect to Server B.

  I run ssh client and sshd on Server B in debug mode, please find logs
  attached.

  Most important strings from auth.log:

  ...
  Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_request_receive entering
  Apr 16 20:58:47 ubuntu sshd[21728]: debug3: monitor_read: checking request 21
  Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_answer_keyallowed entering
  Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_answer_keyallowed: 
key_from_blob: 0xb9084978
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: Checking blacklist file 
/usr/share/ssh/blacklist.DSA-1024
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: Checking blacklist file 
/etc/ssh/blacklist.DSA-1024
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: temporarily_use_uid: 1000/1000 
(e=0/0)
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: trying public key file 
/home/sasha/.ssh/authorized_keys
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: restore_uid: 0/0
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: temporarily_use_uid: 1000/1000 
(e=0/0)
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: trying public key file 
/home/sasha/.ssh/authorized_keys2
  Apr 16 20:58:47 ubuntu sshd[21728]: debug1: restore_uid: 0/0
  Apr 16 20:58:47 ubuntu sshd[21728]: Failed publickey for sasha from 10.0.0.11 
port 51194 ssh2
  Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_answer_keyallowed: key 
0xb9084978 is not allowed
  ...

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

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


[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

2019-01-19 Thread Amr Ibrahim
** Tags added: bionic

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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


[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2019-01-19 Thread Antonios Hadjigeorgalis
uname -a
Linux one 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux


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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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


[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2019-01-19 Thread Antonios Hadjigeorgalis
Clean install Ubuntu 18.04 Bionic on Asus Z390 Prime with Intel i5-9600K.
- Enabled -proposed repo
- apt update && apt upgrade

Now graphics chip is correctly identified:

$ glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Coffeelake 3x8 GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.2.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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


[Touch-packages] [Bug 1574746] Re: Enable support for libsoxr

2019-01-19 Thread Rijnhard Hessel
Is it possible to get this backported to 18.04?

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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


[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

2019-01-19 Thread Fernando
Forgot to say, I've attached a screencast which hopefully will attract
the attention of someone able to fix this and to make a decision on how
to proceed. As you can see, when searching, unless you type extremely
fast, the first character is search and then the rest are dedicated to
type-ahead, not achieving any of the desired results (type ahead starts
with the second character).

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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


[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

2019-01-19 Thread Fernando
I'd say the solution is to remove the
restore_filechooser_typeaheadfind.patch, see this commit:

https://git.launchpad.net/ubuntu/+source/gtk+3.0/commit/?id=99cb6330706eadb58bf9d3c5b77120fdd5971189

After all, such patches were removed from Nautilus for a good reason. It
should also be removed from the file chooser, since currently it breaks
both behaviors. Both search and type ahead are currently broken, by
removing this, at least search will work, which is the upstream
behavior.

** Attachment added: "Screencast from 19-01-19 19:20:32.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1592177/+attachment/5230592/+files/Screencast%20from%2019-01-19%2019%3A20%3A32.webm

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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


[Touch-packages] [Bug 1812507] [NEW] Typo in description of snap

2019-01-19 Thread Tim Bannister
Public bug reported:

https://snapcraft.io/network-manager lists the description for
NetworkManager as “Network management based on NeworkManager” (sic).

NeworkManager should be NetworkManager.

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


** Tags: snap

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

Title:
  Typo in description of snap

Status in network-manager package in Ubuntu:
  New

Bug description:
  https://snapcraft.io/network-manager lists the description for
  NetworkManager as “Network management based on NeworkManager” (sic).

  NeworkManager should be NetworkManager.

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

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


[Touch-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter

2019-01-19 Thread Vadim Andreyev
Bug still exists in 18.10. How can you mark it fixed???

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

Title:
  Bluetooth mouse usage makes A2DP audio stutter

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: bluez

  When I use my Bluetooth A2DP headset (Philips SHB7102) together with
  my mouse (Lenovo Bluetooth Laser Mouse), I notice this:

  Whenever I leave the mouse still for a few seconds (it seems to enter
  some kind of lower-power-mode) and then start to move it, my music
  most of the time skips for a second. This makes using these two
  bluetooth devices together quite annoying...

  The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate
  II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.)

  I am running current karmic amd64 (linux 2.6.31-9).

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

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


[Touch-packages] [Bug 1812502] [NEW] When I use my Bluetooth A2DP headset (Philips SHB7102) together with my mouse (Lenovo Bluetooth Laser Mouse), I notice this: Whenever I leave the mouse still for a

2019-01-19 Thread Vadim Andreyev
Public bug reported:

When I use my Bluetooth A2DP headset together with my mouse, I notice
this:

Whenever I leave the mouse still for a few seconds (it seems to enter
some kind of lower-power-mode) and then start to move it, my music most
of the time skips for a second. This makes using these two bluetooth
devices together quite annoying...

It exists with every bluetooth adapter and any mouse.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 19 18:59:22 2019
InstallationDate: Installed on 2019-01-19 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: TOSHIBA Satellite Radius P55W-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=c23973fb-1c63-4119-86be-0b17173e5a2a ro quiet splash acpi_osi=Linux 
"acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax 
i915.enable_rc6=1 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 
drm.vblankoffdelay=1 acpi_backlight=vendor vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.60
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.60:bd12/23/2014:svnTOSHIBA:pnSatelliteRadiusP55W-B:pvrPSVP2U-003004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: INVALID
dmi.product.name: Satellite Radius P55W-B
dmi.product.sku: INVALID
dmi.product.version: PSVP2U-003004
dmi.sys.vendor: TOSHIBA
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: E8:2A:EA:6E:E5:28  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:309822 acl:9284 sco:0 events:14449 errors:0
TX bytes:9130591 acl:13720 sco:0 commands:309 errors:0

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


** Tags: amd64 apport-bug cosmic

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

Title:
  When I use my Bluetooth A2DP headset (Philips SHB7102) together with
  my mouse (Lenovo Bluetooth Laser Mouse), I notice this:  Whenever I
  leave the mouse still for a few seconds (it seems to enter some kind
  of lower-power-mode) and then start to move it, my music most of the
  time skips for a second. This makes using these two bluetooth devices
  together quite annoying...  The adapter is a Lenovo "ThinkPad
  Bluetooth with Enhanced Data Rate II" (Bus 004 Device 005: ID
  0a5c:2145 Broadcom Corp.)

Status in bluez package in Ubuntu:
  New

Bug description:
  When I use my Bluetooth A2DP headset together with my mouse, I notice
  this:

  Whenever I leave the mouse still for a few seconds (it seems to enter
  some kind of lower-power-mode) and then start to move it, my music
  most of the time skips for a second. This makes using these two
  bluetooth devices together quite annoying...

  It exists with every bluetooth adapter and any mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 18:59:22 2019
  InstallationDate: Installed on 2019-01-19 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: TOSHIBA Satellite Radius P55W-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=c23973fb-1c63-4119-86be-0b17173e5a2a ro quiet splash acpi_osi=Linux 
"acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax 
i915.enable_rc6=1 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 
drm.vblankoffdelay=1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis 

[Touch-packages] [Bug 1811812] Re: Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies

2019-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet 
dependencies.
  Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version 
is login (1:4.5-1ubuntu1).

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

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


[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2019-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

2019-01-19 Thread Xavier Bestel
FWIW my system has 8GB RAM.

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

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

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


[Touch-packages] [Bug 1812474] [NEW] /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

2019-01-19 Thread Xavier Bestel
Public bug reported:

/usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
If I wait long enough, the addressbook crashes (not enough memory ?).

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evolution-data-server 3.30.1-1build1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jan 19 09:59:18 2019
ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify
InstallationDate: Installed on 2017-01-09 (740 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution-data-server
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

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

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