July 2010 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 587014] New: Winbind offline authentication not working after upgrade to samba 3.5.x
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=587014 http://bugzilla.novell.com/show_bug.cgi?id=587014#c0 Summary: Winbind offline authentication not working after upgrade to samba 3.5.x Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: koen.dewitte(a)jandenul.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.1 Safari/533.2 Using OSS11.2 as desktop on a AD2003 domain with offline login enabled. After upgrade to the 3.5 stack (tried 3.5.0 and 3.5.1) I can no longer user offline login. It seems there is a problem with the tdb in the backend. This is what I get in the log for version 3.5 [2010/03/07 09:19:23, 0] winbindd/winbindd.c:1093(main) winbindd version 3.5.0-1.1-2315-SUSE-SL11.2 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2010/03/07 09:19:23.416658, 1] lib/tdb_validate.c:470(tdb_validate_and_backup) tdb '/var/lib/samba/winbindd_cache.tdb' is invalid [2010/03/07 09:19:23.416779, 1] lib/tdb_validate.c:476(tdb_validate_and_backup) No backup found. [2010/03/07 09:19:23.416935, 1] lib/tdb_validate.c:494(tdb_validate_and_backup) Corrupt tdb stored as '/var/lib/samba/winbindd_cache.tdb.corrupt' [2010/03/07 09:19:23.416967, 0] winbindd/winbindd_cache.c:4094(winbindd_cache_validate_and_initialize) winbindd cache tdb corrupt and no backup could be restored. [2010/03/07 09:19:23.417420, 0] winbindd/winbindd_cache.c:3076(initialize_winbindd_cache) initialize_winbindd_cache: clearing cache and re-creating with version number 1 And the same for 3.5.1 winbindd version 3.5.1-1.1-2323-SUSE-SL11.2 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2010/03/10 10:09:24.823684, 1] lib/tdb_validate.c:470(tdb_validate_and_backup) tdb '/var/lib/samba/winbindd_cache.tdb' is invalid [2010/03/10 10:09:24.823738, 1] lib/tdb_validate.c:478(tdb_validate_and_backup) backup '/var/lib/samba/winbindd_cache.tdb.bak' found. [2010/03/10 10:09:24.824374, 1] lib/tdb_validate.c:482(tdb_validate_and_backup) Backup '/var/lib/samba/winbindd_cache.tdb.bak' is invalid. [2010/03/10 10:09:24.824437, 1] lib/tdb_validate.c:494(tdb_validate_and_backup) Corrupt tdb stored as '/var/lib/samba/winbindd_cache.tdb.corrupt' [2010/03/10 10:09:24.824555, 0] winbindd/winbindd_cache.c:3103(initialize_winbindd_cache) initialize_winbindd_cache: clearing cache and re-creating with version number 1 To fix it, i have to downgrade. (To the OSS11.2 3.4.2 standard) [2010/03/10 11:17:04, 0] winbindd/winbindd.c:1244(main) winbindd version 3.4.2-1.1.3.1-2229-SUSE-SL11.2 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2010/03/10 11:17:04, 0] winbindd/winbindd_cache.c:3673(cache_traverse_validate_fn) cache_traverse_validate_fn: unknown cache entry key : [2010/03/10 11:17:04, 0] ../lib/util/util.c:304(_dump_data) [0000] 4E 44 52 2F 52 4F 4F 54 44 4F 4D 41 49 4E 2F 32 NDR/ROOT DOMAIN/2 [0010] 2F 0F 00 00 00 00 00 00 00 0F 00 00 00 44 45 5F /....... .....DE_ [0020] 4E 55 4C 5F 4E 45 54 57 4F 52 4B 00 00 05 00 00 NUL_NETW ORK..... [0030] 00 00 00 00 00 05 00 00 00 52 4F 4F 54 00 00 00 ........ .ROOT... [0040] 00 08 00 00 00 ..... [2010/03/10 11:17:04, 0] winbindd/winbindd_cache.c:3675(cache_traverse_validate_fn) data : [2010/03/10 11:17:04, 0] ../lib/util/util.c:304(_dump_data) [0000] 2F 68 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 /h...... ........ [0010] 73 00 00 C0 s... [2010/03/10 11:17:04, 1] lib/tdb_validate.c:459(tdb_validate_and_backup) tdb '/var/lib/samba/winbindd_cache.tdb' is invalid [2010/03/10 11:17:04, 1] lib/tdb_validate.c:467(tdb_validate_and_backup) backup '/var/lib/samba/winbindd_cache.tdb.bak' found. [2010/03/10 11:17:04, 1] lib/tdb_validate.c:488(tdb_validate_and_backup) valid backup '/var/lib/samba/winbindd_cache.tdb.bak' found [2010/03/10 11:17:04, 1] lib/tdb_validate.c:496(tdb_validate_and_backup) Restored tdb backup from '/var/lib/samba/winbindd_cache.tdb.bak' Reproducible: Always Steps to Reproduce: 1.Install OSS11.2 and enable AD login with offline enabled 2.upgrade to latest samba stable packages (3.5.1) 3.try to login offline Actual Results: "User is not known to the underlying authentication module" Also, you do not see the user in the GDM screen at login (when offline!) Expected Results: normally you can login with an AD user offline and see that cached account in the GDM. When logging in you get the message "logging in with cached credentials" -- 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 12

