You are not logged in.
Pages: 1
Hi all,
It seems that some recent update broke emacs. If I start it with
$ emacs -nw
it works fine, but if I start it with
$ emacs
(defaulting to X11)
it just hangs indefinitely.
Anyone got any ideas?
Offline
check journalctl and dmesg and xorg.log when you try to start with emacs
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Doesn't really seem like any of those would be especially relevant, but they don't show anything interesting.
However, I am getting some rather weird errors (which may or may not be related to this) when I tried to "tail" .xsession-errors to see if that had any errors:
tail: inotify resources exhausted
tail: inotify cannot be used, reverting to polling
also getting a few others from some KDE/Qt-using code:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No space left on device
However, nothing is printed when I start emacs.
Offline
Just checked the inotify thing: It appears that firefox was the culprit (for unknown reasons), but I tried killing FF and made sure that that particular error no longer appeared when doing a "tail -f" before starting emacs. Still hangs. (So, it's probably unrelated.)
Just for completeness here's the last few lines printed by strace:
stat(7, {st_mode=S_IFREG|0600, st_size=66, ...}) = 0
lseek(7, 66, SEEK_SET) = 66
lseek(7, 0, SEEK_CUR) = 66
close(7) = 0
munmap(0x7f35722ed000, 4096) = 0
open("/usr/share/themes/oxygen-gtk/gtk-3.0/argb-apps.conf", O_RDONLY) = 7
read(7, "################################"..., 8191) = 2460
read(7, "", 8191) = 0
open("/home/bardur/.config/oxygen-gtk/argb-apps.conf", O_RDONLY) = 8
read(8, "# argb-apps.conf\n# Put your user"..., 8191) = 66
read(8, "", 8191) = 0
close(8) = 0
close(7) = 0
pipe([7, 8]) = 0
pipe([9, 10]) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f3572285bd0) = 8343
close(8) = 0
close(10) = 0
read(7, "", 8) = 0
close(7) = 0
select(10, [9], NULL, NULL, NULL) = 1 (in [9])
read(9, "/home/bardur/.kde/share/config/:"..., 4096) = 51
select(10, [9], NULL, NULL, NULL) = 1 (in [9])
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=8343, si_status=0, si_utime=0, si_stime=0} ---
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG|WSTOPPED, NULL) = 8343
wait4(-1, 0x7fffa86507fc, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child processes)
rt_sigreturn() = 1
read(9, "", 4096) = 0
close(9) = 0
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 7
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], [], 8) = 0
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 8
write(8, "\1\0\0\0\0\0\0\0", 8) = 8
mmap(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f355fea9000
mprotect(0x7f355fea9000, 4096, PROT_NONE) = 0
clone(child_stack=0x7f35606a8df0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x7f35606a99d0, tls=0x7f35606a9700, child_tidptr=0x7f35606a99d0) = 8344
futex(0xe58870, FUTEX_WAKE_PRIVATE, 1) = 1
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigaction(SIGCHLD, {0x7f356f95ed60, [], SA_RESTORER|SA_RESTART|SA_NOCLDSTOP, 0x7f356c2540e0}, NULL, 8) = 0
wait4(8343, 0xe58a44, WNOHANG, NULL) = -1 ECHILD (No child processes)
poll([{fd=7, events=POLLIN}], 1, 4294967295) = 1 ([{fd=7, revents=POLLIN}])
poll([{fd=7, events=POLLIN}], 1, 4294967295) = 1 ([{fd=7, revents=POLLIN}])
read(7, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=7, events=POLLIN}], 1, 4294967295
Last edited by ba (2013-04-22 18:20:09)
Offline
I can confirm the same problem (with the same strace output). x86_64, in kde environment. However, most of today's updates were gnome-related so I suspect (although can't currently test) that gtk3 might be the culprit...? (Just rebuilding emacs from the abs doesn't work, btw).
Offline
It seems as though there's a similar problem in kubuntu?
Offline
OK, so the problem (as in Kubuntu) is with oxygen-gtk3. Disable this and emacs will start properly. I'm not sure if this is a problem with emacs or with oxygen-gtk3, for bug-reporting purposes...?
Offline
Confirming the same problem, with very similar strace output, using the gtk2 build of emacs from the AUR. I don't have oxygen-gtk2 or oxygen-gtk3 installed.
EDIT: the problem appears to be with the qtcurve theme for gtk2.
Last edited by dburgoyn (2013-04-26 14:30:51)
Offline
It seems there's a problem with recent update of GTK2/3 (based from earlier posts).
Maybe some themes doesn't compatible with recent GTK2/3.
Ask, and it shall be given you.
Seek, and ye shall find.
Knock, and it shall be opened unto you.
Offline
Pages: 1