On Freitag, 8. April 2016 17:25:06 CEST Aleix Pol wrote:
> On Fri, Apr 8, 2016 at 3:42 PM, Andreas Hartmetz
wrote:
> > On Donnerstag, 7. April 2016 20:33:19 CEST Andreas Hartmetz wrote:
> >> On Mittwoch, 6. April 2016 20:10:53 CEST Aleix Pol wrote:
> >> > Hi,
> >> > I've seen a couple of times su
On Fri, Apr 8, 2016 at 3:42 PM, Andreas Hartmetz wrote:
> On Donnerstag, 7. April 2016 20:33:19 CEST Andreas Hartmetz wrote:
>> On Mittwoch, 6. April 2016 20:10:53 CEST Aleix Pol wrote:
>> > Hi,
>> > I've seen a couple of times such backtrace [1] which shows Qt
>> > waiting
>> > for something that
On Donnerstag, 7. April 2016 20:33:19 CEST Andreas Hartmetz wrote:
> On Mittwoch, 6. April 2016 20:10:53 CEST Aleix Pol wrote:
> > Hi,
> > I've seen a couple of times such backtrace [1] which shows Qt
> > waiting
> > for something that never happens. An easy way to reproduce is to
> > load
> > konv
On Mittwoch, 6. April 2016 20:10:53 CEST Aleix Pol wrote:
> Hi,
> I've seen a couple of times such backtrace [1] which shows Qt waiting
> for something that never happens. An easy way to reproduce is to load
> konversation (or any application with KDBusService::Unique), hide it
> and run it again.
On Wednesday, April 6, 2016 8:10:53 PM CEST Aleix Pol wrote:
> Hi,
> I've seen a couple of times such backtrace [1] which shows Qt waiting
> for something that never happens. An easy way to reproduce is to load
> konversation (or any application with KDBusService::Unique), hide it
> and run it agai
Hi,
I've seen a couple of times such backtrace [1] which shows Qt waiting
for something that never happens. An easy way to reproduce is to load
konversation (or any application with KDBusService::Unique), hide it
and run it again. The exit call will never be fulfilled in the second
process.
Any id
