We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: notify-osd (Ubuntu
My bad, the right line will be:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log
/usr/lib/notify-osd/notify-osd
Also, you'll have to
1) kill notify-osd (killall notify-osd) which would be already running then,
otherw
I'm getting the same output:
$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log notify-osd
/usr/lib/notify-osd/notify-osd
valgrind: notify-osd: command not found
--
notify-osd crashed with SIGSEGV in realloc()
http
I believe you should use CmdLine from crash output:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log notify-osd
/usr/lib/notify-osd/notify-osd
--
notify-osd crashed with SIGSEGV in realloc()
https://bugs.launchpad.n
I'm not sure how to make such log, This is my console output:
$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log notify-osd
valgrind: notify-osd: command not found
--
notify-osd crashed with SIGSEGV in realloc()
ht
could you provide the valgrind log ? Thanks.
** Changed in: notify-osd (Ubuntu)
Status: New => Incomplete
--
notify-osd crashed with SIGSEGV in realloc()
https://bugs.launchpad.net/bugs/348995
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm having this issue on Karmic quite constantly, for no apparent
reason.
** Changed in: notify-osd (Ubuntu)
Status: Invalid => New
--
notify-osd crashed with SIGSEGV in realloc()
https://bugs.launchpad.net/bugs/348995
You received this bug notification because you are a member of Ubuntu
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Visibility chang
