Bug 506734

Summary: GDM crashes after ldap idle timeout
Product: [Fedora] Fedora Reporter: Ray Strode [halfline] <rstrode>
Component: gdmAssignee: jmccann
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: alexandre.magaz, cschalle, jmccann, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 499489
: 506998 (view as bug list) Environment:
Last Closed: 2010-06-28 13:07:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
GDM messages and traceback
none
GDM messages and traceback with UTF-8 set up none

Description Ray Strode [halfline] 2009-06-18 14:24:57 UTC
+++ This bug was initially created as a clone of Bug #499489 +++
--- Additional comment from alexm.cat on 2009-06-17 08:22:04 EDT ---

It works for me, but not at all. GDM no longer crashes after 10 minutes of inactivity, but It does when I try to log in after every 10 minutes. This is the traceback I get:

Jun 17 14:05:32 PL-REC019 gdm-binary[21771]: nss_ldap: could not search LDAP server - Server is unavailable
Jun 17 14:05:32 PL-REC019 gdm-simple-slave[23053]: WARNING: Failed to add user authorization: Message did not receive a reply (timeout by message bus)
Jun 17 14:05:32 PL-REC019 gdm[23230]: ******************* START **********************************
Jun 17 14:05:33 PL-REC019 gdm[23230]: [Thread debugging using libthread_db enabled]
Jun 17 14:05:33 PL-REC019 gdm[23230]: 0x008cd424 in __kernel_vsyscall ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: #0  0x008cd424 in __kernel_vsyscall ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: #1  0x0045ed43 in __waitpid_nocancel () from /lib/libc.so.6
Jun 17 14:05:33 PL-REC019 gdm[23230]: #2  0x080666a1 in gdm_signal_handler_backtrace ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: #3  0x08066791 in signal_handler ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: #4  <signal handler called>
Jun 17 14:05:33 PL-REC019 gdm[23230]: #5  0x008cd424 in __kernel_vsyscall ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: #6  0x003ec7c1 in raise () from /lib/libc.so.6
Jun 17 14:05:33 PL-REC019 gdm[23230]: #7  0x003ee092 in abort () from /lib/libc.so.6
Jun 17 14:05:33 PL-REC019 gdm[23230]: #8  0x007546fd in g_assertion_message () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: #9  0x00754cbd in g_assertion_message_expr () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: #10 0x08061f84 in start_session_timeout ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: #11 0x0072b341 in ?? () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: #12 0x0072d1e8 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: #13 0x007307f8 in ?? () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: #14 0x00730caf in g_main_loop_run () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: #15 0x0804d2cf in main ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: 
Jun 17 14:05:33 PL-REC019 gdm[23230]: Thread 1 (Thread 0xb8055720 (LWP 23053)):
Jun 17 14:05:33 PL-REC019 gdm[23230]: #0  0x008cd424 in __kernel_vsyscall ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #1  0x0045ed43 in __waitpid_nocancel () from /lib/libc.so.6
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #2  0x080666a1 in gdm_signal_handler_backtrace ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #3  0x08066791 in signal_handler ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #4  <signal handler called>
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #5  0x008cd424 in __kernel_vsyscall ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #6  0x003ec7c1 in raise () from /lib/libc.so.6
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #7  0x003ee092 in abort () from /lib/libc.so.6
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #8  0x007546fd in g_assertion_message () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #9  0x00754cbd in g_assertion_message_expr () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #10 0x08061f84 in start_session_timeout ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #11 0x0072b341 in ?? () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #12 0x0072d1e8 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #13 0x007307f8 in ?? () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #14 0x00730caf in g_main_loop_run () from /lib/libglib-2.0.so.0
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: #15 0x0804d2cf in main ()
Jun 17 14:05:33 PL-REC019 gdm[23230]: No symbol table info available.
Jun 17 14:05:33 PL-REC019 gdm[23230]: The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]
Jun 17 14:05:33 PL-REC019 gdm[23230]: ******************* END **********************************

Notice the LDAP error, it's always before the traceback.

--- Additional comment from alexm.cat on 2009-06-17 08:33:42 EDT ---

Sorry sorry! The comment I've just posted does not correspond to the GDM package with the bug fixed. I'll try it tomorrow.

--- Additional comment from alexm.cat on 2009-06-18 08:03:36 EDT ---

Ok, I've tried now with the new version. As I said in comment #19, it not longer crashes after 10 minutes but it does under other circumstances, I'll explain.

The first time I log in all goes well, it never crashes. But if I wait for 5 minutes and try again, it always crashes. It seems like the cause of the problem is that the OpenLDAP server closes inactive connections after 5 minutes (idletimeout option in sldapd.conf). GDM opens a connection the firs time a user logs in and then keeps it open.

