July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 589433] New: Install grub into root (/) partition gives error
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589433 http://bugzilla.novell.com/show_bug.cgi?id=589433#c0 Summary: Install grub into root (/) partition gives error Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fisiu82(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=349250) --> (http://bugzilla.novell.com/attachment.cgi?id=349250) YaST2 screen from installation of grub User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.8 Firefox/3.6 During install 11.3 M3 from KDE LiveCD on spare partition, installation of grub gave me an error. By default setup wanted to install grub into mbr (finally it works!) but I have fully working system on first partition with grub in mbr. So I decided to install grub into a root of new system (M3). Then I got this error. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 589431] New: preload kmp has broken supplements
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589431 http://bugzilla.novell.com/show_bug.cgi?id=589431#c0 Summary: preload kmp has broken supplements Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: coolo(a)novell.com ReportedBy: mls(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- $ rpm -q --supplements preload-kmp-desktop kernel-desktop packageand(kernel-desktop:preload) packageand(kernel-desktop:preload) Please remove "kernel-desktop". And one of "packageand(kernel-desktop:preload)" is enough. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 589293] New: DMZ Cursor theme needs to be removed from desktop-data-openSUSE
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589293 http://bugzilla.novell.com/show_bug.cgi?id=589293#c0 Summary: DMZ Cursor theme needs to be removed from desktop-data-openSUSE Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: awafaa(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 Currently desktop-data-openSUSE contains the DMZ Cursor theme. As part of the Moblin submissions to Factory I submitted icon-them-dmz-cursors. There was talk about splitting it out in the past, but no real push. Any chance this can be done now? Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 589021] New: Better protect java stack
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589021 http://bugzilla.novell.com/show_bug.cgi?id=589021#c0 Summary: Better protect java stack Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: pmladek(a)novell.com QAContact: qa(a)suse.de CC: mmeeks(a)novell.com Found By: Development Blocker: --- Could you please backport the fix from http://cr.openjdk.java.net/~aph/6929067-jdk7-webrev-4/ into our openJDK package? It should better protect the java stack and help with debugging problems, for example the bug #578802. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 588998] New: yast2-schema: no element "printer" in profile.rng
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588998 http://bugzilla.novell.com/show_bug.cgi?id=588998#c0 Summary: yast2-schema: no element "printer" in profile.rng Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: qa(a)suse.de CC: mzugec(a)novell.com Found By: Development Blocker: --- I run as root "yast2 --gtk autoyast" and therein I do -> tools -> create reference profile (check only printer) -> create and then -> tools -> check validity of profile I get an error poput with the folowing xmllint error (I added only here \ to wrap the too long lines) -------------------------------------------------------------- /usr/bin/xmllint --noout --relaxng \ /usr/share/YaST2/schema/autoyast/rng/profile.rng \ /tmp/YaST2-15945-JC4X8S/printer.xml /tmp/YaST2-15945-JC4X8S/printer.xml:4: element printer: \ Relax-NG validity error : \ Element profile has extra content: printer /tmp/YaST2-15945-JC4X8S/printer.xml fails to validate -------------------------------------------------------------- I think xmllint is right because there is no element printer in /usr/share/YaST2/schema/autoyast/rng/profile.rng Adding -------------------------------------------------------- <optional> <ref name="printer"/> </optional> -------------------------------------------------------- to /usr/share/YaST2/schema/autoyast/rng/profile.rng does not help and I get another xmllint error: ------------------------------------------------------------------- /usr/bin/xmllint --noout --relaxng \ /usr/share/YaST2/schema/autoyast/rng/profile.rng \ /tmp/YaST2-15945-JC4X8S/printer.xml /usr/share/YaST2/schema/autoyast/rng/profile.rng:80: \ element ref: Relax-NG parser error : \ Reference printer has no matching definition Relax-NG schema /usr/share/YaST2/schema/autoyast/rng/profile.rng \ failed to compile ------------------------------------------------------------------- When this issue is fixed for openSUSE 11.3 please have in mind that the AutoYaST printer client in yast2-printer will change a lot for openSUSE 11.3, see bug #588679. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 588770] New: Installer complains that the "custom bootloader isn't available anymore".
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588770 http://bugzilla.novell.com/show_bug.cgi?id=588770#c0 Summary: Installer complains that the "custom bootloader isn't available anymore". Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chobbs(a)siloamsprings.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.9 (KHTML, like Gecko) Chrome/5.0.307.7 Safari/532.9 I'm installing Milestone 3 under VirtualBox. When the installer makes it to the Installation Settings screen, I opened the Booting screen, then Bootloader Options and changed the boot time from 8 seconds to 3. After saving the option, when the installer returns to the Installation Settings screen, a dialog pops up that reads "Custom bootloader isn't available anymore. Would you like to proceed with the default bootloader." I have not yet tried to reproduce this on actual hardware, so it may be a vbox thing. Reproducible: Always Steps to Reproduce: 1. Run the installer. 2. Change the boot time from 8 to 3 seconds in GRUB's options 3. Save the changes. Actual Results: A custom bootloader dialog pops up explaining that the custom bootloader is no longer available. Expected Results: The installer should return to the Installation Settings screen without error. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 588679] New: yast2-printer: AutoYaST client destroys information in cupsd.conf
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588679 http://bugzilla.novell.com/show_bug.cgi?id=588679#c0 Summary: yast2-printer: AutoYaST client destroys information in cupsd.conf Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEEDINFO Severity: Major Priority: P5 - None Component: AutoYaST AssignedTo: jsmeix(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: qa(a)suse.de CC: ug(a)novell.com, mzugec(a)novell.com Found By: Development Blocker: --- When AutoYaST calls the "Write" function in printer_auto.ycp it results - a /etc/cups/cupsd.conf without any comments and without any indentation but with a strange unexpected re-ordering of the entries and - a /etc/cups/client.conf without any comments which is totally empty if there was no active entry in the /etc/cups/client.conf of the system wherefrom the AutoYaST control file was created. Because the comments provide useful and sometimes even very important information for the admin, the yast2-printer AutoYaST client destroys information. Because the ordering in /etc/cups/cupsd.conf in the cloned system is the well known upstream ordering, an unexpected strange re-ordering makes it very hard to understand the /etc/cups/cupsd.conf file afterwards. Therefore the bug severity is "major". Details: When AutoYaST calls the "Write" function in printer_auto.ycp it calls Printerlib::WriteClientSettings and Printerlib::WriteCupsSettings which call SCR::Write(.cups.client, ay) and SCR::Write(.cups.server, ay) where ay is a map as follows: ------------------------------------------------------------------------ $["cups_remote_server": $[], "server_settings": $["BrowseAllow":["all"], "BrowseOrder":["allow,deny"], "Browsing":["On"], "DefaultAuthType":["Basic"], "DefaultPolicy":["default"], "Listen":["localhost:631", "/var/run/cups/cups.sock"], "LogLevel":["info"], "SystemGroup":["sys root"], .. ------------------------------------------------------------------------ and the /etc/cups/cupsd.conf file is as follows: ------------------------------------------------------------------------ Listen localhost:631 Listen /var/run/cups/cups.sock Browsing On BrowseOrder allow,deny BrowseAllow none BrowseDeny all DefaultPolicy default DefaultAuthType Basic SystemGroup sys root .. LogLevel info ------------------------------------------------------------------------ I assume because a YCP map does not keep any ordering but the actual sequence of its entries is random, one gets also a random re-ordered cupds.conf file written. Uwe, for openSUSE 11.3 I will clean it up, compare https://bugzilla.novell.com/show_bug.cgi?id=582680#c35 Which YCP structure works for AutoYaST so that config files are written 100% identical on the target system? I.e. on one same system "Read"->"Export"->"Import"->"Write" must result 100% identical (i.e. unchanged) config files. I would prefer to have both cupsd.conf and client.conf as XML CDATA in the AutoYaST control file. Which YCP data must the "Export" function in printer_auto.ycp provide to AutoYaST so that the result are two XML CDATA sections, one for cupsd.conf and one for client.conf? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 20

