January 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 797439] New: digikam and gwenview segfault at startup because of broken libGL link
by bugzilla_noreply＠novell.com 09 Jan '13

09 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=797439 https://bugzilla.novell.com/show_bug.cgi?id=797439#c0 Summary: digikam and gwenview segfault at startup because of broken libGL link Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: stephan.barth(a)suse.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Both digikam and gwenview almost immediately exit with a segmentation fault. When inspecting the core libGL seems to be the culprit: Reading symbols from /usr/bin/digikam...Reading symbols from /usr/lib/debug/usr/bin/digikam.debug...done. done. [New LWP 23011] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `digikam'. Program terminated with signal 11, Segmentation fault. #0 0xb2a58069 in ?? () from /usr/lib/libGL.so.1 /usr/lib/libGL.so.1 points to a left over from an old package it seems: lrwxrwxrwx 1 root root 15 Jan 2 20:20 /usr/lib/libGL.so.1 -> libGL.so.280.13 -rwxr-xr-x 1 root root 370620 Aug 28 17:52 /usr/lib/libGL.so.1.2 -rwxr-xr-x 1 root root 794628 Aug 6 2011 /usr/lib/libGL.so.280.13 # rpm -qf /usr/lib/libGL.so.280.13 file /usr/lib/libGL.so.280.13 is not owned by any package # rpm -qf /usr/lib/libGL.so.1.2 Mesa-libGL1-8.0.4-20.7.1.i586 This command fixes the issue: ln -sf /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1 I already had to fix this a second time since the upgrade to 12.2. -- 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 796907] New: "Create Virtual Machines" in YAST produces error "libvirtmod.so: wrong ELF class"
by bugzilla_noreply＠novell.com 09 Jan '13

09 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=796907 https://bugzilla.novell.com/show_bug.cgi?id=796907#c0 Summary: "Create Virtual Machines" in YAST produces error "libvirtmod.so: wrong ELF class" Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: KVM AssignedTo: kvm-bugs(a)forge.provo.novell.com ReportedBy: lbickley(a)bickleywest.com QAContact: jdouglas(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4 After installing KVM and rebooting, attempting to "Create Virtual Machines" in YAST yields the following error: "libvirtmod.so: wrong ELF class" Reproducible: Always Steps to Reproduce: 1. Start YAST 2. Go to Virtualization 3. Select Create Virtual Machines Actual Results: Traceback (most recent call last): File "/usr/bin/vm-install", line 24, in <module> import vmdisks.disks File "/usr/lib/python2.7/site-packages/vmdisks/__init__.py", line 2, in <module> from diskmap import * File "/usr/lib/python2.7/site-packages/vmdisks/diskmap.py", line 1, in <module> import libvirt File "/usr/lib/python2.7/site-packages/libvirt.py", line 25, in <module> raise lib_e ImportError: /usr/lib/python2.7/site-packages/libvirtmod.so: wrong ELF class: ELFCLASS32 Expected Results: Began creation of VM Re-installed "libvert-python" which provides libvirtmod.so, and the same error occurred. Reinstalled all KVM and KVM supporting libraries and same error occurred. -- 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 777387] New: virsh / virt-manager: lacking qcow2 image preallocation options
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=777387 https://bugzilla.novell.com/show_bug.cgi?id=777387#c0 Summary: virsh / virt-manager: lacking qcow2 image preallocation options Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: graham(a)andtech.eu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1226.0 Safari/537.4 SUSE/22.0.1226.0 It is not currently possible to create a KVM volume in the qcow2 image format with full metadata preallocation via virt-manager GUI app or the virsh shell/command line. If I choose to manually create a qcow2 image, the option I would always pass (in combination with others) to qemu-image to avoid performance issues would be "preallocation=metadata". The option to create a qcow2 image with virsh or virt-manager with this option is simple not available. In practical terms, if you wish not to have very poorly performing disk IO in any KVM guest domain, you must choose a raw image format and something like an LVM storage pool. A directory based pool is not an option if you wish to also snapshot your guests. I believe this is an upstream limitation rather than one specifically in the openSUSE virsh/libvirtd packages. I have no upstream issue # at the moment as I'm still wading through libvirt ML backlog. 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 4

