December 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 906990] Add "Boot Linux" to installation media
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=906990 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint(a)suse.com --- Comment #3 from Lukas Ocilka <locilka(a)suse.com> --- Anyway, it's definitely a feature and belongs to FATE (openFATE), hard to tell if it's possible at all though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 906990] Add "Boot Linux" to installation media
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=906990 --- Comment #2 from Lukas Ocilka <locilka(a)suse.com> --- Yast and GRUB are two different things, Yast can find other systems but it cannot boot them. On the other hand, broken GRUB can't find systems and cannot offer to boot them. Additionally, the install media (Linuxrc) offer to boot from disk (installed systems), but it only tries to load the installed bootloader (GRUB in some cases). So, I'm afraid this is not possible with the tools we have now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907965] New: boot option in kde menus is permanent
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.opensuse.org/show_bug.cgi?id=907965 Bug ID: 907965 Summary: boot option in kde menus is permanent Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jdd(a)dodin.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- sorry, I don't know how to classify this, buts it's very annoying. I had the same problem years ago, may I'm the only one to use this option :-). The bug is critical only if you use the option. I speak of the ability to choose the next starting system directly from the close menu in kde4 or kdm, here in 13.2. In fact the choice is not for the next reboot, but permanent. In my case, I choosed to start the old 13.1, and the computer started then 13.1 with no other choice, at any reboot. It became impossible to boot any other system. One can just see the upper left flashing "grub" starting message. To fix this, I had to go to the bios start menu, choose the other disk 13.1 is installed in to get the 13.1 menu (for what ever reason 13.1 do not see 13.2 boot), enter the grub console, load the kernel, the initrd and then I could bring up the 13.2 standard boot, and in kdm choose the "opensuse" normal option. This seems to reset the system to normal working state (I hope so :-). The problem sits somewhere in the grub2 config file. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 792309] systemd: Apache2 fails to start (timeout) at boot when mod_ssl enabled
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=792309 --- Comment #6 from Kristyna Streitova <kstreitova(a)suse.com> --- Thank you, I will prepare an update. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902067] Yast2 Live Installer has no icon in Gnome
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=902067 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjharms(a)gmail.com Flags| |needinfo?(sjharms(a)gmail.com | |) --- Comment #3 from Lukas Ocilka <locilka(a)suse.com> --- And does it have any icon in KDE? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 893270] [yast2-apparmor] Removal of Functional Aspect to Create an AppArmor Profile by Self Learning an Application Execution
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=893270 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #7 from Lukas Ocilka <locilka(a)suse.com> --- Scott, let me explain the Yast AppArmor case: This "Yast module", although it might look like a common Yast module, just a little bit weird, has been developer by Immunix guys. Those guys who wrote the whole AppArmor. After a few years, all of them left the company, but Yast AppArmor was still here, rotting. The current code is written around technology that nobody in Yast team understands in a way that nobody in Yast team is able to maintain. The fact, that it's "Yast" doesn't make the Yast team responsible for it. If you yourself developed and maintained some open-source app for GNOME and then you lost your interest, would that make GNOME responsible for that app? Obviously not. We haven't dropped the module, but we've removed some functionality that nobody was able to maintain. Yast team is not a big team, we cannot do everything. Other open source projects have external contributions, we have had just a few. If anyone is willing to take this over, then we'll gladly hand it over to them. If you know someone, please reopen this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 856391] grub2-reboot sets default boot entry permanently
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.opensuse.org/show_bug.cgi?id=856391 Wolfgang Bauer <wbauer(a)tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdd(a)dodin.org --- Comment #16 from Wolfgang Bauer <wbauer(a)tmo.at> --- *** Bug 907965 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907796] gcc: internal compiler error
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=907796 --- Comment #4 from Richard Biener <rguenther(a)suse.com> --- Btw, a cross-cc1plus needs -O -fPIC -fstack-protector -fomit-frame-pointer (maybe). For the fun of it I'm trying to reduce the testcase (but I don't expect much success here). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 850656] New: Trying to add a remote Samba printer gets 'lpadmin: Bad device-uri scheme "smb".'
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