[Bug 586555] New: lxde dumps messages to console
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586555 http://bugzilla.novell.com/show_bug.cgi?id=586555#c0 Summary: lxde dumps messages to console Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE AssignedTo: andrea(a)opensuse.org ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- the error messages from the X session are dumped to the console (/dev/tty1) when lxdm is used. lxdm should detach from the console and session messages should go to ~/.xsession-errors. looks like /etc/X11/xdm/Xsession is not executed -- 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 13

[Bug 586486] New: Multiple Issues with Yast Configuration of Postfix MTA for Relaying over SMTP
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586486 http://bugzilla.novell.com/show_bug.cgi?id=586486#c0 Summary: Multiple Issues with Yast Configuration of Postfix MTA for Relaying over SMTP Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andrew(a)acooke.org QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 The Yast configuration of Postfix as MTA, using the standard (not advanced) mode, for delivering mail over SMTP to a relay, has a number of issues. 1 - When using TLS authentication (SASL) the host address is not surrounded with [] as recommended here - http://www.postfix.org/SASL_README.html (see section titled "Enabling SASL authentication in the Postfix SMTP/LMTP client"). This is necessary because often the same name (mail.example.com or smtp.example.com) is used both as a relay and to handle incoming mail. Only the relay needs authentication, and so is given one physical machine, while other physical machines handle the main mail volume. In such a case, MX records point to the "other" machines, and [] is necessary to use the "real" machine (which is the only one with autentication). For a concrete example of the pain this causes please see http://forum.webfaction.com/viewtopic.php?pid=15066 2 - When the config is changed in Yast (eg the SMT server name changed), the changes appear in /etc/systconfig/postfix and sasl_passwd, but not in main.cnf. 3 - When the config is changed in Yast (eg the SMT auth details changed), the sasl_passwd.db file is not regenerated with "postmap sasl_passwd". Reproducible: Always Steps to Reproduce: 1. Use Yast to configure SMTP 2. See it fail to work in the case described above, where MX names are used instead of the exact, given host. 3. Change details 4. See how the updated details are not used in subsequent connections. -- 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 16

[Bug 586376] New: network settings: "activate device" event -- add option for exclusive activation
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586376 http://bugzilla.novell.com/show_bug.cgi?id=586376#c0 Summary: network settings: "activate device" event -- add option for exclusive activation Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Yast -> network devices -> network settings -> interface -> activate device Currently there are several options, like on boot, on cable connection, manual, etc. Let's focus on cable connection -- when cable is connected that device is activated. That is what this option says. But what this option _does not_ say is this activation is exclusive, i.e. it will shutdown all other active interfaces. I am not discussing if such implicit, additional action is useful or not (for me not), but anyway, if there is an _extra_ action, there should be an _extra_ option. Namely: [ ] exclusive activation that way user could set/control if she/he really wants exclusive connection over only one interface. This way also it would be finally possible to use "on cable connection" settings with multiple interfaces/connections (currently it is not possible and user has to set it up manually with ifup). -- 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 7

