You are not logged in.

#1 2013-02-14 15:22:13

ayr0
Member
Registered: 2010-08-12
Posts: 85

KDE 4.10 complete crash

Hi,

I am experiencing a very strange problem.  At seemingly random times, KDE 4.10 will complete die and I am sent back to KDM.  Depending on the day, it has happened up to 4 times a day!  It is very frustrating because it is like pulling the plug and I lose _everything_ that I had open (browser tabs, any unsaved work, etc). The most information that I've been able to gather comes from .xessesion-errors

"/org/freedesktop/UDisks2/drives/SD04G_0xb0032353" : property "Table" does not exist 
ksmserver(3824) ScreenLocker::LockWindow::x11Event: CreateNotify: 27349950
ksmserver(3824) ScreenLocker::KSldApp::doUnlock: Grab Released
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabButton.qml:111:5: QML QObject_QML_117: Binding loop detected for property "portrait"
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/Notifications.qml:186:17: QML TabButton: Binding loop detected for property "implicitHeight"
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/Notifications.qml:186:17: QML TabButton: Binding loop detected for property "implicitHeight"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabButton.qml:111:5: QML QObject_QML_117: Binding loop detected for property "portrait"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabButton.qml:111:5: QML QObject_QML_117: Binding loop detected for property "portrait"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabButton.qml:111:5: QML QObject_QML_117: Binding loop detected for property "portrait"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabButton.qml:111:5: QML QObject_QML_117: Binding loop detected for property "portrait"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabButton.qml:111:5: QML QObject_QML_117: Binding loop detected for property "portrait"
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
file:///usr/lib/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:189:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:189:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Binding loop detected for property "height"
plasma-desktop(3843)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
plasma-desktop(3843)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
synaptiks: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
kded4: Fatal IO error: client killed
kwin: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
QProcess: Destroyed while process is still running.
kactivitymanagerd: Fatal IO error: client killed
xcb_connection_has_error() returned true
[29639:29639:0214/001617:ERROR:chrome_browser_main_x11.cc(62)] X IO error received (X server probably went away)
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
kDebugStream called after destruction (from void Jobs::Encryption::Private::Encfs::unmountAll() file /build/src/kactivities-4.10.0/src/service/jobs/encryption/private/Encfs.cpp line 90)
Unmounting everything 
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.

The interesting bit is at the end.  Everything in KDE seems to die at once with a Fatal IO error.  Is anyone else experiencing this?

What logs should I look for the get more information?

EDIT: My graphics chip is Intel 3000.  I'm not sure why my system is trying to load libvdpau_nvidia.so

Last edited by ayr0 (2013-02-14 15:28:05)

Offline

#2 2013-02-14 15:37:42

Awebb
Member
Registered: 2010-05-06
Posts: 4,437

Re: KDE 4.10 complete crash

Anything that is compiled with possible vdpau support, will look for libvdpau. If it cannot find the library, it will simply ignore it. Most of the time at least.

Offline

#3 2013-02-14 21:16:34

LordChaos73
Member
From: .nl
Registered: 2008-11-11
Posts: 118

Re: KDE 4.10 complete crash

Have you tried using KDE with a new (temporary) user to see if the issue still persists?
Have you upgraded KDE or is this a fresh install?

I have the same graphics chip, I use the intel (i915) driver with sna acceleration enabled and KDE is rock stable for me.

[ericd@vaiopro13 ~]$ cat /etc/X11/xorg.conf.d/20-intel.conf 
Section "Device"
        Identifier "Intel Graphics"
        Driver "intel" 
        Option "Accelmethod" "sna" 
EndSection

Last edited by LordChaos73 (2013-02-14 21:20:20)

Offline

#4 2013-02-15 01:43:58

ayr0
Member
Registered: 2010-08-12
Posts: 85

Re: KDE 4.10 complete crash

Some new information.  I figured out how to get info from systemd journal.  Some thing is causing X to crash.

