May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1160706] Display Freeze-Up Problem With nVidia gfxG03 Drivers And OpenSUSE Leap 15.1 KDE Plasma 5.12.8
by bugzilla_noreply＠novell.com 08 May '20

08 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1160706 http://bugzilla.suse.com/show_bug.cgi?id=1160706#c28 David Smith <dasmith(a)electronicaidesdesign.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #28 from David Smith <dasmith(a)electronicaidesdesign.com> --- (In reply to Stefan Dirsch from comment #26) > Created attachment 837291 [details] > This patch may help I actually went the long route and recompiled the whole kernel-4.12.17 from scratch yesterday and it compiled fine without any errors. Then I rebooted the computer and went into runlevel3 mode and manually installed the nVidia 340.107 driver by executing: sh ./NVIDIA-Linux-x86_64-340.107.run -a and continued with the installation text screen, which ran through the installation process fine without any issue. It registered the Kernel Source Modules with DKMS and installed the 32-bit Compatibility Libraries as well as Built the Kernel Module and backup the Xorg Config file. Attached is the NVIDIA-Installer.log file of this process. After the nVidia driver installation process was completed, I ran: grub2-mkconfig -o /root/grub2/grub.cfg to insure the new kernel-4.12.17 with the nVidia driver would boot. Then I typed in: systemctl set-default graphical.target to insure the system would go into runlevel5 mode on boot up. I then rebooted the system and it booted up smoothly without any issues and it went into graphical mode fantastic after I login. However, once the complete work disktop appeared on screen, the computer froze and I couldn't exit it. The screen froze, mouse and keyboard as well. I let the system run for about ten minutes to see what happens and to generate log files. I then killed the power to the system. Lucky I have installed a second Linux system to boot up from and I used that to examine the log files from and write this report from. I have attached the Xorg.0.log, boot.log, boot.msg and messages files from this run period. Maybe it will give us a clue to what's going on? I am tempted to try an earlier kernel version prior to 4.12.17 to see if it freezes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1167638] [doc] 5.3 Manually Configuring a 389 Directory Server
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1167638 http://bugzilla.suse.com/show_bug.cgi?id=1167638#c3 William Brown <william.brown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from William Brown <william.brown(a)suse.com> --- The update has been released to leap15.1 and I can confirm it's presence: Version : 1.4.2.12~git0.b11942c36-lp151.5.6.1 Arch : x86_64 Vendor : openSUSE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170588] [Build 20200425] GNote is not initialized with sample notes on first start
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1170588 http://bugzilla.suse.com/show_bug.cgi?id=1170588#c4 Bruce Rogers <brogers(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brogers(a)suse.com --- Comment #4 from Bruce Rogers <brogers(a)suse.com> --- (In reply to Dominique Leuenberger from comment #3) > Upstream commited a fix for this issue; backported into our GNOME:Factory > package I don't know enough about how gnote works to know if this change caused it, but after installing the most recent gnote available as part of the Tumbleweed update today, I no longer see any of my notes. I built a gnote without this latest patch added, but that still doesn't see them - perhaps the damage is already done. I have a whole lot of notes stored in gnote and really want them available again. I see where they are still stored under ~/.local/share/gnote, so it seems bizzare that they are not found. Instead gnote acts like it needs to newly initialize, which this bug seems to be addressing in part. I add this report to this bug because it seems related to this change. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1163197] New: Installer kernel panic
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1163197 Bug ID: 1163197 Summary: Installer kernel panic Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: ivanleo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 829724 --> http://bugzilla.opensuse.org/attachment.cgi?id=829724&action=edit Kernel panic outputs Opensuse 15.2 installer is unable to boot on a Dell XPS 15.2 laptop, the existing 42.3 installation works fine. Unable to save any data as the system freezes, so I've attached a picture instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 46

