Processing control commands:
> tags -1 +fixed-upstream
Bug #804694 [libqt5xcbqpa5] libqt5xcbqpa5 SIGSEGV crashes sporadically at
QXcbWindow::handleClientMessageEvent
Added tag(s) fixed-upstream.
--
804694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804694
Debian Bug Tracking Sys
Control: tags -1 +fixed-upstream
On Mon, 16 Nov 2015 16:52:27 +0300, Dmitry Shachnev wrote:
> Qt has some known problems with multi-monitor setup right now. According to
> Alexander at the upstream bug I filed, it should be fixed when [1] is merged.
>
> [1]:
Hi Markus,
On Mon, Nov 16, 2015 at 11:30:34AM +0100, Markus Frosch wrote:
> Thanks for your efforts.
>
> It seems like the bug vanished kind of.
>
> Quassel sometimes still goes away, but without a SIGSEGV, this is another
> problem.
>
> I updated gnome and mutter due to other problems to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for your efforts.
It seems like the bug vanished kind of.
Quassel sometimes still goes away, but without a SIGSEGV, this is another
problem.
I updated gnome and mutter due to other problems to the unstable versions
(3.18.2-1) last week.
Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-49450
Hallo Markus,
On Thu, Nov 12, 2015 at 02:18:42PM +0100, Markus Frosch wrote:
> I'm running Debian testing for more than 3 years, reinstalled stretch on a
> new notebook months ago (April).
>
> It never crashed like this.
I have
Processing control commands:
> forwarded -1 https://bugreports.qt.io/browse/QTBUG-49450
Bug #804694 [libqt5xcbqpa5] libqt5xcbqpa5 SIGSEGV crashes sporadically at
QXcbWindow::handleClientMessageEvent
Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-49450'.
--
804694: h
On Thursday 12 November 2015 14:18:42 Markus Frosch wrote:
[snip]
> > Also, do you know if it is a new bug in Qt 5.5, or did it exist with Qt
> > 5.4 too?
> I think yes, this started with 5.5.
>
> I'm running Debian testing for more than 3 years, reinstalled stretch on a
> new notebook months
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.11.2015 16:05, Dmitry Shachnev wrote:
> It would be nice if you could provide a more useful stacktrace (i.e. with
> qtbase5-dbg installed).
Hi Dmitry,
Oh sure, sorry for that. Here it is:
Program received signal SIGSEGV, Segmentation
Hallo Markus,
On Tue, Nov 10, 2015 at 04:54:36PM +0100, Markus Frosch wrote:
> Applications that are based on QT can crash with a SIGSEGV.
>
> This happens for me on owncloud-client and quasselclient, others maybe
> as well, but not yet stacktraced.
>
> Here is a backtrace for quasselclient.
>
Package: libqt5xcbqpa5
Version: 5.5.1+dfsg-6
Severity: important
Applications that are based on QT can crash with a SIGSEGV.
This happens for me on owncloud-client and quasselclient, others maybe
as well, but not yet stacktraced.
Here is a backtrace for quasselclient.
I'll happily supply more
10 matches
Mail list logo