Feb 14 18:30:30 think systemd[1]: Started Suspend.
Feb 14 18:30:30 think systemd[1]: Service sleep.target is not needed anymore. Stopping.
Feb 14 18:30:30 think systemd[1]: Stopping Sleep.
Feb 14 18:30:30 think systemd[1]: Stopped target Sleep.
Feb 14 18:30:30 think systemd[1]: Starting Suspend.
Feb 14 18:30:30 think systemd[1]: Reached target Suspend.
Feb 14 18:30:31 think kernel: firewire_core 0000:0d:00.3: rediscovered device fw0
Feb 14 18:30:31 think kernel: mmc0: new ultra high speed SDR50 SDHC card at address 0007
Feb 14 18:30:31 think kernel: mmcblk0: mmc0:0007 SD04G 3.70 GiB 
Feb 14 18:30:31 think kernel:  mmcblk0: p1
Feb 14 18:30:33 think kernel: ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D3
Feb 14 18:30:34 think kernel: ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D3
Feb 14 18:30:38 think kernel: iwlwifi 0000:03:00.0: >L1 Disabled; Enabling L0S
Feb 14 18:30:38 think kernel: iwlwifi 0000:03:00.0: >Radio type=0x1-0x2-0x0
Feb 14 18:30:38 think kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 14 18:30:45 think wicd[361]: dhcpcd[30027]: dhcpcd not running
Feb 14 18:30:45 think dhcpcd[30027]: dhcpcd not running
Feb 14 18:30:45 think kernel: iwlwifi 0000:03:00.0: >L1 Disabled; Enabling L0S
Feb 14 18:30:45 think kernel: iwlwifi 0000:03:00.0: >Radio type=0x1-0x2-0x0
Feb 14 18:30:45 think kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 14 18:30:45 think wicd[361]: Failed to connect to non-global ctrl_ifname: wlan0  error: No such file or directory
Feb 14 18:30:45 think wicd[361]: dhcpcd[30035]: dhcpcd not running
Feb 14 18:30:45 think dhcpcd[30035]: dhcpcd not running
Feb 14 18:30:45 think kernel: iwlwifi 0000:03:00.0: >L1 Disabled; Enabling L0S
Feb 14 18:30:45 think kernel: iwlwifi 0000:03:00.0: >Radio type=0x1-0x2-0x0
Feb 14 18:30:46 think kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 14 18:30:46 think wicd[361]: Failed to connect to non-global ctrl_ifname: wlan0  error: No such file or directory
Feb 14 18:30:48 think kernel: wlan0: authenticate with b0:48:7a:c9:ba:c0
Feb 14 18:30:48 think kernel: wlan0: send auth to b0:48:7a:c9:ba:c0 (try 1/3)
Feb 14 18:30:48 think kernel: wlan0: authenticated
Feb 14 18:30:48 think kernel: wlan0: waiting for beacon from b0:48:7a:c9:ba:c0
Feb 14 18:30:48 think kernel: wlan0: associate with b0:48:7a:c9:ba:c0 (try 1/3)
Feb 14 18:30:48 think kernel: wlan0: RX AssocResp from b0:48:7a:c9:ba:c0 (capab=0x431 status=0 aid=1)
Feb 14 18:30:48 think kernel: wlan0: associated
Feb 14 18:30:48 think kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 14 18:30:49 think dhcpcd[30071]: version 5.6.4 starting
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: sending IPv6 Router Solicitation
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: sendmsg: Cannot assign requested address
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: rebinding lease of 10.24.66.136
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: NAK: from 192.168.1.1
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: sending IPv6 Router Solicitation
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: sendmsg: Cannot assign requested address
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: broadcasting for a lease
Feb 14 18:30:49 think avahi-daemon[400]: Registering new address record for fe80::8e70:5aff:fe49:6ca0 on wlan0.*.
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: offered 192.168.1.100 from 192.168.1.1
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: acknowledged 192.168.1.100 from 192.168.1.1
Feb 14 18:30:49 think dhcpcd[30071]: wlan0: checking for 192.168.1.100
Feb 14 18:30:53 think dhcpcd[30071]: wlan0: sending IPv6 Router Solicitation
Feb 14 18:30:54 think dhcpcd[30071]: wlan0: leased 192.168.1.100 for 7200 seconds
Feb 14 18:30:54 think avahi-daemon[400]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.100.
Feb 14 18:30:54 think avahi-daemon[400]: New relevant interface wlan0.IPv4 for mDNS.
Feb 14 18:30:54 think avahi-daemon[400]: Registering new address record for 192.168.1.100 on wlan0.IPv4.
Feb 14 18:30:54 think dhcpcd[30071]: forked to background, child pid 30198
Feb 14 18:30:57 think dhcpcd[30198]: wlan0: sending IPv6 Router Solicitation
Feb 14 18:30:58 think systemd-coredump[30225]: Process 841 (X) dumped core.
Feb 14 18:30:58 think acpid[358]: client 841[0:0] has disconnected
Feb 14 18:30:58 think kdm[783]: X server for display :0 terminated unexpectedly
Feb 14 18:30:58 think polkitd[727]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.23, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Feb 14 18:30:58 think kdm[1948]: :0[1948]: pam_unix(kde:session): session closed for user ----
Feb 14 18:30:58 think acpid[358]: client connected from 30231[0:0]
Feb 14 18:30:58 think acpid[358]: 1 client rule loaded
Feb 14 18:30:58 think colord[3799]: Profile removed: icc-de30e8075ed10861888f6bb33a9e10c2
Feb 14 18:30:58 think colord[3799]: Profile removed: icc-8231b0e3ec6c8b1053771956c0a70272
Feb 14 18:30:58 think pulseaudio[30232]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
Feb 14 18:30:58 think rtkit-daemon[4092]: Successfully made thread 30242 of process 30242 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 14 18:30:58 think rtkit-daemon[4092]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 18:31:04 think pulseaudio[30242]: [pulseaudio] pid.c: Stale PID file, overwriting.
Feb 14 18:31:04 think acpid[358]: client 30231[0:0] has disconnected
Feb 14 18:31:04 think dhcpcd[30198]: wlan0: sending IPv6 Router Solicitation
Feb 14 18:31:04 think dhcpcd[30198]: wlan0: no IPv6 Routers available
Feb 14 18:31:04 think pulseaudio[30242]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-jWZ2Vyt1gx: Connection refused
Feb 14 18:31:04 think pulseaudio[30242]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: ""): initialization failed.
Feb 14 18:31:04 think pulseaudio[30242]: [pulseaudio] main.c: Module load failed.
Feb 14 18:31:04 think pulseaudio[30242]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-jWZ2Vyt1gx: Connection refused
Feb 14 18:31:04 think pulseaudio[30242]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-jWZ2Vyt1gx: Connection refused