As it starts a new copy of the Xorg every time, I post it here, but if you want I can open a new bug report.

This is the traceback:

Jun 18 13:38:57 PL-REC019 gdm-binary[1453]: nss_ldap: could not search LDAP server - Server is unavailable
Jun 18 13:38:57 PL-REC019 gdm-simple-slave[3595]: WARNING: Failed to add user authorization: Message did not receive a reply (timeout by message bus)
Jun 18 13:38:57 PL-REC019 gdm[3746]: ******************* START **********************************
Jun 18 13:38:59 PL-REC019 gdm[3746]: [Thread debugging using libthread_db enabled]
Jun 18 13:38:59 PL-REC019 gdm[3746]: 0x00c7b424 in __kernel_vsyscall ()
Jun 18 13:38:59 PL-REC019 gdm[3746]: #0  0x00c7b424 in __kernel_vsyscall ()
Jun 18 13:38:59 PL-REC019 gdm[3746]: #1  0x0045ed43 in __waitpid_nocancel () from /lib/libc.so.6
Jun 18 13:38:59 PL-REC019 gdm[3746]: #2  0x08066869 in crashlogger_get_backtrace () at gdm-signal-handler.c:192
Jun 18 13:38:59 PL-REC019 gdm[3746]: #3  gdm_signal_handler_backtrace () at gdm-signal-handler.c:219
Jun 18 13:38:59 PL-REC019 gdm[3746]: #4  0x08066961 in signal_handler (signo=-1077559396)
Jun 18 13:38:59 PL-REC019 gdm[3746]:     at gdm-signal-handler.c:247
Jun 18 13:38:59 PL-REC019 gdm[3746]: #5  <signal handler called>
Jun 18 13:38:59 PL-REC019 gdm[3746]: #6  0x00c7b424 in __kernel_vsyscall ()
Jun 18 13:38:59 PL-REC019 gdm[3746]: #7  0x003ec7c1 in raise () from /lib/libc.so.6
Jun 18 13:38:59 PL-REC019 gdm[3746]: #8  0x003ee092 in abort () from /lib/libc.so.6
Jun 18 13:38:59 PL-REC019 gdm[3746]: #9  0x007546fd in g_assertion_message () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: #10 0x00754cbd in g_assertion_message_expr () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: #11 0x08062124 in start_session_timeout (slave=0x9f32010)
Jun 18 13:38:59 PL-REC019 gdm[3746]:     at gdm-simple-slave.c:393
Jun 18 13:38:59 PL-REC019 gdm[3746]: #12 0x0072b341 in ?? () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: #13 0x0072d1e8 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: #14 0x007307f8 in ?? () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: #15 0x00730caf in g_main_loop_run () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: #16 0x0804d34f in main (argc=1, argv=0xbfc5c7a4) at simple-slave-main.c:260
Jun 18 13:38:59 PL-REC019 gdm[3746]: 
Jun 18 13:38:59 PL-REC019 gdm[3746]: Thread 1 (Thread 0xb7f28720 (LWP 3595)):
Jun 18 13:38:59 PL-REC019 gdm[3746]: #0  0x00c7b424 in __kernel_vsyscall ()
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #1  0x0045ed43 in __waitpid_nocancel () from /lib/libc.so.6
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #2  0x08066869 in crashlogger_get_backtrace () at gdm-signal-handler.c:192
Jun 18 13:38:59 PL-REC019 gdm[3746]:         estatus = <value optimized out>
Jun 18 13:38:59 PL-REC019 gdm[3746]: #3  gdm_signal_handler_backtrace () at gdm-signal-handler.c:219
Jun 18 13:38:59 PL-REC019 gdm[3746]: st_mode = 33261, 
Jun 18 13:38:59 PL-REC019 gdm[3746]: __pad2 = 0, 
Jun 18 13:38:59 PL-REC019 gdm[3746]: st_blocks = 16, st_atim = {
Jun 18 13:38:59 PL-REC019 gdm[3746]: tv_nsec = 212571561}, st_mtim = {
Jun 18 13:38:59 PL-REC019 gdm[3746]: tv_sec = 1245310188, 
Jun 18 13:38:59 PL-REC019 gdm[3746]: __unused5 = 0}
Jun 18 13:38:59 PL-REC019 gdm[3746]: #4  0x08066961 in signal_handler (signo=-1077559396)
Jun 18 13:38:59 PL-REC019 gdm[3746]:     at gdm-signal-handler.c:247
Jun 18 13:38:59 PL-REC019 gdm[3746]: 
Jun 18 13:38:59 PL-REC019 gdm[3746]: 
Jun 18 13:38:59 PL-REC019 gdm[3746]: #5  <signal handler called>
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #6  0x00c7b424 in __kernel_vsyscall ()
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #7  0x003ec7c1 in raise () from /lib/libc.so.6
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #8  0x003ee092 in abort () from /lib/libc.so.6
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #9  0x007546fd in g_assertion_message () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #10 0x00754cbd in g_assertion_message_expr () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #11 0x08062124 in start_session_timeout (slave=0x9f32010)
Jun 18 13:38:59 PL-REC019 gdm[3746]:     at gdm-simple-slave.c:393
Jun 18 13:38:59 PL-REC019 gdm[3746]:         auth_file = 0x0
Jun 18 13:38:59 PL-REC019 gdm[3746]:         migrated = <value optimized out>
Jun 18 13:38:59 PL-REC019 gdm[3746]: 
Jun 18 13:38:59 PL-REC019 gdm[3746]: #12 0x0072b341 in ?? () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #13 0x0072d1e8 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #14 0x007307f8 in ?? () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #15 0x00730caf in g_main_loop_run () from /lib/libglib-2.0.so.0
Jun 18 13:38:59 PL-REC019 gdm[3746]: No symbol table info available.
Jun 18 13:38:59 PL-REC019 gdm[3746]: #16 0x0804d34f in main (argc=1, argv=0xbfc5c7a4) at simple-slave-main.c:260
Jun 18 13:38:59 PL-REC019 gdm[3746]:         main_loop = 0x9f2dd68
Jun 18 13:38:59 PL-REC019 gdm[3746]:         context = <value optimized out>
Jun 18 13:38:59 PL-REC019 gdm[3746]:         connection = <value optimized out>
Jun 18 13:38:59 PL-REC019 gdm[3746]:         slave = <value optimized out>
Jun 18 13:38:59 PL-REC019 gdm[3746]: 
Jun 18 13:38:59 PL-REC019 gdm[3746]: 
Jun 18 13:38:59 PL-REC019 gdm[3746]: 
Jun 18 13:38:59 PL-REC019 gdm[3746]:         signal_handler = 0x9f2b850
Jun 18 13:38:59 PL-REC019 gdm[3746]: short_name = 0 '\0', 
Jun 18 13:38:59 PL-REC019 gdm[3746]: arg = G_OPTION_ARG_NONE, arg_data = 0x8075778, 
Jun 18 13:38:59 PL-REC019 gdm[3746]: , 
Jun 18 13:38:59 PL-REC019 gdm[3746]: long_name = 0x8068130 "display-id", 
Jun 18 13:38:59 PL-REC019 gdm[3746]: arg = G_OPTION_ARG_STRING, 
Jun 18 13:38:59 PL-REC019 gdm[3746]: description = 0x806813b "Display ID", 
Jun 18 13:38:59 PL-REC019 gdm[3746]: , {
Jun 18 13:38:59 PL-REC019 gdm[3746]: short_name = 0 '\0', 
Jun 18 13:38:59 PL-REC019 gdm[3746]: arg = G_OPTION_ARG_NONE, arg_data = 0x8075774, 
Jun 18 13:38:59 PL-REC019 gdm[3746]: , 
Jun 18 13:38:59 PL-REC019 gdm[3746]: short_name = 0 '\0', 
Jun 18 13:38:59 PL-REC019 gdm[3746]: arg = G_OPTION_ARG_NONE, arg_data = 0x0, 
Jun 18 13:38:59 PL-REC019 gdm[3746]: arg_description = 0x0}}
Jun 18 13:38:59 PL-REC019 gdm[3746]: The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]
Jun 18 13:38:59 PL-REC019 gdm[3746]: ******************* END **********************************

