March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 807230] New: 12.3RC2: Fails to detect network and printer during installation (works afterwords)
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=807230 https://bugzilla.novell.com/show_bug.cgi?id=807230#c0 Summary: 12.3RC2: Fails to detect network and printer during installation (works afterwords) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: johanp(a)aditus.nu QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.26 (KHTML, like Gecko) Chrome/26.0.1383.0 Safari/537.26 SUSE/26.0.1383.0 12.3RC2, X86_64, Network installation When doing a network installation all packages are installed and network card is obviously working. However at the end of the installation two steps fails which may give a bad user experience for newcomers to OpenSuSE since they are given the impression that two critical functions are not working. PROBLEM 1: The "Checking Internet Connection" fails, which is funny since the installation just spent a long time downloading and installing components from the network so it obviously does work. PROBLEM 2: Running the printer detection during installation fails. However re-running the printer installation from Yast2 after the installation is done works just fine. Reproducible: Always Steps to Reproduce: 1. Try to install the network 12.3RC2 version 2. 3. Actual Results: Fails to detect network Fails to detect printers Expected Results: Network detection succeeds Printers are detect also during installation If this can't be fixed for gold then some kind of information text should be added so that newcomers can re-run the setup after the installation is completed. -- 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 803008] New: YaST2 reports Traditional method with ifup, however ifdown reports Network is managed by 'NetworkManager.service' -> skipping
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=803008 https://bugzilla.novell.com/show_bug.cgi?id=803008#c0 Summary: YaST2 reports Traditional method with ifup, however ifdown reports Network is managed by 'NetworkManager.service' -> skipping Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 After generating a new 12.3 RC1 system in a VM with a virtual ethernet interface Yast chooses a configuration with the Traditional Method with ifup. I was trying to change the default for IPv6 using ifsysctl, but the reported test using /etc/sysconfig/network/scripts/ifup-sysctl eth0 -o debug did not show any result. Closer inspection revealed that a test in that script prevented any setting. This test was about using Networkmanager or not. Finally I tried the ifdown eth0 command, which reported that the NetworkManager service was used. However YaST2 still reports the traditional setup with ifup. Also the file /etc/sysconfig/network/config shows NETWORKMANAGER="no" Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Consistency in what YaST2 reports and what the system does. -- 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 807179] New: yast-Statically Assigned IP Address is ignored
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=807179 https://bugzilla.novell.com/show_bug.cgi?id=807179#c0 Summary: yast-Statically Assigned IP Address is ignored Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: i586 OS/Version: Windows XP Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mircea.mucha(a)siemens.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E; MS-RTC LM 8; InfoPath.2) Environment: Oracle Virtual Box 4.2.6.r82870 running under a Windows XP OS. There are 2 OpenSuse virtual machines installed from scratch: OpenSuse 12.2 and OpenSuse 12.3. Same route (ADSL) Huawei is DHCP server for the private network: 192.168.1.0/24. In both cases using yast – Network Devices – Network Settings there are the same settings: Network Settings: Network Setup Method=Traditional Method with ifup, IPV6=disabled, DHCP Client Options=empty, Hostname to Send=Empty, Change Default Route via DHCP=empty. Network Card Setup=eth0, Statically Assigned IP Address=192.168.1.53/24 (OpenSuse12.2), 192.168.1.54/24 (OpenSuse 12.3), in both cases: in Routing, Default IPv4 Gateway= 192.168.1.1, Device: eth0. In case of OpenSuse 12.2 changing in the menu Network Card Setup from Statically Assigned IP Address to Dynamic Address, changes are immediately done, while in case of OpenSuse 12.3 the same IP address initial allocated by DHCP can be seen after changes in yast are done, even after a reboot of the OpenSuse 12.3 and reboot of DHCP router, the statically allocated IP is ignored. Is it a bug of the OpenSuse 12.3 itself or this problem is related with BUG-806416 (virtualbox-guest-tools-4.2.6-3.1.7.i586.rpm is not installed)? Reproducible: Always Steps to Reproduce: 1.Described in Details 2. 3. Actual Results: Cannot change to a statically allocated IP address -- 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 806576] New: games/steam: Bug
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=806576 https://bugzilla.novell.com/show_bug.cgi?id=806576#c0 Summary: games/steam: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: christian.morales.vega(a)gmail.com ReportedBy: nlminhtl(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: prusnak(a)opensuse.org Found By: --- Blocker: --- It seems needs libGL as a requirement package. I have received an error message after starting: >You are missing the following 32-bit libraries, and Steam may not run: >libGL.so.1 -- 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 725006] New: Tracker enabled when running on battery
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=725006 https://bugzilla.novell.com/show_bug.cgi?id=725006#c0 Summary: Tracker enabled when running on battery Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: rdb(a)ccb.ac.uk QAContact: qa(a)suse.de Found By: --- Blocker: --- Installed system is openSUSE Factory + GNOME Factory + GNOME apps for Factory with last zypper dupped at 18oct 20:57 UTC tracker 0.12.5-90.5 from G:A:F is installed Observed behaviour: Indexing is enabled by default to run when on battery Expected behaviour: I would expect Tracker to have indexing disabled when operating on battery to dramatically improve battery life. This is a particular concern on laptops equipped with SSDs, where Indexing can occur much quicker than on HDDs, which produces both high CPU and SSD load while the indexing is carried out. IIRC our previous behaviour was to have Indexing only enabled on battery for initial data population, which I believe would be a much more sensible default. -- 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 807156] New: 12.3 RC2: tracker mining is enabled on battery by default.
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=807156 https://bugzilla.novell.com/show_bug.cgi?id=807156#c0 Summary: 12.3 RC2: tracker mining is enabled on battery by default. Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- 12.3 RC2: tracker mining is enabled on battery by default. I'm using XFCE. I just started "tracker-preferences" and to my surprise it is enabled when running on battery. If people are already mad at the reource hog indexing is, think how they will get if their laptop batteries get drained. -- 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 808132] New: multipathd does not add active/good/ok paths back to dm-multipath devices during failback
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808132 https://bugzilla.novell.com/show_bug.cgi?id=808132#c0 Summary: multipathd does not add active/good/ok paths back to dm-multipath devices during failback Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: michaelc(a)cs.wisc.edu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=528752) --> (http://bugzilla.novell.com/attachment.cgi?id=528752) Full /var/log/messages and multipath -ll output. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130220 Firefox/17.0 With sles11 sp2 and multipath-tools-0.4.9-0.68.1, we hit a bug where we do a port down on some ports, and that goes ok. But when we bring the ports back, the paths are a little unstable at first so the paths might be returning errors. But eventually everything is ok. However, multipath is stuck in a state where it does not seem to be sending path testing IO. At this time, READ/WRITE block/fs IO to the dm devices hang, and also SG IO to the dm devices hang. Here is multipath -ll for one of the dm devices: mpathc (23761343133383032) dm-2 FUSIONIO,ION LUN size=56G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='queue-length 0' prio=80 status=enabled | |- 3:0:1:2 sdl 8:176 failed ready running | `- 3:0:0:2 sdd 8:48 failed ready running `-+- policy='queue-length 0' prio=50 status=enabled |- 4:0:1:2 sdab 65:176 failed ready running `- 4:0:0:2 sdt 65:48 failed ready running sdl and sdd are in the alua unavailable path state, but sdab and sdt are ok to use. If I manually send IO it works ok. ionr1c126:~ # sg_dd if=/dev/sdab of=/dev/null blk_sgio=1 bs=4096 count=1 1+0 records in 1+0 records out ionr1c126:~ # sg_dd if=/dev/sdt of=/dev/null blk_sgio=1 bs=4096 count=1 1+0 records in 1+0 records out ionr1c126:~ # sg_turs /dev/sdab ionr1c126:~ # sg_turs /dev/sdt multipath.conf: devices { device { vendor "FUSIONIO" features "3 queue_if_no_path pg_init_retries 50" hardware_handler "1 alua" path_grouping_policy group_by_prio path_selector "queue-length 0" failback immediate path_checker tur prio alua fast_io_fail_tmo 15 dev_loss_tmo 60 # we are using the version of multipathd that overrides this and sets this to the max when using queue_if_no_path } } We have a bunch of stuck blkids 26933 ? 00:00:00 blkid 26990 ? 00:00:00 blkid 27006 ? 00:00:00 blkid 27015 ? 00:00:00 blkid 27016 ? 00:00:00 blkid 27047 ? 00:00:13 blkid 27414 ? 00:00:13 blkid 27431 ? 00:00:13 blkid 27452 ? 00:00:13 blkid 27454 ? 00:00:13 blkid 27463 ? 00:00:13 blkid 27590 ? 00:00:13 blkid 27598 ? 00:00:13 blkid 27619 ? 00:00:13 blkid 27620 ? 00:00:13 blkid 27627 ? 00:00:13 blkid 27722 ? 00:00:13 blkid 27736 ? 00:00:13 blkid 27740 ? 00:00:13 blkid Also, I am not sure if it is related, but we also see a lit of udev errors around this time: Mar 4 12:26:10 ionr1c126 udevd[438]: worker [27641] unexpectedly returned with status 0x0100 Mar 4 12:26:10 ionr1c126 udevd[438]: worker [27641] failed while handling '/devices/virtual/block/dm-2' Reproducible: Always Steps to Reproduce: 1. 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 0

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c124 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #124 from Felix Miata <mrmazda(a)earthlink.net> 2013-03-07 16:35:07 UTC --- Just happened again in 12.2 2.0GHz 32 bit AMD family 6 model 8 stepping 1: host m7ncd old kernel 3.4.11-2.16.1-desktop new kernel 3.4.28-2.20.1-desktop -- 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 807797] New: KDE screensaver vanish without password
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=807797 https://bugzilla.novell.com/show_bug.cgi?id=807797#c0 Summary: KDE screensaver vanish without password Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: kukuk(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: Yes Installed openSUSE 11.3 RC2 from DVD, created user during installation. After installation, logged in as user, wait some time until KDE locks automatically the screen. If you move the mouse, screen is unlocked without entering the password. -- 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 803179] New: Kickoff: Wrong entry sort order if "Show applications by name" is switched off
by bugzilla_noreply＠novell.com 07 Mar '13

07 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=803179 https://bugzilla.novell.com/show_bug.cgi?id=803179#c0 Summary: Kickoff: Wrong entry sort order if "Show applications by name" is switched off Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: All Status: ASSIGNED Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: wbauer(a)tmo.at ReportedBy: wbauer(a)tmo.at QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- If "Show applications by name" is switched off in KDE's Kickoff menu (which is the default), the entries are still sorted by application name although the generic name is shown. In unpatched KDE the entries are sorted by generic name in that case, as one would expect. This is a bug in plasma-kickoff-newly-collapsing.diff and exists since at least 11.4. I already have a fix ready, so I'm assigning this to myself... -- 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