Last edited by ayr0 (2013-02-15 01:48:19)

Offline

#5 2013-02-15 05:57:49

chx
Member
Registered: 2011-05-28
Posts: 95

Re: KDE 4.10 complete crash

Yes X crashes for me too, but looking at https://bugs.archlinux.org/task/33796 and knowing that many of us with Sandy Bridge CPUs didn't upgrade the kernel because of the heat issue in https://bbs.archlinux.org/viewtopic.php?id=150743 I can't stop wondering whether it's the "old" kernel. ayr0, what's your kernel version? I am on 3.5.6-1, that bug report is on 3.6.11-1.

I will dowgrade xf86-video-intel to 2.20 something and hope that fixes it.

Although rolling release is great, having IgnorePkg is also great smile I am now at

IgnorePkg   = linux linux-headers hplip hplip-plugin skype xf86-video-intel

Last edited by chx (2013-02-15 06:05:02)

Offline

#6 2013-02-15 09:26:34

LordChaos73
Member
From: .nl
Registered: 2008-11-11
Posts: 118

Re: KDE 4.10 complete crash

Are you both using uxa or sna acceleration ?

Offline

#7 2013-02-15 17:07:54

ayr0
Member
Registered: 2010-08-12
Posts: 85

Re: KDE 4.10 complete crash

My kernel version is 3.5.6-1.  I have avoided upgrading my kernel because my system experienced the power/heat issue that the Thinkpads seem to be having lately.

My gfx driver is xf86-video-intel 2.21.2-1.  X has crashed regularly since 2.20.5 with either sna or uxa (doesn't make a difference).

At first I thought it was a problem with KDE 4.9.  I didn't experience these crashes near as often in 4.8 and it seemed to be specific to KDE (I've not had X crash in any other DE).  I read that disabling the OpenGL2 shaders might solve the problem.  No luck.  I disabled most of the non-essential kwin effects (blur, thumbnails, etc).  Still no change.

X crashed again this morning and the very last things in the log are messages from wicd and dhcpcd.  I've been trying to track down this problem since upgrading to KDE 4.9.  I've run out of ideas, and it is a very anti-productive behavior for a work laptop.

I've noticed that all the crashes seem to happen during a keystroke.  Doesn't seem to matter which key, but they all seem to happen during or immediately after a keystroke.

Offline

#8 2013-02-15 19:34:57

seth
Member
Registered: 2012-09-03
Posts: 17

Re: KDE 4.10 complete crash

