KDE display turned to black unresponsive screen during Yast scanner configuration

English Hardware
1

During the Yast scanner configuration the display failed to update and became unresponsive and I was forced to do hard power off with the power button. The journalctl log shows NVRM kernel messages, XCB error 3, XIO: fatal IO error 11, nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0, and BUG: unable to handle kernel NULL pointer dereference at 0000000000000070

My hardware: MSI Z370M gaming pro AC, Evga 1080 FTW2, Intel 8700K CPU, samsung NVME m.2

I would like know where is the best place to report this problem so that it gets fixed.

I placed the relevant excerpt of the journalctl log below my signature. I had to remove some lines as the first submission hit some limit. Apparently, there is no way to attach a log file.

Thanks.
Regards,
Bob W
----------------- log excerpt ----------------------------------------------------------------------------------------------------------------------------------------------------
Sep 14 17:09:00 localhost plasmashell[2587]: libkcups: 0
Sep 14 17:09:32 localhost kernel: NVRM: Xid (PCI:0000:01:00): 8, Channel 0000000a
Sep 14 17:09:32 localhost kwin_x11[2578]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 63435, resource id: 67109021, major code: 19 (DeleteProperty), minor code: 0

Sep 14 17:09:37 localhost kwin_x11[2578]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2457, resource id: 67109025, major code: 18 (ChangeProperty), minor code: 0
Sep 14 17:09:41 localhost kernel: NVRM: Xid (PCI:0000:01:00): 8, Channel 0000000a
Sep 14 17:09:49 localhost kernel: NVRM: Xid (PCI:0000:01:00): 8, Channel 0000000a

Sep 14 17:10:38 localhost kernel: NVRM: Xid (PCI:0000:01:00): 62, 2c937(9424) 040140cf 1000d054
Sep 14 17:10:40 localhost kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Sep 14 17:10:42 localhost kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Sep 14 17:10:53 localhost kdeinit5[2543]: The X11 connection broke: I/O error (code 1)
Sep 14 17:10:53 localhost at-spi-bus-launcher[2506]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server “:0”
Sep 14 17:10:53 localhost at-spi-bus-launcher[2506]: after 310 requests (310 known processed) with 0 events remaining.
Sep 14 17:10:53 localhost kdesud[3266]: Fatal IO error, exiting…
Sep 14 17:10:53 localhost org_kde_powerdevil[2613]: The X11 connection broke (error 1). Did the X11 server die?
Sep 14 17:10:53 localhost python3[2611]: The X11 connection broke (error 1). Did the X11 server die?
Sep 14 17:10:53 localhost xembedsniproxy[2591]: The X11 connection broke (error 1). Did the X11 server die?

Sep 14 17:10:53 localhost systemd[2420]: Reached target Shutdown.
Sep 14 17:10:53 localhost systemd[2420]: Starting Exit the Session…
Sep 14 17:10:53 localhost systemd[2420]: Received SIGRTMIN+24 from PID 22511 (kill).
Sep 14 17:10:53 localhost drkonqi[22507]: qt.qpa.screen: QXcbConnection: Could not connect to display :0
Sep 14 17:10:53 localhost drkonqi[22507]: Could not connect to any X display.
Sep 14 17:10:54 localhost systemd[1]: Stopped User Manager for UID 1001.
Sep 14 17:10:54 localhost systemd[1]: Removed slice User Slice of bob1.
Sep 14 17:10:56 localhost kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Sep 14 17:10:58 localhost kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Sep 14 17:10:58 localhost kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0
Sep 14 17:10:58 localhost sddm[2239]: Removing display “:0” …
Sep 14 17:10:58 localhost sddm[2239]: Adding new display on vt 7 …
Sep 14 17:10:58 localhost sddm[2239]: Loading theme configuration from “”
Sep 14 17:10:58 localhost sddm[2239]: Display server starting…
Sep 14 17:10:58 localhost sddm[2239]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{259aca52-b94a-4fa5-ad31-ed5ece62c1e1} -background none -noreset -displayfd 19 -seat seat0 vt7
Sep 14 17:11:10 localhost plasmashell[2587]: The X11 connection broke: I/O error (code 1)
Sep 14 17:11:10 localhost kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000917e:0:0
Sep 14 17:11:10 localhost plasmashell[2587]: QtDBus: cannot relay signals from parent Phonon::AbstractAudioOutput(0x558efded21c0 “”) unless they are emitted in the object’s thread QThread(0x558efb26cfb0 “”). Current thread is QSGRenderThread(0x558efb33e9b0 “”).
Sep 14 17:11:10 localhost plasmashell[2587]: QtDBus: cannot relay signals from parent QObject(0x558efded21c0 “”) unless they are emitted in the object’s thread QThread(0x558efb26cfb0 “”). Current thread is QSGRenderThread(0x558efb33e9b0 “”).
Sep 14 17:11:10 localhost plasmashell[2587]: QObject::~QObject: Timers cannot be stopped from another thread
Sep 14 17:11:10 localhost plasmashell[2587]: The X11 connection broke: I/O error (code 1)
Sep 14 17:11:10 localhost plasmashell[2587]: The X11 connection broke: I/O error (code 1)
Sep 14 17:11:10 localhost plasmashell[2587]: QtDBus: cannot relay signals from parent QObject(0x558efb790390 “”) unless they are emitted in the object’s thread QThread(0x558efb26cfb0 “”). Current thread is QSGRenderThread(0x558efb33e9b0 “”).
Sep 14 17:11:10 localhost plasmashell[2587]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread
Sep 14 17:11:10 localhost plasmashell[2587]: QObject::~QObject: Timers cannot be stopped from another thread
Notifications") unless they are emitted in the object’s thread QThread(0x558efb26cfb0 “”). Current thread is QSGRenderThread(0x558efb33e9b0 “”).
Sep 14 17:11:10 localhost plasmashell[2587]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread
Sep 14 17:11:10 localhost plasmashell[2587]: QObject::~QObject: Timers cannot be stopped from another thread

