This bug is marked as invalid and closed because lack of my information.
So notoriousdbp, you should open a new bug report.
And there, you should attach valgrind.log by following instructions.
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/346569/comments/5
Thank you.
--
g
The system which has the bug is gone on re-installing, I'm sorry for
that.
The above valgrind.log is on re-installed normally working system with
the same machine.
--
gnome-settings-daemon crashed with signal 7
https://bugs.launchpad.net/bugs/346569
You received this bug notification because you
This is Valgrind log under normally working system.
I killed gnome-settings-daemon on gnome-system-monitor.
And I enter the following line:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log gnome-settings-daemon
** At
I re-installed Jaunty, so I don't have the system crashing gnome-
settings-daemon.
Is Valgrind test useful under normally working Jaunty?
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log gnome-settings-daemon
Is thi
I searched "gnome-settings-daemon" in gnome-system-log,
but no hit except apport.log.
So, I gave up and re-install Jaunty.
I tried to get the same circumstance.
With fglrx, hung-up very easily.
But after reboot, the system works normally.
I only have /var/log/ and /var/crash/ at that time.
The ot
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/24198508/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24198509/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/24198510/Disassembly.txt
** Attachm
