notify-osd crashed with SIGSEGV in ___fprintf_chk()

StacktraceTop:___fprintf_chk (fp=0x0, flag=1, format=0x41f6ad "[%s, %s %s] %s\n")
log_bubble (bubble=0x16bb010,
stack_notify_handler (self=0x1621100,
dbus_glib_marshal_stack_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER (closure=0x7ffffbbeaf90,
gobject_message_function (connection=0x15ba550,

It seems the logger cannot open/reset the file. Could you check permissions and other file attributes on ~/.cache/notify-osd.log?

Waves% ls -alh ~/.cache/notify-osd.log
-rw-r--r-- 1 root root 193 2009-03-20 03:02 /home/spider/.cache/notify-osd.log

Now why it's owned by root, I do not know....

removing it and hoping that this goes away.

I am also getting this problem. I have checked the permissions of the log file in my .cache directory and the file is owned by my user. I have also tried to remove the log file. This does not solve the problem.

The program that causes this crash on my system (asus eee 1000h) is "Eee PC ACPI Settings". Please find additional version information about this program in the attached picture.

Hope this helps, thanks for the great work with ubuntu.

BR
/thorsten

I got the same problem with eee pc acpi settings and jaunty beta, i have asus 900.

Some more information. The errors i can see via "dmesg" when the crashes occur look like this:

[ 8300.264466] notify-osd[28880]: segfault at 0 ip b77e291d sp bfee3c08 error 4 in libc-2.9.so[b76e7000+15c000]

Just upgraded to version 0.9.7-0ubuntu1 of notify-osd via aptitude. The problem is still there, sorry.

Mar 30 20:14:42 hal kernel: [ 103.208826] notify-osd[3984]: segfault at 0 ip b77f691d sp bf9f9f08 error 4 in libc-2.9.so[b76fb000+15c000]

I performed the upgrade by issuing the following

aptitude update
aptitude full-upgrade

So the system should be fully up to date. I am using the SE mirror.

those new comments are not clear, did you open a bug using apport and did you get redirected there? how do you know you are getting the same crash?

Sebastian: You are correct in your assumption that i was redirected here from apport. I am not sure that i get the same crash, sorry. Should I open an new bug?

no need to open a new bug no, it was just not obvious if apport redirected you there or if you had a similar issue (in such case it's better to try to open a bug with apport to see if that's really the same crash)

I'm trying to get hold of that "Eee PC ACPI Settings"-program. Can anybody tell me where to get its source from? Thanks in advance!

I downloaded it here: http://www.informatik.uni-bremen.de/~elmurato/EeePC/Jaunty_Eeeasy-Scripts.tar.gz

Ok, thanks for the report. I've committed a patch (rev. 268) to fix the bug.

Awesome. I wish I could code, but hopefully submitting bug reports will
help!

On Tue, Mar 31, 2009 at 3:51 PM, David Barth <email address hidden>wrote:

> Ok, thanks for the report. I've committed a patch (rev. 268) to fix the
> bug.
>
> ** Changed in: notify-osd (Ubuntu)
> Status: Confirmed => Fix Committed
>
> --
> notify-osd crashed with SIGSEGV in ___fprintf_chk()
> https://bugs.launchpad.net/bugs/345770
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “notify-osd” source package in Ubuntu: Fix Committed
>
> Bug description:
> Binary package hint: notify-osd
>
> I started my IM client and the notifyer crashed instantly.
>
> Jaunty, all updated,
> notify-osd:
> Installed: 0.9.6-0ubuntu2
> Candidate: 0.9.6-0ubuntu2
> Version table:
> *** 0.9.6-0ubuntu2 0
> 500 http://se.archive.ubuntu.com jaunty/main Packages
> 100 /var/lib/dpkg/status
>
> ProblemType: Crash
> Architecture: amd64
> CrashCounter: 1
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/lib/notify-osd/notify-osd
> NonfreeKernelModules: nvidia
> Package: notify-osd 0.9.6-0ubuntu2
> ProcCmdline: /usr/lib/notify-osd/notify-osd
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/zsh
> Signal: 11
> SourcePackage: notify-osd
> StacktraceTop:
> ___fprintf_chk (fp=0x0, flag=1, format=0x41f6ad "[%s, %s %s] %s\n")
> log_bubble ()
> stack_notify_handler ()
> dbus_glib_marshal_stack_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER
> ()
> ?? () from /usr/lib/libdbus-glib-1.so.2
> Title: notify-osd crashed with SIGSEGV in ___fprintf_chk()
> Uname: Linux 2.6.28-11-generic x86_64
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>

--
010010010110011000100000011101000110100001101001011100110010000001110000011000010111010001110100011001010111001001101110001000000111001101110101011001110110011101100101011100110111010001110011001000000110000101101110001000000110100101101110011101000110010101101100011011000110100101100111011001010110111001110100001000000110011001101111011100100110001101100101001000000110000101110100001000000111011101101111011100100110101100100000011010010110111000100000011010010111010001110011001000000111000001110010011011110110010001110101011000110111010001101001011011110110111000101100001000000110010001101111011001010111001100100000010001000100111001000001001000000110111001101111011101000010000001110011011101010110011101100111011001010111001101110100001000000110000101101110001000000110100101101110011101000110010101101100011011000110100101100111011001010110111001110100001000000110011001101111011100100110001101100101001000000110000101110100001000000111011101101111011100100110101100111111
http://www.roubaixinteractive.com/PlayGround/Binary_Conversion/Binary_To_Text.asp

david did you push your fixes somewhere? lp:notify-osd has only 265 revisions right now

This bug was fixed in the package notify-osd - 0.9.8-0ubuntu1

---------------
notify-osd (0.9.8-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - introduced env. variable NOTIFY_OSD_MUST_NOT_USE_COMPOSITING for UNR
    - added fallback positioning-behaviour for corner-case
      when no gnome-panel was found (lp: #351516, #351593)
    - added sanity-check for existence of $HOME/.cache (lp: #345770)
  * debian/patches/correct_service_install.patch:
    - the change is in the new version

 -- Sebastien Bacher <email address hidden> Wed, 01 Apr 2009 15:33:59 +0200

Fix in version 0.9.8-0ubuntu1 verified on my eee 1000h. Works great.
Thanks for the excellent work with ubuntu.
/thorsten

I just updated, but it still happens on my EeePC 900