Hi,
Thanks for the advices. I didn't have autologin and the SSD firmware is at its newest version. I will be more cautious now to say that it is resolved, but it works for the time being. What I did now was that I've found an advice in debian forums that stated that the phase of the xembedsniproxy startup should be postponed by changing the phase from 0 to a higher value in /etc/xdg/autostart/xembedsniproxy.desktop. Therefore I have changed the parameter X-KDE-autostart-phase to 2 at first (it still segfaulted) and then to 4 (it seems to work now). So I guess it might be that when I have it started with applications phase it works.
EDIT: Not solved, after another reboot it segfaulted again. Therefore I'm officially out of ideas, since when I start it immediately after loging in, with just the following command, it works:
Thanks for the advices. I didn't have autologin and the SSD firmware is at its newest version. I will be more cautious now to say that it is resolved, but it works for the time being. What I did now was that I've found an advice in debian forums that stated that the phase of the xembedsniproxy startup should be postponed by changing the phase from 0 to a higher value in /etc/xdg/autostart/xembedsniproxy.desktop. Therefore I have changed the parameter X-KDE-autostart-phase to 2 at first (it still segfaulted) and then to 4 (it seems to work now). So I guess it might be that when I have it started with applications phase it works.
EDIT: Not solved, after another reboot it segfaulted again. Therefore I'm officially out of ideas, since when I start it immediately after loging in, with just the following command, it works:
Code:
xembedsniproxy &