Rootserver Sponsor

webtropia"

Donations

Please support your operating system's further development:

donate"

Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
finottiOffline
Post subject: [solved] Panel Freezes  PostPosted: 30.11.2016, 17:39



Joined: 2010-09-12
Posts: 470

Status: Offline
I've just DUed today, after a while waiting for conflicts to resolve. (See: http://paste.debian.net/899889/)

Now, KDE's panel freezes. When I start the desktop it works fine, but after a little while it does not work anymore. Nor does right-clicking on the desktop or widgets. Right clicking on the window decoration works, as well a keyboard shortcuts and krunner (Alt+F2).

I've been looking for errors, but I could only find:

      Code:

# dmesg
[snip]
[  161.475258] kactivitymanage[1599]: segfault at 7fc06617acb0 ip 00007fc04c48c701 sp 00007ffefea841c8 error 4 in libQt5Sql.so.5.7.1[7fc04c476000+45000]
[ 1311.112756] traps: pasystray[3604] trap int3 ip:7f835d42f261 sp:7ffda7e34ce0 error:0
[ 1321.106033] kactivitymanage[2946]: segfault at 7f5b507d3cb0 ip 00007f5b348b3701 sp 00007ffd2fe0b948 error 4 in libQt5Sql.so.5.7.1[7f5b3489d000+45000]
[ 3289.115966] traps: pasystray[5943] trap int3 ip:7fa839e07261 sp:7ffe314e12c0 error:0
[ 3304.101459] kactivitymanage[5268]: segfault at 7f88aa500cb0 ip 00007f888a5bb701 sp 00007ffd77334808 error 4 in libQt5Sql.so.5.7.1[7f888a5a5000+45000]
[ 4003.086065] traps: pasystray[9704] trap int3 ip:7f51b2ff6261 sp:7ffea5dae320 error:0
[ 4031.264842] kactivitymanage[9011]: segfault at 7fb41d58dcb0 ip 00007fb401653701 sp 00007fff185bab48 error 4 in libQt5Sql.so.5.7.1[7fb40163d000+45000]
[ 4068.109197] traps: pasystray[13347] trap int3 ip:7ff8cbd96261 sp:7ffd32e241b0 error:0
[ 4068.295248] kactivitymanage[12675]: segfault at 7f00037c6cb0 ip 00007effe82b1701 sp 00007ffd943e91d8 error 4 in libQt5Sql.so.5.7.1[7effe829b000+45000]


These might correspond to all the "freezes" I had today, but I am not sure.

I tried changing the compositor from OpenGL 3.1 to XRender, as the former had given me problems in the past, but it did not help.

Here is the system info:

      Code:

root@finottim83[/home/finotti]# infobash -v3
Host/Kernel/OS  "finottim83" running Linux 4.8.0-11.slh.2-aptosid-amd64 x86_64 UEFI64 [ aptosid 2013-01 Ἑσπερίδες - kde-full - (201305050307) ]
CPU Info        8x Intel Core i7-4790 @ 8192 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 3717.114 MHz ]
Videocard       Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller  X.Org 1.19.0  [ 1920x1200@59.95hz, 1280x1024@60.02hz ]
Network cards   Intel I217-LM
Processes 324 | Uptime 2:07 | Memory 5057.6/31977.3MB | HDD Crucial_CT512M55,WDC WD5000AAKX-0,ATAPI-6 Bridge C Size 2012GB (21%used) | Client Shell | Infobash v3.50


Any help would be greatly appreciated.

(If this is an isolated problem (just me), feel free to move it from the "Upgrade Warnings" section.)

P.S.: Probably unrelated, but Firefox also hangs every once in a while after the upgrade. (Firefox itself was not upgraded.)


Last edited by finotti on 19.01.2017, 14:18; edited 1 time in total
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: Panel Freezes  PostPosted: 30.11.2016, 18:48



Joined: 2010-09-12
Posts: 470

Status: Offline
OK, I've unistalled pasystray (PulseAudio system tray icon), as it was not working anyway. (It was grayed out.)

But, the problem persists. I can see that the crash was at 13:26:43 (since my clock widget froze at that time), but I cannot find any error within seconds from that.

      Code:

