January 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 853512] New: Macbook(2,1) Wireless Connection Drops Out Every Few Minutes
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=853512 https://bugzilla.novell.com/show_bug.cgi?id=853512#c0 Summary: Macbook(2,1) Wireless Connection Drops Out Every Few Minutes Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Macintosh OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: julia.mailings(a)gmx.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 My wireless connection drops at random intervals, but generally will not persist for more than 10 minutes at a time. When the connection drops out, I am unable to find my wireless network in the network manager applet. To see it again, I must first disable wireless in the applet, and then re-enable it (after any short interval), and the network will be easily rediscovered and reconnected to. Output of lspci | grep Network: 02:00.0 Network controller: Qualcomm Atheros AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01) Reproducible: Always Steps to Reproduce: 1. Connect to a wireless network 2. Wait for any interval between 2 and 20 minutes 3. Connection drops 4. Disable wireless in the network manager applet 5. Re-enable wireless in the applet 6. Network Manager will reconnect with the wireless network; goto 1. Actual Results: The connection drops out regularly. Expected Results: The connection should persist. I tried setting the MTU manually, as this is suggested in several places online, but it didn't help. My Internet provider is AT&T. Please pardon the classification as a major bug if inappropriate. Constant Internet disconnects are inconvenient at best, but could be a major problem for large and frequent data transfers. -- 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 827412] New: fn-keys do not work with kernel 3.9 on asus u30sd
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=827412 https://bugzilla.novell.com/show_bug.cgi?id=827412#c0 Summary: fn-keys do not work with kernel 3.9 on asus u30sd Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: srid(a)rkmail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11) KHTML/4.10.3 (like Gecko) Konqueror/4.10 SUSE I'm using Asus u30sd notebook computer. Fn-keys, like volume or media player control, do not work anymore with linux 3.9.8. Xev detects no keycodes. Brightness keys work, but it takes seconds before it actually changes. The keys used to work fine with linux 2.6.29 - 3.6, but I'm not sure about 3.7 and 3.8 The software is openSUSE 12.3 (KDE) and linux kernel 3.9.8 from kernel:stable 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 12