https://bugzilla.novell.com/show_bug.cgi?id=850656 https://bugzilla.novell.com/show_bug.cgi?id=850656#c0 Summary: Trying to add a remote Samba printer gets 'lpadmin: Bad device-uri scheme "smb".' Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i686 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: siftspam-dev(a)fpchico.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 On RC2, I tried to add a remote Samba printer using Yast2 and CUPS, but it always failed with the error 'lpadmin: Bad device-uri scheme "smb". The remote printer is served by a Seagate GoFlex Home Samba Server. There is no problem adding and using the same SMB printer from openSUSE 12.3 (and Win/XP) clients. I found this problem and a workaround discussed on the French and English forums. Here's a post from the English forum summarizing the problem and workaround: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta… As this post puts it, "For some reason samba-client doesn't create the symbolic link to smbspool in /usr/lib/cups/backend/smb." The workaround is to create the symlink manually. No one else seems to have reported this problem; but, I thought you'd want to know. Reproducible: Always Steps to Reproduce: Try to add a remote Samba printer using Yast2's "Add a New Printer Configuration" 1. Enter printer information 2. Click [OK] button Actual Results: Printer is not added. Error: lpadmin: Bad device-uri scheme "smb" Expected Results: Printer added successfully Not sure if the problem is related to the type or version of the SMB printer server. IIRC, the Seagate GoFlex Home is running Samba version 3.0??, but not I'm not certain. Sorry, I don't have access to the GoFlex now, to verify the version number. As soon as I have access, I'll post the full version number. -- 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 907796] gcc: internal compiler error
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.novell.com/show_bug.cgi?id=907796 --- Comment #3 from Richard Biener <rguenther(a)suse.com> --- Ok, so this is triggered by -fstack-protector and the patch we have on the branch for its support. gen/wxe_funcs.cpp:31754:2: internal compiler error: in gen_add2_insn, at optabs.c:4713 0x9f8f8b gen_add2_insn(rtx_def*, rtx_def*) /space/rguenther/src/svn/gcc-4_8-branch/gcc/optabs.c:4713 0xa4ce68 gen_reload /space/rguenther/src/svn/gcc-4_8-branch/gcc/reload1.c:8638 0x522640 emit_input_reload_insns /space/rguenther/src/svn/gcc-4_8-branch/gcc/reload1.c:7594 0x522640 do_input_reload /space/rguenther/src/svn/gcc-4_8-branch/gcc/reload1.c:7880 0x522640 emit_reload_insns /space/rguenther/src/svn/gcc-4_8-branch/gcc/reload1.c:8072 0x522640 reload_as_needed /space/rguenther/src/svn/gcc-4_8-branch/gcc/reload1.c:4648 0xa51dcf reload(rtx_def*, int) /space/rguenther/src/svn/gcc-4_8-branch/gcc/reload1.c:1054 0x983c1b do_reload /space/rguenther/src/svn/gcc-4_8-branch/gcc/ira.c:4679 0x983c1b rest_of_handle_reload /space/rguenther/src/svn/gcc-4_8-branch/gcc/ira.c:4791 it also needs reload (the 4.9 branch uses LRA by default but still supports reload via -mno-lra which is where the 4.9 branch shows the same bug, on trunk -mno-lra runs into walls way earlier). It runs into the very very fallback /* If that failed, copy the address register to the reload register. Then add the constant to the reload register. */ gcc_assert (!reg_overlap_mentioned_p (out, op0)); gen_reload (out, op1, opnum, type); insn = emit_insn (gen_add2_insn (out, op0)); set_dst_reg_note (insn, REG_EQUIV, in, out); trying to get a (plus (reg:DI 8 x8) (mem/u/c:DI (symbol_ref/u:DI ("*.LC207") [flags 0x2]) [0 S8 A64])) generated which is exactly 'in' (thus what we wanted to reload). Micha? -- You are receiving this mail because: You are on the CC list for the bug.

1 0