You are not logged in.
Hi all,
I'm facing a very strange bug...gnome crashes every day at the same time.
At 6.01 PM (I live in Italy) I get a freeze.
I can switch to the second shell using crtl+alt+f2 and there all is ok (without gui).
If I run htop I don't see zombie processes or something of strange.
How can I fix this problem?
Could be this discussion useful https://bbs.archlinux.org/viewtopic.php?pid=1281584 ?
Thanks a lot.
Offline
Do you use cron at all? Maybe there is a bad job that runs daily at that time. Also, did you see anything interesting when checking the journal?
"Think for yourself and question authority." -T. Leary
Offline
Sorry for the delay.
No, I don't ues cron.
Yesterday it didn't crash, today it does.
I don't know which log can I post here to help you to figure out what is happening.
Thanks a lot.
Offline
You can check the journal to see if it has any useful information. See
man journalctlfor more information. Also, from the post you referenced above, what is the output of
localeLast edited by BluMongoose (2013-09-12 01:20:06)
"Think for yourself and question authority." -T. Leary
Offline
locale returns this:
LANG=it_IT.utf8
LC_CTYPE="it_IT.utf8"
LC_NUMERIC="it_IT.utf8"
LC_TIME="it_IT.utf8"
LC_COLLATE="it_IT.utf8"
LC_MONETARY="it_IT.utf8"
LC_MESSAGES="it_IT.utf8"
LC_PAPER="it_IT.utf8"
LC_NAME="it_IT.utf8"
LC_ADDRESS="it_IT.utf8"
LC_TELEPHONE="it_IT.utf8"
LC_MEASUREMENT="it_IT.utf8"
LC_IDENTIFICATION="it_IT.utf8"
LC_ALL=instead journalctl --full --reverse returns this:
set 14 18:00:46 laptop systemd[1]: Starting Getty on tty2...
set 14 17:59:39 laptop dbus-daemon[389]: dbus[389]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.ModemManager1.service' for details.
set 14 17:59:39 laptop dbus[389]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.ModemManager1.service' for details.
set 14 17:59:39 laptop dbus[389]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
set 14 17:59:39 laptop dbus-daemon[389]: dbus[389]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
set 14 17:57:39 laptop dbus-daemon[389]: dbus[389]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.ModemManager1.service' for details.
set 14 17:57:39 laptop dbus[389]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service':Anyway the line
Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.ModemManager1.service' for details.is also present in other places in the log file.
Thanks a lot.
Offline
The locale is correct. About the error on the ModemManager.Service, there is a post about that here. Was this the only thing of interest around the time of the freeze? It seems there are quite a few other people running into system freezing recently. There is a post discussing their issues more in detail here. It seems for them that both downgrading or upgrading the kernel helped alleviate their freezing issue.
"Think for yourself and question authority." -T. Leary
Offline
Hi, first of all thanks for your reply.
I updated to linux 3.11 but nothing changes.
The very strange thing is that I get the freeze always at the same time!
Does anyone have an idea?
Offline
try disabling cronie.service
Offline
I cannot fathom why it would happen at 18:01 Local, but.....
The last time I played with Gnome, I tried enabling the seconds display on the clock in the top bar. With that enabled, the shell would hang at the start. It is probably completely unrelated. OTOH, if the clock implementation is buggy in one way, there could interesting effects in other ways too. Try turning off the clock display; it cannot hurt.
Edit: If you create a new user and start with a clean Gnome configuration and make no customizations, does it hang?
Last edited by ewaller (2013-09-17 20:54:46)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Just a thought, but maybe use something along the lines of top or htop and see if maybe a program is misbehaving.
"Think for yourself and question authority." -T. Leary
Offline
Comment out
1 18 * * * /usr/bin/crash-gnome
![]()
Offline