This bug was fixed in the package notification-daemon - 0.4.0-0ubuntu4
---
notification-daemon (0.4.0-0ubuntu4) jaunty-proposed; urgency=low
* debian/patches/09_change_themes_crash_rev1.patch resolve (LP: #131227)
- fix crash when changing themes (based on the patch from
copied to karmic
** Changed in: notification-daemon (Ubuntu)
Status: Fix Committed = Fix Released
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I am able to reproduce this crash with the version of notification-
daemon in jaunty, 0.4.0-0ubuntu3, and can confirm that the version of
notification-daemon in jaunty-proposed, 0.4.0-0ubuntu4, does not crash,
despite running a similar for-loop that mvo posted, which caused the
released version to
Eek, of course, immediately after I did that, I managed to cause it to
crash; if I do:
gconftool --type string -s /apps/notification-daemon/theme standard
sleep 2 notify-send -t 1 lala gconftool --type string
-s /apps/notification-daemon/theme ubuntu sleep 2 notify-send -t
1
Accepted notification-daemon into jaunty-proposed; please test and give
feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed
for documentation how to enable and use -proposed. Thank you in advance!
** Changed in: notification-daemon (Ubuntu)
Milestone: jaunty-updates =
Just for the record, the removal of Wl,--as-needed is also required,
otherwise the daemon crashes when it loads libsexy. The reason seems to
be that libsexy is not mapped into memory from the daemon. So when the
theme engine module is loaded it maps libsexy and registers with the
gobject system.
I uploaded a fixed version (that works for me and survives the TEST CASE)
into my PPA at:
deb http://ppa.launchpad.net/mvo/ubuntu jaunty main
Feedback is welcome.
** Changed in: notification-daemon (Ubuntu Jaunty)
Status: Incomplete = Fix Committed
** Description changed:
Binary
** Changed in: notification-daemon (Ubuntu Jaunty)
Milestone: None = jaunty-updates
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: notification-daemon (Ubuntu Jaunty)
Status: Confirmed = In Progress
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ok, sorry. even with the patch I can still reproduce the problem when
running /usr/bin/notification-properties and switching themes while they
are displayed.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because
It might be worthwhile to convert the code to use GtkLinkButton and
see if that fixes the problem.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thanks for your patch, I tested it, but I can still trigger the crash
with:
$ notify-send lala ; sleep 5; gconftool -t string -s /apps
/notification-daemon/theme standard ; notify-send lala; gconftool -t
string -s /apps/notification-daemon/theme ubuntu; sleep 10; notify-send
lala
(sometimes
I commited the patch to
lp:~ubuntu-desktop/notification-daemon/ubuntu
but the crash is still not fixed in this version :/
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop
I looked a bit into it and it seems to be unreleated to the patch. I
sponsor the patch now, it fixes the problem at hand. A alternative
approach would be to use g_timeout_add() in the destroy_engine() code
and have a really_destory_engine() function that is run on the next
gtk_main_loop and does
I modified the patch a bit because there is already a
theme_destroy_notification () function so no need to have a additional
one. But the effect is the same, one crash fixed, but still crashing in
SexyUrl label. I suspect its a bug in libsexy because using a stock
GtkLabel does not seem to crash.
** Changed in: notification-daemon (Ubuntu Jaunty)
Target: ubuntu-9.04-beta = None
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ok, look at this solution...I had to add a new function used to destroy
properly notification gtk_widget (nw) and engine.
I noticed that the problem was in an uncorrected closure of a G_Modules after
the destruction of the widget.
Practically the daemon destroys engine, in particular
yes, this patch is probably wrong. Most likely its a not cancelled dbus
call/signal subscription.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
unsubscribing main sponsors; please re-subscribe if you have the right
patch.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Yes they have right, this patch not destroy old engine.
But probably I found the problem. I noticed that the daemon crash when the
function destroy_engine it is call from gtk_widget_destroy in function
_notify_timeout_destroy.
If you comment the g_module_close(engine-module) in
Thanks for your patch!
I seems like with the patch applied the memory of active_engine is never
freed. I think while this fixes the crash, its not the right fix.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification
** Changed in: notification-daemon (Ubuntu)
Assignee: Ubuntu Sponsors for main (ubuntu-main-sponsors) = Michael Vogt
(mvo)
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
did somebody send the change to the upstream bug tracker? what do you
think about the change mvo, that's a crash which gets quite some
duplicates
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a
After update it works good.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to notification-daemon in ubuntu.
--
desktop-bugs mailing list
It should remain as confirmed for now I think. The next step is to apply
the patch to the ubuntu package and use that to create a debdiff. The
debdiff should the be attached to this bug and then you subscribe
ubuntu-main-sponsors or ubuntu-universe-sponsors as appropriate and
request sponsorship
** Changed in: notification-daemon (Ubuntu)
Assignee: Antonio Litterio (antonio-litterio-gmail) = (unassigned)
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: notification-daemon (Ubuntu)
Target: None = ubuntu-9.04-beta
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ok I have follow the guidelines, and I attached the correct patch.
Thanks Martin and all for the help.
** Attachment added: fix crash notification-daemon when change themes
http://launchpadlibrarian.net/22483722/notification-daemon_0.4.0-0ubuntu3.debdiff
** Changed in: notification-daemon
** Changed in: notification-daemon (Ubuntu)
Status: Triaged = Fix Released
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: notification-daemon (Ubuntu)
Status: Fix Released = Fix Committed
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Not sure what the procedure is, here. How do we go about testing
whether the patch worked for us? Wait for the next alpha/beta, or will
it eventually go into the repository and we'll get it as an update, or
what.
--
notification-daemon crashed with SIGSEGV in strcmp()
Tchalvak you're right, I wring. I put what return confirmed or In
progress? excuse yet.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: notification-daemon (Ubuntu)
Status: Fix Committed = Confirmed
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ah, Indeed thanks for the info. Just wanted to see how it looked and was
disappointed with that error, but it works now thank you. :)
On Sun, Feb 8, 2009 at 11:22 AM, Josh Holland
jshholl...@googlemail.comwrote:
Happens to me in alpha 4 in a VM. Clicking on preview a second time
makes it work
I can report the same for me as Kestal. I crashes on live cd and clean install
(alpha4).
It crashes with ubuntu theme or default.
As Kestal reported when I click second time it works.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received
** Changed in: notification-daemon (Ubuntu)
Assignee: Michael Vogt (mvo) = Antonio Litterio (antonio-litterio-gmail)
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop
I solved this bus.
The problem was the incorrect delete previous theme when this change.. in
daemon application notification_daemon
I noticed that it crash when change theme and i have found the problem in
notification_daemon in engine.
The problem it is:
when change theme in function
Gracias por la ayuda Antonio.
Saludos!
2009/2/7 Antonio Litterio antonio.litte...@gmail.com
I solved this bus.
The problem was the incorrect delete previous theme when this change.. in
daemon application notification_daemon
I noticed that it crash when change theme and i have found the
Same in Ubuntu 9.04 Alpha 4
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to notification-daemon in ubuntu.
--
desktop-bugs mailing list
This has been occurring for me since its been introduced. I can easily
confirm this.. ubuntu theme or default one.
Though, when I do click it a second time (After the crash message) it
works.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You
For me it fails when I select Standard Theme in Pop-up notifications.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to notification-daemon in
automatically reported bug
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to notification-daemon in ubuntu.
--
desktop-bugs mailing list
I have a similar prolem to Ara, but further clicking simply throwns more
of these errors.
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Same bug -- Easy to duplicate.
Preferences - Pop-Up Notifications
Theme: Ubuntu Theme
Click Preview -- Crash happens
Theme: Standard Theme
Click Preview -- Notification Works
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug
This bug occurs when chaning the settings of the notification deamon. It
had during me testing Ubuntu 9.04 Alpha 3
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I am marking this bug as public. It does not contain any sensitive
information.
** Visibility changed to: Public
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Attachment removed: apport report
http://launchpadlibrarian.net/20544882/_usr_lib_notification-
daemon_notification-daemon.999.crash
--
notification-daemon crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/131227
You received this bug notification because you are a member
yes that's pretty easy to reproduce, just click on preview on the
notification-properties dialog. Michael may you have a look to it?
thanks.
** Changed in: notification-daemon (Ubuntu)
Assignee: (unassigned) = Michael Vogt (mvo)
Status: Confirmed = Triaged
--
notification-daemon
48 matches
Mail list logo
