Arch Linux

ssri

Member

Registered: 2010-02-16

Posts: 216

Re: KF 5 & Plasma

Anyone having trouble making new gestures (System Settings>Shortcuts>Custom Shortcuts)?  Whenever I create one for a program and try to have plasma detect it (Conditions>New Active Window>New>Autodetect), the cross-hairs remain in place and all of the mouse buttons disable [verified with xev].  I mean, clicking the program I wish to create mouse gestures for with the crosshair, say an open session of konsole, does nothing.  The crosshair remains and none of the mouse buttons work.  Now, I have to use the keyboard to navigate around KDE.  If I want mouse button functionality back, I have to ZAP X.

Can anyone test the above out?  It still happens with the latest Plasma packages from [extra].

I already reported the bug; I just want to know if anyone else is experiencing the above: https://bugs.kde.org/show_bug.cgi?id=354109

aurelieng

Member

Registered: 2010-02-02

Posts: 104

Re: KF 5 & Plasma

Since I upgraded from KDE4 to KF5, resume from suspend to RAM fails 50% of the time: SDDM displays the login screen instead of my screensaver lock screen, When it happens, I can briefly see one one of the tty (possibly tty1), before X is restarted. As you can guess, it's really annoying since suspend to RAM is useless if it's not reliable. It used to work very well w/ KDE4 on this computer (Dell Precision M6400).

I found two related core dumps with coredumpctl. The first one is for /usr/bin/kactivitymanagerd (SIGSEGV), and the second one for /usr/lib/xorg-server/Xorg (SIGABRT).

Here's the stack trace for /usr/bin/kactivitymanagerd

