Re: What happened with the emacs24 port?
Hi, are we waiting for emacs25? :) Aside from that, the question of unlinking older Emacs versions is still open, it seems. I've been told in private mail that this was not an option, as some developers want to keep older versions. I don't know what to think about this, except that it would be a shame if one side stood up for keeping all current versions, and the other side didn't want to import newer versions because of the maintenance burden and increased build time. -- Jérémie Courrèges-Anglas GPG Key fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: What happened with the emacs24 port?
I would also support this! On 11/25/12 15:59, Mike Belopuhov wrote: Please consider importing Emacs 24. FWIW, it works fine for me now. On Sat, Nov 17, 2012 at 10:33 PM, Jérémie Courrèges-Anglas wrote: Hi, the next Emacs (24.3) pretest cycle will start on Nov. 24. I intend to publish an updated port for it when the -rc tarball will be available, so that people can test it asap. But we're not there yet; it would be nice to see the work of both Manuel Giraud and myself, as well as the reports sent by porters here, made useful for all -current users. I really do wonder if there's a blatant problem that I fail to see and no one tells me about. So, ok for committing what we have*, and unlinking emacs[23]? Regards, * previous mail in this thread -- Jérémie Courrèges-Anglas GPG Fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: What happened with the emacs24 port?
Please consider importing Emacs 24. FWIW, it works fine for me now. On Sat, Nov 17, 2012 at 10:33 PM, Jérémie Courrèges-Anglas wrote: > Hi, > > the next Emacs (24.3) pretest cycle will start on Nov. 24. > I intend to publish an updated port for it when the -rc tarball will be > available, so that people can test it asap. > > But we're not there yet; it would be nice to see the work of both Manuel > Giraud and myself, as well as the reports sent by porters here, made > useful for all -current users. I really do wonder if there's a blatant > problem that I fail to see and no one tells me about. > > So, ok for committing what we have*, and unlinking emacs[23]? > > Regards, > > * previous mail in this thread > -- > Jérémie Courrèges-Anglas > GPG Fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494 > >
Re: What happened with the emacs24 port?
Hi, the next Emacs (24.3) pretest cycle will start on Nov. 24. I intend to publish an updated port for it when the -rc tarball will be available, so that people can test it asap. But we're not there yet; it would be nice to see the work of both Manuel Giraud and myself, as well as the reports sent by porters here, made useful for all -current users. I really do wonder if there's a blatant problem that I fail to see and no one tells me about. So, ok for committing what we have*, and unlinking emacs[23]? Regards, * previous mail in this thread -- Jérémie Courrèges-Anglas GPG Fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: What happened with the emacs24 port?
(trimming the Cc list)
jca+o...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:
[...]
> The problem is that some people don't run a session manager / desktop
> environment that might spawn dbus, and forget to do so in their own
> ~/.xinitrc. I think the dbus port README should come back.
Oops, thanks to Antoine (sorry for the noise), this README had already
been reintroduced on November 9.
I've modified the Emacs README so that it points to the dbus one.
> New port attached. I've changed the ${OSREV}/--build=${GCCARCH} stuff
> so that we don't include ${OSREV} in the PLIST, but I don't really
> know about the possible bad consequences. Adding myself as
> maintainer.
Regards,
--
Jérémie Courrèges-Anglas
Empreinte GPG : 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
emacs24.tgz
Description: Binary data
Re: What happened with the emacs24 port?
Stuart Henderson writes:
> The last I remember from the discussion is that it sometimes hangs at shutdown
> unless a system dbus is running,
I don't think it was a system dbus problem, rather a user session dbus
problem.
> but there's no documentation to tell people to do this
I'm currently writing a README, but I still don't really know what should
its content be: every time I try to reproduce this problem, I fail.
What I have observed on the gtk3 flavor (using emacs -q):
- with my personal .xinitrc that does nothing related to dbus, Emacs
(or rather the glib/gtk3 backend) automatically spawns a dbus session
and seems to use it.
jca 21115 0.0 0.1 1052 1548 ?? Ss 2:03PM0:00.02
/usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
jca 15409 0.0 0.2 864 1656 ?? S 2:03PM0:00.02
/usr/local/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf
--nofork --print-address 3
jca 6960 0.0 0.1 424 1452 p9 S+ 2:03PM0:00.01 dbus-launch
--autolaunch ff6ac36d53058081989a13de508345c5 --binary-syntax --close-stderr
emacs spawns /usr/local/bin/dbus-launch
dbus-launch spawns /usr/local/bin/dbus-daemon
dbus-daemon spawns /usr/local/libexec/at-spi-bus-launcher
at-spi-bus-launcher spawns /usr/local/bin/dbus-daemon
Killing the dbus session results in Emacs exiting with this error
message:
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
But I couldn't trigger freezing at exit time.
- with the stock /etc/X11/xdm/Xsession and fvwm:
At session start:
jca 25633 0.0 0.1 428 1480 ?? S 2:11PM0:00.00 dbus-launch
--sh-syntax --exit-with-session
jca 3625 0.0 0.1 660 916 ?? Ss 2:11PM0:00.00
/usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
After emacs -q:
jca 25633 0.0 0.1 428 1480 ?? I 2:11PM0:00.00 dbus-launch
--sh-syntax --exit-with-session
jca 3625 0.0 0.2 896 1568 ?? Is 2:11PM0:00.05
/usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
jca 18004 0.0 0.2 832 1640 ?? I 2:12PM0:00.04
/usr/local/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf
--nofork --print-address 3
After pkill dbus, Emacs prints errors (related to committing changes
to dconf) but still "works OK" and exits without hanging.
After Emacs has been exited, it tries to connect to the previous dbus
socket since it is still defined in its environment, but stops
bothering after a few failures. There again, I couldn't trigger
freezing at exit.
So, what I'm going to put in this README is:
--8<--
There is some random bug in graphical Emacs sessions (freeze/crash at
exit time) that some do experience and some don't. It seems that
starting a global dbus user session solves the problem; if you use your
own .xinitrc / .xsession, please have a look at /etc/X11/xinit/xinitrc.
-->8--
I don't know if the wording looks clear enough or those hints are
optimal.
> (and I'm not aware of other software behaving like this so it's
> a bit unexpected..)
Wha, is it really the first Heisenbug ever? :)
I've been unable to reproduce it on -current i386, even without a dbus
user session running.
As experienced by others in the 24.1 and 24.2 threads, either the
changes made to the default xinitrc/xsession or using a session manager
that automatically starts dbus should fix the bug.
http://marc.info/?l=openbsd-ports&m=134054137119141&w=2
The problem is that some people don't run a session manager / desktop
environment that might spawn dbus, and forget to do so in their own
~/.xinitrc. I think the dbus port README should come back.
New port attached. I've changed the ${OSREV}/--build=${GCCARCH} stuff
so that we don't include ${OSREV} in the PLIST, but I don't really know
about the possible bad consequences. Adding myself as maintainer.
[...]
--
Jérémie Courrèges-Anglas
GPG Fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
emacs24.tgz
Description: Binary data
Re: What happened with the emacs24 port?
The last I remember from the discussion is that it sometimes hangs at shutdown unless a system dbus is running, but there's no documentation to tell people to do this (and I'm not aware of other software behaving like this so it's a bit unexpected..) Lars Engblom wrote: >Hello, > >I just wonder what happened with the Emacs24 port. The last mails in >the >thread about the port pretty much gave OK to submit it... and I have >not >seen any submission yet, and no further discussion either. > >Lasse
