The last few comments (#22 onwards) seem to refer to another crash
entirely - that other crash was reported as bug #931820 , which (IMHO
erronously) was marked as a duplicate from this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Crashes on startup on Precise LiveCD for me. Shows no notifications after
restarting it under Valgrind, simply prints
GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width 0'
failed
Killed after I run notify-send test several times.
Valgrind log and GDB output are attached.
** Attachment added: gdb_output.txt
https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/122637/+attachment/2903704/+files/gdb_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, we can't reopen the bug, we don't seem to have the permissions to
do it. All statuses are grayed out for commoners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
here's a more complete gdb output, with a backtrace and debugging
symbols installed
** Attachment added: gdb_with_backtrace
https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/122637/+attachment/2904516/+files/gdb_with_backtrace
--
You received this bug notification because
crashed when waking up computer in Lubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed with signal 5 in g_logv()
To manage notifications about this bug
Happens all the time to me in Lubuntu Precise Pangolin. Notification-
daemon is worthless. It worked when I first upgraded, but recent updates
have broken it, not sure which ones.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upgrade from Lucid-Precise, not sure what the crash was. Otherwise,
upgrade went smoothly.
Hardware: Advent G10 netbook (rebadged MSI Wind)
fatman@jizo-bosatsu:~$ uname -a
Linux jizo-bosatsu 3.2.0-18-generic-pae #28-Ubuntu SMP Fri Mar 2 22:11:12 UTC
2012 i686 i686 i386 GNU/Linux
--
You
lubuntu precise pangolin Alpha1 updated to 3.2.0-12 on IBM Thinkpad T40
DISTRIB_DESCRIPTION=Ubuntu precise (development branch)
Linux ThinkPadT40 3.2.0-12-generic #21-Ubuntu SMP Tue Jan 31 18:40:37 UTC 2012
i686 i686 i386 GNU/Linux
Crashed a bit after boot. Just had a terminal session up and
Crashed 12.04 on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed with signal 5 in g_logv()
To manage notifications about this bug go to:
Also crashed in lubuntu 11.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed with signal 5 in g_logv()
To manage notifications about this bug go to:
just crashed on 11.10 (oneiric) amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed with signal 5 in g_logv()
To manage notifications about this bug go
Apport brought me here after notification daemon crashed on oneiric ?
This bug seems quite old, regression ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed
I was starting with a Lubuntu 11.10 beta1 on VirtualBox
(3.0.0-9-generic) and I got the bug message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed with
To add more details, apport point to this bug report when trying to
report it automaticly. It's reproductible with Lubuntu ISO 20110830.2.
I opened a new bug report (bug 838383) with the details, but maybe
apport need to be fixed.
--
You received this bug notification because you are a member
** Changed in: notification-daemon (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed with signal 5 in g_logv()
To manage
Crash after livecd boot.
** Attachment added: CoreDump.gz
https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/122637/+attachment/260/+files/CoreDump.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: crashlogs.tar
https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/122637/+attachment/2333417/+files/crashlogs.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/122637
Title:
notification-daemon crashed with signal 5 in g_logv()
To manage notifications about this bug go to:
please open a new report this was closed ages ago and also is not
installed by default in oneiric so no way you get that using the cd.
** Changed in: notification-daemon (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
--
** Changed in: notification-daemon (Ubuntu)
Assignee: Brian Murray (brian-murray) = (unassigned)
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I no longer run Ubuntu 7.10 so I can't actively help with this bug. Good
luck. (Unsubscribing)
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Killed notification-daemon after all, but I already had this warning
***MEMORY-WARNING***: notification-daemon[23571]: GSlice:
g_thread_init() must be called before all other GLib functions; memory
corruption due to late invocation of g_thread_init() has been detected;
this program is likely to
no compiz, but I will go back into my crash report to find out the most
I can about it.
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Here's the valgrind logs of gnome-power-manager, I hope that the right
program. I'll try again with notification-daemon later
I had trouble reproducing this as the timing of taking the power
connection out and in again seems to be quite specific. I'm wondering if
it has something to do with the
Can't run Valgrind on notification-daemon
[EMAIL PROTECTED]:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
notification-daemon
valgrind: notification-daemon: command not found
[EMAIL PROTECTED]:~$
--
you can attach the valgrind log to a new gnome-power-manager bug, the
bug is not a notification-daemon one
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
You need to use /usr/lib/notification-daemon
Could you install gnome-power-manager-dbgsym and get a new log? There is
an error in the log and no detail
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you
Here's what I just got trying to run valgrind and notification-daemon
[EMAIL PROTECTED]:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --num-callers=40 --log-
file=valgrind.log /usr/lib/notification-daemon/notification-daemon
***MEMORY-WARNING***:
the warning is not likely the cause of the crasher. The gnome-power-
manager error should go to a new bug
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
ok, those the g_logv function are misleading, the real crash is the
gdk_x_error there. Do people having the bug use compiz?
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs,
Ok as one of the users whose bug has been marked as a duplicate of this
bug, no haven't used compiz.
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
The gdk_x_error seems to be just another error message logger, the bug
seems to lay between notify_daemon_notify_handler and a call to
XGetWindowProperty. Perhaps XGetWindowProperty is getting called with
an invalid parameter? length=2147483647 looks odd, but could also be an
invalid pointer.
Yes, using compiz -- this is right from the very first load after
install + dist-upgrade. Dell D610 (ATI graphics.)
Paul.
Sebastien Bacher wrote:
ok, those the g_logv function are misleading, the real crash is the
gdk_x_error there. Do people having the bug use compiz?
--
...and I've seen this bug with and without compiz enabled.
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Thanks 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 add the file as an attachment to
your bug report. This will greatly help us in tracking down your
problem.
**
From by backtrace (bug 122909) I see:
(gdb) bt
#0 IA__g_logv (log_domain=0x2ae47c213bd3 Gdk, log_level=value optimized
out, format=0x2ae47c230794 %s, args1=0x7fff2fa06800)
at /build/buildd/glib2.0-2.13.5/glib/gmessages.c:503
#1 0x2ae47cdf6693 in IA__g_log (log_domain=0x2ae47d5f3960 ,
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/8218774/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/8218775/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/8218776/Disassembly.txt
** Attachment
StacktraceTop:IA__g_logv (log_domain=value optimized out,
log_level=G_LOG_LEVEL_ERROR, format=0xb7a775a0 %s, args1=0xbfb7760c `[K\b�)
IA__g_log (log_domain=0xb7a5b0a3 Gdk, log_level=G_LOG_LEVEL_ERROR,
format=0xb7a775a0 %s) at /build/buildd/glib2.0-2.13.5/glib/gmessages.c:517
gdk_x_error
** Changed in: notification-daemon (Ubuntu)
Importance: Undecided = Medium
Status: New = Triaged
--
notification-daemon crashed with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122637
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
42 matches
Mail list logo