root@finottim83[/home/finotti]# journalctl --since "2016-11-30 13:25:00"
-- Logs begin at Wed 2016-11-30 10:28:00 EST, end at Wed 2016-11-30 13:39:01 EST. --
Nov 30 13:25:20 finottim83 dbus[780]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 30 13:25:20 finottim83 dbus[780]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: kwalletd5 started
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: Migration agent starting...
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: old wallets were already migrated
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: Migration agent stop.
Nov 30 13:39:01 finottim83 CRON[22591]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 30 13:39:01 finottim83 CRON[22592]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Nov 30 13:39:01 finottim83 CRON[22591]: pam_unix(cron:session): session closed for user root


      Code:

root@finottim83[/home/finotti]# journalctl -p err -b
-- Logs begin at Wed 2016-11-30 10:28:00 EST, end at Wed 2016-11-30 13:39:01 EST. --
Nov 30 10:28:00 finottim83 kernel: tpm tpm0: A TPM error (6) occurred attempting to read a pcr value
Nov 30 10:28:01 finottim83 liblogging-stdlog[791]: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.23.0 t
Nov 30 10:28:03 finottim83 kernel: sd 7:0:0:0: [sdc] No Caching mode page found
Nov 30 10:28:03 finottim83 kernel: sd 7:0:0:0: [sdc] Assuming drive cache: write through
Nov 30 10:28:06 finottim83 /hpfax[1341]: [1341]: error: Failed to create /var/spool/cups/tmp/.hplip
Nov 30 10:28:06 finottim83 hp[1336]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Nov 30 10:28:06 finottim83 /hpfax[1341]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Nov 30 10:28:10 finottim83 /hp-systray[1643]: hp-systray[1643]: error: option -s not recognized
Nov 30 10:28:13 finottim83 spice-vdagent[2249]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 10:30:43 finottim83 pulseaudio[1575]: [pulseaudio] module.c: Module "module-device-manager" should be loaded once at most. Re
Nov 30 10:30:43 finottim83 /hp-systray[2974]: hp-systray[2974]: error: option -s not recognized
Nov 30 10:30:46 finottim83 spice-vdagent[3611]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 10:50:06 finottim83 pulseaudio[5280]: [pulseaudio] pid.c: Daemon already running.
Nov 30 10:50:06 finottim83 /hp-systray[5308]: hp-systray[5308]: error: option -s not recognized
Nov 30 10:50:10 finottim83 spice-vdagent[5946]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 11:25:08 finottim83 pulseaudio[9030]: [pulseaudio] pid.c: Daemon already running.
Nov 30 11:25:08 finottim83 /hp-systray[9054]: hp-systray[9054]: error: option -s not recognized
Nov 30 11:25:12 finottim83 spice-vdagent[9712]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 11:35:15 finottim83 pulseaudio[8980]: [pulseaudio] module.c: Module "module-device-manager" should be loaded once at most. Re
Nov 30 11:35:15 finottim83 /hp-systray[12704]: hp-systray[12704]: error: option -s not recognized
Nov 30 11:35:20 finottim83 spice-vdagent[13354]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 11:37:15 finottim83 pulseaudio[13676]: [pulseaudio] pid.c: Daemon already running.
Nov 30 11:37:15 finottim83 /hp-systray[13709]: hp-systray[13709]: error: option -s not recognized
Nov 30 11:37:17 finottim83 spice-vdagent[14324]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 13:19:52 finottim83 pulseaudio[13630]: [pulseaudio] module.c: Module "module-device-manager" should be loaded once at most. R
Nov 30 13:19:53 finottim83 /hp-systray[18186]: hp-systray[18186]: error: option -s not recognized
Nov 30 13:19:59 finottim83 spice-vdagent[18827]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 13:24:13 finottim83 pulseaudio[20643]: [pulseaudio] pid.c: Daemon already running.
Nov 30 13:24:13 finottim83 /hp-systray[20662]: hp-systray[20662]: error: option -s not recognized
Nov 30 13:24:15 finottim83 spice-vdagent[21288]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0


Here is the output since my last login in KDE:

      Code:

