[Touch-packages] [Bug 1389657] Re: Libpixman segfaults when searching

2016-05-11 Thread photon
dmesg on a debian system:

[ 8507.445846] dibosys-disp-40[21440]: segfault at 7f4a67fff000 ip
7f4b01a4fa70 sp 7fff57fdb098 error 4 in
libpixman-1.so.0.33.6[7f4b019c1000+a]

..so the current libpixman version (0.33.6-1) seems to have the same
problem, triggered using a gtk3 webkit browser written in perl (when
running on xserver with 4k resolution, javascipt enabled and scrolling a
web page 1 pixel at a time).. [reproducible, crash after scrolling about
50 pixels]

same effect (segfault) occurs with version 0.32.6-3

serious indeed, affects all our appliances / customers...

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

Title:
  Libpixman segfaults when searching

Status in pixman package in Ubuntu:
  Confirmed

Bug description:
  [ 2810.133252] pool[8519]: segfault at bc ip 7f966bdabb71 sp
  7f962bfed040 error 4 in libpixman-1.so.0.32.4[7f966bd55000+a3000]

  Compiz crashed and I saw the above line in the dmesg output.

  Happens EVERY time I pressed "d" on the ubuntu button for file search
  (dash, icon on top in the sidebar).

  Furthermore .xsession-errors has logged this as well:
  upstart: unity7 main process (1925) killed by SEGV signal
  upstart: unity7 main process ended, respawning

  Pretty serious I'd say ...

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

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


[Touch-packages] [Bug 1387955] Re: Alt-F4 keystroke does not work after restarting Unity.

2017-04-19 Thread Photon
*** This bug is a duplicate of bug 1292833 ***
https://bugs.launchpad.net/bugs/1292833

Probably duplicate of
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292833

** This bug has been marked a duplicate of bug 1292833
   Alt+F4 doesn't work after restarting unity

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

