Rodrigo says he has an idea about the issue
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Michael Terry (mterry) = Rodrigo Moya (rodrigo-moya)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
** Branch linked: lp:~rodrigo-moya/ubuntu/natty/gnome-settings-
daemon/fix_685785
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
https://bugs.launchpad.net/bugs/685785
Title:
gnome-settings-daemon
See attached branch. I think this should fix it, so please Matt, can you
test it? To build the package, just run, from the branch:
bzr bd -- -b
and install the packages that it builds.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This bug was fixed in the package gnome-settings-daemon -
2.32.1-0ubuntu5
---
gnome-settings-daemon (2.32.1-0ubuntu5) natty; urgency=low
* debian/patches/06_use_application_indicator.patch:
- Initialize variable to avoid crashes on free (LP: #685785)
-- Rodrigo Moya
Mike, as Chris already has tons of bugs assigned, do you have some time
to look into this? Thanks!
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Chris Coulson
(chrisccoulson)
** Changed in: gnome-settings-daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
https://bugs.launchpad.net/bugs/685785
Title:
gnome-settings-daemon crashed
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
@Chris - It looks like your hypothesis was correct.
I've rebuilt gnome-settings-daemon with DEB_BUILD_OPTIONS=noopt
nostrip to get a full stack trace, and filed a new crash report as bug
692149. Here's the popup_menu_set_group stack frame showing group_number
g:
#5 0x7f4cb00667b0 in
I rebuilt gnome-settings-daemon for debugging, and just had it crash
again. Unfortunately, telepathy-gabble is also still crashing routinely
on my system (bug 668306) and this seems to have prevented apport from
capturing the crash because they both crashed at the same time:
apport (pid 2974) Thu
Two other symptoms I've seen which may be related:
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 141 (XInputExtension)
Minor opcode of failed request: 37 (X_ChangeDeviceProperty)
Device id in failed request: 0x17
Serial number of
I've tried repeatedly suspending and resuming my laptop, and also
connecting and disconnecting a USB keyboard while it's running, to try
to trigger this problem. So far, I have been unsuccessful in finding a
reproducer, though it continues to crash as shown in comment #9.
--
You received this
@Chris, can you tell if this is the same as bug 658777 or not?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
https://bugs.launchpad.net/bugs/685785
Title:
gnome-settings-daemon crashed with
Bug 658777 was a different issue, but still one that could have caused a
similar crash, and I fixed that one already.
We could just initialize the pointer that I think is being wrongly freed
here, but the condition that causes it to happen shouldn't really occur
anyway, so I'd like to try and
On Tue, Dec 14, 2010 at 12:30:29PM -, Chris Coulson wrote:
We could just initialize the pointer that I think is being wrongly freed
here, but the condition that causes it to happen shouldn't really occur
anyway, so I'd like to try and figure that out too. How often does this
normally
Hmmm, it's a shame that the trace doesn't show the value of group_number
in frame #1. If group_number g, then there would be a condition where
free() is called on an uninitialized pointer, which I guess is what is
happening here (layout_name looks fairly uninitialized to me)
--
You received
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
https://bugs.launchpad.net/bugs/685785
Title:
gnome-settings-daemon crashed with SIGSEGV in __libc_free()
--
16 matches
Mail list logo
