June 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 765461] New: first steps of installation are not localized although language is selected
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=765461 https://bugzilla.novell.com/show_bug.cgi?id=765461#c0 Summary: first steps of installation are not localized although language is selected Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Translations AssignedTo: ke(a)suse.com ReportedBy: honyczek(a)centrum.cz QAContact: ke(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 If you on boot or at first installer step select some localization, it's ignored from Welcome to Disk steps. Next User Settings step and so on are OK. Tested on NET and DVD installation openSUSE 12.2 Beta 1 (build 0398 i586). Reproducible: Always Steps to Reproduce: 1. Boot installation DVD 2. at first step of installer select some other language (Czech, German, etc.) 3. next steps will be in English until User Settings Actual Results: There are English strings. Expected Results: There should be localized strings. -- 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.

1 9

[Bug 763779] New: YaST2 software management Seg faults when selecting delete of a package.
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=763779 https://bugzilla.novell.com/show_bug.cgi?id=763779#c0 Summary: YaST2 software management Seg faults when selecting delete of a package. Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: upscope(a)nwi.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.8.3 Safari/534.34 Enter YaST2 --> Software Management --> Select delete (X) on package boost-license1_46_1 - Boost License under @System. Seg faults Reproducible: Always Steps to Reproduce: 1. Enter YaST2 --> Software Management --> 2. Right click on package boost-license1_46_1 - Boost License under @System. 3. Select X 4. Crashes with error message above. Actual Results: Crashed with following message: Kdialog Error Message: Code ------------ YaST got signal 11 at YCP file PackagesUI.ycp:280 /sbin/yast2: line 427: 11496 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS /Code -------------- Expected Results: Expect it to change from keep to red X, then allow me to continue. Have not tried on other rpms. openSUSE MS4 (Factory) KDE 4.8.3 Factory Intel DX48BT2 Motherboard 2.53 MHZ Core 2 duo 8GB Ram 3- 1TB Drives and a320 GB drive MS4 is on seperate 1 TB drive, other has 12.1, other Backup. 320 empty. -- 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.

1 7

[Bug 765227] New: sysconfig security calls wrong script to set the default policy
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=765227 https://bugzilla.novell.com/show_bug.cgi?id=765227#c0 Summary: sysconfig security calls wrong script to set the default policy Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ManuelStol(a)operamail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.10.229 Version/11.64 YaST sysconfig editor calls 'polkit_default_privs' instead of 'set_polkit_default_privs', when a default policy setting has been changed. In /etc/sysconfig/security line 5 is: ## Config: polkit_default_privs This should be: ## Config: set_polkit_default_privs I think the name of the script has changed sometime in the past without updating the sysconfig script. So earlier SuSE versions may be affected as well. Reproducible: Always Steps to Reproduce: 1. Start YaST 2. Start: System > /etc/sysconfig Editor 3. Select: System > Security > PolicyKit 4. Change a '*_PRIVS' setting 5. Click [Ok] Actual Results: The sysconfig Editor tries to call the script 'polkit_default_privs', which does not exist. Expected Results: The script '/sbin/set_polkit_default_privs' should be called to set the changes. The 'Config:' argument in the sysconfig scripts is used in /usr/lib/YaST2/bin/parse_configs.pl -- 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.

1 3

[Bug 738102] New: udevd cannot start on boot
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=738102 https://bugzilla.novell.com/show_bug.cgi?id=738102#c0 Summary: udevd cannot start on boot Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa(a)suse.de CC: fcrozat(a)suse.com Found By: --- Blocker: --- Every other bootup of a freshly installed 12.1 (using systemd) fails to start udevd. Messages on console 1 are basically those (could not cut'n'paste) udevd: worker did not accept message -1 (Connection refused), kill it [a few times] udevd: bind failed: Address already in use udevd: error binding udev control socket [few times] Aftwards no network is available (apparently no network device up). Last time it worked to systemctl start udev.service to make the system work (somehow). Now tried the same and switched between console and X11 and my machine died completely. (I'm not sure this is directly connected yet) I _guess_ that udevd failing is somehow related to systemd and therefore adding fcrozat to CC. -- 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.

