February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1022360] Crash during E-Mail-Server setup, when outgoing mailserver is empty
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1022360 http://bugzilla.suse.com/show_bug.cgi?id=1022360#c3 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jreidinger(a)suse.c | |om) | --- Comment #3 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Peter Varkoly from comment #2) > (In reply to Josef Reidinger from comment #1) > > Peter it looks like caused by your commit > > https://github.com/yast/yast-mail/commit/ > > c80bf3c3ded0c0d5773432cf9faaed5d9c6db4a5 > I hope I've fixed it. > https://github.com/yast/yast-mail/pull/22 approved -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 984982] utf8 console font mismatch
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=984982 http://bugzilla.opensuse.org/show_bug.cgi?id=984982#c6 --- Comment #6 from Ludwig Nussel <lnussel(a)suse.com> --- In Leap and TW it's fixed by switching the default font to eurlatgr. SP3 however didn't dare to switch so far, see https://fate.suse.com/318426. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018371] VUL-0: CVE-2016-10030: slurm: prolog failure vulnerability
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1018371 http://bugzilla.suse.com/show_bug.cgi?id=1018371#c2 --- Comment #2 from Egbert Eich <eich(a)suse.com> --- Updating to 16.05.8.1 will fix this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 957365] New: password input for crypted devices dislays awkwardly
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=957365 Bug ID: 957365 Summary: password input for crypted devices dislays awkwardly Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: rommel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 657927 --> http://bugzilla.suse.com/attachment.cgi?id=657927&action=edit screen on first keystroke With grub_terminal=console in /etc/sysconfig/grub I observed the following: Having crypted partitions mounted at boot time resulted in the password prompt being repeated for every key that I type. Password input succeeds, but this looks really awkward on the console (and might make the other boot messages scroll out of sight). -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 967772] A missing device causes systemd to boot single user mode
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=967772 http://bugzilla.suse.com/show_bug.cgi?id=967772#c5 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Ulrich.Windl(a)rz.uni-regensb | |urg.de Flags| |needinfo?(Ulrich.Windl(a)rz.u | |ni-regensburg.de) --- Comment #5 from Dr. Werner Fink <werner(a)suse.com> --- Do you have solved the problem, e.g. by using nofail as described in man:systemd.mount(5): If nofail is given, this mount will be only wanted, not required, by the local-fs.target. This means that the boot will continue even if this mount point is not mounted successfully. Option fail has the opposite meaning and is the default. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 980923] New: cmus playback fairly slow and stuttering
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=980923 Bug ID: 980923 Summary: cmus playback fairly slow and stuttering Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: maiktapwagner(a)aol.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Dear openSUSE-Team, Current Tumbleweed installation with LXDE here. I am trying to playback audio mp3-Files which in general works great but only using "Videos" (totem). I tried a basic console application called "cmus" and noticed that the sound is stuttering a lot and suffers from lags. mwagner@linux-6s7s:~$ /sbin/lspci | grep Audio 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 02) Could you look into this, please? Regards, Maik -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1023015] New: After update VirtualBox cannot start a some saved snapshots
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1023015 Bug ID: 1023015 Summary: After update VirtualBox cannot start a some saved snapshots Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: neocube216(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Packages after update (Announcement ID: openSUSE-SU-2017:0332-1): # rpm -qa|grep virtualbox virtualbox-5.0.32-34.1.x86_64 virtualbox-host-kmp-default-5.0.32_k4.1.36_44-34.1.x86_64 virtualbox-qt-5.0.32-34.1.x86_64 virtualbox-guest-kmp-default-5.0.32_k4.1.36_44-34.1.x86_64 # uname -a Linux machine 4.1.36-44-default #1 SMP PREEMPT Mon Dec 12 21:24:10 UTC 2016 (b1c0ac2) x86_64 x86_64 x86_64 GNU/Linux Error after start snapshot with Debian 8, opensuse 42.2: The device helper structure version has changed. If you have upgraded VirtualBox recently, please make sure you have terminated all VMs and upgraded any extension packs. If this error persists, try re-installing VirtualBox. (VERR_PDM_DEVHLPR3_VERSION_MISMATCH). Start snapshot with Win XP, another Debian 8 is OK Probably this same error in Ubuntu Bug: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5118097.html -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1021969] New: Any patch applying to both systemd and systemd-sysvinit should have the reboot flag
by bugzilla_noreply＠novell.com 02 Feb '17

02 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1021969 Bug ID: 1021969 Summary: Any patch applying to both systemd and systemd-sysvinit should have the reboot flag Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: All OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- I almost REOPENED bug 1017976, then I remembered that reopening a bug doesn't necessary make it blip on the radar, especially if it was VERIFIED before. Again, a patch applying to both systemd and systemd-sysvinit has been published without the "reboot" flag. This time it is patch openSUSE-2017-150 on the 42.2 Update-OSS repo. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 904015] outlined fonts didn't get their antialias enabled by fontconfig in openSUSE 13.2 and above
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=904015 http://bugzilla.suse.com/show_bug.cgi?id=904015#c44 --- Comment #44 from Simon Lees <simonf.lees(a)suse.com> --- (In reply to Petr Gajdos from comment #42) > Needinfo on me so I do not forgot. I have much to do right now, I'll look > into it later. I'll also try and have a look, mostly as a learning experience, whether I get anywhere before you is another question though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 993643] New: grub config generation uses uuid's and is incompatible with cloning hard drives. Even on identical machines.
by bugzilla_noreply＠novell.com 01 Feb '17

01 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=993643 Bug ID: 993643 Summary: grub config generation uses uuid's and is incompatible with cloning hard drives. Even on identical machines. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: padamsn(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 687995 --> http://bugzilla.opensuse.org/attachment.cgi?id=687995&action=edit grub.cfg With a fresh install of 42.1 on a recent model laptop (Not UEFI) grub.cfg has these lines, which only work on this laptop. If clonezilla is used to replace the hard drive, or clone to a identical laptop. It will not boot due to UUID's being used in grub.cfg (Clonezilla settings, disks-Images, basic/beginner, Restore/save disks, all other default options, Via samba) You can then from the grub console easily find and boot the system, But YaST2 Boot Loader BUG # https://bugzilla.opensuse.org/show_bug.cgi?id=949796 will occur preventing a permanent fix. You can edit the grub.cfg by hand to fix the issue, but given yast2 still crashes on boot loader config, i worry this isn’t a good solution. This bug can be reproduced on identical machines. A set of 4 Identically configured Lenovo X300 Laptops with SSD's were used. ATTACHED grub.cfg If you replace all lines like this... search --no-floppy --fs-uuid --set=root 6ab67475-b1f0-4f91-81ac-0bcb395f4b31 With this line... search --no-floppy --fs-uuid --set=root hd0,msdos2 Everything works for cloning and booting. But if you try to run YaST2 Boot Loader, BUG # https://bugzilla.opensuse.org/show_bug.cgi?id=949796 will occur. SYSTEM Configuration /etc/fstab LABEL=swap swap swap defaults 0 0 LABEL=root / ext4 noatime,acl,user_xattr 1 1 LABEL=home /home ext4 noatime,acl,user_xattr 1 2 fdisk /dev/sda (Print) Disk /dev/sda: 59.6 GiB, 64023257088 bytes, 125045424 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xf38e3fd3 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 8402943 8400896 4G 82 Linux swap / Solaris LABEL=swap /dev/sda2 * 8402944 29382655 20979712 10G 83 Linux LABEL=root /dev/sda3 29382656 125044735 95662080 45.6G 83 Linux LABEL=home ======================== Start /dev/disks On working Origin system. ======================== linux-930q:/dev/disk # ls -R .: by-id by-label by-path by-uuid ./by-id: ata-MATSHITADVD-RAM_UJ-844 scsi-SATA_SAMSUNG_MCCOE64GSE816A6533 ata-SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533 scsi-SATA_SAMSUNG_MCCOE64G_SE816A6533 ata-SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533-part1 scsi-SATA_SAMSUNG_MCCOE64G_SE816A6533-part1 ata-SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533-part2 scsi-SATA_SAMSUNG_MCCOE64GSE816A6533-part1 ata-SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533-part3 scsi-SATA_SAMSUNG_MCCOE64G_SE816A6533-part2 scsi-0ATA_SAMSUNG_MCCOE64G_SE816A6533 scsi-SATA_SAMSUNG_MCCOE64GSE816A6533-part2 scsi-0ATA_SAMSUNG_MCCOE64G_SE816A6533-part1 scsi-SATA_SAMSUNG_MCCOE64G_SE816A6533-part3 scsi-0ATA_SAMSUNG_MCCOE64G_SE816A6533-part2 scsi-SATA_SAMSUNG_MCCOE64GSE816A6533-part3 scsi-0ATA_SAMSUNG_MCCOE64G_SE816A6533-part3 scsi-SATA_SAMSUNG_MCCOE64SE816A6533 scsi-1ATA_SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533 scsi-SATA_SAMSUNG_MCCOE64SE816A6533-part1 scsi-1ATA_SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533-part1 scsi-SATA_SAMSUNG_MCCOE64SE816A6533-part2 scsi-1ATA_SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533-part2 scsi-SATA_SAMSUNG_MCCOE64SE816A6533-part3 scsi-1ATA_SAMSUNG_MCCOE64G8MPP-0VA_SE816A6533-part3 ./by-label: home root swap ./by-path: pci-0000:00:1f.1-ata-1.0 pci-0000:00:1f.2-ata-1.0-part1 pci-0000:00:1f.2-scsi-0:0:0:0 pci-0000:00:1f.2-scsi-0:0:0:0-part3 pci-0000:00:1f.1-scsi-3:0:0:0 pci-0000:00:1f.2-ata-1.0-part2 pci-0000:00:1f.2-scsi-0:0:0:0-part1 pci-0000:00:1f.2-ata-1.0 pci-0000:00:1f.2-ata-1.0-part3 pci-0000:00:1f.2-scsi-0:0:0:0-part2 ./by-uuid: 565fc838-eae8-4b00-854d-4881abea156b 6ab67475-b1f0-4f91-81ac-0bcb395f4b31 6cb9f8ea-7da4-4eb3-80a5-24651095e5f8 ======================== End /dev/disks On working Origin system. ======================== ======================== Start /dev/disks On Cloned Broken System Identical Laptop. ======================== user@linux-930q:/dev/disk> ls -R .: by-id by-label by-path by-uuid ./by-id: ata-MATSHITADVD-RAM_UJ-844 scsi-SATA_SAMSUNG_MMCRE64GSE837B7191 ata-SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191 scsi-SATA_SAMSUNG_MMCRE64G_SE837B7191 ata-SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191-part1 scsi-SATA_SAMSUNG_MMCRE64G_SE837B7191-part1 ata-SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191-part2 scsi-SATA_SAMSUNG_MMCRE64GSE837B7191-part1 ata-SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191-part3 scsi-SATA_SAMSUNG_MMCRE64G_SE837B7191-part2 scsi-0ATA_SAMSUNG_MMCRE64G_SE837B7191 scsi-SATA_SAMSUNG_MMCRE64GSE837B7191-part2 scsi-0ATA_SAMSUNG_MMCRE64G_SE837B7191-part1 scsi-SATA_SAMSUNG_MMCRE64G_SE837B7191-part3 scsi-0ATA_SAMSUNG_MMCRE64G_SE837B7191-part2 scsi-SATA_SAMSUNG_MMCRE64GSE837B7191-part3 scsi-0ATA_SAMSUNG_MMCRE64G_SE837B7191-part3 scsi-SATA_SAMSUNG_MMCRE64SE837B7191 scsi-1ATA_SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191 scsi-SATA_SAMSUNG_MMCRE64SE837B7191-part1 scsi-1ATA_SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191-part1 scsi-SATA_SAMSUNG_MMCRE64SE837B7191-part2 scsi-1ATA_SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191-part2 scsi-SATA_SAMSUNG_MMCRE64SE837B7191-part3 scsi-1ATA_SAMSUNG_MMCRE64G8MPP-0VA_SE837B7191-part3 ./by-label: home root swap ./by-path: pci-0000:00:1f.2-ata-1.0 pci-0000:00:1f.2-ata-1.0-part3 pci-0000:00:1f.2-scsi-0:0:0:0-part1 pci-0000:00:1f.2-scsi-1:0:0:0 pci-0000:00:1f.2-ata-1.0-part1 pci-0000:00:1f.2-ata-2.0 pci-0000:00:1f.2-scsi-0:0:0:0-part2 pci-0000:00:1f.2-ata-1.0-part2 pci-0000:00:1f.2-scsi-0:0:0:0 pci-0000:00:1f.2-scsi-0:0:0:0-part3 ./by-uuid: 565fc838-eae8-4b00-854d-4881abea156b 6ab67475-b1f0-4f91-81ac-0bcb395f4b31 6cb9f8ea-7da4-4eb3-80a5-24651095e5f8 ======================== End /dev/disks On Cloned Broken System Identical Laptop. ======================== YaST2 PARTITIONER I have set mount by to device ID. This causes the yast2 boot loader config to keep a setting of /dev/sda for the boot drive. But this setting has no effect on how the grub.cfg is generated. If you use volume label as the mount by, then the boot drive changes to /dev/disk/by-id/msdos which is bogus and will never save. POSSIBLE SOLUTIONS Write /etc/grub.d/10-linux.cfg so the generated grub.cfg trys UUID first, (hd) paths 2nd, Labels 3rd ..... Make YaST2 Bootloader prefer disk Lables if they are set, and, add a option to change the preferred method for finding drives in grub. If disk labels were initialized every time on install to a random value + mount name. then they might be a more reliable way to go for mounting and booting. -- You are receiving this mail because: You are on the CC list for the bug.

1 1