[Bug 797264] New: virt-manager does not allow to configure CDROM devices as virtio but accepts them if configured by hand
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=797264 https://bugzilla.novell.com/show_bug.cgi?id=797264#c0 Summary: virt-manager does not allow to configure CDROM devices as virtio but accepts them if configured by hand Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: KVM AssignedTo: kvm-bugs(a)forge.provo.novell.com ReportedBy: lang(a)b1-systems.de QAContact: jdouglas(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 In virt-manager, in the dropdown for adding drives, only qemu IDE is offered for CDROM drives. In advanced settings, this can later be changed to SCSI but not to virtio. Manually adding a section <disk type='file' device='cdrom'> <driver name='qemu' type='raw' cache='unsafe'/> <source file='/home/rlang/Downloads/virtio-win-0.1-49.iso'/> <target dev='vdd' bus='virtio'/> <readonly/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </disk> will yield a working virtio-based CDROM drive which is detected by both windows 7 and linux guests. It even displays it correctly as virtIO CDROM and the line "Disk bus" prints "virtio", but not in a dropdown box. It does not offer to change back to IDE/SCSI CDROMs. This is inconsistent with Hard Disks. Reproducible: Always Steps to Reproduce: See above Actual Results: See above Expected Results: Have a third option to change a CDROM's bus to virtio. Have an option for virtio CDROM's to change them to IDE or SCSI. Have SCSI and virtio CDROMs show up along with IDE CDROMs, IDE HDD, SCSI HDD and Virtio HDD in the initial new storage dialog. -- 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 794084] New: usage of absolute paths / get_kernel_version
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=794084 https://bugzilla.novell.com/show_bug.cgi?id=794084#c0 Summary: usage of absolute paths / get_kernel_version Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: ohering(a)suse.com QAContact: jsrain(a)suse.com Found By: Outsourced Testing Blocker: --- The inst-sys in current factory prints some warnings to system console in first stage installation, /sbin/get_kernel_version does not exist. I see this particular file referenced in yast2-kdump and scrconf/boot_vmlinux_version.scr Please remove usage of absolute pathnames and rely on $PATH instead. I'm sure there are other places where binaries are called with absolute paths, please fix such places as well. -- 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 17

[Bug 797124] New: xorg-x11-Xvfb doesn't depend on xkeyboard-config
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=797124 https://bugzilla.novell.com/show_bug.cgi?id=797124#c0 Summary: xorg-x11-Xvfb doesn't depend on xkeyboard-config Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jkt(a)gentoo.org QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) rekonq/2.0.50 Safari/534.34 Unless the xkeyboard-config package is installed, running Xvfb results in the following error: XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. Fatal server error: Failed to activate core devices. This looks like a missing dependency because the Xvfb cannot even start. Reproduced by the Trojita package [1] on OBS, I don't run OpenSuSE myself. The bug affects all SuSE versions currently in OBS, including SLES, Factory, Tumbleweed and the latest OpenSuSE release. [1] https://build.opensuse.org/package/show?package=trojita-nightly&project=hom… Reproducible: Always -- 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 796170] New: Dvorak Keyboard Layout not Functional
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=796170 https://bugzilla.novell.com/show_bug.cgi?id=796170#c0 Summary: Dvorak Keyboard Layout not Functional Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Macintosh OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jane.d.anonymous(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 The Dvorak keyboard layout, a variant of the US English layout, does not function properly when selected in YaST. Instead, it is identical to the English (US) layout. Reproducible: Always Steps to Reproduce: 1. Open YaST 2. Navigate to Hardware: System Keyboard Layout 3. Select Dvorak as the keyboard layout. Actual Results: The layout is identical to English (US). Expected Results: The layout should be Dvorak. People on the forums seem to have had similar problems selecting other languages; this is a major issue and can cause serious headaches, especially when your physical keyboard is not laid out in the QWERTY format. -- 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 776600] New: pam winbind settings are only set if we join a windows domain using Yast as a client
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=776600 https://bugzilla.novell.com/show_bug.cgi?id=776600#c0 Summary: pam winbind settings are only set if we join a windows domain using Yast as a client Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: i586 OS/Version: openSUSE 12.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: lynn(a)steve-ss.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/22.0.1190.0 Safari/537.1 SUSE/22.0.1190.0 If we are ourselves the domain controller such as with Samba4 AD, we have no way of setting pam winbind in /etc/pam.d Reproducible: Always Steps to Reproduce: 1.Install Samba4 DC 2.call the samba binary 3.edit /etc/nsswitch.conf to contain passwd: and group: to contain winbind 4.attempt to login on the DC Actual Results: We are authenticated correctly via Kerberos but we cannot login: The pam settings for winbind are not set. Expected Results: We can login. The workaround is not to use winbind on the Samba4 DC. e.g. nss-pam-ldapd works fine This is discussed in this thread: http://lists.opensuse.org/opensuse/2012-08/msg00476.html -- 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 28

