slack-current: this is redickulious why am I getting Bus error onlyin Slackware current? rror
I just up dated slack current (Dec 1, 2018) now I am getting this message, Enlightenment caused a Bus error, check your hardware, or OS as Enlightenment does not cause bus error, ignore, reboot, exit OS.
I've gotten it three times, so far. I uninstalled e16, recompiled it via sbotools, installed it again, updated grub just cuz, then logged back into e16 and got the same message, only this time before it even started completely. does anyone have any idea what this is all about? right now I am in openbox, should I expect any type notification from using a different WM/DT so it may lead me to where and why this is happening, ie HW issues, or just e16 and current, because I run e16 on other distors I have installed on this laptop, and have not had the same error, as I was just in e16 in Manjaro to update grub as that one has the control of grub2, and I did not get any such message. |
update: another bus error cused by something else.
Code:
$ mh5000 BAD RAM BAD? :tisk: MOD UPDATE Manjaro is not throwing any Bus error's. Could this be a Slack - current thing? stay tuned: same Slack channel same Slack time :D maybe stop using Slack-Curr until its next update, then see if it is still doing it. bye-bye slack, see ya in a few days, maybe. |
What is the exact error?
|
Quote:
Quote:
I did get this when trying to login to i3, and it kicked me out, so I went in wmaker instead. Code:
[ 163.649092] i3[1323]: segfault at c0 ip 00007f7b084dd094 sp 00007ffeda4553b0 error 4 in libc-2.28.so[7f7b084a4000+169000] |
Quote:
Quote:
|
Quote:
|
All times are GMT -5. The time now is 04:19 AM. |