[Bug 858380] New: 13.1: Bluetooth does not work in XFCE
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=858380 https://bugzilla.novell.com/show_bug.cgi?id=858380#c0 Summary: 13.1: Bluetooth does not work in XFCE Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: IA64 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: --- The release notes do not say that bluetooth doesn't work in XFCE, they only say that it doesn't work in KDE. So it should work. But it does not. In 13.1, I see this in the log when I connect the usb-bt dongle: <3.6> 2014-01-10 23:44:22 minas-tirith bluetoothd 1764 - - Endpoint registered: sender=:1.222 path=/MediaEndpoint/A2DPSource <3.6> 2014-01-10 23:44:22 minas-tirith bluetoothd 1764 - - Endpoint registered: sender=:1.222 path=/MediaEndpoint/A2DPSink but nothing in the XFCE panel indicates it is working. I have tried two machines, 3 installs. It worked on previous releases on the same hardware. People in the mail list say that it is broken and that I should report it in Bugzilla. -- 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 856475] New: Installation of restricted multimedia formats fail in all cases due to a non existing package / dependency on a 32 bit system, fresh install
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856475 https://bugzilla.novell.com/show_bug.cgi?id=856475#c0 Summary: Installation of restricted multimedia formats fail in all cases due to a non existing package / dependency on a 32 bit system, fresh install Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: stakanov(a)freenet.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=572718) --> (http://bugzilla.novell.com/attachment.cgi?id=572718) screenshot of the error message in question User-Agent: Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 I am trying to finish a complete new install of a 32 bit opensuse 13.1 system. While trying to install the "restricted multimedia" formats, this fails no matter if using the proposed migration or the usual method (pass on to packman repos, with vendor change). The error message is: nothing allows the installation of libx264.so.135 necessary to .... (several packages of course) libx264.135 is installed from KDE Extra (where zypper did find it) but the desired dependency seems to exist only in 64 bit. This system is with Nvidea video drivers installed. Users have been added to video group. Reproducible: Always Steps to Reproduce: 1.install 13.1 with all upgrades 2.follow the upgrade path for restricted format / or pass to packman 3.installation fails due to dependency of a non existing package Actual Results: Installation fails because of the lack of libx264.so.135 as dependency Expected Results: Installation should go in automagic. If ignoring and installing the same, major features (like VLC, mp4 and other format reproduction are broken). -- 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 854353] New: YaST incorrectly removes UEFI boot variables on installation and kernel update.
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=854353 https://bugzilla.novell.com/show_bug.cgi?id=854353#c0 Summary: YaST incorrectly removes UEFI boot variables on installation and kernel update. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: dexter.1234(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=570740) --> (http://bugzilla.novell.com/attachment.cgi?id=570740) YaST logs and hwinfo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 On installation, or when a kernel update is installed, YaST assumes any boot variable with the term "opensuse" in the label field refers to an installation residing in /boot/efi/EFI/opensuse and removes all boot variable containing "opensuse". This behavior is wrong and contrary to the UEFI specification. The behavior occurs in 13.1 and 12.3. Background. The UEFI specification provides for vendor specific directories in the boot partition. OpenSuse uses /EFI/opensuse. During installation/kernel update, YaST is not checking that a boot variable actually belongs to opensuse by examining the path in the UEFI boot variable (via efivars or efivarfs), but rather, it simply examines the label field in the UEFI boot variable and if it contains "opensuse" it removes the boot variable even if: 1) the path points to some location other than /EFI/opensuse, and 2) there are multiple instances of "opensuse" in EFI boot variables. The label field is intended as a descriptive field that a user may freely change without restriction other than character set. The way YaST utilizes the lablel field adds a restriction not embraced in the UEFI specification. This behavior causes problems where there are multiple installations of opensuse on a system in which the boot directories exist in the boot partition in directories other than /EFI/opensuse. Discussion. One area of the UEFI specification that is problematic is that it does not address the installation of multiple versions of an OS as is common in the Linux community. Rather, it assumes that each vendor will use a specific directory in the boot partition and leaves open the issue of multiple installations by a single vendor on a platform. To date, the Linux community has not addressed this issue. Since I use multiple OS installations on UEFI platforms, I do this by using differently named directories in /EFI and boot via the kernel efi boot stub. Since I uses labels on the UEFI boot variables like "openSUSE 12.2", "openSUSE 12.3", and so on, each time there is an install or kernel update in 12.3 or 13.1, all UEFI boot variables containing the term "opensuse" are summarily removed by YaST. The fix has been to remove "opensuse" from all UEFI boot variable labels so YaST does not erroneously remove them. Reproducible: Always Steps to Reproduce: 1.Install opensuse 12.3 or 13.1 then rename the uefi boot directory to something other than /EFI/opensuse, for example, /EFI/foobar. 2.Rename the initrd and vmlinuz files in /EFI/foobar to "initrd" and "vmlinuz.efi", respectively. Use efibootmgr to create a UEFI boot entry as: efibootmgr -c -d /dev/sda -p 1 -L "openSUSE YaST will clobber this" -l "\EFI\foobar\vmlinuz.efi" -@ vmlinuxargs-ucs2 Note: vmlinuxargs-ucs2 is simply a UCS2 encoded file that contains the kernel command line parameters which are written to the boot variable. In my case, this file contains: initrd=\EFI\foobar\initrd root=/dev/disk/by-id/ata-WDC_WD10EALX-009BA0_WD-WCATR9648710-part5 resume=/dev/disk/by-id/ata-WDC_WD10EALX-009BA0_WD-WCATR9648710-part2 splash=silent quiet showopts 3.Boot the system and note the UEFI bios will have a boot entry "openSUSE YaST will clobber this". 4.Install opensuse 12.3 or 13.1 again. This will install to /EFI/opensuse. Now, checking the boot variables via the UEFI bios boot manager or efibootmgr in linux it will be noted that the boot variable containing "openSUSE YaST will clobber this" will have been removed by YaST on the second installation. Note that the contents of /EFI/foobar are unaltered and can be made bootable by rewriting the boot entry with efibootmgr. Actual Results: As described, YaST arbitrarily removes any and all UEFI boot variables containing the term "opensuse" with regard for the path in the boot variable. Expected Results: YaST should not remove any UEFI boot variable that does not have the path /EFI/opensuse. FYI, I do have a UEFI boot manager solution which I will release to the community in about 3 months (currenty implementing all the secure boot shims) which has a solution to the multiple os issue in UEFI and allows multiple installations to reside in the vendor directory without conflict. -- 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 854914] New: IBM Notes 9.0.1 (IBM JRE 1.6.0) crashes with libgobject-32bit
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=854914 https://bugzilla.novell.com/show_bug.cgi?id=854914#c0 Summary: IBM Notes 9.0.1 (IBM JRE 1.6.0) crashes with libgobject-32bit Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Commercial AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: asvetter(a)cip.physik.uni-wuerzburg.de 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 IBM Notes 9.0.1 (IBM JRE 1.6.0) crashes in libgobject-32bit Notes is a 32bit software based on Eclipse. I will attach a javacore file. 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 18

