January 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 746156] problems with multiselection table widget in YaST
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=746156 https://bugzilla.novell.com/show_bug.cgi?id=746156#c7 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner(a)suse.com, | |opensuse-bugs(a)opensuse.org --- Comment #7 from Martin Vidner <mvidner(a)suse.com> 2014-01-07 14:15:53 CET --- No sensitive info here. Making the bug public (by CCing opensuse-bugs ML) to reference it from https://github.com/libyui/libyui-qt/pull/21 -- 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 799274] New: OS 12.3 Beta1 Installation faill - dmraid with lvm manual partitioning
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=799274 https://bugzilla.novell.com/show_bug.cgi?id=799274#c0 Summary: OS 12.3 Beta1 Installation faill - dmraid with lvm manual partitioning Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST AssignedTo: fehr(a)suse.com ReportedBy: cattom(a)o2.pl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Using GnomeLive CD during fresh instalation process after manual partitioning, instalator can't initialize lvm groups on dmraid partitions. Looks like device maps wasn't created, didn't exists in /dev/mapper. My quick soulution to push process forward was: execute kpartx -a /dev/mapper/$nvidiadm -p _part and restart/repeat all instalation process on the same partitions. Unfortunatelly after image installation/1st reboot system can't find lvm group during boot process. Im guess now is systemd fail, not sure anyway. Any advice ? Reproducible: Always Steps to Reproduce: 1.Use manual partitioning during installation process 2.Create LVM on dmraid partition 3.Accept partition table and step forward. Actual Results: Message : Can't initialize system logical group on partition /dev/mapper/nvidia.... partition /dev/mapper/nvidia.... doesn't exists Choiced Polish language during instalation 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 11

[Bug 851877] New: Wrong suse_version macro in 13.1
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=851877 https://bugzilla.novell.com/show_bug.cgi?id=851877#c0 Summary: Wrong suse_version macro in 13.1 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: emendonca(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Field Engineer Blocker: --- The macro "suse_version" is defined in /usr/lib/rpm/suse/macros from the package "rpm". It should evaluate to "1310", but is still evaluating to "1230" (from openSUSE 12.3). # rpm --eval '%{suse_version}' 1230 The problem exists in shipping 13.1 distribution. This will cause problems for anyone developing RPM packages. === Name : rpm Version : 4.11.1 Release : 6.2.1 Architecture: x86_64 Install Date: Qua 20 Nov 2013 16:14:08 BRST Group : System/Packages Size : 4663090 License : GPL-2.0+ Signature : RSA/SHA256, Sex 27 Set 2013 15:05:34 BRT, Key ID b88b2fd43dbdc284 Source RPM : rpm-4.11.1-6.2.1.src.rpm Build Date : Sex 27 Set 2013 15:05:04 BRT Build Host : build05 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE Summary : The RPM Package Manager Description : RPM Package Manager is the main tool for managing the software packages of the SuSE Linux distribution. RPM can be used to install and remove software packages. With rpm, it is easy to update packages. RPM keeps track of all these manipulations in a central database. This way it is possible to get an overview of all installed packages. RPM also supports database queries. Distribution: openSUSE 13.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 10

