[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2017-02-22 Thread Amr Ibrahim
** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/874924 Title: WARNING: Failed to open CK session: Timeout

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2016-04-04 Thread Robert Ancell
Closing this bug since it is so old. Please open new bugs if you are still getting issues like this. ** No longer affects: consolekit (Ubuntu) ** No longer affects: consolekit (Ubuntu Precise) ** No longer affects: ecryptfs-utils (Ubuntu) ** No longer affects: ecryptfs-utils (Ubuntu Precise)

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2014-10-24 Thread Tyler Hicks
Marking the ecryptfs-utils task as invalid. Encryption is a cpu intensive operation and there's nothing that can be done, from an eCryptfs standpoint, for this specific bug. Software depending on hard-coded timeout values is troublesome since the home directory may be encrypted, may be in an NFS

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2013-01-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ecryptfs-utils (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu.

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2013-01-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: consolekit (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu.

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2013-01-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ecryptfs-utils (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu.

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2013-01-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: consolekit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu.

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2012-03-22 Thread Kate Stewart
** Tags added: precise rls-mgr-p-tracking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/874924 Title: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2012-01-02 Thread Sebastien Bacher
The bug is triaged as High and will be looked at this cycle, people are just busy and the end of year is usually low activity time, not sure where the issue is, lightdm got it but it seems consolekit timeouts due to those non automounted ecryptfs private dirs, not sure why those create issues for

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-12-29 Thread Miłosz Kosobucki
Does _anyone_ take this seriously? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/874924 Title: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir) Status in

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-12-22 Thread Miłosz Kosobucki
This bug is quite severe. It left me with almost unusable system. Even after reinstallation it wasn't working properly because there was still this .ecryptfs folder (I preserved my /home volume). Is there any workaround beyond making your Private folder unusable? -- You received this bug

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-12-22 Thread VS
Yes. Use gdm instead of lightdm: apt-get install gdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/874924 Title: WARNING: Failed to open CK session: Timeout was reached (ecryptfs

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-11-01 Thread whoop
I have same problems, using a non-auto-mount ~/Private folder containing non-essential files on a 64 bit machine. CPU is 100% all of the time, all kinds of stuff like audio and network are not working properly... -- You received this bug notification because you are a member of Desktop Packages,

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-10-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu.

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-10-20 Thread Vegar
Adding some other possibly relevant info: - My ~/.ecryptfs does _not_ have the auto-mount file, i.e. it will not be mounted automatically when I log in. Could something be waiting for ~/Private to be automounted when it won't be? I notice that the reporter of bug #872939 had a similar ecryptfs

Re: [Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-10-20 Thread Dustin Kirkland
Do you have any configuration information, directories or files that lightdm might need stashed in your non-auto-mounted Private dir? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu.

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-10-20 Thread Vegar
Nope. It only contains some pdf and png files. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/874924 Title: WARNING: Failed to open CK session: Timeout was reached (ecryptfs

[Desktop-packages] [Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

2011-10-19 Thread Sebastien Bacher
** Summary changed: - WARNING: Failed to open CK session: Timeout was reached + WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu.