[Bug 1086804] New: fonts-config warns about ninitialized HOME in posttrans
http://bugzilla.suse.com/show_bug.cgi?id=1086804 Bug ID: 1086804 Summary: fonts-config warns about ninitialized HOME in posttrans Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: simonf.lees@suse.com Reporter: kukuk@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After the last update I saw the following error message in the log files: # 2018-03-24 01:14:52 Output of fonts-config-20160921-3.1.noarch.rpm %posttrans script: # Use of uninitialized value $ENV{"HOME"} in concatenation (.) or string at /usr/sbin/fonts-config line 391. And yes, HOME was of course not set. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1086804
http://bugzilla.suse.com/show_bug.cgi?id=1086804#c3
Thorsten Kukuk
Hi, Thorsten,
can you please tell which package triggered this error?
I installed latest fonts-config in a clean environment, and I can't reproduce this error.
Most likely you had an HOME variable set? Which is the default if you run it from a shell, but not if the run was triggered by something like a systemd service. To reproduce, unset the HOME environment variable, that should be the easiest way. Else write a systemd service, which updates or runs fonts-config. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1086804 http://bugzilla.suse.com/show_bug.cgi?id=1086804#c4 --- Comment #4 from Marguerite Su --- Hi, Thorsten, Yes, I have HOME env set. I mean, if HOME is set under all cases that triggering fonts-config user config, it can be safely ignored. HOME is used to run fonts-config user config. user config means there has to be a user. if there's a user, there's a HOME. I am curious how we can have a user without HOME. The error message you provided is of course not fake. So I want to examine the service (maybe) to make sure we do have a user without HOME in some situations. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1086804
http://bugzilla.suse.com/show_bug.cgi?id=1086804#c5
--- Comment #5 from Thorsten Kukuk
The error message you provided is of course not fake. So I want to examine the service (maybe) to make sure we do have a user without HOME in some situations.
This usual happens, if you do automatic updates from a systemd service, e.g. a timer. systemd service is calling directly zypper up/dup, which installs the RPM, which runs fontsäconfig in the post-install. Or systemd service is calling a script, which calls zypper, ... Or something like salt is calling zypper. Or you boot by DVD to update the system with YaST. So every time zypper is not called by an user/admin on the commandline, there is no HOME set. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1086804 http://bugzilla.suse.com/show_bug.cgi?id=1086804#c6 --- Comment #6 from Marguerite Su --- (In reply to Thorsten Kukuk from comment #5)
(In reply to Marguerite Su from comment #4) This usual happens, if you do automatic updates from a systemd service, e.g. a timer. systemd service is calling directly zypper up/dup, which installs the RPM, which runs fontsäconfig in the post-install. Or systemd service is calling a script, which calls zypper, ...
Or something like salt is calling zypper.
Or you boot by DVD to update the system with YaST.
So every time zypper is not called by an user/admin on the commandline, there is no HOME set.
Ha, I understand zypper can be called by anything, but zypper and fonts-config are tied up via fontpackages’s %reconfigure_fonts macro, which calls “fonts-config -quiet”, that is system mode not user mode, HOME stuff shouldn’t be called at all. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1086804
http://bugzilla.suse.com/show_bug.cgi?id=1086804#c7
--- Comment #7 from Thorsten Kukuk
I understand zypper can be called by anything, but zypper and fonts-config are tied up via fontpackages’s %reconfigure_fonts macro, which calls “fonts-config -quiet”, that is system mode not user mode, HOME stuff shouldn’t be called at all.
As you can see on the log entries from zypper, it reports an error. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com