Comment 1 Ray Strode [halfline] 2009-06-18 15:01:22 UTC
start_session_timeout only has one g_assert call in it:

auth_file = NULL;
add_user_authorization (slave, &auth_file);
g_assert (auth_file != NULL);

We probably shouldn't be asserting there but instead cancelling the session or similar.

That's not the root problem though.  add_user_authorization ends up doing an IPC call to another process which invokes gdm_display_real_add_user_authorization.

My guess is this IPC message is malformed so the message bus is kicking the slave off.

The call has one input argument that is a string type.  If the string passed in was NULL or not utf-8 that might explain this problem.

That string comes from gdm_session_direct_get_username () which bubbles up from the worker managing the pam conversation.

Now the first message you showed is: 

nss_ldap: could not search LDAP server - Server is unavailable

One theory is one of the pam modules in the pam stack is trying to talk to the ldap server (via nsswitch) and is failing to succeed to.  Somehow the PAM conversation is still succeeding, though, and when the PAM conversation finishes PAM_USER isn't set so we end up passing a NULL username over the message bus.

Two things would be very useful for me:

- Would you mind running "debuginfo-install gdm" so the backtrace is more complete
- Would you mind:

1) booting up
2) logging in once and then back out again after 5 minutes (to stage the environment for the problem to happen)
3) logging into a terminal and running:

