August 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 770856] New: lensfun from multimedia:photo lacks pkgconfig info
by bugzilla_noreply＠novell.com 19 Aug '13

19 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=770856 https://bugzilla.novell.com/show_bug.cgi?id=770856#c0 Summary: lensfun from multimedia:photo lacks pkgconfig info Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: P.Suetterlin(a)royac.iac.es QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.10.229 Version/11.64 The lensfun packages from the multimedia:photo repository do not install the lensfun.pc file for compile info. Therefore packages in this repository like ufraw are built without lensfun support. Reproducible: Always Steps to Reproduce: 1. install ufraw and/or lensfun withe multimedia:photo active 2. use ufraw or try to comile something that uses pkgconfig to detect lensfun 3. ....no lensfun support Actual Results: compiling: configure:6480: checking for LENSFUN configure:6487: $PKG_CONFIG --exists --print-errors "lensfun >= 0.2.5" Package lensfun was not found in the pkg-config search path. Perhaps you should add the directory containing `lensfun.pc' to the PKG_CONFIG_PATH environment variable No package 'lensfun' found using official package (e.g., ufraw) ldd /usr/bin/ufraw shows it is not linked against lensfun -- 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 267903] KDM kcm module conflicts with /etc/sysconfig/displaymanager settings
by bugzilla_noreply＠novell.com 19 Aug '13

19 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=267903 https://bugzilla.novell.com/show_bug.cgi?id=267903#c59 Christian Trippe <ctrippe(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nc.carneiro(a)yahoo.com --- Comment #59 from Christian Trippe <ctrippe(a)opensuse.org> 2013-08-19 06:24:11 UTC --- *** Bug 831803 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=831803 -- 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 826727] New: mkinitrd selects wrong md device from where to mount root file system
by bugzilla_noreply＠novell.com 18 Aug '13

