December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 836578] New: wireless does not work
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=836578 https://bugzilla.novell.com/show_bug.cgi?id=836578#c0 Summary: wireless does not work Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: illumilore(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/28.0.1500.71 Chrome/28.0.1500.71 Safari/537.36 After a new install of 12.3, there was no option for enable wireless in the network options for the first boot up. Only after restarting did the option actually show up. But I can still check the enable wireless button, but it will just uncheck itself after a couple of seconds, and then I am required to use my laptops wireless hardware shortcut key to make the enable wireless checkbox selectable again. According to the opensuse guide http://www.opensuse-guide.org/wlan.php, the wireless adapters I have should work. wlan0, atheros ar9285 wlan1, ralink Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: see above Expected Results: na -- 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 824861] New: boot fails because xp dependant drive not found
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c0 Summary: boot fails because xp dependant drive not found Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 32bit OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: root.aimcmp2(a)cox.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 6/13/2013 Dear Sirs, I have backup hardware, i.e. 2 computer with same hardware; none the less the drive ids are different slightly. These are Intel Core I7 CPU 870 @2.93GHz, 3 Western Digital VelociRaptor 1 300gb main drive and 2 150gb data drives. After restore of backup image from Main Desktop, backup hardware fails to boot on a dual boot system with Grub2 because it can not file "depentant drives" as the drive ids are slightly differnet even with the same drive model and size. Grub2 now finds Linux, where grub did not for a while, same reason; main drive id slightly different Desktop and backup hardware; and Grub2 find Xp, But Grub2 OR the boot system does not find "depentant drives" on the XP SP3 system and FAILS TO BOOT. WHY WOULD Linux not boot because of XP? Seems always should boot if finds Linux? Please advise. Even if I replace Grub2, system would still not start as your log clearly states: fail dependent drives and lanches emerency system and a mount -a fails to clear the problem. Reproducible: Always Steps to Reproduce: 1.6/13/2013 Dear Sirs, I have backup hardware, i.e. 2 computer with same hardware; none the less the drive ids are different slightly. These are Intel Core I7 CPU 870 @2.93GHz, 3 Western Digital VelociRaptor 1 300gb main drive and 2 150gb data drives. After restore of backup image from Main Desktop, backup hardware fails to boot on a dual boot system with Grub2 because it can not file "depentant drives" as the drive ids are slightly differnet even with the same drive model and size. Grub2 now finds Linux, where grub did not for a while, same reason; main drive id slightly different Desktop and backup hardware; and Grub2 find Xp, But Grub2 OR the boot system does not find "depentant drives" on the XP SP3 system and FAILS TO BOOT. WHY WOULD Linux not boot because of XP? Seems always should boot if finds Linux? Please advise. Even if I replace Grub2, system would still not start as your log clearly states: fail dependent drives and lanches emerency system and a mount -a fails to clear the problem. 2. 3. Actual Results: boot fails emeregcy login provided only Expected Results: dual 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 17

