December 2006 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 224985] VUL-0: dazuko 3.23 release
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224985 mt(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #2 from mt(a)novell.com 2006-12-01 02:46 MST ------- I'm going to prepare packages & check old versions. -- 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, or are watching someone who is.

1 0

[Bug 224818] RC4: Installation bails out with "cannot start novell-zmd" even though zmd is up and running
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224818 ------- Comment #34 from nabhishek(a)novell.com 2006-12-01 02:43 MST ------- The signal handler's only purpose in rug was to kill the process. This can be removed but it does not seem to be responsible for the hang. The only possible cause seems to be the changes made to mono-core. Looking at Miguel's patch (bug 221277), the new locking which was introduced could be the issue. Can someone who knows mono look at this snippet of the patch? The unlock seems to happen only in the conditional and not outside, was that intentional? diff -ru /tmp/mono-1.1.18/mono/metadata/metadata.c metadata/metadata.c --- /tmp/mono-1.1.18/mono/metadata/metadata.c 2006-10-12 20:16:07.000000000 +0200 +++ metadata/metadata.c 2006-12-01 01:14:19.000000000 +0100 @@ -1490,6 +1490,7 @@ int count = 0; gboolean found; + mono_loader_lock (); /* * According to the spec, custom modifiers should come before the byref * flag, but the IL produced by ilasm from the following signature: @@ -1561,6 +1562,7 @@ if (!do_mono_metadata_parse_type (type, m, container, ptr, &ptr)) { if (type != &stype) g_free (type); + mono_loader_unlock (); return NULL; } -- 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, or are watching someone who is.

1 0

[Bug 224775] zen-remove will attempt to remove all the packages **always**
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224775 kkaempf(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mauro(a)novell.com ------- Comment #9 from kkaempf(a)novell.com 2006-12-01 02:24 MST ------- It _is_ desired behaviour. The solver has two basic rules - carry out the users request - keep the system consistent So the removal request will be carried out and - to ensure system consistency - all dependent packages will also be removed. However, I do not understand the initial comment which talks about different behaviour in zen-remover and rug. As both are just different frontends to the same package management stack, both must show identical behaviour. Needinfo to Mauro to verify zen-remover vs. rug behaviour -- 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, or are watching someone who is.

1 0

[Bug 224924] yast2-x11: take care for fbdev restrictions
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224924 kkaempf(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hvogel(a)novell.com ------- Comment #18 from kkaempf(a)novell.com 2006-12-01 02:02 MST ------- Its a _usability issue_. YaST offers to change to color depth. So a customer will do what I did. YaST _does_ detect that this is not possible (It shows "No proposal") YaST does _not_ offer a way out. -> Deadlock -- 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, or are watching someone who is.

1 0

[Bug 224818] RC4: Installation bails out with "cannot start novell-zmd" even though zmd is up and running
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224818 aj(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lupus(a)ximian.com ------- Comment #33 from aj(a)novell.com 2006-12-01 01:29 MST ------- Why was the signal handler needed at all? Does it explain the hang - or is this a result of the mono-core change? Note: We see the hang and the earlier mono fails on a two cpu machine - I do not see it on my two one cpu machines. So, let's test this on SMP systems! -- 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, or are watching someone who is.

1 0

[Bug 224818] RC4: Installation bails out with "cannot start novell-zmd" even though zmd is up and running
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224818 ------- Comment #32 from aj(a)novell.com 2006-12-01 01:19 MST ------- Run successfully for another 840 iterations and then hung again.. -- 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, or are watching someone who is.

1 0

[Bug 224775] zen-remove will attempt to remove all the packages **always**
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224775 aj(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|zlm-code10- |kkaempf(a)novell.com |bugs(a)forge.provo.novell.com | Status|NEEDINFO |NEW Info Provider|jjoy(a)novell.com | ------- Comment #8 from aj(a)novell.com 2006-12-01 01:07 MST ------- Problem is: yast2-sound 2.14.0-10 (system) yast2-sound-2.14.0-10.i586[System packages] dependend on alsa yast2-sound-2.14.0-10.i586[System packages] is missing the requirement libasound.so.2(ALSA_0.9) which leads to: yast2-tv 2.14.0-12 (system) yast2-tv-2.14.0-12.noarch[System packages] dependend on yast2-sound yast2-tv-2.14.0-12.noarch[System packages] is missing the requirement yast2-sound which leads to: yast2_basis 10.2-145 (system) pattern:yast2_basis-10.2-145.i586[System packages] dependend on yast2-tv pattern:yast2_basis-10.2-145.i586[System packages] is missing the requirement yast2-tv and so on. So, yes this looks like desired behaviour. -- 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, or are watching someone who is.

1 0

[Bug 224834] New: Wrong czech translation for "Disabled Support for IPv6 Protocol"
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224834 Summary: Wrong czech translation for "Disabled Support for IPv6 Protocol" Product: openSUSE 10.2 Version: RC 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations AssignedTo: cihlarov(a)novell.com ReportedBy: mmarek(a)novell.com QAContact: ke(a)novell.com michal@brutus:~> msgunfmt /usr/share/YaST2/locale/cs/LC_MESSAGES/network.mo | \ grep -A1 'Support for IPv6 Protocol"' msgid "Disabled Support for IPv6 Protocol" msgstr "Podpora protokolu IPv6 povolena" # <- should be "zakázána" -- msgid "Enabled Support for IPv6 Protocol" msgstr "Podpora protokolu IPv6 povolena" This string is used in the network configuration dialog during installation. -- 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, or are watching someone who is.

1 1

[Bug 224818] RC4: Installation bails out with "cannot start novell-zmd" even though zmd is up and running
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224818 ------- Comment #31 from aj(a)novell.com 2006-12-01 00:57 MST ------- I'm testing now with the mono-core from Bug #221277. It looks much better on the machine with the problems but now I seem to run in a dead-lock: K29:~ # ps -l 4951 8345 F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD 0 S 0 4951 1 0 94 19 - 19899 stext ? 0:08 zmd /usr/lib/zmd/zmd.exe 0 S 0 8345 4401 0 83 0 - 4934 stext pts/1 0:00 /usr/bin/mono /usr/lib/rug/rug.exe ping This was iteration 475 - normally it would bail out far earlier... -- 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, or are watching someone who is.

1 0

[Bug 224775] zen-remove will attempt to remove all the packages **always**
by bugzilla_noreply＠novell.com 01 Dec '06

01 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=224775 ------- Comment #7 from jjoy(a)novell.com 2006-12-01 00:40 MST ------- Created an attachment (id=107801) --> (https://bugzilla.novell.com/attachment.cgi?id=107801&action=view) rug rm alsa -- 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, or are watching someone who is.

1 0