18 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=826727 https://bugzilla.novell.com/show_bug.cgi?id=826727#c0 Summary: mkinitrd selects wrong md device from where to mount root file system Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martti.laaksonen(a)tecnotree.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 In a LVM root system, where there are several (>10) LVM logical volumes created on top different MD devices, mkinitrd creates an invalid mdadm.conf which activates wrong MD device during boot so the kernel is not able mount its root file system. In my system I have the following LVM and MD setup: darkside:~ # pvs PV VG Fmt Attr PSize PFree /dev/md2 sys lvm2 a-- 80.00g 0 /dev/md3 virtual lvm2 a-- 93.07g 18.07g darkside:~ # vgs VG #PV #LV #SN Attr VSize VFree sys 1 4 0 wz--n- 80.00g 0 virtual 1 9 1 wz--n- 93.07g 18.07g darkside:~ # lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert home sys -wi-ao--- 40.00g root sys -wi-ao--- 20.00g tmp sys -wi-ao--- 10.00g var sys -wi-ao--- 10.00g centos5 virtual -wi-a---- 10.00g centos6 virtual owi-a-s-- 10.00g centos6-snap virtual swi-a-s-- 10.00g centos6 11.30 debian-6 virtual -wi-a---- 10.00g freebsd9 virtual -wi-a---- 10.00g scientific6 virtual -wi-a---- 10.00g zfs1 virtual -wi-a---- 5.00g zfs2 virtual -wi-a---- 5.00g zfs3 virtual -wi-a---- 5.00g darkside:~ # lvdisplay -c /dev/virtual/centos6:virtual:3:1:-1:0:20971520:2560:-1:0:-1:253:5 /dev/virtual/centos6-snap:virtual:3:1:-1:0:20971520:2560:-1:0:-1:253:7 /dev/virtual/debian-6:virtual:3:1:-1:0:20971520:2560:-1:0:-1:253:8 /dev/virtual/scientific6:virtual:3:1:-1:0:20971520:2560:-1:0:-1:253:9 /dev/virtual/zfs1:virtual:3:1:-1:0:10485760:1280:-1:0:-1:253:10 /dev/virtual/zfs2:virtual:3:1:-1:0:10485760:1280:-1:0:-1:253:11 /dev/virtual/zfs3:virtual:3:1:-1:0:10485760:1280:-1:0:-1:253:12 /dev/virtual/freebsd9:virtual:3:1:-1:0:20971520:2560:-1:0:-1:253:13 /dev/virtual/centos5:virtual:3:1:-1:0:20971520:2560:-1:0:-1:253:14 /dev/sys/home:sys:3:1:-1:1:83877888:10239:-1:0:-1:253:0 /dev/sys/root:sys:3:1:-1:1:41943040:5120:-1:0:-1:253:1 /dev/sys/tmp:sys:3:1:-1:1:20971520:2560:-1:0:-1:253:2 /dev/sys/var:sys:3:1:-1:1:20971520:2560:-1:0:-1:253:3 darkside:~ # darkside:~ # cat /etc/mdadm.conf DEVICE containers partitions ARRAY /dev/md/0 UUID=b7155105:16de1826:2f21e0a9:e303082c ARRAY /dev/md/1 UUID=fee74ee8:6d2c68d9:8cbaec5a:01978ab6 ARRAY /dev/md/2 UUID=d309bc4b:e43890f1:b60bc8d9:d4c76f77 ARRAY /dev/md/3 UUID=8d2857fb:7c3ead15:caa04a0d:1e290036 darkside:~ # ll /dev/md* brw-rw---- 1 root disk 9, 0 Jun 25 17:35 /dev/md0 brw-rw---- 1 root disk 9, 1 Jun 25 17:35 /dev/md1 brw-rw---- 1 root disk 9, 2 Jun 25 17:35 /dev/md2 brw-rw---- 1 root disk 9, 3 Jun 25 17:35 /dev/md3 /dev/md: total 0 lrwxrwxrwx 1 root root 6 Jun 25 17:35 0 -> ../md0 lrwxrwxrwx 1 root root 6 Jun 25 17:35 1 -> ../md1 lrwxrwxrwx 1 root root 6 Jun 25 17:35 2 -> ../md2 lrwxrwxrwx 1 root root 6 Jun 25 17:35 3 -> ../md3 darkside:~ # But the mdadm.conf generated for the initrd looks like shown below: AUTO -all ARRAY /dev/md/3 metadata=1.2 name=darkside.localnet:3 UUID=8d2857fb:7c3ead15:caa04a0d:1e290036 ARRAY /dev/md/1 metadata=1.0 name=linux:1 UUID=fee74ee8:6d2c68d9:8cbaec5a:01978ab6 Reproducible: Always Steps to Reproduce: 1. Create several MD devices (RAID configuration shouldn't matter in this case) during initial installation, e.g. md0 - /boot md1 - swap md2 - LVM2 2. Create a LVM volume group and several logical volumes on top of the md2 devices (root file system is on one of the LVs), e.g. /dev/sys/home /dev/sys/root /dev/sys/tmp /dev/sys/var 3. Create another MD device (md3) after installation, add it to another LVM volume group, and create several logical volumes on it so that there will be more than 10 logical volumes in total (both volume groups combined). 4. Run mkinitrd 5. Boot the system using the generated initrd image. Actual Results: The system boot fails when the kernel tries mount root file system, because the MD device containing the root file system hasn't been activated. Expected Results: The correct MD device containing root file system is activated during boot. Modifying the /usr/lib/mkinitrd/scripts/setup-lvm2.sh where volume group name is resolved by making sed match from the end of the line, like shown below vg_name=$(lvdisplay -c 2> /dev/null | sed -n "/.*:$blockmajor:$blockminor$/p") seems to fix the problem. Actually, the match anything part at the beginning then becomes redundant and could be removed altogether. -- 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

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 18 Aug '13

18 Aug '13

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.com/) that require attention. All of these bugs are in the NEW orREOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reassign bug to default assignee of selected component" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Just use the "Accept bug" command. To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark it if you like!): http://bugzilla.novell.com/buglist.cgi?bug_status=NEW&bug_status=REOPENED&a… Or, you can use the general query page, at http://bugzilla.novell.com/query.cgi Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! wiki.opensuse.org redirects to wiki.opensuse.org// -> http://bugzilla.novell.com/show_bug.cgi?id=761235 Accepting change in my Application wiki not possible -> http://bugzilla.novell.com/show_bug.cgi?id=814036 help.opensuse.org still uses the old 'openSUSE' theme instead of 'bento' -> http://bugzilla.novell.com/show_bug.cgi?id=821405

1 0

[Bug 779240] New: Backlight not restored after switching user session in graphic mode
by bugzilla_noreply＠novell.com 18 Aug '13

