Re: Transition of Qt to 5.12.5
Downloaded latest plasma-workspace 4:5.14.5.1-4 and it works. Thanks!! Il 24/10/19 07:32, Matthieu Gallien ha scritto: On Wednesday, October 23, 2019 9:05:11 PM CEST Lisandro Damián Nicanor Pérez Meyer wrote: Hi! Hello El mié., 23 oct. 2019 16:01, luca.pedrielli escribió: Thanks for your workI'm still not very familiar with debian tools Best, Luca. I have just uploaded plasma-workspace, it should fix the crash Thanks a lot for the very quick fix. Thanks to all people involved in solving this. Best regards -- Saluti, Luca Pedrielli
Re: Transition of Qt to 5.12.5
On Wednesday, October 23, 2019 9:05:11 PM CEST Lisandro Damián Nicanor Pérez Meyer wrote: > Hi! Hello > El mié., 23 oct. 2019 16:01, luca.pedrielli escribió: > > Thanks for your workI'm still not very familiar with debian tools > > Best, Luca. > > I have just uploaded plasma-workspace, it should fix the crash Thanks a lot for the very quick fix. Thanks to all people involved in solving this. Best regards
Re: Transition of Qt to 5.12.5
Lisandro Damián Nicanor Pérez Meyer - 23.10.19, 21:05:11 CEST: > El mié., 23 oct. 2019 16:01, luca.pedrielli escribió: > > Thanks for your workI'm still not very familiar with debian > > tools > > Best, Luca. > > I have just uploaded plasma-workspace, it should fix the crash Affected users who do not like to wait for the updated packages to appear can download "right side" of the two files manually from the upstream patch [Notifications] Don't bind model inside headerItem] https://phabricator.kde.org/D24654 and copy them to /usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/Notifications.qml /usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/main.qml Make a copy of the old files first, just in case. Then restarting plasmashell by first stopping the process and starting it for example through krunner should fix the issue. It did for me. Thanks, -- Martin
Re: Transition of Qt to 5.12.5
Lisandro Damián Nicanor Pérez Meyer - 23.10.19, 21:05:11 CEST: > El mié., 23 oct. 2019 16:01, luca.pedrielli > escribió: > > Thanks for your workI'm still not very familiar with debian > > tools > > Best, Luca. > > I have just uploaded plasma-workspace, it should fix the crash Now isn't that a great turn-around time? And a good example of several people working together, everyone doing their part. Thank you, Lisandro. Thanks also to Mitya who brought my digging for a fix to a conclusion. Let's hope the fix works well. Until then my plasmashell will collect a few more crashes. Who has the high score on those? :) Thanks, -- Martin
How to report bugs (was: Re: Transition of Qt to 5.12.5)
luca.pedrielli - 23.10.19, 21:01:06 CEST: > Thanks for your workI'm still not very familiar with debian tools > Best, Luca. reportbug PACKAGENAME guides you through the process quite well. You can read about how to report bugs at https://www.debian.org/Bugs/Reporting Some stuff may be outdated there, cause I usually recommend checking about upstream bug reports and report there as well if not already done – so the Debian package maintainer won't have to. This work can help the small Debian/Kubuntu Qt/KDE team a lot. There is also some information about applicable severity levels: https://www.debian.org/Bugs/Developer#severities If unsure I tend to err on using a to low level. It can always be raised. Best, -- Martin
Re: Transition of Qt to 5.12.5
Hi! El mié., 23 oct. 2019 16:01, luca.pedrielli escribió: > Thanks for your workI'm still not very familiar with debian tools > Best, Luca. > I have just uploaded plasma-workspace, it should fix the crash >
Re: Transition of Qt to 5.12.5
Thanks for your workI'm still not very familiar with debian tools Best, Luca. Il 23/10/19 20:37, Martin Steigerwald ha scritto: Dear Luca. Martin Steigerwald - 23.10.19, 18:51:19 CEST: luca.pedrielli - 23.10.19, 11:45:46 CEST: plasmashell crashes with notification :( I can reproduce it everytime with: $ kdialog --passivepopup 'text' 5 Thank you for report. I can reproduce it. So while apt dist-upgrade worked smoothly so far, you may like to wait with an upgrade until this is fixed or a generic work-around if found. plasma-workspace: plasmashell with Qt 5.12.5 crashes on any notification https://bugs.debian.org/943344 […] Of course next time, Luca, feel free to report a bug yourself. I just reported the issue straight away on bug tracker and pinged other Debian/ Kubuntu Qt/KDE team members on IRC channel so it can quickly be acted upon. A fix is being tested. If it works it may be uploaded soon. Thank you again for your contribution. Best,
Re: Transition of Qt to 5.12.5
Dear Luca. Martin Steigerwald - 23.10.19, 18:51:19 CEST: > luca.pedrielli - 23.10.19, 11:45:46 CEST: > > plasmashell crashes with notification :( > > > > I can reproduce it everytime with: > > > > $ kdialog --passivepopup 'text' 5 > > Thank you for report. I can reproduce it. > > So while apt dist-upgrade worked smoothly so far, you may like to wait > with an upgrade until this is fixed or a generic work-around if > found. > > plasma-workspace: plasmashell with Qt 5.12.5 crashes on any > notification https://bugs.debian.org/943344 […] Of course next time, Luca, feel free to report a bug yourself. I just reported the issue straight away on bug tracker and pinged other Debian/ Kubuntu Qt/KDE team members on IRC channel so it can quickly be acted upon. A fix is being tested. If it works it may be uploaded soon. Thank you again for your contribution. Best, -- Martin
Re: Transition of Qt to 5.12.5
luca.pedrielli - 23.10.19, 18:55:13 CEST: > plasmashell crash on any notification debug info: > > -- > - > > Application: Plasma (plasmashell), signal: Segmentation fault > Using host libthread_db library > "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 > (Thread 0x7f69a1ce4880 (LWP 15853))] > > Thread 8 (Thread 0x7f697dca2700 (LWP 16144)): > #0 0x7f69a52f0db5 in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib/x86_64-linux-gnu/libpthread.so.0 Thank you. Feel free to add this to the bug report I just created if its different enough from the backtrace I sent there. Thanks, -- Martin
Re: Transition of Qt to 5.12.5
plasmashell crash on any notification debug info: --- Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f69a1ce4880 (LWP 15853))] Thread 8 (Thread 0x7f697dca2700 (LWP 16144)): #0 0x7f69a52f0db5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f69a64097ef in QWaitConditionPrivate::wait (deadline=..., this=0x55f1425ba9c0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55f1425aaae0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f69a64098d9 in QWaitCondition::wait (this=0x55f1425aaae8, mutex=0x55f1425aaae0, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f69a8205009 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f69a82052ad in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f69a64038d2 in QThreadPrivate::start (arg=0x55f1425aaa60) at thread/qthread_unix.cpp:361 #7 0x7f69a52eafb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f69a60a72ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f697e4e0700 (LWP 16143)): #0 0x7f69a609cd2f in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f69a459609e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f69a45961bf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f69a661880b in QEventDispatcherGlib::processEvents (this=0x7f697b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f69a65c171b in QEventLoop::exec (this=this@entry=0x7f697e4dfce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f69a6402751 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f697f8fa2a8 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f69a64038d2 in QThreadPrivate::start (arg=0x55f14255d540) at thread/qthread_unix.cpp:361 #8 0x7f69a52eafb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f69a60a72ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f6985166700 (LWP 16117)): #0 0x7f69a6098900 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f69a45dccef in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f69a4595bee in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f69a4596042 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f69a45961bf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f69a661880b in QEventDispatcherGlib::processEvents (this=0x7f6978000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f69a65c171b in QEventLoop::exec (this=this@entry=0x7f6985165ce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f69a6402751 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f69a817aeb6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f69a64038d2 in QThreadPrivate::start (arg=0x55f13fa79f20) at thread/qthread_unix.cpp:361 #10 0x7f69a52eafb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f69a60a72ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f69874e9700 (LWP 16102)): #0 0x7f69a52f0db5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f69a64097ef in QWaitConditionPrivate::wait (deadline=..., this=0x55f13fa762c0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55f14008cc50, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f69a64098d9 in QWaitCondition::wait (this=0x55f14008cc58, mutex=0x55f14008cc50, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f69a8205009 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f69a82052ad in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f69a64038d2 in QThreadPrivate::start (arg=0x55f14008cbd0) at thread/qthread_unix.cpp:361 #7 0x7f69a52eafb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f69a60a72ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f699abe7700 (LWP 15923)): #0 0x7f69a8a473f0 in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2 #1 0x7f69a6402de6 in get_thread_data () at thread/qthread_unix.cpp:239 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:239 #3 0x7f69a6618ef1 in postEventSourcePrepare (timeout=0x
Re: Transition of Qt to 5.12.5
Hi Luca. luca.pedrielli - 23.10.19, 11:45:46 CEST: > plasmashell crashes with notification :( > > I can reproduce it everytime with: > > $ kdialog --passivepopup 'text' 5 Thank you for report. I can reproduce it. So while apt dist-upgrade worked smoothly so far, you may like to wait with an upgrade until this is fixed or a generic work-around if found. plasma-workspace: plasmashell with Qt 5.12.5 crashes on any notification https://bugs.debian.org/943344 Backtrace should be there soon, just send a mail with it a moment ago. For now it is also here: https://paste.debian.net/1109353/ Thanks, -- Martin
Re: Transition of Qt to 5.12.5
plasmashell crashes with notification :( I can reproduce it everytime with: $ kdialog --passivepopup 'text' 5 -- Saluti, Luca Pedrielli
Re: Transition of Qt to 5.12.5
after latest update plasmashell segfault on login, but restart. as workaround I have disabled network-manager active connection notification in systemsettings. - Saluti, Luca Pedrielli
Re: Transition of Qt to 5.12.5
On maandag 21 oktober 2019 21:20:38 CEST Martin Steigerwald wrote: > Careful with "apt dist-upgrade" Use safe-upgrade signature.asc Description: This is a digitally signed message part.
Re: Transition of Qt to 5.12.5
Le lundi 21 octobre 2019, 21:20:38 CEST Martin Steigerwald a écrit : > Hi! > > Mitya started transition of Qt to 5.12.5 . Careful with "apt dist- > upgrade"! Wait until completion. > > Best, Good news. I hope that he solved the problem of kmail and print message. Cheers. Philippe Merlin