[Bug 588325] New: AUDIT-0: lockdev
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588325 http://bugzilla.novell.com/show_bug.cgi?id=588325#c0 Summary: AUDIT-0: lockdev Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: security-team(a)suse.de ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- lockdev is used to create lock files in /var/lock on behalf of users. To avoid having /var/lock world writeable the /usr/sbin/lockdev helper is setgid 'lock' and /var/lock writable only by group 'lock'. The lockdev package is currently staged for Factory in Base:System. Upstream git repo is here: git://git.debian.org/git/lockdev/lockdev -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 588293] New: systemtap crashes during preload build
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588293 http://bugzilla.novell.com/show_bug.cgi?id=588293#c0 Summary: systemtap crashes during preload build Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: tonyj(a)novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- 100% reproducible ;( Program received signal SIGSEGV, Segmentation fault. #0 0x00007ffff7bd2755 in ebl_abi_cfi (ebl=0xbabababababababa, abi_info=0x7fffffff9c70) at eblabicfi.c:62 #1 0x00007ffff7bbf68e in cie_cache_initial_state (cache=0x2daa818, fde=0x2ea9c40, address=18446744071580105296, frame=0x7fffffff9d78) at cfi.c:429 #2 __libdw_frame_at_address (cache=0x2daa818, fde=0x2ea9c40, address=18446744071580105296, frame=0x7fffffff9d78) at cfi.c:480 #3 0x00007ffff7bbfc75 in dwarf_cfi_addrframe (cache=0x2daa818, address=18446744071580105296, frame=<value optimized out>) at dwarf_cfi_addrframe.c:70 #4 0x00000000004fd4c7 in dwflpp::get_cfa_ops (this=0x1967a60, pc=18446744071580105296) at dwflpp.cxx:2835 #5 0x0000000000504e1c in dwflpp::translate_location (this=0x1967a60, pool=0x7fffffff9f70, attr=0x7fffffffa030, pc=18446744071580105296, fb_attr=0x7fffffffa050, tail=0x7fffffffa118, e=0x2db49f0) at dwflpp.cxx:1731 #6 0x0000000000508d98 in dwflpp::literal_stmt_for_local (this=0x1967a60, scopes=..., pc=18446744071580105296, local=<value optimized out>, e=0x2db49f0, lvalue=false, ty=@0x2db4bb8) at dwflpp.cxx:2341 #7 0x00000000004a5241 in dwarf_var_expanding_visitor::visit_target_symbol (this=0x7fffffffa6f0, e=0x2db49f0) at tapsets.cxx:2422 #8 0x000000000043a2a9 in require<expression> (this=0x7fffffffa6f0, e=0x2db49a0) at staptree.h:866 #9 replace<expression> (this=0x7fffffffa6f0, e=0x2db49a0) at staptree.h:882 #10 update_visitor::visit_functioncall (this=0x7fffffffa6f0, e=0x2db49a0) at staptree.cxx:2436 #11 0x00000000004399df in require<expression> (this=0x7fffffffa6f0, e=0x1979f70) at staptree.h:866 #12 replace<expression> (this=0x7fffffffa6f0, e=0x1979f70) at staptree.h:882 #13 update_visitor::visit_concatenation (this=0x7fffffffa6f0, e=0x1979f70) at staptree.cxx:2381 #14 0x0000000000438da9 in require<expression> (this=0x7fffffffa6f0, e=0x2db5010) at staptree.h:866 #15 replace<expression> (this=0x7fffffffa6f0, e=0x2db5010) at staptree.h:882 #16 update_visitor::visit_print_format (this=0x7fffffffa6f0, e=0x2db5010) at staptree.cxx:2444 #17 0x0000000000436e3f in require<expression> (this=0x7fffffffa6f0, s=0x2db5240) at staptree.h:866 #18 replace<expression> (this=0x7fffffffa6f0, s=0x2db5240) at staptree.h:882 #19 update_visitor::visit_expr_statement (this=0x7fffffffa6f0, s=0x2db5240) at staptree.cxx:2238 #20 0x00000000004368a9 in require<statement> (this=0x7fffffffa6f0, s=0x2276690) at staptree.h:866 #21 replace<statement> (this=0x7fffffffa6f0, s=0x2276690) at staptree.h:882 #22 update_visitor::visit_block (this=0x7fffffffa6f0, s=0x2276690) at staptree.cxx:2219 #23 0x0000000000491fb6 in require<statement> (this=0x2db5130, funcname=<value optimized out>, filename=<value optimized out>, line=1326, module=..., section=..., dwfl_addr=18446744071580105296, addr=1259712, q=..., scope_die=0x2276608) at staptree.h:866 #24 replace<statement> (this=0x2db5130, funcname=<value optimized out>, filename=<value optimized out>, line=1326, module=..., section=..., dwfl_addr=18446744071580105296, addr=1259712, q=..., scope_die=0x2276608) at staptree.h:882 #25 dwarf_derived_probe::dwarf_derived_probe (this=0x2db5130, funcname=<value optimized out>, filename=<value optimized out>, line=1326, module=..., section=..., dwfl_addr=18446744071580105296, addr=1259712, q=..., scope_die=0x2276608) at tapsets.cxx:2917 #26 0x0000000000494294 in dwarf_query::add_probe_point (this=0x7fffffffb070, funcname=..., filename=<value optimized out>, line=<value optimized out>, scope_die=<value optimized out>, addr=18446744071580105296) at tapsets.cxx:1071 #27 0x000000000049454a in query_statement (func=..., file=<value optimized out>, line=-25224, scope_die=0x1, stmt_addr=186, q=0x7fffffffb070) at tapsets.cxx:1158 #28 0x00000000004945f3 in query_func_info (entrypc=<value optimized out>, fi=<value optimized out>, q=0x7fffffffb070) at tapsets.cxx:1349 #29 0x0000000000495a2f in query_cu (cudie=0x7fffffff9c70, arg=0x7fffffffb070) at tapsets.cxx:1616 #30 0x0000000000500295 in dwflpp::iterate_over_cus (this=<value optimized out>, callback=0x4957a0 <query_cu(Dwarf_Die*, void*)>, data=0x7fffffffb070) at dwflpp.cxx:416 #31 0x0000000000495558 in dwarf_query::handle_query_module (this=0x7fffffffb070) at tapsets.cxx:883 #32 0x000000000049cbd7 in query_module (mod=0x196a940, name=<value optimized out>, addr=<value optimized out>, arg=0x7fffffffb070) at tapsets.cxx:1811 #33 0x00007ffff7bc45aa in dwfl_getmodules (dwfl=0x1967fe0, callback=0x49ca00 <query_module(Dwfl_Module*, void**, char const*, Dwarf_Addr, void*)>, arg=0x7fffffffb070, offset=<value optimized out>) at dwfl_getmodules.c:103 #34 0x0000000000493448 in dwarf_builder::build (this=<value optimized out>, sess=<value optimized out>, base=<value optimized out>, location=<value optimized out>, parameters=..., finished_results=<value optimized out>) at tapsets.cxx:4137 #35 0x0000000000445b44 in match_node::find_and_build (this=0x1963930, s=<value optimized out>, p=<value optimized out>, loc=<value optimized out>, pos=2, results=<value optimized out>) at elaborate.cxx:388 #36 0x0000000000445eae in match_node::find_and_build (this=0x19607d0, s=<value optimized out>, p=<value optimized out>, loc=<value optimized out>, pos=1, results=<value optimized out>) at elaborate.cxx:477 #37 0x0000000000445eae in match_node::find_and_build (this=0x758f10, s=<value optimized out>, p=<value optimized out>, loc=<value optimized out>, pos=0, results=<value optimized out>) at elaborate.cxx:477 #38 0x0000000000448ea0 in derive_probes (s=..., p=0x807570, dps=..., optional=<value optimized out>) at elaborate.cxx:715 #39 0x0000000000450b4d in semantic_pass_symbols (s=...) at elaborate.cxx:1210 #40 semantic_pass (s=...) at elaborate.cxx:1494 #41 0x000000000040fe3f in main (argc=<value optimized out>, argv=<value optimized out>) at main.cxx:1190 ==21537== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==21537== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==21537== Command: stap -s 3 -p 4 -DMAXSTRINGSIZE=300 -DMAXSKIPPED=2000 -r 2.6.33-5-default -m preloadtrace obj/default/preloadtrace.stp ==21537== ==21537== Conditional jump or move depends on uninitialised value(s) ==21537== at 0x4E4A8CB: __libdwfl_set_cfi (dwfl_module_dwarf_cfi.c:57) ==21537== by 0x4FD491: dwflpp::get_cfa_ops(unsigned long) (dwflpp.cxx:2829) ==21537== by 0x504E1B: dwflpp::translate_location(obstack*, Dwarf_Attribute*, unsigned long, Dwarf_Attribute*, location**, target_symbol const*) (dwflpp.cxx:1731) ==21537== by 0x508D97: dwflpp::literal_stmt_for_local(std::vector<Dwarf_Die, std::allocator<Dwarf_Die> >&, unsigned long, std::string const&, target_symbol const*, bool, exp_type&) (dwflpp.cxx:2341) ==21537== by 0x4A5240: dwarf_var_expanding_visitor::visit_target_symbol(target_symbol*) (tapsets.cxx:2422) ==21537== by 0x43A2A8: update_visitor::visit_functioncall(functioncall*) (staptree.h:866) ==21537== by 0x4399DE: update_visitor::visit_concatenation(concatenation*) (staptree.h:866) ==21537== by 0x438DA8: update_visitor::visit_print_format(print_format*) (staptree.h:866) ==21537== by 0x436E3E: update_visitor::visit_expr_statement(expr_statement*) (staptree.h:866) ==21537== by 0x4368A8: update_visitor::visit_block(block*) (staptree.h:866) ==21537== by 0x491FB5: dwarf_derived_probe::dwarf_derived_probe(std::string const&, std::string const&, int, std::string const&, std::string const&, unsigned long, unsigned long, dwarf_query&, Dwarf_Die*) (staptree.h:866) ==21537== by 0x494293: dwarf_query::add_probe_point(std::string const&, char const*, int, Dwarf_Die*, unsigned long) (tapsets.cxx:1071) ==21537== -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 588185] New: AppArmor: network rule
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588185 http://bugzilla.novell.com/show_bug.cgi?id=588185#c0 Summary: AppArmor: network rule Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: jeffm(a)novell.com ReportedBy: matwey.kornilov(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I suppose that there is a bug in AppArmor 2.3.1(bundled with opensuse 11.2). The 'network' rule is described in man page and openSUSE Security Guide for 11.2, but It doesn't work for me at all. Network connections aren't blocked and there aren't 'socket_create' messages in my /var/log/audit.log. I created threads in forum and some users confirmed the AppArmor behavior: http://forums.opensuse.org/applications/434684-apparmor-network-rule.html http://forums.novell.com/novell-product-support-forums/apparmor/404069-appa… Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8