Re: Status of Plasma 5.18/5.19?
Hi Marco, On Montag, 29. Juni 2020 13:30:31 CEST Marco Valli wrote: > In data lunedì 29 giugno 2020 13:12:28 CEST, Norbert Preining ha scritto: > > Another great contribution that lines up perfectly with the rest! > > "I remain politely silent about your comments" > > https://imgflip.com/i/12zl00 May I suggest you stick to constructive forms of communication? Yes, Norbert could have answered your assertion that Christian Marillat is no longer remembered or no longer active in Debian in a more verbose form. Yet, what was your contribution to the debate when you sent "facepalm", twice? Cheers, Johannes
Bug#963993: dolphin crashes with segfault
Package: dolphin Version: 4:20.04.2-1 Severity: important Dear Maintainer, I do not know,if this is already been reported, but at the moment dolphin is crashing at start. I am running debian/testing amd64 with plasma5. This is the output, when dophin is crashing,hope it helps: snip -- Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2a237c4840 (LWP 48133))] Thread 3 (Thread 0x7f2a21a5d700 (LWP 48136)): #0 0x7ffe617e88d3 in clock_gettime () #1 0x7f2a2d7ca317 in __GI___clock_gettime (clock_id=1, tp=0x7f2a21a5caa0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:33 #2 0x7f2a2b7280e1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2a2b7269f9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2a2b726fc5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2a2b72853e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2a29197d7f in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f2a2919872b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f2a2919891f in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f2a2b7287db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2a2b6d16db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2a2b5126f1 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2a2b9a64e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #13 0x7f2a2b513872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2a29d6cf27 in start_thread (arg=) at pthread_create.c:479 #15 0x7f2a2d7bd31f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2a22700700 (LWP 48135)): #0 0x7f2a2d7b2b7f in __GI___poll (fds=0x7f2a226ffc68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2a29fa0d02 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2a29fa298a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2a232edca0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f2a2b513872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2a29d6cf27 in start_thread (arg=) at pthread_create.c:479 #6 0x7f2a2d7bd31f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2a237c4840 (LWP 48133)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f2a2d6e555b in __GI_abort () at abort.c:79 #6 0x7f2a2cccf9f2 in KXMLGUIClient::setXML(QString const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #7 0x7f2a2ccd2452 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #8 0x7f2a2ccf658b in KXmlGuiWindow::createGUI(QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #9 0x7f2a2ccf736b in KXmlGuiWindow::setupGUI(QSize const&, QFlags, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #10 0x7f2a2ccf743d in KXmlGuiWindow::setupGUI(QFlags, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #11 0x7f2a2d8dc972 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #12 0x7f2a2d8cba7f in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #13 0x7f2a2d6e6e0b in __libc_start_main (main=0x5561ba073050, argc=1, argv=0x7ffe617a3098, init=, fini=, rtld_fini=, stack_end=0x7ffe617a3088) at ../csu/libc-start.c:308 #14 0x5561ba07308a in _start () [Inferior 1 (process 48133) detached] -- snap - Does this tell you all you need? Thank for any help, hints or tipps. Best regards Hans -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-1-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dolphin depends on: ii baloo-kf5 5.70.0-2 ii kinit 5.70.0-1 ii kio5.70.1-1 ii libc6 2.30-8 ii libdolphinvcs5 4:20.04.2-1 ii libkf5activities5 5.70.0-1 ii libkf5baloo5 5.70.0-2 ii libkf5baloowidgets54:20.04.2-1 ii libkf5bookmarks5 5.70.0-1 ii libkf5codecs5 5.70.0-1 ii libkf5completion5 5.70.0-1 ii libkf5configcore5 5.70.0-1 ii
Bug#963983: marked as done (python3-pyside2.qtsvg: segfault on import)
Your message dated Mon, 29 Jun 2020 22:47:16 +0200
with message-id <06b2b72f-daee-0815-789c-6f89fc2e6...@debian.org>
and subject line Re: python3-pyside2.qtsvg: segfault on import
has caused the Debian Bug report #963983,
regarding python3-pyside2.qtsvg: segfault on import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
963983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyside2.qtsvg
Version: 5.15.0-1
Severity: grave
$ gdb python3
...
Reading symbols from python3...
Reading symbols from
/usr/lib/debug/.build-id/97/0f19629d98e5c631b44f6803fa34a5a07c3806.debug...
(gdb) r
Starting program: /usr/bin/python3
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 3.8.3 (default, May 14 2020, 11:03:12)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from PySide2 import QtSvg
Program received signal SIGSEGV, Segmentation fault.
0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*, char
const*, char const*, PyType_Spec*, char const**, void (*)(void*),
SbkObjectType*, _object*, unsigned int) ()
from
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15
(gdb) bt
#0 0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*,
char const*, char const*, PyType_Spec*, char const**, void (*)(void*),
SbkObjectType*, _object*, unsigned int)
() from
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15
#1 0x7731ec41 in ?? () from
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#2 0x7732a6a3 in PyInit_QtSvg () from
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#3 0x0067d0aa in _PyImport_LoadDynamicModuleWithSpec (
spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>, fp=) at
../Python/importdl.c:164
#4 0x0067dafd in _imp_create_dynamic_impl (module=,
file=,
spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>) at ../Python/import.c:2221
#5 _imp_create_dynamic (module=, args=,
nargs=) at ../Python/clinic/import.c.h:330
#6 0x005c066c in cfunction_vectorcall_FASTCALL (func=, args=, nargsf=,
kwnames=) at ../Objects/methodobject.c:422
#7 0x005f1da9 in PyVectorcall_Call (callable=, tuple=, kwargs={}) at ../Objects/call.c:199
#8 0x0056d160 in do_call_core (kwdict={},
callargs=(,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>,), func=, tstate=) at
../Python/ceval.c:4983
#9 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3559
#10 0x00565602 in PyEval_EvalFrameEx (throwflag=0,
f=Frame 0x77677610, for file , line 219,
in _call_with_frames_removed (f=, args=(,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>,), kwds={})) at ../Python/ceval.c:741
#11 _PyEval_EvalCodeWithName (_co=, globals=,
locals=, args=, argcount=,
kwnames=,
kwargs=0x776de7e0, kwcount=, kwstep=1, defs=0x0,
defcount=0, kwdefs=0x0, closure=0x0, name='_call_with_frames_removed',
qualname='_call_with_frames_removed')
at ../Python/ceval.c:4298
#12 0x005f12a3 in _PyFunction_Vectorcall (func=,
stack=0x776de7d0, nargsf=, kwnames=) at
../Objects/call.c:435
#13 0x0056c1bf in _PyObject_Vectorcall (kwnames=0x0, nargsf=, args=0x776de7d0, callable=) at
../Include/cpython/abstract.h:127
#14 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x959e20) at ../Python/ceval.c:4963
#15 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3469
#16 0x005f10c6 in PyEval_EvalFrameEx (throwflag=0,
f=Frame 0x776de640, for file ,
line 1357, in create_module (self=, spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None,
Processed: Bug#958479 marked as pending in qtbase-opensource-src
Processing control commands: > tag -1 pending Bug #958479 [qt5-qmake] qmake passes unsupported -isystem to gcc Added tag(s) pending. -- 958479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963983: python3-pyside2.qtsvg: segfault on import
Package: python3-pyside2.qtsvg
Version: 5.15.0-1
Severity: grave
$ gdb python3
...
Reading symbols from python3...
Reading symbols from
/usr/lib/debug/.build-id/97/0f19629d98e5c631b44f6803fa34a5a07c3806.debug...
(gdb) r
Starting program: /usr/bin/python3
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 3.8.3 (default, May 14 2020, 11:03:12)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from PySide2 import QtSvg
Program received signal SIGSEGV, Segmentation fault.
0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*, char
const*, char const*, PyType_Spec*, char const**, void (*)(void*),
SbkObjectType*, _object*, unsigned int) ()
from
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15
(gdb) bt
#0 0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*,
char const*, char const*, PyType_Spec*, char const**, void (*)(void*),
SbkObjectType*, _object*, unsigned int)
() from
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15
#1 0x7731ec41 in ?? () from
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#2 0x7732a6a3 in PyInit_QtSvg () from
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#3 0x0067d0aa in _PyImport_LoadDynamicModuleWithSpec (
spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>, fp=) at
../Python/importdl.c:164
#4 0x0067dafd in _imp_create_dynamic_impl (module=,
file=,
spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>) at ../Python/import.c:2221
#5 _imp_create_dynamic (module=, args=,
nargs=) at ../Python/clinic/import.c.h:330
#6 0x005c066c in cfunction_vectorcall_FASTCALL (func=, args=, nargsf=,
kwnames=) at ../Objects/methodobject.c:422
#7 0x005f1da9 in PyVectorcall_Call (callable=, tuple=, kwargs={}) at ../Objects/call.c:199
#8 0x0056d160 in do_call_core (kwdict={},
callargs=(,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>,), func=, tstate=) at
../Python/ceval.c:4983
#9 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3559
#10 0x00565602 in PyEval_EvalFrameEx (throwflag=0,
f=Frame 0x77677610, for file , line 219,
in _call_with_frames_removed (f=, args=(,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>,), kwds={})) at ../Python/ceval.c:741
#11 _PyEval_EvalCodeWithName (_co=, globals=,
locals=, args=, argcount=,
kwnames=,
kwargs=0x776de7e0, kwcount=, kwstep=1, defs=0x0,
defcount=0, kwdefs=0x0, closure=0x0, name='_call_with_frames_removed',
qualname='_call_with_frames_removed')
at ../Python/ceval.c:4298
#12 0x005f12a3 in _PyFunction_Vectorcall (func=,
stack=0x776de7d0, nargsf=, kwnames=) at
../Objects/call.c:435
#13 0x0056c1bf in _PyObject_Vectorcall (kwnames=0x0, nargsf=, args=0x776de7d0, callable=) at
../Include/cpython/abstract.h:127
#14 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x959e20) at ../Python/ceval.c:4963
#15 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3469
#16 0x005f10c6 in PyEval_EvalFrameEx (throwflag=0,
f=Frame 0x776de640, for file ,
line 1357, in create_module (self=, spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>)) at ../Python/ceval.c:741
#17 function_code_fastcall (globals=, nargs=,
args=, co=) at ../Objects/call.c:283
#18 _PyFunction_Vectorcall (func=, stack=,
nargsf=, kwnames=) at ../Objects/call.c:410
#19 0x005674c7 in _PyObject_Vectorcall (kwnames=0x0, nargsf=, args=0x777b2a30, callable=) at
../Include/cpython/abstract.h:127
#20 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x959e20) at ../Python/ceval.c:4963
#21 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3486
#22 0x005f10c6 in PyEval_EvalFrameEx (throwflag=0,
f=Frame 0x777b28b0, for file , line 556,
in module_from_spec (spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None)
Re: wayland
On 29.06.20 15:54, Borden Rhodes wrote: On Mon, 29 Jun 2020 at 09:36, Marco Möller wrote: Interested to discover Wayland without risking to lose my much personalized settings for my KDE Plasma X11 desktop environment (and without drawing in new desktop apps), is it enough to simply install package kwin-Wayland? Are there any current (Plasma X11) settings which might become changed and would not immediately be in use no more if choosing at the sddm login screen to enter a Plasma X11 session again? Marco. I brought this matter up a few weeks ago, and the response is that Wayland _shouldn't_ mulch any of your settings - but it might. KDE on Wayland in Debian has a lot of rough edges and should be considered beta. I've found I've needed to work around crashes, quirks and missing features. It's possible that a KDE app may change a setting and X won't know how to read it. Some things that work in X11 don't in Wayland and vice-versa. Thanks for this information, this is what I needed to know. I was aware already that I will be a beta tester when using it. But I then won't do this on my usual laptop. After having learned from you that Wayland and X11 do not strictly separate there settings but share them although producing interference I am then better opting for a separate OS install. Thanks a lot for the fast and helpful reply! Marco.
Re: wayland
On Mon, 29 Jun 2020 at 09:36, Marco Möller wrote: > > Interested to discover Wayland without risking to lose my much > personalized settings for my KDE Plasma X11 desktop environment (and > without drawing in new desktop apps), is it enough to simply install > package kwin-Wayland? > Are there any current (Plasma X11) settings which might become changed > and would not immediately be in use no more if choosing at the sddm > login screen to enter a Plasma X11 session again? > Marco. I brought this matter up a few weeks ago, and the response is that Wayland _shouldn't_ mulch any of your settings - but it might. KDE on Wayland in Debian has a lot of rough edges and should be considered beta. I've found I've needed to work around crashes, quirks and missing features. It's possible that a KDE app may change a setting and X won't know how to read it. Some things that work in X11 don't in Wayland and vice-versa.
wayland
Interested to discover Wayland without risking to lose my much personalized settings for my KDE Plasma X11 desktop environment (and without drawing in new desktop apps), is it enough to simply install package kwin-Wayland? Are there any current (Plasma X11) settings which might become changed and would not immediately be in use no more if choosing at the sddm login screen to enter a Plasma X11 session again? Marco.
Re: Status of Plasma 5.18/5.19?
Yes, a verbal meeting would be good, Jitsi is fine I guess. I sense that all subscribe to the need to "get KDE updates as fast as possible into Debian" . So the starting point is excellent! Let's discuss if this is correct during the meeting and depending on how that goes poll about ways forward. Normally I would offer you coffee, but this remains virtual for the moment, :=). Luc Op ma 29 jun. 2020 om 14:23 schreef Martin Steigerwald : > Hi Luc. > > Luc Castermans - 29.06.20, 13:52:39 CEST: > > Are we past the point of no return or is there an option to go to > > square one and restart? What would be needed to do so? > > I have no idea. Actually I do not really understand the conflict. > > However… > > > At the same time I note that email is a bad medium for this type of > > interaction, sorry for using this medium I am not aware of another > > one. > > I am willing to offer moderation to find a solution in case both parties > would like to have a go at finding one. We could find a Jitsi or > BigBlueButton instance to do this. I know several instances that could > be used. > > Disclaimer: I worked with Debian/Kubuntu Qt/KDE team, on some bug > triaging or regarding providing information here. And I have no > intention to change that at the moment. So I may be biased and gladly > let a less likely to be biased person offer to do the job. That written, > I learned a lot about ways to communicate that can help to find > resolutions to conflicts and allow everyone to feel accepted as a person. > > Best, > -- > Martin > > > -- Luc Castermans mailto:luc.casterm...@gmail.com
pyside2_5.15.0-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 29 Jun 2020 15:26:26 +0300 Source: pyside2 Architecture: source Version: 5.15.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 963709 Changes: pyside2 (5.15.0-2) unstable; urgency=medium . * Team upload. * Preload libGLX_mesa.so.0 in web_engine_initialize.py, to work around test failure on arm64 (closes: #963709). Checksums-Sha1: f53f105356f7e052c991addb1a2543f363a4b6a6 7013 pyside2_5.15.0-2.dsc e0387a836d96a954c58864277b1bc710cacd5a5a 51560 pyside2_5.15.0-2.debian.tar.xz ce75ddea2df92bef13ec20d6d1f1a18b4306641c 21030 pyside2_5.15.0-2_source.buildinfo Checksums-Sha256: 0b5e340ca30e2ea64245b52ed615c76141309b5b4d3ba1f783f6d7a9dc374e07 7013 pyside2_5.15.0-2.dsc 9b0cdc0c5b142d81b224b0c405c127e51d439129767038aea7e0bff014883855 51560 pyside2_5.15.0-2.debian.tar.xz f038649ee19e6b64766529dd49e5f240db7e17c2b43c8042ac7be11a5f89c260 21030 pyside2_5.15.0-2_source.buildinfo Files: 83e6a5e3e61d1dd6ab2be16129447e2c 7013 python optional pyside2_5.15.0-2.dsc 5a848d0d4c9169e0ac5bd95280667ab9 51560 python optional pyside2_5.15.0-2.debian.tar.xz ed5109f0fe8a854a85581d7e2a33180d 21030 python optional pyside2_5.15.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl753i0THG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBmRiZbWGuDy8FKEACTRU6KCwwdj1/zVKfZ2Eje92T1i6Af np9OOAvi8w82qwOqgWOfw+BhO/b8Z4J+Zz1jHrsO2+xZjrFvoGPaddfX/18eGgYf 75rJtMqH26nMaYSEhiWJ4wclFEoQv7J1gFuvxjCQskC9/MPfq0gwQFww8xwjV8l4 JyXu8n5HbMWzEu6LTE1iU016yXsf5rXJnlee8vFRBUbQv3UdffgY2/fkEZ8k7oPx MzviLWvTnQbbPRpcBTiVWEEkP0ctKrovmGfYG5ObyKZLS4bVgg2muPiJUDGkStXD ofRogOVCUe4Ue55mDBMwSdPlL5YkyOHs+XFxvoWlitG7g6b8HLUkNeE3DZDPRtgj ybLOcAik1uVZgpYH4gZdfHPjJMRLbD7XzZLRVuP3l8Dsku1luNmN7XHHr0mHgfTP wFUAXMO22P6M2aCO8zIbN0Qx4+gN24bXYIonirXr60L145SbwRDLliGbskOqIP7X 67g5ToxDPl68d2HQ9+vbAInoUiD40Q1yBIcJsCEZsB4cx1VBPuVvlaTJSULdL5v6 Luol8gK9DQewTTyuC1jtxoL/At2PVmpUZhs4IxsgPB7MpHfilr06LEXvZMNf8J6J TvC4mVF/ndDUderEsgxyDV5SBewkg8iXWBv3U7VOtS8fx24S3uFSzyyoL0osaf19 YP/izv4orihuxg== =1cGA -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of pyside2_5.15.0-2_source.changes
pyside2_5.15.0-2_source.changes uploaded successfully to localhost along with the files: pyside2_5.15.0-2.dsc pyside2_5.15.0-2.debian.tar.xz pyside2_5.15.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: Status of Plasma 5.18/5.19?
On maandag 29 juni 2020 14:15:41 CEST Martin Steigerwald wrote: > Sander van Grieken - 29.06.20, 13:23:41 CEST: > > On zondag 28 juni 2020 12:53:15 CEST Martin Steigerwald wrote: > > > Dear Marco, dear Qt/KDE team, dear Norberg, dear community, > > > > > > Marco Valli - 28.06.20, 11:12:03 CEST: > > > > Do you remember debian multimedia of Marillat, another "very > > > > experienced DD"? No? well, even preining in a few years will no > > > > longer remember by anyone. Debian yes. > > > > > > I am not sure whether it makes sense to discuss this out to the end… > > > > Well I'm afraid this topic will keep coming back occasionally until it > > is resolved in one way or the other. > > It is not on me to moderate anything here and… as I wrote I am not sure > what the best approach to proceed would be. I know, I was not addressing you specifically, it was more a general observation for the ML as a whole. I do really appreciate your offer (in your other email) for moderation, and I hope al parties seriously consider this! -- Sander
Bug#963709: marked as done (pyside2: FTBFS on arm64: web_engine_initialize test fails with "Could not initialize GLX")
Your message dated Mon, 29 Jun 2020 12:49:10 + with message-id and subject line Bug#963709: fixed in pyside2 5.15.0-2 has caused the Debian Bug report #963709, regarding pyside2: FTBFS on arm64: web_engine_initialize test fails with "Could not initialize GLX" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyside2 Version: 5.13.2-3 Severity: serious Justification: fails to build from source User: debian-qt-kde@lists.debian.org Usertags: qt5.14 Dear Maintainers, Today's pyside2 binNMU failed to build on all architectures, because of the following failing test: RUN 1: == RUN 1: ERROR: testQDate (__main__.TestDateTimeConversions) RUN 1: -- RUN 1: Traceback (most recent call last): RUN 1: File "/<>/sources/pyside2/tests/QtCore/python_conversion.py", line 41, in testQDate RUN 1: other = QDate(date) RUN 1: TypeError: 'PySide2.QtCore.QDate' called with wrong argument types: RUN 1: PySide2.QtCore.QDate(date) RUN 1: Supported signatures: RUN 1: PySide2.QtCore.QDate() RUN 1: PySide2.QtCore.QDate(int, int, int) RUN 1: RUN 1: -- It looks like Python date → QDate conversion should be handled by the conversion-qdate-pydate snippet, but for some reason this does not work. P.S. I noticed that the sid branch in git repo (which contains the current version in unstable) is not merged into master. Please fix that. -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: pyside2 Source-Version: 5.15.0-2 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of pyside2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated pyside2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 29 Jun 2020 15:26:26 +0300 Source: pyside2 Architecture: source Version: 5.15.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 963709 Changes: pyside2 (5.15.0-2) unstable; urgency=medium . * Team upload. * Preload libGLX_mesa.so.0 in web_engine_initialize.py, to work around test failure on arm64 (closes: #963709). Checksums-Sha1: f53f105356f7e052c991addb1a2543f363a4b6a6 7013 pyside2_5.15.0-2.dsc e0387a836d96a954c58864277b1bc710cacd5a5a 51560 pyside2_5.15.0-2.debian.tar.xz ce75ddea2df92bef13ec20d6d1f1a18b4306641c 21030 pyside2_5.15.0-2_source.buildinfo Checksums-Sha256: 0b5e340ca30e2ea64245b52ed615c76141309b5b4d3ba1f783f6d7a9dc374e07 7013 pyside2_5.15.0-2.dsc 9b0cdc0c5b142d81b224b0c405c127e51d439129767038aea7e0bff014883855 51560 pyside2_5.15.0-2.debian.tar.xz f038649ee19e6b64766529dd49e5f240db7e17c2b43c8042ac7be11a5f89c260 21030 pyside2_5.15.0-2_source.buildinfo Files: 83e6a5e3e61d1dd6ab2be16129447e2c 7013 python optional pyside2_5.15.0-2.dsc 5a848d0d4c9169e0ac5bd95280667ab9 51560 python optional pyside2_5.15.0-2.debian.tar.xz ed5109f0fe8a854a85581d7e2a33180d 21030 python optional pyside2_5.15.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl753i0THG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBmRiZbWGuDy8FKEACTRU6KCwwdj1/zVKfZ2Eje92T1i6Af np9OOAvi8w82qwOqgWOfw+BhO/b8Z4J+Zz1jHrsO2+xZjrFvoGPaddfX/18eGgYf 75rJtMqH26nMaYSEhiWJ4wclFEoQv7J1gFuvxjCQskC9/MPfq0gwQFww8xwjV8l4 JyXu8n5HbMWzEu6LTE1iU016yXsf5rXJnlee8vFRBUbQv3UdffgY2/fkEZ8k7oPx MzviLWvTnQbbPRpcBTiVWEEkP0ctKrovmGfYG5ObyKZLS4bVgg2muPiJUDGkStXD ofRogOVCUe4Ue55mDBMwSdPlL5YkyOHs+XFxvoWlitG7g6b8HLUkNeE3DZDPRtgj ybLOcAik1uVZgpYH4gZdfHPjJMRLbD7XzZLRVuP3l8Dsku1luNmN7XHHr0mHgfTP wFUAXMO22P6M2aCO8zIbN0Qx4+gN24bXYIonirXr60L145SbwRDLliGbskOqIP7X 67g5ToxDPl68d2HQ9+vbAInoUiD40Q1yBIcJsCEZsB4cx1VBPuVvlaTJSULdL5v6
Processed: Bug#963955 marked as pending in qtbase-opensource-src
Processing control commands: > tag -1 pending Bug #963955 [qtbase5-dev] qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS Added tag(s) pending. -- 963955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Processed: your mail
Processing commands for cont...@bugs.debian.org: > notfound 963955 5.14 Bug #963955 [qtbase5-dev] qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS There is no source info for the package 'qtbase5-dev' at version '5.14' with architecture '' Unable to make a source version for version '5.14' No longer marked as found in versions 5.14. > notfound 963955 5.14.2 Bug #963955 [qtbase5-dev] qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS There is no source info for the package 'qtbase5-dev' at version '5.14.2' with architecture '' Unable to make a source version for version '5.14.2' No longer marked as found in versions 5.14.2. > found 963955 qtbase-opensource-src/5.14.2+dfsg-4 Bug #963955 [qtbase5-dev] qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS Marked as found in versions qtbase-opensource-src/5.14.2+dfsg-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 963955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#963709 marked as pending in pyside2
Processing control commands: > tag -1 pending Bug #963709 [src:pyside2] pyside2: FTBFS on arm64: web_engine_initialize test fails with "Could not initialize GLX" Added tag(s) pending. -- 963709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Status of Plasma 5.18/5.19?
Hi Luc. Luc Castermans - 29.06.20, 13:52:39 CEST: > Are we past the point of no return or is there an option to go to > square one and restart? What would be needed to do so? I have no idea. Actually I do not really understand the conflict. However… > At the same time I note that email is a bad medium for this type of > interaction, sorry for using this medium I am not aware of another > one. I am willing to offer moderation to find a solution in case both parties would like to have a go at finding one. We could find a Jitsi or BigBlueButton instance to do this. I know several instances that could be used. Disclaimer: I worked with Debian/Kubuntu Qt/KDE team, on some bug triaging or regarding providing information here. And I have no intention to change that at the moment. So I may be biased and gladly let a less likely to be biased person offer to do the job. That written, I learned a lot about ways to communicate that can help to find resolutions to conflicts and allow everyone to feel accepted as a person. Best, -- Martin
Re: Status of Plasma 5.18/5.19?
Sander van Grieken - 29.06.20, 13:23:41 CEST: > On zondag 28 juni 2020 12:53:15 CEST Martin Steigerwald wrote: > > Dear Marco, dear Qt/KDE team, dear Norberg, dear community, > > > > Marco Valli - 28.06.20, 11:12:03 CEST: > > > Do you remember debian multimedia of Marillat, another "very > > > experienced DD"? No? well, even preining in a few years will no > > > longer remember by anyone. Debian yes. > > > > I am not sure whether it makes sense to discuss this out to the end… > > Well I'm afraid this topic will keep coming back occasionally until it > is resolved in one way or the other. It is not on me to moderate anything here and… as I wrote I am not sure what the best approach to proceed would be. > > I really would have preferred for Debian/Kubuntu Qt/KDE team to work > > together. But if that isn't the case that also is how it is. And it > > is important to accept that. That does not make anyone who is > > involved right or wrong either. It is just different approaches. > > None of them inherently better or worse than the other. > > Personally, I find this situation hard to accept. The maintainer team > is not just a collection of individuals, it's a body that is a > gatekeeper of the K/Qt stack into Debian. This gatekeeper role > doesn't just give its members significant power, it also assigns to > the team a responsibility to keep enabling contributions and > improvements to reach the user. I get that. For me first accepting a situation as it is can open up a path way to change it. > No process can be made totally free of friction. But it is a matter of > maturity how friction is handled Right. Best, -- Martin
Re: Status of Plasma 5.18/5.19?
Hi, Right Sander: Knowing nothing about the history of the frictions but knowing the needs and acknowledging each other's skills I regret to read the thread. Are we past the point of no return or is there an option to go to square one and restart? What would be needed to do so? At the same time I note that email is a bad medium for this type of interaction, sorry for using this medium I am not aware of another one. Regards Luc Op ma 29 jun. 2020 om 13:30 schreef Sander van Grieken < san...@outrightsolutions.nl>: > On zondag 28 juni 2020 12:53:15 CEST Martin Steigerwald wrote: > > Dear Marco, dear Qt/KDE team, dear Norberg, dear community, > > > > Marco Valli - 28.06.20, 11:12:03 CEST: > > > Do you remember debian multimedia of Marillat, another "very > > > experienced DD"? No? well, even preining in a few years will no > > > longer remember by anyone. Debian yes. > > > > I am not sure whether it makes sense to discuss this out to the end… > > Well I'm afraid this topic will keep coming back occasionally until it is > resolved in one way or the other. > > > I really would have preferred for Debian/Kubuntu Qt/KDE team to work > > together. But if that isn't the case that also is how it is. And it is > > important to accept that. That does not make anyone who is involved > > right or wrong either. It is just different approaches. None of them > > inherently better or worse than the other. > > Personally, I find this situation hard to accept. The maintainer team is > not just a collection of individuals, it's a body that is a gatekeeper of > the K/Qt stack into Debian. This gatekeeper role doesn't just give its > members significant power, it also assigns to the team a responsibility to > keep enabling contributions and improvements to reach the user. > > No process can be made totally free of friction. But it is a matter of > maturity how friction is handled. > > -- > Sander > > > > -- Luc Castermans mailto:luc.casterm...@gmail.com
Re: Status of Plasma 5.18/5.19?
On zondag 28 juni 2020 12:53:15 CEST Martin Steigerwald wrote: > Dear Marco, dear Qt/KDE team, dear Norberg, dear community, > > Marco Valli - 28.06.20, 11:12:03 CEST: > > Do you remember debian multimedia of Marillat, another "very > > experienced DD"? No? well, even preining in a few years will no > > longer remember by anyone. Debian yes. > > I am not sure whether it makes sense to discuss this out to the end… Well I'm afraid this topic will keep coming back occasionally until it is resolved in one way or the other. > I really would have preferred for Debian/Kubuntu Qt/KDE team to work > together. But if that isn't the case that also is how it is. And it is > important to accept that. That does not make anyone who is involved > right or wrong either. It is just different approaches. None of them > inherently better or worse than the other. Personally, I find this situation hard to accept. The maintainer team is not just a collection of individuals, it's a body that is a gatekeeper of the K/Qt stack into Debian. This gatekeeper role doesn't just give its members significant power, it also assigns to the team a responsibility to keep enabling contributions and improvements to reach the user. No process can be made totally free of friction. But it is a matter of maturity how friction is handled. -- Sander
Re: Status of Plasma 5.18/5.19?
In data lunedì 29 giugno 2020 13:12:28 CEST, Norbert Preining ha scritto: > Another great contribution that lines up perfectly with the rest! "I remain politely silent about your comments" https://imgflip.com/i/12zl00 -- Marco Valli
Re: Status of Plasma 5.18/5.19?
Another great contribution that lines up perfectly with the rest!
Re: Status of Plasma 5.18/5.19?
In data lunedì 29 giugno 2020 00:39:34 CEST, Norbert Preining ha scritto: > Looking at contributors.debian.org, I remain politely silent about your > comments. https://en.wikipedia.org/wiki/Facepalm -- Marco Valli
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 963955 5.14.2 Bug #963955 [qtbase5-dev] qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS There is no source info for the package 'qtbase5-dev' at version '5.14.2' with architecture '' Unable to make a source version for version '5.14.2' Marked as found in versions 5.14.2. > notfound 963955 5.12.5 Bug #963955 [qtbase5-dev] qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS There is no source info for the package 'qtbase5-dev' at version '5.12.5' with architecture '' Unable to make a source version for version '5.12.5' Ignoring request to alter found versions of bug #963955 to the same values previously set > stop Stopping processing here. Please contact me if you need assistance. -- 963955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963955: qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS
Package: qtbase5-dev Version: 5.14 Severity: normal Tags: upstream Dear Maintainer, As of Qt 5.14, a change to moc means that packages that build-depend on both Qt and TBB (libtbb-dev) fail to build. This is QTBUG-80990/QTBUG-80578 [1,2]. I have verified that this is a problem for src:gudhi, which fails to build with Qt 5.14.2. The upstream bug also indicates that packages that build-depend on both Qt and MongoDB may be affected. There is a patch upstream for the 5.15 branch, but it does not apply cleanly to the current Debian version (5.14.2), so I did not investigate further. [1] https://bugreports.qt.io/browse/QTBUG-80990 [2] https://bugreports.qt.io/browse/QTBUG-80578
Bug#949846: libpyside2-dev: Wrong include path for CMake in INTERFACE_INCLUDE_DIRECTORIES
Hi, libshiboken2-dev 5.15.0-1 is now in sid, and it seems this is broken again. The packages from experimental used to work fine, but they are gone now. It would be great if someone could have a look. Thanks in advance Tobias