[Bug 797034] New: Update osc-plugin-collab in 12.2 to version 0.96
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=797034 https://bugzilla.novell.com/show_bug.cgi?id=797034#c0 Summary: Update osc-plugin-collab in 12.2 to version 0.96 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEEDINFO Severity: Normal Priority: P5 - None Component: Other AssignedTo: vuntz(a)suse.com ReportedBy: vuntz(a)suse.com QAContact: qa-bugs(a)suse.de InfoProvider: maintenance(a)opensuse.org Found By: --- Blocker: --- I'd like to update osc-plugin-collab in 12.2 to version 0.96. The only change is the default server that it uses: it's now a server in the openSUSE infrastructure, instead of a temporary machine. The update will allow dropping the use of that temporary machine faster. The diff is at https://build.opensuse.org/package/rdiff?opackage=osc-plugin-collab&oprojec… -- 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 764990] New: Flash plugin 11.2.202.235-14.1, SUSE 11.4, crashes immediately in Firefox, SEE BUG#764269 - refers to same issues in SUSE 12.1
by bugzilla_noreply＠novell.com 08 Jan '13

08 Jan '13

https://bugzilla.novell.com/show_bug.cgi?id=764990 https://bugzilla.novell.com/show_bug.cgi?id=764990#c0 Summary: Flash plugin 11.2.202.235-14.1, SUSE 11.4, crashes immediately in Firefox, SEE BUG#764269 - refers to same issues in SUSE 12.1 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: nabramski(a)gmail.com QAContact: qa-bugs(a)suse.de CC: meissner(a)suse.com, sndirsch(a)suse.com, dmueller(a)suse.com, wolfgang(a)rosenauer.org, ddadap(a)nvidia.com Depends on: 761975,764269 Found By: System Test Blocker: --- Niko Abramski <nabramski(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |CCB_Review? I do not want to inadvertently create a duplicate bug report however I noticed this same issues under BUG#764269. That particular Bug Report (#764269) is referring to SUSE 12.1 and I'd like to advise that 11.4 is experiencing the exact same issue(s) identical to the descriptions in the Suse 12.1 Bug report. Flash-Player 11.2.202.235-14.1 does nothing BUT crash within Firefox; the only recourse is to revert back to the previous edition (11.2.202.233-9.1). If/When you have a moment, please advise if this IS INCLUDED under the SUSE 12.1 report & I will close-out/mark as duplicate. I apologize in advance for any inconvenience. Otherwise, Thanks to all those who are diligently working on this matter. Please advise if I can be of further assistance and I will do my best and as quickly as possible!!! As always, sincerest gratitude for all the hard work & dedication!! :):):):) Yours, Niko +++ This bug was initially created as a clone of Bug #764269 +++ (copy of public facing bug which ahs too many people cced) i debugged flash-player a bit export MOZ_X_SYNC=1 firefox& gdb attach to plugin container wait for crash bt I get different backtraces every time, but libvdpau* and the main plugin gtk2 window are involved always. -- 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