jiml8 wrote:In the interest of providing any information that might be useful, I upgraded my system without incident. I now have the 3.14 kernel and the latest dbus. No problems. My system is a Phenom-II 955 system with 32 GB RAM, 2 SATA and 5 SCSI drives, Nvidia GT740 graphics with driver 337.25.
Hi,
I've made a lengthy explanation of what I did from this bug thread (more specifically on comment 29):
https://bugs.mageia.org/show_bug.cgi?id=14249Could it be that your machine does not exhibit the symptoms that some users are experiencing? You said that you have the latest kernel 3.14, in which mine is 3.14.18-desktop-3.mga4 to be exact, if you have done your upgrade via MCC > "Update your system" it should have updated the corresponding dbus and it's other dependencies in that one upgrade instance and didn't exhibit the issues after 2 to 5 consecutive reboots then probably your machine could be one of the exceptions to this bug.
There was also a reply from Claire Robinson in the bug thread in which she attempted to downgrade the dbus and upgraded them back again by booting to runlevel 3 to perform the upgrade. I'd like to test how she specifically did it since my laptop is affected but if anyone can share the specific steps she did (not very proficient doing linux stuff yet so kindly guide me) i'd be willing to try it on my machine and see what happens. If that works then I can accept it, and hopefully the affected users as well, as a solution until the next dbus and its dependency update.
In connection to my statement above, the thead I referred to basically did involve me downgrading the dbus and upgrading the dbus again via mcc (after waiting for ~15 minutes to get a work-able KDE desktop) in which Thomas was asking for some files. I partially did the same step Claire did except that I performed the upgrade by waiting for the entire KDE thing to load after logging in and still going through MCC > "Update your system".
By the way, hats of to the hardworking Mageia Devs. It seems they're busy squishing Mageia 5 bugs and thus the reason I responded on this thread instead of responding on the bug thread since I do not have specific logs or files that I can provide as a basis for this response.