[Bug 856828] New: gphoto2 doesn't connect to canons s100
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856828 https://bugzilla.novell.com/show_bug.cgi?id=856828#c0 Summary: gphoto2 doesn't connect to canons s100 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: arun(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Connecting a canon s100 and trying to do a gphoto2 -P ends in an io error in gphoto2. These seems to be the bugs: http://sourceforge.net/p/gphoto/bugs/958/ http://sourceforge.net/p/gphoto/bugs/965/ I managed to get my camera connected by doing rm /usr/lib64/libgphoto2/2.5.2.1/canon.so cp /usr/lib64/libgphoto2/2.5.2.1/ptp2.so /usr/lib64/libgphoto2/2.5.2.1/canon.so these are in the libgphoto2-6 package Reproducible: Always Steps to Reproduce: 1. connect canon s100 via usb 2. run e.g. env LANG=C gphoto2 --debug 3. Actual Results: io error Expected Results: connect to camera -- 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 813244] New: Shutdown fails to power off
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=813244 https://bugzilla.novell.com/show_bug.cgi?id=813244#c0 Summary: Shutdown fails to power off Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: aaroncosand(a)yahoo.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=533334) --> (http://bugzilla.novell.com/attachment.cgi?id=533334) dmesg output related to ACPI User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.32 (KHTML, like Gecko) Chrome/27.0.1425.0 Safari/537.32 SUSE/27.0.1425.0 Shutdown (tried gnome menu, command prompt <shutdown -P now, poweroff systemctl poweroff>) does not power off machine, although it seems to reach the end of shutting down processes and unmounting file systems. If I reboot, instead of poweroff, the system boots to the grub2 menu, then hangs after "loading init ramdisk". I have no value for splash so normally the system starts displaying startup messages. I have taken to selecting reboot, then pressing 'c' when the grub menu comes up, and typing halt, which does power off the machine. A cold boot works fine. Reproducible: Always Steps to Reproduce: 1.boot 2.login (non root) 3.shutdown Actual Results: System displays shutdown messages and then hangs after last unmount message Expected Results: System no powers off This happens on a clean install before and after the initial round of updates are loaded from the internet. -- 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 771566] New: gleichzeitiges Brennen mit mehreren USB-Brennern
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=771566 https://bugzilla.novell.com/show_bug.cgi?id=771566#c0 Summary: gleichzeitiges Brennen mit mehreren USB-Brennern Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hb(a)bacu.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 Seit ca. Februar 2012 kann man mit Suse 11.3 und neuer keine CD's und DVD's mehr mit meheren Brennern brennen. Die Prgramme sind egal ob wodim, cdrecord. Nach ausführlicher Rücksprache mit Jörg Schilling muß es am Kernel liegen. Es wurde auf mehreren Rechnern mit Suse 11.4 12.1 getestet. Mit centos 6.1 geht alles prima Reproducible: Always Steps to Reproduce: 1. Basissystem 12.1 installieren (bei mir AMD X3 oder AMD E-350) 2. 3 USB-Brenner anschließen 3. mit wodim 3 CD's mit 12 Fach brennen 4. Brenngeschwindigkeit bricht ein auf 3-fach 5. Mit DVD noch schlimmer Expected Results: Brenne mit centos 6.1 problemlos mit 5 Brennern 12 oder 16-fach oder 3 DVD mit 4-6 fach übrigends mit suse 11.1 auch noch -- 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 847794] New: openSUSE_13.1 RC1: after installation /var/tmp/ is present in /var/tmp
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=847794 https://bugzilla.novell.com/show_bug.cgi?id=847794#c0 Summary: openSUSE_13.1 RC1: after installation /var/tmp/ is present in /var/tmp Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: richard.bos(a)xs4all.nl 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/30.0.1599.66 Safari/537.36 SUSE/30.0.1599.66 Installed openSUSE_13.1 normal procedure Played with it. Checked /var/tmp: # cd /var/tmp # ls Hmm, there is a directory called var # cd var # ls tmp So there is the directory: /var/tmp/var/tmp Which is unexpected Reproducible: Didn't try Steps to Reproduce: 1. see details 2. I installed openSUSE_13.1 rc1 only once, I don't know if it is reproduable 3. Actual Results: /var/tmp/var is present Expected Results: /var/tmp/var should not exist -- 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