November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1110412] Color Emoji support is disabled by Noto Emoji (monochrome) and DejaVu fonts
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1110412 http://bugzilla.suse.com/show_bug.cgi?id=1110412#c11 --- Comment #11 from Yunhe Guo <i(a)guoyunhe.me> --- Correct previous comment: openSUSE provided a configuration with higher priority (60-family-prefer.conf) than fontconfig (61-latin.conf). In openSUSE's 60-family-prefer.conf DejaVu Sans has been removed from sans-serif list. And I tested if only install Noto Color Emoji and DejaVu fonts, Chromium and Firefox can render almost all Emoji correctly (except several common symbols). Tested web pages: https://en.wikipedia.org/wiki/Emoji https://getemoji.com/ However, KDE/Qt applications, like Konversation, KAddressbook, still use some DejaVu monochrome symbols. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1113894] [Staging] Virtualbox fails to build against puthon 3.7
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1113894 http://bugzilla.suse.com/show_bug.cgi?id=1113894#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1113894) was mentioned in https://build.opensuse.org/request/show/646211 Factory / virtualbox -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1112097] VUL-0: virtualbox: October 2018 release, multiple vulnerabilities
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1112097 http://bugzilla.suse.com/show_bug.cgi?id=1112097#c7 --- Comment #7 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1112097) was mentioned in https://build.opensuse.org/request/show/646211 Factory / virtualbox -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1110412] Color Emoji support is disabled by Noto Emoji (monochrome) and DejaVu fonts
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1110412 http://bugzilla.suse.com/show_bug.cgi?id=1110412#c10 --- Comment #10 from Yunhe Guo <i(a)guoyunhe.me> --- (In reply to Petr Gajdos from comment #8) > Apologize, I just do not understand why a program do not use a font returned > by `fc-match emoji`. Removing a font from a preference lists for > monospace/sans/sans-serif feels more like a workaround to me, but I am > probably missing something. The result of `fc-match emoji` is correct. But it seems not working in any actual applications. Applications still got DejaVu Sans, rather than emoji fonts. I looked deeper into all system fontconfig files and found that DejaVu fonts have a super high priority: https://gitlab.freedesktop.org/fontconfig/fontconfig/blob/master/conf.d/60-… I deleted this line manually and everything works well. It seems fontconfig will first look at latin fonts, and then look for emoji if nothing provide the font. But if some latin fonts have provided it, then it use the latin font to render the emoji. I don't know why fontconfig ships a default font list like this. It is out-dated and doesn't match openSUSE's configuration there https://github.com/openSUSE/fonts-config We already have a font family matching configuration, which is very nicely designed for modern desktop. So we don't need to do anything with dejavu-fonts package. We just need to disable the 60-latin.conf configuration by removing symlink. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1113151] Out of date package: openSUSE:Factory/libisoburn is out of date
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1113151 http://bugzilla.suse.com/show_bug.cgi?id=1113151#c1 Asterios Dramis <asterios.dramis(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #1 from Asterios Dramis <asterios.dramis(a)gmail.com> --- Update submitted. See: https://build.opensuse.org/request/show/646179 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114573] New: Expand libyui to support setting YImage from icon theme
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114573 Bug ID: 1114573 Summary: Expand libyui to support setting YImage from icon theme Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: hellcp(a)mailbox.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- YImage is commonly used to display icons, both qt and gtk support setting images from icon themes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 900558] New: Impossible to boot in single user mode with root mounted read only
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=900558 Bug ID: 900558 Summary: Impossible to boot in single user mode with root mounted read only Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: archie(a)dellroad.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a 13.1 system with all the latest updates as of today and it is spitting out the UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY message for the root filesystem, and then booting normally with root mounted root read-write. First of all, I would expect it to not boot normally in this case, but whatever. Anyway, when I try to do what it says, it's impossible! Here's why: even though I reboot with "single ro" on the boot line and it does in fact go into single user mode, it still mounts root read-write (after complaining of the same fsck errors). Since the 1980's single user mode has always left root mounted read-only so you can run fsck if needed, and you can always remount it read-write if you want. Why did this change? Of course "mount -o remount,ro /" doesn't work. Because root is mounted read-write and it's impossible to get the system to boot with root mounted read-only, then even in single user mode, it's impossible to run fsck and fix the problem. So it's impossible to resolve this problem without the use of a rescue disk. Please fix, this is a bad dead-end people can fall into. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1114568] New: Brightness slider don't working on GNOME with 1060 6GB GPU.
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114568 Bug ID: 1114568 Summary: Brightness slider don't working on GNOME with 1060 6GB GPU. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: RLFontan(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The brightness slider, and even the energy section on GNOME settings from Leap 15.0 are not working by default on my NVIDIA 1060 6GB GPU. I tried to use the xbacklight program from terminal, and its not working at all as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114567] New: ceph-volume: memoryview: a bytes-like object is required, not 'str'
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114567 Bug ID: 1114567 Summary: ceph-volume: memoryview: a bytes-like object is required, not 'str' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: All OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: marcos.souza.org(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ceph-volume has a problem to create an OSD: CEPH_VOLUME_DEBUG=1 ceph-volume lvm create --data /dev/sdb Running command: /usr/bin/ceph-authtool --gen-print-key Running command: /usr/bin/ceph --cluster ceph --name client.bootstrap-osd --keyring /var/lib/ceph/bootstrap-osd/ceph.keyring -i - osd new 1acafc42-c63c-4e8d-b4cb-b454b35c5293 Traceback (most recent call last): File "/usr/sbin/ceph-volume", line 6, in <module> main.Volume() File "/usr/lib/python3.6/site-packages/ceph_volume/main.py", line 37, in __init__ self.main(self.argv) File "/usr/lib/python3.6/site-packages/ceph_volume/decorators.py", line 59, in newfunc return f(*a, **kw) File "/usr/lib/python3.6/site-packages/ceph_volume/main.py", line 153, in main terminal.dispatch(self.mapper, subcommand_args) File "/usr/lib/python3.6/site-packages/ceph_volume/terminal.py", line 182, in dispatch instance.main() File "/usr/lib/python3.6/site-packages/ceph_volume/devices/lvm/main.py", line 38, in main terminal.dispatch(self.mapper, self.argv) File "/usr/lib/python3.6/site-packages/ceph_volume/terminal.py", line 182, in dispatch instance.main() File "/usr/lib/python3.6/site-packages/ceph_volume/devices/lvm/create.py", line 69, in main self.create(args) File "/usr/lib/python3.6/site-packages/ceph_volume/decorators.py", line 16, in is_root return func(*a, **kw) File "/usr/lib/python3.6/site-packages/ceph_volume/devices/lvm/create.py", line 26, in create prepare_step.safe_prepare(args) File "/usr/lib/python3.6/site-packages/ceph_volume/devices/lvm/prepare.py", line 216, in safe_prepare self.prepare(args) File "/usr/lib/python3.6/site-packages/ceph_volume/decorators.py", line 16, in is_root return func(*a, **kw) File "/usr/lib/python3.6/site-packages/ceph_volume/devices/lvm/prepare.py", line 245, in prepare self.osd_id = prepare_utils.create_id(osd_fsid, json.dumps(secrets), osd_id=args.osd_id) File "/usr/lib/python3.6/site-packages/ceph_volume/util/prepare.py", line 72, in create_id show_command=True File "/usr/lib/python3.6/site-packages/ceph_volume/process.py", line 201, in call stdout_stream, stderr_stream = process.communicate(stdin) File "/usr/lib64/python3.6/subprocess.py", line 843, in communicate stdout, stderr = self._communicate(input, endtime, timeout) File "/usr/lib64/python3.6/subprocess.py", line 1499, in _communicate input_view = memoryview(self._input) TypeError: memoryview: a bytes-like object is required, not 'str' This error was fixed in ceph-osd 13.2.2 [1] as per this tracker issue[2]. Opensuse Leap 15.0 still has ceph-osd version 13.0.2: Information for package ceph-osd: --------------------------------- Repository : openSUSE-Leap-15.0-1 Name : ceph-osd Version : 13.0.2.1874+ge31585919b-lp150.1.2 Arch : x86_64 Vendor : openSUSE Installed Size : 41.7 MiB Installed : Yes (automatically) Status : up-to-date Source package : ceph-13.0.2.1874+ge31585919b-lp150.1.2.src Summary : Ceph Object Storage Daemon Description : ceph-osd is the object storage daemon for the Ceph distributed file system. It is responsible for storing objects on a local file system and providing access to them over the network. Would be possible to upgrade the ceph-osd package in order to have this bug fixed? [1]: https://github.com/ceph/ceph/pull/23239 [2]: https://tracker.ceph.com/issues/24993 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1055834] [FAILED] Failed to start Setup Virtual Console.
by bugzilla_noreply＠novell.com 03 Nov '18

03 Nov '18

http://bugzilla.novell.com/show_bug.cgi?id=1055834 http://bugzilla.novell.com/show_bug.cgi?id=1055834#c130 --- Comment #130 from Frank Kruger <fkrueger(a)mailbox.org> --- Updating to dracut-044.1-49.4.x86_64 from https://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/ with the alleged fix (https://build.opensuse.org/request/show/645917) I am getting the following error messages while rebooting: -- [FAILED] Failed to start Setup Virtual Console See 'systemctl status systemd-vconsole-setup.service' for details [DEPEND] Dependency failed for dracut ask for additional cmdline parameters Starting dracut cmdline hook... -- Anyone else seeing this? Any idea? Thx. -- You are receiving this mail because: You are on the CC list for the bug.

1 0