This may be a teamviewer problem. I don't know if it is relevant, but when searching /var/log for any mention of munmap, I got the following results: ---------------------------------------- dvs4@dvs4-E6540:/var/log$ sudo grep -R munmap * auth.log:Dec 7 08:31:22 dvs4-E6540 sudo: dvs4 : TTY=pts/2 ; PWD=/var/log ; USER=root ; COMMAND=/bin/grep munmap alternatives.log alternatives.log.1 alternatives.log.10.gz alternatives.log.11.gz alternatives.log.12.gz alternatives.log.2.gz alternatives.log.3.gz alternatives.log.4.gz alternatives.log.5.gz alternatives.log.6.gz alternatives.log.7.gz alternatives.log.8.gz alternatives.log.9.gz apache2 apport.log apport.log.1 apport.log.2.gz apport.log.3.gz apport.log.4.gz apport.log.5.gz apport.log.6.gz apport.log.7.gz apt auth.log auth.log.1 auth.log.2.gz auth.log.3.gz auth.log.4.gz boot.log bootstrap.log btmp btmp.1 chkrootkit ConsoleKit cups dirmngr dist-upgrade dmesg dmesg.0 dmesg.1.gz dmesg.2.gz dmesg.3.gz dmesg.4.gz dpkg.log dpkg.log.1 dpkg.log.10.gz dpkg.log.11.gz dpkg.log.12.gz dpkg.log.2.gz dpkg.log.3.gz dpkg.log.4.gz dpkg.log.5.gz dpkg.log.6.gz dpkg.log.7.gz dpkg.log.8.gz dpkg.log.9.gz faillog fontconfig.log fsck git-daemon gpu-manager.log hp installer kern.log kern.log.1 auth.log:Dec 7 08:32:45 dvs4-E6540 sudo: dvs4 : TTY=pts/2 ; PWD=/var/log ; USER=root ; COMMAND=/bin/grep -R munmap alternatives.log alternatives.log.1 alternatives.log.10.gz alternatives.log.11.gz alternatives.log.12.gz alternatives.log.2.gz alternatives.log.3.gz alternatives.log.4.gz alternatives.log.5.gz alternatives.log.6.gz alternatives.log.7.gz alternatives.log.8.gz alternatives.log.9.gz apache2 apport.log apport.log.1 apport.log.2.gz apport.log.3.gz apport.log.4.gz apport.log.5.gz apport.log.6.gz apport.log.7.gz apt auth.log auth.log.1 auth.log.2.gz auth.log.3.gz auth.log.4.gz boot.log bootstrap.log btmp btmp.1 chkrootkit ConsoleKit cups dirmngr dist-upgrade dmesg dmesg.0 dmesg.1.gz dmesg.2.gz dmesg.3.gz dmesg.4.gz dpkg.log dpkg.log.1 dpkg.log.10.gz dpkg.log.11.gz dpkg.log.12.gz dpkg.log.2.gz dpkg.log.3.gz dpkg.log.4.gz dpkg.log.5.gz dpkg.log.6.gz dpkg.log.7.gz dpkg.log.8.gz dpkg.log.9.gz faillog fontconfig.log fsck git-daemon gpu-manager.log hp installer kern.log kern.log .1 grep: teamviewer/lightdm: No such file or directory ---------------------------------------- ls -al in /var/log shows the following link for teamviewer lrwxrwxrwx 1 root root 24 Jan 15 2015 teamviewer -> /opt/teamviewer/logfiles
Checking that link includes the following lightdm link: dvs4@dvs4-E6540:/var/log$ ls -al /opt/teamviewer/logfiles/ lrwxrwxrwx 1 root root 41 Dec 10 2014 dvs4 -> /home/dvs4/.config/teamviewer10/logfiles/ lrwxrwxrwx 1 root root 47 Feb 3 2015 lightdm -> /var/lib/lightdm/.config/teamviewer10/logfiles/ Checking where that should point to shows it is not there: dvs4@dvs4-E6540:/var/log$ sudo ls -al /var/lib/lightdm/* ls: cannot access /var/lib/lightdm/*: No such file or directory Because of the similarities and because I am the only user on this machine, I changed the lightdm link to match the dvs4 user link: lrwxrwxrwx 1 root root 41 Dec 7 08:36 lightdm -> /home/dvs4/.config/teamviewer10/logfiles/ I have never seen this particular error before, but I have had some annoying glitches with the way Teamviewer starts, so I will try it this way for a while and see if it seems to make any difference... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504724 Title: lightdm crashed with SIGSEGV in munmap() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1504724/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
