August 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1084811] New: E-sata hotplugging stopped working since kernel 4.15
by bugzilla_noreply＠novell.com 03 Jul '22

03 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084811 Bug ID: 1084811 Summary: E-sata hotplugging stopped working since kernel 4.15 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: attila.schler(a)atskler.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have noticed that on my Dell E6520 notebook the e-sata hotplugging stopped working since kernel 4.15. Currently I can observe this problem with kernel: 4.15.7-1.6-x86_64 4.16.0-rc4-4.g7a5941a-x86-64 The e-sata cable is OK, and an e-sata device can be used with kernel 4.15 if it is turned on and plugged in before powering on my notebook. (The e-sata hotplugging works well with the Leap kernel 4.12.14-lp150.5.3-x86_64.) ___ (I’m not an advanced user, but I’m ready to follow detailed instructions.) -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1028460] New: grub2 ignores active_devices
by bugzilla_noreply＠novell.com 30 Jun '22

30 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1028460 Bug ID: 1028460 Summary: grub2 ignores active_devices Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: rw(a)suse.de Reporter: bg(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- after doing the latest update, I found that /boot/zipl/active_devices.txt was emptied. Even after copying the old data in there, the newly generated initrd ignores active_devices.txt which results in an unbootable system. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1092326] New: Plasma Wayland does not use the configured system keyboard layout and freezes when trying to set a keyboard layout
by bugzilla_noreply＠novell.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1092326 Bug ID: 1092326 Summary: Plasma Wayland does not use the configured system keyboard layout and freezes when trying to set a keyboard layout Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This bug report is related to bug #1091816 but behaves different in Leap 15.0. Also in this case during installation US keyboard with dead keys is configured. But there is no layout configured in systemsettings5. However starting konsole and pressing the accent key or another dead key gives a popup showing spectacle and asks to select something to make a screen copy. When trying to configure a keyboard layout in systemsettings5 the screen freezes. The mouse pointer does not move anymore. After a minute or so, I get the login screen again, but this may be caused by pressing <Ctrl><Alt>+<Backspace>+<Backspace>. I did not try to wait if without pressing these keys the login screen still appears. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1091818] New: After starting a Wayland Plasma session and leaving the session, login into a normal Plasma session does not work
by bugzilla_noreply＠novell.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 Bug ID: 1091818 Summary: After starting a Wayland Plasma session and leaving the session, login into a normal Plasma session does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started a Wayland Plasma session. Because being unable to enter certain characters in that session I finished that session and got the login screen. I changed the type of session to a classic Plasma session and entered the password. After a while I did not enter the session, but the system returned to the login screen. I needed to reboot, to be able to start a normal Plasma session. -- You are receiving this mail because: You are on the CC list for the bug.

2 17

[Bug 1080842] New: plasma with wayland gives flickering applications
by bugzilla_noreply＠novell.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1080842 Bug ID: 1080842 Summary: plasma with wayland gives flickering applications Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried Leap 15.0 updated to Build 128.1 using Plasma with Wayland. Having a few application windows open. These windows appear partly behind each other in a flickering way. The screen is constantly changing showing part of one window in front of another, but disappearing a bit later behind that window. There is no stable screen. The window with focus may be partly behind another window. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1042528] New: security/keepassx: Segfault for search
by bugzilla_noreply＠novell.com 21 Jun '22