[Bug 829436] New: systemd[1] dependency failed for /windows/G , grub2, no repair tools
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=829436 https://bugzilla.novell.com/show_bug.cgi?id=829436#c0 Summary: systemd[1] dependency failed for /windows/G , grub2, no repair tools Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: root.aimcmp2(a)cox.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 Thread: systemd[1] dependency failed for /windows/G , grub2, no repair tools http://forums.opensuse.org/english/get-technical-help-here/install-boot-log… Also: https://bugzilla.novell.com/show_bug.cgi?id=824861 alannsandiego Join Date May 2009 Location San Diego CA 92138 Posts 25 Default Re: systemd[1] dependency failed for /windows/G , grub2, no repair tools I noticed no one yet has a good solution to my original problem, except to get the developers to correct the problem ( 7/12/2013, This fix of the boot system is a complex fix and not to be done manually. > This is about asking the developers to build onto OpenSuse a GUI tool If you want to communicate with the developers, you need to open a bug in Bugzilla or a feature request in FATE. OK I see about this. Without an OpenSuse GUI repair tools and admin functions like saving all emails and personal settings, not everyone want to be a Linux expert, or do commands in text lines in Linux to use it. Without better support Linux remains unusable for productions system; it is just very pretty but not useful.) so here it is again: 7/5/2013, Dear Forum, I have backup hardware the same as my desktop, but after a Restore on the backup hardware OpenSuse 12.3 will not boot: Novell missing the fact the Backup Hardware never will be the same as the original system. I only reason the system boot at all is you now ignoring /Dev/by id method and booted /Dev/root Here is more description: last boot mesg: started show plymouth boot screen ---- boot log says this: systemd[1] dependency failed for /windows/G. =================================================== Even though the hardware is the same the device by ID is slightly different and so that method fails and the backup hardware will not start up completely. It boot too the emergency system even though all of OpenSuse is found and only non primary XP partitions are not found. The only reason that OpenSuse 12.3 boot at all is the start up script now ignores Dev/by id and now ignoring /Dev/by id method and booted /Dev/root must do the same thing for the XP C drive, but OpenSuse missed ignoring /Dev/by id method for my two other internal hard drives. Even if I replace my one of my failing drive OpenSuse 12.3 would fail to boot with the Dev/by id method; because the new drive will have a new ID and the only time OpenSuse repairs the boot method now is on an install; so any changes or do a restore to backup hardware and OpenSuse 12.3 can not be easily repair at present. Since there is no Live-CD with repair tools to fix the boot method like ================================================= BTW DO NOT USE THIS TOOL ON OPENSUSE, IT DOES NOT WORK FOR OPENSUSE. How about Novell fix this so that it works for OpenSuse? boot-repair: Simple GUI tool to Repair Grub2 Boot Loader | Handy Tutorial boot-repair-disk - Browse Files at SourceForge.net Home How-To Ubuntu Linux Windows About Us Handy Tutorial boot-repair: Simple GUI tool to Repair Grub2 Boot Loader I tried this tool and it missing one routine "xxxx..." someone commented about it; the routine is not on the disk and so this tool is broken. ================================================================================= The particular bug in Grub2 is that if you change from /Dev/by id to Dev/device this does not change the installation itself; it changes back. And further Grub2 does not present a list of /Dev/by id, or /Dev/device, or /Dev/by label to choose from so that one does not make an error in a long description. ======================================================== OpenSuse 12.3 is a great op system if nothing breaks, but the lack of repair tools on a Live-CD is a great defect. Any suggestion for a non expert? a simple way to fix this problem? ========================================================== It does not matter who owns OpenSuse This is not a backup issue, the backup and restore work very well. This is about asking the developers to build onto OpenSuse a GUI tool like the one above and this comment This entails booting from a live/rescue DVD/CD and doing a chroot Might want to look at this thread https://forums.opensuse.org/english/...-not-boot.html >From a live-CD tool you have to use chroot to change the broken system, and of course if you read carefully, this boot does not need to fail at all same method use to find the /dev/root and c for XP can find all the drives with the same partition structure if the fix systemd[1]? Yes, if you can expert you can use the emergency repair system to manual fix the broken system, But why not have a GUI repair tool for this and other repairs? As soon as I replace my week drive OpenSuse 12.3 will not boot because the boot process will not see the new drive with the /Dev/by ID method. Until you fix this I can not use OpenSuse. At the present time on on install do you fix the boot process and that is not good enough to use your system. User benefit: If you replace a hard drive on an OpenSuse system at present the system will fail boot because you have no process to fix the boot process by repair GUI. Also after a restore to almost identical hardware the system does not boot even after a restore because your boot process does not see the same partitions on drive with a different /Dev/by ID number There is a simple fix to this problem is to change the systemd[1] script to ignore /Dev/ by ID number and boot to /dev/root and ADD a method to SEE non root partitions as you have already done for /Dev/root and XP root or C: drive. 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 836506] New: When I use skk-mode, Emacs can not be finished because Emacs cannot load '$HOME/.skk-jisho' .
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=836506 https://bugzilla.novell.com/show_bug.cgi?id=836506#c0 Summary: When I use skk-mode, Emacs can not be finished because Emacs cannot load '$HOME/.skk-jisho' . Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bkbin005(a)rinku.zaq.ne.jp QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=554012) --> (http://bugzilla.novell.com/attachment.cgi?id=554012) a GDB backtrace file User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1608.1 Safari/537.36 I am testing openSUSE 13.1 Milestone 4 x86_64 with GNOME desktop in VirtualBox 4.2.16 r86992 on Windows 7 SP1 64 bit . Host information: https://dl.dropboxusercontent.com/u/86335040/DxDiag17.txt . When I use skk-mode, Emacs can not be finished because Emacs cannot load '$HOME/.skk-jisho' . I attached a GDB backtrace file . Reproducible: Always Steps to Reproduce: 1. $emacs . 2. M-x skk-mode . 3. C-x C-c 4. $kill {emacs's pid} Actual Results: 3. Emacs cannot load '$HOME/.skk-jisho' and Emacs can not be finished . 4. Emacs crashes with SIGABRT in raise at ./nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 Expected Results: 3. Emacs should be finished normally . 4. Emacs should not crash with SIGABRT, Emacs should be finished normally . emacs-x11-24.3-4.3.x86_64 libtiff5-4.0.3-6.2.x86_64 libgif6-5.0.4-1.2.x86_64 libXpm4-3.5.10-6.3.x86_64 libXft2-2.3.1-6.3.x86_64 libMagickWand-6_Q8-1-6.8.5.7-3.5.x86_64 libMagickCore-6_Q8-1-6.8.5.7-3.5.x86_64 libotf0-0.9.13-1.2.x86_64 libm17n0-1.6.4-1.2.x86_64 libjbig2-2.0-9.1.x86_64 libgomp1-4.8.1_20130711-1.2.x86_64 liblcms2-2-2.5-1.2.x86_64 libbz2-1-1.0.6-25.4.x86_64 ddskk-20121010_14.4-3.8.noarch skkdic-20121010_14.4-3.8.noarch Please see also: http://lists.opensuse.org/opensuse-ja/2013-08/msg00061.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 5

