Am Mittwoch, den 13.06.2012, 13:39 +0200 schrieb Paul Menzel:
> forwarded 675852 https://bugs.freedesktop.org/show_bug.cgi?id=51031
> quit
> 
> 
> Am Sonntag, den 10.06.2012, 17:08 -0400 schrieb Douglas F. Calvert:
> > Package: colord
> > Version: 0.1.21-1
> > Followup-For: Bug #675852
> 
> Douglas, unfortunately using reportbug is not quite useful for doing
> follow ups, since it does not add people to CC being involved in the
> report and it messes up threading.
> 
> Downloading the last message over the mbox link or getting the whole
> mbox with `bts show --mbox 675852` is preferable in my experience. You
> then can import it from `~/.devscripts_cache/bts/` to your mail program.
> 
> > Here is what i did:
> > 
> > 1. I rebuilt the colord packages with debuging symbols
> 
> It would be great if a package with debugging symbols could be provided.
> James, do you need a separate report for that?
> 
> > 2. Logged into gnome and killed colord / colord-sane and restarted them 
> > under gdb
> > 3. When I restart gdm3 colord crashes. 
> 
> Great that you rebuilt the package and could reproduce the crash I am
> also seeing.
> 
> > I have attached the gdb log. I ran
> > 
> > bt
> > bt full
> > thread apply all bt
> > thread apply all bt full
> 
> I created a new ticket at the freedesktop.org Bugzilla tracked as
> #51031.

The author replied to upstream’s report [2]. But running

        $ LANG=C sudo /usr/lib/i386-linux-gnu/colord/colord -v

I do not see any critical messages. But it has not crashed either. Can
someone of you reproduce the crash and look for critical warnings?


Thanks,

Paul


> [1] https://bugs.freedesktop.org/show_bug.cgi?id=51031
[2] https://bugs.freedesktop.org/show_bug.cgi?id=51031#c1

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to