18 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=779240 https://bugzilla.novell.com/show_bug.cgi?id=779240#c0 Summary: Backlight not restored after switching user session in graphic mode Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: PC OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fbourdonnec(a)chez.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 Hello, Create another user on your openSUSE, switch to it (do not disconnect running session). Desktop starts as usual. Do some work (need some time to appear). Switch back to initial user (CTRL-ALT-F7) LCD backlight is set to minimal. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: backligth set to minimal Expected Results: backligth restored correctly Log from message at the switch moment : Sep 7 13:34:43 ntkiller2 acpid: 1 client rule loaded Sep 7 13:34:44 ntkiller2 pulseaudio[3778]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 7 13:34:44 ntkiller2 pulseaudio[3778]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" namereg_fail=false tsched=yes ignore_dB=no deferred_volume=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 7 13:34:45 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Sep 7 13:34:45 ntkiller2 dbus[604]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Sep 7 13:34:45 ntkiller2 org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave. Sep 7 13:34:46 ntkiller2 dbus[604]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Sep 7 13:34:46 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Sep 7 13:34:55 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Sep 7 13:34:55 ntkiller2 dbus[604]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Sep 7 13:34:55 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' Sep 7 13:34:55 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. Sep 7 13:34:55 ntkiller2 dbus[604]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' Sep 7 13:34:55 ntkiller2 dbus[604]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. Sep 7 13:34:55 ntkiller2 dbus-daemon[604]: (packagekitd:6463): GLib-GObject-WARNING **: invalid (NULL) pointer instance Sep 7 13:34:55 ntkiller2 dbus-daemon[604]: (packagekitd:6463): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Sep 7 13:34:55 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Successfully activated service 'org.freedesktop.PackageKit' Sep 7 13:34:55 ntkiller2 dbus[604]: [system] Successfully activated service 'org.freedesktop.PackageKit' Sep 7 13:34:58 ntkiller2 dbus-daemon[604]: (packagekitd:6463): PkPlugin-WARNING **: failed to clear /var/run/PackageKit/udev Sep 7 13:35:05 ntkiller2 dbus-daemon[604]: (packagekitd:6463): PkPlugin-WARNING **: not correct size, 0 Sep 7 13:35:05 ntkiller2 dbus-daemon[604]: (packagekitd:6463): PkPlugin-WARNING **: failed to get list Sep 7 13:35:27 ntkiller2 dbus-daemon[604]: (packagekitd:6463): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Sep 7 13:35:31 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Sep 7 13:35:31 ntkiller2 dbus[604]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Sep 7 13:35:31 ntkiller2 org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave. Sep 7 13:35:31 ntkiller2 dbus[604]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Sep 7 13:35:31 ntkiller2 dbus-daemon[604]: dbus[604]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' -- 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 835306] New: KDE:Frameworks/kf5 needs a %sysconfdir/ld.so.conf.d/kf5.conf
by bugzilla_noreply＠novell.com 17 Aug '13

17 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=835306 https://bugzilla.novell.com/show_bug.cgi?id=835306#c0 Summary: KDE:Frameworks/kf5 needs a %sysconfdir/ld.so.conf.d/kf5.conf Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: hrvoje.senjan(a)gmail.com ReportedBy: johannesobermayr(a)gmx.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- %install mkdir -p %buildroot%sysconfdir/ld.so.conf.d echo "# kdm_greet prefers wrong %_kf5_libdir/libkdeui.so.5 which does not contain _ZN11KPushButton16staticMetaObjectE otherwise %_libdir # kdm_greet does not find so in %_kf5_libdir %_kf5_libdir" > %buildroot%sysconfdir/ld.so.conf.d/kf5.conf %files %sysconfdir/ld.so.conf.d/kf5.conf -- 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 834278] New: Updates om August 9th break texlive
by bugzilla_noreply＠novell.com 17 Aug '13