1 4

[Bug 764418] New: YaST2 (GTK) crashes on package search
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=764418 https://bugzilla.novell.com/show_bug.cgi?id=764418#c0 Summary: YaST2 (GTK) crashes on package search Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sbrabec(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- YaST2 crashes whenever I try to search for package. Here is the backtrace: Core was generated by `/usr/lib/YaST2/bin/y2base sw_single gtk'. Program terminated with signal 11, Segmentation fault. #0 0x00007f5d1eaba1bd in ?? () from /usr/lib64/YaST2/plugin/libpy2gtk_pkg.so.2 Thread 2 (Thread 0x7f5d3881b740 (LWP 7548)): #0 0x00007f5d36fb82ed in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x00007f5d349a0692 in YUI::waitForUIThread() () from /usr/lib64/libyui.so.4 #2 0x00007f5d34c22310 in YUIFunction::evaluateCall() () from /usr/lib64/YaST2/plugin/libpy2UI.so.2 #3 0x00007f5d37f4030d in YEFunction::evaluate (this=0x10533e0, cse=<optimized out>) at YExpression.cc:3129 #4 0x00007f5d37f41274 in YEPropagate::evaluate (this=0x1052d70, cse=<optimized out>) at YExpression.cc:1158 #5 0x00007f5d37f505b7 in YSAssign::evaluate (this=0x1053340, cse=<optimized out>) at YStatement.cc:653 #6 0x00007f5d37f610cb in YBlock::evaluate (this=0xfa6530, cse=<optimized out>) at YBlock.cc:632 #7 0x00007f5d37f35297 in Y2YCPFunction::evaluateCall (this=<optimized out>) at YExpression.cc:3366 #8 0x00007f5d37f4030d in YEFunction::evaluate (this=0x156dc90, cse=<optimized out>) at YExpression.cc:3129 #9 0x00007f5d37f505b7 in YSAssign::evaluate (this=0x156ddb0, cse=<optimized out>) at YStatement.cc:653 #10 0x00007f5d37f610cb in YBlock::evaluate (this=0x156d0f0, cse=<optimized out>) at YBlock.cc:632 #11 0x00007f5d37f4a5b1 in YSBlock::evaluate (this=<optimized out>, cse=<optimized out>) at YStatement.cc:326 #12 0x00007f5d37f4e8a4 in YSIf::evaluate (this=0x1576b20, cse=<optimized out>) at YStatement.cc:1057 #13 0x00007f5d37f610cb in YBlock::evaluate (this=0x156cf60, cse=<optimized out>) at YBlock.cc:632 #14 0x00007f5d37f4a5b1 in YSBlock::evaluate (this=<optimized out>, cse=<optimized out>) at YStatement.cc:326 #15 0x00007f5d37f4e8a4 in YSIf::evaluate (this=0x1576b70, cse=<optimized out>) at YStatement.cc:1057 #16 0x00007f5d37f610cb in YBlock::evaluate (this=0x156acf0, cse=<optimized out>) at YBlock.cc:632 #17 0x00007f5d37f4ecd6 in YSDo::evaluate (this=0x156acb0, cse=<optimized out>) at YStatement.cc:1471 #18 0x00007f5d37f610cb in YBlock::evaluate (this=0xf6fe50, cse=<optimized out>) at YBlock.cc:632 #19 0x00007f5d37f35297 in Y2YCPFunction::evaluateCall (this=<optimized out>) at YExpression.cc:3366 #20 0x00007f5d37f4030d in YEFunction::evaluate (this=0x156aa80, cse=<optimized out>) at YExpression.cc:3129 #21 0x00007f5d37f50361 in YSReturn::evaluate (this=0x1569350, cse=<optimized out>) at YStatement.cc:436 #22 0x00007f5d37f610cb in YBlock::evaluate (this=0x15913e0, cse=<optimized out>) at YBlock.cc:632 #23 0x00007f5d37f4a5b1 in YSBlock::evaluate (this=<optimized out>, cse=<optimized out>) at YStatement.cc:326 #24 0x00007f5d37f4e837 in YSIf::evaluate (this=0x1591050, cse=false) at YStatement.cc:1062 #25 0x00007f5d37f610cb in YBlock::evaluate (this=0x649de0, cse=<optimized out>) at YBlock.cc:632 #26 0x00007f5d37f2e62d in YCPCodeRep::evaluate (this=0x1576370, cse=false) at YCPCode.cc:82 #27 0x00007f5d38412fd9 in Y2WFMComponent::doActualWork (this=0x64a820, arglist=<optimized out>, displayserver=0x636030) at Y2WFMComponent.cc:200 #28 0x00007f5d37cadb58 in main (argc=<optimized out>, argv=<optimized out>) at genericfrontend.cc:873 #29 0x00007f5d35c9a455 in __libc_start_main (main=0x400690 <main@plt>, argc=3, ubp_av=0x7fff18cb0478, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff18cb0468) at libc-start.c:226 #30 0x00000000004006d9 in _start () at ../sysdeps/x86_64/elf/start.S:113 Thread 1 (Thread 0x7f5d2a87b700 (LWP 7549)): #0 0x00007f5d1eaba1bd in ?? () from /usr/lib64/YaST2/plugin/libpy2gtk_pkg.so.2 #1 0x00007f5d1eabe6fe in YGPackageSelector::Impl::refreshQuery() () from /usr/lib64/YaST2/plugin/libpy2gtk_pkg.so.2 #2 0x00007f5d1eae66af in YGtkPkgQueryWidget::notifyDelay(int)::inner::timeout_cb(void*) () from /usr/lib64/YaST2/plugin/libpy2gtk_pkg.so.2 #3 0x00007f5d2c878fab in g_timeout_dispatch (source=0x17158a0, callback=<optimized out>, user_data=<optimized out>) at gmain.c:3882 #4 0x00007f5d2c878415 in g_main_dispatch (context=0x16143b0) at gmain.c:2539 #5 g_main_context_dispatch (context=0x16143b0) at gmain.c:3075 #6 0x00007f5d2c878748 in g_main_context_iterate (context=0x16143b0, block=<optimized out>, dispatch=1, self=) at gmain.c:3146 #7 0x00007f5d2c878804 in g_main_context_iteration (context=0x16143b0, may_block=1) at gmain.c:3207 #8 0x00007f5d2f5b3c6c in YGUI::waitInput(unsigned long, bool) () from /usr/lib64/YaST2/plugin/libpy2gtk.so.2 #9 0x00007f5d349c09a6 in YDialog::waitForEvent(int) () from /usr/lib64/libyui.so.4 #10 0x00007f5d2f5b2789 in YGUI::runPkgSelection(YWidget*) () from /usr/lib64/YaST2/plugin/libpy2gtk.so.2 #11 0x00007f5d34c2efac in YCP_UI::RunPkgSelection(YCPValue const&) () from /usr/lib64/YaST2/plugin/libpy2UI.so.2 #12 0x00007f5d34c1ad6d in YUINamespace::RunPkgSelection(YCPValue const&) () from /usr/lib64/YaST2/plugin/libpy2UI.so.2 #13 0x00007f5d34c1e0bc in YUIFunction::evaluateCall_int() () from /usr/lib64/YaST2/plugin/libpy2UI.so.2 #14 0x00007f5d34c34669 in YCPBuiltinCaller::call() () from /usr/lib64/YaST2/plugin/libpy2UI.so.2 #15 0x00007f5d349a0db1 in YUI::uiThreadMainLoop() () from /usr/lib64/libyui.so.4 #16 0x00007f5d349a0f0e in start_ui_thread(void*) () from /usr/lib64/libyui.so.4 #17 0x00007f5d36fb1e0e in start_thread (arg=0x7f5d2a87b700) at pthread_create.c:305 #18 0x00007f5d35d5d28d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 -- 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.

