[Bug 45122] Re: hang on login after gnome-session has left a socket in /tmp/.ICE-unix
Just got around to trying to reproduce this one again. With an uptodate dapper, it seems harder to get than it used to be. But I managed to get it, though only using ctrl-alt-backspace. (I've seen it without that before) A gnome session backtrace indeed looks quite suggestive - its stuck in a nested event handler inside gnome_accessibility_module_shutdown. (gdb) thread apply all bt Thread 1 (Thread -1223522624 (LWP 1957)): #0 0xe410 in __kernel_vsyscall () #1 0xb780988d in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0xb789f7d8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0xb789fe0e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0xb797f56a in link_main_iteration () from /usr/lib/libORBit-2.so.0 #5 0xb7964515 in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0 #6 0xb7967cc5 in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0 #7 0xb7967e96 in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0 #8 0xb79796be in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0 #9 0xb6f8c5e8 in Accessibility_EventListener_notifyEvent () from /usr/lib/libspi.so.0 #10 0xb6fd34e5 in gnome_accessibility_module_shutdown () from /usr/lib/gtk-2.0/modules/libatk-bridge.so #11 0xb6fd44fb in gnome_accessibility_module_shutdown () from /usr/lib/gtk-2.0/modules/libatk-bridge.so #12 0xb792810f in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #13 0xb7929b19 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #14 0xb7929e89 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #15 0xb6f38e4b in gail_util_get_type () from /usr/lib/gtk-2.0/modules/libgail.so #16 0xb7925e54 in g_cclosure_marshal_VOID__UINT_POINTER () from /usr/lib/libgobject-2.0.so.0 #17 0xb791979f in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #18 0xb79282ea in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #19 0xb7929b19 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #20 0xb792d030 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #21 0xb6f312a2 in gail_toplevel_new () from /usr/lib/gtk-2.0/modules/libgail.so #22 0xb6f3132d in gail_toplevel_new () from /usr/lib/gtk-2.0/modules/libgail.so #23 0xb792810f in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #24 0xb7929b19 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #25 0xb7929e89 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #26 0xb7e0a9da in gtk_widget_hide () from /usr/lib/libgtk-x11-2.0.so.0 #27 0x0805ad50 in ?? () #28 0x08109070 in ?? () #29 0x080c7db0 in ?? () #30 0x08105e50 in ?? () #31 0xb78b35ca in g_slist_remove () from /usr/lib/libglib-2.0.so.0 #32 0x08050afb in ?? () #33 0x in ?? () #0 0xe410 in __kernel_vsyscall () (gdb) thread apply all bt Hope this is useful - good luck! -- hang on login after gnome-session has left a socket in /tmp/.ICE-unix https://launchpad.net/bugs/45122 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44121] Re: Remote Desktop Preference misleads about security by saying localhost:0
Yes, same issue, different solution I guess. This one is just asking for the wording in the dialog be made clearer (Current wording in connection with the default suggested address localhost suggests that the solution in bug #54312 is already implemented) (But that solution would be really good too) -- Remote Desktop Preference misleads about security by saying localhost:0 https://launchpad.net/bugs/44121 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 54312] Re: vino listen on all addresses
Heres a ssh forwarding vnc viewer script that I use. It would need a GUI tho. GPLed. ** Attachment added: sshxvncviewer http://librarian.launchpad.net/4272669/sshxvncviewer -- vino listen on all addresses https://launchpad.net/bugs/54312 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44121] Re: Remote Desktop Preference misleads about security by saying localhost:0
Unmarked as duplicate because #13102 is talking about something else (that localhost isn't the correct address to use for connecting to this machine) This bug is complaining that its not clear from the dialog that vino has enabled all remote users to access this machine, especially without a password. As this is a security issue, I think the wording needs changing to make this absolutely unmistakable. ** This bug is no longer a duplicate of bug 13012 vino-preference: command shows localhost.localdomain -- Remote Desktop Preference misleads about security by saying localhost:0 https://launchpad.net/bugs/44121 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 47307] Re: Lots of windows needing Force Quit can hang metacity
It happened again. I'm not so convinced its metacity and not the X server. I had two instances of the deadlocked program. I clicked on one close box, got the force quit dialog, clicked on force quit, and got a frozen display. The force quit button was still pressed. ctrl-alt-f1 switched to another VT, logged in, looked at the processes running. There were still 2 deadlocked ones, so I thought It might be waiting for one to die. I kill -9ed them. Switch back to X with alt-f7. Redraw doesn't happen for the hung windows, for the gnome panels, for the backdrop. It /does/ happen for a firefox in background. I try alt-tab a bit, and ctrl-shift-right to switch desktops. Nothing works. But strangely, Neither does ctrl-alt-f1 anymore!! Isn't that implemented at the X server level? How can it be blocked? I ssh into laptop from another machine and chvt 1. This works fine. From vt 1, I gdb attach to metacity to get a backtrace. Not very exciting: (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb772b88d in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0xb78f57d8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0xb78f5ca8 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #4 0x080749e2 in ?? () #5 0x080ec3b8 in ?? () #6 0x080bd760 in _IO_stdin_used () #7 0x in ?? () (gdb) quit How about strace? Process 5649 attached - interrupt to quit ioctl(12, FIONREAD, [0])= 0 poll( unfinished ... Process 5649 detached Ok. I switch back to the screen with alt-f7. Still broken, crtl-alt-f1 still fails. sshed chvt again. Now I try DISPLAY=:0 metacity --replace on vt1. alt-f7, and interestingly, the desktop switch has happened, all the windows are gone, backdrop and panels redraw properly. But the desktop switch panel is stuck visible in the centre, no mouse or keyboard response. ctrl-alt-f1 still not working. sshed chvt again. ctrl-c that metcity. Check ps - no metacity processes around. Run fvwm in the same way. switch to vt7. Redrawn ugly window borders, still no key/mouse response. (Pointer moves tho). sshed chvt. Re-run metacity from vt1. Still non-resposive. Hmm. while typing this, the screensaver kicked in. Working fine. pressing space prompts for pw pw dialog works fine... its back!!! Everything now working fine. I'm stumped. ideas anyone? How is X keyboard grabbing supposed to integrate with ctrl-alt-f1? -- Lots of windows needing Force Quit can hang metacity https://launchpad.net/bugs/47307 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 47307] Re: Lots of windows needing Force Quit can hang metacity
Yes, the wm was hung, it wasn't possible to change focus. It did seem to hand over nicely to a new wm though I don't know whether the X protocol for that needs the previous one to be alive. It happened several times, but since then, I can't reproduce it with latest updates, even though I've carefully not got around to fixing my bug :-) It never really used to happen when I tried though anyway. So who knows. I'll keep an eye out for it, and try to debug if I can. -- Lots of windows needing Force Quit can hang metacity https://launchpad.net/bugs/47307 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 47307] Re: Lots of windows needing Force Quit can hang metacity
This is on an uptodate dapper beta. -- Lots of windows needing Force Quit can hang metacity https://launchpad.net/bugs/47307 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45122] Re: hang on login after gnome-session has left a socket in /tmp/.ICE-unix
Yes, I've seen it a few times now, and just reproduced it on demand again. If I log out normally and then immediately log in again, I get the same sort of hang - gnome session seeming unresponsive, stuck splash, and gnome terminal and eg gedit not opening. Note that the splash redraws with no text on it. -- hang on login after gnome-session has left a socket in /tmp/.ICE-unix https://launchpad.net/bugs/45122 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45122] gconfd not shutting down/not restarting after X server killed
Public bug reported: After I kill the X server using ctrl-alt backspace, logging back on usually hangs partway through the gnome setup progress with the centre splash still up, sometimes showing update-notifier. Launching gnome terminal just hangs - no window appears. firefox will start tho. Manually killing gconfd from outside X can make things work again. ** Affects: gconf2 (Ubuntu) Severity: Normal Priority: (none set) Status: Needs Info -- gconfd not shutting down/not restarting after X server killed https://launchpad.net/bugs/45122 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45122] Re: gconfd not shutting down/not restarting after X server killed
Oooh, interesting.
In the hung state, gnome-terminal launched from a panel icon or the
gnome menu fails to appear.
But gnome-terminal run from the command line (from an xterm launched
from a text console login) actually works.
The non-working gnome-terminal hasn't got as far as running gnome-pty-
helper.
In fact, here's the end of a strace of a hung gnome-terminal:
munmap(0xb6ded000, 4096)= 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
time(NULL) = 1147818268
mkdir(/home/brian/.gnome2, 0700) = -1 EEXIST (File exists)
mkdir(/home/brian/.gnome2_private, 0700) = -1 EEXIST (File exists)
chmod(/home/brian/.gnome2_private/, 0700) = 0
mkdir(/home/brian/.gnome2/accels, 0700) = -1 EEXIST (File exists)
socket(PF_FILE, SOCK_STREAM, 0) = 14
uname({sys=Linux, node=ecthelion, ...}) = 0
connect(14, {sa_family=AF_FILE, path=/tmp/.ICE-unix/9262}, 21) = 0
fcntl64(14, F_SETFD, FD_CLOEXEC)= 0
write(14, \0\1\0\0\0\0\0\0, 8)= 8
read(14,
[EMAIL PROTECTED]:/usr/bin# ps 9262
PID TTY STAT TIME COMMAND
9262 ?Ss 0:01 /usr/bin/gnome-session
So its trying to talk to gnome-sessions and getting no reply...
--
gconfd not shutting down/not restarting after X server killed
https://launchpad.net/bugs/45122
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45122] Re: gconfd not shutting down/not restarting after X server killed
The above all happened in a hang that didn't start with an extra gconfd running. [details in a reply by email that hasn't made it here yet] -- gconfd not shutting down/not restarting after X server killed https://launchpad.net/bugs/45122 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45122] Re: gconfd not shutting down/not restarting after X server killed
Ok, I reckon the hang on startup happens if a dead gnome-session has a left-over socket in /tmp/.ICE-unix. I've just done a successful logon after cleaning that up, even with a left-over gconfd. Since I was really reporting the hang on login, it would be worth renaming this bug and assigning it to gnome-session, IMHO. ** Summary changed: - gconfd not shutting down/not restarting after X server killed + hang on login after gnome-sessions has left a socket in /tmp/.ICE-unix ** Description changed: After I kill the X server using ctrl-alt backspace, logging back on usually hangs partway through the gnome setup progress with the centre splash still up, sometimes showing update-notifier. Launching gnome terminal just hangs - no window appears. firefox will start tho. - Manually killing gconfd from outside X can make things work again. + XXX Manually killing gconfd from outside X can make things work again. + XXX + + I now think that was a red herring. + + Things are hung trying to talk to a gnome-session that isn't replying. ** Summary changed: - hang on login after gnome-sessions has left a socket in /tmp/.ICE-unix + hang on login after gnome-session has left a socket in /tmp/.ICE-unix -- hang on login after gnome-session has left a socket in /tmp/.ICE-unix https://launchpad.net/bugs/45122 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45122] Re: hang on login after gnome-session has left a socket in /tmp/.ICE-unix
Moving to gnome-session - I think gconfd is blameless. ** Changed in: gconf2 (Ubuntu) Sourcepackagename: gconf2 = gnome-session Status: Needs Info = Unconfirmed -- hang on login after gnome-session has left a socket in /tmp/.ICE-unix https://launchpad.net/bugs/45122 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44118] Prompt to decrypt a partition thats already in use
Public bug reported: Affects: nautilus (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Binary package hint: nautilus Using a crypted root partition, its already mapped to /dev/mapper/root by the initramfs, but something, I'm guessing nautilus but its not clear, prompts to decryprt the partition on desktop login. This is a LUKS encrypted partition. -- Prompt to decrypt a partition thats already in use https://launchpad.net/bugs/44118 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