Sep 14 17:11:10 localhost plasmashell[2587]: QtDBus: cannot relay signals from parent QObject(0x558efcb374b0 “Application Job Information”) unless they are emitted in the object’s thread QThread(0x558efb26cfb0 “”). Current thread is QSGRenderThread(0x558efb33e9b0 “”).
Sep 14 17:11:12 localhost kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0
Sep 14 17:12:12 localhost kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0
Sep 14 17:12:23 localhost systemd[1]: Starting Cleanup of Temporary Directories…
Sep 14 17:12:23 localhost systemd-tmpfiles[22542]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path “/var/tmp”, ignoring.
Sep 14 17:12:23 localhost systemd-tmpfiles[22542]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path “/var/lib”, ignoring.
Sep 14 17:12:23 localhost systemd-tmpfiles[22542]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path “/var/spool”, ignoring.
Sep 14 17:12:23 localhost systemd[1]: Started Cleanup of Temporary Directories.
Sep 14 17:12:33 localhost kernel: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
Sep 14 17:12:33 localhost kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
Sep 14 17:12:37 localhost kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000070
Sep 14 17:12:37 localhost kernel: IP: _nv002371kms+0x5e/0x100 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: PGD 0 P4D 0
Sep 14 17:12:37 localhost kernel: Oops: 0000 #1] SMP PTI
Sep 14 17:12:37 localhost kernel: Modules linked in: ppdev parport_pc lp parport cmac rfcomm fuse af_packet nf_conntrack_netbios_ns nf_conntrack_broadcast xt_tcpudp xt_CT ip6t_rpfilter ip6t_REJECT nf_log_ipv6 ipt_REJECT nf_log_ipv4 nf_log_common xt_LOG xt_pkttype xt_conntrack iscsi_ibft iscsi_boot_sysfs ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables bnep snd_hda_codec_hdmi nls_iso8859_1 nls_cp437 vfat fat xfs libcrc32c btusb btrtl btbcm btintel sr_mod cdrom bluetooth hid_generic ecdh_generic usbhid snd_hda_codec_realtek
Sep 14 17:12:37 localhost kernel: snd_hda_codec_generic arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel kvm_intel snd_hda_codec iwlmvm snd_hda_core kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel iTCO_wdt mac80211 pcbc iTCO_vendor_support mxm_wmi snd_pcm iwlwifi aesni_intel snd_timer aes_x86_64 crypto_simd glue_helper cryptd snd e1000e pcspkr cfg80211 ptp i2c_i801 pps_core rfkill soundcore mei_me mei shpchp thermal fan wmi video acpi_pad button btrfs xor uas usb_storage raid6_pq dm_service_time nvidia_drm(PO) nvidia_modeset(PO) nvidia_uvm(PO) nvidia(PO) drm_kms_helper drm xhci_pci drm_panel_orientation_quirks syscopyarea crc32c_intel sysfillrect xhci_hcd nvme sysimgblt fb_sys_fops nvme_core ahci ipmi_devintf libahci usbcore ipmi_msghandler dm_mirror dm_region_hash dm_log
Sep 14 17:12:37 localhost kernel: coretemp msr sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs
Sep 14 17:12:37 localhost kernel: CPU: 5 PID: 22516 Comm: X Tainted: P O 4.12.14-lp150.12.16-default #1 openSUSE Leap 15.0
Sep 14 17:12:37 localhost kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B44/Z370M GAMING PRO AC (MS-7B44), BIOS 1.20 12/21/2017
Sep 14 17:12:37 localhost kernel: task: ffff880fed998080 task.stack: ffffc900241b4000
Sep 14 17:12:37 localhost kernel: RIP: 0010:_nv002371kms+0x5e/0x100 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: RSP: 0018:ffffc900241b7d40 EFLAGS: 00010246
Sep 14 17:12:37 localhost kernel: RAX: 0000000000000000 RBX: 0000000000000fff RCX: 00000000000f4240
Sep 14 17:12:37 localhost kernel: RDX: 0000000000010009 RSI: ffff881000cf0640 RDI: 00000000c1d00010
Sep 14 17:12:37 localhost kernel: RBP: 0000000000010009 R08: 0000000000000087 R09: 0000000000000001
Sep 14 17:12:37 localhost kernel: R10: 0000000000000219 R11: ffffffffa0918860 R12: 0000000000010008
Sep 14 17:12:37 localhost kernel: R13: ffff881006d47008 R14: ffff881006d470a0 R15: ffff880fc3250008
Sep 14 17:12:37 localhost kernel: FS: 00007f91f9a48300(0000) GS:ffff88102e340000(0000) knlGS:0000000000000000
Sep 14 17:12:37 localhost kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 14 17:12:37 localhost kernel: CR2: 0000000000000070 CR3: 0000000fa26c0005 CR4: 00000000003606e0
Sep 14 17:12:37 localhost kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 14 17:12:37 localhost kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 14 17:12:37 localhost kernel: Call Trace:
Sep 14 17:12:37 localhost kernel: ? _nv002178kms+0x29d/0x2b0 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: ? _nv000457kms+0x2c/0x40 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: ? nvKmsIoctl+0x117/0x230 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: ? nvidia_ioctl+0x196/0x6e0 [nvidia]
Sep 14 17:12:37 localhost kernel: ? _nv000505kms+0x40/0x40 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: ? nvkms_ioctl_common+0x3b/0x80 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: ? nvkms_ioctl+0x57/0x80 [nvidia_modeset]
Sep 14 17:12:37 localhost kernel: ? nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
Sep 14 17:12:37 localhost kernel: ? do_vfs_ioctl+0x90/0x5f0
Sep 14 17:12:37 localhost kernel: ? SyS_ioctl+0x74/0x80
Sep 14 17:12:37 localhost kernel: ? do_syscall_64+0x7b/0x150
Sep 14 17:12:37 localhost kernel: ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Sep 14 17:12:37 localhost kernel: Code: 00 20 ba 02 00 00 00 89 c6 89 c5 48 89 1c 24 e8 79 53 00 00 85 c0 0f 85 91 00 00 00 49 8b 85 a0 01 00 00 8b 3d b4 f1 0a 00 89 ea <8b> 70 70 e8 7a 52 00 00 85 c0 75 67 41 8b b5 d0 00 00 00 85 f6
Sep 14 17:12:37 localhost kernel: RIP: _nv002371kms+0x5e/0x100 [nvidia_modeset] RSP: ffffc900241b7d40
Sep 14 17:12:37 localhost kernel: CR2: 0000000000000070
Sep 14 17:12:37 localhost kernel: — end trace 0dc551f1bd85925c ]—
Sep 14 17:14:22 localhost systemd-logind[1403]: Power key pressed.
Sep 14 17:14:22 localhost systemd-logind[1403]: Powering Off…
Sep 14 17:14:22 localhost systemd-logind[1403]: System is powering down.