Title:
  Alt-F4 keystroke does not work after restarting Unity.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After restarting Unity using the "unity" command from the command
  dialog in Dash the Alt-F4 keystroke to close windows no longer
  functions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 31 02:06:24 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-37-generic, x86_64: installed
   vboxhost, 4.3.18, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:1556]
  InstallationDate: Installed on 2014-10-19 (11 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=5eade3a0-fa35-48ad-ab0b-289425b80caa ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/13/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: GA-990XA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-990XA-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Oct 25 21:40:01 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

2017-07-08 Thread Photon
@all: Please try if the problem appears for a new clean user. In my case
it didn't so I suspect that it is related to some configuration files in
~/.

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

2017-07-08 Thread Photon
Thanks for testing, looks like several different bugs are mixed up here
(or it's just me posting a similar problem in the wrong bug report...).

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

2017-07-02 Thread Photon
A followup on my report about skypeonlinux: It looks like the problem is
related to some user config in this case. If I create a clean user,
gnome-keyring works as expected. However, I wasn't able to find where
exactly the problematic configuration file is located yet.

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

2017-06-28 Thread Photon
I experience the same problem on Manjaro Linux with gnome-keyring
3.20.0+57+g9db67ef6 and skypeforlinux. So it seems to be a bug in gnome-
keyring, not in Ubuntu's package.

Some observations (citing my post on the Manjaro forums
https://forum.manjaro.org/t/skypeforlinux-weird-and-inconsistent-
authentification-behaviour/26076):

I read that the old Skype client will stop working on Juli 1st, that is
in less than two weeks, so I switched to the new client on several
machines. However, the new client behaves in a weird way on starting up:

 1.   On some machines the user gets logged in without being asked for his 
password
 2.   On some machines the user gets a gnome-keyring password dialogue
 3.   On some machines the user has to enter the complete Skype user name and 
password into the Skype client itself

In the ideal world I would like to have all machines behave as in 1. But
how to do so? Does anybody else experience the same problem?

I have digged deeper into this issue. It turned out that the gnome-
keyring-daemon is running with different command lines in the three
cases.

Case 1:
gnome-keyring-daemon --start --foreground --components=secrets (on my Manjaro 
laptop)
gnome-keyring-daemon --start (on my old Arch install)

Case2:
gnome-keyring-daemon is not running at all. It is then launched when 
skypeforlinux is started and needs a password to unlock the keyring.

Case3:
gnome-keyring-daemon --daemonize --login

So there seem to be two problems: First, the problem that gnome-keyring-
daemon is not launched at login at all, second, if it is launched, it is
launched with a bad command line.

I looked in the Xfce session settings and there is an entry for gnome-
keyring-daemon with the correct (Case 1) command line, but it is not
activated. I activated it, but it seems to have changed nothing, gnome-
keyring is still launched with the wrong command line. It looks like it
is started by some system wide service and then the Xfce session
settings entry collides with the already running instance. But what is
this system wide service and why does it use the wrong command line on
some machines but the right command line on others?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgnome-keyring 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 gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring 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:

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

2017-06-28 Thread Photon
I need to correct my previous statement. It looks like skypeforlinux is
actually starting the

  gnome-keyring-daemon --start --foreground --components=secrets

command line, it is not there at boot. The

  gnome-keyring-daemon --daemonize --login

command line seems to sometimes be there and sometimes not, on all
machines.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgnome-keyring 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 gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring 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 1733142] [NEW] unattended-upgrades 0.90ubuntu0.8 spit ERROR: os.close(4): [Errno 9] Bad file descriptor

2017-11-18 Thread photon
Public bug reported:

Description:
unattended-upgrades could execute its task successfully, but gives the error 
message during the task.

$ lsb_release -a
Description:Ubuntu 16.04.3 LTS
Codename:   xenial

$ uname -a
Linux  4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

dpkg -l unattended-upgrades
Version: 0.90ubuntu0.8

Reduplication procedure:
* Available packages for unattended-upgrades to upgrade
* sudo unattended-upgrades
* Wait for unattended-upgrades to finish its task
* check the console message:

... ...
marking libmircommon5 for remove
Packages that are auto removed: 'libmircommon5'
ERROR: os.close(4): [Errno 9] Bad file descriptor
ERROR: os.close(5): [Errno 9] Bad file descriptor
ERROR: os.close(6): [Errno 9] Bad file descriptor
ERROR: os.close(150): [Errno 9] Bad file descriptor

Sometimes the os.close error is:
Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
ERROR: os.close(4): [Errno 9] Bad file descriptor

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ubuntu16.04.3 unattended-upgrades

** Description changed:

+ Description:
+ unattended-upgrades could execute its task successfully, but gives the error 
message during the task.
+ 
  $ lsb_release -a
  Description:  Ubuntu 16.04.3 LTS
  Codename: xenial
  
  $ uname -a
  Linux  4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  
  dpkg -l unattended-upgrades
  Version: 0.90ubuntu0.8
  
  Reduplication procedure:
- * Available packages for unattended-upgrades to upgrade 
+ * Available packages for unattended-upgrades to upgrade
  * sudo unattended-upgrades
  * Wait for unattended-upgrades to finish its task
  * check the console message:
  
  ... ...
  marking libmircommon5 for remove
  Packages that are auto removed: 'libmircommon5'
  ERROR: os.close(4): [Errno 9] Bad file descriptor
  ERROR: os.close(5): [Errno 9] Bad file descriptor
  ERROR: os.close(6): [Errno 9] Bad file descriptor
  ERROR: os.close(150): [Errno 9] Bad file descriptor
  
  Sometimes the os.close error is:
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  ERROR: os.close(4): [Errno 9] Bad file descriptor

** Summary changed:

- unattended-upgrades 0.90 spit ERROR: os.close(4): [Errno 9] Bad file 
descriptor
+ unattended-upgrades 0.90ubuntu0.8 spit ERROR: os.close(4): [Errno 9] Bad file 
descriptor

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

Title:
  unattended-upgrades 0.90ubuntu0.8 spit ERROR: os.close(4): [Errno 9]
  Bad file descriptor

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Description:
  unattended-upgrades could execute its task successfully, but gives the error 
message during the task.

  $ lsb_release -a
  Description:  Ubuntu 16.04.3 LTS
  Codename: xenial

  $ uname -a
  Linux  4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

  dpkg -l unattended-upgrades
  Version: 0.90ubuntu0.8

  Reduplication procedure:
  * Available packages for unattended-upgrades to upgrade
  * sudo unattended-upgrades
  * Wait for unattended-upgrades to finish its task
  * check the console message:

  ... ...
  marking libmircommon5 for remove
  Packages that are auto removed: 'libmircommon5'
  ERROR: os.close(4): [Errno 9] Bad file descriptor
  ERROR: os.close(5): [Errno 9] Bad file descriptor
  ERROR: os.close(6): [Errno 9] Bad file descriptor
  ERROR: os.close(150): [Errno 9] Bad file descriptor

  Sometimes the os.close error is:
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  ERROR: os.close(4): [Errno 9] Bad file descriptor

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

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