1 6

[Bug 738588] New: systemd boot failed with mdadm arrays
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=738588 https://bugzilla.novell.com/show_bug.cgi?id=738588#c0 Summary: systemd boot failed with mdadm arrays Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hnsz2002(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 If mountpoints on md array, system booting hang up, because cannot mount the partition. Reproducible: Always Steps to Reproduce: 1. Place your system (/,/boot,/home) on md array (on my pc is a 3disk raid5) 2. Do it the neccassary things (mdadm.conf,fstab fix, grub kernel command line fix...) 3. And try to boot with systemd (with legacy sysvinit boot my system correctly) Actual Results: Booting hangup, emergency system, give root passoword for login... Then i press ctrl+d once or twice, and the boot process continue. Expected Results: Booting without any problem here is my boot log: http://paste.opensuse.org/80511697 -- 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.

1 13

[Bug 746704] New: sudo: must be setuid root
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=746704 https://bugzilla.novell.com/show_bug.cgi?id=746704#c0 Summary: sudo: must be setuid root Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: vcizek(a)suse.com ReportedBy: jslaby(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Sudo doesn't work in factory. For about 10 days. It just does nothing: $ sudo echo ahoj $ If one straces the process, they can see: write(2, "sudo", 4sudo) = 4 write(2, ": ", 2: ) = 2 write(2, "must be setuid root", 19must be setuid root) = 19 write(2, "\n", 1 Otherwise the error cannot be seen? Why? # rpm -V sudo 5S.T..... c /etc/sudoers # ll /usr/bin/sudo -rwsr-xr-x 1 root root 79768 1. úno 14.08 /usr/bin/sudo -- 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.