2

Welcome to openSUSE Forums bwheater. Graphics-related issues like the one you have encountered can be complex to diagnose and resolve, (especially when a proprietary driver is in use). In any case, I assume this happens consistently when trying to use the YaST scanner configuration utility? Is this the only YaST component that is affected?

Here’s a guide on openSUSE bug reporting…
https://en.opensuse.org/openSUSE:Submitting_bug_reports

BTW, from a scanner configuration perspective, it is not necessary to use the YaST utility at all. This can be done from a terminal. So if you would like help with that I recommend starting a new thread and someone (including myself) should be able to assist further.

3

Thanks for your reply and the link for reporting bugs. I ran through the Yast configure scanner 3 more times but I was not able to recreate the graphic mode reset and kernel oops with my Nvidia card. I have since seen some utube videos recommending a nomodereset as a kernel parameter on other distros (for example Ubuntu). So if it happens again I will try this.

I have got the scanner configured and works with the supplied skanlite software but It is severely limited functionality. I have installed simple scanner and it is better but not sufficient. Then I tried gscan2pdf. It took quite a bit of research and fiddling with the configuration to get a frontend that will not distort the image and scan at 300dpi or greater.

I was wondering what type of user that OpenSuse is intended for in terms of scanning software. Since you provide Skanlite by default it seems that it is intended for the home user. What about the small office or corporate office?