pkill -USR2 -f gdm-simple-slave
pkill -USR1 -f gdm-session-worker

4) Logging into GDM so that the problem happens

attaching the now much more verbose log.

Comment 2 Àlex Magaz Graça 2009-06-19 10:39:56 UTC
Created attachment 348630 [details]
GDM messages and traceback

Hi Ray,

You mention that there may be problems if the string passed is not UTF-8. All our systems use ISO-8859-1, but although I've tried setting it to UTF-8 in this installation, it's still failing in the same way.

Comment 3 Àlex Magaz Graça 2009-06-19 12:35:56 UTC
Created attachment 348652 [details]
GDM messages and traceback with UTF-8 set up

Ok, I was wrong. There is a little (but, I suppose important) difference between an ISO-8859-1 set up and an UTF-8 one.

This is with ISO-8859-1:

Jun 19 09:05:25 PL-REC019 gdm-binary[1456]: nss_ldap: could not search LDAP server - Server is unavailable
Jun 19 09:05:25 PL-REC019 gdm-simple-slave[2240]: WARNING: Failed to add user authorization: Message did not receive a reply (timeout by message bus)

And this with UTF-8:

Jun 19 11:53:39 PL-REC019 gdm-binary[1450]: nss_ldap: could not search LDAP server - Server is unavailable
Jun 19 11:53:39 PL-REC019 gdm-simple-slave[2128]: WARNING: Failed to add user authorization: could not find user "t7809263" on system

Comment 4 Ray Strode [halfline] 2009-06-19 17:58:28 UTC
Hi,

So looking at the first set of messages I see:

Apr 29 09:02:01 localhost gdm-simple-greeter[1643]: DEBUG(+): GdmGreeterSession: Info query: Username:
Apr 29 09:02:01 localhost gdm-simple-greeter[1643]: DEBUG(+): GdmGreeterLoginWindow: info query: Username:
Apr 29 09:02:01 localhost gdm-simple-greeter[1643]: DEBUG(+): GdmGreeterLoginWindow: focusing task Password Authentication
Apr 29 09:12:01 localhost gdm[1757]: ******************* START **********************************
Apr 29 09:12:02 localhost gdm[1757]: 0x005d8422 in __kernel_vsyscall ()
...

So I'm guessing the order of events are:

1) greeter asked for a username
<10 seconds go by>
2) You type in a username and press enter
3) CRASH!

Is that what happened?  Or did you click cancel or something else after 10 seconds?

If that is what happened, what username did you type in in that case? t7809263?

As you pointed out above, the second log has:

Jun 19 11:53:39 PL-REC019 gdm-simple-slave[2128]: DEBUG(+): GdmSlave: Requesting user authorization
Jun 19 11:53:39 PL-REC019 gdm-binary[1450]: nss_ldap: could not search LDAP server - Server is unavailable
Jun 19 11:53:39 PL-REC019 gdm-simple-slave[2128]: WARNING: Failed to add user authorization: could not find user "t7809263" on system

In this case, the AddUserAuthentication call is successfully invoked, it makes it across the bus to the other side, and then it fails in

_create_xauth_file_for_user is trying to do

password_entry = getpwnam ("t7809263");

and failing.

This failure appears to be a bug in nss_ldap.   It should automatically detect when the server goes away and try to reconnect.  That appears to be the root problem.  All the other problems are poor error handling.

Since I need to fix the bad error handling, too, I'm going to clone this report instead of reassign.

Comment 5 Ray Strode [halfline] 2009-06-19 18:06:57 UTC
I've cloned the nss_ldap half of this problem as bug 506998.

Comment 6 Àlex Magaz Graça 2009-06-22 06:33:54 UTC
(In reply to comment #4)
> ...
> 
> So I'm guessing the order of events are:
> 
> 1) greeter asked for a username
> <10 seconds go by>
> 2) You type in a username and press enter
> 3) CRASH!
> 
> Is that what happened?  Or did you click cancel or something else after 10
> seconds?

Well, not exactly. Actually it crashes after entering the password. I didn't do anything else after the 10 seconds, I only entered the user name and password through the keyboard.

> If that is what happened, what username did you type in in that case? t7809263?

Yes, t7809263 is the username I typed.

Comment 7 Bug Zapper 2010-04-27 15:03:31 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2010-06-28 13:07:28 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.