Nov 30 13:24:12 finottim83 sddm-greeter[20423]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 30 13:24:12 finottim83 sddm[929]: Message received from greeter: Login
Nov 30 13:24:12 finottim83 sddm[929]: Reading from "/usr/share/xsessions/plasma.desktop"
Nov 30 13:24:12 finottim83 sddm[929]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
Nov 30 13:24:12 finottim83 sddm-helper[20440]: [PAM] Starting...
Nov 30 13:24:12 finottim83 sddm-helper[20440]: [PAM] Authenticating...
Nov 30 13:24:12 finottim83 sddm-helper[20440]: [PAM] Preparing to converse...
Nov 30 13:24:12 finottim83 sddm-helper[20440]: [PAM] Conversation with 1 messages
Nov 30 13:24:12 finottim83 sddm-helper[20440]: [PAM] returning.
Nov 30 13:24:12 finottim83 sddm[929]: Authenticated successfully
Nov 30 13:24:12 finottim83 sddm-greeter[20423]: Message received from daemon: LoginSucceeded
Nov 30 13:24:12 finottim83 systemd-logind[792]: New session 34 of user finotti.
Nov 30 13:24:12 finottim83 systemd[1]: Started Session 34 of user finotti.
Nov 30 13:24:12 finottim83 sddm-helper[20440]: pam_unix(sddm:session): session opened for user finotti by (uid=0)
Nov 30 13:24:12 finottim83 sddm-helper[20440]: pam_systemd(sddm:session): Cannot create session: Already running in a session
Nov 30 13:24:12 finottim83 sddm-helper[20440]: Starting: "/etc/sddm/Xsession" "/usr/bin/startkde"
Nov 30 13:24:12 finottim83 sddm-helper[20441]: Adding cookie to "/home/finotti/.Xauthority"
Nov 30 13:24:12 finottim83 sddm[929]: Session started
Nov 30 13:24:12 finottim83 sddm-helper[20420]: [PAM] Ended.
Nov 30 13:24:12 finottim83 sddm[929]: Auth: sddm-helper exited successfully
Nov 30 13:24:12 finottim83 sddm[929]: Greeter stopped.
Nov 30 13:24:12 finottim83 udev-acl.ck[20505]: g_slice_set_config: assertion 'sys_page_size == 0' failed
Nov 30 13:24:12 finottim83 console-kit-daemon[1419]: missing action
Nov 30 13:24:13 finottim83 pulseaudio[20591]: [pulseaudio] pid.c: Stale PID file, overwriting.
Nov 30 13:24:13 finottim83 polkitd(authority=local)[1083]: Registered Authentication Agent for unix-session:34 (system bus name :1.4
Nov 30 13:24:13 finottim83 pulseaudio[20643]: [pulseaudio] pid.c: Daemon already running.
Nov 30 13:24:13 finottim83 org.kde.kuiserver[20478]: QDBusConnection: session D-Bus connection created before QCoreApplication. Appl
Nov 30 13:24:13 finottim83 org.kde.kuiserver[20478]: QDBusConnection: session D-Bus connection created before QCoreApplication. Appl
Nov 30 13:24:13 finottim83 /hp-systray[20662]: hp-systray[20662]: error: option -s not recognized
Nov 30 13:24:13 finottim83 dbus[780]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Nov 30 13:24:13 finottim83 dbus[780]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Nov 30 13:24:13 finottim83 org.kde.KScreen[20478]: kscreen.xrandr: Connected output 67 to CRTC 63
Nov 30 13:24:13 finottim83 org.kde.KScreen[20478]: kscreen.xrandr: Connected output 70 to CRTC 64
Nov 30 13:24:13 finottim83 org.kde.KScreen[20478]: kscreen.xcb.helper: Detected XRandR 1.5
Nov 30 13:24:13 finottim83 org.kde.KScreen[20478]: kscreen.xcb.helper: Event Base:  89
Nov 30 13:24:13 finottim83 org.kde.KScreen[20478]: kscreen.xcb.helper: Event Error:  147
Nov 30 13:24:15 finottim83 spice-vdagent[21288]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 30 13:24:15 finottim83 org.a11y.atspi.Registry[21291]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Regis
Nov 30 13:24:15 finottim83 dbus[780]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 30 13:24:15 finottim83 dbus[780]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.
Nov 30 13:24:15 finottim83 obexd[21303]: OBEX daemon 5.43
Nov 30 13:24:25 finottim83 su[20705]: Successful su for root by finotti
Nov 30 13:24:25 finottim83 su[20705]: + /dev/pts/3 finotti:root
Nov 30 13:24:25 finottim83 su[20705]: pam_unix(su:session): session opened for user root by finotti(uid=1000)
Nov 30 13:24:25 finottim83 su[20705]: pam_systemd(su:session): Cannot create session: Already running in a session
Nov 30 13:25:20 finottim83 dbus[780]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Nov 30 13:25:20 finottim83 dbus[780]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: kwalletd5 started
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: Migration agent starting...
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: old wallets were already migrated
Nov 30 13:25:20 finottim83 org.kde.kwalletd5[20478]: Migration agent stop.
Nov 30 13:39:01 finottim83 CRON[22591]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 30 13:39:01 finottim83 CRON[22592]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Nov 30 13:39:01 finottim83 CRON[22591]: pam_unix(cron:session): session closed for user root


No errors in dmesg, ker.log, X.0.log, messages...
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Panel Freezes  PostPosted: 30.11.2016, 22:24



Joined: 2010-08-25
Posts: 949

Status: Offline
This is indeed a problem (so far I don't really think it's SQL related though) and seems to have been introduced by the last batch of KDE updates (which coincided with the X.org transition, but the later doesn't appear to be responsible). X11forwarding seems to trigger it more quickly, but that isn't (by far) the only trigger.

While certainly not a good bugreport, far from it, it seems t have been reported under #846389
 
 View user's profile Send private message  
Reply with quote Back to top
samohtOffline
Post subject: RE: Panel Freezes  PostPosted: 01.12.2016, 09:19



Joined: 2010-09-12
Posts: 17
Location: Berlin
Status: Offline
Many thanks to @finotti for reporting, and @slh for comment.
As siduction user I confirm @finotti's findings:
random (?) plasma panel freeze, but still working: logout via hotkey ..., window management via mouse ...
Relogin sometimes works, sometimes only after restarting runlevel 5, sometimes login stops after kde icon on black background appearence not reaching my desktop ...
These bugs occured on my machine only after installing the recent plasma release, thus I confirm @slh's comment.
I did not know, where to look for corresponding logfiles. And did not post bugreports to Debian, KDE or siduction forum, resp.
Greetings,
Tom
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: Panel Freezes  PostPosted: 01.12.2016, 18:50



Joined: 2010-09-12
Posts: 470

Status: Offline
The behavior seems very random. Once it happened when I opened okular. So, I restarted KDE and opened okular, and it did not happen. Then I opened Emacs, and it happened. So, I restarted KDE and opened Emacs again, but it did not happen. Opened okular and it did not happen.

Today after many hours without problems, I opened Emacs and it happened...
 
 View user's profile Send private message  
Reply with quote Back to top
samohtOffline
Post subject: RE: Panel Freezes  PostPosted: 02.12.2016, 18:01



Joined: 2010-09-12
Posts: 17
Location: Berlin
Status: Offline
There 's a bug report on kde bugzilla matching our descriptions:
https://bugs.kde.org/show_bug.cgi?id=373131
Greetings,
Tom
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: Panel Freezes  PostPosted: 14.12.2016, 17:50



Joined: 2010-09-12
Posts: 470

Status: Offline
OK, the bug reports are still there, but I haven't had a freeze in a few days... If some update fixed it, I have no idea which one. (I don't remember seeing plasma updates recently.) On the other hand, the freezes were so random, that maybe it's just been luck. I am not sure if I should mark this as solved (and if I should DU my other systems). I will wait a few more details and report again (unless someone knows it has been indeed fixed).
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Panel Freezes  PostPosted: 14.12.2016, 18:55



Joined: 2010-08-25
Posts: 949

Status: Offline
No, the bug is still open - I can pretty much reliably trigger it by copying files for longer times (either multi-GB files locally or uploading files via kio-slaves over a slow uplink or by just using X11Forwarding via ssh, no these aren't the only occurences, but the most easily reproducable ones). Personally for me, this is just one more nail for KDE5's coffin. I still haven't quite managed to move to another desktop environment, but there are only small nits remaining (like a pretty braindead strategy to place new windows on the screen, no kio-slaves (yes, this is still one of KDE's major advantages), no screen locking without xscreensaver being installed (no, I don't want that) - small things, but very annoying for daily full time use).
 
 View user's profile Send private message  
Reply with quote Back to top
samohtOffline
Post subject: RE: Panel Freezes  PostPosted: 17.12.2016, 08:34



Joined: 2010-09-12
Posts: 17
Location: Berlin
Status: Offline
There is hope now: Wink
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23847025#25
      Quote:
xorg-server (2:1.19.0-3) unstable; urgency=medium
...
* Cherry-pick upstream commit d6da2086951,
Revert "damage: Make damageRegionProcessPending take a damage not a
drawable". Fixes a crash caused by trying to free an invalid pointer.
Closes: #847025, #848321.

-- Emilio Pozuelo Monfort <pochu@debian.org> Fri, 16 Dec 2016 19:39:45 +0100

Greetings
Tom
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Panel Freezes  PostPosted: 17.12.2016, 21:59



Joined: 2010-08-25
Posts: 949

Status: Offline
Hope perhaps, but only the false, short lived, kind - plasma still freezes still within seconds when poking it.

Given that I have absolutely no such problems using a different desktop environment, I find it hard not to blame KDE5.
 
 View user's profile Send private message  
Reply with quote Back to top
samohtOffline
Post subject: RE: Panel Freezes  PostPosted: 19.12.2016, 08:20



Joined: 2010-09-12
Posts: 17
Location: Berlin
Status: Offline
Confirm. Annoying bug did not disappear.
Greetings
Tom
 
 View user's profile Send private message  
Reply with quote Back to top
piperOffline
Post subject: RE: Panel Freezes  PostPosted: 02.01.2017, 12:40
Moderator


Joined: 2010-09-11
Posts: 481
Location: cheektowaga, ny
Status: Offline
I have solved this on my secondary machine

      Code:
apt remove --purge xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-radeon


rebooted and no more lockups

      Code:
System:    Host: x2 Kernel: 4.9.0-towo.2-siduction-amd64 x86_64 (64 bit) Console: tty 2
           Distro: siduction 16.1.0 Patience - kde - (201701010034)
Machine:   Device: desktop Mobo: Gigabyte model: M61PM-S2 BIOS: Award v: F8 date: 10/05/2007
CPU:       Dual core AMD Athlon 64 X2 4200+ (-MCP-) cache: 1024 KB
           clock speeds: max: 2200 MHz 1: 1000 MHz 2: 1000 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550]
           Display Server: X.org 1.19.0 drivers: modesetting (unloaded: fbdev,vesa)

_________________
debian sid | apt-get into it
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: Panel Freezes  PostPosted: 02.01.2017, 20:56



Joined: 2010-09-12
Posts: 470

Status: Offline
FWIW, in my system with the intel driver, piper's suggestion did not work...
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Panel Freezes  PostPosted: 02.01.2017, 22:35



Joined: 2010-08-25
Posts: 949

Status: Offline
Using the fallback VESA drivers isn't a good solution with AMD graphics cards (the equivalent goes for nouveau and intel as well) anyways, actually it's among the worst choices possible (no power/ heat management, no h/w acceleration, less choices for screen resolutions, etc.). It's sad that KDE5 tries more to behave like a 3d ego-shooter, than just like a friggin' desktop manager - none of these problems exist when using a different desktop environment.
 
 View user's profile Send private message  
Reply with quote Back to top
towoOffline
Post subject: RE: Panel Freezes  PostPosted: 03.01.2017, 06:29



Joined: 2010-09-13
Posts: 516
Location: Pößneck / Thüringen
Status: Offline
The modesetting driver is not a fallback to VESA. And it should work for all cards, which supports KMS,

_________________
      Code:

System:    Host: Defiant Kernel: 4.9.1-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: Cinnamon 3.2.7
           Distro: siduction 13.2.0 December - xfce - (201312310323)
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio