March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 808853] New: home:j-engel:KDE4/frescobaldi: Featurerequest
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808853 https://bugzilla.novell.com/show_bug.cgi?id=808853#c0 Summary: home:j-engel:KDE4/frescobaldi: Featurerequest Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software AssignedTo: j-engel(a)gmx.de ReportedBy: saloution(a)googlemail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Thank you very much for packaging frescobaldi. Please make it also available for opensuse 12.3. It would be more feature-complete, if you would add the following dependencies: - python-portmidi, portmidi and python-pygame for midi support I'm using frescobaldi with qsynth (in pulseaudio mode) as a software synthesizer. Works like a charm! :) At the moment I use your 12.2 package on my opensuse 12.3, but I experienced huge performance issues when opening a file (frescobaldi gui is unresponsive for ~30sec) and editing is not smooth. It is not clear to me, if this is related or not. I only remember, that I didn't run into these issues using opensuse 12.1. Best, Robert -- 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 1

[Bug 808560] New: opensuse security update not published after 5 days openSUSE-SU-2013:0395-1 & openSUSE-SU-2013:0396-1
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808560 https://bugzilla.novell.com/show_bug.cgi?id=808560#c0 Summary: opensuse security update not published after 5 days openSUSE-SU-2013:0395-1 & openSUSE-SU-2013:0396-1 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: bruno(a)ioda-net.ch QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 openSUSE security bulletin announce fixes for kernel http://lists.opensuse.org/opensuse-security-announce/2013-03/msg00004.html http://lists.opensuse.org/opensuse-security-announce/2013-03/msg00005.html But none of them are available in update channel Reproducible: Always Steps to Reproduce: 1. try zypper patch as mentionned in security bulletin 2. zypper give no patch available 3. Actual Results: zypper in -t patch openSUSE-2013-175 zypper in -t patch openSUSE-2013-175 Loading repository data... Reading installed packages... 'openSUSE-2013-175' not found in package names. Trying capabilities. No provider of 'patch:openSUSE-2013-175' found. Resolving package dependencies... Nothing to do. Expected Results: Patches installed The updated kernel are available in 12.2-update-test repository. Did someone forget to push them on the main update channel ? -- 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 780006] New: PROMPT_FOR_CONFIRM has no effect with systemd
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=780006 https://bugzilla.novell.com/show_bug.cgi?id=780006#c0 Summary: PROMPT_FOR_CONFIRM has no effect with systemd Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alien.www(a)gmx.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 With PROMPT_FOR_CONFIRM="yes" set in /etc/sysconfig/boot the system should ask whether to confirm every step of the boot process, for interactive debugging. It works with SysVinit, but with default systemd the boot process occurs as usual, without any prompts. Reproducible: Always Steps to Reproduce: 1. Set PROMPT_FOR_CONFIRM="yes" in /etc/sysconfig/boot 2. Reboot Actual Results: The boot process runs as usual, without prompts Expected Results: The system should ask whether to confirm every step of the boot process -- 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 5

[Bug 744818] New: /etc/sysconfig/ulimit has no effect on systemd based systems
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=744818 https://bugzilla.novell.com/show_bug.cgi?id=744818#c0 Summary: /etc/sysconfig/ulimit has no effect on systemd based systems Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: sbrabec(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- In 11.4 it was possible to enable core files by editing /etc/sysconfig/ulimit. Starting with 12.1, it is not possible any more. It seems that systemd does not read this file at all. It seems that systemd does not provide any feature that would allow to set system wide limits. -- 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 11

[Bug 803006] New: Error while creating client module users in yast2
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=803006 https://bugzilla.novell.com/show_bug.cgi?id=803006#c0 Summary: Error while creating client module users in yast2 Classification: openSUSE Product: openSUSE 12.2 Version: RC 1 Platform: 64bit OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hloeffler3(a)gmx.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 I try to open users and groups (Benutzer- und Gruppenverwaltung) and get this message Error while creating client module users excerpt from /var/log/Yast2/y2log: 2013-02-10 22:30:04 <3> linux-suse.site(1639) [Interpreter] users/complex.ycp:40 Loading module 'PamSettings' failed 2013-02-10 22:30:04 <3> linux-suse.site(1639) [libycp] Import.cc(import):97 No matching component found 2013-02-10 22:30:04 <3> linux-suse.site(1639) [Interpreter] users/complex.ycp:40 Import 'PamSettings' failed... 2013-02-10 22:30:04 <3> linux-suse.site(1639) [Interpreter] users/complex.ycp:40 Could not create its namespace 2013-02-10 22:30:04 <3> linux-suse.site(1639) [libycp] Bytecode.cc(readFile):1161 Caught invalid bytecode in '/usr/share/YaST2/modules/Security.ybc' 2013-02-10 22:30:04 <3> linux-suse.site(1639) [Interpreter] users/complex.ycp:40 Loading module 'Security' failed 2013-02-10 22:30:04 <3> linux-suse.site(1639) [Parser] users/complex.ycp:40 Can't load module 'Security'. 2013-02-10 22:30:04 <1> linux-suse.site(1639) [wfm] Y2WFMComponent.cc(import):771 Y2WFMComponent::import (GetInstArgs) 2013-02-10 22:30:04 <1> linux-suse.site(1639) [wfm] Y2WFMComponent.cc(import):771 Y2WFMComponent::import (LdapPopup) 2013-02-10 22:30:04 <1> linux-suse.site(1639) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2013-02-10 22:30:04 <3> linux-suse.site(1639) [liby2] genericfrontend.cc(print_error):869 Error while creating client module users 2013-02-10 22:30:04 <1> linux-suse.site(1639) [Y2Perl] YPerl.cc(destroy):164 Shutting down embedded Perl interpreter. Reproducible: Always Steps to Reproduce: 1.just open user management, also happens when I try to open securrity 2. 3. -- 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 808877] New: Plasma Desktop folder widget/plasmoid passes wrong address to dolphin.
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808877 https://bugzilla.novell.com/show_bug.cgi?id=808877#c0 Summary: Plasma Desktop folder widget/plasmoid passes wrong address to dolphin. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: david.casson(a)ntlworld.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 A link to a folder in the "Plasma Desktop folder" widget seems to point to the wrong address when calling Dolphin if using right click -> "View Original Folder". However it still finds it correctly when its icon is left clicked or the "open" command is used from the right click menu. The problem only seems to occur with symbolic links to folders elsewhere in the filesystem which have been placed onto the desktop. Actual folders don't need the "View Original Folder" option of course so never show the problem. Reproducible: Always Steps to Reproduce: 1. Place a symbolic link to an already existing folder onto the users desktop. (It should have the Icon text shown in italic style). 2. Right click that link in the Desktop Folder plasmoid (not a dolphin window). 3. Select the top option "View Original Folder" Actual Results: 1. Dolphin opens in a window with a red error bar at the top - "The file or folder /../.... does not exist" 2. In the error message, the directory given in the path appears to have been partially recursed wrongly. Expected Results: The original directory contents should be displayed with its correct path shown on the dolphin window. On this system the effect is reproducible every time and with various different directories whether from the users home directory or the general file system. Perhaps it could be worked around by removing the top option in the right click menu? -- 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 0

[Bug 752291] New: systemd boot fails and drops to rescue mode when mounts fail
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=752291 https://bugzilla.novell.com/show_bug.cgi?id=752291#c0 Summary: systemd boot fails and drops to rescue mode when mounts fail Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: 64bit OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: danielm(a)ecoscentric.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.7.2 Safari/534.34 Similar to https://bugzilla.novell.com/show_bug.cgi?id=731480, I have an issue with my desktop system. I've always mounted the opensuse iso images through /etc/fstab (locally networked machines then use these via vsftpd too) like:- /mirrors/torrentable/openSUSE-12.1-DVD-x86_64.iso /mirrors/opensuse-121 iso9660 loop,uid=danielm,gid=users,ro 0 2 This however stops the system booting, reporting Dependency failed. Aborted start of File System Check on /mirrors/tor... Dependency failed. Aborted start of /mirrors/opensuse-121 Welcome to emergency mode. use "systemctl default" or ^D to activate default mode. I guess that there is a race condition with the underlying mount point still being checked as systemd tries to do things in parallel. It works well post boot, but I have to comment the lines out in /etc/fstab to avoid needing console input. It seems (for the other bug too) that rather than "grumble and carry on" the system bails for operator input if a mount fails, which is not helpful if the machine's power is interrupted (this used to happen a lot, due to a flaky photostat machine from the 80's in another office tripping the circuit breakers!). Reproducible: Always Steps to Reproduce: 1. add a loopback mount to /etc/fstab using / as the mountpoint 2. reboot 3. Actual Results: I'm "Welcomed" to emergency mode Expected Results: mount deferred for a few seconds and retried, or a big moan dropped into the boot log and the file system left unmounted. This used to work from SuSE Linux 8.something through to 11.3. Also happens with 32 bit install on the laptop, and for a hibernated M$ partition. -- 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 11

[Bug 788282] New: systemd problems on live cd
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=788282 https://bugzilla.novell.com/show_bug.cgi?id=788282#c0 Summary: systemd problems on live cd Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: coolo(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- No idea what it means, but I better track it - this happens when starting the live cd (build157) ===> Calling pre-init stage in system image [ 6.859440] systemd[1]: Failed to open configuration file '/run/systemd/syslog.core': No such file or directory [ 6.890380] systemd[1]: Cannot add dependency job for unit syslog.service, ignoring: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. [ 6.912633] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details. [ 6.925761] systemd[1]: Cannot add dependency job for unit syslog.service, ignoring: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. [ 7.373688] systemd-journald[517]: Failed to resolve 'adm' group: No such process [ 7.387032] systemd-udevd[516]: specified group 'tape' unknown -- 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 2

[Bug 792182] New: systemd uses wrong locale
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=792182 https://bugzilla.novell.com/show_bug.cgi?id=792182#c0 Summary: systemd uses wrong locale Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com Found By: Third Party Developer/Partner Blocker: --- I have set my locale to german, but root should only use LC_CTYPE: susi:~ # grep -v ^# /etc/sysconfig/language|grep -v '""'|grep -v ^$ RC_LANG="de_DE.UTF-8" ROOT_USES_LANG="ctype" AUTO_DETECT_UTF8="no" However, systemd-started services use LANG=de_DE.UTF-8: susi:~ # pidof libvirtd 1216 susi:~ # cat /proc/1216/environ|xargs -0 -n1 echo ROOTFS_FSTYPE=ext4 ROOTFS_FSCK=0 OLDPWD=/ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin vga=0x367 splash=silent ROOTFS_BLKDEV=/dev/disk/by-label/root-FACTORY LANG=de_DE.UTF-8 LIBVIRTD_CONFIG=/etc/libvirt/libvirtd.conf LIBVIRTD_ARGS=--listen And thus pollute syslog etc. with german messages. IMVHO, systemd should respect teh ROOT_USES_LANG setting. -- 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 10

[Bug 707836] New: YaST2 HTTP server configuration tool does not support "Options"
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=707836 https://bugzilla.novell.com/show_bug.cgi?id=707836#c0 Summary: YaST2 HTTP server configuration tool does not support "Options" Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 The HTTPd option named "Options" is essential for configuring CGI access; it is one of the basic options. YaST2 fails to support it. Reproducible: Always Steps to Reproduce: 1. Tell YaST2 to show the HTTP server configuration tool. 2. Tell the HTTP server configuration tool to add a new Web directory. 3. Tell the current directory view to add an option. 4. Review the available option. Replace the text "Action" with "O". Actual Results: 3. An option dialog box offers you to add an option named "Action", with a drop-down box. 4. MultiviewsMatch Order "O" matches option "Order". Expected Results: 4. MultiviewsMatch Options Order Workaround: You can type "Options" by hand and YaST2 will treat it as a custom option with text value. This is clearly suboptimal as the content model for the option "Options" is not text, it is a table of option names that can be either on, off or undefined. -- 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