Every time I start the notebook with a Mageia 1 KDE, a window error appears: "Details: Executable: kdeinit4 PID 1265 Sinal: Aborted (6)" - Unusual behavior I noticed: This only occurs in a notebook, does not occur on other computers. I close the window and a Mageia works normally. But that window come back every time I restart the computer. I created a new user and and the window with error appears again. I renamed the folder .kde4 and restart the computer and he window with error appears again. I saw that the error only occurs when the user initialization is automatic. If I restart the session and make access to the user again through login and password, the error does not occur. In Mageia Forum (https://forums.mageia.org/en/viewtopic.php?f=7&t=830#p5910) Djennings said: "If you only see the problem when using auto login then it could be related to speedboot. Mageia/Mandriva has a system called speedboot which attempts to load all the essential parts of the system as rapidly as possible while leaving non essential parts to be initialised later. Speedboot reduces boot times considerably, but can cause some anomalies. Try disabling speedboot as described here. ( http://wiki.mandriva.com/en/2010.0_Errata#Sometimes_you_may_see_anomalies_which_may_be_caused_by_speedboot )" I tested putting "speedboot=no" in the boot and the error doesn't occur in the automatically at startup.
Note that KDE 4.6.5 is in core/update_testing, and will be pushes as an official update soon. Did you test it?
Assignee: bugsquad => balcaen.johnSource RPM: (none) => kdelibs4
Hum it seems more a speedboot issue if it does not appears with speedboot disable.
@Thierry an idea maybe ? (if i'm not wrong you worked on speedboot)
CC: (none) => thierry.vignaud
No idea.
CC: thierry.vignaud => (none)
Settings to initscripts since it's speedboot related & i' added colin in cc since he might have some ideas :)
CC: (none) => balcaen.john, mageiaSource RPM: kdelibs4 => initscripts
If it's related to speedboot, then I think the only option is to disable it for autologin PCs. I'm not sure of what component is at fault, but by the same token, I think this is an easy workaround just now and the problem will not occur in mga2 as we'll be ripping out speedboot generally in favour of systemd. So I suspect that this likely won't get overly much attention :(
reassigning to bugsquad @ macxi did you try with speedboot disable ?
Assignee: balcaen.john => bugsquad
(In reply to comment #7) > reassigning to bugsquad > > @ macxi > did you try with speedboot disable ? John Balcaen, Yes. I tested putting "speedboot = no" in the boot and the error does not occur in the automatically at startup.
(In reply to comment #8) > (In reply to comment #7) > > reassigning to bugsquad > > > > @ macxi > > did you try with speedboot disable ? > > John Balcaen, > > Yes. I tested putting "speedboot = no" in the boot and the error does not occur > in the automatically at startup. Good to hear that the workaround works :) I think there is no point in assigning this to anyone, because of what Colin said in comment #6 : > If it's related to speedboot, then I think the only option is to disable it for > autologin PCs. > > I'm not sure of what component is at fault, but by the same token, I think this > is an easy workaround just now and the problem will not occur in mga2 as we'll > be ripping out speedboot generally in favour of systemd. > > So I suspect that this likely won't get overly much attention :( So closing as wontfix Feel free to reopen if you think I'm wrong to close this bug, and explain why you think so.
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => WONTFIX