[SOLVED] .profile not parsed after latest updates

remus · 2016-10-17 09:27:15

I did a Pacman update yesterday evening (last one was last Monday, 10/10) and now it seems my .profile file is being ignored. None of the settings there (most important: changes to $PATH) take any effect anymore (neither in the terminal, nor when, e.g., using a keyboard shortcut or Alt+F2 to start a program).
I can't find anything related in either dmesg or journalctl, and I have already rebooted once (and also just logged out once) to see if that helps – no dice.
Does anyone have any idea what could be going wrong there, and what I could try to resolve this?

Another problem I now have is that Gnome terminal windows aren't listed anymore in the output of "wmctrl -l" and, thus, also cannot be manipulated with wmctrl anymore – which is a problem because I used that to center newly created terminal windows. Does anyone have any solution for that? Is this expected behavior now? (Or should I create a separate topic for this question?)

These are the updated packages:

accountsservice-0.6.43-1-x86_64
adwaita-icon-theme-3.22.0-1-any
atk-2.22+1+gd57f97d-1-x86_64
at-spi2-atk-2.22.0-1-x86_64
at-spi2-core-2.22.0-1-x86_64
baobab-3.22.0+3+g423a1a1-1-x86_64
calibre-2.70.0-1-x86_64
cheese-3.22.1-1-x86_64
clutter-1.26.0+24+g79da526-1-x86_64
clutter-gtk-1.8.2-1-x86_64
colord-1.3.3-1-x86_64
dconf-editor-3.22.1-1-x86_64
dhclient-4.3.5-1-x86_64
eog-3.20.5-1-x86_64
evince-3.22.1-1-x86_64
evolution-data-server-3.22.1+5+g45951fc-1-x86_64
file-roller-3.22.1-1-x86_64
folks-0.11.3-2-x86_64
gdb-7.12-1-x86_64
gdb-common-7.12-1-x86_64
gdk-pixbuf2-2.36.0+2+ga7c869a-1-x86_64
gdm-3.22.1-1-x86_64
geocode-glib-3.20.1+1+ga646012-1-x86_64
gjs-1.46.0-1-x86_64
glib2-2.50.1-1-x86_64
glibmm-2.50.0-1-x86_64
glib-networking-2.50.0-1-x86_64
gnome-autoar-0.1.1+1+g8d75c44-1-x86_64
gnome-backgrounds-3.22.1-1-any
gnome-bluetooth-3.20.0+6+g3bac4f9-1-x86_64
gnome-calculator-3.22.1-1-x86_64
gnome-clocks-3.22.0+2+g74a75f7-1-x86_64
gnome-color-manager-3.22.1-1-x86_64
gnome-control-center-3.22.1-1-x86_64
gnome-desktop-1:3.22.1-1-x86_64
gnome-dictionary-3.20.0+28+g7dce582-1-x86_64
gnome-disk-utility-3.22.0+3+gb7a9243-1-x86_64
gnome-font-viewer-3.22.0+1+gd3cf893-1-x86_64
gnome-keyring-1:3.20.0+16+gbf8aa97-1-x86_64
gnome-logs-3.22.0+1+g9479eb0-1-x86_64
gnome-maps-3.22.1-1-x86_64
gnome-online-accounts-3.22.1-1-x86_64
gnome-screenshot-3.22.0+1+g7568f0e-1-x86_64
gnome-session-3.22.1-1-x86_64
gnome-settings-daemon-3.22.1-1-x86_64
gnome-shell-3.22.1+2+g5a08886-1-x86_64
gnome-shell-extensions-3.22.1-1-any
gnome-system-monitor-3.22.0+3+g8e6b08a-1-x86_64
gnome-terminal-3.22.0+4+g87e36d3-1-x86_64
gnome-themes-standard-3.22.2-1-x86_64
gnome-tweak-tool-3.22.0+3+g2f9d966-1-any
gnome-video-effects-0.4.1+56+g393c78f-1-any
gnutls-3.4.16-1-x86_64
gobject-introspection-runtime-1.50.0+1+gb8d92b0-1-x86_64
grilo-0.3.2+8+g6ffe445-1-x86_64
gsettings-desktop-schemas-3.22.0+1+g6f52ab5-1-any
gst-libav-1.9.90+2+g108b08c-1-x86_64
gst-plugins-bad-1.9.90+20+g7dd42ae-1-x86_64
gst-plugins-base-1.9.90+12+g667931e-1-x86_64
gst-plugins-base-libs-1.9.90+12+g667931e-1-x86_64
gst-plugins-good-1.9.90+8+g6542edd-1-x86_64
gstreamer-1.9.90+8+g6d0d350-1-x86_64
gtk3-3.22.1+8+ge11df6c-2-x86_64
gtk3-print-backends-3.22.1+8+ge11df6c-2-x86_64
gtkmm3-3.22.0-1-x86_64
gtksourceview3-3.22.0+4+g87c38b3-1-x86_64
gtk-update-icon-cache-3.22.1+8+ge11df6c-2-x86_64
guile-2.0.13-1-x86_64
gvfs-1.30.1-2-x86_64
gvfs-afc-1.30.1-2-x86_64
gvfs-mtp-1.30.1-2-x86_64
harfbuzz-1.3.2-1-x86_64
harfbuzz-icu-1.3.2-1-x86_64
imagemagick-6.9.6.2-1-x86_64
iproute2-4.8.0-1-x86_64
jasper-1.900.2-1-x86_64
json-glib-1.2.2+4+gd725fb5-1-x86_64
lib32-sqlite-3.14.2-1-x86_64
libchamplain-0.12.14+2+ge1f6e59-1-x86_64
libedit-20160903_3.1-1-x86_64
libgdata-0.17.6-1-x86_64
libgdm-3.22.1-1-x86_64
libgee-0.18.1-1-x86_64
libgnomekbd-3.22.0.1-1-x86_64
libgtop-2.34.1-1-x86_64
libgweather-3.20.3+20+gb9a6ef3-1-x86_64
libgxps-0.2.4+12+g4709da9-1-x86_64
libnautilus-extension-3.22.1-1-x86_64
libnotify-0.7.7-1-x86_64
libpeas-1.20.0-1-x86_64
libreoffice-fresh-5.2.2-2-x86_64
libsigc++-2.10.0-1-x86_64
libsoup-2.56.0-1-x86_64
libtracker-sparql-1.10.1-1-x86_64
lightsoff-3.22.0+2+ga5dbe9b-1-x86_64
linux-firmware-20161005.9c71af9-1-any
mutter-3.22.1-1-x86_64
nautilus-3.22.1-1-x86_64
pacman-mirrorlist-20161013-1-any
pcre2-10.22-1-x86_64
php-7.0.12-1-x86_64
php-apache-7.0.12-1-x86_64
php-gd-7.0.12-1-x86_64
php-mcrypt-7.0.12-1-x86_64
php-pgsql-7.0.12-1-x86_64
php-sqlite-7.0.12-1-x86_64
pygobject-devel-3.22.0-1-x86_64
python2-gobject-3.22.0-1-x86_64
python-gobject-3.22.0-1-x86_64
seahorse-3.20.0+44+ga1474bb-1-x86_64
s-nail-14.8.12-1-x86_64
strace-4.14-1-x86_64
totem-plparser-3.10.7+1+gb25e497-1-x86_64
vte3-0.46.0+5+g398a3f8-1-x86_64
vte-common-0.46.0+5+g398a3f8-1-x86_64
webkit2gtk-2.14.1-1-x86_64
zenity-3.22.0+1+gcd1647c-1-x86_64