1 68

[Bug 757668] New: X crashing when I attempt to "sudo -s"
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=757668 https://bugzilla.novell.com/show_bug.cgi?id=757668#c0 Summary: X crashing when I attempt to "sudo -s" Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jeffm(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Created an attachment (id=486564) --> (http://bugzilla.novell.com/attachment.cgi?id=486564) .xsession-errors.old After fixing my gnome-shell systemd session crash issue reported in bnc#757666, I found that X is still crashing. I've attached my .xsession-errors. There's nothing out of the ordinary in /var/log/Xorg.0.log.old. I also see this in /var/log/messages: Apr 17 23:49:46 jetfire sudo: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/jeffm/keyring-JxbzPn/control Apr 17 23:49:46 jetfire sudo: gkr-pam: couldn't unlock the login keyring. Apr 17 23:49:46 jetfire sudo: jeffm : TTY=pts/0 ; PWD=/home/jeffm ; USER=root ; COMMAND=/bin/bash Apr 17 23:49:46 jetfire systemd-logind[605]: Removed session 7. Apr 17 23:49:46 jetfire gdm-simple-slave[3474]: WARNING: Freeing conversation 'gdm' with active job Apr 17 23:49:46 jetfire console-kit-daemon[891]: rmdir: failed to remove `/var/run/dbus/at_console/jeffm': Directory not empty Apr 17 23:49:46 jetfire gnome-session[3776]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 17 23:49:46 jetfire polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.192, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) -- 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.

1 4

[Bug 728313] New: YaST crash during 2 round of update tests on installation
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=728313 https://bugzilla.novell.com/show_bug.cgi?id=728313#c0 Summary: YaST crash during 2 round of update tests on installation Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dkukawka(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- The YaST installation crash during 2 round of update tests. System was in a strange state after that, neither 'reboot' nor 'shutdown -h now' worked on console. -- 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.

1 25

[Bug 764063] New: cdemu-daemon: suse-dbus-unauthorized-service
by bugzilla_noreply＠novell.com 05 Jun '12

05 Jun '12

https://bugzilla.novell.com/show_bug.cgi?id=764063 https://bugzilla.novell.com/show_bug.cgi?id=764063#c0 Summary: cdemu-daemon: suse-dbus-unauthorized-service Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- filesystem/cdemu-daemon is almost ready for submission to factory. cdemu-daemon.x86_64: E: suse-dbus-unauthorized-service (Badness: 10000) /usr/share/dbus-1/system-services/net.sf.cdemu.CDEMUD_Daemon.service cdemu-daemon.x86_64: E: suse-dbus-unauthorized-service (Badness: 10000) /etc/dbus-1/system.d/cdemud-dbus.conf The package installs a DBUS system service file. If the package is intended for inclusion in any SUSE product please open a bug report to request review of the service by the security team. -- 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.

1 12