November 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 781204] New: lastlog command is missing
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=781204 https://bugzilla.novell.com/show_bug.cgi?id=781204#c0 Summary: lastlog command is missing Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: thomas(a)suse.com QAContact: qa-bugs(a)suse.de CC: draht(a)suse.com, security-team(a)suse.de Found By: --- Blocker: --- Since 12.2 the lastlog command is missing. The lastlog is very useful for system security and is a de factot standard in the unix world. Please add it again to Factory and 12.2. -- 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 7

[Bug 786714] New: systemd documentation issue: serial console
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=786714 https://bugzilla.novell.com/show_bug.cgi?id=786714#c0 Summary: systemd documentation issue: serial console Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: aj(a)suse.com ReportedBy: ro(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- as we just talked about it: up to now I still have not seen a machine/VM running with systemd that has a serial console properly set up, so it's either incredibly hard or not documented in a way that people do it ... sysvinit case: - you do it for the bootloader and probably in the same file for the kernel commandline - you probably adapt etc/sysconfig/bootloader to match the above - you modify inittab to properly set the serial console getty - you configure etc/securetty adding ttyS0 (or xvc0 in xen) to allow root login on the serial console which steps are needed in a factory (or future sles12 environment) ? -- 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 729796] New: mdns reenabled during upgrade
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=729796 https://bugzilla.novell.com/show_bug.cgi?id=729796#c0 Summary: mdns reenabled during upgrade Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hamann.w(a)t-online.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040113 upgrade installation (from 11.4 to 12.1 - same happened when upgrading to 11.4) activates avahi-daemon and modifies /etc/nsswitch.conf to use mdns-minimal Reproducible: Always Steps to Reproduce: 1. insert installation media, choose upgrade .... 2. 3. Actual Results: after installation avahi was active, and .local resolution used mdns Since the remainder of the network uses port 53 dns, local name resolution failed Expected Results: preserve old settings. There are very few reasons why one would have turned off mdns. These include a) existing network with .local name scheme b) no network at all (just a single computer connected to the internet) c) incompatible hardware on an existing network (e.g. printers and telephones that respond to mdns but do not allow setting of meaningful names) Neither of these reasons can be expected to change by upgrading a system May I also add a suggestion for enhancement: during a fresh install there is a warning against using .local domain. Could there be an option to disable mdns or a link to instructions? -- 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 848663] New: no memtest available to chose before installation (.iso written to usb key)?, 13.1/rc2/x64
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848663 https://bugzilla.novell.com/show_bug.cgi?id=848663#c0 Summary: no memtest available to chose before installation (.iso written to usb key)?, 13.1/rc2/x64 Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: abittner(a)abittner.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 I was wondering if there was really no memtest bootoption being available early before actual install as in the past with opensuse? I was using .iso image of 13.1/rc2/x64 from an usb-key. All I could select was install? Maybe this gotta do something with classic bios mode and efi mode of install, I am actually not that sure any more. Is there no memtest from the efi style to boot the .iso media? Reproducible: Didn't try 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 6

[Bug 804160] New: Boot menu entry "Check Installation Media" doesn't work
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=804160 https://bugzilla.novell.com/show_bug.cgi?id=804160#c0 Summary: Boot menu entry "Check Installation Media" doesn't work Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdelvare(a)suse.com QAContact: jsrain(a)suse.com Found By: Community User Blocker: --- Booting on the Gnome Live CD of openSUSE 12.3 RC1/x86_64, if I select Check Installation Media in the boot menu, it doesn't work. It seems to boot as when staring the Gnome Live system, but the wait screen is displayed forever. At some point (10 minutes), I got tired waiting, switched to the first console (Ctrl+Alt+F1) and typed "Enter". It unstuck the boot process and after a few minutes I could see the regular Gnome desktop of the Live system. I couldn't see any error message, but if you tell me where to look, I can check again. As a side note, I don't quite see the value of this boot menu entry. Checking the installation media is one of the many things which can be achieved from the Live system (which is what I ended up doing.) So if we can't fix the boot menu entry, I'd rather just remove it. -- 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 25