21 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1042528 Bug ID: 1042528 Summary: security/keepassx: Segfault for search Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: meissner(a)suse.com Reporter: sebix+novell.com(a)sebix.at QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- After pressing Ctrl+F it shortly (~0.2s) shows the search view and then gave me a Segfault. Running it with gdb gave me another error: > gdb keepass keepassx keepassxc ele@melekess:~> gdb keepassx GNU gdb (GDB; openSUSE Tumbleweed) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from keepassx...Reading symbols from /usr/lib/debug/usr/bin/keepassx.debug...done. done. (gdb) r Starting program: /usr/bin/keepassx Missing separate debuginfo for /usr/lib64/libQtCore.so.4 Try: zypper install -C "debuginfo(build-id)=aae09ee6055dc186575945fad62f28e198a9d356" Missing separate debuginfo for /usr/lib64/libQtGui.so.4 Try: zypper install -C "debuginfo(build-id)=be91c0bccafd94ecc5fd1a4437e2de5b77696ca1" Missing separate debuginfo for /usr/lib64/libgcrypt.so.20 Try: zypper install -C "debuginfo(build-id)=4e0a9294838b3fb3dac12e68cb00f2e4f397b2e9" Missing separate debuginfo for /lib64/libz.so.1 Try: zypper install -C "debuginfo(build-id)=21b301d5592177bf542e8d8c41c0b27df7e2440d" Missing separate debuginfo for /usr/lib64/libstdc++.so.6 Try: zypper install -C "debuginfo(build-id)=ee9fd8cc6fbbf42cc79e4924f6118b496b45b3a8" [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=561783b5517f6a4c17726f96ef692597377d9fc8" Missing separate debuginfo for /lib64/libgcc_s.so.1 Try: zypper install -C "debuginfo(build-id)=d2a8238991eb9ac4afa570da0419d6188b64a546" Missing separate debuginfo for /usr/lib64/libpng16.so.16 Try: zypper install -C "debuginfo(build-id)=22de6f0dd806ef44469f30509bd7c1919730cdbd" Missing separate debuginfo for /usr/lib64/libfreetype.so.6 Try: zypper install -C "debuginfo(build-id)=ddfced10958280dc5cbc5031dda671a6bd0ecd70" Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=64f04f5c97010448c3a51b03bb9fa2b437888e57" Missing separate debuginfo for /usr/lib64/libSM.so.6 Try: zypper install -C "debuginfo(build-id)=488ce271a4e9b76d429602888b6e2cd766e4d4bd" Missing separate debuginfo for /usr/lib64/libICE.so.6 Try: zypper install -C "debuginfo(build-id)=95e0e706f873fbd16c643ec072b3e7f21a48138c" Missing separate debuginfo for /usr/lib64/libXi.so.6 Try: zypper install -C "debuginfo(build-id)=04842b5af5cbfdca656d65ed3e2f69f3f078d9c5" Missing separate debuginfo for /usr/lib64/libXrender.so.1 Try: zypper install -C "debuginfo(build-id)=dbd5711f34b7cfa50f28059240da17240894187e" Missing separate debuginfo for /usr/lib64/libXrandr.so.2 Try: zypper install -C "debuginfo(build-id)=cc3f4cf227f8e8d5ddec9ae0dfea02e450ae45e1" Missing separate debuginfo for /usr/lib64/libXfixes.so.3 Try: zypper install -C "debuginfo(build-id)=446be2aebf53829fe05f0257d4b94765639e218b" Missing separate debuginfo for /usr/lib64/libXcursor.so.1 Try: zypper install -C "debuginfo(build-id)=b589fe995a2a95a9e8b4a1404466c24186c2647c" Missing separate debuginfo for /usr/lib64/libXinerama.so.1 Try: zypper install -C "debuginfo(build-id)=a9dd93da989813b45ffed48101f4e69f8f5f3b79" Missing separate debuginfo for /usr/lib64/libfontconfig.so.1 Try: zypper install -C "debuginfo(build-id)=1657bc30ca61f5a5165b0a1bf4c14ea432d740c6" Missing separate debuginfo for /usr/lib64/libXext.so.6 Try: zypper install -C "debuginfo(build-id)=9825de0ced273155a4f9cbed9c35aa6219fd2311" Missing separate debuginfo for /usr/lib64/libX11.so.6 Try: zypper install -C "debuginfo(build-id)=261d9592a95e4724a3d7019faa591320ec3834d0" Missing separate debuginfo for /usr/lib64/libgpg-error.so.0 Try: zypper install -C "debuginfo(build-id)=9985ccc9f6380b4be688069ae226dfbd77013f9b" Missing separate debuginfo for /usr/lib64/libpcre.so.1 Try: zypper install -C "debuginfo(build-id)=8b15c8089ae69924185eb89f09c0b4d2c4178e59" Missing separate debuginfo for /usr/lib64/libbz2.so.1 Try: zypper install -C "debuginfo(build-id)=6e4dee957505d111d0eb00fe0830394c3dd44f6a" Missing separate debuginfo for /usr/lib64/libffi.so.7 Try: zypper install -C "debuginfo(build-id)=b93e3c6f234f62f861d6a429bc3672a85ae22c95" Missing separate debuginfo for /usr/lib64/libuuid.so.1 Try: zypper install -C "debuginfo(build-id)=4c7dba3b81d600005bc342e1b31982eb259349f5" Missing separate debuginfo for /usr/lib64/libexpat.so.1 Try: zypper install -C "debuginfo(build-id)=6de3c39118914851895f9af7c9abf737d717aa13" Missing separate debuginfo for /usr/lib64/libxcb.so.1 Try: zypper install -C "debuginfo(build-id)=b3a1aeb7294c2b5503d2401b1317bfddc34220c7" Missing separate debuginfo for /usr/lib64/libXau.so.6 Try: zypper install -C "debuginfo(build-id)=86d79656851311fd78521e28b18cf88b7f7ffec0" Cannot find user-level thread for LWP 12821: generic error (gdb) Not sure how to debug it further. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1091291] New: GNOME:Factory/gnome-disk-utility: function bd_loop_setup_from_fd not found
by bugzilla_noreply＠novell.com 21 Jun '22

21 Jun '22

2 1