[Bug 1169826] New: Computer shuts down during hardware detection
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1169826 Bug ID: 1169826 Summary: Computer shuts down during hardware detection Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: All Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: ivanleo(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 836069 --> http://bugzilla.opensuse.org/attachment.cgi?id=836069&action=edit hwinfo from the 42.3 system Tested from openSUSE-Leap-15.2-NET-x86_64-Build631.2-Media.iso Test video: https://www.youtube.com/watch?v=ib-i_L2Ajak Laptop has a working opensuse 42.3 setup -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1169222] New: drm amdgpu crashes when closing laptop lid while having external hdmi screen
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1169222 Bug ID: 1169222 Summary: drm amdgpu crashes when closing laptop lid while having external hdmi screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Apr 11 16:54:00 letik kernel: [drm] pstate TEST_DEBUG_DATA: 0x3FFE0000 Apr 11 16:54:00 letik kernel: ------------[ cut here ]------------ Apr 11 16:54:00 letik kernel: WARNING: CPU: 2 PID: 2114 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:1015 dcn10_verify_allow_pstate_change_high+0x32/0x280 [amdgpu] Apr 11 16:54:00 letik kernel: Modules linked in: tun binfmt_misc ccm rfcomm fuse cmac algif_hash algif_skcipher af_packet af_alg uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 v> Apr 11 16:54:00 letik kernel: k10temp r8169 joydev i2c_piix4 wmi_bmof snd_timer ccp snd_pci_acp3x realtek ipmi_devintf ledtrig_audio libphy ipmi_msghandler snd ucsi_acpi rfkill typec_ucsi > Apr 11 16:54:00 letik kernel: CPU: 2 PID: 2114 Comm: gnome-shell Not tainted 5.6.2-1-default #1 openSUSE Tumbleweed (unreleased) Apr 11 16:54:00 letik kernel: Hardware name: LENOVO 20NJS0DC00/20NJS0DC00, BIOS R12ET50W(1.20 ) 02/19/2020 Apr 11 16:54:00 letik kernel: RIP: 0010:dcn10_verify_allow_pstate_change_high+0x32/0x280 [amdgpu] Apr 11 16:54:00 letik kernel: Code: 8b 87 30 03 00 00 48 89 fb 48 8b b8 b0 01 00 00 e8 63 33 01 00 84 c0 0f 85 3c 02 00 00 80 3d 44 54 2a 00 00 0f 85 32 02 00 00 <0f> 0b 80 bb b7 01 00 00 0> Apr 11 16:54:00 letik kernel: RSP: 0018:ffffbe934159f8a8 EFLAGS: 00010246 Apr 11 16:54:00 letik kernel: RAX: 0000000000000000 RBX: ffff97d9e66c0000 RCX: 0000000000000000 Apr 11 16:54:00 letik kernel: RDX: 0000000000000000 RSI: ffff97d9f0a9bdd8 RDI: ffff97d9f0a9bdd8 Apr 11 16:54:00 letik kernel: RBP: 0000000000000b0b R08: 000000000000064f R09: 0000000000000004 Apr 11 16:54:00 letik kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff97d8fece1da8 Apr 11 16:54:00 letik kernel: R13: ffff97d8fece1da8 R14: ffff97d9e66c0000 R15: ffff97d9e66c0000 Apr 11 16:54:00 letik kernel: FS: 00007ff60fbdeb00(0000) GS:ffff97d9f0a80000(0000) knlGS:0000000000000000 Apr 11 16:54:00 letik kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 11 16:54:00 letik kernel: CR2: 00007f1214036628 CR3: 0000000387eb0000 CR4: 00000000003406e0 Apr 11 16:54:00 letik kernel: Call Trace: Apr 11 16:54:00 letik kernel: dc_commit_state_no_check+0x58d/0x6d0 [amdgpu] Apr 11 16:54:00 letik kernel: dc_commit_state+0x8f/0xb0 [amdgpu] Apr 11 16:54:00 letik kernel: amdgpu_dm_atomic_commit_tail+0x344/0x11d0 [amdgpu] Apr 11 16:54:00 letik kernel: ? ttm_bo_handle_move_mem+0x118/0x5a0 [ttm] Apr 11 16:54:00 letik kernel: ? ttm_bo_validate+0x134/0x150 [ttm] Apr 11 16:54:00 letik kernel: ? ktime_get_raw+0x2e/0x80 Apr 11 16:54:00 letik kernel: ? dm_plane_helper_prepare_fb+0x1a8/0x260 [amdgpu] Apr 11 16:54:00 letik kernel: ? wait_for_completion_timeout+0x103/0x130 Apr 11 16:54:00 letik kernel: ? wait_for_completion_interruptible+0x11b/0x170 Apr 11 16:54:00 letik kernel: commit_tail+0x94/0x130 [drm_kms_helper] Apr 11 16:54:00 letik kernel: drm_atomic_helper_commit+0x113/0x140 [drm_kms_helper] Apr 11 16:54:00 letik kernel: drm_atomic_helper_set_config+0x70/0xb0 [drm_kms_helper] Apr 11 16:54:00 letik kernel: drm_mode_setcrtc+0x194/0x6a0 [drm] Apr 11 16:54:00 letik kernel: ? drm_mode_getcrtc+0x180/0x180 [drm] Apr 11 16:54:00 letik kernel: drm_ioctl_kernel+0xaa/0xf0 [drm] Apr 11 16:54:00 letik kernel: drm_ioctl+0x1f7/0x390 [drm] Apr 11 16:54:00 letik kernel: ? drm_mode_getcrtc+0x180/0x180 [drm] Apr 11 16:54:00 letik kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Apr 11 16:54:00 letik kernel: ksys_ioctl+0x87/0xc0 Apr 11 16:54:00 letik kernel: __x64_sys_ioctl+0x16/0x20 Apr 11 16:54:00 letik kernel: do_syscall_64+0x64/0x240 Apr 11 16:54:00 letik kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe Apr 11 16:54:00 letik kernel: RIP: 0033:0x7ff612d3e227 Apr 11 16:54:00 letik kernel: Code: 00 00 90 48 8b 05 69 8c 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c> Apr 11 16:54:00 letik kernel: RSP: 002b:00007ffd2841ee08 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Apr 11 16:54:00 letik kernel: RAX: ffffffffffffffda RBX: 00007ffd2841ee40 RCX: 00007ff612d3e227 Apr 11 16:54:00 letik kernel: RDX: 00007ffd2841ee40 RSI: 00000000c06864a2 RDI: 0000000000000009 Apr 11 16:54:00 letik kernel: RBP: 00000000c06864a2 R08: 0000000000000000 R09: 000055594f583d20 Apr 11 16:54:00 letik kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000055594f78ccb0 Apr 11 16:54:00 letik kernel: R13: 0000000000000009 R14: 00007ff600007ee0 R15: 000055594f583d20 Apr 11 16:54:00 letik kernel: ---[ end trace 8854aa1e02adb989 ]--- Apr 11 16:54:00 letik kernel: [drm] pstate TEST_DEBUG_DATA: 0x3FFE0000 Possible upstream issues: https://gitlab.freedesktop.org/drm/amd/issues/891 https://gitlab.freedesktop.org/drm/amd/issues/695 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1171368] [Build 20200506] openQA ppc64 test fails with new ruby 2.7
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171368 http://bugzilla.suse.com/show_bug.cgi?id=1171368#c5 --- Comment #5 from Andreas Schwab <schwab(a)suse.com> --- A ruby version switch is always painful and requires a rebuild of all rubygems and dependent packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171397] New: using x2go, drkonqi pops up and crashes frequently
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171397 Bug ID: 1171397 Summary: using x2go, drkonqi pops up and crashes frequently Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: i686 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: paul(a)borowicz.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I login to KDE via x2go (NX protocol), drkonqi pops up and crashes. It keeps doing this in the background while I work. I've exported a crash report below: Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd70d1018c0 (LWP 20595))] Thread 2 (Thread 0x7fd6f20b7700 (LWP 20597)): #0 0x00007fd70869c6db in poll () from /lib64/libc.so.6 #1 0x00007fd7046781a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fd7046782bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fd708fdf7fb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007fd708f8479a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007fd708da2d4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x00007fd70a4389e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x00007fd708da7c8d in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x00007fd70699c4f9 in start_thread () from /lib64/libpthread.so.0 #9 0x00007fd7086a6f2f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd70d1018c0 (LWP 20595)): [KCrash Handler] #6 0x0000561cf0ce97f0 in ?? () #7 0x00007fd6e84f46bd in ?? () from /usr/lib64/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeXcbPlugin0.so #8 0x00007fd7085e7138 in __run_exit_handlers () from /lib64/libc.so.6 #9 0x00007fd7085e718a in exit () from /lib64/libc.so.6 #10 0x00007fd7085cf351 in __libc_start_main () from /lib64/libc.so.6 #11 0x0000561cef228afa in _start () [Inferior 1 (process 20595) detached] -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1171379] VUL-0: CVE-2020-11888: python-markdown2: Unsanitized input allows for cross-site scripting (XSS)
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

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

1 0

[Bug 1171026] New: openjfx Does is not Discoverable by JRE
by bugzilla_noreply＠novell.com 07 May '20

07 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171026 Bug ID: 1171026 Summary: openjfx Does is not Discoverable by JRE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: dashonwwIII(a)pm.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The openjfx/openjfx8 packages for openSuse Tumbleweed obsoletes the package java-1_8_0-openjfx. but does not make the JavaFX libraries accessible to the java runtime environment or sdk by default. For example, I am using openjdk8 package name java-1_8_0-openjdk, and it can not find the any of the openjfx libraries. However, by uninstalling openjfx and installing java-1_8_0-openjfx from a third party repository located here (https://software.opensuse.org/package/java-1_8_0-openjfx) on the openSuse software site; the JavaFX libraries were able to be discovered by the java apps that needed them. Steps To Reproduce: 1. Install the packages java-1_8_0-openjdk and openjfx8. 2. Install any app that makes use of the JavaFX libraries Observed Result: The JavaFX libraries can't be found. Expected Result: Java apps find the JavaFx libraries provided by openjfx/openjfx8 Temporary Solution: Uninstall openjfx/openjfx8 Install the obsoleted package java-1_8_0-openjfx for compatibility. -- You are receiving this mail because: You are on the CC list for the bug.

1 1