[Bug 848700] New: Network connection doesn't work
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848700 https://bugzilla.novell.com/show_bug.cgi?id=848700#c0 Summary: Network connection doesn't work Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: i686 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: hkaustin(a)luukku.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Opensuse 13.1 installation goes smoothly but doesn't recognize my internet connection. I have to give systemctl commands to make the internet connection to work. Reproducible: Always Steps to Reproduce: 1.Try to install openSUSE 13,1 2. 3. Actual Results: Doesn't recognize my internet connection. Expected Results: It should recognize that. Every other ubuntu-based distro does that. I would very much like to help you to fix this problem. -- 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 841451] "rcnetwork stop" has an incomplete effect
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=841451 https://bugzilla.novell.com/show_bug.cgi?id=841451#c2 Marius Tomaschewski <mt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mt(a)suse.com |os.gnome.maintainers@gmail. | |com --- Comment #2 from Marius Tomaschewski <mt(a)suse.com> 2013-11-07 11:36:47 UTC --- "rcnetwork stop" just forwards to "systemctl stop network.service", calling "systemctl stops NetworkManager.service" via the alias link. Anything else is in the responsibility of NetworkManager.service. -- 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 0

[Bug 849274] New: The installer loads disk partitions too early
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=849274 https://bugzilla.novell.com/show_bug.cgi?id=849274#c0 Summary: The installer loads disk partitions too early Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mustafaa1987(a)yahoo.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 I think the installer loads disk partitions too early, after I opened the installer (and before the partitioning), I opened gparted and changed the partitions, after closing gparted and getting back to the installation, proceeding to the partitioning step gave me the same old layout, and that caused some error. Reproducible: Always Steps to Reproduce: 1. Start the installer 2. open gparted and change the partition layout and apply changes and close it 3. Proceed to the partitioning step of the installer Actual Results: The installer loads the old partition layout Expected Results: The installer loads the current partition layout I think loading disk info must be in the start of partitioning step -- 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 843718] kiwi: missing patch: use kpartx sync mode to make sure devices are created
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843718 https://bugzilla.novell.com/show_bug.cgi?id=843718#c16 Marcus Schaefer <ms(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms(a)suse.com |adrian(a)suse.com --- Comment #16 from Marcus Schaefer <ms(a)suse.com> 2013-11-07 10:00:52 UTC --- in reply to comment #14 I agree to what Rudi said about the tools which should create the device nodes. With regards to LVM the situation is that udev and the device-mapper creates devices. The one from the device mapper appear all in /dev/mapper/... the one udev creates are in /dev/... the schema of both is different and from the use of the device mapper created devices I was discouraged because people told me udev is the way to go. That's the reason why kiwi uses the devices udev creates and those devices are also used if I install a system with yast + lvm I'm not sure but I think if you run tools which creates device nodes under linux these days they mostly use udev and our entire distribution would fail if we don't start udev as the very first task in the initrd Thus we can complain about the use of udev and how much pain it still cause but we also have decided that SUSE uses udev and I think with regards to this a buildservice VM should also be able to cope with udev in the same way a standard system would do it I also would love if the bs worker kernel is not different from the distro kernel in the Studio project we use containment systems which are also simple JeOS VM's building inside them does not outline any lvm device node issues. I think I can't do much with this bug, thus assigning to the buildservice space hope that's ok -- 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 0

[Bug 807098] New: rescue environment has no tools to handle GPT partitions - needs gptfdisk, at least.
by bugzilla_noreply＠novell.com 07 Nov '13

07 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=807098 https://bugzilla.novell.com/show_bug.cgi?id=807098#c0 Summary: rescue environment has no tools to handle GPT partitions - needs gptfdisk, at least. Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 The rescue environment has no tools to handle GPT partitions - needs gptfdisk, at least.. 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