Bug #420307 “computer-janitor-gtk crashed with SIGSEGV in gdk_wi...” : Bugs : computer-janitor package : Ubuntu

Revision history for this message

kumis (bsugianto) wrote on 2009-08-28:

#1

Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (41.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (735 bytes, text/plain; charset="utf-8")
Registers.txt Edit (959 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-29: Stacktrace.txt (retraced)

#2

Stacktrace.txt (retraced) Edit (9.4 KiB, text/plain)

StacktraceTop:IA__gdk_window_set_geometry_hints (window=0x0,
gtk_window_check_resize (
IA__g_closure_invoke (closure=0x14ba840,
signal_emit_unlocked_R (node=0x14ba890,
IA__g_signal_emit_valist (instance=0x155b030,

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-29: ThreadStacktrace.txt (retraced)

#3

ThreadStacktrace.txt (retraced) Edit (30.1 KiB, text/plain)

Changed in computer-janitor (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

to be removed (liw) wrote on 2009-09-07:

#4

Thanks for your bug report. If you can reproduce this, could you run computer-janitor-gtk from the command line, and attach the output? The stack traces included by apport are for the Python interpreter, and not useful for debugging the Python source code.

Changed in computer-janitor (Ubuntu):
status:	New → Incomplete

Revision history for this message

to be removed (liw) wrote on 2009-09-17:

#5

I think this bug, and all the bugs I've marked as duplicates of it, are due to something going wrong in how the Computer Janitor background threads use GTK+. I have not been able to figure out what it is, so instead I've attempted to make sure they never use GTK+. I have made the modifications and uploaded the new packages to my PPA at https://launchpad.net/~liw/+archive/ppa

Could all of you who have reported these problems try the 1.13.3-0ubuntu2~ppa1 version from my PPA and tell me if it works for you or not? Thanks.

Changed in computer-janitor (Ubuntu):
status:	Incomplete → Triaged
visibility:	private → public

to be removed (liw) on 2009-09-17

Changed in computer-janitor (Ubuntu):
status:	Triaged → In Progress

Revision history for this message

Shade (mrjuul) wrote on 2009-09-18: Re: [Bug 420307] Re: computer-janitor-gtk crashed with SIGSEGV in gdk_window_set_geometry_hints()

#6

New version still crashes on my computer.

/Lars

2009/9/17 Lars Wirzenius <email address hidden>

> I think this bug, and all the bugs I've marked as duplicates of it, are
> due to something going wrong in how the Computer Janitor background
> threads use GTK+. I have not been able to figure out what it is, so
> instead I've attempted to make sure they never use GTK+. I have made the
> modifications and uploaded the new packages to my PPA at
> https://launchpad.net/~liw/+archive/ppa<https://launchpad.net/%7Eliw/+archive/ppa>
>
> Could all of you who have reported these problems try the
> 1.13.3-0ubuntu2~ppa1 version from my PPA and tell me if it works for
> you or not? Thanks.
>
>
> ** Changed in: computer-janitor (Ubuntu)
> Status: Incomplete => Triaged
>
> ** Visibility changed to: Public
>
> --
> computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> https://bugs.launchpad.net/bugs/420307
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “computer-janitor” package in Ubuntu: In Progress
>
> Bug description:
> Binary package hint: computer-janitor
>
> it just crashed
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 27 21:50:54 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/computer-janitor-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: computer-janitor-gtk 1.13.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/computer-janitor-gtk
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
> SegvAnalysis:
> Segfault happened at: 0x7f1d4310a734 <gdk_window_set_geometry_hints+52>:
> testb $0x30,0x84(%rax)
> PC (0x7f1d4310a734) ok
> source "$0x30" ok
> destination "0x84(%rax)" (0x00000084) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: computer-janitor
> StacktraceTop:
> gdk_window_set_geometry_hints ()
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> g_signal_emit_valist ()
> Title: computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> Uname: Linux 2.6.31-7-generic x86_64
> UserGroups:
>

New version still crashes on my computer.

/Lars

2009/9/17 Lars Wirzenius <lars@ubuntu.com>

> I think this bug, and all the bugs I've marked as duplicates of it, are
> due to something going wrong in how the Computer Janitor background
> threads use GTK+. I have not been able to figure out what it is, so
> instead I've attempted to make sure they never use GTK+. I have made the
> modifications and uploaded the new packages to my PPA at
> https://launchpad.net/~liw/+archive/ppa<https://launchpad.net/%7Eliw/+archive/ppa>
>
> Could all of you who have reported these problems try the
> 1.13.3-0ubuntu2~ppa1  version from my PPA and tell me if it works for
> you or not? Thanks.
>
>
> ** Changed in: computer-janitor (Ubuntu)
>       Status: Incomplete => Triaged
>
> ** Visibility changed to: Public
>
> --
> computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> https://bugs.launchpad.net/bugs/420307
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “computer-janitor” package in Ubuntu: In Progress
>
> Bug description:
> Binary package hint: computer-janitor
>
> it just crashed
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 27 21:50:54 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/computer-janitor-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: computer-janitor-gtk 1.13.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/computer-janitor-gtk
> ProcEnviron:
>  PATH=(custom, no user)
>  LANG=en_CA.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
> SegvAnalysis:
>  Segfault happened at: 0x7f1d4310a734 <gdk_window_set_geometry_hints+52>:
> testb  $0x30,0x84(%rax)
>  PC (0x7f1d4310a734) ok
>  source "$0x30" ok
>  destination "0x84(%rax)" (0x00000084) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: computer-janitor
> StacktraceTop:
>  gdk_window_set_geometry_hints ()
>  ?? () from /usr/lib/libgtk-x11-2.0.so.0
>  g_closure_invoke ()
>  ?? () from /usr/lib/libgobject-2.0.so.0
>  g_signal_emit_valist ()
> Title: computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> Uname: Linux 2.6.31-7-generic x86_64
> UserGroups:
>

Revision history for this message

to be removed (liw) wrote on 2009-10-13:

#7

OK, so I basically have no idea how to find and fix this problem.

Changed in computer-janitor (Ubuntu):
status:	In Progress → Confirmed

Revision history for this message

to be removed (liw) wrote on 2009-10-13:

#8

Could those having this problem please try to get a valgrind log?

1. Open a terminal.
2. Copy-paste the following commands to the command line (and do whatever you need to do to get computer-janitor to crash while using it, but don't worry if it doesn't actually remove packages):

bzr get lp:computer-janitor/trunk
cd trunk
sudo env G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log ./test-env ./computer-janitor-gtk
sudo chmod a+r valgrind.log

3. Attach valgrind.log to this bug report.

Very much thank you.

See https://wiki.ubuntu.com/Valgrind for more information.

Revision history for this message

Shade (mrjuul) wrote on 2009-10-13:

#9

valgrind.log attached.

/Lars

2009/10/13 Lars Wirzenius <email address hidden>

> Could those having this problem please try to get a valgrind log?
>
> 1. Open a terminal.
> 2. Copy-paste the following commands to the command line (and do whatever
> you need to do to get computer-janitor to crash while using it, but don't
> worry if it doesn't actually remove packages):
>
> bzr get lp:computer-janitor/trunk
> cd trunk
> sudo env G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
> --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
> ./test-env ./computer-janitor-gtk
> sudo chmod a+r valgrind.log
>
> 3. Attach valgrind.log to this bug report.
>
> Very much thank you.
>
> See https://wiki.ubuntu.com/Valgrind for more information.
>
> --
> computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> https://bugs.launchpad.net/bugs/420307
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “computer-janitor” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: computer-janitor
>
> it just crashed
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 27 21:50:54 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/computer-janitor-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: computer-janitor-gtk 1.13.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/computer-janitor-gtk
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
> SegvAnalysis:
> Segfault happened at: 0x7f1d4310a734 <gdk_window_set_geometry_hints+52>:
> testb $0x30,0x84(%rax)
> PC (0x7f1d4310a734) ok
> source "$0x30" ok
> destination "0x84(%rax)" (0x00000084) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: computer-janitor
> StacktraceTop:
> gdk_window_set_geometry_hints ()
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> g_signal_emit_valist ()
> Title: computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> Uname: Linux 2.6.31-7-generic x86_64
> UserGroups:
>

valgrind.log attached.

/Lars

2009/10/13 Lars Wirzenius <lars@ubuntu.com>

> Could those having this problem please try to get a valgrind log?
>
> 1. Open a terminal.
> 2. Copy-paste the following commands to the command line (and do whatever
> you need to do to get computer-janitor to crash while using it, but don't
> worry if it doesn't actually remove packages):
>
> bzr get lp:computer-janitor/trunk
> cd trunk
> sudo env G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v
> --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
> ./test-env ./computer-janitor-gtk
> sudo chmod a+r valgrind.log
>
> 3. Attach valgrind.log to this bug report.
>
> Very much thank you.
>
> See https://wiki.ubuntu.com/Valgrind for more information.
>
> --
> computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> https://bugs.launchpad.net/bugs/420307
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “computer-janitor” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: computer-janitor
>
> it just crashed
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 27 21:50:54 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/computer-janitor-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: computer-janitor-gtk 1.13.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/computer-janitor-gtk
> ProcEnviron:
>  PATH=(custom, no user)
>  LANG=en_CA.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
> SegvAnalysis:
>  Segfault happened at: 0x7f1d4310a734 <gdk_window_set_geometry_hints+52>:
> testb  $0x30,0x84(%rax)
>  PC (0x7f1d4310a734) ok
>  source "$0x30" ok
>  destination "0x84(%rax)" (0x00000084) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: computer-janitor
> StacktraceTop:
>  gdk_window_set_geometry_hints ()
>  ?? () from /usr/lib/libgtk-x11-2.0.so.0
>  g_closure_invoke ()
>  ?? () from /usr/lib/libgobject-2.0.so.0
>  g_signal_emit_valist ()
> Title: computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> Uname: Linux 2.6.31-7-generic x86_64
> UserGroups:
>

Revision history for this message

to be removed (liw) wrote on 2009-10-14:

#10

Shade, I don't see the attachment. Did you forget it?

Revision history for this message

Shade (mrjuul) wrote on 2009-10-14:

#11

I must have forgot, I try one more time.

/Lars

2009/10/14 Lars Wirzenius <email address hidden>

> Shade, I don't see the attachment. Did you forget it?
>
> --
> computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> https://bugs.launchpad.net/bugs/420307
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “computer-janitor” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: computer-janitor
>
> it just crashed
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 27 21:50:54 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/computer-janitor-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: computer-janitor-gtk 1.13.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/computer-janitor-gtk
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
> SegvAnalysis:
> Segfault happened at: 0x7f1d4310a734 <gdk_window_set_geometry_hints+52>:
> testb $0x30,0x84(%rax)
> PC (0x7f1d4310a734) ok
> source "$0x30" ok
> destination "0x84(%rax)" (0x00000084) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: computer-janitor
> StacktraceTop:
> gdk_window_set_geometry_hints ()
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> g_signal_emit_valist ()
> Title: computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> Uname: Linux 2.6.31-7-generic x86_64
> UserGroups:
>

Revision history for this message

Shade (mrjuul) wrote on 2009-10-14:

#12

valgrind.log Edit (4.0 KiB, text/x-log; charset=US-ASCII; name="valgrind.log")

E-mail client could not read the file, it's fixed now.

This time the file should be attached.

/Lars

2009/10/14 Lars Wirzenius <email address hidden>

> Shade, I don't see the attachment. Did you forget it?
>
> --
> computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> https://bugs.launchpad.net/bugs/420307
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “computer-janitor” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: computer-janitor
>
> it just crashed
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 27 21:50:54 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/computer-janitor-gtk
> InterpreterPath: /usr/bin/python2.6
> Package: computer-janitor-gtk 1.13.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/bin/computer-janitor-gtk
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
> SegvAnalysis:
> Segfault happened at: 0x7f1d4310a734 <gdk_window_set_geometry_hints+52>:
> testb $0x30,0x84(%rax)
> PC (0x7f1d4310a734) ok
> source "$0x30" ok
> destination "0x84(%rax)" (0x00000084) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: computer-janitor
> StacktraceTop:
> gdk_window_set_geometry_hints ()
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> g_signal_emit_valist ()
> Title: computer-janitor-gtk crashed with SIGSEGV in
> gdk_window_set_geometry_hints()
> Uname: Linux 2.6.31-7-generic x86_64
> UserGroups:
>

Revision history for this message

Barry Warsaw (barry) wrote on 2010-03-10:

#13

I've refactored c-j to use a dbus service, which eliminates the need to use threads at all. This should fix the problem and will hopefully get it into Lucid. I will try to build a PPA asap (need to update some packaging details first) for you to try out. For now, I'll target Lucid b1 though it's not certain to make it in.

Changed in computer-janitor (Ubuntu):
assignee:	nobody → Barry Warsaw (barry)
milestone:	none → ubuntu-10.04-beta-1

Colin Watson (cjwatson) on 2010-03-19

Changed in computer-janitor (Ubuntu):
milestone:	ubuntu-10.04-beta-1 → ubuntu-10.04-beta-2

Revision history for this message

Michael Vogt (mvo) wrote on 2010-03-19:

#14

Just for reference, the FeatureFreezeException bug is here: #541990

Revision history for this message

Barry Warsaw (barry) wrote on 2010-03-22:

#15

I now have CJ 2.0 in my PPA: https://edge.launchpad.net/~barry/+archive/python

Would the OP or any else having this problem please try to reproduce it with the PPA? I'll mark this as fix committed as all the refactored code is now in the CJ trunk.

Changed in computer-janitor (Ubuntu):
status:	Confirmed → Fix Committed

Revision history for this message

Jasonx8x (jason-ramirez08) wrote on 2010-04-24:

#16

0x7f1d4310a734 <gdk_window_set_geometry_hints+52>:
    testb $0x30,0x84(%rax)
0x7f1d4310a73b <gdk_window_set_geometry_hints+59>:
    je 0x7f1d4310a760 <gdk_window_set_geometry_hints+96>
0x7f1d4310a73d <gdk_window_set_geometry_hints+61>: mov 0x58(%rsp),%rbx
0x7f1d4310a742 <gdk_window_set_geometry_hints+66>: mov 0x60(%rsp),%rbp
0x7f1d4310a747 <gdk_window_set_geometry_hints+71>: mov 0x68(%rsp),%r12
0x7f1d4310a74c <gdk_window_set_geometry_hints+76>: mov 0x70(%rsp),%r13
0x7f1d4310a751 <gdk_window_set_geometry_hints+81>: add $0x78,%rsp
0x7f1d4310a755 <gdk_window_set_geometry_hints+85>: retq
0x7f1d4310a756 <gdk_window_set_geometry_hints+86>:
    nopw %cs:0x0(%rax,%rax,1)
0x7f1d4310a760 <gdk_window_set_geometry_hints+96>: mov %r13,%rsi
0x7f1d4310a763 <gdk_window_set_geometry_hints+99>: mov %rbx,%rdi
0x7f1d4310a766 <gdk_window_set_geometry_hints+102>:
    callq 0x7f1d430b4cb8 <g_type_check_instance_cast@plt>
0x7f1d4310a76b <gdk_window_set_geometry_hints+107>: cmpb $0x2,0x7c(%rax)
0x7f1d4310a76f <gdk_window_set_geometry_hints+111>:
    je 0x7f1d4310a73d <gdk_window_set_geometry_hints+61>
0x7f1d4310a771 <gdk_window_set_geometry_hints+113>: mov %r13,%rsi
0x7f1d4310a774 <gdk_window_set_geometry_hints+116>: mov %rbx,%rdi

Revision history for this message

Barry Warsaw (barry) wrote on 2010-04-24:

#17

@Jasonx8x: Please try CJ 2.0 in my PPA.

Barry Warsaw (barry) on 2010-05-26

Changed in computer-janitor (Ubuntu):
milestone:	ubuntu-10.04-beta-2 → maverick-alpha-1
status:	Fix Committed → Fix Released

Ubuntu
computer-janitor package

computer-janitor-gtk crashed with SIGSEGV in gdk_window_set_geometry_hints()

Bug Description

Duplicates of this bug

Other bug subscribers

Related blueprints

Bug attachments

Remote bug watches

Ubuntucomputer-janitor package

computer-janitor-gtk crashed with SIGSEGV in gdk_window_set_geometry_hints()

Bug Description

Duplicates of this bug

Other bug subscribers

Related blueprints

Bug attachments

Remote bug watches

Ubuntu
computer-janitor package