[Bug 768859] New: my nvidia fakeraid array on which I have the root partition is not activated properly by the initrd
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=768859 https://bugzilla.novell.com/show_bug.cgi?id=768859#c0 Summary: my nvidia fakeraid array on which I have the root partition is not activated properly by the initrd Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: josua.m(a)t-online.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1 I have opensuse installed on a nvidia fakeraid raid1 array at /dev/mapper/nvidia_bbbdidfc_part4. After installing opensuse(which in fact doesn't work without manual work), the system will not boot. Reproducible: Always Steps to Reproduce: 1. create a hardware fakeraid raid1 array 2. install opensuse to a partition on that array 3. try to boot the resulting system Actual Results: Console complains /dev/sdb4 beeing in use(where sdb is part of the array) and falls to a shell Expected Results: normal system boot what happened is that "/dev/mapper/nvidia_bbbdidfc" exists, but no partitions. there should also be nvidia_bbbdidfc_part{1..4}. I found a fix for this issue which involves editing /lib/mkinitrd/boot/21-dmraid.sh Inside, there is a line saying "/sbin/dmraid -a y -p" This line, according to man will initialize the raid array but no partitions. so obviously a boot cant work. I changed it to say this: "/sbin/dmraid -a y -P _part" then recreated the initrd by chrooting into the system and from then on I can boot fine. I am adding this _part, because I noticed during the installation that some unknown things expect the dmraid devices to be called like this: nvidia_bbbdidfc,nvidia_bbbdidfc_part1,... By default, dmraid will name the devices liek this: nvidia_bbbdidfc,nvidia_bbbdidfcp1,... -- 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 856648] New: I cannot set Composition type and QT-Graphic system to respectively XRender and Native
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856648 https://bugzilla.novell.com/show_bug.cgi?id=856648#c0 Summary: I cannot set Composition type and QT-Graphic system to respectively XRender and Native Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i686 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: f.leerink(a)xs4all.nl QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 This happened on openSUSE 13.1 final EDU-Live Today I made a new install of openSUSE/EDU-Live 13.1 FINAL, system -Intel Pentium D Dual Core Processor 830-3 GHz with 3 GB memory and connected with 2 1440x900 displays, a vga and a dvi one. I want to configure the position of the vga screen as absolute 0,0 and the position of the dvi screen as left of vga. The system has 2 hard disks. The install as well as the reboot went oke, although detecting linux partitions and installing boot manager last very long respectively 25 and 40 minutes, so finally I could log in as wanted. The configuration of the position of the 2 screens is a problem. Trying it, with the knowledge of my earlier installation of 13.1 RC, configurations, resulted in a garbled,very slow display and garbled default panel. Two shutdown/boot cycles with reconfiguring the position of the 2 screens did not help. I disabled desktop effects and tried to changed Composition-type and QT-Graphic system in desktop effects to respectively XRender and Native. as done during my earlier installation of 13.1 RC's. I could not configure the 2 displays as wanted. So defenitely not oke and a real problem for new openSUSE 13.1 users. What can I do to help solving this problem. Regards, Frans Reproducible: Always Steps to Reproduce: 1.After every reboot the same problem 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 3

