Re : Re: Re : Re: Subsurface on Opensuse Tumbleweed
- Dirk Hohndel a écrit : > > > On June 22, 2018 4:37:13 PM GMT+09:00, Martin Gysel wrote: > >Am 20.06.2018 um 13:04 schrieb Dirk Hohndel: > >> It builds. What happens if you resort the dive list based on a > >different column? > >once I upgraded to Qt-5.11.1 (on gentoo), the issue has gone (was there > >with 5.11) > > Qt-5.11.1 is supposed to fix more than 150 bugs. I'm glad this one is among > them. Qt 5.11.1 will land in openSUSE Tumbleweed soon: https://build.opensuse.org/request/show/616864 :) Guillaume > > In my infinite spare time I can start working on moving Windows, Mac, iOS, > and Android to 5.11.1... > > /D > > -- > from my phone. > ___ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Re : Re: Subsurface on Opensuse Tumbleweed
On June 22, 2018 4:37:13 PM GMT+09:00, Martin Gysel wrote: >Am 20.06.2018 um 13:04 schrieb Dirk Hohndel: >> It builds. What happens if you resort the dive list based on a >different column? >once I upgraded to Qt-5.11.1 (on gentoo), the issue has gone (was there >with 5.11) Qt-5.11.1 is supposed to fix more than 150 bugs. I'm glad this one is among them. In my infinite spare time I can start working on moving Windows, Mac, iOS, and Android to 5.11.1... /D -- from my phone. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Re : Re: Subsurface on Opensuse Tumbleweed
Am 20.06.2018 um 13:04 schrieb Dirk Hohndel: > It builds. What happens if you resort the dive list based on a different > column? once I upgraded to Qt-5.11.1 (on gentoo), the issue has gone (was there with 5.11) /martin ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface on Opensuse Tumbleweed
Am Mittwoch, 20. Juni 2018, 22:15:27 CEST schrieb Thiago Macieira: > On Wednesday, 20 June 2018 12:35:45 PDT Martin Gysel wrote: > > I get the following backtrace: > > > > QPainter::begin: Paint device returned engine == 0, type: 2 > > Thanks Martin. > > I don't see anything in the backtrace belonging to Subsurface, so this > appears to be a regular Qt regression. Turns out there were a lot of > changes to QHeaderView earlier this year, so one of the must be at fault. I > can't spot which one just by looking though. > > To help constrain the search, do you know if this warning was printed with > Qt 5.10 too? I switch from 5.9.x to 5.11, so I don't know > > > #3 0x72724f74 in QPainter::begin(QPaintDevice*) () from > > /usr/lib64/libQt5Gui.so.5 > > #4 0x73551777 in () from /usr/lib64/libQt5Widgets.so.5 > > #5 0x73551c0c in QHeaderView::mousePressEvent(QMouseEvent*) () > > from /usr/lib64/libQt5Widgets.so.5 > > I'm trying to guess which frame is that ??, but it's not clear what it is. > My first guess was QHeaderViewPrivate::setupSectionIndicator, which does > have a QPainter, but that function is painting on a QPixmap and that > wouldn't have printed the warning. But that leaves me out of options. > > Can you install the debug symbols for the library? > > zypper in libQt5Gui5-debuginfo > > That should resolve the ?? to something useful, and possibly also give us > line numbers. I this still needed after the backtrace from Dietrich? If so I can compile 5.11.1 with debug symbols (I'm on gentoo) > > PS: I'm experimenting with an optimised build of Qt5 that you can find at > https://build.opensuse.org/package/show/ > home:thiagomacieira:branches:openSUSE:Factory/libqt5-qtbase is there any related patch included I should try? /martin ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface on Opensuse Tumbleweed
On Wednesday, 20 June 2018 13:53:03 PDT Dietrich Meyer wrote: > Here is another backtrace, running subsurface 4.7.8-372 on Tumbleweed, not > sure if this can give any more clues... Sorry, it's exactly the same: > #9 0x7fd01de07127 in QPainter::begin(QPaintDevice*) () at /usr/lib64/ > libQt5Gui.so.5 > #10 0x7fd01ec586ce in () at /usr/lib64/libQt5Widgets.so.5 > #11 0x7fd01ec58b4c in QHeaderView::mousePressEvent(QMouseEvent*) () at / > usr/lib64/libQt5Widgets.so.5 -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface on Opensuse Tumbleweed
Hi, > On Wednesday, 20 June 2018 12:35:45 PDT Martin Gysel wrote: > > I get the following backtrace: > > > > QPainter::begin: Paint device returned engine == 0, type: 2 > Here is another backtrace, running subsurface 4.7.8-372 on Tumbleweed, not sure if this can give any more clues... - Application: subsurface (subsurface), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd024f0ce80 (LWP 5979))] Thread 8 (Thread 0x7fcfda5d5700 (LWP 5992)): #0 0x7fd01b8e3179 in poll () at /lib64/libc.so.6 #1 0x7fd016620429 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd01662053c in g_main_context_iteration () at /usr/lib64/ libglib-2.0.so.0 #3 0x7fd01c9c988b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd01c97114a in QEventLoop::exec(QFlags) () at /usr/lib64/ libQt5Core.so.5 #5 0x7fd01c7ac36a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd01c7b6b58 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fd02407459b in start_thread () at /lib64/libpthread.so.0 #8 0x7fd01b8eda1f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fcfd9dd4700 (LWP 5990)): #0 0x7fd02407a899 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/ libpthread.so.0 #1 0x7fd01c7b7820 in QWaitCondition::wait(QMutex*, unsigned long) () at / usr/lib64/libQt5Core.so.5 #2 0x7fd01c7ae81e in () at /usr/lib64/libQt5Core.so.5 #3 0x7fd01c7b6b58 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fd02407459b in start_thread () at /lib64/libpthread.so.0 #5 0x7fd01b8eda1f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fcfe0fc6700 (LWP 5986)): #0 0x7fd02407db34 in read () at /lib64/libpthread.so.0 #1 0x7fd016664ab0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd01661ff17 in g_main_context_check () at /usr/lib64/ libglib-2.0.so.0 #3 0x7fd0166203d0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd01662053c in g_main_context_iteration () at /usr/lib64/ libglib-2.0.so.0 #5 0x7fd01c9c988b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd01c97114a in QEventLoop::exec(QFlags) () at /usr/lib64/ libQt5Core.so.5 #7 0x7fd01c7ac36a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fd01d725f85 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fd01c7b6b58 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fd02407459b in start_thread () at /lib64/libpthread.so.0 #11 0x7fd01b8eda1f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fcff29ba700 (LWP 5985)): #0 0x7fd02407a56c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/ libpthread.so.0 #1 0x7fcff35068db in () at /usr/lib64/dri/i965_dri.so #2 0x7fcff3506607 in () at /usr/lib64/dri/i965_dri.so #3 0x7fd02407459b in start_thread () at /lib64/libpthread.so.0 #4 0x7fd01b8eda1f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fd00dfbe700 (LWP 5982)): #0 0x7fd016665e29 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd01661fe4c in g_main_context_check () at /usr/lib64/ libglib-2.0.so.0 #2 0x7fd0166203d0 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd01662053c in g_main_context_iteration () at /usr/lib64/ libglib-2.0.so.0 #4 0x7fd01c9c988b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd01c97114a in QEventLoop::exec(QFlags) () at /usr/lib64/ libQt5Core.so.5 #6 0x7fd01c7ac36a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd0159f2a85 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7fd01c7b6b58 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fd02407459b in start_thread () at /lib64/libpthread.so.0 #10 0x7fd01b8eda1f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fd00e9ff700 (LWP 5981)): #0 0x7fd01b8e3179 in poll () at /lib64/libc.so.6 #1 0x7fd016620429 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd01662053c in g_main_context_iteration () at /usr/lib64/ libglib-2.0.so.0 #3 0x7fd01c9c988b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd01c97114a in QEventLoop::exec(QFlags) () at /usr/lib64/ libQt5Core.so.5 #5 0x7fd01c7ac36a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd01c7b6b58 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fd02407459b in start_thread () at /lib64/libpthread.so.0 #8 0x7fd01b8eda1f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fd00f49d700 (LWP 5980)): #0 0x7fd02407a56c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/ libpthread.so.0 #1 0x7fd01be87b3c in std::condition_variable::wait(std::unique_lock&) () at /usr/lib64/ libstdc++.so.6 #2 0x7fd021a71f17 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fd021a72059 in () at /usr/lib64/libQt5WebKit.so.5 #4 0x7fd01be8d35f in () at /usr/lib64/libstdc++.so.6 #5
Re: Subsurface on Opensuse Tumbleweed
On Wednesday, 20 June 2018 12:35:45 PDT Martin Gysel wrote: > I get the following backtrace: > > QPainter::begin: Paint device returned engine == 0, type: 2 Thanks Martin. I don't see anything in the backtrace belonging to Subsurface, so this appears to be a regular Qt regression. Turns out there were a lot of changes to QHeaderView earlier this year, so one of the must be at fault. I can't spot which one just by looking though. To help constrain the search, do you know if this warning was printed with Qt 5.10 too? > #3 0x72724f74 in QPainter::begin(QPaintDevice*) () from > /usr/lib64/libQt5Gui.so.5 > #4 0x73551777 in () from /usr/lib64/libQt5Widgets.so.5 > #5 0x73551c0c in QHeaderView::mousePressEvent(QMouseEvent*) () > from /usr/lib64/libQt5Widgets.so.5 I'm trying to guess which frame is that ??, but it's not clear what it is. My first guess was QHeaderViewPrivate::setupSectionIndicator, which does have a QPainter, but that function is painting on a QPixmap and that wouldn't have printed the warning. But that leaves me out of options. Can you install the debug symbols for the library? zypper in libQt5Gui5-debuginfo That should resolve the ?? to something useful, and possibly also give us line numbers. PS: I'm experimenting with an optimised build of Qt5 that you can find at https://build.opensuse.org/package/show/ home:thiagomacieira:branches:openSUSE:Factory/libqt5-qtbase -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface on Opensuse Tumbleweed
Am 20.06.2018 um 19:46 schrieb Thiago Macieira: > On Wednesday, 20 June 2018 07:23:27 PDT guillaume.gar...@free.fr wrote: >> If I click the dive number it is fine. Otherwise, I get a blank area with >> the following messages in console: QPainter::begin: Paint device returned >> engine == 0, type: 2 >> QPainter::setFont: Painter not active >> QPainter::setOpacity: Painter not active >> QPainter::end: Painter not active, aborted > Can you run with QT_FATAL_WARNINGS=1 and once Subsurface aborts, get the > backtrace from these warnings? > > If these are not the first warnings printed by Subsurface, increase the > number > 1 to be the number of warnings until that "QPainter::begin". > I get the following backtrace: QPainter::begin: Paint device returned engine == 0, type: 2 Thread 1 "subsurface" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x701c1ec1 in __GI_abort () at abort.c:79 #2 0x7118ffb0 in QMessageLogger::warning(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #3 0x72724f74 in QPainter::begin(QPaintDevice*) () from /usr/lib64/libQt5Gui.so.5 #4 0x73551777 in ?? () from /usr/lib64/libQt5Widgets.so.5 #5 0x73551c0c in QHeaderView::mousePressEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #6 0x7332823f in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #7 0x733c9a5e in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #8 0x73540cbb in QAbstractItemView::viewportEvent(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #9 0x7355075c in QHeaderView::viewportEvent(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #10 0x7134b85a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #11 0x732e8d55 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x732f084f in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7134ba97 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x732ef822 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib64/libQt5Widgets.so.5 #15 0x733428e3 in ?? () from /usr/lib64/libQt5Widgets.so.5 #16 0x73344ea9 in ?? () from /usr/lib64/libQt5Widgets.so.5 #17 0x732e8d7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x732f02f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7134ba97 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x725320a3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #21 0x72533d25 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #22 0x7250cc7b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #23 0x7fffe370a9eb in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #24 0x7134a88a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #25 0x71353270 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #26 0x5566b527 in main () ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface on Opensuse Tumbleweed
On Wednesday, 20 June 2018 07:23:27 PDT guillaume.gar...@free.fr wrote: > If I click the dive number it is fine. Otherwise, I get a blank area with > the following messages in console: QPainter::begin: Paint device returned > engine == 0, type: 2 > QPainter::setFont: Painter not active > QPainter::setOpacity: Painter not active > QPainter::end: Painter not active, aborted Can you run with QT_FATAL_WARNINGS=1 and once Subsurface aborts, get the backtrace from these warnings? If these are not the first warnings printed by Subsurface, increase the number 1 to be the number of warnings until that "QPainter::begin". -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Re : Re: Subsurface on Opensuse Tumbleweed
Hi all, > It builds. What happens if you resort the dive list based on a different > column? dive list disappears, following output in console: -- QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setFont: Painter not active QPainter::setOpacity: Painter not active QPainter::end: Painter not active, aborted -- but I guess you already knew this... running on up-to-date Opensuse Tumbleweed. Starting subsurface with "subsurface -vvv" doesn't give any more information when re-sorting the divelist. I am not a C++ nor QT programmer, so unable to really help except for testing. Dietrich > > > On June 20, 2018 5:40:33 PM GMT+09:00, guillaume.gar...@free.fr wrote: > >Hi, > > > >- Dirk Hohndel a écrit : > >> > On Jun 18, 2018, at 5:27 PM, Robert Helling wrote: > >> > > >> > Hi, > >> > > >> > I was informed that Opensuse upgrading to gcc8 and plasma 5.11 in > > > >Tumbleweed broke the subsurface package. I don’t know who takes care of > >that. Just to let you know. > > > >> I just kicked off new builds of current master. > >> But given that Qt 5.11 is known to cause errors for Subsurface, we > > > >need to fix those before the next release, anyway. > > > >The good news is that current daily (4.7.8.372) does build fine for > >Tumbleweed! \o/ > > > >Guillaume > > > >> /D > >> ___ > >> subsurface mailing list > >> subsurface@subsurface-divelog.org > > > >http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re : Re: Re : Re: Subsurface on Opensuse Tumbleweed
- Dirk Hohndel a écrit : > It builds. What happens if you resort the dive list based on a different > column? If I click the dive number it is fine. Otherwise, I get a blank area with the following messages in console: QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setFont: Painter not active QPainter::setOpacity: Painter not active QPainter::end: Painter not active, aborted Guillaume > > On June 20, 2018 5:40:33 PM GMT+09:00, guillaume.gar...@free.fr wrote: > > > >Hi, > > > >- Dirk Hohndel a écrit : > >> > >> > On Jun 18, 2018, at 5:27 PM, Robert Helling wrote: > >> > > >> > Hi, > >> > > >> > I was informed that Opensuse upgrading to gcc8 and plasma 5.11 in > >Tumbleweed broke the subsurface package. I don’t know who takes care of > >that. Just to let you know. > >> > >> I just kicked off new builds of current master. > >> But given that Qt 5.11 is known to cause errors for Subsurface, we > >need to fix those before the next release, anyway. > > > >The good news is that current daily (4.7.8.372) does build fine for > >Tumbleweed! \o/ > > > >Guillaume > > > >> > >> /D > >> ___ > >> subsurface mailing list > >> subsurface@subsurface-divelog.org > >> > >http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface > > -- > from my phone. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Re : Re: Subsurface on Opensuse Tumbleweed
It builds. What happens if you resort the dive list based on a different column? On June 20, 2018 5:40:33 PM GMT+09:00, guillaume.gar...@free.fr wrote: > >Hi, > >- Dirk Hohndel a écrit : >> >> > On Jun 18, 2018, at 5:27 PM, Robert Helling wrote: >> > >> > Hi, >> > >> > I was informed that Opensuse upgrading to gcc8 and plasma 5.11 in >Tumbleweed broke the subsurface package. I don’t know who takes care of >that. Just to let you know. >> >> I just kicked off new builds of current master. >> But given that Qt 5.11 is known to cause errors for Subsurface, we >need to fix those before the next release, anyway. > >The good news is that current daily (4.7.8.372) does build fine for >Tumbleweed! \o/ > >Guillaume > >> >> /D >> ___ >> subsurface mailing list >> subsurface@subsurface-divelog.org >> >http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface -- from my phone. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re : Re: Subsurface on Opensuse Tumbleweed
Hi, - Dirk Hohndel a écrit : > > > On Jun 18, 2018, at 5:27 PM, Robert Helling wrote: > > > > Hi, > > > > I was informed that Opensuse upgrading to gcc8 and plasma 5.11 in > > Tumbleweed broke the subsurface package. I don’t know who takes care of > > that. Just to let you know. > > I just kicked off new builds of current master. > But given that Qt 5.11 is known to cause errors for Subsurface, we need to > fix those before the next release, anyway. The good news is that current daily (4.7.8.372) does build fine for Tumbleweed! \o/ Guillaume > > /D > ___ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface on Opensuse Tumbleweed
> On Jun 18, 2018, at 5:27 PM, Robert Helling wrote: > > Hi, > > I was informed that Opensuse upgrading to gcc8 and plasma 5.11 in Tumbleweed > broke the subsurface package. I don’t know who takes care of that. Just to > let you know. I just kicked off new builds of current master. But given that Qt 5.11 is known to cause errors for Subsurface, we need to fix those before the next release, anyway. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
