December 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 894084] Kernel:HEAD/kernel-desktop update useless forces updating crda and wireless-regdb
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=894084 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johannesobermayr(a)gmx.de Flags| |needinfo?(johannesobermayr@ | |gmx.de) --- Comment #4 from Lukas Ocilka <locilka(a)suse.com> --- Please follow this howto and attach yast logs including solver testcase https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_want_to_report_a_bug_r… (Extras/Generate_Dependency_Resolver_Test_Case) Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907614] Named not showing up in services manager until started
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=907614 --- Comment #3 from Bob Goddard <suse-20050616(a)bgcomp.co.uk> --- Sorry, using systemctl shows that they do exist, else I would not have been able to start them. Remember, they are not listed in yast until I actually use systemctl to start/enable them. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907614] Named not showing up in services manager until started
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=907614 --- Comment #2 from Bob Goddard <suse-20050616(a)bgcomp.co.uk> --- Yes, I checked for named. In fact there seems to be quite a few services missing. All the quagga ones were not listed in yast until started/enabled. There were other, but I never took a note of them. -- 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 #2 from Matwey Kornilov <matwey.kornilov(a)gmail.com> --- (In reply to Richard Biener from comment #1) > Did you try using g++-4.9 from the gcc49-c++ package? No I did not, because Factory uses gcc 4.8 as default now, and gcc 4.9 would not solve the problem. -- 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 #1 from Richard Biener <rguenther(a)suse.com> --- Also takes ages to compile because of the gigantic switch stmt. Trying to reproduce with a cross compiler from x86_64. Did you try using g++-4.9 from the gcc49-c++ package? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907457] New: perl-bootloader: pbl-8400.2 Core::GRUB2::GrubDev2UnixDev.252: Error: did not find a match for hd0 in the device map
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.opensuse.org/show_bug.cgi?id=907457 Bug ID: 907457 Summary: perl-bootloader: pbl-8400.2 Core::GRUB2::GrubDev2UnixDev.252: Error: did not find a match for hd0 in the device map Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: snwint(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 615222 --> http://bugzilla.opensuse.org/attachment.cgi?id=615222&action=edit pbl.log When updating openSUSE-Factory, following error appears: pbl-8400.2 Core::GRUB2::GrubDev2UnixDev.252: Error: did not find a match for hd0 in the device map Error however seems to be harmless. # cat /boot/grub2/device.map (hd1) /dev/sda # cat /boot/grub2/device.map.old (hd1) /dev/sda (hd0) /dev/sdb (hd2) /dev/sdc -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 907715] Predictable iSCSI device links are not being created any more in /dev/disks/by-path
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=907715 --- Comment #2 from Dr. Werner Fink <werner(a)suse.com> --- The patch/commit is already part of factory: 1063-udev-path_id-suppress-ID_PATH-for-devices-with-an-un.patch I have only not enabled it for 13.2 nor SLES12 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 904534] [libyui-gtk] Stage2 of autoyast does not work
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=904534 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |bnc-team-gnome(a)forge.provo. | |novell.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 904534] [libyui-gtk] Stage2 of autoyast does not work
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=904534 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|AutoYaST |GNOME -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 906201] System Services module seems broken
by bugzilla_noreply＠novell.com 02 Dec '14

02 Dec '14

http://bugzilla.suse.com/show_bug.cgi?id=906201 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(roger.luedecke@gm | |ail.com) --- Comment #5 from Lukas Ocilka <locilka(a)suse.com> --- Roger, we need these Yast logs including debug logs, how this can be done is described here: https://en.opensuse.org/openSUSE:Report_a_YaST_bug#The_y2logs_don.27t_seem_… shorter version: On a commandline (xterm, konsole, etc.) su - Y2DEBUG=1 yast2 services-manager Anyway, Yast uses systemctl to get list of services and their details: systemctl show ${service_name} systemctl status ${service_name} If systemctl already shows wrong info, then systemctl or the service itself is to blame, not Yast. -- You are receiving this mail because: You are on the CC list for the bug.

1 0