[Bug 946674] Re: unity-greeter crashed with SIGSEGV in background_loader_ready_cb()
I'm also affected by this bug. It doesn't happen every time on restart, but often. Below is from my Lightdm.log. Hopefully it will be helpful in resolving this very annoying bug. It also happens when logging in/out from one user to another. "[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.1.9, UID=0 PID=1167 [+0.00s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registered seat module xlocal [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Adding default seat [+0.00s] DEBUG: Starting seat [+0.00s] DEBUG: Starting new display for greeter [+0.00s] DEBUG: Starting local X display [+0.02s] DEBUG: X server :0 will replace Plymouth [+0.05s] DEBUG: Using VT 7 [+0.05s] DEBUG: Activating VT 7 [+0.05s] DEBUG: Logging to /var/log/lightdm/x-0.log [+0.05s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0 [+0.05s] DEBUG: Launching X Server [+0.05s] DEBUG: Launching process 1204: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none [+0.05s] DEBUG: Waiting for ready signal from X server :0 [+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.05s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.85s] DEBUG: Got signal 10 from process 1204 [+0.85s] DEBUG: Got signal from X server :0 [+0.85s] DEBUG: Stopping Plymouth, X server is ready [+0.88s] DEBUG: Connecting to XServer :0 [+0.88s] DEBUG: Starting greeter [+0.88s] DEBUG: Started session 1403 with service 'lightdm', username 'lightdm' [+0.96s] DEBUG: Session 1403 authentication complete with return value 0: Success [+0.96s] DEBUG: Greeter authorized [+0.96s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log [+0.96s] DEBUG: Session 1403 running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter [+1.21s] DEBUG: Greeter connected version=1.1.9 [+1.21s] DEBUG: Greeter connected, display is ready [+1.21s] DEBUG: New display ready, switching to it [+1.21s] DEBUG: Activating VT 7 [+1.97s] DEBUG: Greeter start authentication for baldrick [+1.97s] DEBUG: Started session 1650 with service 'lightdm', username 'baldrick' [+1.98s] DEBUG: Session 1650 got 1 message(s) from PAM [+1.98s] DEBUG: Prompt greeter with 1 message(s) [+4.13s] DEBUG: Session 1403 exited with return value 0 [+4.14s] DEBUG: Greeter quit [+4.14s] DEBUG: Failed to start greeter [+4.14s] DEBUG: Stopping display [+4.14s] DEBUG: Sending signal 15 to process 1204 [+4.15s] DEBUG: Greeter closed communication channel [+4.24s] DEBUG: Process 1204 exited with return value 0 [+4.24s] DEBUG: X server stopped [+4.24s] DEBUG: Removing X server authority /var/run/lightdm/root/:0 [+4.24s] DEBUG: Releasing VT 7 [+4.24s] DEBUG: Display server stopped [+4.24s] DEBUG: Display stopped [+4.24s] DEBUG: Active display stopped, switching to greeter [+4.24s] DEBUG: Switching to greeter [+4.24s] DEBUG: Starting new display for greeter [+4.24s] DEBUG: Starting local X display [+4.24s] DEBUG: Using VT 7 [+4.24s] DEBUG: Logging to /var/log/lightdm/x-0.log [+4.24s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0 [+4.24s] DEBUG: Launching X Server [+4.24s] DEBUG: Launching process 1778: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+4.24s] DEBUG: Waiting for ready signal from X server :0 [+5.11s] DEBUG: Got signal 10 from process 1778 [+5.11s] DEBUG: Got signal from X server :0 [+5.11s] DEBUG: Connecting to XServer :0 [+5.11s] DEBUG: Starting greeter [+5.11s] DEBUG: Started session 1782 with service 'lightdm', username 'lightdm' [+5.13s] DEBUG: Session 1782 authentication complete with return value 0: Success [+5.13s] DEBUG: Greeter authorized [+5.13s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log [+5.13s] DEBUG: Session 1782 running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter [+5.32s] DEBUG: Greeter connected version=1.1.9 [+5.32s] DEBUG: Greeter connected, display is ready [+5.32s] DEBUG: New display ready, switching to it [+5.32s] DEBUG: Activating VT 7 [+5.32s] DEBUG: Stopping greeter display being switched from [+6.33s] DEBUG: Greeter start authentication for baldrick [+6.33s] DEBUG: Started session 1872 with service 'lightdm', username 'baldrick' [+6.34s] DEBUG: Session 1872 got 1 message(s) from PAM [+6.34s] DEBUG: Prompt greeter with 1 message(s) [+7.05s] DEBUG: Session 1782 exited with return value 0 [+7.05s] DEBUG: Greeter quit [+7.05s] DEBUG: Failed to start greeter [+7.05s] DEBUG: Stopping display [+7.05s] DEBUG: Sending signal 15 to process 1778 [+7.06s] DEBUG: Greeter closed communication channel [+7.19s] DEBUG: Process 1778 exited with return value 0 [+7.19s] DEBUG: X server stopped [+7.19s] DEBUG: Removing X server authority /var/run/lightdm/root/:0 [+7.19s] DEBUG: Relea
[Bug 971839] Re: aptd crashed with UnboundLocalError in _emit_acquire_item(): local variable 'lang' referenced before assignment
I'm running a 32bit system too, same prob. Happened after reboot following after update using update manager. Usually use terminal yo update/upgrade, so not aware if this is a regular occurrence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971839 Title: aptd crashed with UnboundLocalError in _emit_acquire_item(): local variable 'lang' referenced before assignment To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/971839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946674] Re: unity-greeter crashed with SIGSEGV in background_loader_ready_cb()
Worked for me, too. Thanks heaps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946674 Title: unity-greeter crashed with SIGSEGV in background_loader_ready_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/946674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211514] Re: Shutdowns fail to finish if laptop lid is closed before completely shutdown
The same thing happens under Ubuntu Gnome too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211514 Title: Shutdowns fail to finish if laptop lid is closed before completely shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1211514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 960757] Re: whoopsie crashed with SIGSEGV in g_object_newv()
Not running Nvidia drivers, using 12.04 beta1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/960757 Title: whoopsie crashed with SIGSEGV in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/960757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857702] Re: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
Same here, though I'm using 12.04 beta2 and i386. I was opening gwibber at the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857702 Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/857702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239010] Re: gnome-settings activation freezes computer
I have an Intel Sandybridge chip, and suffer the same problem on two laptops. The screens on both laptops just freeze mid application, then slowly unfreeze. If music is playing, it stutters as the screen freezes. Ram usage post freeze is about 600mb for systems settings alone. Killing the process in System manager following freeze fixes issue, and the laptop then performs fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239010 Title: gnome-settings activation freezes computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1239010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120737] Re: signon-ui crashed with SIGSEGV in SignOnUi::BrowserRequestPrivate::~BrowserRequestPrivate()
+1 to Steven Beer's comment. Changing to Firefox yields same results. Once logged into facebook account, the webpage says 'Success', but empathy fails to sign you in, and crashes instead. I don't know why they simply don't revert to the way they had it in 12.04, signing up and in worked flawlessly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120737 Title: signon-ui crashed with SIGSEGV in SignOnUi::BrowserRequestPrivate::~BrowserRequestPrivate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1120737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120737] Re: signon-ui crashed with SIGSEGV in SignOnUi::BrowserRequestPrivate::~BrowserRequestPrivate()
It seems to work better since an update today (28/2), but you seem to have to type really quickly once you've got through the facebook login screen (which is now implemented nicely within the app) to the next screen where you have to name your device. It seems like you've only got a second or two to fill out your device name before it times out, and you then have to physically clear the 'intruder alert' message on your facebook page. This is not enough time for the average, non-typist, user. Hopefully this is just a bug & will get sorted before final release. It works now for me. Thanks to all involved in sorting this out. Using 13.04, 32bit, on a Dell Latitude, i5 laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120737 Title: signon-ui crashed with SIGSEGV in SignOnUi::BrowserRequestPrivate::~BrowserRequestPrivate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1120737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034112] Re: usb-creator-gtk crashed with SIGSEGV in g_main_context_query()
I'm using 13.04, 32bit, but the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034112 Title: usb-creator-gtk crashed with SIGSEGV in g_main_context_query() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1034112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058672] Re: Can't add my Facebook account
Does exactly the same thing in Empathy too! Full message, Ubuntu 13.04 x64. Fresh install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058672 Title: Can't add my Facebook account To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/1058672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
