April 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 775855] New: /etc/default/grub_installdevice contains kernel device names
by bugzilla_noreply＠novell.com 26 Apr '13

26 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=775855 https://bugzilla.novell.com/show_bug.cgi?id=775855#c0 Summary: /etc/default/grub_installdevice contains kernel device names Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: ohering(a)suse.com QAContact: jsrain(a)suse.com Found By: Outsourced Testing Blocker: --- after install of 12.2-rc2, while trying to rescue a test system for bug #775669, I noticed /dev/sda4 in /etc/default/grub_installdevice Please make sure to not use kernel device names in config files, instead some sort of /dev/disk/by-something should be used. -- 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 775678] New: Old Fedora Core 6 installation doesn't boot with grub2
by bugzilla_noreply＠novell.com 26 Apr '13

26 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=775678 https://bugzilla.novell.com/show_bug.cgi?id=775678#c0 Summary: Old Fedora Core 6 installation doesn't boot with grub2 Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: i586 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: johanh.botha(a)eskom.co.za QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=502123) --> (http://bugzilla.novell.com/attachment.cgi?id=502123) grub2_mkconfig output User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20100101 Firefox/13.0.1 My system has Fedora Core 6, Ubuntu 12.04 and OpenSuSE 12.2 RC2 on OpenSuSE was installed last, and installed the bootloader. Everything appears in the boot menu, but the Fedora installation doesn't boot. It gives a message about not being able to find device xxx (the uuid of the device) Then says loading kernel, but gets stuck there. Reproducible: Always Steps to Reproduce: 1.Install Fedora Core 6 2.Install OpenSuSE 12.2 RC2 and grub2 bootloader 3.Try to boot Fedora Core 6 Actual Results: System stops at the time of loading the kernel Expected Results: System should 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 3

[Bug 775610] New: grub2-efi incorrect win7 menu stanza
by bugzilla_noreply＠novell.com 26 Apr '13

26 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=775610 https://bugzilla.novell.com/show_bug.cgi?id=775610#c0 Summary: grub2-efi incorrect win7 menu stanza Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: dana(a)wellen.us QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.75 Safari/537.1 Installed RC2 onto a duel boot system with existing win7 efi install. I have the openSUSE 12.2RC2 booting fine with grub2-efi install but the win7 entry is unbootable. The efi partition is at the end partition which I think is causing the problem. Model: ATA WDC WD5000AAKS-0 (scsi)Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 32.3kB 500GB 500GB ntfs Microsoft basic data 2 500GB 500GB 209MB fat32 boot The stanza created automatically by the 30_os-prober in /etc/grub.d creates this which points to the first partition (ntfs) and appears to be a mbr boot config. ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-746C89606C891E4C' { insmod part_gpt insmod ntfs set root='hd0,gpt1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 746C89606C891E4C else search --no-floppy --fs-uuid --set=root 746C89606C891E4C fi chainloader +1 } ### END /etc/grub.d/30_os-prober ### The uuids are for the ntfs partition not the gpt partition and the chainloader command is should be: chainloader (${root})/efi/Microsoft/Boot/bootmgfw.efi grub2-probe --target=fs_uuid /boot/efi/EFI/Microsoft/Boot/bootmgr.efi 3185-A28F grub2-probe --target=fs_uuid /windows/C/ 746C89606C891E4C As seen the uuid being used is the one for the ntfs but should be the uuid for the efi partition. And what I think is casuing the problem is that it isn't on the first partition. I can fix the issue by adding a custom menu item in the /etc/gub.d/40_custom using please_try_again's guide but the automatic generation produces a extra menu item. Reproducible: Always Steps to Reproduce: 1.run grub2-efi-mkconfig 2. 3. Actual Results: Mbr stanza instead of efi stanza Expected Results: correct stanza for efi booting --- Comment #1 from Lukas Ocilka <locilka(a)suse.com> 2012-09-06 14:57:36 UTC --- *** Bug 775611 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=775611 -- 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 15

