Hi Thomas, thanks for the info.
That landscape-client/landscape-config crash will happen again if you run it as a regular user instead of root, or without using sudo. That's somewhat expected and we will fix it so it doesn't crash, but prints a nice error message. That is being tracked in bug #268879. landscape-sysinfo, however, is something else. It can run both as root or as a regular user. When run as a regular user, it parses a config file in the user's home directory (inside ~/.landscape/ actually), and that's where it also logs its output. The crash you reported happened while trying to log something there: it got a permission denied error. That's odd, because it would mean that the user cannot write to his/her own home directory. I can only see this happening if it was run via sudo to another user, like this: $ sudo -u anotheruser landscape-sysinfo If user "foo" ran the above, we would see a crash, because landscape- sysinfo would be running as "anotheruser" but with "foo"'s environment, in particular his HOME var. This, however, would work: $ sudo -u anotheruser -H landscape-sysinfo landscape-sysinfo is designed to print a summary of the system information upon a terminal/ssh login. It can run every time such a login happens, or every 10min via a cron job that will cache that information. You can configure this behaviour via "dpkg --reconfigure landscape-common" and "update-motd --enable". So, if you want to keep trying to reproduce the crash, please use "landscape-sysinfo" in your tests, which is what crashed according to the original apport report. Thanks! -- landscape-sysinfo crashed with IOError in __init__() https://bugs.launchpad.net/bugs/270007 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
