[Desktop-packages] [Bug 1454698] Re: Unlocking the screen after sleep logs user off and back on
Re-open this bug! This problem is not resolved. ** Changed in: gnome-screensaver (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1454698 Title: Unlocking the screen after sleep logs user off and back on Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: Locking the session from the system menu appears to happen normally, but the lightdm page shows the default background. Logging in starts a new session. It seems clear that invoking screen lock kills the session entirely. I consider this bug urgent and a show stopper. May 13 09:19:25 ctesphon kernel: [425322.609985] compiz[25534]: segfault at 2000 2 ip 00020002 sp 7fff92811f38 error 14 May 12 15:54:31 ctesphon gnome-session[25301]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: Application 'compiz.desk top' killed by signal 11 May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: App 'compiz.desktop' res pawning too quickly May 13 09:19:25 ctesphon gnome-session[25301]: CRITICAL: We failed, but the fail whale is dead. Sorry May 13 09:19:26 ctesphon colord: device removed: xrandr-Sun Electronics Corporat ion-778 May 13 09:19:26 ctesphon colord: Profile removed: icc-c8d6bf485b49fb0ac6607eab40 fcdd84 May 13 09:19:27 ctesphon kernel: [425324.763633] nvidia :03:00.0: irq 44 for MSI/MSI-X May 13 09:19:27 ctesphon acpid: client 24802[0:0] has disconnected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:31:30 2015 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2013-10-18 (571 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-04-30 (378 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1454698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1454698] Re: Unlocking the screen after sleep logs user off and back on
Sebastien, I should point out that I used the standard bug reporting tools to create the original ticket. It is very surprising to me that these do not send you the files you need. I hope you have communicated this deficiency to the team that maintains 'ubuntu-bug' I have run ubuntu-bug /var/crash/_usr_share_apport_apport-gtk.0.crash - however, that file was created on May 12, and the unexpected logout has occured many times since then. I have also submitted _usr_bin_compiz.1000.crash On Tue, May 19, 2015 at 4:12 AM, Sebastien Bacher seb...@ubuntu.com wrote: Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a .crash file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding. ** Changed in: gnome-screensaver (Ubuntu) Importance: Undecided = High ** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1454698 Title: Unlocking the screen after sleep logs user off and back on Status in gnome-screensaver package in Ubuntu: Invalid Bug description: Locking the session from the system menu appears to happen normally, but the lightdm page shows the default background. Logging in starts a new session. It seems clear that invoking screen lock kills the session entirely. I consider this bug urgent and a show stopper. May 13 09:19:25 ctesphon kernel: [425322.609985] compiz[25534]: segfault at 2000 2 ip 00020002 sp 7fff92811f38 error 14 May 12 15:54:31 ctesphon gnome-session[25301]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: Application 'compiz.desk top' killed by signal 11 May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: App 'compiz.desktop' res pawning too quickly May 13 09:19:25 ctesphon gnome-session[25301]: CRITICAL: We failed, but the fail whale is dead. Sorry May 13 09:19:26 ctesphon colord: device removed: xrandr-Sun Electronics Corporat ion-778 May 13 09:19:26 ctesphon colord: Profile removed: icc-c8d6bf485b49fb0ac6607eab40 fcdd84 May 13 09:19:27 ctesphon kernel: [425324.763633] nvidia :03:00.0: irq 44 for MSI/MSI-X May 13 09:19:27 ctesphon acpid: client 24802[0:0] has disconnected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:31:30 2015 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2013-10-18 (571 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-04-30 (378 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1454698/+subscriptions -- +-+ Walter R. Moore -- Sr. Systems Administrator, Eckerd College moor...@eckerd.edu -- http://home.eckerd.edu/~moorewr It was glorious to see -- if your heart were iron, And you could keep from grieving at all the pain - The Iliad (13.355) I'm on twitter: http://twitter.com/moorewreckerd ***Reminder! ITS will never ask you to e-mail your password!*** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1454698 Title: Unlocking the screen after sleep logs user off and back on Status in gnome-screensaver package in Ubuntu
[Desktop-packages] [Bug 1454698] Re: Unlocking the screen after sleep logs user off and back on
Please assign this ticket! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1454698 Title: Unlocking the screen after sleep logs user off and back on Status in gnome-screensaver package in Ubuntu: New Bug description: Locking the session from the system menu appears to happen normally, but the lightdm page shows the default background. Logging in starts a new session. It seems clear that invoking screen lock kills the session entirely. I consider this bug urgent and a show stopper. May 13 09:19:25 ctesphon kernel: [425322.609985] compiz[25534]: segfault at 2000 2 ip 00020002 sp 7fff92811f38 error 14 May 12 15:54:31 ctesphon gnome-session[25301]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: Application 'compiz.desk top' killed by signal 11 May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: App 'compiz.desktop' res pawning too quickly May 13 09:19:25 ctesphon gnome-session[25301]: CRITICAL: We failed, but the fail whale is dead. Sorry May 13 09:19:26 ctesphon colord: device removed: xrandr-Sun Electronics Corporat ion-778 May 13 09:19:26 ctesphon colord: Profile removed: icc-c8d6bf485b49fb0ac6607eab40 fcdd84 May 13 09:19:27 ctesphon kernel: [425324.763633] nvidia :03:00.0: irq 44 for MSI/MSI-X May 13 09:19:27 ctesphon acpid: client 24802[0:0] has disconnected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:31:30 2015 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2013-10-18 (571 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-04-30 (378 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1454698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454698] [NEW] Unlocking the screen after sleep logs user off and back on
Public bug reported: Locking the session from the system menu appears to happen normally, but the lightdm page shows the default background. Logging in starts a new session. It seems clear that invoking screen lock kills the session entirely. I consider this bug urgent and a show stopper. May 13 09:19:25 ctesphon kernel: [425322.609985] compiz[25534]: segfault at 2000 2 ip 00020002 sp 7fff92811f38 error 14 May 12 15:54:31 ctesphon gnome-session[25301]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: Application 'compiz.desk top' killed by signal 11 May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: App 'compiz.desktop' res pawning too quickly May 13 09:19:25 ctesphon gnome-session[25301]: CRITICAL: We failed, but the fail whale is dead. Sorry May 13 09:19:26 ctesphon colord: device removed: xrandr-Sun Electronics Corporat ion-778 May 13 09:19:26 ctesphon colord: Profile removed: icc-c8d6bf485b49fb0ac6607eab40 fcdd84 May 13 09:19:27 ctesphon kernel: [425324.763633] nvidia :03:00.0: irq 44 for MSI/MSI-X May 13 09:19:27 ctesphon acpid: client 24802[0:0] has disconnected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:31:30 2015 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2013-10-18 (571 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-04-30 (378 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1454698 Title: Unlocking the screen after sleep logs user off and back on Status in gnome-screensaver package in Ubuntu: New Bug description: Locking the session from the system menu appears to happen normally, but the lightdm page shows the default background. Logging in starts a new session. It seems clear that invoking screen lock kills the session entirely. I consider this bug urgent and a show stopper. May 13 09:19:25 ctesphon kernel: [425322.609985] compiz[25534]: segfault at 2000 2 ip 00020002 sp 7fff92811f38 error 14 May 12 15:54:31 ctesphon gnome-session[25301]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: Application 'compiz.desk top' killed by signal 11 May 13 09:19:25 ctesphon gnome-session[25301]: WARNING: App 'compiz.desktop' res pawning too quickly May 13 09:19:25 ctesphon gnome-session[25301]: CRITICAL: We failed, but the fail whale is dead. Sorry May 13 09:19:26 ctesphon colord: device removed: xrandr-Sun Electronics Corporat ion-778 May 13 09:19:26 ctesphon colord: Profile removed: icc-c8d6bf485b49fb0ac6607eab40 fcdd84 May 13 09:19:27 ctesphon kernel: [425324.763633] nvidia :03:00.0: irq 44 for MSI/MSI-X May 13 09:19:27 ctesphon acpid: client 24802[0:0] has disconnected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 09:31:30 2015 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 600 InstallationDate: Installed on 2013-10-18 (571 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-04-30 (378 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1454698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183398] Re: pulseaudio can't start on nfsv4 home
Confirmed - problem exists on trusty. Any progress on this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1183398 Title: pulseaudio can't start on nfsv4 home Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: When I configure 12.04 LTS to use autofs and nfs mount the home volume, pulseaudio stops working. Although permissions in $HOME seem correct, it fails with this error: $ pulseaudio --start E: [autospawn] core-util.c: Failed to create secure directory: Operation not permitted W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock $ df -h . Filesystem Size Used Avail Use% Mounted on eckserver:/export/home3 1009G 483G 517G 49% /home3/eckserver strace of `pulseaudio --start' attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1183398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 478931] Re: IBus Korean(Hangul) input bug
This still happens in Ubuntu 14.04 with Version 34.0.1847.116 Ubuntu 14.04 aura (260972). Any possibility for getting it fixed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-hangul in Ubuntu. https://bugs.launchpad.net/bugs/478931 Title: IBus Korean(Hangul) input bug Status in “ibus-hangul” package in Ubuntu: Confirmed Bug description: Binary package hint: ibus IBus on Ubuntu 9.10 has a bug when typing Korean(Hangul). If you press enter key or press a submit button in a web input form, the last Korean character is often sent twice. ProblemType: Bug Architecture: amd64 Date: Mon Nov 9 15:25:44 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/yelp InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Package: yelp 2.28.0-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: yelp Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/478931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183398] [NEW] pulseaudio can't start on nfsv4 home
Public bug reported: When I configure 12.04 LTS to use autofs and nfs mount the home volume, pulseaudio stops working. Although permissions in $HOME seem correct, it fails with this error: $ pulseaudio --start E: [autospawn] core-util.c: Failed to create secure directory: Operation not permitted W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock $ df -h . Filesystem Size Used Avail Use% Mounted on eckserver:/export/home3 1009G 483G 517G 49% /home3/eckserver strace of `pulseaudio --start' attached. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: output of `strace pulseaudio --start' https://bugs.launchpad.net/bugs/1183398/+attachment/3684863/+files/pulseaudio-start-strace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1183398 Title: pulseaudio can't start on nfsv4 home Status in “alsa-driver” package in Ubuntu: New Bug description: When I configure 12.04 LTS to use autofs and nfs mount the home volume, pulseaudio stops working. Although permissions in $HOME seem correct, it fails with this error: $ pulseaudio --start E: [autospawn] core-util.c: Failed to create secure directory: Operation not permitted W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock $ df -h . Filesystem Size Used Avail Use% Mounted on eckserver:/export/home3 1009G 483G 517G 49% /home3/eckserver strace of `pulseaudio --start' attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1183398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