you'll likely find backtraces of X11 in /var/log/Xorg.*.log and they'll hint you what crashes the server. usually the graphics driver and in that case likely because of the gap between X11 driver and kernel module  (despite 2.20.5 is 2012-08-27 and your kernel -nearly, there's no 3.5.6-1 in the history - is 2012-09-16, the timeframe is still quite tight)
=> pot. solution is to downgrade xf86-video-intel and intel-dri

xsession errors are worthless. if X dies, all dies with it.

Offline

#9 2013-02-15 20:14:19

ayr0
Member
Registered: 2010-08-12
Posts: 85

Re: KDE 4.10 complete crash

Here is the message from Xorg.0.log.  Looks like an intel driver problem after all.

[ 21657.788] (EE) 
[ 21657.788] (EE) Backtrace:
[ 21657.788] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a416]
[ 21657.788] (EE) 1: /usr/bin/X (0x400000+0x18e269) [0x58e269]
[ 21657.789] (EE) 2: /usr/lib/libpthread.so.0 (0x7f3474105000+0xf1e0) [0x7f34741141e0]
[ 21657.789] (EE) 3: /usr/lib/libpixman-1.so.0 (0x7f3473c61000+0x82a8b) [0x7f3473ce3a8b]
[ 21657.789] (EE) 4: /usr/lib/libpixman-1.so.0 (0x7f3473c61000+0x82b86) [0x7f3473ce3b86]
[ 21657.789] (EE) 5: /usr/lib/libpixman-1.so.0 (pixman_image_composite32+0x459) [0x7f3473c6c349]
[ 21657.789] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f34718ce000+0x94e73) [0x7f3471962e73]
[ 21657.789] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f34718ce000+0x954f7) [0x7f34719634f7]
[ 21657.789] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f34718ce000+0x67520) [0x7f3471935520]
[ 21657.789] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f34718ce000+0x678f5) [0x7f34719358f5]
[ 21657.789] (EE) 10: /usr/bin/X (0x400000+0x1141f9) [0x5141f9]
[ 21657.789] (EE) 11: /usr/bin/X (0x400000+0x10d174) [0x50d174]
[ 21657.789] (EE) 12: /usr/bin/X (0x400000+0x37e51) [0x437e51]
[ 21657.789] (EE) 13: /usr/bin/X (0x400000+0x2695a) [0x42695a]
[ 21657.789] (EE) 14: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f3472f91a15]
[ 21657.789] (EE) 15: /usr/bin/X (0x400000+0x26c9d) [0x426c9d]
[ 21657.789] (EE) 
[ 21657.789] (EE) Bus error at address 0x7f345fa44400
[ 21657.789] 
Fatal server error:
[ 21657.789] Caught signal 7 (Bus error). Server aborting
[ 21657.789] 
[ 21657.789] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[ 21657.789] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 21657.789] (EE) 

Offline

#10 2013-02-15 20:21:54

ayr0
Member
Registered: 2010-08-12
Posts: 85

Re: KDE 4.10 complete crash

seth wrote:

you'll likely find backtraces of X11 in /var/log/Xorg.*.log and they'll hint you what crashes the server. usually the graphics driver and in that case likely because of the gap between X11 driver and kernel module  (despite 2.20.5 is 2012-08-27 and your kernel -nearly, there's no 3.5.6-1 in the history - is 2012-09-16, the timeframe is still quite tight)
=> pot. solution is to downgrade xf86-video-intel and intel-dri

xsession errors are worthless. if X dies, all dies with it.

I got the 3.5.6-1 packages from here
http://arm.konnichi.com/2012/10/10/core/os/x86_64/

I can try to use the xf86-video-intel and intel-dri from this day as well...but these are built against Mesa 8.

Last edited by ayr0 (2013-02-15 20:22:52)

Offline

#11 2013-02-15 21:32:00

chx
Member
Registered: 2011-05-28
Posts: 95

Re: KDE 4.10 complete crash

I downgraded to http://arm.konnichi.com/2013/02/02/extra/os/x86_64/ this xf86-video-intel now it's 2.20.19-1 and it's stable as a rock. sna yes.

Last edited by chx (2013-02-15 21:34:09)

Offline

#12 2013-02-15 22:08:00

ayr0
Member
Registered: 2010-08-12
Posts: 85

Re: KDE 4.10 complete crash

chx wrote:

I downgraded to http://arm.konnichi.com/2013/02/02/extra/os/x86_64/ this xf86-video-intel now it's 2.20.19-1 and it's stable as a rock. sna yes.

I downgraded as well.  It was still in my pkg cache.  I'll keep an eye on it and post any further errors.

Offline

#13 2013-02-17 20:38:03

bradmccormack
Member
Registered: 2012-04-13
Posts: 7

Re: KDE 4.10 complete crash

chx wrote:

I downgraded to http://arm.konnichi.com/2013/02/02/extra/os/x86_64/ this xf86-video-intel now it's 2.20.19-1 and it's stable as a rock. sna yes.


Thanks for this. I've been hit by the issue too and wasn't sure what was going on. I've got an Intel HD 4000 Ivy Bridge.

I'll downgrade and see how I go.

Offline

Board footer

Powered by FluxBB