[opensuse-factory] Tumbleweed: Emacs/AucTeX+GTK - LaTeX process does not finish
Hej! I have a problem with Emacs/AucTeX, which is *somehow* connected to the big Gnome update that landed in Tumbleweed within the last couple of days. I have not yet reported this as a bug since I quite frankly do not know what to report. I get *no* error messages via Emacs's Messages buffer or via console output etc. Normally, when compiling a LaTeX-document with Emacs & AucTeX, the output is sent to another buffer, emacs runs pdflatex and once pdflatex finishes, Emacs prints "Successfully wrote [x] pages" in the minibuffer. Afterwards, one can call another command, be it another LaTeX-run, Biber/Bibtex/Biblatex etc. etc. *However*, Emacs does *not* produce the "Successfully..." message, and subsequently, the latex process never finishes, unless killed by hand. This *only* happens in Emacs+GTK(3), emacs-x11 works as intended. This means *something* GTK-related breaks Emacs/AucTeX, however, I have no idea where I should even start to look since I get no output/errors etc. Does anybody have any ideas what could be causing this? Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Apr 28, 2013 at 08:46:59PM +0100, Peter Hanisch wrote:
Hej!
I have a problem with Emacs/AucTeX, which is *somehow* connected to the big Gnome update that landed in Tumbleweed within the last couple of days. I have not yet reported this as a bug since I quite frankly do not know what to report. I get *no* error messages via Emacs's Messages buffer or via console output etc.
Normally, when compiling a LaTeX-document with Emacs & AucTeX, the output is sent to another buffer, emacs runs pdflatex and once pdflatex finishes, Emacs prints "Successfully wrote [x] pages" in the minibuffer. Afterwards, one can call another command, be it another LaTeX-run, Biber/Bibtex/Biblatex etc. etc.
*However*, Emacs does *not* produce the "Successfully..." message, and subsequently, the latex process never finishes, unless killed by hand. This *only* happens in Emacs+GTK(3), emacs-x11 works as intended.
This means *something* GTK-related breaks Emacs/AucTeX, however, I have no idea where I should even start to look since I get no output/errors etc.
Does anybody have any ideas what could be causing this?
If you drop back to the version of emacs that is in 12.3, does this problem go away? I have been putting the latest versions of emacs in Tumbleweed, so I would blame emacs before the GNOME update. Oh, make sure you really have all the gnome updates installed, see Andi's email thread earlier today for how to verify this (hint, run 'zypper update -t package', you shouldn't see anything there.) thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 29/04/13 04:51, Greg KH wrote:
On Sun, Apr 28, 2013 at 08:46:59PM +0100, Peter Hanisch wrote:
If you drop back to the version of emacs that is in 12.3, does this problem go away? I have been putting the latest versions of emacs in Tumbleweed, so I would blame emacs before the GNOME update.
I use neither version normally, but instead compile Emacs directly from git (24.3.50.7). However, the same problem appears with both the tumbleweed and 12.3 version. Yet, not changing Emacs but reverting the GNOME packages does fix the problem, which suggest that this is, indeed, a GNOME problem.
Oh, make sure you really have all the gnome updates installed, see Andi's email thread earlier today for how to verify this (hint, run 'zypper update -t package', you shouldn't see anything there.)
'zypper update -t package' shows a list of packages, however, I use Tumbleweed with a higher priority and therefore all packages that are included in Tumbleweed and installed are already updated to the newest (tumbleweed) version. (I also checked by hand.) I also played around with downgrading GTK2/3 to their 12.3 counterparts etc, yet to no avail. It seems the breakage happens somewhere in the GNOME core, yet I still can't find any specifics.
thanks,
greg k-h
Cheers, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Apr 29, 2013 at 12:14:30PM +0100, Peter Hanisch wrote:
On 29/04/13 04:51, Greg KH wrote:
On Sun, Apr 28, 2013 at 08:46:59PM +0100, Peter Hanisch wrote:
If you drop back to the version of emacs that is in 12.3, does this problem go away? I have been putting the latest versions of emacs in Tumbleweed, so I would blame emacs before the GNOME update.
I use neither version normally, but instead compile Emacs directly from git (24.3.50.7). However, the same problem appears with both the tumbleweed and 12.3 version. Yet, not changing Emacs but reverting the GNOME packages does fix the problem, which suggest that this is, indeed, a GNOME problem.
Oh, make sure you really have all the gnome updates installed, see Andi's email thread earlier today for how to verify this (hint, run 'zypper update -t package', you shouldn't see anything there.)
'zypper update -t package' shows a list of packages, however, I use Tumbleweed with a higher priority and therefore all packages that are included in Tumbleweed and installed are already updated to the newest (tumbleweed) version. (I also checked by hand.)
I also played around with downgrading GTK2/3 to their 12.3 counterparts etc, yet to no avail. It seems the breakage happens somewhere in the GNOME core, yet I still can't find any specifics.
Then I suggest you take this to the opensuse gnome list, or even better yet, the gnome developers upstream mailing list, there's not much I can do here, sorry. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 29/04/13 16:46, Greg KH wrote:
Then I suggest you take this to the opensuse gnome list, or even better yet, the gnome developers upstream mailing list, there's not much I can do here, sorry.
greg k-h
Alright, I'll see what they think about this rather odd behaviour! Thank you for your help. And if someone else happens to have any ideas, feel free to chime in. Cheers, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Peter Hanisch writes:
This means *something* GTK-related breaks Emacs/AucTeX, however, I have no idea where I should even start to look since I get no output/errors etc.
Does anybody have any ideas what could be causing this?
It seems that there must be a bug/change in glib 2.36 that's responsible (fingers point to g_spawn*, but I haven't found a bug report yet). Additionally, Emacs versions older than 24.2 don't even start when the Gtk theme is "Oxygen", this seems to be related to glib but has supposedly been worked around in gtk2-engine-oxygen-1.3.3 and gtk3-engine-oxygen-1.1.3 (both of which are not yet in Tumbleweed). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14/05/13 21:22, Achim Gratz wrote:
Peter Hanisch writes:
This means *something* GTK-related breaks Emacs/AucTeX, however, I have no idea where I should even start to look since I get no output/errors etc.
Does anybody have any ideas what could be causing this?
It seems that there must be a bug/change in glib 2.36 that's responsible (fingers point to g_spawn*, but I haven't found a bug report yet). Additionally, Emacs versions older than 24.2 don't even start when the Gtk theme is "Oxygen", this seems to be related to glib but has supposedly been worked around in gtk2-engine-oxygen-1.3.3 and gtk3-engine-oxygen-1.1.3 (both of which are not yet in Tumbleweed).
Regards, Achim.
Oxygen-gtk seems to be indeed somewhere in the mix here, since the problem does not occur Adwaita as gtk3-theme. The problem, however, occurs with gtk3-engine-oxygen-1.1.3 here as well, so I am still not quite sure what the root of the issue is... Cheers, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Peter Hanisch writes:
Oxygen-gtk seems to be indeed somewhere in the mix here, since the problem does not occur Adwaita as gtk3-theme. The problem, however, occurs with gtk3-engine-oxygen-1.1.3 here as well, so I am still not quite sure what the root of the issue is...
I've installed the newer gtk[23]-engine-oxygen from factory and the earlier emacs-gtk versions still don't start up, so whatever fixes went into these are ineffective for this particular problem. Switching to a different Gtk theme (I've tested Adwaita and Clearlooks) fixes the startup issue, though. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Achim Gratz -
Greg KH -
Peter Hanisch