Last edited by remus (2016-10-17 11:46:11)

WorMzy · 2016-10-17 09:34:19

I'm not sure about the .profile problem, but every other problem with gnome this week seems to have been caused by the default gnome session now being wayland (rather than X). Try logging into the X session and see if it solves your wmctrl problem. If your .profile is also parsed, this would suggest that gnome wayland doesn't parse this file, put your PATH manipulation into your shell initialization file (e.g. .bashrc, .zshrc, etc.) instead.

Mod note: Not a pacman/update issue, moving to NC.

remus · 2016-10-17 11:45:58

Thanks a lot, that seems to have been it! Switched back to X and it worked fine again. (Even the issue with the terminal window not being recognized.)
Is there any reason I should still switch to Wayland and try to make that work, or is staying with X fine, too?

Also thanks for moving the topic. Wasn't sure where this belonged.

WorMzy · 2016-10-17 12:05:47

To be honest, I have no idea if the wayland problems people are having are with gnome's wayland implementation, specific apps, or just a misconfiguration somewhere. You're probably best sticking with X for now, and switching to wayland when the problems have been addressed. Of course, if you want to be a pioneer, you can investigate the problems and file bugs upstream where appropriate. The more people testing this stuff, the more feedback devs get, the better experience people get.

remus · 2016-10-18 08:21:56

Just in case someone else is interested in this topic: there's already been a bug report for this for two years, but apparently not running shell scripts is a feature, not a bug, and providing a working alternative wasn't a priority. (Or something like that – read it yourself, if you want to know the details.) There are a bunch of alternatives discussed there, like /usr/share/gdm/env.d and ~/.config/environment.d/, but I'm not sure whether they are already working.

For now, I'm staying with X and testing carefully. Maybe I'll give Wayland another shot in a few months.

Last edited by remus (2016-10-18 08:22:25)

Arch Linux

#1 2016-10-17 09:27:15

[SOLVED] .profile not parsed after latest updates

#2 2016-10-17 09:34:19

Re: [SOLVED] .profile not parsed after latest updates

#3 2016-10-17 11:45:58

Re: [SOLVED] .profile not parsed after latest updates

#4 2016-10-17 12:05:47

Re: [SOLVED] .profile not parsed after latest updates

#5 2016-10-18 08:21:56

Re: [SOLVED] .profile not parsed after latest updates

Board footer