No reply, bug closed. Feel free to reopen with the asked informations if
you still get that problem
** Changed in: rhythmbox (Ubuntu)
Status: Needs Info => Rejected
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu-
it might be useful, debug log can point incorrect uses which can lead to
a crash
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sure, I will try (after vacations, i.e. next year). Is the valgrind log
useful even without reproducing the crash?
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Could you rather try getting the valgrind log as described before?
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The gdb file was from running gdb on the old coredump, but after
installing -dbg package. I have tried to reproduce but no luck. It might
be a race condition / timing issue, I have an old laptop where I am able
to do some clicking faster than gtk would be used to. I filed the bug
anyway, in case ot
What is the gdb file if you have not been able to reproduce? The
backtrace doesn't look wrong, could you get a valgrind log as described
on https://wiki.ubuntu.com/Valgrind?
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu
Sorry, I haven't been able to reproduce. This is standard Ubuntu with
Gnome and metacity.
** Attachment added: "gdb output"
http://librarian.launchpad.net/5430584/gdb-rhythmbox.txt
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing
Do you still have that problem? What window manager do you use? Could
you attach a complete crash file to the bug maybe?
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
(I tried twice to attach the full gdb output, launchpad is not
behaving.)
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for that debug package. Here is a new backtrace:
#0 0xb75c984b in IA__gdk_window_set_transient_for (window=0x871c680,
parent=0x8467860) at gdkwindow-x11.c:2913
#1 0xb7854b60 in gtk_window_transient_parent_realized (parent=0x82ce800,
window=0x8627090) at gtkwindow.c:1831
#2 0xb7858566 i
Thanks for your bug. Could you install libgtk2.0-0-dbg and try to get a
backtrace with it?
** Changed in: rhythmbox (Ubuntu)
Importance: Untriaged => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
rhythmbox segfault in gdk_window_set_tran
** Attachment added: "apport crash report (small)"
http://librarian.launchpad.net/4411523/_usr_bin_rhythmbox.4mSjxJ.crash
--
rhythmbox segfault in gdk_window_set_transient_for
https://launchpad.net/bugs/61944
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
12 matches
Mail list logo
