Your message dated Wed, 29 Oct 2014 23:09:01 +0200
with message-id <[email protected]>
and subject line Re: Bug#759206: libgrilo-0.2-1: rhythmbox crashed using grilo
plugin
has caused the Debian Bug report #759206,
regarding libgrilo-0.2-1: rhythmbox crashed using grilo plugin
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 [email protected]
immediately.)
--
759206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759206
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgrilo-0.2-1
Version: 0.2.10-1
Severity: important
Dear Maintainer,
It often crashed with grilo plugin:
Output in syslog:
rhythmbox[10673]: segfault at a00000002 ip 00007f2382aaddce sp
00007fff206f4070 error 4 in libgrltracker.so[7f2382aa5000+f000]
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (650, 'testing'), (600, 'stable'), (500,
'testing-updates'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libgrilo-0.2-1 depends on:
ii libc6 2.19-9
ii libglib2.0-0 2.40.0-4
ii libsoup2.4-1 2.46.0-2
ii libtotem-plparser18 3.10.2-3
ii libxml2 2.9.1+dfsg1-4
ii multiarch-support 2.19-9
libgrilo-0.2-1 recommends no packages.
Versions of packages libgrilo-0.2-1 suggests:
ii grilo-plugins-0.2 0.2.12-4
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 759206 unreproducible
thanks
On Fri, Oct 24, 2014 at 11:50:07AM +0300, Alberto Garcia wrote:
> > Did you try with those versions of grilo/grilo-plugins? Is the
> > problem still happening? Can you get a backtrace? Thanks!
I'm unable to reproduce this and I don't have any information to debug
so I'm closing it.
Please reply if you can still reproduce it with the latest version.
Thanks!
Berto
--- End Message ---