17 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=834278 https://bugzilla.novell.com/show_bug.cgi?id=834278#c0 Summary: Updates om August 9th break texlive Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chris(a)infosun.fim.uni-passau.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 Updating the system with 'zypper update' updated many tex live rpm packages. Now I have version 2012.20120611-3.6.3 . After that tex is broken on my system. 'latex example.tex' delivers warning: kpathsea: /etc/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/lib/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/cache/texmf/fonts/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/TeX Live for SUSE Linux) restricted \write18 enabled. kpathsea: Running mktexfmt latex.fmt warning: kpathsea: /etc/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/lib/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/cache/texmf/fonts/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found (ls-R missing?). fmtutil: config file `fmtutil.cnf' not found. I can't find the format file `latex.fmt'! instead of a dvi-file. Same with pdflatex. example.tex only contains a minimal document: \documentclasss{article} \begin{document} Hello, World! \end{document} Reproducible: Always Steps to Reproduce: 1. update texlive to the latest version available in final 2. create example.tex 3. latex example.tex Actual Results: warning: kpathsea: /etc/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/lib/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/cache/texmf/fonts/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/TeX Live for SUSE Linux) restricted \write18 enabled. kpathsea: Running mktexfmt latex.fmt warning: kpathsea: /etc/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/lib/texmf/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. warning: kpathsea: /var/cache/texmf/fonts/ls-R: No usable entries in ls-R. warning: kpathsea: See the manual for how to generate ls-R. tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not found (ls-R missing?). fmtutil: config file `fmtutil.cnf' not found. I can't find the format file `latex.fmt'! Expected Results: A dvi file. -- 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 806388] New: warning: %post(plymouth-branding-openSUSE-12.2-11.12.1.noarch) scriptlet failed, exit status 1
by bugzilla_noreply＠novell.com 16 Aug '13

16 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=806388 https://bugzilla.novell.com/show_bug.cgi?id=806388#c0 Summary: warning: %post(plymouth-branding-openSUSE-12.2-11.12.1.noarch) scriptlet failed, exit status 1 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chris.sylvain(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.97 Safari/537.22 while doing zypper dup from 12.1 -> 12.2 :: Installing: plymouth-branding-openSUSE-12.2-11.12.1 [done] Additional rpm output: Kernel image: /boot/vmlinuz-3.4.28-2.20-default Initrd image: /boot/initrd-3.4.28-2.20-default KMS drivers: radeon /lib/mkinitrd/setup/03-plymouth.sh: line 12: plymouth: command not found The default plymouth plugin (script) doesn't exist. There was an error generating the initrd (1) warning: %post(plymouth-branding-openSUSE-12.2-11.12.1.noarch) scriptlet failed, exit status 1 Reproducible: Always Steps to Reproduce: 1. change 12.1 repos to 12.2 repos 2. zypper ref ; zypper dup 3. zypper wp /lib/mkinitrd/setup/03-plymouth.sh # (checking to see where this came from) provides no package owning this file. only package plymouth-scripts puts scripts in /lib/mkinitrd/scripts , therefore where the 03-plymouth.sh comes from is not known to me. -- 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 825170] New: Clicking "enable" or "disable" next to boot options on Installation Settings screen does nothing
by bugzilla_noreply＠novell.com 16 Aug '13

16 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=825170 https://bugzilla.novell.com/show_bug.cgi?id=825170#c0 Summary: Clicking "enable" or "disable" next to boot options on Installation Settings screen does nothing Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: PC OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: malv_star(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:21.0) Gecko/20100101 Firefox/21.0 On the final screen in the openSUSE 13.1 M2 installer, a summary of installation settings is displayed. In the "Booting" section, there will be an option to (for example) click "enable" next to "Boot from MBR". This does nothing. Reproducible: Always Steps to Reproduce: 1. Start installation 2. De-select automatic configuration 3. Reach "Installation Settings" screen 4. Click "Enable" next to "Boot from MBR". Actual Results: The screen flickers briefly but no change is made. Expected Results: The settings should change to boot from MBR, and disable booting from / at the same time. Note that if you manually go in and change the system to boot from MBR, the text shown says "Disable". Clicking the text still does nothing. -- 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 801375] New: Device Notifier Shows Floppy Drive Even When No Disk Inserted
by bugzilla_noreply＠novell.com 16 Aug '13

16 Aug '13

https://bugzilla.novell.com/show_bug.cgi?id=801375 https://bugzilla.novell.com/show_bug.cgi?id=801375#c0 Summary: Device Notifier Shows Floppy Drive Even When No Disk Inserted Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: malv_star(a)hotmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20100101 Firefox/16.0 The device notifier in the system tray shows a "0 B" sized floppy when clicked on, even when no disk is inserted into the drive. To be clear, the system in question DOES have a 3.5" floppy drive attached. Reproducible: Always Steps to Reproduce: 1. Use KDE 2. Click on Device Notifier Actual Results: A floppy disk is shown in Device Notifier at all times. Expected Results: A floppy disk should only be shown in Device Notifier when a disk has been mounted. -- 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