Bug#240027: kdm: keyboard not working on startup
Package: kdm Version: 4:3.3.1-3 Followup-For: Bug #240027 hi there, i have just upgraded two system from kdm 3.2.x to 3.3.1-3 and experienced a failure off my keyboard after reboot on two systems. on both system my intention was to keep the kdmrc file. when disabling kdm at boot and starting it manually, input devices are OK. when reinstalling kdm 3.3.1-3 and replacing kdmrc during kdm install, the functionality seems to be restored. cheers, mike gabriel -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9-kanotix-8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kdm depends on: ii debconf 1.4.30.11 Debian configuration management sy ii kdebase-bin 4:3.3.1-3 KDE Base (binaries) ii kdelibs4 4:3.3.1-4 KDE core libraries ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-6client library to control the FAM ii libgcc1 1:3.4.3-6 GCC support library ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library ii libidn11 0.5.2-3GNU libidn library, implementation ii libpam-runtime0.76-22Runtime support for the PAM librar ii libpam0g 0.76-22Pluggable Authentication Modules l ii libpng12-01.2.8rel-1 PNG library - runtime ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-8 X Window System Session Management ii libstdc++51:3.3.5-5 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-8 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii libxtst6 4.3.0.dfsg.1-8 X Window System event recording an ii xbase-clients 4.3.0.dfsg.1-8 miscellaneous X clients ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m ii zlib1g1:1.2.2-3 compression library - runtime -- debconf information: kdm/stop_running_server_with_children: false * kdm/default_servers_nolisten_tcp: * kdm/default_servers_100dpi: * shared/default-x-display-manager: kdm * kdm/default_nolisten_udp: kdm/daemon_name: /usr/bin/kdm
Bug#289055: kdm always shows username
Package: kdm Version: 4:3.3.0a-1 Severity: normal hi there, just upgraded all of kde to 3.3.1-3 and after that i cannot get rid of the username in the login window (do not know, whether it is taken from the user logged in last, or from the auto-auth field, etc.). on systems that offer xdmcp on the net i consider this as a security issue. even a downgrade of the kdm debian package does not restore the old functionality. might this be caused by some kde lib? mike gabriel my kdmrc is: [General] ConfigVersion=2.2 PidFile=/var/run/kdm.pid ServerVTs=-7 Xservers=/etc/kde3/kdm/Xservers [Shutdown] HaltCmd=/sbin/halt RebootCmd=/sbin/reboot UseLilo=false [X-*-Core] AllowNullPasswd=false AllowRootLogin=false AllowShutdown=Root AutoReLogin=false ClientLogFile=.xsession-errors-%s Reset=/etc/kde3/kdm/Xreset Session=/etc/kde3/kdm/Xsession Setup=/etc/kde3/kdm/Xsetup Startup=/etc/kde3/kdm/Xstartup [X-*-Greeter] AntiAliasing=false ColorScheme= DefaultUser=jim EchoMode=OneStar FaceSource=AdminOnly FailFont=Futura Md BT,12,-1,5,75,0,0,0,0,0 FocusPasswd=false ForgingSeed=1096162550 GUIStyle= GreetFont=Bremen Bd BT,24,-1,5,50,0,0,0,0,0 GreetString=Mobiles GURU-Buch GreeterPos=50,50 HiddenUsers= Language=en_US LogoArea=Clock LogoPixmap= MaxShowUID=2 MinShowUID=1000 PreselectUser=None SelectedUsers= ShowUsers=NotHidden SortUsers=true StdFont=Futura Lt BT,12,-1,5,50,0,0,0,0,0 UseBackground=true UserCompletion=false UserList=false [X-:*-Core] AllowNullPasswd=true AllowShutdown=All NoPassEnable=false NoPassUsers= [X-:*-Greeter] AllowClose=false FocusPasswd=true LoginMode=DefaultLocal PreselectUser=Previous [X-:0-Core] AutoLoginEnable=false AutoLoginUser=jim ClientLogFile=.xsession-errors [Xdmcp] Enable=false Willing=/etc/kde3/kdm/Xwilling -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9-kanotix-8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kdm depends on: ii debconf 1.4.30.11 Debian configuration management sy ii kdebase-bin 4:3.3.1-3 KDE Base (binaries) ii kdelibs4 4:3.3.1-4 KDE core libraries ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-6client library to control the FAM ii libgcc1 1:3.4.3-6 GCC support library ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library ii libidn11 0.5.2-3GNU libidn library, implementation ii libpam-runtime0.76-22Runtime support for the PAM librar ii libpam0g 0.76-22Pluggable Authentication Modules l ii libpng12-01.2.8rel-1 PNG library - runtime ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v ii libsm64.3.0.dfsg.1-8 X Window System Session Management ii libstdc++51:3.3.5-5 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-8 X Window System miscellaneous exte ii libxrender1 0.8.3-7X Rendering Extension client libra ii libxtst6 4.3.0.dfsg.1-8 X Window System event recording an ii xbase-clients 4.3.0.dfsg.1-8 miscellaneous X clients ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m ii zlib1g1:1.2.2-3 compression library - runtime -- debconf information: kdm/stop_running_server_with_children: false * kdm/default_servers_nolisten_tcp: * kdm/default_servers_100dpi: * shared/default-x-display-manager: kdm * kdm/default_nolisten_udp: kdm/daemon_name: /usr/bin/kdm
Bug#289055: kdm always shows username
hi simo, thanks for your quick reply. the point just is, that i did not touch the configs manually. they were created by the login manager plugin of kcontrol and could not be reversed... i'll change the config manually for now... mike -- mike gabriel, hamburger chaussee 240, 24113 kiel fon: +49 431 6474196, mail: [EMAIL PROTECTED] links: http://www.sunweavers.net
Bug#289055: kdm always shows username
hi adeato, uhm, perhaps you could check if you just used the default configuration, and that you really can achieve the desired behavior with the plugin. OK, i reinstalled the kdm package. dpkg asked me to overwrite my kdmrc and i accepted. then i tried to setup my own kdmrc via the kcontrol login manager plugin. everything worked fine except the radio button of Preselect User - None. after logging out, there still was my username in the username field of the kdm login window. this is my kdmrc after i have committed my personal changes to the config with kcontrol's login manager (i marked the preselectuser lines, the last one probably causes the bug i reported): [EMAIL PROTECTED]:/etc/kde3/kdm$ cat kdmrc [General] ConfigVersion=2.2 PidFile=/var/run/kdm.pid ServerVTs=-7 Xservers=/etc/kde3/kdm/Xservers [Shutdown] HaltCmd=/sbin/halt RebootCmd=/sbin/reboot UseLilo=false [X-*-Core] AllowNullPasswd=false AllowRootLogin=false AllowShutdown=Root AutoReLogin=false ClientLogFile=.xsession-errors-%s Reset=/etc/kde3/kdm/Xreset Session=/etc/kde3/kdm/Xsession Setup=/etc/kde3/kdm/Xsetup Startup=/etc/kde3/kdm/Xstartup [X-*-Greeter] AntiAliasing=false ColorScheme= DefaultUser=mike EchoMode=OneStar FaceSource=AdminOnly FailFont=helvetica,12,-1,5,75,0,0,0,0,0 FocusPasswd=false ForgingSeed=1102776522 GUIStyle= GreetFont=Charlesworth,24,-1,5,75,0,0,0,0,0 GreetString=Villa-Drachensee Server GreeterPos=50,50 HiddenUsers= Language=en_US LogoArea=Clock LogoPixmap= MaxShowUID=2 MinShowUID=1000 PreselectUser=None SelectedUsers= ShowUsers=NotHidden SortUsers=true StdFont=helvetica,12,-1,5,50,0,0,0,0,0 UseBackground=true UserCompletion=false UserList=false [X-:*-Core] AllowNullPasswd=true AllowShutdown=All NoPassEnable=false NoPassUsers= [X-:*-Greeter] AllowClose=false FocusPasswd=true LoginMode=DefaultLocal PreselectUser=Previous [X-:0-Core] AutoLoginEnable=false AutoLoginUser=mike ClientLogFile=.xsession-errors [Xdmcp] Enable=false Willing=/etc/kde3/kdm/Xwilling -- mike gabriel, hamburger chaussee 240, 24113 kiel fon: +49 431 64-74-126 mail: [EMAIL PROTECTED]
Bug#725090: Please add libkolab-dev to build dependencies and link against that library
Package: kdepim Severity: wishlist Dear KDE maintainer team, recently the library package libkolab entered Debian. It is a converion library and facilitates conversions between KDE containers and the Kolab storage format. Please build/link against that library and for that add libkolab-dev to the build depencies of kdepim. light+love, Mike -- mike gabriel aka sunweaver (Debian Developer) fon: +49 (1520) 1976 148 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net bin3x1e3oVgeu.bin Description: Öffentlicher PGP-Schlüssel pgpiw1BGP0URM.pgp Description: Digitale PGP-Signatur
Bug#725090: Please add libkolab-dev to build dependencies and link against that library
Hi all, sorry, my bad. It must be kde-runtime. Mike (from my N900) -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de - Original message - Hi, In data martedì 1 ottobre 2013 11:05:30, Mike Gabriel ha scritto: recently the library package libkolab entered Debian. It is a converion library and facilitates conversions between KDE containers and the Kolab storage format. Yes, we know that. I was the main reviewer and sponsor of Paul's packaging of libkolabxml and libkolab. Please build/link against that library and for that add libkolab-dev to the build depencies of kdepim. I don't see anything in kdepim requiring/using libkolab; on the other hand kdepim-runtime (i.e. the akonadi and kresource resources) had the kolab support enabled in 4:4.10.5-2 (#705406). If you know anything further that needs manual enabling/tweaking on the packaging side of the kdepim stack, feel free to let us know. -- Pino Toscano -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1380634296.3915.5.camel@Nokia-N900
Bug#739494: Test your package(s) with libssh 0.6.x
Package: kde-runtime Dear maintainers, the libssh maintainers are planning the upload of libssh 0.6.x to unstable soon (4-6 weeks from now). Please test your package's functionality with libssh 0.6.1 as found in Debian experimental (currently: 0.6.1-1~exp1). Thanks, Mike Gabriel -- mike gabriel aka sunweaver (Debian Developer) fon: +49 (1520) 1976 148 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpgRqKKeoVwm.pgp Description: Digitale PGP-Signatur
Bug#765624: Please don't recommend kde-workspace
Package: kdm Severity: normal Version: 4:4.11.12-2 Installing kdm pulls in a complete KDE/Plasma desktop. The Debian Edu team wants to combine kdm with other desktop shells, as well, but automatic system installation results in full kde installations only because of kdm recommending kde-workspace. Please downgrade kde-workspace to Suggests: field. Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1413481583.1414.5.camel@Nokia-N900
Bug#774699: kdevelop regularly crashes on diverse actions
Package: kdevelop
Version: 4:4.3.1-3+b1
Severity: grave
Dear maintainers of kdevelop,
I have just though, I might try some
debugging in kdevelop for the first time. Co-developers in X2Go
recommended the tool to me.
However, for nearly every action I tried, I experienced this or that
crash:
o import a Makefile
o open onmainwindow.cpp [1] of X2Go Client
o restart kdevelop after it crashed the first time
The last issue seems to be most painful:
o cause kdevelop to crash
o reopen kdevelop, then it crashes again
o remove rm /home/mike/.kde/share/apps/kdevelop/ -Rf
o kdevelop opens again...
To my first impression, kdevelop in Debian jessie/unstable is not at all
usable and not appropriate for the next Debian stable.
Thanks+Greets,
Mike
PS: Here is the backtrace after crashing when simply opening
onmainwindow.cpp (main file in X2Go Client code) [1]:
mike@minobo:~$ gdb kdevelop
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from kdevelop...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/kdevelop
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
WARNING: deleting stale lockfile
/home/mike/.kdevduchain/{1538df91-bcc6-46de-bd9c-1846a1792c56}/0/lock
kdevelop(16360)/kdevplatform (language) KDevelop::ItemRepositoryRegistry::open:
version-hint not found, seems to be an old version
kdevelop(16360)/kdevplatform (language) KDevelop::ItemRepositoryRegistry::open:
The data-repository at
/home/mike/.kdevduchain/{1538df91-bcc6-46de-bd9c-1846a1792c56}/0 has to be
cleared.
[New Thread 0x7fffd9add700 (LWP 16364)]
kdevelop(16360)/kdecore (KLibrary) findLibraryInternal: plugins should not have
a 'lib' prefix: libkonsolepart.so
[New Thread 0x7fffc9b3d700 (LWP 16365)]
[New Thread 0x7fffc287c700 (LWP 16371)]
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString)
[New Thread 0x7fffc1e6e700 (LWP 16375)]
[New Thread 0x7fffc166d700 (LWP 16377)]
[Thread 0x7fffc166d700 (LWP 16377) exited]
[Thread 0x7fffc1e6e700 (LWP 16375) exited]
[New Thread 0x7fffc1e6e700 (LWP 16382)]
[New Thread 0x7fffc166d700 (LWP 16383)]
[Thread 0x7fffc1e6e700 (LWP 16382) exited]
[Thread 0x7fffc166d700 (LWP 16383) exited]
[New Thread 0x7fffc1e6e700 (LWP 16384)]
[New Thread 0x7fffc166d700 (LWP 16385)]
[Thread 0x7fffc1e6e700 (LWP 16384) exited]
[Thread 0x7fffc166d700 (LWP 16385) exited]
[New Thread 0x7fffc1e6e700 (LWP 16386)]
[New Thread 0x7fffc166d700 (LWP 16387)]
[Thread 0x7fffc1e6e700 (LWP 16386) exited]
[Thread 0x7fffc166d700 (LWP 16387) exited]
[New Thread 0x7fffc166d700 (LWP 16388)]
[New Thread 0x7fffc1e6e700 (LWP 16389)]
[Thread 0x7fffc166d700 (LWP 16388) exited]
[Thread 0x7fffc1e6e700 (LWP 16389) exited]
[New Thread 0x7fffc1e6e700 (LWP 16393)]
[New Thread 0x7fffc166d700 (LWP 16395)]
[Thread 0x7fffc1e6e700 (LWP 16393) exited]
[Thread 0x7fffc166d700 (LWP 16395) exited]
[New Thread 0x7fffc166d700 (LWP 16403)]
[New Thread 0x7fffc1e6e700 (LWP 16404)]
[Thread 0x7fffc166d700 (LWP 16403) exited]
[New Thread 0x7fffc166d700 (LWP 16409)]
[New Thread 0x7fffc0aa0700 (LWP 16410)]
[New Thread 0x7fff73bfd700 (LWP 16411)]
[Thread 0x7fffc1e6e700 (LWP 16404) exited]
/bin/cat:
/home/mike/.kde/share/apps/kdevelop/sessions//{1538df91-bcc6-46de-bd9c-1846a1792c56}/default.sh:
Datei oder Verzeichnis nicht gefunden
[New Thread 0x7fffc1e6e700 (LWP 16501)]
[New Thread 0x7fff7187b700 (LWP 16502)]
[New Thread 0x7fff7107a700 (LWP 16507)]
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x4000107
[New Thread 0x7fff6b37f700 (LWP 16508)]
[New Thread 0x7fff6ab7e700 (LWP 16509)]
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fff6b37f700 (LWP 16508)]
0x75002107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht
gefunden.
(gdb) bt
#0 0x75002107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x750034e8 in __GI_abort () at abort.c:89
#2 0x753d6b3d in
Bug#774699: kdevelop regularly crashes if setup is bogus (not a bug)
Control: close -1 Control: retitle -1 kdevelop regularly crashes if setup is bogus (not a bug) Hi Pino, On Di 06 Jan 2015 13:57:42 CET, Pino Toscano wrote: tag 774699 + moreinfo thanks On 2015-01-06 13:40, Mike Gabriel wrote: Package: kdevelop Version: 4:4.3.1-3+b1 This is in wheezy ... -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 ... but wheezy is debian 7.x, not 8.x (which is jessie) ... Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) ... this is from jessie too ... Versions of packages kdevelop depends on: ii kde-runtime4:4.14.2-2 ii kdevelop-data 4:4.7.0-1 ii libc6 2.19-13 ii libgcc11:4.9.1-19 ii libkcmutils4 4:4.14.2-4 ii libkdecore54:4.14.2-4 ii libkdeui5 4:4.14.2-4 ii libkio54:4.14.2-4 ii libkparts4 4:4.14.2-4 ii libktexteditor44:4.14.2-4 ii libplasma3 4:4.14.2-4 ii libqt4-dbus4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-help4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtwebkit4 2.3.4.dfsg-3 ii libstdc++6 4.9.1-19 ii libthreadweaver4 4:4.14.2-4 ... these are in jessie too ... ii kdevplatform5-libs 1.3.1-2 ii libkasten1controllers1 4:4.8.4+dfsg-1 ii libkasten1core14:4.8.4+dfsg-1 ii libkasten1okteta1controllers1 4:4.8.4+dfsg-1 ii libkasten1okteta1core1 4:4.8.4+dfsg-1 ii libkasten1okteta1gui1 4:4.8.4+dfsg-1 ii libprocessui4a 4:4.8.4-6 ii libsublime51.3.1-2 ... but these are in wheezy, and most probably are there because of the old kdevelop version. Your system is a weird mixup of wheezy and jessie, with a not totally clear situation (at least from the information provided here) of what is being installed. Please fix it first, either by having it fully on wheezy or on jessie, otherwise it is hard to debug such weird setup. Thanks, oh dang... Sorry for not doing my homework properly. Running another round of dist-upgrade on my machine now. Closing this bug... sorry for the noise. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp18Vrw1IqsY.pgp Description: Digitale PGP-Signatur
Re: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs
Hi all, hi Yves-Alexis, On Mo 02 Mär 2015 21:30:49 CET, Yves-Alexis Perez wrote: On dim., 2015-03-01 at 21:58 +, Simon McVittie wrote: slim and lightdm do have native systemd .service files, but don't have those relationships, which I think is probably a bug in those DMs' service files; they should probably gain those lines too. However, because they participate in managing the display-manager.service symlink, they suppress gdm.service altogether, so they might avoid get this problem with the plymouth handover. So what's your advice here for lightdm? Maybe it's worth adding it, but it doesn't warrant a freeze exception? Regards, I am quite positive that some missing gettys because of two DMs being installed in parallel (or some similar normal thing that people might do) will definitely be worth a freeze exception. IMHO, if gettys don't come up properly, the system is rather broken and this is a no-go for jessie. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpdEArtguiQ1.pgp Description: Digitale PGP-Signatur
Bug#892271: KDE5 crash in drkonqi on session logout when KDE5 runs under X2Go / in nested nxagent
Package: plasma-workspace Version: 4:5.12.2-1 Hi, when using KDE5 in an X2Go Session, I get a segfault in drkonqi (see below). ``` Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3b119f6540 (LWP 22552))] Thread 2 (Thread 0x7f3af5ebc700 (LWP 22556)): #0 0x7f3b0d02e5d9 in __GI___poll (fds=0x7f3af001ae60, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3b08fe6119 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3b08fe622c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3b0d9640ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3b0d9092aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3b0d72835a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3b0ef8ae45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f3b0d72d22d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3b0b2cf5aa in start_thread (arg=0x7f3af5ebc700) at pthread_create.c:463 #9 0x7f3b0d038cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f3b119f6540 (LWP 22552)): [KCrash Handler] #6 0x5600a8bda530 in ?? () #7 0x7f3aee5f94cd in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeXcbPlugin0.so #8 0x7f3b0cf79831 in __run_exit_handlers (status=0, listp=0x7f3b0d2f6718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #9 0x7f3b0cf7992a in __GI_exit (status=) at exit.c:139 #10 0x7f3b0cf63a8e in __libc_start_main (main=0x5600a73491f0, argc=16, argv=0x7ffd0edc8668, init=, fini=out>, rtld_fini=, stack_end=0x7ffd0edc8658) at ../csu/libc-start.c:344 #11 0x5600a734a53a in _start () ``` How to reproduce? * use Debian unstable, latest set of packages * terminal 1: $ nxagent -ac :1 * terminal 2: $ export DISPLAY=:1 $ STARTUP=startkde dbus-run-session /etc/X11/Xsession $ $ I'd love to see Debian 9 become ready for the Remote Debian Desktop. Hopefully, someone on the KDE5 team can take a closer look. Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpgQDY72EuYg.pgp Description: Digitale PGP-Signatur
Bug#891920: KDE5 not usable in X2Go Sessions
Package: plasma-desktop Severity: normal Version: 4:5.12.2-1 Hi, I have justed tested recent KDE5 from Debian unstable in an X2Go session. I was happy to see KDE5 from Debian stretch work well together with latest X2Go (i.e. its underlying Xserver nxagent). Unfortunately, in Debian unstable, KDE5 fails to launch dramatically. I see many crashes of krunner. Once someone is interested in looking at this issue, I can provide more debug info and/or X2Go expertise (I am part of nxagent aka nx-libs upstream). The test case is simple (no X2Go needed for this, can be tested from an unstable chroot). Get nxagent 2:3.5.99.14-3 or above for this from Debian unstable. I assume that your real server is on DISPLAY :0. $ export DISPLAY=:0 $ nxagent -ac :1 This launches nxagent in nested Xserver mode. The nxagent window is resizable and has Xinerama support on by default. Then in another terminal, do: $ export DISPLAY=:1 $ STARTUP=startkde dbus-run-session /etc/X11/Xsession Try this with a KDE5 from stretch, and it should work flawlessly. Try this with a KDE5 from buster, and you get plenty of problems. The Bluez integration creates high load on the user DBus. Once bluez has been removed, I see less output on stderr, but still various crashes and no KDE5 desktop comming up. I'd love to see KDE5 support in X2Go for Debian buster. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpGtespU4s_F.pgp Description: Digitale PGP-Signatur
Re: qtsystems-opensource-src_5.0~git20181230.e3332ee3-1_amd64.changes ACCEPTED into unstable, unstable
Hi Pino, On Mo 20 Apr 2020 23:40:42 CEST, Pino Toscano wrote: Hi Mike, In data lunedì 20 aprile 2020 14:24:36 CEST, Mike Gabriel ha scritto: > Can qtsystem be built also without Mir with no loss of binary packages? > If so, I'd do that, and enable the support for Mir when it is available > in unstable. What do you think? Yeah, that should work. Will prepare an upload. Great, thanks for the -2 upload, which indeed started to build fine (at least somewhere)! I see that most of the issues at the moment are symbols issues; I will handle that in the following days, waiting for the builds on almost all the architectures. Ah, ok. I had planned to do this upload myself, but I am open to sharing the workload. In the meanwhile, I opened a -3 changelog in git, and started adding few bits; feel free to add your changes. One question: what is debian/copyright.in for? It looks like some unused leftover template. I uses this script [1] to generate my copyright.in template file. And I do this when packaging a project initially and also for every upstream release (or Git snapshot). When doing it for the first time, this copyright.in file is my starting point for drafting d/copyright. With the first upload, I leave d/copyright.in in the package (or rather: in the Git repo). When I do a new upstream release of the package, I re-run the script [1] and get a "git diff" for d/copyright.in showing me all auto-detectable changes between last upstream version and this upstream version. I then take this auto-detected diff and weave it manually into debian/copyright itself. Mike [1] https://github.com/sunweaver/MyHomeConfig/blob/master/bin/update-copyright.in -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpQ8AfgjzNjO.pgp Description: Digitale PGP-Signatur
Re: qtsystems-opensource-src_5.0~git20181230.e3332ee3-1_amd64.changes ACCEPTED into unstable, unstable
Hi Pino, On Mo 20 Apr 2020 23:40:42 CEST, Pino Toscano wrote: Hi Mike, In data lunedì 20 aprile 2020 14:24:36 CEST, Mike Gabriel ha scritto: > Can qtsystem be built also without Mir with no loss of binary packages? > If so, I'd do that, and enable the support for Mir when it is available > in unstable. What do you think? Yeah, that should work. Will prepare an upload. Great, thanks for the -2 upload, which indeed started to build fine (at least somewhere)! I see that most of the issues at the moment are symbols issues; I will handle that in the following days, waiting for the builds on almost all the architectures. In the meanwhile, I opened a -3 changelog in git, and started adding few bits; feel free to add your changes. One question: what is debian/copyright.in for? It looks like some unused leftover template. Thanks, Thanks for updating qtsystems. Did the unit tests succeed with --parallel (which happens when calling dh_auto_test directly). My reason for having run-tests.sh was to run unit tests in --no-parallel mode. The limitation of dbus-test-runner is that you can't pass cmdline option to the script to run, so I wrapped the -j1 (or rather --no-parallel for dh_auto_test). If the tests succeed on all archs, that change is fine. Thanks for working on qtsystems. Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpGQ15eF70t3.pgp Description: Digitale PGP-Signatur
Re: qtsystems-opensource-src_5.0~git20181230.e3332ee3-1_amd64.changes ACCEPTED into unstable, unstable
Hi Pino, On Di 21 Apr 2020 14:00:56 CEST, Pino Toscano wrote: Hi Mike, In data martedì 21 aprile 2020 11:26:15 CEST, Mike Gabriel ha scritto: Thanks for updating qtsystems. Did the unit tests succeed with --parallel (which happens when calling dh_auto_test directly). It worked fine on my machine, and apparently on every buildd... but amd64 (!). Hence I just uploaded disabling the parallel execution of the test suite. Also as additional change I doubled the timeout (even if so far was fine even for slow architectures). I have seen 1 or 2 freezes exact at the same position (out of 40-50 builds, I guess) and tended to ignore them. Interesting that they pop up with 2nd build series on Debian's buildds. We might have to disable one of those tests. Let's see. Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpGMLu6P3N9P.pgp Description: Digitale PGP-Signatur
Re: qtsystems-opensource-src_5.0~git20181230.e3332ee3-1_amd64.changes ACCEPTED into unstable, unstable
Dear ftpmaster team.
thanks for accepting qtsystems to unstable. However, you are aware
that it requires the Mir Display Server (mir) as a build requirement?
Mir is still in NEW afaict.
Mike
On Mo 20 Apr 2020 12:00:26 CEST, Debian FTP Masters wrote:
Accepted:
Format: 1.8
Date: Sun, 15 Mar 2020 08:02:31 +0100
Source: qtsystems-opensource-src
Binary: libqt5publishsubscribe5 libqt5publishsubscribe5-dbgsym
libqt5serviceframework5 libqt5serviceframework5-dbgsym
libqt5systeminfo5 libqt5systeminfo5-dbgsym
qml-module-qtpublishsubscribe qml-module-qtpublishsubscribe-dbgsym
qml-module-qtserviceframework qml-module-qtserviceframework-dbgsym
qml-module-qtsysteminfo qml-module-qtsysteminfo-dbgsym
qtsystems5-dev qtsystems5-examples qtsystems5-examples-dbgsym
qtsystems5-private-dev qtsystems5-tools qtsystems5-tools-dbgsym
Architecture: source amd64
Version: 5.0~git20181230.e3332ee3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Mike Gabriel
Description:
libqt5publishsubscribe5 - Qt Systems module - publish subscribe
libqt5serviceframework5 - Qt Systems module - service framework
libqt5systeminfo5 - Qt Systems module - system info
qml-module-qtpublishsubscribe - Qt 5 Publish Subscribe QML module
qml-module-qtserviceframework - Qt 5 Service Framework QML module
qml-module-qtsysteminfo - Qt 5 System Info QML module
qtsystems5-dev - Qt 5 Systems development files
qtsystems5-examples - Qt 5 Systems examples
qtsystems5-private-dev - Qt 5 Systems private development files
qtsystems5-tools - Qt 5 Systems tools
Closes: 953959
Changes:
qtsystems-opensource-src (5.0~git20181230.e3332ee3-1) unstable;
urgency=medium
.
[ Timo Jyrinki ]
* Initial release. (Closes: #953959).
* debian/patches/build_with_udisk.patch:
- Build with udisks support.
* debian/patches/skip_failing_tests.patch:
- Skip failing unit tests to allow the rest to be run during build.
.
[ Mike Gabriel ]
* debian/control:
+ Add B-D: libmirclient-dev.
* debian/patches:
+ Rename patches, following a certain patch naming scheme, see
debian/patches/README.
+ Add / update patch headers.
* debian/patches: Add 1003_typo-fixes.patch.
* debian/{control,compat}:
+ Switch to debhelper-compat notation. Bump DH compat level to
version 12.
* debian/{control,rules}:
+ Drop qtsystems5-dbg dbg:pkg.
* debian/*.install:
+ Update file lists to be installed.
* debian/rules:
+ Run tests inside a dbus-test-runner task.
+ Move --fail-missing into dh_missing override.
+ Add get-orig-source target facilitating Git snapshooting.
+ Drop 'mkdir .git'. The .git folder triggers running syncqt.pl (which
we implemented in get-orig-source target manually, instead).
+ Use rm with wildcards, not with DEB_ variables.
+ Include architecture.mk.
+ Drop minified jquery.js files from upstream files.
+ Honour DEB_BUILD_OPTIONS in dh_auto_test override.
+ Drop now default --parallel flag from DH call.
+ Don't call qmake directly.
+ Set all hardening build flags.
* debian/control:
+ Add B-D: dbus-test-runner.
+ Update Vcs-*: fields. Packaging now takes place on salsa.debian.org.
+ Bump Standards-Version: to 4.5.0. No changes needed.
+ Add myself to Uploaders: field.
+ Update Homepage: URL (now with https).
+ Add Rules-Requires-Root: field and set it to 'no'.
+ Add further B-Ds: qtbase5-dev, libbluetooth-dev,
libevdev-dev, libx11-dev
(to enable further build features).
+ Add Debian UBports Team to Uploaders: field.
* debian/copyright:
+ Update Source: field.
+ Use secure URL in Format: field.
+ Rewrite copyright file. Detailed style.
+ Add auto-generated copyright.in template file.
* debian/*.symbols:
+ Add .symbols files.
* debian/qtsystems5-examples.lintian-overrides:
+ Drop file. Not needed.
* debian/watch:
+ Add file, pointing to the location where we may some time find release
tarballs of qtsystems.
* debian/upstream/metadata:
+ Add file. Comply with DEP-12.
Checksums-Sha1:
bc46ca70df7de61efa530314fa700cf99fca9bb6 3207
qtsystems-opensource-src_5.0~git20181230.e3332ee3-1.dsc
6aef145e86c23dd7f12417101a3fc25684a26287 1003840
qtsystems-opensource-src_5.0~git20181230.e3332ee3.orig.tar.xz
389415da539629b7811f54e3003ff7e400e0ce8e 17076
qtsystems-opensource-src_5.0~git20181230.e3332ee3-1.debian.tar.xz
9d3d39ea0407dc07489ec4d15fd9931f482241a5 638516
libqt5publishsubscribe5-dbgsym_5.0~git20181230.e3332ee3-1_amd64.deb
7f0e7eabaf57af7110a7a1b87ed76b69585bff56 49060
libqt5publishsubscribe5_5.0~git20181230.e3332ee3-1_amd64.deb
f24a9eb30671ffec604375706cd6d282daa81d97 2866680
libqt5serviceframework5-dbgsym_5.0~git20181230.e3332ee3-1_amd64.deb
d903bb75ebbf56bac76c5293a1961e399bf1e02e 152368
libqt5serviceframework5_5.0~git20181230.e3332ee3-1_amd64.deb
Re: qtsystems-opensource-src_5.0~git20181230.e3332ee3-1_amd64.changes ACCEPTED into unstable, unstable
Hi Pino, On Mo 20 Apr 2020 12:45:15 CEST, Pino Toscano wrote: Hi Mike, In data lunedì 20 aprile 2020 12:10:11 CEST, Mike Gabriel ha scritto: thanks for accepting qtsystems to unstable. However, you are aware that it requires the Mir Display Server (mir) as a build requirement? Mir is still in NEW afaict. (please do not forget to push missing commits and tags to the packaging repository ;-) ) Will do. Can qtsystem be built also without Mir with no loss of binary packages? If so, I'd do that, and enable the support for Mir when it is available in unstable. What do you think? Yeah, that should work. Will prepare an upload. Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpfRyOhRb88Z.pgp Description: Digitale PGP-Signatur
Bug#954035: ITP: qtfeedback-opensource-src -- Qt Feedback module
Package: wnpp Severity: wishlist Owner: Mike Gabriel * Package name: qtfeedback-opensource-src Version : 5.0~git20180329.a14bd0bb-1 Upstream Author : Chris Adams * URL : https://code.qt.io/qt/qtsystems.git * License : LGPL-2.1 (with exception) or GPL-3 Programming Lang: C++ Description : Qt Feedback module Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. . This package contains Qt Feedback module. . This Qt module will be packaged under the umbrella of the Debian Qt/KDE Maintainers and will be maintained by the Debian UBports Team.
Bug#955124: ITP: qtpim-opensource-src -- Qt PIM module
Package: wnpp Severity: wishlist Owner: Mike Gabriel * Package name: qtpim-opensource-src Version : 5.0~git20190618.8fec622c Upstream Author : Chris Adams * URL : https://code.qt.io/qt/qtpim.git * License : LGPL-2.1 (with exception) or GPL-3 Programming Lang: C++ Description : Qt PIM module Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. . This package contains Qt PIM module, shipping Qt libraries for contacts and organizers. . This Qt module will be packaged under the umbrella of the Debian Qt/KDE Maintainers and will be maintained by the Debian UBports Team.
Bug#949177: [Pkg-ayatana-devel] libaccounts-glib appears to be unmaintained.
Hi Peter, thanks for bringing this up. Am Samstag, 19. September 2020 schrieb peter green: > The libaccounts-glib package does not seem to be getting maintained in > Debian, it has had a rc bug (deprecated declarations > and -Werror) for 8 months with no maintainer response and has recently picked > up a second one (unversioned python removal). > It has not had an upload for 3 years. > > Both of the rc bugs have been fixed in ubuntu. The ubuntu package has a > higher "upstream version" than the Debian one, > but this does not seem to actually represent a newer version from upstream. > The changes outside the Debian directory > between the "upstream version" in Debian and the one in Ubuntu seem to be > limited to a small number of changes in the > "tests" directory (changing a timeout and removing some gitignore files) and > I could not find corresponding changes > in the upstream vcs. It seems the Debian and Ubuntu packaging diverged back > in 2016. > > There does seem to be activity upstream with a release 5 months ago, but > neither Debian or Ubuntu seem to have packaged it. > > So I started looking at the reverse dependencies to see if this was a package > that was still being used and I found quite > a bit. Looking at the first two levels I get: > > direct: > > ayatana-indicator-datetime > kaccounts-integration > kaccounts-providers > kio-gdrive > ktp-accounts-kcm > libaccounts-qt > purpose > telepathy-accounts-signon > > second levels: > > ktp-common-internals (via > kaccounts-integration/libaccounts-qt/telepathy-accounts-signon) > ktp-auth-handler (via kaccounts-integration/libaccounts-qt) > meta-kde-telepathy (via ktp-accounts-kcm) > kaccounts-integration (via libaccounts-qt) > akonadi (via libaccounts-qt) > signon-ui (via libaccounts-qt) > choqok (via purpose) > falkon (via purpose) > gwenview (via purpose) > kamaso (via purpose) > kde-spectacle (via purpose) > kdenlive (via purpose) > kdeplasma-addons (via purpose) > kdevelop (via purpose) > kphotoalbum (via purpose) > libkf5pimcommon (via purpose) > okular (via purpose) > plasma-browser-integration (via purpose) > > So, it doesn't look like removal is an option. Can someone (perhaps the > maintainer of one of the reverse-dependencies > take a look at getting this package back into shape?). Bringing across the > fixes from the Ubuntu package looks like it > would be fairly easy but I have no idea how to test the results. I'll take a look. Thanks for digging into this. Mike -- Sent from my Fairphone powered by SailfishOS
Bug#964447: plasma-workspace: please split out xembed-sni-proxy into separate bin:pkg
Package: src:plasma-workspace Severity: whishlist X-Debbugs-Cc: debian-m...@lists.debian.org Hi all, I just stumbled over the xembed-sni-proxy executable from src:plasma-workspace. I plan to support it in ayatana-indicator-application [1] (and thus in the mate-indicator-applet of the MATE desktop environment). For a cross-desktop use case, it would be nice to have xembed-sni-proxy available as a standalone package (that does not pull in the complete KDE package stack). Would that be a feasible thing to do for plasma-workspace in Debian? Thanks+Greets, Mike [1] https://github.com/AyatanaIndicators/ayatana-indicator-application/issues/1 -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgprNWL9BGhC8.pgp Description: Digitale PGP-Signatur
Bug#988759: pkg-kde-tools: typo in error messages produced by pkgkde-symbolshelper
Package: pkg-kde-tools Version:0.15.32 Severity: minor The pkgkde-symbolshelper scripts on occasion produces an error message that contains a type: pkgkde-symbolshelper: error: unreadale file/directory: symbols.amd64 ^ sed -e 's/unreadale/unreadable/' -i
Bug#1004705: qtfeedback: contains flawed auto-generated cmake config file
Control: retitle -1 qtfeedback: contains flawed auto-generated cmake config file Control: reassing -1 src:qtfeedback-opensource-src Re-assigning to qtfeedback-opensource-src. The fix is to remove /usr/lib/*/cmake/Qt5Feedback/Qt5Feedback_.cmake. Mike -- mike gabriel aka sunweaver (Debian Developer) fon: +49 (1520) 1976 148 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net signature.asc Description: PGP signature
Re: Bug#1057755: Qt WebEngine Security Support In Stable
Hi everyone, On Do 14 Dez 2023 00:38:29 CET, Soren Stoutner wrote: Patrick, On Wednesday, December 13, 2023 3:00:23 PM MST Patrick Franz wrote: Don't forget that the open-source Qt LTS releases are delayed by a year. I wasn’t aware of that. Can you please elaborate on how that timeline works? One of the things I am hoping to accomplish with this bug report is to collect all the information that everyone has regarding this issue in one place to make it easy for others to find it in the future. My understanding is that LTS releases for Qt WebEngine are not delayed because the AGPL license doesn’t allow it. AFAIK, QtWebengine is not affected by the one-year-delay-release policy. In Ubuntu Touch (i.e. Morph Web Browser) we currently also use QtWebEngine (Qt5 version). For Ubuntu Touch we regularly bump to a latest QtWebEngine 5.15.x release. Problems is that it is based on a very old version of the Chromium webengine (receiving security support, but not progressing forwards). To switch to a latest chromium engine one needs to build ones browser software against the Qt6 variant of QtWebEngine (this is planned for Ubuntu Touch, but no ETA, yet). All in all, I dearly welcome Soren's initiative on turning QtWebEngine 5.x and 6.x into rolling release packages inside Debian as the Morph Web Browser (morph-browser by package name) heavily will benefit from this. Debian stable tends to release in the summer of odd years and Ubuntu LTS tends to release in the spring of even years. If KDE synchronizes their schedule to release at the beginning of even years to make it easier to be packaged into Ubuntu LTS releases, that makes we wonder how many other projects also synchronize their release schedules to make it easier for Ubuntu. In the past QtWebEngine has received totally different release management compared to Qt core components. So possibly, none of this applies to QtWebEngine. Perhaps there are really good reasons for not doing so, but would it be in Debian’s interest to change our release schedule to be in the summer of even years? If other projects besides KDE coordinate their LTS releases around even years, then it might make the lives of many package maintainers easier. Off topic here. Debian can't synchronize with all upstreams the ship software of nor can upstreams synchronize with Debian. In theory, this is possible, but we in Debian should find workflows that fit with all upstreams. And yes, sometimes its painful missing an upstream release by 2 months because of Debian's freeze policy shortly before a Debian release. [...] Responding to Qt core related thoughts only with this: Sticking with LTS upstreams is always a good choice for massive packaging projects (i.e. when many many packages are involved). This applies to Qt and KDE/Plasma I guess. Greets, Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpTdax_JMeoJ.pgp Description: Digitale PGP-Signatur
Re: state of kalzium package, and metapackage dependencies on it.
Hi Peter, On Sa 13 Apr 2024 19:23:07 CEST, Peter Green wrote: kalzium needs to be rebuilt for the time64 transition, but it has had a FTBFS bug with no maintainer response for 4 months. The only reverse dependencies seem to be a number of metapackages. In particular, the kdeedu package is a key package and has a hard dependency on kalzium. This means that it can't be autoremoved from testing, making it a blocker the time64 transition. Is there someone who can step up and fix kalzium? or should it be dropped from the metapackages so it can be removed from testing? Metapackages built from the meta-kde source (key, hard dependencies) * kdeedu Metapackages built from the debian-edu source (key, but only reccomends): * education-chemistry * education-highschool * education-primaryschool * education-secondaryschool Metapackages built from the debian-science source (not key, only reccomends): * science-chemistry Metapackages built from the debichem source (not key, only reccomends): * debichem-visualisation it seems the kalzium package has been upgraded last night and buildds look good. So, ignore this mail? Or is anything else needed? Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpxWF1iriCCE.pgp Description: Digitale PGP-Signatur
