[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] Segfault when the dbus connection is lost
From:       Scott Kitterman <debian () kitterman ! com>
Date:       2012-04-14 19:58:59
Message-ID: 5115307.1yf5P8Ko9E () scott-latitude-e6320
[Download RAW message or body]

On Saturday, April 14, 2012 06:16:00 PM Phil Thompson wrote:
> On Sat, 14 Apr 2012 13:07:58 -0400, Scott Kitterman <debian@kitterman.com>
> 
> wrote:
> > Phil Thompson <phil@riverbankcomputing.com> wrote:
> >>On Fri, 13 Apr 2012 11:52:31 -0300, "Alejandro J. Cura"
> >>
> >><alecu@canonical.com> wrote:
> >>> Hi,
> >>> 
> >>> first of all, since I'm new to the list I'd like to thank the people
> >>> responsible for PyQt a lot for making such a great project.
> >>> I'd like to report a bug: when using DBusQtMainLoop, I'm getting
> >>> SIGSEGVs when the DBus connection is closed. I've managed to
> >>reproduce
> >>> this from Ubuntu Lucid (PyQt 4.7.2) up to Ubuntu Precise beta 2 (PyQt
> >>> 4.9.1).
> >>> 
> >>> Attached is a script that when ran shows the issue, but not every
> >>time;
> >>> on my Precise machine it happens about 3 out of 10 times; on a Lucid
> >>VM it happens every time.
> >>> 
> >>> Please let me know if I should attach any other info, or if there's
> >>some simple way to fix it that I'm missing.
> >>> 
> >>> BTW: I've seen this bug reported elsewhere[0] for projects using
> >>PyQt,
> >>
> >>> but I'm not sure where I should report it for PyQt.
> >>> 
> >>> thanks!
> >>
> >>Should be fixed in tonight's PyQt snapshot.
> >>
> > I suspect I will be able to figure it out by diffing the two snapshots,
> > but I'd appreciate it if you would provide the patch that fixes this so
> we can apply it to the current release.  Ubuntu is very close to release,
> so they aren't in a position to wait for the next PyQt release.
> > 
> > Scott K
> 
> Attached.
> 
> Why wasn't the bug (which is 5 years old) not reported upstream earlier?

Thanks for the quick turnaround.

I've only recently started helping with PyQt maintenance, primarily in Debian, 
but also some in Ubuntu.  It was initially reported as a PyKDE bug.  
Personally, I'm working my way through old bugs to try and get things caught 
up, but with some of them it's really hard to know which ones are still valid.  

It was reported now because Alejandro had come up with a reduced test case and 
I encouraged him to join the list and report it.

Scott K
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]