Thanks for your time.

Regards
Bob

4

Not distro specific. Skanlite is the default KDE application supplied when using KDE desktop, but of course you’re free to use any SANE front-end. My personal preference is simple-scan, but my needs are basic. HP and Canon provide their own proprietary applications.

5

I know you can get the iScan software and drivers for the (not mentioned) Epson scanners but I’m not sure about Canon. I don’t believe there is even a Canon driver for my Canoscan although it is supported by Linux.

HEading a bit more in towards the question you responded to. My own choice of Linux scanner software is Xsane but I think it’s a case of pick what suits you best. If you might need to perform a task regularly, you could try using the command line scanimage and a simple script. My mother has a shortcut on her desktop for example which will “photocopy” to the laser printer and that’s quicker than using a GUI.

Taking that idea further, my scanner has buttons that can be programmed for a few tasks, I’ll not go into that part (which was mentioned in another thread) but will include my main (python) script which doubtless could be improved no end but does most of what I’ve wanted and shuld give some idea.

import glob

 import os
 import sys
 
 
 def getFilename(prefix, suffix):
     try:
         filelist=glob.glob(prefix + "*." + suffix)
         l = len(prefix)
         r = len(suffix) + 1
         x=0
         for file in filelist:
             name = file[l:-r]
             try:
                 name = int(name)
                 if (name>x):
                     x = name
             except:
                 pass
         x = x + 1
     except:
         x = 1
              
     return prefix + str(x).zfill(3) + "." + suffix
 
 
 
 
 def colorScan(device):
     os.chdir("/home/scanout/")
     filename = getFilename("colorscan-", "tiff")
     os.system("scanimage -d " + device + " --source Flatbed --mode Color --resolution 600 > " + filename)
     os.system("chown jon " + filename)
 
 
 def colorPdf(device):
     os.chdir("/home/scanout/")
     filename = getFilename("colorpdf-", "pdf")
     os.system("scanimage -d " + device + " --source Flatbed --mode Color --resolution 150 --format=pdf | convert - -page a4 -quality 72 temp.pdf")
     os.system("ps2pdf temp.pdf " + filename)
     os.system("rm temp.pdf")
     os.system("chown jon " + filename)
          
 def monoPdf(device):
     os.chdir("/home/scanout/")
     filename = getFilename("monopdf-", "pdf")
     os.system("scanimage -d " + device + " --source Flatbed --mode Gray --resolution 150 --format=pdf | convert - -page a4 -quality 72 temp.pdf")
     os.system("ps2pdf temp.pdf " + filename)
     os.system("rm temp.pdf")
     os.system("chown jon " + filename)
      
 def colorPrint(device):
     os.system("scanimage -d " + device + " --source Flatbed --mode Color --resolution 300 -x 210 -y 297 --format=tiff | lp -d Laser_Printer_Colour_172_23_41_10 -o fit-to-page")
        
 def monoPrint(device):
     os.system("scanimage -d " + device + " --source Flatbed --mode Gray --resolution 150 -x 210 -y 297 --format=tiff | lp -d Laser_Printer_Mono_172_23_41_10 -o fit-to-page")
 
 
 def slideProject(device):
     os.chdir("/home/scanout")
     os.system("scanimage -d " + device + " --source 'Transparency Unit' --resolution 1200 --format=tiff --mode Color -l 90 -t 32 -x 36 -y 205 " +
     "| convert tiff:- -crop 1x4-0-880@\! +repage +adjoin -density 600 tmp-%d.jpeg")
     os.system("chown jon tmp*.jpeg")
     os.system("chgrp users tmp*.jpeg")
     os.system("mv tmp-0.jpeg " + getFilename("slide-", "jpeg") )
     os.system("mv tmp-1.jpeg " + getFilename("slide-", "jpeg") )
     os.system("mv tmp-2.jpeg " + getFilename("slide-", "jpeg") )
     os.system("mv tmp-3.jpeg " + getFilename("slide-", "jpeg") )
 
 
 if (sys.argv[1] == "colorscan"):
     colorScan(sys.argv[2])
 elif (sys.argv[1] == "colorpdf"):
     colorPdf(sys.argv[2])
 elif (sys.argv[1] == "monopdf"):
     monoPdf(sys.argv[2])
 elif (sys.argv[1] == "colorprint"):
     colorPrint(sys.argv[2])
 elif (sys.argv[1] == "monoprint"):
     monoPrint(sys.argv[2])
 elif(sys.argv[1] == "slideproject"):
     slideProject(sys.argv[2]);

OK it’s a bit of a fiddle and what you can do depends on the scanner and support but I think it can be possible to get to quite a workable set up.