Core was generated by `/usr/bin/kactivitymanagerd start-daemon'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f44358e6881 in QSqlDatabase::close() () from /usr/lib/libQt5Sql.so.5
[Current thread is 1 (Thread 0x7f4453dd5800 (LWP 974))]
(gdb) bt
#0  0x00007f44358e6881 in QSqlDatabase::close() () from /usr/lib/libQt5Sql.so.5
#1  0x00007f44358e7de9 in QSqlDatabase::~QSqlDatabase() () from /usr/lib/libQt5Sql.so.5
#2  0x00007f44358e9e1d in ?? () from /usr/lib/libQt5Sql.so.5
#3  0x00007f4451eaa289 in QHashData::detach_helper(void (*)(QHashData::Node*, void*), void (*)(QHashData::Node*), int, int) () from /usr/lib/libQt5Core.so.5
#4  0x00007f445169bfd5 in exit () from /usr/lib/libc.so.6
#5  0x00007f444689a5de in ?? () from /usr/lib/libQt5XcbQpa.so.5
#6  0x00007f444690fbc0 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#7  0x0000000384d675f0 in ?? ()
#8  0x066e4c1f3cb5c200 in ?? ()
#9  0x00007f4453dd5800 in ?? ()
#10 0x0000000001a30bd0 in ?? ()
#11 0x00007ffc84d675f0 in ?? ()
#12 0x0000000001a15980 in ?? ()
#13 0x00007ffc84d67a80 in ?? ()
#14 0x00007ffc84d675a0 in ?? ()
#15 0x0000000000000000 in ?? ()

Program terminated with signal SIGABRT, Aborted.
#0  0x00007f7b875b95f8 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007f7b875b95f8 in raise () from /usr/lib/libc.so.6
#1  0x00007f7b875baa7a in abort () from /usr/lib/libc.so.6
#2  0x00000000005992ee in OsAbort ()
#3  0x000000000047a41c in ddxGiveUp ()
#4  0x000000000059ef02 in ?? ()
#5  0x000000000059fd3d in FatalError ()
#6  0x0000000000596c4e in ?? ()
#7  <signal handler called>
#8  0x00007f7b80a1ca6d in ?? () from /usr/lib/xorg/modules/drivers/nvidia_drv.so
#9  0x00007f7b80f740a9 in ?? () from /usr/lib/xorg/modules/drivers/nvidia_drv.so
#10 0x00007f7b80f78804 in ?? () from /usr/lib/xorg/modules/drivers/nvidia_drv.so
#11 0x00007f7b80f882f2 in ?? () from /usr/lib/xorg/modules/drivers/nvidia_drv.so
#12 0x00007f7b80f7fcd1 in ?? () from /usr/lib/xorg/modules/drivers/nvidia_drv.so
#13 0x000000000047857b in xf86VTEnter ()
#14 0x000000000043da1d in WakeupHandler ()
#15 0x000000000058f54f in WaitForSomething ()
#16 0x0000000000438be1 in ?? ()
#17 0x000000000043cf0b in ?? ()
#18 0x00007f7b875a6610 in __libc_start_main () from /usr/lib/libc.so.6
#19 0x0000000000427319 in _start ()

I'm using the following versions:

sddm 0.12.0-4
kactivities-frameworks 5.15.0-1
libkactivities4 4.13.3-1

As you may notice, I'm using the proprietary nvidia driver, but I don't think it's related because kactivitymanagerd seems to crash first. Just in case:

lib32-nvidia-340xx-libgl 340.93-1
lib32-nvidia-340xx-utils 340.93-1
nvidia-340xx 340.93-3
nvidia-340xx-libgl 340.93-1
nvidia-340xx-utils 340.93-1

Here's the full log:

Oct 22 19:32:01 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
[... overnight ...]
Oct 23 05:44:36 XXXXXXXXXXX kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct 23 05:44:36 XXXXXXXXXXX kernel: Freezing remaining freezable tasks ... (elapsed 4.769 seconds) done.
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: Suspending system (mem)
Oct 23 05:44:36 XXXXXXXXXXX kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 23 05:44:36 XXXXXXXXXXX kernel: sd 4:0:0:0: [sdb] Synchronizing SCSI cache
Oct 23 05:44:36 XXXXXXXXXXX kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 23 05:44:36 XXXXXXXXXXX kernel: sd 4:0:0:0: [sdb] Stopping disk
Oct 23 05:44:36 XXXXXXXXXXX kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: suspend of devices complete after 1373.934 msecs
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: late suspend of devices complete after 0.547 msecs
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1a.2: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: noirq suspend of devices complete after 45.399 msecs
Oct 23 05:44:36 XXXXXXXXXXX kernel: ACPI: Preparing to enter system sleep state S3
Oct 23 05:44:36 XXXXXXXXXXX kernel: ACPI : EC: EC stopped
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: Saving platform NVS memory
Oct 23 05:44:36 XXXXXXXXXXX kernel: Disabling non-boot CPUs ...
Oct 23 05:44:36 XXXXXXXXXXX kernel: smpboot: CPU 1 is now offline
Oct 23 05:44:36 XXXXXXXXXXX kernel: smpboot: CPU 2 is now offline
Oct 23 05:44:36 XXXXXXXXXXX kernel: smpboot: CPU 3 is now offline
Oct 23 05:44:36 XXXXXXXXXXX kernel: ACPI: Low-level resume complete
Oct 23 05:44:36 XXXXXXXXXXX kernel: ACPI : EC: EC started
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: Restoring platform NVS memory
Oct 23 05:44:36 XXXXXXXXXXX kernel: Enabling non-boot CPUs ...
Oct 23 05:44:36 XXXXXXXXXXX kernel: x86: Booting SMP configuration:
Oct 23 05:44:36 XXXXXXXXXXX kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Oct 23 05:44:36 XXXXXXXXXXX kernel:  cache: parent cpu1 should not be sleeping
Oct 23 05:44:36 XXXXXXXXXXX kernel: CPU1 is up
Oct 23 05:44:36 XXXXXXXXXXX kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Oct 23 05:44:36 XXXXXXXXXXX kernel:  cache: parent cpu2 should not be sleeping
Oct 23 05:44:36 XXXXXXXXXXX kernel: CPU2 is up
Oct 23 05:44:36 XXXXXXXXXXX kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct 23 05:44:36 XXXXXXXXXXX kernel:  cache: parent cpu3 should not be sleeping
Oct 23 05:44:36 XXXXXXXXXXX kernel: CPU3 is up
Oct 23 05:44:36 XXXXXXXXXXX kernel: ACPI: Waking up from system sleep state S3
Oct 23 05:44:36 XXXXXXXXXXX kernel: yenta_cardbus 0000:03:01.0: proprietary Ricoh MMC controller disabled (via cardbus function)
Oct 23 05:44:36 XXXXXXXXXXX kernel: yenta_cardbus 0000:03:01.0: MMC cards are now supported by standard SDHCI controller
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: uhci_hcd 0000:00:1a.2: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: noirq resume of devices complete after 44.299 msecs
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: early resume of devices complete after 0.595 msecs
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb usb3: root hub lost power or was reset
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb usb4: root hub lost power or was reset
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb usb5: root hub lost power or was reset
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb usb6: root hub lost power or was reset
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb usb7: root hub lost power or was reset
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb usb8: root hub lost power or was reset
Oct 23 05:44:36 XXXXXXXXXXX kernel: tg3 0000:09:00.0 eth0: Link is down
Oct 23 05:44:36 XXXXXXXXXXX kernel: iwlwifi 0000:0c:00.0: RF_KILL bit toggled to disable radio.
Oct 23 05:44:36 XXXXXXXXXXX kernel: rtc_cmos 00:02: System wakeup disabled by ACPI
Oct 23 05:44:36 XXXXXXXXXXX kernel: sd 0:0:0:0: [sda] Starting disk
Oct 23 05:44:36 XXXXXXXXXXX kernel: sd 4:0:0:0: [sdb] Starting disk
Oct 23 05:44:36 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
Oct 23 05:44:36 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:36 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb 1-6: reset high-speed USB device number 3 using ehci-pci
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb 5-1: reset full-speed USB device number 2 using uhci_hcd
Oct 23 05:44:36 XXXXXXXXXXX kernel: usb 7-1: reset full-speed USB device number 2 using uhci_hcd
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata6: SATA link down (SStatus 0 SControl 300)
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata1.00: configured for UDMA/133
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata2.00: configured for UDMA/133
Oct 23 05:44:36 XXXXXXXXXXX kernel: ata5.00: configured for UDMA/133
Oct 23 05:44:36 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: resume of devices complete after 2236.514 msecs
Oct 23 05:44:36 XXXXXXXXXXX kernel: PM: Finishing wakeup.
Oct 23 05:44:36 XXXXXXXXXXX kernel: Restarting tasks ... done.
Oct 23 05:44:36 XXXXXXXXXXX kernel: video LNXVIDEO:00: Restoring backlight state
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Time has been changed
Oct 23 05:44:36 XXXXXXXXXXX rtkit-daemon[1032]: The canary thread is apparently starving. Taking action.
Oct 23 05:44:36 XXXXXXXXXXX systemd[865]: Time has been changed
Oct 23 05:44:36 XXXXXXXXXXX rtkit-daemon[1032]: Demoting known real-time threads.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Starting Verify integrity of password and group files...
Oct 23 05:44:36 XXXXXXXXXXX rtkit-daemon[1032]: Successfully demoted thread 1042 of process 1031 (/usr/bin/pulseaudio).
Oct 23 05:44:36 XXXXXXXXXXX kwin_x11[1002]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 13711, resource id: 654, major code: 3 (GetWindowAttributes), minor code: 0
Oct 23 05:44:36 XXXXXXXXXXX rtkit-daemon[1032]: Successfully demoted thread 1041 of process 1031 (/usr/bin/pulseaudio).
Oct 23 05:44:36 XXXXXXXXXXX kwin_x11[1002]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 13712, resource id: 654, major code: 14 (GetGeometry), minor code: 0
Oct 23 05:44:36 XXXXXXXXXXX rtkit-daemon[1032]: Successfully demoted thread 1031 of process 1031 (/usr/bin/pulseaudio).
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Starting Rotate log files...
Oct 23 05:44:36 XXXXXXXXXXX rtkit-daemon[1032]: Demoted 3 threads.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Starting Update locate database...
Oct 23 05:44:36 XXXXXXXXXXX Tor[20594]: Your system clock just jumped 36756 seconds forward; assuming established circuits no longer work.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Starting Update man-db cache...
Oct 23 05:44:36 XXXXXXXXXXX dhcpcd[1183]: eth0: carrier lost
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Started Rotate log files.
Oct 23 05:44:36 XXXXXXXXXXX nscd[23970]: 23970 monitoring file `/etc/passwd` (1)
Oct 23 05:44:36 XXXXXXXXXXX nscd[23970]: 23970 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX Tor[20594]: Heartbeat: Tor's uptime is 3:09 hours, with 2 circuits open. I've sent 495 kB and received 3.48 MB.
Oct 23 05:44:36 XXXXXXXXXXX Tor[20594]: Average packaged cell fullness: 64.433%. TLS write overhead: 6%
Oct 23 05:44:36 XXXXXXXXXXX nscd[23970]: 23970 monitored file `/etc/resolv.conf` was written to
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Stopping Name Service Cache Daemon...
Oct 23 05:44:36 XXXXXXXXXXX nscd[23970]: 23970 monitoring file `/etc/group` (3)
Oct 23 05:44:36 XXXXXXXXXXX nscd[23970]: 23970 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Started Verify integrity of password and group files.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Stopped Name Service Cache Daemon.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Starting Name Service Cache Daemon...
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring file `/etc/passwd` (1)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring file `/etc/group` (3)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring file `/etc/hosts` (4)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring file `/etc/resolv.conf` (5)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring file `/etc/services` (6)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring file `/etc/netgroup` (7)
Oct 23 05:44:36 XXXXXXXXXXX nscd[24585]: 24585 monitoring directory `/etc` (2)
Oct 23 05:44:36 XXXXXXXXXXX dhcpcd[1183]: eth0: deleting default route via XXXXXXXXXX
Oct 23 05:44:36 XXXXXXXXXXX avahi-daemon[841]: Withdrawing address record for XXXXXXXXXX on eth0.
Oct 23 05:44:36 XXXXXXXXXXX avahi-daemon[841]: Leaving mDNS multicast group on interface eth0.IPv4 with address XXXXXXXXXX.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Started Name Service Cache Daemon.
Oct 23 05:44:36 XXXXXXXXXXX avahi-daemon[841]: Interface eth0.IPv4 no longer relevant for mDNS.
Oct 23 05:44:36 XXXXXXXXXXX kernel: psmouse serio1: synaptics: queried max coordinates: x [..5652], y [..4628]
Oct 23 05:44:36 XXXXXXXXXXX kscreenlocker_greet[24416]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/user-identity
Oct 23 05:44:36 XXXXXXXXXXX kscreenlocker_greet[24416]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/system-log-out
Oct 23 05:44:36 XXXXXXXXXXX kscreenlocker_greet[24416]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/system-switch-user
Oct 23 05:44:36 XXXXXXXXXXX systemd-sleep[24434]: System resumed.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Started Suspend.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Stopped target Sleep.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Reached target Suspend.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
Oct 23 05:44:36 XXXXXXXXXXX systemd[1]: Stopped target Suspend.
Oct 23 05:44:36 XXXXXXXXXXX systemd-logind[707]: Operation finished.
Oct 23 05:44:37 XXXXXXXXXXX dhcpcd[1183]: eth0: carrier acquired
Oct 23 05:44:37 XXXXXXXXXXX dhcpcd[1183]: eth0: IAID 19:e3:e5:7f
Oct 23 05:44:37 XXXXXXXXXXX kernel: tg3 0000:09:00.0 eth0: Link is up at 1000 Mbps, full duplex
Oct 23 05:44:37 XXXXXXXXXXX kernel: tg3 0000:09:00.0 eth0: Flow control is on for TX and on for RX
Oct 23 05:44:37 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
Oct 23 05:44:37 XXXXXXXXXXX dhcpcd[1183]: eth0: rebinding lease of XXXXXXXXXX
Oct 23 05:44:37 XXXXXXXXXXX dhcpcd[1183]: eth0: probing static address XXXXXXXXXX/24
Oct 23 05:44:38 XXXXXXXXXXX systemd[1]: Started Update man-db cache.
Oct 23 05:44:38 XXXXXXXXXXX ntpd[1207]: Deleting interface #5 eth0, XXXXXXXXXX#123, interface stats: received=195, sent=195, dropped=0, active_time=48950 secs
Oct 23 05:44:38 XXXXXXXXXXX ntpd[1207]: 37.187.107.140 local addr XXXXXXXXXX -> <null>
Oct 23 05:44:38 XXXXXXXXXXX ntpd[1207]: 37.187.5.167 local addr XXXXXXXXXX -> <null>
Oct 23 05:44:38 XXXXXXXXXXX ntpd[1207]: 91.121.154.183 local addr XXXXXXXXXX -> <null>
Oct 23 05:44:38 XXXXXXXXXXX ntpd[1207]: 195.154.10.106 local addr XXXXXXXXXX -> <null>
Oct 23 05:44:39 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:39 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:39 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
Oct 23 05:44:39 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
Oct 23 05:44:42 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:42 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:42 XXXXXXXXXXX dhcpcd[1183]: eth0: leased XXXXXXXXXX for infinity
Oct 23 05:44:42 XXXXXXXXXXX dhcpcd[1183]: eth0: adding route to XXXXXXXXXX/XX
Oct 23 05:44:42 XXXXXXXXXXX avahi-daemon[841]: Joining mDNS multicast group on interface eth0.IPv4 with address XXXXXXXXXX.
Oct 23 05:44:42 XXXXXXXXXXX avahi-daemon[841]: New relevant interface eth0.IPv4 for mDNS.
Oct 23 05:44:42 XXXXXXXXXXX dhcpcd[1183]: eth0: adding default route via XXXXXXXXXX
Oct 23 05:44:42 XXXXXXXXXXX avahi-daemon[841]: Registering new address record for XXXXXXXXXX on eth0.IPv4.
Oct 23 05:44:42 XXXXXXXXXXX nscd[24585]: 24585 monitored file `/etc/resolv.conf` was written to
Oct 23 05:44:42 XXXXXXXXXXX systemd[1]: Stopping Name Service Cache Daemon...
Oct 23 05:44:42 XXXXXXXXXXX systemd[1]: Stopped Name Service Cache Daemon.
Oct 23 05:44:42 XXXXXXXXXXX systemd[1]: Starting Name Service Cache Daemon...
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring file `/etc/passwd` (1)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring directory `/etc` (2)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring file `/etc/group` (3)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring directory `/etc` (2)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring file `/etc/hosts` (4)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring directory `/etc` (2)
Oct 23 05:44:42 XXXXXXXXXXX systemd[1]: Started Name Service Cache Daemon.
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring file `/etc/resolv.conf` (5)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring directory `/etc` (2)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring file `/etc/services` (6)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring directory `/etc` (2)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring file `/etc/netgroup` (7)
Oct 23 05:44:42 XXXXXXXXXXX nscd[24661]: 24661 monitoring directory `/etc` (2)
Oct 23 05:44:42 XXXXXXXXXXX dhcpcd[1183]: eth0: removing route to XXXXXXXXXX/XX
Oct 23 05:44:43 XXXXXXXXXXX kdeinit5[912]: The X11 connection broke (error 1). Did the X11 server die?
Oct 23 05:44:43 XXXXXXXXXXX kdeinit5[915]: The X11 connection broke: I/O error (code 1)
Oct 23 05:44:43 XXXXXXXXXXX kactivitymanagerd[974]: The X11 connection broke (error 1). Did the X11 server die?
Oct 23 05:44:43 XXXXXXXXXXX kdeinit5[911]: kdeinit5: Fatal IO error: client killed
Oct 23 05:44:43 XXXXXXXXXXX kernel: kactivitymanage[974]: segfault at 7f443569cd10 ip 00007f44358e6881 sp 00007ffc84d67438 error 4 in libQt5Sql.so.5.5.0 (deleted)[7f44358d0000+41000]
Oct 23 05:44:43 XXXXXXXXXXX autossh[24494]: ssh exited with error status 255; restarting ssh
Oct 23 05:44:43 XXXXXXXXXXX kdeinit5[911]: kdeinit5: sending SIGHUP to children.
Oct 23 05:44:43 XXXXXXXXXXX autossh[24494]: starting ssh (count 2)
Oct 23 05:44:43 XXXXXXXXXXX kdeinit5[928]: The X11 connection broke (error 1). Did the X11 server die?
Oct 23 05:44:43 XXXXXXXXXXX autossh[24494]: ssh child pid is 24674
Oct 23 05:44:43 XXXXXXXXXXX kwalletd5[1464]: The X11 connection broke (error 1). Did the X11 server die?
Oct 23 05:44:43 XXXXXXXXXXX sudo[1576]: pam_unix(sudo:session): session closed for user root
Oct 23 05:44:43 XXXXXXXXXXX kglobalaccel5[967]: The X11 connection broke (error 1). Did the X11 server die?
Oct 23 05:44:43 XXXXXXXXXXX sddm[744]: Display server stopped.
Oct 23 05:44:43 XXXXXXXXXXX sddm[744]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Oct 23 05:44:43 XXXXXXXXXXX sddm[744]: Removing display ":0" ...
Oct 23 05:44:43 XXXXXXXXXXX sddm[744]: Adding new display on vt 1 ...
Oct 23 05:44:43 XXXXXXXXXXX sddm[744]: Display server starting...
Oct 23 05:44:43 XXXXXXXXXXX sddm[744]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{d5b7b766-0cae-41b2-92d8-ee082b16d9e2} -background none -noreset -displayfd 20 vt1
Oct 23 05:44:43 XXXXXXXXXXX systemd[865]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Oct 23 05:44:43 XXXXXXXXXXX systemd[865]: pulseaudio.service: Unit entered failed state.
Oct 23 05:44:43 XXXXXXXXXXX systemd[865]: pulseaudio.service: Failed with result 'exit-code'.
Oct 23 05:44:43 XXXXXXXXXXX pulseaudio[1031]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Oct 23 05:44:43 XXXXXXXXXXX pulseaudio[1031]: after 14 requests (14 known processed) with 0 events remaining.
Oct 23 05:44:43 XXXXXXXXXXX polkitd[938]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.28, object path /org/kde/PolicyKit1/AuthenticationAgent, locale ia_FR.UTF-8) (disconnected from bus)
Oct 23 05:44:43 XXXXXXXXXXX org.a11y.atspi.Registry[1924]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Oct 23 05:44:43 XXXXXXXXXXX org.a11y.atspi.Registry[1924]: after 168705 requests (168705 known processed) with 0 events remaining.
Oct 23 05:44:43 XXXXXXXXXXX org.kde.kuiserver[881]: kuiserver: Fatal IO error: client killed
Oct 23 05:44:43 XXXXXXXXXXX kdeinit5[911]: kdeinit5: sending SIGTERM to children.
Oct 23 05:44:43 XXXXXXXXXXX kdeinit5[911]: kdeinit5: Exit.
Oct 23 05:44:43 XXXXXXXXXXX kwin_x11[1002]: The X11 connection broke: I/O error (code 1)
Oct 23 05:44:43 XXXXXXXXXXX systemd[865]: pulseaudio.service: Service hold-off time over, scheduling restart.
Oct 23 05:44:43 XXXXXXXXXXX systemd[865]: Stopped Sound Service.
Oct 23 05:44:43 XXXXXXXXXXX systemd[865]: Started Sound Service.
Oct 23 05:44:43 XXXXXXXXXXX ntpd[1207]: Listen normally on 6 eth0 XXXXXXXXXX:123
Oct 23 05:44:43 XXXXXXXXXXX ntpd[1207]: new interface(s) found: waking up resolver
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:43 XXXXXXXXXXX pulseaudio[24682]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Oct 23 05:44:44 XXXXXXXXXXX systemd-coredump[24677]: Process 974 (kactivitymanage) of user 1000 dumped core.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Supervising 0 threads of 0 processes of 0 users.
Oct 23 05:44:44 XXXXXXXXXXX rtkit-daemon[1032]: Recovering from system lockup, not allowing further RT threads.
Oct 23 05:44:44 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
Oct 23 05:44:44 XXXXXXXXXXX systemd-coredump[24614]: Process 786 (Xorg) of user 0 dumped core.
Oct 23 05:44:46 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Display server started.
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Socket server starting...
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Socket server started.
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Greeter starting...
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Adding cookie to "/var/run/sddm/{d5b7b766-0cae-41b2-92d8-ee082b16d9e2}"
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Oct 23 05:44:46 XXXXXXXXXXX sddm-helper[24691]: [PAM] Starting...
Oct 23 05:44:46 XXXXXXXXXXX sddm-helper[24691]: [PAM] Authenticating...
Oct 23 05:44:46 XXXXXXXXXXX sddm-helper[24691]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Oct 23 05:44:46 XXXXXXXXXXX sddm-helper[24691]: [PAM] returning.
Oct 23 05:44:46 XXXXXXXXXXX systemd[1]: Created slice user-994.slice.
Oct 23 05:44:46 XXXXXXXXXXX systemd[1]: Starting User Manager for UID 994...
Oct 23 05:44:46 XXXXXXXXXXX systemd-logind[707]: New session c9 of user sddm.
Oct 23 05:44:46 XXXXXXXXXXX systemd[1]: Started Session c9 of user sddm.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Reached target Paths.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Starting Set Environment DBUS_SESSION_BUS_ADDRESS...
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Listening on Sound System.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Reached target Timers.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Started Set Environment DBUS_SESSION_BUS_ADDRESS.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Listening on D-Bus User Message Bus Socket.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Reached target Sockets.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Reached target Basic System.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Reached target Default.
Oct 23 05:44:46 XXXXXXXXXXX systemd[24693]: Startup finished in 37ms.
Oct 23 05:44:46 XXXXXXXXXXX systemd[1]: Started User Manager for UID 994.
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Greeter session started successfully
Oct 23 05:44:46 XXXXXXXXXXX sddm-greeter[24699]: Reading from "/usr/share/xsessions/plasma-mediacenter.desktop"
Oct 23 05:44:46 XXXXXXXXXXX sddm-greeter[24699]: Reading from "/usr/share/xsessions/plasma.desktop"
Oct 23 05:44:46 XXXXXXXXXXX sddm-greeter[24699]: Reading from "/usr/share/xsessions/failsafe.desktop"
Oct 23 05:44:46 XXXXXXXXXXX sddm-greeter[24699]: Connected to the daemon.
Oct 23 05:44:46 XXXXXXXXXXX sddm[744]: Message received from greeter: Connect
Oct 23 05:44:47 XXXXXXXXXXX sddm-greeter[24699]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is SDDM::GreeterApp(0x7fff9c8d62a0), parent's thread is QThread(0x1cb3580), current thread is QThread(0x1fc46d0)
Oct 23 05:44:47 XXXXXXXXXXX sddm-greeter[24699]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is SDDM::GreeterApp(0x7fff9c8d62a0), parent's thread is QThread(0x1cb3580), current thread is QThread(0x1fc46d0)
Oct 23 05:44:47 XXXXXXXXXXX sddm-greeter[24699]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is SDDM::GreeterApp(0x7fff9c8d62a0), parent's thread is QThread(0x1cb3580), current thread is QThread(0x1fc46d0)
Oct 23 05:44:47 XXXXXXXXXXX sddm-greeter[24699]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is SDDM::GreeterApp(0x7fff9c8d62a0), parent's thread is QThread(0x1cb3580), current thread is QThread(0x1fc46d0)
Oct 23 05:44:47 XXXXXXXXXXX sddm-greeter[24699]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Oct 23 05:44:47 XXXXXXXXXXX systemd[24693]: Started D-Bus User Message Bus.
Oct 23 05:44:47 XXXXXXXXXXX sddm-greeter[24699]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is SDDM::GreeterApp(0x7fff9c8d62a0), parent's thread is QThread(0x1cb3580), current thread is QThread(0x1fc46d0)
Oct 23 05:44:47 XXXXXXXXXXX sddm-greeter[24699]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Oct 23 05:44:49 XXXXXXXXXXX sddm-greeter[24699]: Message received from daemon: Capabilities
Oct 23 05:44:49 XXXXXXXXXXX sddm-greeter[24699]: Message received from daemon: HostName
Oct 23 05:44:56 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
Oct 23 05:44:58 XXXXXXXXXXX kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
Oct 23 05:44:58 XXXXXXXXXXX systemd[1]: Started Getty on tty2.
Oct 23 05:45:00 XXXXXXXXXXX systemd[1]: Started Update locate database.
[... then I login ...]
Oct 23 05:45:08 XXXXXXXXXXX login[24711]: pam_unix(login:session): session opened for user XXXXXXXXXXX by LOGIN(uid=0)

Do you have an idea? That would really help me a lot

Aurelien

hussam

Member

Registered: 2006-03-26

Posts: 572

Website

Re: KF 5 & Plasma

Since I upgraded from KDE4 to KF5, resume from suspend to RAM fails 50% of the time: SDDM displays the login screen instead of my screensaver lock screen, When it happens, I can briefly see one one of the tty (possibly tty1), before X is restarted. As you can guess, it's really annoying since suspend to RAM is useless if it's not reliable. It used to work very well w/ KDE4 on this computer (Dell Precision M6400).

Likely https://bugreports.qt.io/browse/QTBUG-42985

trapanator

Member

From: Italy

Registered: 2009-08-10

Posts: 151

Re: KF 5 & Plasma

Hi, I'm having Dolphin freezes after opening any image from SFTP location. Does it happen to you, too?

mareex

Member

From: Oldenburg, Germany

Registered: 2014-08-27

Posts: 28

Re: KF 5 & Plasma

Hi, I'm having Dolphin freezes after opening any image from SFTP location. Does it happen to you, too?

yes, sftp and fish is hanging here quite often. I think sftp is horribly broken. Cannot not even connect to sftp with my ssh-key.
Also each time when i open a document with libreoffice in a fish location and close that document afterwards, dolphin is going to freeze.

aurelieng

Member

Registered: 2010-02-02

Posts: 104

Re: KF 5 & Plasma

Since I upgraded from KDE4 to KF5, resume from suspend to RAM fails 50% of the time: SDDM displays the login screen instead of my screensaver lock screen, When it happens, I can briefly see one one of the tty (possibly tty1), before X is restarted. As you can guess, it's really annoying since suspend to RAM is useless if it's not reliable. It used to work very well w/ KDE4 on this computer (Dell Precision M6400).

Likely https://bugreports.qt.io/browse/QTBUG-42985

Thank you for the link. This bug seems to occur systematically. If it's the culprit, I wonder why 'only' about 50% of my resume attempts fail.

The last comment on that bug, 6 days ago, refers to a patch still under review for the Qt 5.6 branch. Am I right if I understand that it won't be solved until December, 8th?

Are you too having problems coming back from suspend to RAM?

Tromzy

Member

Registered: 2015-02-15

Posts: 166

Re: KF 5 & Plasma

Hi, I'm having Dolphin freezes after opening any image from SFTP location. Does it happen to you, too?

I have this when opening a remote LibreOffice file. I opened a bug report :

https://bugs.kde.org/show_bug.cgi?id=353037

Last edited by Tromzy (2015-10-23 14:39:29)

jaergenoth

Member

Registered: 2015-01-16

Posts: 85

Re: KF 5 & Plasma

Anyone else having problems with Dolphin freezing for 5-30 seconds when copying or moving files?
It happens every time I copy/move files around (partition to same partition, partition to different partition, hdd to different hdd, local to network).
Dolphin also freezes if I start Places > Network > Add Network Folder.
Kate freezes too, when saving to a network drive (sftp).

Edit:
Other problem is krunner crashing at every startup. Not a huge problem since it can restart itself. A minor annoyance.

Edit 2:
System Settings sometimes crashes when going to Desktop Behavior > Desktop Effects

Last edited by jaergenoth (2015-11-02 09:15:48)

The Infinity

Member

Registered: 2014-07-05

Posts: 91

Website

Re: KF 5 & Plasma

Yes, sometimes Dolphin is freezing for 1-3 seconds when copying files. Dolphin is also a bit slow when showing dirs with lots of sub dirs (detail view).
However, adding a network drive works for me.

---

AUR packages | GitHub page

afikl

Member

Registered: 2013-02-10

Posts: 6

Re: KF 5 & Plasma

Has anyone managed to get automatic spellchecking to work in Kate / Kile? It works just fine on-demand with a right-click, but incorrect words are not underlined on the fly even when "Automatic spell checking enabled by default" is checked.

fxlgore

Member

Registered: 2015-09-05

Posts: 30

Re: KF 5 & Plasma

Does anyone have installed another desktop?, i mean if i have plasma and i wanna try Xfce or something, will plasma continue work fine?

snack

Member

From: Italy

Registered: 2009-01-13

Posts: 866

Re: KF 5 & Plasma

Does anyone have installed another desktop?, i mean if i have plasma and i wanna try Xfce or something, will plasma continue work fine?

You can install any other desktop environment side by side with plasma, except for KDE4. I personally tried with Gnome and Lxqt and they give no conflict with plasma.

fxlgore

Member

Registered: 2015-09-05

Posts: 30

Re: KF 5 & Plasma

Does anyone have installed another desktop?, i mean if i have plasma and i wanna try Xfce or something, will plasma continue work fine?

You can install any other desktop environment side by side with plasma, except for KDE4. I personally tried with Gnome and Lxqt and they give no conflict with plasma.

Thanks, I wanna try installing Lxqt or cinnamon but  then uninstall them without problems to my plasma, i will...

desaparecido

Member

From: Liège, Belgium

Registered: 2010-03-14

Posts: 155

Re: KF 5 & Plasma

I'm using the following versions:

sddm 0.12.0-4
kactivities-frameworks 5.15.0-1
libkactivities4 4.13.3-1

Aurelien

hi, reading about your problem, I have a question: did you still needs libkactivities4 package? could be a conflict libs issue ? :-/ probably there's no problem but who knows :-)

---

KF5 & Plasma5 (git versions) - Awesome WM
ASUS Sabertooth 990FX - AMD FX8350 - ATI Radeon HD 7970
[testing] repo

kifuna

Member

Registered: 2015-01-29

Posts: 40

Re: KF 5 & Plasma

Hi,

I am not sure that this is the appropriate place for my problem, but today's updates of some plasma components want to remove kdebase-workspace and replace it by plasma-workspace. Currently, I am using the KDE4 desktop and would like to continue doing so, i.e., to avoid having to upgrade now to Plasma 5. Following the output of yaourt -Syu, it is plasma-nm (current version: 5.4.2-1 and to be installed: 5.4.3-1) that requires plasma-workspace.

Is there something that I can do?

Thanks,
kifuna

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,104

Re: KF 5 & Plasma

Hi,

I am not sure that this is the appropriate place for my problem, but today's updates of some plasma components want to remove kdebase-workspace and replace it by plasma-workspace. Currently, I am using the KDE4 desktop and would like to continue doing so, i.e., to avoid having to upgrade now to Plasma 5. Following the output of yaourt -Syu, it is plasma-nm (current version: 5.4.2-1 and to be installed: 5.4.3-1) that requires plasma-workspace.

Is there something that I can do?

The question is, why do you have plasma-nm installed if you aren't using Plasma 5?

kifuna

Member

Registered: 2015-01-29

Posts: 40

Re: KF 5 & Plasma

arojas, thanks a lot for this perfectly reasonable question! To be honest, I don't know; maybe it is a remnant of a test installation of Plasma 5 (from which I downgraded back to KDE4). However, I now removed this package and everything behaves normally again. Sometimes one thinks to complicated and easily oversees the easiest and most obvious solution.

theodore

Member

Registered: 2008-09-09

Posts: 151

Re: KF 5 & Plasma

hi guys, since the last update I am facing the following issue the Device Notifier alerts me about 0 B Removable media (empty floppy drives) at each login does anyone has similar issue? Making a quick research I found this bug report but it seems that it is old and not related to this kde version. I guess it is resurrected or something

Last edited by theodore (2015-11-13 10:56:13)

nierro

Member

From: Milan, Italy

Registered: 2011-09-02

Posts: 849

Re: KF 5 & Plasma

Are breeze-icons 5.16 more...colorful? Too much for my tastes (but they're *mine* obviously).
And what about task manager light blue highlighting? (http://postimg.org/image/koy5bbaf1/full/)
Are these bugs or features?

Thanks!

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,104

Re: KF 5 & Plasma

Are breeze-icons 5.16 more...colorful? Too much for my tastes (but they're *mine* obviously).
And what about task manager light blue highlighting? (http://postimg.org/image/koy5bbaf1/full/)
Are these bugs or features?

That's the new plasma 5.5 theme (which for some reason is shipped in kf5 instead of plasma). So it's a 'feature'

nierro

Member

From: Milan, Italy

Registered: 2011-09-02

Posts: 849

Re: KF 5 & Plasma

Ah i see, thanks!
And about noto fonts, i know they're gonna be default in plasma 5.5, but they don't ship a mono font. Is there a suggested font?
Thank you very much.

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,104

Re: KF 5 & Plasma

Ah i see, thanks!
And about noto fonts, i know they're gonna be default in plasma 5.5, but they don't ship a mono font. Is there a suggested font?
Thank you very much.

Oxygen is still the upstream default mono font

nierro

Member

From: Milan, Italy

Registered: 2011-09-02

Posts: 849

Re: KF 5 & Plasma

Ah ok! Again thank you very much

hifi25nl

Member

Registered: 2011-05-07

Posts: 263

Re: KF 5 & Plasma

I see that in 5.16 widget corners are not rounded. Can I change this to the previous behaviour?

sl1pkn07

Member

From: Spanishtán

Registered: 2010-03-30

Posts: 371

Re: KF 5 & Plasma

I dont know what, but install kf5 in [testing] break plasmashell, if revert all to [extra] works again

anyone have this problem? :S

steps:

enable testing
update the system (pacman -Syu)
close KDE and relogin with sddm or startx
get blackscreen (with cursor), and when launch plasmashell manually (DISPLAY=:0 plasmashell), gets 3 times signal 11
in dmesg: kactivitymanage[7272]: segfault at 7ffb30c23d10 ip 00007ffb30e6f881 sp 00007ffd6342e308 error 4 in libQt5Sql.so.5.5.1[7ffb30e59000+41000]
close startx or stop sddm
disable testing
downgrade with pacman -Syuu
relogin kde again
all works again