[Bug 377573] New: micasad won't start
https://bugzilla.novell.com/show_bug.cgi?id=377573 Summary: micasad won't start Product: openSUSE 11.0 Version: Factory Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sbrys@novell.com QAContact: qa@suse.de Found By: Field Engineer Environment: - openSUSE 11.0 (i586) Alpha3 - CASA packages: -------------------------/snip/------------------------- linux-lh7i:~ # rpm -qa|grep -i casa CASA-gui-1.7.1464-85 CASA-1.7.1464-85 yast2-CASA-1.7.1461-94 -------------------------/snip/------------------------- Steps to duplicate: -------------------------/snip/------------------------- linux-lh7i:~ # rcmicasad start Starting miCASA daemon done linux-lh7i:~ # rcmicasad status Checking miCASA daemon unused -------------------------/snip/------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 Martin Mrazik <mmrazik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |cmashayekhi@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c1 Dan Elder <delder@novacoast.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |delder@novacoast.com --- Comment #1 from Dan Elder <delder@novacoast.com> 2008-05-08 07:30:18 MST --- CASA isn't working in beta 2 on x86_64, either. Same problem, no logs of failure or anything else I can find. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c2 --- Comment #2 from Dan Elder <delder@novacoast.com> 2008-05-08 12:15:58 MST --- on x86_64 I noticed in strace that micasa was looking for a missing library which I was able to solve with: ln -s /usr/lib64/libMonoPosixHelper.so /usr/lib64/libMonoPosixHelper.so.so The extra .so suffix sounds like CASA wasn't build properly but I'll keep digging into it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c3 --- Comment #3 from Dan Elder <delder@novacoast.com> 2008-05-09 14:09:03 MST --- Installing the vanilla CASA rpms from developer.novell.com (CASA-1.7.1464-0) results in a version of CASA which will startup but it fails once you start loading secrets as a user. Secrets can sucessfully be created but on subsequent launches of CASAManager it just keeps popping up the master password dialog asking for your password no matter how many times you enter it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c4 --- Comment #4 from Dan Elder <delder@novacoast.com> 2008-05-09 15:34:29 MST --- After installing additional debuginfo packages I can actually get the factory version of CASA to start now. I haven't been able to verify whether it's actually working though as the manager gui crashes immediately on launch: delder@delder:~> CASAManager.sh Stacktrace: at System.BitConverter..cctor () <0xffffffff> at System.BitConverter..cctor () <0x0000d> at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff> at System.Net.IPAddress..ctor (uint16[],long) <0xffffffff> at System.Net.IPAddress..ctor (uint16[],long) <0x00082> at System.Net.IPAddress.ParseIPV6 (string) <0x0005c> at System.Net.IPAddress..cctor () <0x00098> at (wrapper runtime-invoke) System.Net.Sockets.Socket.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff> at Novell.CASA.MiCasa.Communication.UnixIPCClientChannel.Open () <0xffffffff> at Novell.CASA.MiCasa.Communication.UnixIPCClientChannel.Open () <0x000bc> at Novell.CASA.MiCasa.Communication.MiCasaRequestReply.Send (int,string,string,string,object) <0x00078> at Novell.CASA.MiCasa.Communication.MiCasaRequestReply.Send (int,object) <0x0001f> at Novell.CASA.GUI.CasaMain.Main (string[]) <0x00083> at (wrapper runtime-invoke) Novell.CASA.GUI.CasaMain.runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0xffffffff> Native stacktrace: mono [0x533b19] mono [0x4fe31d] /lib64/libpthread.so.0 [0x7f23c20a7b30] /lib64/libc.so.6(memcpy+0x60) [0x7f23c1b6abd0] mono(mono_breakpoint_clean_code+0x1b) [0x42868b] mono [0x44063d] mono [0x538710] [0x4002c160] Debug info from gdb: (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f23c2fab720 (LWP 26606)] [New Thread 0x4172c950 (LWP 26608)] [New Thread 0x4059a950 (LWP 26607)] 0x00007f23c20a690b in read () from /lib64/libpthread.so.0 Current language: auto; currently asm 3 Thread 0x4059a950 (LWP 26607) 0x00007f23c20a7251 in nanosleep () from /lib64/libpthread.so.0 2 Thread 0x4172c950 (LWP 26608) 0x00007f23c20a3dd9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 1 Thread 0x7f23c2fab720 (LWP 26606) 0x00007f23c20a690b in read () from /lib64/libpthread.so.0 Thread 3 (Thread 0x4059a950 (LWP 26607)): #0 0x00007f23c20a7251 in nanosleep () from /lib64/libpthread.so.0 #1 0x00000000004d5132 in ?? () #2 0x00007f23c20a0040 in start_thread (arg=<value optimized out>) at pthread_create.c:297 #3 0x00007f23c1bbd03d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x4172c950 (LWP 26608)): #0 0x00007f23c20a3dd9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00000000004e04b5 in ?? () #2 0x00000000004e275b in ?? () #3 0x00000000004e399e in ?? () #4 0x00000000005397c3 in ?? () #5 0x000000000048253b in ?? () #6 0x00000000004daba3 in ?? () #7 0x00000000004f4272 in ?? () #8 0x00007f23c20a0040 in start_thread (arg=<value optimized out>) at pthread_create.c:297 #9 0x00007f23c1bbd03d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f23c2fab720 (LWP 26606)): #0 0x00007f23c20a690b in read () from /lib64/libpthread.so.0 #1 0x00007f23c275187e in read_ints (fd=14, buf=0x7fffcafcbd80, n_ints_in_buf=<value optimized out>, n_ints_read=0x7fffcafcbdd8, error=0x0) at /usr/include/bits/unistd.h:45 #2 0x00007f23c2751d66 in fork_exec_with_pipes (intermediate_child=0, working_directory=0x0, argv=0xab2990, envp=0x0, close_descriptors=1, search_path=1, stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, child_setup=0, user_data=0x0, child_pid=0x7fffcafcbf14, standard_input=0x0, standard_output=0x7fffcafcbf1c, standard_error=0x7fffcafcbf18, error=0x0) at gspawn.c:1309 #3 0x00007f23c27527db in IA__g_spawn_sync ( working_directory=0x7fffcafcbd80 "@\003", argv=0x8, envp=0x0, flags=<value optimized out>, child_setup=0, user_data=0x0, standard_output=0x7fffcafcc860, standard_error=0x7fffcafcc858, exit_status=0x7fffcafcc86c, error=0x0) at gspawn.c:259 #4 0x00007f23c2752c98 in IA__g_spawn_command_line_sync ( command_line=<value optimized out>, standard_output=0x7fffcafcc860, standard_error=0x7fffcafcc858, exit_status=0x7fffcafcc86c, error=0x0) at gspawn.c:682 #5 0x0000000000533bb4 in ?? () #6 0x00000000004fe31d in ?? () #7 <signal handler called> #8 0x00007f23c1b6abd0 in memcpy () from /lib64/libc.so.6 #9 0x000000000042868b in mono_breakpoint_clean_code () #10 0x000000000044063d in ?? () #11 0x0000000000538710 in ?? () #12 0x000000004002c160 in ?? () #13 0x00000000406a905d in ?? () #14 0x00007f23c270e55d in IA__g_hash_table_lookup (hash_table=0xa1efd8, key=0xa1f2e0) at ghash.c:118 #15 0x0000000000502518 in ?? () #16 0x0000000000456c1b in ?? () #17 0x000000000045979c in ?? () #18 0x00007fffcafcdd19 in ?? () #19 0x00007f23c2fab718 in ?? () #20 0x0000000000a1f350 in ?? () #21 0x00000000406a900d in ?? () #22 0x000000000099b868 in ?? () #23 0x00007fffcafcd490 in ?? () #24 0x00007fffcafcd430 in ?? () #25 0x0000000000a1efd8 in ?? () #26 0x0000000000a1f2e0 in ?? () #27 0x00000000c2fab720 in ?? () #28 0x0000000000000001 in ?? () #29 0x0000000000000000 in ?? () #0 0x00007f23c20a690b in read () from /lib64/libpthread.so.0 ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= /usr/bin/CASAManager.sh: line 11: 26606 Aborted mono /usr/bin/CASAManager.exe $1 $2 $3 $4 I have the following CASA packages installed: yast2-CASA-1.7.1461-108 CASA-1.7.1464-99 CASA-kwallet-debuginfo-1.7.758-188 CASA-gui-1.7.1464-99 CASA-32bit-1.7.1464-99 CASA-cli-1.7.1464-99 CASA-kwallet-1.7.758-188 CASA-debuginfo-1.7.1464-99 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User cmashayekhi@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c5 Cameron Mashayekhi <cmashayekhi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cmashayekhi@novell.com |jnorman@novell.com --- Comment #5 from Cameron Mashayekhi <cmashayekhi@novell.com> 2008-05-13 09:12:44 MST --- Jim, This is a micasad issue. -- Cameron -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User jnorman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c6 --- Comment #6 from Jim Norman <jnorman@novell.com> 2008-05-13 16:07:34 MST --- Is there a server that hosts the images for Suse11? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User jnorman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c7 --- Comment #7 from Jim Norman <jnorman@novell.com> 2008-05-13 16:14:56 MST --- Found it on kirk.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 Dan Elder <delder@novacoast.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c8 --- Comment #8 from Dan Elder <delder@novacoast.com> 2008-05-28 18:56:51 MDT --- If you install CASA from SLED it will at least create /var/run/.novellCASA (which for some reason the OpenSUSE version has problems creating) so that micasad will start. Unfortunately, it still doesn't really work though. Micasad (both SLED and OpenSUSE version) will just keep looping forever: [pid 11289] bind(1, {sa_family=AF_FILE, path="/var/run/.novellCASA"}, 23) = 0 [pid 11289] listen(1, 50) = 0 [pid 11289] mmap(NULL, 65536, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x41fe6000 [pid 11289] epoll_create(256) = 2 [pid 11289] semop(294914, 0x41fe49f0, 1) = 0 [pid 11289] semop(294914, 0x41fe49f0, 1) = 0 [pid 11289] semop(294914, 0x41fe4ad0, 1) = 0 [pid 11289] mmap(NULL, 2101248, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x41ff6000 [pid 11289] mprotect(0x41ff6000, 4096, PROT_NONE) = 0 [pid 11289] clone(Process 11290 attached child_stack=0x421f6220, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x421f69e0, tls=0x421f6950, child_tidptr=0x421f69e0) = 11290 [pid 11289] futex(0x7f75b922db78, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...> [pid 11285] semop(294914, 0x7fffc1260f80, 1) = -1 EAGAIN (Resource temporarily unavailable) [pid 11285] semop(294914, 0x7fffc1260f80, 1) = -1 EAGAIN (Resource temporarily unavailable) [pid 11285] nanosleep({0, 100000000}, <unfinished ...> [pid 11290] set_robust_list(0x421f69f0, 0x18) = 0 [pid 11290] futex(0x7f75b922db78, FUTEX_WAKE_PRIVATE, 1) = 1 [pid 11290] futex(0x7f75b718ea90, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...> [pid 11289] <... futex resumed> ) = 0 [pid 11289] semop(294914, 0x41fe4ad0, 1) = 0 [pid 11289] futex(0x7f75b718ea90, FUTEX_WAKE_PRIVATE, 1) = 1 [pid 11289] epoll_ctl(2, EPOLL_CTL_ADD, 1, {EPOLLIN, {u32=1, u64=1}}) = 0 [pid 11289] futex(0x7f75b6d1a59c, FUTEX_WAIT_PRIVATE, 1, {0, 99274102} <unfinished ...> [pid 11290] <... futex resumed> ) = 0 [pid 11290] epoll_wait(2, <unfinished ...> [pid 11285] <... nanosleep resumed> NULL) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] nanosleep({0, 100000000}, <unfinished ...> [pid 11289] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 11289] futex(0x7f75b6d1a570, FUTEX_WAKE_PRIVATE, 1) = 0 [pid 11289] futex(0x7f75b6d1a59c, FUTEX_WAIT_PRIVATE, 3, {0, 99727442} <unfinished ...> [pid 11285] <... nanosleep resumed> NULL) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] nanosleep({0, 100000000}, <unfinished ...> [pid 11289] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 11289] futex(0x7f75b6d1a570, FUTEX_WAKE_PRIVATE, 1) = 0 [pid 11289] futex(0x7f75b6d1a59c, FUTEX_WAIT_PRIVATE, 5, {0, 99772559}) = -1 ETIMEDOUT (Connection timed out) [pid 11289] futex(0x7f75b6d1a570, FUTEX_WAKE_PRIVATE, 1) = 0 [pid 11289] futex(0x7f75b6d1a59c, FUTEX_WAIT_PRIVATE, 7, {0, 99748965} <unfinished ...> [pid 11285] <... nanosleep resumed> NULL) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] nanosleep({0, 100000000}, <unfinished ...> [pid 11289] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 11289] futex(0x7f75b6d1a570, FUTEX_WAKE_PRIVATE, 1) = 0 [pid 11289] futex(0x7f75b6d1a59c, FUTEX_WAIT_PRIVATE, 9, {0, 99788368} <unfinished ...> [pid 11285] <... nanosleep resumed> NULL) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] semop(294914, 0x7fffc1260f80, 1) = 0 [pid 11285] nanosleep({0, 100000000}, <unfinished ...> [pid 11289] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out) and any clients trying to connect will similarly be stuck looping through while trying to connect: (from CASAcli -l) getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 brk(0) = 0x604000 brk(0x625000) = 0x625000 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl(3, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/.novellCASA"}, 110) = 0 write(3, "\1\0\32\0\0\0\0\0\1\0\f\0\0\0SecretStore\0", 26) = 26 read(3, 0x60c380, 14) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 1000000}, NULL) = 0 read(3, 0x60c380, 14) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 1000000}, NULL) = 0 read(3, 0x60c380, 14) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 1000000}, NULL) = 0 read(3, 0x60c380, 14) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 1000000}, NULL) = 0 Did something maybe change on the Mono.Posix assemblies that might be affecting this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User jnorman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c9 --- Comment #9 from Jim Norman <jnorman@novell.com> 2008-05-29 08:56:54 MDT --- Dan, Thanks for the investigation on this one. I've also spent some time looking as to what changed. The micasad service is started my a micasad-init binary which does a exec on the micasad.exe. I've found that if I start micasad.exe directly using mono, things work. Try this I you could and let me know what your findings are: In a terminal: export MONO_PATH=/usr/lib mono /usr/bin/micasad.exe & Then test CASAcli and CASAManager.sh. Thanks, Jim -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c10 --- Comment #10 from Dan Elder <delder@novacoast.com> 2008-05-29 09:28:33 MDT --- Brilliant! That certainly does seem to be working quite a bit better for me. I'm still getting a few weird issues but I think if I do a full restart things will work much better for me. I'm not sure what micasad-init is (or isn't) doing but it does seem to be the cause of micasad not starting up correctly. This one is easy to fix in the init script at least. Many thanks, Dan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User jnorman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c11 --- Comment #11 from Jim Norman <jnorman@novell.com> 2008-05-29 16:02:37 MDT --- A long time ago, the casa init script used to start micasad that way. However, for reasons I can't remember we had to change that and wrote a small app(micasad-init) to do an 'exec' to get micasad start. I'll have to research as to why we changed it. I hope to find the dialog in my email archive. Thanks, Jim -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c12 --- Comment #12 from Dan Elder <delder@novacoast.com> 2008-06-20 18:50:18 MDT --- Just checking to see if there was any update on this. It looks like the version of CASA shipping with 11 is still broken. It would be great to have an updated CASA plugin for Firefox but that's never been part of any SUSE product. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c13 --- Comment #13 from Dan Elder <delder@novacoast.com> 2008-08-15 07:41:03 MDT --- Is CASA still a supported part of OpenSUSE or is Novell dropping it from everything? It hasn't ever worked in 11 and just causes errors so if it can't be fixed it should be removed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User jnorman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c14 --- Comment #14 from Jim Norman <jnorman@novell.com> 2008-08-18 08:59:32 MDT --- Hi Dan, Are you seeing other errors besides the one noted above? Thanks, Jim -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c15 --- Comment #15 from Dan Elder <delder@novacoast.com> 2008-08-18 09:11:21 MDT --- Hi Jim, It still seems like there's a lot of problems with CASA in 11. The install itself can't ever setup the pam modules due to bug #389026 and even with manually setting up pam modules and the startup script there seems to still be errors on startup. Bug #398625 might even be related to CASA startup but I'll have to keep digging into that one. I also had a lot of gnome-keyring-daemon problems with evolution that went away after uninstalling CASA. Sorry, Dan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User jnorman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c16 --- Comment #16 from Jim Norman <jnorman@novell.com> 2008-08-19 09:02:21 MDT --- Hi Dan, CASA has 2 modes of operation: 1: User credentials storage. 2: Service credentials storage(ZEN-AuthTokens, DHCP, DNS, etc). PAM configuration for CASA is only supported on SLED machines(User credential storage), hence bug 389026 is marked as an enhancement. Currently, no active development is being done on CASA. Until management decides to continue development, provide testing, etc. we can only address defects on supported platforms and configurations. I'm not sure how CASA affects 398625, unless enabling PAM(not supported on openSUSE) does something wrong. As for gnome-keyring-daemon.... on SLED there was a patch to gnome-keyring-daemon that stored it's MasterPassword in CASA. I'm not sure that is patched on openSUSE. As for this bug, I need to change the startup script as discussed earlier. I assume you're hoping to use CASA on openSUSE for user credential storage(Firefox, GroupWise, etc) as well? Thanks for you input, Jim -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 User delder@novacoast.com added comment https://bugzilla.novell.com/show_bug.cgi?id=377573#c17 --- Comment #17 from Dan Elder <delder@novacoast.com> 2008-08-19 09:16:01 MDT --- Hi Jim, Thank you for the additional information, that makes a lot more sense to me. I've primarily been a SLED user so that's essentially the behavior I was trying to reproduce on OpenSUSE. The Firefox extension in particular was very useful as not only did it do a better job of recognizing password fields but you could lock and unlock the keystore very easily from the GUI/applet. Given the amount of nasty things that can happen to a web browser I've never felt comfortable having my passwords available to it all the time. The CASA interaction with 398625 doesn't make any sense to me either. It's the only change on my system though that's happened recently but it could also just be luck :) I'll be on the SLED 11 beta so I'll make sure to do my CASA testing there. Thanks, Dan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=377573 Jim Norman <jnorman@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jnorman@novell.com |rsavitha@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com