[Bug 925275] New: NVIDIA Driver not installable
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=925275 Bug ID: 925275 Summary: NVIDIA Driver not installable Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fbernasek(a)netscape.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 629479 --> http://bugzilla.opensuse.org/attachment.cgi?id=629479&action=edit nvidia driver install log install opensuse tumbleweed 20150329 no problems. after reboot i like to install the NVIDIA-346.47 or 349.12 with booth the same problem can't install the driver. now i update with the kernel from the kernel:stable repositories the same problem. 20150328 the same problem -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1004201] New: System hangs during boot due to loop trying to load nvidia modules
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1004201 Bug ID: 1004201 Summary: System hangs during boot due to loop trying to load nvidia modules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: marcelo.jimenez(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lspci is: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 730] (rev a1) Nvidia site explicitly says that the 367.44 driver does support GT 730. In my opinion, there are two problems here: 1 - The system initialization should not loop forever trying to load a module it has already tryed to load and failed 2 - The 367.44 NVIDIA driver should support my hardware. The NVRM messages repeat forever: ... Oct 09 09:17:23 linux-af78 kernel: [drm] Initialized drm 1.1.0 20060810 Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: module license 'NVIDIA' taints kernel. Oct 09 09:17:23 linux-af78 kernel: Disabling lock debugging due to kernel taint Oct 09 09:17:23 linux-af78 systemd-journal[120]: Journal started Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0) Oct 09 09:17:23 linux-af78 systemd[1]: Started Journal Service. ... Oct 09 09:17:31 linux-af78 systemd[1]: Mounting /home... Oct 09 09:17:31 linux-af78 mtp-probe[579]: checking bus 6, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb6/6-1" Oct 09 09:17:31 linux-af78 mtp-probe[578]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb5/5-2" Oct 09 09:17:31 linux-af78 mtp-probe[578]: bus: 5, device: 2 was not an MTP device Oct 09 09:17:31 linux-af78 mtp-probe[579]: bus: 6, device: 2 was not an MTP device Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Mounted /home. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Reached target Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Oct 09 09:17:32 linux-af78 systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Oct 09 09:17:32 linux-af78 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1059001] New: kded5 or kdeint5 crashes after systemctl restart NetworkManager
by bugzilla_noreply＠novell.com 12 Jun '22

12 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1059001 Bug ID: 1059001 Summary: kded5 or kdeint5 crashes after systemctl restart NetworkManager 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: drnn_1076(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: When I resume my laptop after suspending it. I got no connection to the my wireless network. I get the list of wireless networks available but when I hit "connect" nothing happens. So I restart the NetworkManager using "systemctl restart NetworkManager" and it works again properly. I'm getting however the following crash of kded5 or kdeint5 immediately after restarting the NetworkManager: for kded5: kded5 PID: 11541 Signal: Segmentation fault (11) Time: 17/09/2017 10:48:35 for kdeinit5: kdeninit5 PID:2138 Signal: Segmentation fault (11) Time ... Note: It might be related to the touchpad conflicting with my usb mouse. Reproducible: Always Steps to Reproduce: 1. Systemctl restart NetwrokManager 2. Crash kded5 3. Close the crash window and everything works ok Kded5 developer information Application: kded5 (kded5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc16a5dbd40 (LWP 11541))] Thread 9 (Thread 0x7fc10affd700 (LWP 11572)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fc10b7fe700 (LWP 11571)): #0 0x00007fc164747ba4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x00007fc164702ce6 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc116ec8f37 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #8 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #9 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fc10bfff700 (LWP 11565)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc1647030c2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc111f71456 in () at /usr/lib64/libgio-2.0.so.0 #4 0x00007fc164729c05 in () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fc110f34700 (LWP 11564)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc164702e81 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007fc164729c05 in () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc1141ef700 (LWP 11562)): #0 0x00007fc169f21cc8 in read () at /lib64/libc.so.6 #1 0x00007fc164746850 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc16470280b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc164702cd0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #7 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #9 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #10 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc14def9700 (LWP 11546)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc14f429700 (LWP 11545)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc168566a45 in () at /usr/lib64/libQt5DBus.so.5 #7 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #8 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #9 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc15cff1700 (LWP 11542)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164498387 in () at /usr/lib64/libxcb.so.1 #2 0x00007fc16449a17a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x00007fc15fdb64b9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fc16a5dbd40 (LWP 11541)): [KCrash Handler] #6 0x00007fc1664457d9 in XPending () at /usr/lib64/libX11.so.6 #7 0x00007fc1137ca9e8 in () at /usr/lib64/qt5/plugins/kded_touchpad.so #8 0x00007fc1137caa3e in () at /usr/lib64/qt5/plugins/kded_touchpad.so #9 0x00007fc167bcd25a in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #10 0x00007fc167bd9128 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #11 0x00007fc167bd9492 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x00007fc1697629bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x00007fc169769d74 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x00007fc167b9fd48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x00007fc167bf628d in () at /usr/lib64/libQt5Core.so.5 #16 0x00007fc164702b77 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x00007fc164702da8 in () at /usr/lib64/libglib-2.0.so.0 #18 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #20 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #21 0x00007fc167ba6be4 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #22 0x00007fc16a200e1a in kdemain () at /usr/lib64/libkdeinit5_kded5.so #23 0x00007fc169e5af1a in __libc_start_main () at /lib64/libc.so.6 #24 0x0000558fc350f7fa in _start () -- You are receiving this mail because: You are on the CC list for the bug.

2 3