[Bug 856998] New: Default location of bootloader should be MBR on old hardware
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856998 https://bugzilla.novell.com/show_bug.cgi?id=856998#c0 Summary: Default location of bootloader should be MBR on old hardware Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: u.michel(a)t-online.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 When installing openSUSE 13.1 on an old hardware with Celeron CPU and Windows XP and with a hard disk with legacy partioning the bootloader is installed in the extended partition that is generated during the install process after the size of the Windows partition had been reduced. However, no operating system is found during the boot process with this location. The boot loader must be installed in the MBR and this should be the default. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: No operating system is found during the first boot after install. Expected Results: The grub menu should appear during the first boot. -- 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 857531] New: KDE login black screen, all of a sudden, yet permanently now
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=857531 https://bugzilla.novell.com/show_bug.cgi?id=857531#c0 Summary: KDE login black screen, all of a sudden, yet permanently now Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: adev(a)leue.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Symptom After booting, before login screen shows up, the screen wents black. The same happens when applying "telinit 5". Login via network is possible. Environment opensuse 13.1, with various updates Dell XPS 15, with nvidia and 3200/1800 display Detailed description opensuse 13.1 was successfully installed without any trouble on the machine and worked for a while, with few minor quirkses (like touch-capability available only after suspend-to-ram once, a known issue). All of a sudden (well, after closing the lid, like many times before), the screen went black, and stayed bllack. Since then, even after rebooting, the screen stayed black, and still is black. More detailed, after reboting: grub2 shows up, the screen shortly wents black, the kde login background image shows up (but not the login box), and then it wents black and stays black. No keys work (like Ctrl-Alt-F1, or Ctrl-Alt-Backspace etc.) Remote login is possible, and after "telinit 3" the text console appears. With root login, issuing startx successfully starts KDE and I can work, as root. "telinit 5" again produces the black screen. This is repeatable. If I log in from the text console with my username, startx does not work, it claims it cannot remove X.org.log.old, due to insufficient permissions. Indeed , the file is owned by root. Fair enough. Now, after *once* unsuccessfully issuing startx from my user account, afterwards from root "telinit 5" does (!) work. Unfortuantely, after rebooting, the black screen is again there. grub2 kernel option "nomodeset" also helps, I can boot, no black screen. But: with nomodeset, in KDE->Configure Desktop->Display and Monitor only one screen resoultion to choose from is presented (the highest one), so it seems with "nomodeset" a different video driver is used? I'm not sure, at least there's a difference. When booting normally (with the telinit/startx trick) a long list of video modes is presented. Unfortunately, adding a grub2 kernel option "3" does *not* work. It seems that the system is indeed only booting into runlevel "3", but nevertheless the black screen appears. This behaviour seems really strange to me. Reproducible: Always Steps to Reproduce: On the affected machine here: just boot. Actual Results: grub2 screen shows, display wents shortly black (as usual), KDE login background shows, screen wents black and stays black Expected Results: Login prompt should show up -- 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 851402] New: Simple 13.1 system built on susestudio has broken networking
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=851402 https://bugzilla.novell.com/show_bug.cgi?id=851402#c0 Summary: Simple 13.1 system built on susestudio has broken networking Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: VMWare OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: archie(a)dellroad.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:25.0) Gecko/20100101 Firefox/25.0 (First, a meta-problem: it's not clear how to categorize susestudio bugs. There is no classification, product, or category called "susestudio"). I just tried a plain "server" build of openSUSE 13.1 on susestudio, installed on VMWare, and it failed to configure the network interface for DHCP. The problem is the rename of eth0 -> ens33 in 13.1: Nov 20 14:59:14 linux-t5oa systemd[1]: Starting LSB: Configure network interfaces and set up routing... Nov 20 14:59:14 linux-t5oa network[5420]: Setting up network interfaces: Nov 20 14:59:15 linux-t5oa network[5420]: lo Nov 20 14:59:15 linux-t5oa ifup[5709]: lo Nov 20 14:59:15 linux-t5oa ifup[5753]: lo Nov 20 14:59:15 linux-t5oa ifup[5756]: IP address: 127.0.0.1/8 Nov 20 14:59:15 linux-t5oa network[5420]: lo IP address: 127.0.0.1/8 Nov 20 14:59:15 linux-t5oa ifup[5758]: Nov 20 14:59:15 linux-t5oa network[5420]: ..done ens33 Startmode is 'manual' -> skipping Nov 20 14:59:15 linux-t5oa ifup[5815]: ens33 Startmode is 'manual' -> skipping Nov 20 14:59:15 linux-t5oa network[5420]: ..skippedWaiting for mandatory devices: eth0 Nov 20 14:59:45 linux-t5oa network[5420]: 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Nov 20 14:59:45 linux-t5oa network[5420]: eth0 No interface found Nov 20 14:59:45 linux-t5oa network[5420]: ..failedSetting up service network . . . . . . . . . . . . ...failed Nov 20 14:59:45 linux-t5oa systemd[1]: network.service: control process exited, code=exited status=7 Nov 20 14:59:45 linux-t5oa systemd[1]: Failed to start LSB: Configure network interfaces and set up routing. Nov 20 14:59:45 linux-t5oa systemd[1]: Unit network.service entered failed state. The result is a system that can't be reached from the network. Reproducible: Always Steps to Reproduce: 1. Build 13.1 "server" system on susestudio as VMWare instance and DHCP client 2. Boot system 3. Notice it has no IP address Actual Results: No IP assignment via DHCP. Expected Results: IP assignment via DHCP. -- 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 855514] New: Dosbox in oss repo doesn't support timidity
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=855514 https://bugzilla.novell.com/show_bug.cgi?id=855514#c0 Summary: Dosbox in oss repo doesn't support timidity Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin.jakl(a)qbicon.cz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 I have dosbox configured to use midi via timidity (mididevice=alsa, midiconfig=128:0). After upgrade to 13.1 this stopped working. But when I get the sources and compile dosbox myself, it works. So it looks like that dosbox in oss repo is compiled without alsa midi support. Reproducible: Always Steps to Reproduce: 1. run timidity -iA 2. configure dosbox to use timidity 3. start dosbox -- 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 8

[Bug 853167] New: zypper crash with SIGSEGV signal on search action
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=853167 https://bugzilla.novell.com/show_bug.cgi?id=853167#c0 Summary: zypper crash with SIGSEGV signal on search action Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: egdfree(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=569843) --> (http://bugzilla.novell.com/attachment.cgi?id=569843) back trace User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 If i use search action with flags -iv zypper crash with SIGSEGV signal. Reproducible: Always Steps to Reproduce: 1. zypper se -iv flash 2. wait... 3. sigsegv -- 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