closing the bug since there was no reply to the question nor new
activity or duplicate
** Changed in: indicator-sound (Ubuntu)
Importance: Undecided => Low
** Changed in: indicator-sound (Ubuntu)
Status: Confirmed => Invalid
** Changed in: indicator-sound
Importance: Medium => Low
** Changed in: indicator-sound
Status: Incomplete => Confirmed
** Changed in: indicator-sound (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/95311
Launchpad Janitor isn't confused, this isn't fixed yet. :)
** Changed in: indicator-sound (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953111
Title
No reports since I tidied up the g_error fix. Marking incomplete with a
view to it expiring unless others in the meantime report similar issues.
** Changed in: indicator-sound
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Branch linked: lp:ubuntu/indicator-sound
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953111
Title:
indicator-sound-service crashed with SIGABRT in raise()
To manage notifications about this bu
This bug was fixed in the package indicator-sound - 0.8.4.1-0ubuntu1
---
indicator-sound (0.8.4.1-0ubuntu1) precise; urgency=low
* New upstream release.
- fix i18n of indicator-sound's accessible description (LP: #957517)
- don't abort isound via g_error() if it can't connec
This seems to be some problem in the depths of GLib dbus. For now I will leave
this bug as confirmed just to collate the bugs.
ISound however should now not abort if it does come up against some problematic
DBus behavior.
** Changed in: indicator-sound
Status: Fix Committed => Confirmed
Not so sure where this is coming from. I did notice that I was using
g_errors instead of g_criticals. Attached branch rectifies this.
** Branch linked: lp:~cjcurran/indicator-sound/use_g_critical_instead_of_g_error
** Changed in: indicator-sound
Status: In Progress => Fix Committed
--
Y
** Changed in: indicator-sound
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953111
Title:
indicator-sound-service crashed with SIGABRT in raise()
To manage no
Duplicate bug #830715 has a slightly less corrupt log message:
StacktraceTop:
g_assertion_message (domain=, file=,
line=, func=0x7fddc43a0be0 , message=0x7fddc003aa20 "assertion failed: (fd_id ==
data->extra_fd_count)") at /build/buildd/glib2.0-2.31.6/./glib/gtestutils.c:1810
--
You received
** Changed in: indicator-sound
Milestone: None => 0.8.4.0
** Changed in: indicator-sound
Status: Confirmed => Triaged
** Changed in: indicator-sound (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Also affects: indicator-sound
Importance: Undecided
Status: New
** Changed in: indicator-sound
Status: New => Confirmed
** Changed in: indicator-sound
Importance: Undecided => Medium
** Changed in: indicator-sound
Assignee: (unassigned) => Conor Curran (cjcurran)
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-sound (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953111
Titl
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953111
Title:
indicator-sound-service crashed with SIGABRT in raise()
To manage notifications about this bug go to:
ht
14 matches
Mail list logo