[Bug 814756] New: Today's update to grub2-efi is broken. It needs to be pulled.
by bugzilla_noreply＠novell.com 26 Apr '13

26 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=814756 https://bugzilla.novell.com/show_bug.cgi?id=814756#c0 Summary: Today's update to grub2-efi is broken. It needs to be pulled. Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: nrickert(a)ameritech.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) rekonq/2.1 Safari/534.34 An update today to grub2-efi 2.00-19.13.1 results in secure-boot failing. So secure-boot has to be disabled in order to boot into the system. See forum discussion at https://forums.opensuse.org/english/get-technical-help-here/install-boot-lo… In my case, I have two installs of opensuse. I applied the update to only one of those (the one that was not used for testing bug 809038). With secure boot enable, a boot entry for this install did not show up. I could only boot the other install, or boot this install indirectly using the grub menu for the other install). With secure boot disabled, both installs are accessible from the UEFI menu, and it defaults to booting to the one where I applied the update. 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 11

[Bug 816389] New: Segfault in Gparted 0.15.0 when copying partition
by bugzilla_noreply＠novell.com 25 Apr '13

25 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=816389 https://bugzilla.novell.com/show_bug.cgi?id=816389#c0 Summary: Segfault in Gparted 0.15.0 when copying partition Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: Other URL: https://bugzilla.gnome.org/show_bug.cgi?id=697727 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: lazy.kent(a)opensuse.org QAContact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org Found By: --- Blocker: --- Please read: http://gparted.sourceforge.net/download.php "WARNING: Avoid Using GParted 0.15.0 for Partition Moves, Resizes, Copies and Checks. We are investigating reports of intermittent crashes with GParted 0.15.0. The risk of LOSS of DATA is highest when performing partition moves, resizes, copies, and checks. As such we recommend using GParted 0.14.1 for all move, resize, copy, and check operations. Other operations such as create, delete, format, label, set UUID, and delete might also crash, but these should not result in unexpected data loss, and the operation can be repeated." https://bugzilla.gnome.org/show_bug.cgi?id=697727 -- 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 817080] New: graphics/photorec: installed in ../bin (move to ../sbin)
by bugzilla_noreply＠novell.com 25 Apr '13

25 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=817080 https://bugzilla.novell.com/show_bug.cgi?id=817080#c0 Summary: graphics/photorec: installed in ../bin (move to ../sbin) Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software AssignedTo: meissner(a)suse.com ReportedBy: lazy.kent(a)opensuse.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: nadvornik(a)suse.com Found By: --- Blocker: --- photorec and testdisk generally work with block devices. A regular user can't read from a block device. Running photorec I see a message: "You need to be root to use PhotoRec." manpages are installed in man8, that also shows the program is for root usage only. -- 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 780256] New: openSUSE:12.2/taglib: Bug with extracting id from m4a files
by bugzilla_noreply＠novell.com 25 Apr '13

25 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=780256 https://bugzilla.novell.com/show_bug.cgi?id=780256#c0 Summary: openSUSE:12.2/taglib: Bug with extracting id from m4a files Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: crrodriguez(a)opensuse.org ReportedBy: tibirna(a)kde.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Customer Blocker: --- Every application that uses taglib to extract id info from m4a files fails while displaying a very long list of TagLib: String::prepare() - Unicode conversion error. (one for each failed field read, I suppose). Observed with amarok, kid3 and soundkonverter. These apps also replace in their interfaces the missing id fields (title, artist, album etc.) with some date in the format 2012-01-03T08:00:00Z. This is with: - stock openSUSE 12.2 with all updates as of 2012-09-13; - KDE 4.9 from download.opensuse.org/repositories/KDE:/Release:/49; - m4a files pristine from the ITunes store, bought most recently 6 months ago. -- 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 46

[Bug 802206] New: [patch] devel:languages:nodejs/nodejs: mixed v8 headers/libs causes symbol errors and failure to run node apps
by bugzilla_noreply＠novell.com 25 Apr '13

