September 2018 - openSUSE Bugs - openSUSE Mailing Lists

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

05 Sep '18

http://bugzilla.suse.com/show_bug.cgi?id=1055834 http://bugzilla.suse.com/show_bug.cgi?id=1055834#c97 --- Comment #97 from Franck Bui <fbui(a)suse.com> --- (In reply to Franck Bui from comment #86) > I'll create a new upstream bug as it should be treated independently I think. FTR it's there: https://github.com/systemd/systemd/issues/10019 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1104833] Initramfs unpacking failed: junk in compressed archive
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.suse.com/show_bug.cgi?id=1104833 http://bugzilla.suse.com/show_bug.cgi?id=1104833#c10 --- Comment #10 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- More tests on Raspberry Pi 2 (armv7): * kernel-lpae 4.17.14 and 4.18.5 are booting fine * kernel-default 4.17.14 and 4.18.5 are broken * kernel-default 4.12.14 (taken from leap) does boot So, this is definitely kernel related. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1105992] Transactional-Update broken in snapshot 20180824
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.suse.com/show_bug.cgi?id=1105992 http://bugzilla.suse.com/show_bug.cgi?id=1105992#c8 --- Comment #8 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Christian Boltz from comment #7) > Just curious - do you parse the _text_ output of zypper? Of course not. > Using zypper --xmlout might be a better / more robust solution ;-) That's what we do and this output has changed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1104642] New: sddm hangs/waits forever after PW entered, after upgrade to OpenSuse-2018-862
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1104642 Bug ID: 1104642 Summary: sddm hangs/waits forever after PW entered, after upgrade to OpenSuse-2018-862 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: michaelof(a)rocketmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I received an update for sddm - OpenSuse-2018-862. After install, and reboot, no login into plasma possible, anymore. System boots, sddm starts, passwort is entered, login button clicked/return pressed: Hangs/waits forever. System itself runs fine, virtual consoles are available. started yast and fell back to sddm 0.17.0-lp150.8.1 from repo OSS, login fine again. Reproducible always on my box. Does NOT happen on my wife's laptop. Please advice if you need any specific logs etc. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1107313] New: Update applet: Your system is offline
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1107313 Bug ID: 1107313 Summary: Update applet: Your system is offline Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: I login to Plasma 5. I check the update applet in the tray. It is always in the hidden tray. When I move the mouse pointer over the update icon, it says "Your system is offline. However, the system is not offline, and updating with "zypper" works fine. I'll note that this is not seriously important to me, since I normally use "zypper dup" to update. But it seems to be a bug. NOTES: (1) The system where I am seeing this is a KVM virtual machine (host system is Leap 15.0). The update applet seems to work properly on another system where Tumbleweed is installed on the physical machine. So it looks to be a VM only issue. (2) This is relatively recent. The update applet was working in July. I'm not sure which snapshot broke it. (3) The Gnome update applet seems to be working properly (on the same VM). So this does not appear to be a "packagekit" issue. It looks like a Plasma5 issue. (4) The problem occurs with either "wicked" or "NetworkManager". I have tried both, and see the same problem either way. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1100155] LXQt themes - No contrast for icons on Desktop
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.suse.com/show_bug.cgi?id=1100155 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvetter(a)suse.com Assignee|andrea(a)opensuse.org |mvetter(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084751] LEAP 15 - LXQt session - LXCC icons not appearing
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.suse.com/show_bug.cgi?id=1084751 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvetter(a)suse.com Assignee|andrea(a)opensuse.org |mvetter(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1106850] xfig crashes if noto-sans-cjk-fonts are installed
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.suse.com/show_bug.cgi?id=1106850 http://bugzilla.suse.com/show_bug.cgi?id=1106850#c26 --- Comment #26 from Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- (In reply to Stefan Dirsch from comment #24) > Well, fonts-config doesn't rewrite fonts.scale/fonts.dir by default since it > takes ages to regenerate them for each font package, which is being > installed. It is done, if you specify "-f" though. > > I'm sure we're going to create blocker bugs with Prio 1, if we change this > default. Maybe one can change the default once a program like xfig, which > uses X11 core fonts, is installed. So only these customers are affected by > this change. Sorry, no better idea .. > > Unfortunately SUSEconfig{,.fonts} is dead ... In general, the lazy creation of the fonts.scale etc should already be handled by the posttrans trigger in the various font packages. - if mkfontdir/mkfontscale is installed, the fonts-config script creates the files - if not, only fontconfig caches are renewed. *If* a program/package requires core fonts, it should depend on mkfontscale and xorg-x11-fonts-core. The latter is required for the encodings, the former for processing it. The dependency on the encodings could also be transitive via mkfontscale. Currently it is possible to deinstall mkfontdir/mkfontscale, even when e.g. xfig is installed. This way only installations actually using core fonts pay for it. Unfortunately, the default installations contain xterm, which defaults to core fonts, although compiled with truetype support via fontconfig/freetype. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1106635] New: DRM radeon GPU fault detected (gem object lookup failed)
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1106635 Bug ID: 1106635 Summary: DRM radeon GPU fault detected (gem object lookup failed) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: egdfree(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After plug two monitor in DisplayPort i see this errors in dmesg (second monitor connected in HDMI): kernel: [drm:radeon_cs_parser_relocs [radeon]] *ERROR* gem object lookup failed 0xa kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to parse relocation -2! kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ec35014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105B76 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03050014 kernel: VM fault (0x04, vmid 1) at page 1071990, write from CB (80) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0e835014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105B57 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014 kernel: VM fault (0x04, vmid 1) at page 1071959, write from CB (16) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ee36014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105C3E kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020014 kernel: VM fault (0x04, vmid 1) at page 1072190, write from CB (32) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ec36014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105CC0 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014 kernel: VM fault (0x04, vmid 1) at page 1072320, write from CB (16) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ee35014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105D36 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060014 kernel: VM fault (0x04, vmid 1) at page 1072438, write from CB (96) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0e836014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105D9C kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03050014 kernel: VM fault (0x04, vmid 1) at page 1072540, write from CB (80) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0ea35014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105E12 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014 kernel: VM fault (0x04, vmid 1) at page 1072658, write from CB (16) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07435014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105B38 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014 kernel: VM fault (0x04, vmid 1) at page 1071928, write from CB (16) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07035014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105BA3 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014 kernel: VM fault (0x04, vmid 1) at page 1072035, write from CB (16) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07035014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105C26 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060014 kernel: VM fault (0x04, vmid 1) at page 1072166, write from CB (96) kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x07236014 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00105C23 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020014 installed: kernel-default-4.18.5-1.6.x86_64 libdrm_radeon1-32bit-2.4.93-1.1.x86_64 libdrm_amdgpu1-2.4.93-1.1.x86_64 libdrm_nouveau2-2.4.93-1.1.x86_64 libva-drm2-2.2.0-1.1.x86_64 libdrm_nouveau2-32bit-2.4.93-1.1.x86_64 libdrm2-2.4.93-1.1.x86_64 libdrm_intel1-32bit-2.4.93-1.1.x86_64 libdrm_intel1-2.4.93-1.1.x86_64 libdrm_radeon1-2.4.93-1.1.x86_64 libdrm2-32bit-2.4.93-1.1.x86_64 libdrm_amdgpu1-32bit-2.4.93-1.1.x86_64 libdrm-devel-2.4.93-1.1.x86_64 Mesa-libGLESv2-2-18.1.6-207.1.x86_64 Mesa-dri-32bit-18.1.6-205.1.x86_64 libOSMesa8-18.1.6-207.1.x86_64 Mesa-libva-18.1.6-207.1.x86_64 Mesa-libEGL1-18.1.6-207.1.x86_64 Mesa-gallium-18.1.6-207.1.x86_64 Mesa-libEGL-devel-18.1.6-207.1.x86_64 Mesa-libEGL1-32bit-18.1.6-207.1.x86_64 Mesa-gallium-32bit-18.1.6-205.1.x86_64 Mesa-libGL1-18.1.6-207.1.x86_64 Mesa-libglapi0-18.1.6-207.1.x86_64 Mesa-libd3d-32bit-18.1.6-205.1.x86_64 Mesa-dri-18.1.6-207.1.x86_64 Mesa-libglapi0-32bit-18.1.6-207.1.x86_64 Mesa-libGL-devel-18.1.6-207.1.x86_64 Mesa-demo-x-8.4.0-1.3.x86_64 Mesa-libd3d-18.1.6-207.1.x86_64 Mesa-32bit-18.1.6-207.1.x86_64 libOSMesa8-32bit-18.1.6-207.1.x86_64 Mesa-libGL1-32bit-18.1.6-207.1.x86_64 Mesa-18.1.6-207.1.x86_64 hardware: Radeon HD7770 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1088310] python3-botocore-1.9.6 possibly breaking aws-cli
by bugzilla_noreply＠novell.com 05 Sep '18

05 Sep '18

http://bugzilla.suse.com/show_bug.cgi?id=1088310 http://bugzilla.suse.com/show_bug.cgi?id=1088310#c17 --- Comment #17 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2018:2621-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1066528,1075263,1088310 CVE References: Sources used: SUSE OpenStack Cloud Crowbar 8 (src): aws-cli-1.15.40-20.6.1, python-botocore-1.10.57-26.10.1, python-s3transfer-0.1.13-6.6.1 SUSE OpenStack Cloud 8 (src): aws-cli-1.15.40-20.6.1, python-botocore-1.10.57-26.10.1, python-s3transfer-0.1.13-6.6.1 SUSE OpenStack Cloud 7 (src): python-botocore-1.10.57-26.10.1 SUSE Linux Enterprise Module for Public Cloud 12 (src): aws-cli-1.15.40-20.6.1, python-boto3-1.7.42-12.6.1, python-botocore-1.10.57-26.10.1, python-s3transfer-0.1.13-6.6.1 HPE Helion Openstack 8 (src): aws-cli-1.15.40-20.6.1, python-botocore-1.10.57-26.10.1, python-s3transfer-0.1.13-6.6.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0