[Bug 586172] New: sysfs: cannot create duplicate filename '/bus/ieee1394/drivers/sbp2...
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c0 Summary: sysfs: cannot create duplicate filename '/bus/ieee1394/drivers/sbp2... Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jpschewe(a)mtu.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I have a Western Digital MyBook attached via Firewire to my desktop. With the latest 11.2 kernel I'm receiving this error on every boot. The drive works fine, but the warning is concerning. <6>[ 13.564098] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:10.1/input/input5 <7>[ 13.761068] ieee1394: Node added: ID:BUS[0-00:1023] GUID[0090a976213be423] <7>[ 13.761150] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0010dc0000cf92b6] <6>[ 13.930522] scsi6 : SBP-2 IEEE-1394 <6>[ 18.409456] ieee1394: sbp2: Logged into SBP-2 device <6>[ 18.439171] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [1024] <5>[ 18.569852] scsi 6:0:0:0: Direct-Access WD My Book 1025 PQ: 0 ANSI: 4 <5>[ 18.586911] sd 6:0:0:0: Attached scsi generic sg2 type 0 <6>[ 18.605107] scsi7 : SBP-2 IEEE-1394 <5>[ 18.643641] sd 6:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB) <5>[ 18.691159] sd 6:0:0:0: [sdb] Write Protect is off <7>[ 18.707856] sd 6:0:0:0: [sdb] Mode Sense: 10 00 00 00 <5>[ 18.723828] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 18.740441] sd 6:0:0:0: [sdb] Assuming drive cache: write through <5>[ 18.841637] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 18.858351] sd 6:0:0:0: [sdb] Assuming drive cache: write through <6>[ 18.875218] sdb: sdb1 <5>[ 19.509210] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 19.526010] sd 6:0:0:0: [sdb] Assuming drive cache: write through <5>[ 19.542626] sd 6:0:0:0: [sdb] Attached SCSI disk <6>[ 22.908499] ieee1394: sbp2: Logged into SBP-2 device <6>[ 22.938881] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [1024] <5>[ 23.074794] scsi 7:0:1:0: Enclosure WD My Book Device PQ: 0 ANSI: 4 <5>[ 23.091848] scsi 7:0:1:0: Attached scsi generic sg3 type 13 <5>[ 23.108446] ses 7:0:1:0: Attached Enclosure device <4>[ 23.126186] ------------[ cut here ]------------ <4>[ 23.142608] WARNING: at /usr/src/packages/BUILD/kernel-default-2.6.31.12/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xde/0x150() <4>[ 23.159767] Hardware name: MS-7207PV <4>[ 23.176784] sysfs: cannot create duplicate filename '/bus/ieee1394/drivers/sbp2/0090a976213be423-1' <4>[ 23.194258] Modules linked in: ses enclosure sbp2 snd_hda_codec_realtek ppdev pcspkr ohci1394 floppy ieee1394 parport_pc parport sr_mod sg cdrom snd_hda_intel snd_hda_codec snd_hwdep snd_pcm button snd_timer amd64_edac_mod forcedeth edac_core k8temp snd snd_page_alloc nvidia(P) i2c_nforce2 preloadtrace linear raid456 raid6_pq async_xor async_memcpy async_tx xor raid0 dm_snapshot dm_mirror dm_region_hash dm_log reiserfs aic7xxx scsi_transport_spi edd dm_mod raid1 fan ide_pci_generic amd74xx ide_core ata_generic sata_nv pata_amd thermal processor thermal_sys <4>[ 23.268356] Pid: 624, comm: knodemgrd_0 Tainted: P 2.6.31.12-0.1-default #1 <4>[ 23.287049] Call Trace: <4>[ 23.305454] [<ffffffff81011749>] try_stack_unwind+0x189/0x1b0 <4>[ 23.324009] [<ffffffff8101013d>] dump_trace+0x9d/0x330 <4>[ 23.342316] [<ffffffff81011254>] show_trace_log_lvl+0x64/0x90 <4>[ 23.360635] [<ffffffff810112a3>] show_trace+0x23/0x40 <4>[ 23.378712] [<ffffffff81555268>] dump_stack+0x81/0x9e <4>[ 23.378719] [<ffffffff8106db80>] warn_slowpath_common+0x80/0xd0 <4>[ 23.378724] [<ffffffff8106dc5b>] warn_slowpath_fmt+0x4b/0x70 <4>[ 23.378730] [<ffffffff811d6f3e>] sysfs_add_one+0xde/0x150 <4>[ 23.378735] [<ffffffff811d756b>] sysfs_do_create_link+0x14b/0x1a0 <4>[ 23.378740] [<ffffffff811d7621>] sysfs_create_link+0x21/0x40 <4>[ 23.378746] [<ffffffff8135fac8>] driver_sysfs_add+0x38/0xa0 <4>[ 23.378751] [<ffffffff81360050>] device_bind_driver+0x20/0x50 <4>[ 23.378756] [<ffffffff813600cb>] device_attach+0x4b/0xc0 <4>[ 23.378761] [<ffffffff8135e1c1>] bus_rescan_devices_helper+0x61/0x90 <4>[ 23.378766] [<ffffffff8135ed68>] bus_for_each_dev+0x78/0xc0 <4>[ 23.378771] [<ffffffff8135edd7>] bus_rescan_devices+0x27/0x50 <4>[ 23.378787] [<ffffffffa0c575a2>] nodemgr_host_thread+0x272/0x330 [ieee1394] <4>[ 23.378808] [<ffffffff8108ea66>] kthread+0xb6/0xc0 <4>[ 23.378814] [<ffffffff8100d70a>] child_rip+0xa/0x20 <4>[ 23.378819] ---[ end trace 02b373f7d663109a ]--- Reproducible: Always 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 30