25 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=802206 https://bugzilla.novell.com/show_bug.cgi?id=802206#c0 Summary: [patch] devel:languages:nodejs/nodejs: mixed v8 headers/libs causes symbol errors and failure to run node apps Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: opensuse-communityscreening(a)forge.provo.novell.com ReportedBy: adaugherity(a)tamu.edu QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- Dependencies installed via 'npm install' get built with the v8 headers bundled with the node tarball (the default node-gyp behavior) but linked against the libv8 installed from this repo (since nodejs is built with shared-v8). This causes failure to run due to symbol errors, e.g.: ---- node: symbol lookup error: /home/ADaugherity/ec/node_modules/ExportControls/node_modules/ldapjs/node_modules/buffertools/build/Release/buffertools.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPFNS_6HandleINS_5ValueEEERKNS_9ArgumentsEES3_NS1_INS_9SignatureEEE ---- I fixed this by copying a patch from Fedora which patches node-gyp to use the system v8 headers instead of those in the node tarball, and also remove the tarball v8 headers during build so they don't get installed under /usr/include/node. I opened a request via the build service last week but it is still in NEW state and I have not received any feedback on it. https://build.opensuse.org/request/show/150650 This is my first time using osc to branch, submit requests, etc., so if I need to do things differently, please let me know. -- 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 718163] New: xdg-su generic broken
by bugzilla_noreply＠novell.com 25 Apr '13

25 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=718163 https://bugzilla.novell.com/show_bug.cgi?id=718163#c0 Summary: xdg-su generic broken Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: dmueller(a)suse.com ReportedBy: bwiedemann(a)suse.com QAContact: qa(a)suse.de Found By: Development Blocker: --- On Factory+icewm run xdg-su -c yast this produces: /usr/bin/X11/xterm: bad command line option "-geom" without starting the intended program. changing line 358 and 360 in /usr/bin/xdg-su to have "-geometry" instead of "-geom" fixes this. -- 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 615034] New: vsftpd broken
by bugzilla_noreply＠novell.com 25 Apr '13

25 Apr '13

http://bugzilla.novell.com/show_bug.cgi?id=615034 http://bugzilla.novell.com/show_bug.cgi?id=615034#c0 Summary: vsftpd broken Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: mseben(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- vsftpd is broken somehow: $ ftp -a 1.2.3.4 Connected to 1.2.3.4 220 Welcome message 331 Please specify the password. do_ypcall: clnt_call: RPC: Unable to send; errno = Network is unreachable ftp: Login failed. ftp> dir 230 Login successful. parse error! ftp> dir 229 Entering Extended Passive Mode (|||30094|). 229 Entering Extended Passive Mode (|||30017|). 200 EPRT command successful. Consider using EPSV. ftp> dir 150 Here comes the directory listing. 426 Failure writing network stream. ftp> dir 200 EPRT command successful. Consider using EPSV. 200 PORT command successful. Consider using PASV. ftp> dir 200 PORT command successful. Consider using PASV. 150 Here comes the directory listing. drwxr-xr-x 2 40 0 4096 Jun 02 2008 games drwxrwxrwt 2 40 0 4096 Jun 17 09:11 tmp [...] 426 Failure writing network stream. ftp> The very same config works just fine with the 11.2 vsftpd: # grep -v '^#\|^$' /etc/vsftpd.conf|sort anon_mkdir_write_enable=YES anon_root=/srv/ftp anon_umask=022 anon_upload_enable=YES anon_world_readable_only=YES anonymous_enable=YES chroot_local_user=NO connect_from_port_20=YES dirmessage_enable=YES ftpd_banner=Welcome message idle_session_timeout=900 local_enable=NO log_ftp_protocol=NO max_clients=10 max_per_ip=3 nopriv_user=ftpsecure pam_service_name=vsftpd pasv_enable=YES pasv_max_port=30100 pasv_min_port=30000 ssl_enable=NO ssl_sslv2=NO ssl_sslv3=NO ssl_tlsv1=YES syslog_enable=NO write_enable=YES -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 19