Am Donnerstag, 26. Dezember 2013, 19:41:24 schrieb Marco Martin:
On Tuesday 24 December 2013, Mark Petersen wrote:
is it still crashing even after reboot?
if you can get in with ssh, you can try to launch individual components
(like, kwinactive_gles, plasma-device, kdeinit4)
and see
On Thursday, December 26, 2013 19:41:24 Marco Martin wrote:
On Tuesday 24 December 2013, Mark Petersen wrote:
is it still crashing even after reboot?
if you can get in with ssh, you can try to launch individual components
(like, kwinactive_gles, plasma-device, kdeinit4)
and see what
On Tuesday 24 December 2013, Mark Petersen wrote:
is it still crashing even after reboot?
if you can get in with ssh, you can try to launch individual components
(like, kwinactive_gles, plasma-device, kdeinit4)
and see what of those do crash?
Yes, the crashing happens after reboot.
On Tuesday 24 December 2013, Mark Petersen wrote:
is it still crashing even after reboot?
if you can get in with ssh, you can try to launch individual components
(like, kwinactive_gles, plasma-device, kdeinit4)
and see what of those do crash?
Yes, the crashing happens after reboot.
On Tuesday 24 December 2013, Mark Petersen wrote:
Any ideas on how to troubleshoot or repair.
Thanks for any help, and thanks to the plasma-active team for the work they
have done getting kde on tablet devices.
Mark
It seems that update causes problems for everyone. Since it had shipped
On Tuesday, December 24, 2013 10:34:13 Marco Martin wrote:
On Tuesday 24 December 2013, Mark Petersen wrote:
Any ideas on how to troubleshoot or repair.
Thanks for any help, and thanks to the plasma-active team for the work
they
have done getting kde on tablet devices.
Mark
It
I have a nexus 7 that I installed plasma-active 4 on. All was working well
until
I installed updates on December 9th. This was a rather large update with 192
packages updated. Now, when I boot into plasma active I am met with a
kded4 segmentation fault followed by a plasma-device segmentation
