Your message dated Wed, 18 Jan 2012 12:27:39 +0100
with message-id <20120118122739.9f735cb475826fe51cb3e...@yahoo.com>
and subject line Done: Starting the program ends with SIGSEGV
has caused the Debian Bug report #646396,
regarding Starting the program ends with SIGSEGV
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
646396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtimer
Version: 2.0.0-1
Severity: grave
Any attempt to run the program ends with SIGSEGV
$ gtimer
(gtimer:11974): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT
(object)' failed
[1] 11974 segmentation fault gtimer
In Annex output error.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-486
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gtimer depends on:
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-21
ii libcairo2 1.10.2-6.1
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.7-1
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.8-1
ii libgtk2.0-0 2.24.7-1
ii libpango1.0-0 1.29.4-2
ii libx11-6 2:1.4.4-2
ii libxext6 2:1.3.0-3
ii libxss1 1:1.2.1-2
gdb_gtimer
Description: Binary data
--- End Message ---
--- Begin Message ---
Package: gtimer
Version: 2.0.0-1
Currently "gtimer" works well, it runs properly.
--- End Message ---
