This bug is easily reproducible, but not with the same command. It is also fatal and most of the time requires reinstall of the system. Therefore Valgrind is not easy to use. I have one more consolekit crash report in /var/crash, but I guess you will not be able to tell me how to do a backtrace. There are two comments that could reveal the area of trouble of the bug, maybe even the trigger:
1) something similar to Bug #244218: This bug was marked by you as having a useful log. I was able to reproduce something very similar in Bug #277208. It is a landscape- client bug. I got it while trying to reproduce the landscape-sysinfo bug (Bug #270007) for Andreas. Since it was a bug invoked by a permission error I tried something like 'sudo chown -cR 1000 landscape-client ; sudo chmod -cR 777 landscape-client'. It crashed my system and I had to reboot. I also tried 'sudo chown -cR 1000 /* | sudo chmod -cR 777 /*'. This predictably crashed my system previous to planned reinstalling, to validate the aptoncd issue. I will repeat that comment under Valgrind tonight, or more likely tomorrow. Please let me know if you can think of a better way (e.g. not requiring reinstall and always reproducible) to trigger this bug under a Valgrind session. -- console-kit-daemon crashed with SIGSEGV in g_str_hash() https://bugs.launchpad.net/bugs/269651 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
