I have (for a long time) in /etc/emacs/site-start.el setq default-frame-alist '((background-color . "#333333") (foreground-color . "White") (cursor-color . "White"))) (setq initial-frame-alist default-frame-alist) With emacs 29.1-r1 these settings stopped working and background is just white. Rebuilt emacs deps with emacs-updater
> setq default-frame-alist '((background-color . "#333333") (foreground-color . "White") (cursor-color . "White"))) > (setq initial-frame-alist default-frame-alist) I cannot reproduce the problem, this is working just fine here (after adding the missing opening parenthesis). Can you attach your complete site-start.el? What values do you see for default-frame-alist and initial-frame-alist in Emacs, i.e. with C-h v?
Can you reproduce it with emacs -Q?
Created attachment 870977 [details] site-start.el
(In reply to Sam James from comment #2) > Can you reproduce it with emacs -Q? Yes, still same. Creating a New Frame works, only the initial Frame when starting emacs is wrong.
hmm, the problem only manifest if a ssh to a machine with emacs-29 installed.
(In reply to Joakim Tjernlund from comment #5) > hmm, the problem only manifest if a ssh to a machine with emacs-29 installed. and only if emacs-28 is installed on the local machine. If I got emacs-29 on both local and remote machine it works, odd.
(In reply to Joakim Tjernlund from comment #6) > and only if emacs-28 is installed on the local machine. > If I got emacs-29 on both local and remote machine it works, odd. Do you want us to investigate this further, or can this bug be closed?
(In reply to Ulrich Müller from comment #7) > (In reply to Joakim Tjernlund from comment #6) > > and only if emacs-28 is installed on the local machine. > > If I got emacs-29 on both local and remote machine it works, odd. > > Do you want us to investigate this further, or can this bug be closed? As it looks now it will pass once I have emacs-29 on all machines. Lets close it, I will reopen if it resurfaces.
Sorry but I have to reopen this. Upgraded my main machine to the same status as my laptop and my main Desktop still has this problem.
I got a clue: qlist mate-settings | grep xrdb /etc/xrdb/Xaw.ad /etc/xrdb/Tk.ad /etc/xrdb/Motif.ad /etc/xrdb/Emacs.ad /etc/xrdb/Editres.ad /etc/xrdb/General.ad /usr/lib64/mate-settings-daemon/libxrdb.so /usr/lib64/mate-settings-daemon/xrdb.mate-settings-plugin /usr/share/glib-2.0/schemas/org.mate.SettingsDaemon.plugins.xrdb.gschema.xml cat /etc/xrdb/Emacs.ad Emacs.default.attributeForeground: WINDOW_FOREGROUND Emacs.default.attributeBackground: WINDOW_BACKGROUND Emacs*Foreground: WINDOW_FOREGROUND Emacs*Background: WINDOW_BACKGROUND Emacs*menubar*foreground: FOREGROUND Emacs*menubar*background: BACKGROUND Emacs*popup*Foreground: FOREGROUND Emacs*popup*Background: BACKGROUND Emacs*Dialog*foreground: FOREGROUND Emacs*Dialog*background: BACKGROUND Emacs*XlwScrollBar.Foreground: FOREGROUND Emacs*XlwScrollBar.Background: BACKGROUND Emacs*topToolBarShadowColor: BACKGROUND Emacs*bottomToolBarShadowColor: BACKGROUND Emacs*backgroundToolBarColor: BACKGROUND Emacs.scroll-bar.attributeBackground: BACKGROUND Emacs.scroll-bar.attributeForeground: FOREGROUND Emacs.mode-line.attributeForeground: FOREGROUND Emacs.tool-bar.attributeBackground: BACKGROUND Emacs.tool-bar.attributeForeground: FOREGROUND so MATE loads these XRDB settings and if I remove Emacs.ad it works. However, before emacs-29 I did have to change anything. Why now ?
Maybe the relative priority of initial-frame-alist and those resources has changed in Emacs 29. I don't see anything obvious in its NEWS file, however. Maybe ask upstream in the emacs-devel mailing list?
(In reply to Ulrich Müller from comment #11) > Maybe the relative priority of initial-frame-alist and those resources has > changed in Emacs 29. I don't see anything obvious in its NEWS file, however. > > Maybe ask upstream in the emacs-devel mailing list? I did but I see you found out yourself :)
This should be resolved upstream. Closing here.
(In reply to Ulrich Müller from comment #13) > This should be resolved upstream. Closing here. It is? I didn't notice that, any URL/ref to the fix?
(In reply to Joakim Tjernlund from comment #14) > (In reply to Ulrich Müller from comment #13) > > This should be resolved upstream. Closing here. > > It is? I didn't notice that, any URL/ref to the fix? Sorry, "should be" in the sense that upstream should resolve the issue.