[Bug 842725] New: Network connection icon shows disconnect while wireless connected.
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=842725 https://bugzilla.novell.com/show_bug.cgi?id=842725#c0 Summary: Network connection icon shows disconnect while wireless connected. Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bchou(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Component Test Blocker: --- Network connection icon shows disconnect while wireless connected. BUILD: openSUSE 13.1 Beta (Hackathon) Steps: 1. Install openSUSE 13.1 Beta. 2. Connect to a Wi-Fi AP. 3. Make sure the Wi-Fi connection is connected. 4. Observe the Network connection icon. Actual Result: Network connection icon shows offline. Expected Result: Network connection icon shows connected instead of offline. -- 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 855384] New: Kernel Bug leads to X server crash
by bugzilla_noreply＠novell.com 10 Jan '14

10 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=855384 https://bugzilla.novell.com/show_bug.cgi?id=855384#c0 Summary: Kernel Bug leads to X server crash Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mantel(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Created an attachment (id=571735) --> (http://bugzilla.novell.com/attachment.cgi?id=571735) Kernel bug message I was just copying some data to a NAS via NFS, when suddenly the X server was killed and a kernel bug message was printed to the screen. Luckily the message has been logged. See attachment. -- 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 849251] New: zypper: always installs a package not required by anything
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=849251 https://bugzilla.novell.com/show_bug.cgi?id=849251#c0 Summary: zypper: always installs a package not required by anything Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- What I did: zypper dup --no-r (--no-recommends) What I observed: zypper always installs libyui-ncurses5. As I already use --no-r (--no-recommends), it would seems that this behavior is not the cause of Recommends: lines in .spec files. What I expected: Do not install libyui-ncurses5. Log: v-suse:/var/log # zypper dup --no-r Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW package is going to be installed: libyui-ncurses5 1 new package to install. Overall download size: 287.9 KiB. After the operation, additional 1.0 MiB will be used. Continue? [y/n/? shows all options] (y): ^C v-suse:/var/log # rpm -q zypper libzypp zypper-1.9.3-1.1.x86_64 libzypp-13.8.1-1.1.x86_64 -- 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 854321] New: kiwi: netboot initrd creation broken
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=854321 https://bugzilla.novell.com/show_bug.cgi?id=854321#c0 Summary: kiwi: netboot initrd creation broken Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: cyberorg(a)opensuse.org QAContact: adrian(a)suse.com Found By: --- Blocker: --- Created an attachment (id=570722) --> (http://bugzilla.novell.com/attachment.cgi?id=570722) Boot stops with this error User-Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 kiwi --add-profile diskless --add-profile std --prepare /usr/share/kiwi/image/netboot//suse-13.1 --root /srv/kiwi-netboot-i386 && kiwi -y --create /srv/kiwi-netboot-i386 -d /srv/netboot/ Image size is too big: du -sh /srv/netboot/* 90M /srv/netboot/initrd-netboot-suse-13.1.i686-2.1.1.gz 0 /srv/netboot/initrd-netboot-suse-13.1.i686-2.1.1.kernel 4.6M /srv/netboot/initrd-netboot-suse-13.1.i686-2.1.1.kernel.3.11.6-4-default 4.0K /srv/netboot/initrd-netboot-suse-13.1.i686-2.1.1.kernel.3.11.6-4-default.md5 4.0K /srv/netboot/initrd-netboot-suse-13.1.i686-2.1.1.md5 28K /srv/netboot/initrd-netboot-suse-13.1.i686-2.1.1.packages 348K /srv/netboot/initrd-netboot-suse-13.1.i686-2.1.1.verified 0 /srv/netboot/plymouth.splash.active kiwidebug=1 option does not give debug terminal to get the logs. 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 8

[Bug 845644] New: Clock setting dialog does not recognize HW clock setting
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=845644 https://bugzilla.novell.com/show_bug.cgi?id=845644#c0 Summary: Clock setting dialog does not recognize HW clock setting Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rschweikert(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- When the clock setting dialog initially appears during installation the displayed time is off by the timezone factor. This is observed on real hardware, with the HW clock set to UTC. After toggling the "HW Clock is set to UTC" checkbox off and on the time corrects itself. Expected behavior: Time is correct on initial display -- 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 842359] New: dhcp server on openSUSE 12.3 is broken in 4 different ways at the same time
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=842359 https://bugzilla.novell.com/show_bug.cgi?id=842359#c0 Summary: dhcp server on openSUSE 12.3 is broken in 4 different ways at the same time Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Mathias.Homann(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 The dhcp server included in openSUSE 12.3 is broken in 4 different ways at the same time (see linked bugreports) Reproducible: Always Steps to Reproduce: meta bug Actual Results: meta bug Expected Results: meta bug -- 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