This confusion comes from the fact that initially landscape-sysinfo had two running modes: at every login, and via cron.
When run via cron, there is no user logging in, so any backtraces would be stored in /var/log. But when run at login time, we are executing as an user, so we had to write somewhere else. That's where the ~/.landscape comes from. Are the backtraces in your /var/log/landscape/sysinfo.log file old by any change? Perhaps this machine was upgraded from an older distro instead of being a new installation? -- /etc/motd tells me to read ~/.landscape/sysinfo.log which does not exist https://bugs.launchpad.net/bugs/517454 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
