Re: QT target version for trixie
Cc'd the mailing list I mentioned below. Alexandre Rossi - 03.07.24, 12:29:06 CEST: > (Please CC me, I'm not subscribed) > > Wanting to fix #1073004, I was wondering what was the target version of > QT for trixie? Should an application build against QT5 or QT6? > > I have not been able to find that information. A question like this is better directed to the debian-qt-kde mailing list, where developers discuss things. AFAIK Trixie will ship at least 6.6.2 of Qt, which is currently in Unstable. Of course it could also be a later version given that it is still some time till release. Qt 6 is already needed for Plasma 6. I don't know whether Qt 5 will be available in Trixie. It would be preferable to build with Qt 6 as at some time Qt 5 will be removed anyway. Best, -- Martin
Re: Runit with KDE Plasma: krunner current working directory /
Reinhard Karcher - 10.02.23, 15:20:49 CET: > I have a different system: Debian SID/Testing with usrmerge, systemd > and bash, and I see the expected behavior: cwd linked to /home/USER. > So I suspect, that it is not caused by KDE/QT. Just for the record: Sometimes the truth is not that digital. It appears to be that there is a relation with an upstream change that affects anything except Systemd. krunner starts applications with cwd "/" with init system other than systemd (openrc, runit, ...) https://bugs.kde.org/432975 Plasma appears to use different code paths for systemd and non systemd startup: https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ Will be looking with upstream and/or Debian's other init team whether a solution can be found or… apply a work-around. Best, Martin > Am Freitag, 10. Februar 2023, 14:39 schrieb Martin Steigerwald: > > Hi! > > > > This puzzled me for a long time and I have no idea where to report > > this: > > > > …proc# ls -ld $(pidof krunner)/cwd > > lrwxrwxrwx 1 USER USER 0 10. Feb 14:26 15116/cwd -> / > > …proc# ls -ld $(pidof plasmashell)/cwd > > lrwxrwxrwx 1 USER USER 0 10. Feb 14:27 9191/cwd -> /home/USER > > > > This is with /bin/sh pointing to Dash, the user shell is Z-Shell, > > but I have also seen this on systems where the user shell is Bash. > > No usrmerge. (I hope to avoid it as long as possible.) > > > > According to pstree krunner's parent process is runit which of > > course > > has current working directory pointing to /. > > > > Plasmashell instead is going like this > > > > ├─runsv(2066)─┬─sddm(2116)─┬ > > > > ─sddm-helper(8989)───startplasma-x11(8994)─┬─plasma_session(9056)─┬ > > > > I bet through SDDM its working directory is set to the actual home > > directory of the user. > > > > Is this a bug with runit? Is this an upstream bug? > > > > Any idea how to find the root cause for this and determine what > > needs to be fixed? > > > > I tried to work around this by doing "cd $HOME" in my zshrc. However > > this makes open new tabs in Konsole always start at $HOME even when > > I > > open them with a tab active which has a different cwd. Yeah, I got > > only do "cd $HOME" if current working directory is /, but I'd > > rather see this fixed. However, I do not even know where to report > > this issue. > > > > Any insight greatly appreciated. -- Martin
Runit with KDE Plasma: krunner current working directory /
Hi! This puzzled me for a long time and I have no idea where to report this: …proc# ls -ld $(pidof krunner)/cwd lrwxrwxrwx 1 USER USER 0 10. Feb 14:26 15116/cwd -> / …proc# ls -ld $(pidof plasmashell)/cwd lrwxrwxrwx 1 USER USER 0 10. Feb 14:27 9191/cwd -> /home/USER This is with /bin/sh pointing to Dash, the user shell is Z-Shell, but I have also seen this on systems where the user shell is Bash. No usrmerge. (I hope to avoid it as long as possible.) According to pstree krunner's parent process is runit which of course has current working directory pointing to /. Plasmashell instead is going like this ├─runsv(2066)─┬─sddm(2116)─┬ ─sddm-helper(8989)───startplasma-x11(8994)─┬─plasma_session(9056)─┬ I bet through SDDM its working directory is set to the actual home directory of the user. Is this a bug with runit? Is this an upstream bug? Any idea how to find the root cause for this and determine what needs to be fixed? I tried to work around this by doing "cd $HOME" in my zshrc. However this makes open new tabs in Konsole always start at $HOME even when I open them with a tab active which has a different cwd. Yeah, I got only do "cd $HOME" if current working directory is /, but I'd rather see this fixed. However, I do not even know where to report this issue. Any insight greatly appreciated. Best, -- Martin
Bug#974860: Forwarded to upstream
Silvério Santos - 24.12.20, 14:18:18 CET: > forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430787 Please retest once you upgraded to Plasma 5.20 and KF 5.77. They should appear in testing soon. Have a Merry Christmas if you celebrate it, have a quiet and peaceful time, -- Martin
Bug#973973: plasma-workspace: screen looking does not work: kscreenlocker: Greeter Process not available
Martin Steigerwald - 08.11.20, 14:24:11 CET: > On pressing Ctrl-Alt-L or using one of the 'qdbus' commands I see the > following messages in ~/.xsession-errors: > > kscreenlocker: Greeter Process not available […] After another apt dist-upgrade today and after rebooting screenlocking works as usual. Yet the relevant packages have been installed before, they were updated yesterday, maybe the issue happened due to the upgrade? I think I did not restart after this update as it appeared minor to me. If this is to be expected while upgrading while in the session, please close the bug. I will look how it works now. Start-Date: 2020-11-07 09:49:21 Commandline: apt dist-upgrade Requested-By: martin (1000) Install: […] libkscreenlocker5:amd64 (5.19.5-2, 5.19.5-3), […] kde- config-screenlocker:amd64 (5.19.5-2, 5.19.5-3), […] End-Date: 2020-11-07 09:57:55 Ciao, -- Martin
Bug#973973: plasma-workspace: screen looking does not work: kscreenlocker: Greeter Process not available
Package: plasma-workspace Version: 4:5.19.5-3 Severity: important Dear Maintainer, apparently it does not happen to everyone who updated to Plasma 5.19.5, but it definitely happened here: - The screen is not locked after standby or hibernating to disk although the option in Systemsettings is set - I cannot lock the screen manually by pressing Ctrl-Alt-L. - I cannot lock the screen with a DBUS command, I tried: - qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock - qdbus org.kde.ksmserver /ScreenSaver org.freedesktop.ScreenSaver.Lock On pressing Ctrl-Alt-L or using one of the 'qdbus' commands I see the following messages in ~/.xsession-errors: kscreenlocker: Greeter Process not available ktp-kded-module: "screen-saver-away" state change: TelepathyKDEDModulePlugin::Enabled ktp-kded-module: plugin queue activation: "unset" "" I think the issue is that the greeter process is not available. If Martin Graesslin's blog post is still up to date there should be a 'kscreenlocker_greet' process. I do not have this process. [1] https://blog.martin-graesslin.com/blog/2014/05/screenlocker-architecture-in-plasma-next/ Thanks, Martin -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.6-tp520 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages plasma-workspace depends on: ii dbus-x11 [dbus-session-bus] 1.12.20-1 ii drkonqi 5.19.5-3 ii frameworkintegration 5.74.0-2 ii gdb 9.2-1 ii iso-codes4.5.0-1 ii kactivitymanagerd5.19.5-3 ii kded55.74.0-2 ii kinit5.74.0-2 ii kio 5.74.0-2 ii kpackagetool55.74.0-2 ii kwin-common 4:5.19.5-3 ii libappstreamqt2 0.12.11-1 ii libc62.31-4 ii libcolorcorrect5 4:5.19.5-3 ii libgcc-s110.2.0-16 ii libgps26 3.20-12+b1 ii libice6 2:1.0.10-1 ii libkf5activities55.74.0-2 ii libkf5activitiesstats1 5.74.0-2 ii libkf5authcore5 5.74.0-2 ii libkf5baloo5 5.74.0-2 ii libkf5bookmarks5 5.74.0-2 ii libkf5calendarevents55.74.0-2 ii libkf5completion55.74.0-2 ii libkf5config-bin 5.74.0-2 ii libkf5configcore55.74.0-2 ii libkf5configgui5 5.74.0-2 ii libkf5configwidgets5 5.74.0-2 ii libkf5coreaddons55.74.0-2 ii libkf5crash5 5.74.0-2 ii libkf5dbusaddons55.74.0-2 ii libkf5declarative5 5.74.0-2 ii libkf5globalaccel-bin5.74.0-2 ii libkf5globalaccel5 5.74.0-2 ii libkf5guiaddons5 5.74.0-3 ii libkf5holidays5 1:5.74.0-2 ii libkf5i18n5 5.74.0-3 ii libkf5iconthemes55.74.0-2 ii libkf5idletime5 5.74.0-2 ii libkf5itemmodels55.74.0-2 ii libkf5jobwidgets55.74.0-2 ii libkf5kdelibs4support5 5.74.0-3 ii libkf5kiocore5 5.74.0-2 ii libkf5kiofilewidgets55.74.0-2 ii libkf5kiogui55.74.0-2 ii libkf5kiowidgets55.74.0-2 ii libkf5networkmanagerqt6 5.74.0-2 ii libkf5newstuff5 5.74.0-2 ii libkf5notifications5 5.74.0-2 ii libkf5notifyconfig5 5.74.0-2 ii libkf5package5 5.74.0-2 ii libkf5people55.74.0-2 ii libkf5peoplewidgets5 5.74.0-2 ii libkf5plasma55.74.0-2 ii libkf5plasmaquick5 5.74.0-2 ii libkf5prison55.74.0-2 ii libkf5quickaddons5 5.74.0-2 ii libkf5runner55.74.0-2 ii libkf5service-bin5.74.0-2 ii libkf5service5 5.74.0-2 ii libkf5solid5 5.74.0-2 ii libkf
Bug#969171: akonadi-server expects akonadi-backend-mysql allthough any sql backend should work
severity 969171 normal thanks Dear Eric. Akonadi will use whatever database is set in the configuration file, by default on first startup MySQL if the MySQL backend has been installed at first startup. So if you use it with an existing home directory that has MySQL specified as database backend it needs the MySQL database backend of Akonadi to operate with the existing configuration. See the file: '~/.config/akonadi/akonadiserverrc'. This can happen as easily as starting once with the MySQL backend installed, as Plasma starts Akonadi automatically in its default configuration. Then you have an empty MariaDB based Akonadi. If you then switch to PostgreSQL this error occurs. Please ask on debian-kde and/or upstream kdepim-users mailing list for support. The Debian bug tracker is not for user support questions. Also review previous threads on this topic there. Note that on switching the database Akonadi will start anew and some information only stored in the database will be lost. I think it is not a bug of the package. But it is definitely not severity grave as Akonadi is perfectly usable here in exact the same version (usable to the extent Akonadi works reliable, but that is an upstream issue). So downgrading severity to normal. I have seen repeatedly seen that you set too high bug severity. If the package does not work for me does not mean that its automatically grave severity. Especially when it is, as I assume, a configuration error. So please refrain from setting grave when it isn't. It just causes additional work for the already overloaded Debian Qt/KDE team. If you are unsure please ask first in debian-kde mailing list. That is part of what it is there for. Best, -- Martin
Bug#961913: kmail: the access and reading of the received messages is often very slow
forwarded 961913 https://bugs.kde.org/422336 thanks Forwarded to: Bug 422336 - kmail: the access and reading of the received messages is often very slow https://bugs.kde.org/422336 Also relates to: Bug 367892 - During folder synchronisation Akonadi blocks out other operations like deleting or viewing mails https://bugs.kde.org/367892 Thanks, -- Martin
Bug#961913: kmail: the access and reading of the received messages is often very slow
tags 961913 upstream thanks Dear Merlin. merlin - 31.05.20, 14:01:27 CEST: > Package: kmail > Version: 4:20.04.1-1 > Severity: important […] > the access and reading of the received messages is often very slow a > message appears > "Reception of the content of the folder please wait" Same problem for > the trashing of messages. > The CPU increase to 100% > an akonadictl fsck or akonadictl vacuum does not improved . > Its new Thank you very much. I recommend to create an upstream bug report at https://bugs.kde.org as well. It is an upstream bug which has nothing to do with the Debian packaging. Once you created it, please share a link to it to the Debian bug report. However… first, please make sure you have some more information at hand that can help to debug the issue. Currently the only thing developers can do about your bug report is to ask for further information. Well or do nothing about it. If it is your goal to see your issue fixed, then it is helpful to help the developer to help you by providing any information that may be helpful. At the very least I'd include the following in the upstream bug report: - Of course exact versions of the involved components. - Your setup. So you use POP3 with local maildir or anything else? Which resources do you have configured and so on. Anything special settings you use? - Start Akonadi from a shell window and report any log messages that may be related to the issue. Or state that you checked the log and there are none if that is the case. Of course redact as needed for privacy. - Steps to reproduce the problem as best to your current knowledge. - Detailed information on what happens on your system when you do those steps. 100% CPU usage is not very detailed. It would help already to know which processes are using the CPU. "pidstat", contained in package "sysstat", or atop can provide good insight on what is going on. You may even share an atop recording with 10 second interval if you feel comfortable with others knowing what processes ran on your system at that time. Otherwise I bet some lines of "pidstat" output will also do. Also when did the "Reception of the content of the folder, please wait" message appear? On clicking another folder while mail retrieval / filtering was still working in the background? Things like that. - Is it a regression and if so since when? You wrote "It's new", but not since which version. For Debian the developer can guess it was 19.08, cause that was the previous version in Debian, however the upstream developers may not know about that. Also you could have upgraded from Debian Stable to Unstable and then the previous version would have been a much older one. - Also I suggest to use the Akonadi component, if unsure just select Akonadi and do not specify a subsystem of it or set the subsystem to "general" or something like that. The upstream bug tracker is a bit more detailed on this. So if you really like to see your issue fixed, I suggest you invest some additional time. Also see: "The body of the report" in https://www.debian.org/Bugs/Reporting In the page there is the recommendation not to report upstream. I can say already that this is very, very likely an upstream bug, so you can help by creating an upstream report. In case IMAP is involved also see: How To Create Useful Bugreports for the Akonadi IMAP Resource https://community.kde.org/PIM/Akonadi/Debug_IMAP I thought there would be a generic bug reporting page for Akonadi, but I did not find one. Thanks, -- Martin
Bug#943344: plasma-workspace: plasmashell with Qt 5.12.5 crashes on any notification
Thread on debian-kde-Mailinglist: Re: Transition of Qt to 5.12.5 https://lists.debian.org/debian-kde/2019/10/msg00033.html Luca Pedrielli found this initially. I just reported the bug. Thanks, -- Martin
Bug#943344: plasma-workspace: plasmashell with Qt 5.12.5 crashes on any notification
Hi! Probably related: Bug 1758263 - qt 5-12.5 update pushed to testing causes continual crashes https://bugzilla.redhat.com/show_bug.cgi?id=1758263 FEDORA-2019-2a4f82aa58 bugfix update in Fedora 30 for analitza, appmenu-qt5, & 81 more https://bodhi.fedoraproject.org/updates/FEDORA-2019-2a4f82aa58 According to these an update of qt5-qtdeclarative-5.12.5-3 fixed the issue for them. I am currently not sure how to dig out which patch they have applied from above reports, and I need a break anyway. Thanks, -- Martin
Bug#943344: plasma-workspace: plasmashell with Qt 5.12.5 crashes on any notification
Martin Steigerwald - 23.10.19, 18:38:53 CEST:
> Package: plasma-workspace
> Version: 4:5.14.5.1-3+b1
> Severity: important
[…]
> After upgrading to Qt 5.12.5 packages Plasmashell crashes on any
> notification.
>
> I can reproduce this with:
>
> kdialog --passivepopup 'text' 5
>
> Output on Konsole:
>
> KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
> sock_file=/run/user/1000/kdeinit5__0
> KCrash: crashing... crashRecursionCounter = 2
> KCrash: Application Name = plasmashell path = /usr/bin pid = 6549
> KCrash: Arguments: /usr/bin/plasmashell
> KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
> from kdeinit sock_file=/run/user/1000/kdeinit5__0
> QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 56 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 28 and type 'Read', disabling...
> zsh: suspended (signal) plasmashell
>
> It apparently cannot start DrKonqi.
>
> I am trying to obtain debug data.
Here is the backtrace I got:
[Thread 0x7fffa37fe700 (LWP 8517) exited]
Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault.
QObject::setProperty (this=this@entry=0x0, name=name@entry=0x7fffb83f1030
"sourceName", value=...) at kernel/qobject.cpp:3914
3914kernel/qobject.cpp: Datei oder Verzeichnis nicht gefunden.
(gdb)
(gdb)
(gdb)
(gdb)
(gdb) bt full
#0 0x75b72bb7 in QObject::setProperty(char const*, QVariant const&)
(this=this@entry=0x0, name=name@entry=0x7fffb83f1030 "sourceName", value=...)
at kernel/qobject.cpp:3914
d =
meta =
id =
p = {mobj = 0x75c1d790 , handle = 136,
idx = 0, menum = {mobj = 0x11, handle = 3501643008}}
#1 0x7fffb83e7eda in NotificationsHelper::processShow()
(this=0x598ebc40) at
./applets/notifications/plugin/notificationshelper.cpp:133
notificationData = {d = 0x562e6130}
sourceName = {static null = {}, d = 0x59165130}
popup = 0x0
#2 0x7fffb83e8da0 in
NotificationsHelper::displayNotification(QMap const&)
(this=0x598ebc40, notificationData=...)
at ./applets/notifications/plugin/notificationshelper.cpp:223
sourceName =
{d = {data = {c = 48 '0', uc = 48 '0', s = 20784, sc = 48 '0', us =
20784, i = 1494634800, u = 1494634800, l = 93825055215920, ul = 93825055215920,
b = 48, d = 4.6355736501344133e-310, f = 2.64440707e+15, real =
4.6355736501344133e-310, ll = 93825055215920, ull = 93825055215920, o =
0x59165130, ptr = 0x59165130, shared = 0x59165130}, type = 10,
is_shared = 0, is_null = 0}}
i =
j = {c = , i = {i = 0x5e063c90}, n = {i = }}
#3 0x7fffb83ef8eb in NotificationsHelper::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**)
(_o=_o@entry=0x598ebc40, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=9, _a=_a@entry=0x7fff8990)
at
./obj-x86_64-linux-gnu/applets/notifications/plugin/notificationshelperplugin_autogen/EWIEGA46WW/moc_notificationshelper.cpp:163
_t = 0x598ebc40
#4 0x7fffb83f0293 in NotificationsHelper::qt_metacall(QMetaObject::Call,
int, void**)
(this=0x598ebc40, _c=QMetaObject::InvokeMetaMethod, _id=9,
_a=0x7fff8990)
at
./obj-x86_64-linux-gnu/applets/notifications/plugin/notificationshelperplugin_autogen/EWIEGA46WW/moc_notificationshelper.cpp:231
#5 0x773be9fd in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const
(this=this@entry=0x7fff8cd0,
type=type@entry=QMetaObject::InvokeMetaMethod, index=,
index@entry=14, argv=)
at
../../include/QtQml/5.12.5/QtQml/private/../../../../../src/qml/qml/ftw/qflagpointer_p.h:335
#6 0x772b1b5d in CallMethod(QQmlObjectOrGadget const&, int, int, int,
int*, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call)
(object=..., index=, returnType=returnType@entry=43,
argCount=, argTypes=,
engine=engine@entry=0x55752700, callArgs=,
callType=) at jsruntime/qv4qobjectwrapper.cpp:1295
args =
{a = 9, s = 2, ptr = 0x7fff89f0, {array =
"\000\000\000\000\000\000\000\000\230\230n\355\377\177\000\000\220\230n\355\377\177\000\000\000ն\320\v\276\f]\000\000\000\000\000\200\003\000\060a.VUU\000\000\b",
'\000' ,
"\030\212\377\377\377\177\000\000\377\377\377\377\377\177\000\000\220\344\216YUU\000\000;36\367\377\177\000\000\000\000\000\000\000\000\000\000`\213\377\377\377\177\000\000@K\266ZUU\000\000~M+\367\377\177\000\000\000'uUUU\000\000\240\215\377\377\377\177\000\000\210\227n\355\377\177\000\000\000ն\320\v\276\f]\001\000\000\000\000\
Bug#943344: plasma-workspace: plasmashell with Qt 5.12.5 crashes on any notification
Package: plasma-workspace Version: 4:5.14.5.1-3+b1 Severity: important Dear Maintainer, After upgrading to Qt 5.12.5 packages Plasmashell crashes on any notification. I can reproduce this with: kdialog --passivepopup 'text' 5 Output on Konsole: KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasmashell path = /usr/bin pid = 6549 KCrash: Arguments: /usr/bin/plasmashell KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 23 and type 'Read', disabling... QSocketNotifier: Invalid socket 56 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 28 and type 'Read', disabling... zsh: suspended (signal) plasmashell It apparently cannot start DrKonqi. I am trying to obtain debug data. Best, Martin -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.5-tp520 (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_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: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages plasma-workspace depends on: ii dbus-x11 [dbus-session-bus] 1.12.16-2 ii drkonqi 5.14.5-1 ii frameworkintegration 5.62.0-1 ii gdb 8.3.1-1 ii iso-codes4.4-1 ii kactivitymanagerd5.14.5-1 ii kded55.62.0-1 ii kinit5.62.0-1 ii kio 5.62.1-2 ii kpackagetool55.62.0-1 ii kwin-common 4:5.14.5-1+b1 ii libappstreamqt2 0.12.9-1 ii libc62.29-2 ii libcolorcorrect5 4:5.14.5.1-3+b1 ii libgcc1 1:9.2.1-12 ii libgps25 3.19-2 ii libice6 2:1.0.9-2 ii libkf5activities55.62.0-1 ii libkf5authcore5 5.62.0-1 ii libkf5baloo5 5.62.0-2 ii libkf5bookmarks5 5.62.0-1 ii libkf5calendarevents55.62.0-1 ii libkf5completion55.62.0-1 ii libkf5config-bin 5.62.0-1 ii libkf5configcore55.62.0-1 ii libkf5configgui5 5.62.0-1 ii libkf5configwidgets5 5.62.0-1 ii libkf5coreaddons55.62.0-1 ii libkf5crash5 5.62.0-1 ii libkf5dbusaddons55.62.0-1 ii libkf5declarative5 5.62.0-1 ii libkf5globalaccel-bin5.62.0-1 ii libkf5globalaccel5 5.62.0-1 ii libkf5guiaddons5 5.62.0-1 ii libkf5holidays5 1:5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libkf5iconthemes55.62.0-1 ii libkf5idletime5 5.62.0-1 ii libkf5itemviews5 5.62.0-1 ii libkf5jobwidgets55.62.0-1 ii libkf5js55.62.0-1 ii libkf5jsembed5 5.62.0-1 ii libkf5kdelibs4support5 5.62.0-1 ii libkf5kiocore5 5.62.1-2 ii libkf5kiofilewidgets55.62.1-2 ii libkf5kiogui55.62.1-2 ii libkf5kiowidgets55.62.1-2 ii libkf5networkmanagerqt6 5.62.0-1 ii libkf5newstuff5 5.62.0-1 ii libkf5notifications5 5.62.0-1 ii libkf5notifyconfig5 5.62.0-1 ii libkf5package5 5.62.0-1 ii libkf5plasma55.62.0-1 ii libkf5plasmaquick5 5.62.0-1 ii libkf5prison55.62.0-1 ii libkf5quickaddons5 5.62.0-1 ii libkf5runner55.62.0-1 ii libkf5service-bin5.62.0-1 ii libkf5service5 5.62.0-1 ii libkf5solid5 5.62.0-2 ii libkf5texteditor55.62.0-1 ii libkf5textwidgets5 5.62.0-1 ii libkf5wallet-bin
Bug#941120: akonadi-backend-postgresql: fails to stop postgresql 11
Dear Sandro, Sandro Knauß - 10.10.19, 20:31:33 CEST: > Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=386173#c20 […] > as I don't use postgresql as backend, can you explain, why this bug it > that annoying, so I should fix that also for stable? Hmmm, thinking about it, the case for stable may not be all that strong. As I do not use stable, I won't need it there. I am not sure how many Debian users use stable Akonadi with PostgreSQL and PostgreSQL even appears to pick up the running processes after a subsequent "akonadictl start". Considering all this, the only annoyance and confusion is that some PostgreSQL processes keep lingering around. Some users may be confused about this. Okay, all in all, not all that convincing arguments for stable. I just thought if you do all the other fixes, you could put this one in as well. I considered it to be low risk. As the fix is in Akonadi 19.04, you may consider to close the bug right away or close it when uploading Akonadi 19.08 or newer packages. Best, -- Martin
Bug#941118: akonadi-server: fails to start after upgrade to 4:18.08.3-8: apparmor denied access to pg_ctl
Hi intrigeri, Sandro et al,
intrigeri - 05.10.19, 06:04:55 CEST:
> Hi Sandro et al,
>
> Sandro Knauß:
> > I now pushed a first version of Akonadi with the new AppArmor
> > profile, but as you see down here it fails and I'm not sure, what
> > went wrong. What we need to do to debug this?
>
> [...]
>
> >> > I believe the failure may be due to this:
> >> >
> >> > Sep 25 09:21:06 merkaba kernel: [ 266.556167][ T37] audit:
> >> > type=1400 audit(1569396066.434:45): apparmor="DENIED"
> >> > operation="exec" profile="postgresql_akonadi" name="/bin/dash"
> >> > pid=3833 comm="pg_ctl" requested_mask="x" denied_mask="x"
> >> > fsuid=1000
> >> > ouid=0
>
> https://salsa.debian.org/qt-kde-team/kde/akonadi/blob/master/debian/ap
> parmor/postgresql_akonadi#L12 reads:
>
> /usr/bin/dash mrix,
>
> I believe this only does what you mean on a merged-/usr system.
> I suspect Martin is reporting from a system without merged-/usr.
> Replacing this line with that one should fix this particular problem:
>
> /{usr/,}bin/dash mrix,
>
> Hoping it helps :)
Haha! Indeed. No merged-/usr here and after a time with Systemd now
running on sysvinit + elogind.
I made this change and did "aa-enforce postgresql_akonadi".
Akonadi starts fine with that.
Thank you,
--
Martin
Bug#941118: akonadi-server: fails to start after upgrade to 4:18.08.3-8: apparmor denied access to pg_ctl
Martin Steigerwald - 25.09.19, 09:32:15 CEST: > Package: akonadi-server > Version: 4:18.08.3-8 > Severity: important […] > I upgraded and then rebooted the system. > > After upgrading to Akonadi 4:18.08.3-8, Akonadi does not start > anymore: > > % akonadictl start > Connecting to deprecated signal > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString > ) org.kde.pim.akonadicontrol: Application 'akonadiserver' exited > normally... > > I believe the failure may be due to this: > > Sep 25 09:21:06 merkaba kernel: [ 266.556167][ T37] audit: > type=1400 audit(1569396066.434:45): apparmor="DENIED" > operation="exec" profile="postgresql_akonadi" name="/bin/dash" > pid=3833 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 > ouid=0 […] > Also setting to complain mode does not help: > > % aa-complain postgresql_akonadi > Setting /etc/apparmor.d/postgresql_akonadi to complain mode. > > Although access does get allowed then: > > Sep 25 09:30:14 merkaba kernel: [ 814.345508][ T37] audit: > type=1400 audit(1569396614.227:51): apparmor="ALLOWED" > operation="exec" profile="postgresql_akonadi" name="/bin/dash" > pid=5328 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 > ouid=0 target="postgresql_akonadi//null-/bin/dash" Oh, it does help. Akonadi starts again, just did not notice it initially. The pattern in % grep pg_ctl /etc/apparmor.d/postgresql_akonadi /usr/lib/postgresql/*/bin/pg_ctl mrix, seems to be okay tough: % ls -l /usr/lib/postgresql/*/bin/pg_ctl -rwxr-xr-x 1 root root 59888 Sep 24 22:09 /usr/lib/postgresql/11/bin/ pg_ctl However I am no AppArmor expert… Best, -- Martin
Bug#941120: akonadi-backend-postgresql: fails to stop postgresql 11
Package: akonadi-backend-postgresql Version: 4:18.08.3-8 Severity: normal Dear Sandro, you may like to consider Git commit 565700f7fc1d73e337600109867fc01cc647cf13 by Daniel Vrátil. Committed on 20/06/2019 at 09:51. Pushed by dvratil into branch 'Applications/19.04'. Check Postgres status by checking return code of pg_ctl Summary: The current code which was checking the standard output of "pg_ctl status", doesn't work with non-English locale, causing Akonadi to leave Postgres running after shutdown, because it thinks the db is no longer running. FIXED-IN: 5.11.3 https://bugs.kde.org/show_bug.cgi?id=386173#c20 for Akonadi for buster. Thanks, Martin -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.16-tp520 (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_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: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages akonadi-backend-postgresql depends on: ii libqt5sql5-psql 5.11.3+dfsg1-4 Versions of packages akonadi-backend-postgresql recommends: ii akonadi-server 4:18.08.3-8 ii postgresql 11+207 akonadi-backend-postgresql suggests no packages. -- no debconf information
Bug#941118: akonadi-server: fails to start after upgrade to 4:18.08.3-8: apparmor denied access to pg_ctl
Package: akonadi-server Version: 4:18.08.3-8 Severity: important Dear Sandro, I was tempted to raise severity to grave, but then thought that this may just happen on my system. Severity can still be raised if it happens on other systems as well. It may refuse to start on all setups using PostgreSQL backend, see below. I upgraded and then rebooted the system. After upgrading to Akonadi 4:18.08.3-8, Akonadi does not start anymore: % akonadictl start Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally... I believe the failure may be due to this: Sep 25 09:21:06 merkaba kernel: [ 266.556167][ T37] audit: type=1400 audit(1569396066.434:45): apparmor="DENIED" operation="exec" profile="postgresql_akonadi" name="/bin/dash" pid=3833 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 However when I use: % aa-disable postgresql_akonadi Disabling /etc/apparmor.d/postgresql_akonadi. I can still not start Akonadi – same console output as before, syslog output: Sep 25 09:27:17 merkaba kernel: [ 637.670793][ T37] audit: type=1400 audit(1569396437.550:46): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="postgresql_akonadi" pid=5247 comm="apparmor_parser" Sep 25 09:27:26 merkaba kernel: [ 647.098937][ T37] audit: type=1400 audit(1569396446.978:47): apparmor="DENIED" operation="exec" info="profile transition not found" error=-13 profile="/usr/bin/akonadiserver" name="/usr/lib/postgresql/11/bin/pg_ctl" pid=5261 comm="akonadiserver" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Also setting to complain mode does not help: % aa-complain postgresql_akonadi Setting /etc/apparmor.d/postgresql_akonadi to complain mode. Although access does get allowed then: Sep 25 09:30:14 merkaba kernel: [ 814.345508][ T37] audit: type=1400 audit(1569396614.227:51): apparmor="ALLOWED" operation="exec" profile="postgresql_akonadi" name="/bin/dash" pid=5328 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 target="postgresql_akonadi//null-/bin/dash" Best, Martin -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.16-tp520 (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_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: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages akonadi-server depends on: ii akonadi-backend-postgresql 4:18.08.3-8 ii libc62.29-2 ii libgcc1 1:9.2.1-8 ii libkf5akonadiprivate5abi2 [libkf5akonadiprivate5-18.08] 4:18.08.3-8 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-18.08] 4:18.08.3-8 ii libkf5configcore55.62.0-1 ii libkf5coreaddons55.62.0-1 ii libkf5crash5 5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5dbus5 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5network5 5.11.3+dfsg1-4 ii libqt5sql5 5.11.3+dfsg1-4 ii libqt5widgets5 5.11.3+dfsg1-4 ii libqt5xml5 5.11.3+dfsg1-4 ii libstdc++6 9.2.1-8 akonadi-server recommends no packages. Versions of packages akonadi-server suggests: pn akonadi-backend-mysql ii akonadi-backend-postgresql 4:18.08.3-8 pn akonadi-backend-sqlite -- no debconf information
Bug#940966: [qml-module-org-kde-kirigami2] qml-module-org-kde-kirigami2 uses an invalid version of QtQuick.Controls
Hi! Ximo Baldó i Soriano - 24.09.19, 19:49:56 CEST: > Package: qml-module-org-kde-kirigami2 > Version: 5.62.0-1 > > --- Please enter the report below this line. --- > > It affects other parts of 'look and feel' from systemsettings, no > only wallpaper selection. For now, as far I know, no one is working > but color schemes. Please check whether this is fixed in 5.62.0-2 version of the package. Thanks, -- Martin
Bug#940939: Upstream
Hi Matthieu. Matthieu Gallien - 22.09.19, 18:52:07 CEST: > I have open https://phabricator.kde.org/D22974 to propose a solution. Thanks. Okay. As far as I understand this is about Qt 5.11 compatibility. Qt 5.12.5 will likely land in Debian soon as far as I am aware. Best, -- Martin
Bug#935031: konsoles started with KDE are black first
Hi Marc. Marc Haber - 18.08.19, 13:26:51 CEST: > Package: konsole > Version: 4:19.08.0-1 > Severity: normal > > Hi, > > this is a regression that came with the update to 19.08.0 > > I have a number of konsoles that open automatically with KDE. I think > this is a (wanted) feature of the saved session. > > Since today's update, those konsoles are black. Window titla and Menu > bar are there but no contents. When I open a new tab using > Ctrl-Shift-T, the konsole becomes usable. Thank you for your report. Its also discussed in debian-kde mailinst list. One observations from there: It does seem to happen with Konsole windows opened with the session, but it does not seem to happen with a newly opened Konsole window. One idea I have about this that due to the rework of the tabbing mechanism which is available to split both horizontally and vertically at the same time now it may be that Konsole 19.08 would need a newer version of KDE Frameworks than what is packaged in Debian now. So the issue may go away once KDE Frameworks is updated in Debian. For now that is only guesswork, but application feature development often happens with within the application and the frameworks it it using and I am not sure whether every time the version dependency is updated by upstream developers. [1] Konsole empty https://lists.debian.org/debian-kde/2019/08/msg00022.html Thanks. -- Martin
Bug#931483: konsole: Konsole will not launch from mate-panel or from KDE Application Launcher.
Hi David. Well as Maxy could not reproduce it and it is no issue for you anymore, I'd rather wait whether there someone else has the same issue. It could be reopened then or a new bug reported. I see no real benefit in keeping a bug open cause it *may* be relevant to someone else. Let's see whether it is actually an issue for some else. If that is okay with you, there is no need to reply. BTW Debian has already been released as Debian 10 aka Buster. But let's not discuss other issues with sound cards or whatever else in this bug report, there is always debian-kde mailing list you can ask about help with issues you have¹. Please for bug reports always keep focused on the original issue. [1] https://lists.debian.org/debian-kde/ Best, Martin D.J.J. Ring, Jr. - 16.08.19, 22:18:08 CEST: > Martin, > > It is only working because I installed Arch Linux and I'm not running > Debian because of the problems with getting sound card detected with > the Debian installer. I'll wait until the release. > > So maybe this bug should stay, but I cannot help because I am not > using Debian now because I cannot run espeak-ng in console and that's > important to me. […] -- Martin
Re: system settings not opening after upgrade
Dear Kevin KEVIN STORMBREAKER - 04.08.19, 13:24:08 CEST: > Yesterday i upgraded kali linux.Now the system settings is not > opening.I tried uninstalling reinstalling but the same thing > happens.Gnome is also not working /It says segmentation fault.Do > something fast Please note that Kali Linux *is* not Debian Linux. It may be based on it, but it may use different repositories and package versions. Here with Debian GNU/Sid as of today Systemsettings just starts fine. So please use a Kali Linux support channel. For asking user support questions regarding Debian please use the debian-kde mailing list instead. Additional in case you use Kali Linux for security / privacy purposes I suggest not using a gmail address. Thank you, -- Martin
Re: Bug#911844: okular: Prints to the wrong printer
Michael Weghorn - 15.06.19, 23:52: > On 11/06/2019 23.37, Martin Steigerwald wrote: > > Hmmm, so it works okay with okular 19.04.1. > > > > That means somewhere between 17.12 and 19.04.1 is a bug fix for the > > issue you reported. Maybe upstream has an idea which one it might > > be. At this point I believe all that could be done would be to find > > and then backport that fix, as Debian is in deep freeze and > > packaging 19.04 thus out of scope. > > I've investigated a bit and it's not an Okular issue, but one in the > Qt print dialog with printers that don't have PPD files. It can be > reproduced e.g. with kate just the same and Brian even mentioned in > the initial report that qpdfview is affected as well. > > The issue has been fixed upstream (qtbase) with the following commit > (so that's what would have to be backported): > > > commit 84cc8d0badb4abc3c9a96d59c61dddce916a216c > Author: Albert Astals Cid > Date: Mon Feb 5 09:20:20 2018 +0100 > > cups: Support raw printers > > They don't have a ppd but we don't *really* need a ppd to just > print > > Change-Id: Idf6b6dafc19420a511b057194488e2170cae4d70 > > > This probably also fixes #911702, but I didn't test that explicitly. Michael, thank you are lot for your research which made that bug report actionable. Of course there may be another bug in there: When one printer cannot be used for some reason, it should not automatically switch to another one. But nonetheless the commit you pointed out looks like it can really help here. Best, -- Martin
Bug#930168: Unreproducible on clean installation
Martin Steigerwald - 12.06.19, 22:01: > Also please note that Kali Linux is not Debian GNU/Linux. So please > retest any issue you have with Kali Linux with a pure Debian GNU/Linux > install before reporting it here. > > So please retest with a pure Debian GNU/Linux installation. If you > cannot reproduce the issue there, I'd close it. If its reproducible on a Debian GNU/Linux installation even when it does not happen all of the time, the bug will stay open of course. In that case I kindly ask you to research upstream bug tracker for similar issues. There has been a lot of bug fixes regarding discover since version 5.14.5. So it would help if you could find the bug there if its reported and if there is a fix for it, tell us about it. That way you can help the understaffed Debian Qt/KDE team fix the bug by adding a patch for the 5.14.5 version currently packaged in Debian. -- Martin
Re: Bug#930168: Unreproducible on clean installation
severity 930168 important tags 930168 moreinfo thanks Alexander Kernozhitsky - 12.06.19, 19:05: > I just tried to install fresh Debian Buster on a VM and tried to > reproduce the bug. It appears that Discover works fine on a clean > install. > > As I mentioned before, I am able to reproduce this with AppStream > metadata manually disabled in APT configs. So this may be the reason. > > Please lower the severity. Thanks, Alexander. Doesn’t happen here either on a highly customized Debian Sid installation. Lowering severity. P D, thank you for your report. "renders package unusable" is not the right severity if the package is just unusable for you. It is the right severity if it makes the package unusable on most of all Debian installations. This is certainly not the case here. So please do not use a release critical bug severity if it is not appropriate¹. Also please note that Kali Linux is not Debian GNU/Linux. So please retest any issue you have with Kali Linux with a pure Debian GNU/Linux install before reporting it here. So please retest with a pure Debian GNU/Linux installation. If you cannot reproduce the issue there, I'd close it. [1] https://release.debian.org/testing/rc_policy.txt Thanks, -- Martin
Re: Bug#911844: okular: Prints to the wrong printer
Martin Steigerwald - 11.06.19, 23:37: > > I used the neon-user-20190606-1138.iso (okular 19.04.1). Everything > > behaved normally. No observed bug there. Okular 18.04 from > > experimental wouldn't install because of unmet depenencies. Another > > time, perhaps. > > Hmmm, so it works okay with okular 19.04.1. > > That means somewhere between 17.12 and 19.04.1 is a bug fix for the > issue you reported. Maybe upstream has an idea which one it might be. > At this point I believe all that could be done would be to find and > then backport that fix, as Debian is in deep freeze and packaging > 19.04 thus out of scope. Well it would be helpful to test with versions in between. So in case you are still having fun with that, Brian, that would be something you could do :). One way might be to test with Ubuntu live systems of different versions. Another way would be to build the thing yourself and do a git bisect. But well maybe upstream has an idea. -- Martin
Re: Bug#911844: okular: Prints to the wrong printer
Hi Brian. Brian Potkin - 11.06.19, 21:13: > On Tue 11 Jun 2019 at 13:20:40 +0200, Martin Steigerwald wrote: > > Brian Potkin - 11.06.19, 10:42: > > > On Tue 11 Jun 2019 at 09:53:50 +0200, Martin Steigerwald wrote: > > […] > > > > > > Two ways to use your (and our) time in a more productive manner > > > > are: > > > > > > > > 1) Retest with Okular 18.04 from Debian experimental (in case > > > > you > > > > run > > > > buster/sid). Or start KDE Neon in a machine and try with the > > > > newest > > > > Okular available there. > > > > > > There might be time for me to do both of these today or tomorrow. > > > > Wonderful. > > And good fun. Thank you for your contribution. > I used the neon-user-20190606-1138.iso (okular 19.04.1). Everything > behaved normally. No observed bug there. Okular 18.04 from > experimental wouldn't install because of unmet depenencies. Another > time, perhaps. Hmmm, so it works okay with okular 19.04.1. That means somewhere between 17.12 and 19.04.1 is a bug fix for the issue you reported. Maybe upstream has an idea which one it might be. At this point I believe all that could be done would be to find and then backport that fix, as Debian is in deep freeze and packaging 19.04 thus out of scope. Thanks, -- Martin
Bug#911844: okular: Prints to the wrong printer
Brian Potkin - 11.06.19, 10:42: > On Tue 11 Jun 2019 at 09:53:50 +0200, Martin Steigerwald wrote: […] > > Two ways to use your (and our) time in a more productive manner are: > > > > 1) Retest with Okular 18.04 from Debian experimental (in case you > > run > > buster/sid). Or start KDE Neon in a machine and try with the newest > > Okular available there. > > There might be time for me to do both of these today or tomorrow. Wonderful. > > 2) Remind upstream in a friendly way to have a look at the issue. > > Once there is a patch upstream it is very likely it could be > > backported for buster. Maybe it would be an idea to raise the > > upstream bug to KDE's security team. > > You seem to have done that. Thanks. Yes, appeared to be the quickest way to more this forward for me. There is a reply by Albert already. He is member of KDE security team and AFAIK also develops on Okular. Please review his comments there and answer accordingly. It appears he does not yet understand on how to reproduce. Maybe, if you can, give a concrete example with the necessary CUPS commands or probably an example configuration file. Thank you very much. Best,
Bug#911844: okular: Prints to the wrong printer
forwarded 911844 https://bugs.kde.org/402015 thanks -- Martin
Re: Bug#911844: okular: Prints to the wrong printer
severity: important thanks Hi Brian, Brian Potkin - 10.06.19, 21:32: > Severity: critical > thanks > > On Thu 25 Oct 2018 at 12:50:25 +0100, Brian Potkin wrote: > > Package: okular > > Version: 4:17.12.2-2 > > Severity: critical > > Tags: upstream security > > > > > > > > "critical" because a document should always go to where it is sent. > > Please reduce the severity if I have overestimated the security > > implications. > > > > The CUPS version being used is 2.2.8-5 and cups-browsed is not > > running. The issue was encountered while taking another look at > > #911702.> […] > > The job is always sent to a local queue when its destination > > precedes > > realq_desktop alphabetically. […] > I have retested this. There is no change on the present unstable. I > cannot see why a confidential print job going to a staff printer is > anything but a security issue. Maybe this is something that merits > the tag of normal but explanations are in short supply. Brian, before raising a bug severity to the highest severity possible, please read and understand the Debian's release team guidelines regarding release critical bugs¹ as well as the general descriptions of bug severities². A "critical" bug is a bug that introduces a (remotely exploitable) security hole on systems you install the package to. A "grave" bug is a bug that introduces a (remotely exploitable) security hole allowing access to the accounts of users using the package. None of this is the case here. If at all, the bug might be "serious" if in the maintainers opinion it would make the package unsuitable for release. Now please respect the reduced bug severity. Raising the severity again won't get you any priority handling with an already understaffed Debian Qt/KDE team. This is a community of people who are mostly doing unpaid work. Two ways to use your (and our) time in a more productive manner are: 1) Retest with Okular 18.04 from Debian experimental (in case you run buster/sid). Or start KDE Neon in a machine and try with the newest Okular available there. 2) Remind upstream in a friendly way to have a look at the issue. Once there is a patch upstream it is very likely it could be backported for buster. Maybe it would be an idea to raise the upstream bug to KDE's security team. [1] https://release.debian.org/testing/rc_policy.txt [2] https://www.debian.org/Bugs/Developer Thanks, -- Martin
Re: Dolphin, Konsole and others are outdated
Dear Bruno, Bruno Gonçalves Araujo - 19.05.19, 02:15: > Dolphin, konsole and several other packages are getting pretty > outdated in the testing and unstable repositories, is there anything > that volunteers can do to improve this? Thank you for your offer to contribute. First off, please read about and understand the Debian release process. Debian Testing is currently in freeze¹. So for anyone who knows about the release process there is no surprise that the packages are not updated until Debian 10 aka Buster is released. If you like to help, I suggest you show up on #debian-qt-kde IRC channel on OFTC and introduce yourself to the Debian QT/KDE team there. However please understand this will not change the situation until Debian 10 is released. Debian testing/unstable is not a rolling distribution during that period. In any case please refrain from sending mails which include image bugs and tracking links like: https://mailtrack.io/trace/mail/7d833[…] I was very close to not answering your mail due to that as I thought it might be a spam mail. And also please do not use HTML mails². I highly recommend you use a mail provider that respects privacy. [1] https://raphaelhertzog.com/2010/10/18/understanding-debians-release-process/ and other resources on the net explain it [2] It is important to respect the code of conduct of the project you choose to contribute to: https://www.debian.org/MailingLists/#codeofconduct Thanks, -- Martin
Bug#921624: kmail: Crash during/after filtering inbox, probably related to Qt WebEngine integration
Hi. Sandro Knauß - 03.03.19, 23:46: […] > it does not looks like a packaging issue so far. Sorry for not checking in with valgrind so far. I hope to take time for this this week. > It may a duplicate of #923490. Or other way around, my bug report was first :) Thanks, -- Martin
Fwd: [Basket-devel] Basket 2.49-beta released
Hi! Just a heads-up that there now appears to be a basket release that uses KF5 / Qt 5. Thanks, Martin -- Weitergeleitete Nachricht -- Betreff: [Basket-devel] Basket 2.49-beta released Datum: Mittwoch, 27. Februar 2019, 22:20:33 CET Von: Gleb Baryshev An: basket-de...@lists.sourceforge.net Hi all, Happy to announce that 2.49-beta was released! It is based on 2.49-alpha (with some improvements) and is using KDE Frameworks 5. Note that git branches have been swapped: master became kde4 and kde5port became master. You will need to do git hard reset to pull the new master (or just make a new clone). Links to the sources: https://launchpad.net/basket/kde5/2.49b https://github.com/basket-notepads/basket/releases/tag/v2.49b Best regards, Gleb ___ Basket-devel mailing list basket-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/basket-devel - -- Martin
Re: akonadi-backend-mysql installs the mariadb service
Dear Yannick.
Yannick Roehlly - 09.02.19, 10:40:
> The akonadi-backend-mysql package changed its dependency from
> default-mysql- server-core to default-mysql-server.
>
> That means that is automatically installs a mariadb service. What was
> the problem with depending on the core package that only contains the
> binaries and does not launch the service ?
Just read the changelog.
Debian Bug report logs - #921389
akonadi-backend-mysql: akonadi fails to start creating new database/
config - ~/.local/share/akonadi/db_data/ not created
As soon as the core package again contain what is necessary, the work-
can be removed again.
akonadi (4:18.08.3-2) unstable; urgency=medium
* Team upload.
[ Sandro Knauß ]
* Rename {kubuntu_,}disable_secure_file_priv_check.diff.
* Update symbols from buildds for 4:18.08.3
[ Alf Gaida ]
* Replaced wrapper mysqld-akonadi with link mysqld -> mysqld-akonadi
(Closes: #921389)
* Replaced dependency for akonadi-backend-mysql:
- default-mysql-server-core -> default-mysql-server
- virtual-mysql-server-core -> virtual-mysql-server
-- Sandro Knauß <[…]> Wed, 06 Feb 2019 12:56:58 +0100
Thanks,
--
Martin
Bug#921624: kmail: Crash during/after filtering inbox, probably related to Qt WebEngine integration
Package: kmail Version: 4:18.08.3-1 Severity: important Tags: upstream Dear Sandro, Better late than never, I managed to report the KMail crashes during/after filtering inbox upstream. See: Bug 404052 - Crash during/after filtering inbox, probably related to Qt WebEngine integration https://bugs.kde.org/404052 This may or may not be a packaging related issue. Thanks, Martin -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-rc4-tp520 (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_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) Versions of packages kmail depends on: ii akonadi-server 4:18.08.3-2 ii kdepim-runtime 4:18.08.3-1 ii kio 5.54.1-1 ii libc62.28-6 ii libgcc1 1:8.2.0-17 ii libgpgmepp6 1.12.0-6 ii libkf5akonadiagentbase5 4:18.08.3-2 ii libkf5akonadicontact54:18.08.3-1 ii libkf5akonadicore5abi2 4:18.08.3-2 ii libkf5akonadimime5 4:18.08.3-1 ii libkf5akonadisearch-bin 4:18.08.3-1 ii libkf5akonadisearch-plugins 4:18.08.3-1 ii libkf5akonadisearchdebug54:18.08.3-1 ii libkf5akonadisearchpim5 4:18.08.3-1 ii libkf5akonadiwidgets5abi14:18.08.3-2 ii libkf5bookmarks5 5.54.0-1 ii libkf5calendarcore5abi2 4:18.08.3-1 ii libkf5calendarutils5 4:18.08.3-1 ii libkf5codecs55.54.0-1 ii libkf5completion55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configgui5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5contacts5 4:18.08.3-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5followupreminder5 4:18.08.3-1 ii libkf5grantleetheme-plugins 18.08.3-1 ii libkf5gravatar5abi2 4:18.08.3-1 ii libkf5guiaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes55.54.0-1 ii libkf5identitymanagement518.08.3-1 ii libkf5itemmodels55.54.0-1 ii libkf5itemviews5 5.54.0-1 ii libkf5jobwidgets55.54.0-1 ii libkf5kcmutils5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiofilewidgets55.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5kontactinterface5 18.08.3-1 ii libkf5ksieveui5 4:18.08.3-1 ii libkf5libkdepim-plugins 4:18.08.3-1 ii libkf5libkdepim5 4:18.08.3-1 ii libkf5libkdepimakonadi5 4:18.08.3-1 ii libkf5libkleo5 4:18.08.3-1 ii libkf5mailcommon5abi24:18.08.3-1 ii libkf5mailtransport5 18.08.3-1 ii libkf5mailtransportakonadi5 18.08.3-1 ii libkf5messagecomposer5abi1 4:18.08.3-1 ii libkf5messagecore5abi1 4:18.08.3-1 ii libkf5messagelist5abi1 4:18.08.3-1 ii libkf5messageviewer5abi1 4:18.08.3-1 ii libkf5mime5abi1 18.08.3-1 ii libkf5mimetreeparser5abi14:18.08.3-1 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5pimcommon5abi2 4:18.08.3-1 ii libkf5pimcommonakonadi5abi1 4:18.08.3-1 ii libkf5pimtextedit5abi2 18.08.3-1 ii libkf5sendlater5 4:18.08.3-1 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5sonnetui5 5.54.0-1 ii libkf5templateparser54:18.08.3-1 ii libkf5textwidgets5 5.54.0-1 ii libkf5tnef5 4:18.08.3-1 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libkf5webengineviewer5abi1 4:18.08.3-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqgpgme7 1.12.0-6 ii libqt5core5a 5.11.3+dfsg-2 ii libqt5dbus5 5.11.3+dfsg-2 ii libqt5gui5 5.11.3+dfsg-2 ii libqt5network5 5.11.3+dfsg-2 ii libqt5widgets5 5.11.3+dfsg-2 ii libqt5xml5 5.11.3+dfsg-2 ii libstdc++6 8.2.0-17 Versions of packages kmail recommends: ii accountwizard 4:18.08.3-1 ii gnupg 2.2.12-1 ii kdepim-addons 18.08.3-1 ii kdepim-themeeditors 4:18.08.3-1 pn mbox-importer pn pim-data-exporter pn pim-sieve-editor ii pinentry-gnome3 [pinentry-x11] 1.1.0-1+b1 ii pinentry-qt [pinentry-x11] 1.1.0-1+b1 Versions of packages kmail suggests: ii
Bug#913596: Link to KDE security advisory
It is not on the announcement page, but on the KDE security advisories page: https://www.kde.org/info/security/advisory-20181012-1.txt Thanks, -- Martin
Bug#913596: CVE-2018-19120: kio-extras: HTML Thumbnailer automatic remote file access
Package: kde-runtime Version: 4:17.08.3-2 Severity: important Tags: security Dear Maintainer, "KDE Project Security Advisory: kio-extras: HTML Thumbnailer automatic remote file access" (Message-ID: <5460566.RsyoOK3lV2@xps>, for some reason the mailing list archives are for subscribers only) mentions that 'htmlthumbnail.so' accesses content from remote files in HTML files to thumbnail. It has been assigned CVE number CVE-2018-19120. KDE developers removed the HTML thumbnailer for KDE Applications 18.12. KDE advisory mentions kio-extras. I am not sure whether 'htmlthumbnail.so' from KDE SC 4 in 'kde-runtime' is also affected. If so, work-around is to remove /usr/lib/kde4/htmlthumbnail.so The announcement should be accessible to the public on https://www.kde.org/announcements/ soon. Thanks, Martin -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-tp520 (SMP w/4 CPU cores; PREEMPT) 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) Versions of packages kde-runtime depends on: ii drkonqi 5.13.4-1 ii kde-runtime-data4:17.08.3-2 ii kdelibs5-plugins4:4.14.38-2 ii libasound2 1.1.7-1 ii libattica0.40.4.2-2 ii libc6 2.27-8 ii libcanberra00.30-6 ii libexiv2-14 0.25-4 ii libgcc1 1:8.2.0-9 ii libgcrypt20 1.8.4-3 ii libgpgme++2v5 4:4.14.10-10 ii libgpgme11 1.12.0-4 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libkactivities6 4:4.13.3-2 ii libkcmutils44:4.14.38-2 ii libkdeclarative54:4.14.38-2 ii libkdecore5 4:4.14.38-2 ii libkdesu5 4:4.14.38-2 ii libkdeui5 4:4.14.38-2 ii libkdewebkit5 4:4.14.38-2 ii libkdnssd4 4:4.14.38-2 ii libkemoticons4 4:4.14.38-2 ii libkfile4 4:4.14.38-2 ii libkhtml5 4:4.14.38-2 ii libkio5 4:4.14.38-2 ii libkmediaplayer44:4.14.38-2 ii libknewstuff3-4 4:4.14.38-2 ii libknotifyconfig4 4:4.14.38-2 ii libkparts4 4:4.14.38-2 ii libkpty44:4.14.38-2 ii libntrack-qt4-1 016-1.3 ii libopenexr232.2.1-4 ii libphonon4 4:4.10.1-1 ii libplasma3 4:4.14.38-2 ii libpulse-mainloop-glib0 12.2-2 ii libpulse0 12.2-2 ii libqt4-dbus 4:4.8.7+dfsg-17 ii libqt4-declarative 4:4.8.7+dfsg-17 ii libqt4-network 4:4.8.7+dfsg-17 ii libqt4-script 4:4.8.7+dfsg-17 ii libqt4-svg 4:4.8.7+dfsg-17 ii libqt4-xml 4:4.8.7+dfsg-17 ii libqtcore4 4:4.8.7+dfsg-17 ii libqtgui4 4:4.8.7+dfsg-17 ii libqtwebkit42.3.4.dfsg-10 ii libsmbclient2:4.9.1+dfsg-2 ii libsolid4 4:4.14.38-2 ii libssh-gcrypt-4 0.8.4-3 ii libstdc++6 8.2.0-9 ii libwebp60.6.1-2 ii libx11-62:1.6.7-1 ii libxcursor1 1:1.1.15-1 ii oxygen-icon-theme 5:5.51.0-1 ii phonon 4:4.10.1-1 ii plasma-scriptengine-javascript 4:17.08.3-2 Versions of packages kde-runtime recommends: ii icoutils 0.32.3-2 pn libcanberra-pulse | libcanberra-gstreamer ii sound-theme-freedesktop0.8-2 ii udisks22.8.1-2 ii upower 0.99.9-1 Versions of packages kde-runtime suggests: pn djvulibre-bin ii finger 0.17-15.1 -- no debconf information -- debsums errors found: debsums: missing file /usr/lib/kde4/htmlthumbnail.so (from kde-runtime package)
Bug#913595: CVE-2018-19120: kio-extras: HTML Thumbnailer automatic remote file access
Package: kio-extras Version: 4:18.08.1-1 Severity: important Tags: security Dear Maintainer, "KDE Project Security Advisory: kio-extras: HTML Thumbnailer automatic remote file access" (Message-ID: <5460566.RsyoOK3lV2@xps>, for some reason the mailing list archives are for subscribers only) mentions that 'htmlthumbnail.so' accesses content from remote files in HTML files to thumbnail. It has been assigned CVE number CVE-2018-19120. KDE developers removed the HTML thumbnailer for KDE Applications 18.12. Work-around is to remove /usr/lib/x86_64-linux-gnu/qt5/plugins/htmlthumbnail.so The announcement should be accessible to the public on https://www.kde.org/announcements/ soon. Thanks, Martin -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-tp520 (SMP w/4 CPU cores; PREEMPT) 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) Versions of packages kio-extras depends on: ii kio 5.51.0-1 ii kio-extras-data 4:18.08.1-1 ii libc62.27-8 ii libgcc1 1:8.2.0-9 ii libkf5activities55.51.0-1 ii libkf5archive5 5.51.0-1 ii libkf5bookmarks5 5.51.0-1 ii libkf5codecs55.51.0-1 ii libkf5configcore55.51.0-1 ii libkf5configgui5 5.51.0-1 ii libkf5configwidgets5 5.51.0-1 ii libkf5coreaddons55.51.0-1 ii libkf5dbusaddons55.51.0-1 ii libkf5dnssd5 5.51.0-1 ii libkf5guiaddons5 5.51.0-1 ii libkf5i18n5 5.51.0-1 ii libkf5iconthemes55.51.0-1 ii libkf5khtml5 5.51.0-1 ii libkf5kiocore5 5.51.0-1 ii libkf5kiofilewidgets55.51.0-1 ii libkf5kiowidgets55.51.0-1 ii libkf5parts5 5.51.0-1 ii libkf5pty5 5.51.0-1 ii libkf5service-bin5.51.0-1 ii libkf5service5 5.51.0-1 ii libkf5solid5 5.51.0-1 ii libkf5xmlgui55.51.0-1 ii libmtp9 1.1.13-1 ii libopenexr23 2.2.1-4 ii libphonon4qt5-4 4:4.10.1-1 ii libqt5core5a 5.11.2+dfsg-4 ii libqt5dbus5 5.11.2+dfsg-4 ii libqt5gui5 5.11.2+dfsg-4 ii libqt5network5 5.11.2+dfsg-4 ii libqt5sql5 5.11.2+dfsg-4 ii libqt5svg5 5.11.2-2 ii libqt5webenginewidgets5 5.11.2+dfsg-2 ii libqt5widgets5 5.11.2+dfsg-4 ii libqt5xml5 5.11.2+dfsg-4 ii libsmbclient 2:4.9.1+dfsg-2 ii libssh-4 0.8.4-3 ii libstdc++6 8.2.0-9 ii libtag1v51.11.1+dfsg.1-0.2+b1 ii phonon4qt5 4:4.10.1-1 kio-extras recommends no packages. kio-extras suggests no packages. -- no debconf information -- debsums errors found: debsums: missing file /usr/lib/x86_64-linux-gnu/qt5/plugins/htmlthumbnail.so (from kio-extras package)
Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related
Dmitry Shachnev - 19.10.18, 17:48: > Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=400028 > > On Fri, Oct 19, 2018 at 11:49:45AM +0200, Martin Steigerwald wrote: > > Unfortunately Akregator still crashes with Qt 5.11.2 packages. > > > > Maybe heise.de is a quite good way to reproduce it, in case that > > tracking script stuff is somehow related: > > > > http://www.heise.de/open/news/news-atom.xml > > I have reported this bug to Qt upstream, but they say it is not their > bug, but a thread safety issue in libkf5webengineviewer5. So I have > now filed a bug to KDE. Here further links to upstream bug reports. Bug which the bug 400028 you marked a duplicate of: [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click) https://bugs.kde.org/371511 Another upstream bug report: [akregator] [Bug 397866] akregator crashes when closing the rightmost tab https://bugs.kde.org/397866 Thanks -- Martin
Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related
Hi Dmitry. Dmitry Shachnev - 19.10.18, 09:00: > On Fri, Oct 12, 2018 at 12:10:26PM +0200, Martin Steigerwald wrote: > > Package: libqt5webengine5 > > Version: 5.11.1+dfsg-5 > > Severity: serious > > Justification: crashes make Akregator almost unusable > > > > Dear Dmitry, > > > > I found Akregator crashing very often when accessing articles as > > webpages which are rendered by Qt WebEngine. These may also be > > related to KDEPIM 18.08 update. Please reassign if needed. > > Can you please check if this still happens with Qt 5.11.2 packages, > which are now in Debian unstable? Unfortunately Akregator still crashes with Qt 5.11.2 packages. Maybe heise.de is a quite good way to reproduce it, in case that tracking script stuff is somehow related: http://www.heise.de/open/news/news-atom.xml Here another backtrace: WebEnginePage::javaScriptConsoleMessage lineNumber: 16 message: "A parser-blocking, cross site (i.e. different eTLD+1) script, https://adserver.idg.de/gptjs/tn/tn_dogpt_sync.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message. See https://www.chromestatus.com/feature/5718547946799104 for more details." WebEnginePage::javaScriptConsoleMessage lineNumber: 651 message: "Uncaught TypeError: googletag.defineSlot is not a function" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught TypeError: Cannot read property 'getItem' of null" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught TypeError: Cannot read property 'getItem' of null" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught TypeError: Cannot read property 'getItem' of null" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught (in promise) TypeError: Cannot read property 'getUserHash' of undefined" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "TypeError: b.toUpperCase is not a function" [Thread 0x7fff2fda2700 (LWP 6050) exited] [Thread 0x7fff9f7fe700 (LWP 5327) exited] [Thread 0x7fffbcff9700 (LWP 5325) exited] Thread 21 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff7700 (LWP 5333)] 0x7fffed21086c in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 (gdb) bt full #0 0x7fffed21086c in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #1 0x7fffeeca82a6 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #2 0x7fffeedf86eb in net::URLRequest::Start() [clone .part.109] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #3 0x7fffedb13bce in content::ResourceLoader::StartRequestInternal() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #4 0x7fffedb148ad in content::ResourceLoader::Resume(bool) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #5 0x7fffedb14a9a in content::ResourceLoader::StartRequest() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #6 0x7fffedb0e1de in content::ResourceDispatcherHostImpl::BeginRequestInternal(std::unique_ptr >, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #7 0x7fffedb0faff in content::ResourceDispatcherHostImpl::BeginNavigationRequest(content::ResourceContext*, net::URLRequestContext*, storage::FileSystemContext*, content::NavigationRequestInfo const&, std::unique_ptr >, content::NavigationURLLoaderImplCore*, mojo::InterfacePtr, mojo::InterfaceRequest, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, unsigned int, content::GlobalRequestID*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #8 0x7fffedafd855 in content::NavigationURLLoaderImplCore::Start(content::ResourceContext*, net::URLRequestContextGetter*, storage::FileSystemContext*, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, std::unique_ptr >, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so
Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related - another backtrace
Hello. I produced another backtrace. Backtraces appear to be random to me. If its helpful I can produce some more backtrace at a later time. I think that "A parser-blocking, cross site" message on console is unrelated. The message comes very often. Also way before it crashes. I think I may better switch Akregator to use an external web browser that I hardened before in the future. WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught TypeError: Cannot read property 'mobile_detect_force_mobile' of null" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught TypeError: Cannot read property 'getItem' of null" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught (in promise) TypeError: Cannot read property 'getItem' of null" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "Uncaught (in promise) TypeError: Super expression must either be null or a function, not undefined" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "TypeError: b.toUpperCase is not a function" [New Thread 0x7fff32a5d700 (LWP 24326)] WebEnginePage::javaScriptConsoleMessage lineNumber: 2 message: "JQMIGRATE: Migrate is installed, version 1.4.1" [New Thread 0x7fff3225c700 (LWP 24568)] [Thread 0x7fff3b7ff700 (LWP 22492) exited] [New Thread 0x7fff3b7ff700 (LWP 24692)] Thread 21 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff7700 (LWP 19839)] 0x0020 in ?? () (gdb) bt full #0 0x0020 in ?? () No symbol table info available. #1 0x7fffed18811f in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #2 0x7fffeec1db86 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #3 0x7fffeed6c1ab in net::URLRequest::Start() [clone .part.109] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #4 0x7fffeda8b01e in content::ResourceLoader::StartRequestInternal() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #5 0x7fffeda8bcfd in content::ResourceLoader::Resume(bool) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #6 0x7fffeda8beea in content::ResourceLoader::StartRequest() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #7 0x7fffeda8562e in content::ResourceDispatcherHostImpl::BeginRequestInternal(std::unique_ptr >, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #8 0x7fffeda86f4f in content::ResourceDispatcherHostImpl::BeginNavigationRequest(content::ResourceContext*, net::URLRequestContext*, storage::FileSystemContext*, content::NavigationRequestInfo const&, std::unique_ptr >, content::NavigationURLLoaderImplCore*, mojo::InterfacePtr, mojo::InterfaceRequest, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, unsigned int, content::GlobalRequestID*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #9 0x7fffeda74ca5 in content::NavigationURLLoaderImplCore::Start(content::ResourceContext*, net::URLRequestContextGetter*, storage::FileSystemContext*, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, std::unique_ptr >, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #10 0x7fffeda745b0 in base::internal::Invoker >, std::unique_ptr >), scoped_refptr, content::ResourceContext*, base::internal::UnretainedWrapper, base::internal::UnretainedWrapper, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, base::internal::PassedWrapper > >, base::internal::PassedWrapper > > >, void ()>::RunOnce(base::internal::BindStateBase*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #11 0x7fffee71a218 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #12 0x7fffee73a91a in base::MessageLoop::RunTask(base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #13 0x7fffee73b3bf in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #14 0x7fffee73b558 in base::MessageLoop::DoWork() [clone .part.202] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info avai
Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related
Package: libqt5webengine5 Version: 5.11.1+dfsg-5 Severity: serious Justification: crashes make Akregator almost unusable Dear Dmitry, I found Akregator crashing very often when accessing articles as webpages which are rendered by Qt WebEngine. These may also be related to KDEPIM 18.08 update. Please reassign if needed. I downgraded libqt5quick5 to 5.11.1-5 due to the hint in #910317: libqt5quick5: Sefault in applications using QWebEngineView https://bugs.debian.org/910500 However this did not help. Thus I installed debug packages to retrieve a useful backtrace. Steps to reproduce: - Start Akregator - Open articles in a few feeds (I used feeds from pro-linux.de, heise.de/open and various Debian related and other feeds, I bet it does not matter all that much which ones) - Click around in those articles, follow links, close QtWebEngine rendered articles Basically I just "use" Akregator as usual and it usually crashes within 5 minutes. I have also seen crashes in KMail after having rendered HTML mail. I did not yet generate a backtrace from those. Often I see this "A parser-blocking, cross site" message on console. I do not know whether this is related. I'd love to use uBlock Origin with my hardened settings within Qt WebEngine to get rid of that advertising and tracking crap. WebEnginePage::javaScriptConsoleMessage lineNumber: 0 message: "Mixed Content: The page at 'https://www.pro-linux.de/news/1/26392/pydio-cells-12-verzichtet-auf-php.html' was loaded over HTTPS, but requested an insecure script 'http://pagead2.googlesyndication.com/pagead/show_ads.js'. This request has been blocked; the content must be served over HTTPS." WebEnginePage::javaScriptConsoleMessage lineNumber: 16 message: "A parser-blocking, cross site (i.e. different eTLD+1) script, https://adserver.idg.de/gptjs/tn/tn_dogpt_sync.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message. See https://www.chromestatus.com/feature/5718547946799104 for more details." WebEnginePage::javaScriptConsoleMessage lineNumber: 16 message: "A parser-blocking, cross site (i.e. different eTLD+1) script, https://adserver.idg.de/gptjs/tn/tn_dogpt_sync.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message. See https://www.chromestatus.com/feature/5718547946799104 for more details." WebEnginePage::javaScriptConsoleMessage lineNumber: 620 message: "Uncaught TypeError: googletag.defineSlot is not a function" WebEnginePage::javaScriptConsoleMessage lineNumber: 2 message: "Uncaught Error: Error: No input element in the page matches .algolia-search" Thread 21 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff7700 (LWP 28635)] 0x00750062006d in ?? () (gdb) bt full #0 0x00750062006d in ?? () No symbol table info available. #1 0x7fffed18811f in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #2 0x7fffeec1db86 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #3 0x7fffeed6c1ab in net::URLRequest::Start() [clone .part.109] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #4 0x7fffeda8b01e in content::ResourceLoader::StartRequestInternal() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #5 0x7fffeda8bcfd in content::ResourceLoader::Resume(bool) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #6 0x7fffeda8beea in content::ResourceLoader::StartRequest() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #7 0x7fffeda8562e in content::ResourceDispatcherHostImpl::BeginRequestInternal(std::unique_ptr >, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 No symbol table info available. #8 0x7fffeda86f4f in content::ResourceDispatcherHostImpl::BeginNavigationRequest(content::ResourceContext*, net::URLRequestContext*, storage::FileSystemContext*, content::NavigationRequestInfo const&, std::unique_ptr >, content::NavigationURLLoaderImplCore*, mojo::InterfacePtr, mojo::InterfaceRequest, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, unsigned int, content::GlobalRequestID*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEng
Bug#908079: Buster: No window title bars in KDE?
local10 - 07.09.18, 16:12: > Sep 7, 2018, 8:18 AM by mar...@lichtvoll.de: > > It does recommend kwin-x11 by depending on kde-plasma-desktop which > > depends on plasma-desktop which recommends kwin-x11 (>= 4:5.13) | > > kwin > I do not install recommended packages, only what's necessary. However, > if the system cannot function properly without a package it's a > requirement, not a recommendation. local10, a bug report is really not the right place to discuss Debian packaging policy: > Recommends > > This declares a strong, but not absolute, dependency. > > The Recommends field should list packages that would be found > together with this one in all but unusual installations. https://www.debian.org/doc/debian-policy/ch-relationships.html If you choose not to install recommends which is perfectly your choice you get to deal with the consequences. Installing them is default for a reason. If you really want to challenge this policy, then I suggest you post to debian-devel, but then you better have a very good explanation for using a depends on packages like kwin-x11 while systems can and do work perfectly fine without them. Thanks, -- Martin
Bug#908095: Buster: Kwrite crashes while opening a file
tag 908095 upstream thanks local10 - 07.09.18, 12:15: > Was able to open the problematic file by reconfiguring Kwrite and > changing the default encoding to UTF-8 and the fallback encoding to > UTF-16 (Kwrite keeps changing UTF-16 to ucs2 but whatever). > > That's a good news for me, of course, but still I feel Kwrite > shouldn't crash like that even if the default and fallback encoding > do not match the file's encoding. In Wheezy I sometimes would open a > binary file with Kwrite and I don't even remember when Kwrite crashed > like that, if it ever did. This is an upstream issue. Please report with https://bugs.kde.org if not already done so and report the link to this bug report. By doing so you help our small Debian Qt/KDE team a lot. Bugs to Debian are not automatically forwarded to the upstream bug tracker. Before doing so please retest with Kate 18.08 which is available in Buster meanwhile. Actually, for smaller upstream issues I think its better to just report upstream. If there is an upstream patch depending on the severity of the issue and on planned release date of next Debian stable release, it can make sense to open a Debian bug report asking to include it. Thanks, -- Martin
Bug#908079: Buster: No window title bars in KDE?
local10 - 06.09.18, 18:22: > Also: > > # dpkg -S kwin_x11 > dpkg-query: no path found matching pattern *kwin_x11* % dpkg -S kwin_x11 kwin-x11: /usr/lib/x86_64-linux-gnu/libkdeinit5_kwin_x11.so kwin-x11: /usr/bin/kwin_x11 (with http://ftp.de.debian.org/debian/ as mirror) As of now kwin-x11 package is available for buster: % rmadison kwin-x11 kwin-x11 | 4:5.8.6-1 | stable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x kwin-x11 | 4:5.13.4-1| testing| amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x kwin-x11 | 4:5.13.4-1| unstable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x So I´d use "apt update" and if the package then still is not available, check your /etc/apt/sources.list. Maybe your mirror is outdated. But again, this is no user support forum. Please use debian-kde mailing list. Thanks, -- Martin
Bug#908079: Buster: No window title bars in KDE?
local10 - 06.09.18, 18:06: > luser@tstsrv:~$ kwin_x11 --replace & > [1] 12686 > bash: kwin_x11: command not found > luser@tstsrv:~$ kwin_x11 is in package kwin-x11 (as dpkg -S tells). But the Debian bugtracker is no user support forum. Please use debian- kde mailing list. The bugtracker is for bug reports and improvement suggestions only. Thanks, -- Martin
Re: Bug#908043: plasma-desktop: Plasma-desktop loads with black screen
severity 908043 important tags 908043 upstream thanks Dear MH. This looks like an upstream bug. I recommend you report this to upstream bugtracker¹ in case not already done so. Please report back the link to the upstream bug report. By doing so you help the small Debian Qt/KDE team. Severity of this bug is in no way grave as what you reported only happens in a special use case, while the package just works fine for the majority of users. It may be grave to you, but that is not what is meant with "grave" severity in Debian. Instead this is what bug severity "important" is for². [1] https://bugs.kde.org [2] see https://www.debian.org/Bugs/Developer#severities (especially description for "important") Thanks, Martin MH - 05.09.18, 14:58: > Package: plasma-desktop > Version: 4:5.8.6-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > When PC is connected to AVR via HDMI, plasma-desktop loads with a > black screen. Apparently, it queries the EDID of the connected TV, > which is 4k. Previously, SDDM did the same thing. The AVR is limited > to 1920x1080 input. Creating an xorg.conf file using NVidia Settings > solve the issue for SDDM, but that file seems to be ignored by > plasma-desktop. The desktop still responds to keyboard input, but is > otherwise unusable. This situation also exists under Buster. > > IMO the problem is not with the AVR, which needs to passthrough EDID > so monitors with lesser resolutions are correctly detected. > Plasma-desktop should not requery for EDID but should accept the same > settings as SDDM. Or maybe this is an issue with Xserver? > > -- System Information: > Debian Release: 9.5 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages plasma-desktop depends on: > ii breeze 4:5.8.5-2 > ii kactivitymanagerd5.8.4-1 > ii kde-cli-tools4:5.8.4-2 > ii kded55.28.0-1 > ii kio 5.28.0-2 > ii libc62.24-11+deb9u3 > ii libcanberra0 0.30-3 > ii libfontconfig1 2.11.0-6.7+b1 > ii libgcc1 1:6.3.0-18+deb9u1 > ii libkf5activities55.28.0-1 > ii libkf5activitiesstats1 5.28.0-1 > ii libkf5archive5 5.28.0-2 > ii libkf5auth5 5.28.0-2 > ii libkf5baloo5 5.28.0-2 > ii libkf5bookmarks5 5.28.0-1 > ii libkf5codecs55.28.0-1+b2 > ii libkf5completion55.28.0-1 > ii libkf5configcore55.28.0-2 > ii libkf5configgui5 5.28.0-2 > ii libkf5configwidgets5 5.28.0-2 > ii libkf5coreaddons55.28.0-2 > ii libkf5dbusaddons55.28.0-1 > ii libkf5emoticons-bin 5.28.0-1 > ii libkf5emoticons5 5.28.0-1 > ii libkf5globalaccel5 5.28.0-1 > ii libkf5guiaddons5 5.28.0-1 > ii libkf5i18n5 5.28.0-2 > ii libkf5iconthemes55.28.0-2 > ii libkf5itemmodels55.28.0-2 > ii libkf5itemviews5 5.28.0-1 > ii libkf5jobwidgets55.28.0-2 > ii libkf5kcmutils5 5.28.0-2 > ii libkf5kdelibs4support5 5.28.0-1 > ii libkf5kiocore5 5.28.0-2 > ii libkf5kiofilewidgets55.28.0-2 > ii libkf5kiowidgets55.28.0-2 > ii libkf5newstuff5 5.28.0-1 > ii libkf5notifications5 5.28.0-1 > ii libkf5notifyconfig5 5.28.0-1 > ii libkf5parts5 5.28.0-1 > ii libkf5people55.28.0-1 > ii libkf5peoplewidgets5 5.28.0-1 > ii libkf5plasma55.28.0-2 > ii libkf5plasmaquick5 5.28.0-2 > ii libkf5quickaddons5 5.28.0-1 > ii libkf5runner55.28.0-1 > ii libkf5service-bin5.28.0-1 > ii libkf5service5 5.28.0-1 > ii libkf5solid5 5.28.0-3 > ii libkf5sonnetui5 5.28.0-2 > ii libkf5wallet-bin 5.28.0-3 > ii libkf5wallet5
Bug#902611: kate: add build dependency for editorconfig support
Pino Toscano - 28.06.18, 21:57: > In data giovedì 28 giugno 2018 14:19:26 CEST, Martin Steigerwald ha > scritto: > > Please add libeditorconfig-dev as a build dependency for Kate in > > order to enable editorconfig support. > > Kate has no editorconfig support, so there is no build dependency to > add. > ktexteditor has editorconfig support, and it is already enabled (see > the dependencies of libkf5texteditor5). Thank you. I missed that. Sorry for the noise. Ciao, -- Martin
Bug#902611: kate: add build dependency for editorconfig support
Package: kate Version: 4:18.04.0-1 Severity: normal Dear Pino, dear Maintainers, Please add libeditorconfig-dev as a build dependency for Kate in order to enable editorconfig support. editorconfig support? https://mail.kde.org/pipermail/kwrite-devel/2018-June/000564.html And: https://editorconfig.org/ It is a standard so that mutiple editors can share same settings for coding styles in different editors and IDEs. Thanks, Martin -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT) 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) Versions of packages kate depends on: ii kate5-data 4:18.04.0-1 ii kio 5.47.0-1 ii ktexteditor-katepart 5.47.0-1 ii libc62.27-3 ii libkf5activities55.47.0-1 ii libkf5bookmarks5 5.47.0-1 ii libkf5completion55.47.0-1 ii libkf5configcore55.47.0-1 ii libkf5configgui5 5.47.0-1 ii libkf5configwidgets5 5.47.0-1 ii libkf5coreaddons55.47.0-1 ii libkf5crash5 5.47.0-1 ii libkf5dbusaddons55.47.0-1 ii libkf5guiaddons5 5.47.0-1 ii libkf5i18n5 5.47.0-1 ii libkf5iconthemes55.47.0-1 ii libkf5itemmodels55.47.0-1 ii libkf5jobwidgets55.47.0-1 ii libkf5kiocore5 5.47.0-1 ii libkf5kiofilewidgets55.47.0-1 ii libkf5kiowidgets55.47.0-1 ii libkf5newstuff5 5.47.0-1 ii libkf5parts5 5.47.0-1 ii libkf5plasma55.47.0-1 ii libkf5service-bin5.47.0-1 ii libkf5service5 5.47.0-1 ii libkf5texteditor55.47.0-1 ii libkf5textwidgets5 5.47.0-1 ii libkf5threadweaver5 5.47.0-1 ii libkf5wallet-bin 5.47.0-1 ii libkf5wallet55.47.0-1 ii libkf5widgetsaddons5 5.47.0-1 ii libkf5windowsystem5 5.47.0-1 ii libkf5xmlgui55.47.0-1 ii libqt5core5a 5.10.1+dfsg-7 ii libqt5dbus5 5.10.1+dfsg-7 ii libqt5gui5 5.10.1+dfsg-7 ii libqt5sql5 5.10.1+dfsg-7 ii libqt5widgets5 5.10.1+dfsg-7 ii libqt5xml5 5.10.1+dfsg-7 ii libstdc++6 8.1.0-8 ii plasma-framework 5.47.0-1 ii qml-module-org-kde-kquickcontrolsaddons 5.47.0-1 ii qml-module-qtquick-layouts 5.10.1-4 ii qml-module-qtquick2 5.10.1-4 Versions of packages kate recommends: ii sonnet-plugins 5.47.0-1 Versions of packages kate suggests: ii darcs2.14.0-1 pn exuberant-ctags ii git 1:2.18.0-1 ii khelpcenter 4:18.04.0-1 ii konsole-kpart4:18.04.0-1 ii mercurial4.6.1-1 ii subversion 1.10.0-2 -- no debconf information
Re: Pulseaudio module migration gconf => gsettings
Ben Cooksley - 27.06.18, 13:09: > > Ben, you are shooting the messenger and there is a misunderstanding > > coming from a lack of knowledge on how Debian works. > > > > The dropping of the pulseaudio gconf subpackage It's not a decision > > of the Debian KDE Team. This is a decision of the Debian Pulseaudio > > packagers, and according the other comments from the bug, other > > distributions are doing exactly the same. > > Having looked at the exchanges made by the Debian Pulseaudio > maintainer, they appear to have completely ignored plasma-pa, so their > position of refusing to support GConf (when GSettings support has > only just been introduced by Pulseaudio upstream) is quite > unconscionable. No notice has been given at all. They should be > compelled to restore that support to allow for a reasonable window > for us to port. > > Given how new the support in Pulseaudio is, it is unreasonable to > expect us to have support ready for it in such a short time frame. As I wrote in the Plasma bug report Bug 386665 - Drop dependency on pulseaudio-gconf https://bugs.kde.org/386665 but probably should have better written here: > It seems everyone seems to have different expectations here: > > - Pulseaudio project appears to expect that people port over to > gsettings at the *first* release with gsettings module, maybe due to > technical difficulties of providing both modules (and synchronisation > between them). > > - Debian Pulseaudio package maintainer just uploaded Pulseaudio to > upstream, instead of providing it in experimental in order to allow > packages to be ported, arguing that gconf module has been deprecated > (without proper replacement) since a long time. > > - KDE upstream expects to have something stable to port to before > starting the work. > > All totally valid expectations, each with their own reasons. Just they > do not go well together. Clearly communication about how to > coordinate this migration has been missing. […] But this all is in the past now and there is a plan forward. If anything to take away from this, it might be to take a look at how the different involved projects can work together better. We have the distro-packagers list as a channel for communication between KDE and distros. It probably would have made sense to use this earlier for communicating about this issue. I decided to do that next time. But as as far as I am aware there is nothing in place for communication of upstreams for Plasma / KDE Applications / KF5 with the KDE community. At the moment I don´t really have a clear idea on how to improve this. Maybe some upstream mailing list for important incompatibility announcements would be good, but it would put an additional burden on upstreams. Ideally upstreams would have a standard release note format for breaking changes that could be used. In the end even with a communication channel, it is up to the individual persons to use it. OTOH this something like this does not happen all that often… Thanks, -- Martin
Re: Pulseaudio module migration gconf => gsettings
Sorry, forgot to reply to all.
Ben Cooksley - 27.06.18, 07:53:
> > You might want to use the frugalware patch [1] as a base for this.
> > This patch
> > is mentioned in the kde bug (although it wasn't linked), I was
> > considering using something like that, before plasma-pa gets
> > removed from Debian testing
> > (if it comes to that).
>
> I'm not hugely happy with the inference here that if we don't address
> this, you'll be removing the Pulseaudio applet. Given that
> controlling system audio is a rather crucial part of the desktop
> experience, it's a bit disappointing you're thinking of resorting to
> that.
Ben, just a short clarification for that one:
Debian has an autoremoval process of packages from testing due to bug
reports of a certain priority. I think Maxy may have referred to this
process ("if it comes to that").
There has been the consideration to replace plasma-pa by kmix
temporarily, but I think this was not really a good option.
Anyway, Maxy just uploaded Plasma 5.13 to Debian Unstable with gconf
module support removed, so plasma-pa will still be available, although
with a limited functionality (no virtual sound devices).
Thanks,
--
Martin
Bug#886048: Bug#902181: Bug#886048: plasma-pa: Depends on gconf
Martin Steigerwald - 26.06.18, 12:04: > I still have no clear idea at what functionality will break by doing > so. Asked so on kde-distro-packagers list. I now also asked on > upstream bug report again: > > https://bugs.kde.org/show_bug.cgi?id=386665#c18 Here is the functionality that will break: From David Rosca: > Two checkboxes under Advanced tab in KCM: > > * Add virtual output device for simultaneous output on all local sound > cards > * Automatically switch all running streams when a new output > becomes available Those will be now hidden when building without GConf. From Christophe Giboudeaux: > Virtual devices. The openSUSE maintainers for pulseaudio tried > removing the gconf plugin and it made my virtual card to have sound > both on my speakers & USB card disappear. To me it seems like it is dropping gconf support for *now* and readding gsettings support back in with Plasma 5.14. There may be some users who use virtual devices, but I bet most users won´t. And those may still be able to use paprefs as a interim solution. Upstream patch for dropping gconf support, by David Rosca: https://phabricator.kde.org/D13734 Thanks, -- Martin
Bug#886048: Bug#902181: Bug#886048: plasma-pa: Depends on gconf
Martin Steigerwald - 25.06.18, 17:39: > Felipe Sateler - 25.06.18, 16:41: > > > With Debian's pulseaudio 12.0 upload, pulseaudio has removed > > > pulseaudio- module-gconf in favour of pulseaudio-module-gsettings, > > > which would break current plasma-pa. > > > > Indeed. While pulseaudio can build a gconf or a gsettings backend, > > building both is not advisable and would lead to confusion, as > > changes would not be synchronized between the modules. Therefore I > > have removed the gconf module. > > > > The only reverse dependencies are plasma-pa and paprefs. paprefs is > > already fixed upstream and I'm only waiting on a release to upload > > to debian. That would leave plasma-pa to be fixed. > > Please also see upstream bug report: > > [plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf? > https://bugs.kde.org/386665 > > I hope that upstream provides a fix soon. A port before Plasma 5.14 is unlikely: https://bugs.kde.org/show_bug.cgi?id=386665#c17 So seems to me that building without gconf module support is the best option for now. See: https://bugs.kde.org/show_bug.cgi?id=386665#c16 => https://build.opensuse.org/package/view_file/ home:cfeck:branches:KDE:Unstable:Frameworks/plasma5-pa/plasma-pa.diff? expand=1 I still have no clear idea at what functionality will break by doing so. Asked so on kde-distro-packagers list. I now also asked on upstream bug report again: https://bugs.kde.org/show_bug.cgi?id=386665#c18 Thanks, -- Martin
Re: Pulseaudio module migration gconf => gsettings
Hi David. Many thanks for your prompt response. David Rosca - 26.06.18, 08:23: > On Mon, Jun 25, 2018 at 11:01 PM Martin Steigerwald wrote: > > Hi! > > > > The unfixed bug > > > > Bug 386665 - Drop dependency on pulseaudio-gconf > > > > makes plasma-pa uninstallable in the development versions of Debian > > and Arch. > > > > We would really appreciate an upstream fix for that one. The comment > > by Luigi points out commits for paprefs gconf => gsettings > > migration. Maybe something similar would work with Plasma PA? > > > > https://bugs.kde.org/show_bug.cgi?id=386665#c13 > > > > Would someone help David Rosca (in Cc) in case he is unavailable or > > has no time to attend to the issue? > > We are aware of the issue and are planning to port to gsettings. > Actually, it may be added as alternative to gconf as otherwise it will > break the functionality for distros that doesn't have PulseAudio 12 > yet. For now, I'll make the gconf dependency optional. > > Also, PulseAudio 12 was released less then one week ago, and you > immediately dropped gconf package, would be cool if you gived us a > little more time. Pulseaudio package maintainer did so. I bet Qt/KDE team would also liked to have more time. On the other hand the deprecation of gconf module in Pulseaudio is quite old I believe. What is the functionality that will break without the gconf or gsettings module? I think building without gconf may be good enough as an interim solution if not too much stuff breaks for our Debian Unstable / Testing users. Thansk, -- Martin
Pulseaudio module migration gconf => gsettings
Hi! The unfixed bug Bug 386665 - Drop dependency on pulseaudio-gconf makes plasma-pa uninstallable in the development versions of Debian and Arch. We would really appreciate an upstream fix for that one. The comment by Luigi points out commits for paprefs gconf => gsettings migration. Maybe something similar would work with Plasma PA? https://bugs.kde.org/show_bug.cgi?id=386665#c13 Would someone help David Rosca (in Cc) in case he is unavailable or has no time to attend to the issue? Many thanks. -- Martin
Bug#886048: Bug#902181: Bug#886048: plasma-pa: Depends on gconf
Dear Felipe, dear Maintainers. Felipe Sateler - 25.06.18, 16:41: > > With Debian's pulseaudio 12.0 upload, pulseaudio has removed > > pulseaudio- module-gconf in favour of pulseaudio-module-gsettings, > > which would break current plasma-pa. > > Indeed. While pulseaudio can build a gconf or a gsettings backend, > building both is not advisable and would lead to confusion, as > changes would not be synchronized between the modules. Therefore I > have removed the gconf module. > > The only reverse dependencies are plasma-pa and paprefs. paprefs is > already fixed upstream and I'm only waiting on a release to upload to > debian. That would leave plasma-pa to be fixed. Please also see upstream bug report: [plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf? https://bugs.kde.org/386665 I hope that upstream provides a fix soon. Thanks, -- Martin
Bug#900145: Bug#900352: new xorg-server version causes a random freezes in plasmashell
Hi. Maximiliano Curia - 29.05.18, 14:18: > Package: src:xorg-server > Version: 2:1.20.0-2 > Severity: critical > Tags: upstream […] > The severity is set as it breaks "unrelated programs" although I'm not > sure a desktop environment can be called "unrelated" to x, but in any > case, it would be better if this version of xorg does not migrate to > testing till this is fixed. Probably related: xserver-xorg-core: flickering, black screen and modeset driver error: flip queue failed: Cannot allocate memory https://bugs.debian.org/900333 But depends on whether you use modesettings driver and have your Xorg log spammed with: [ 1201.939] (WW) modeset(0): flip queue failed: Cannot allocate memory [ 1201.939] (WW) modeset(0): Page flip failed: Cannot allocate memory [ 1201.939] (EE) modeset(0): present flip failed Thanks, -- Martin
Re: KDEPIM 17.12: pane that show message structure missing?
Reinhard Karcher - 12.04.18, 10:04: > Am Thursday, 12 April 2018, 09:33:43 CEST schrieb Martin Steigerwald: > > With KDEPIM prior 17.12 I always had a pane that shows the message > > structure where I could select which part of the message to view in > > the message content display area. So with messages that are both > > available as text and HTML I could select which one to view. > > > > This is gone since KDEPIM 17.12 and I found no way to enable it > > again. I remember there was an option but I digged through all > > menus and configuration options three times without finding it. > > > > Any idea? > > > > Thanks, > > Use Settings, Configure Toolbar, > Move Show Message Structure Thank you Reinhard. Wonderful. So I disable show HTML by default again. -- Martin
Bug#894425: kaddressbook: Broken package, errors on start
tag 894425 moreinfo thanks Hi skyguide. skyguide - 30.03.18, 09:11: >* What exactly did you do (or not do) that was effective (or > ineffective)? > > After installation of the kaddressbook, it did not run, errored out with > a message 'The Akonadi personal information management service is not > operational', I did a research, could not find any relevant / helpful > info on-line, attempts to run this software via GUI was not succsessful. > Purgin via apt and re-installing resulted in a same failure to star the > appliaction. Usually this comes with a log you can view, a kind of self-test report that lists which components do and which do not work, usually including error messages. Please include this report *in full*. Also look for any error logs in ~/.local/share/akonadi like akonadiserver.error and akonadi_control.error and db_data/mysql.err If you find anything, please review it and post any errors and the surroundings messages. Or attach in full after you made sure it does not contain and sensitive information regarding your privacy. Please also provide the output of the following command *in full*: apt list --installed | egrep "^akonadi|^mariadb|^mysql" Also please provide the output of the following command after you attempted to start KAddressBook. ps aux | egrep "akonadi|mysql|mariadb" Without more detailed information your bug report is not actionable. Thanks, -- Martin
Bug#886048: plasma-pa: Depends on gconf
Hi. I do not know what the best solution is, but upstream Pulseaudio developer Tanu recommends not using gconf at all: https://bugs.freedesktop.org/show_bug.cgi?id=57743#c2 However that would need extensions to Pulseaudio client API: https://bugs.freedesktop.org/show_bug.cgi?id=57743#c4 I am not sure of the current state on this, since this comment was in 2014. So I asked upstream about it. Another approach would be: pulseaudio-module-gconf: migration to a dconf PA backend https://bugs.debian.org/757909 Thanks, -- Martin
Bug#863844: kwalletmanager: Migration does not work and restarts at every login
Martin Steigerwald - 06.02.18, 22:57: > Please note that this is also an upstream issue, so you can help by > researching in the upstream bug tracker² for a bug about it. If you find > one, please add information about it to this bug report. Well I searched > there for "kwalletmanager migration", but found no obvious fit for your bug > description³. But please look for yourself and probably try out different > search terms. […] Hmmm, I think this one may be a fit of the original bug reports bug title and description: KDE Wallet migration assistant doesn't migrate https://bugs.kde.org/357058 > [3] https://bugs.kde.org/buglist.cgi?quicksearch=kwallet%20migration Thanks, -- Martin
Re: Bug#809964: all my passwords are gone
severity 809964 normal kthxbye Dear Tomas, Tomas Pospisek - 06.02.18, 21:38: > originally I've posted this as a follow up to > #863844, however #809964 seems to be the more appropriate place. please refrain from raising the severity of unrelated bugs to critical. It won´t help you towards a solution. Please read my comment to kwalletmanager: Migration does not work and restarts at every login https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863844#15 And ask in debian-kde mailing list for help on how to complete the migration. It is not beneficial to discuss this in the bug tracker, so please use user support mailing list for finding help with this upstream issue. The aim of the Qt/KDE team is to remove Qt4 for next Debian release. So there are no plans on making kwalletmanager from KDE SC 4 and kwalletmanager5 from Plasma 5 co-installable. Thanks, -- Martin
Bug#863844: all my passwords are gone
Hello Tomas. Tomas Pospisek - 06.02.18, 21:30: > just as Rainer reported: > > * before upgrading from jessie to stretch I've checked the release notes >there seems to be no mention of kwallet in the notes > * then I've upgraded from jessie to stretch > * when I start kwalletmanager it comes up empty >* all my passwords seem to be gone > * when I select File -> Import a wallet, nothing happens, no dialog shows up > * when I select File -> Import XML, nothing happens, no dialog shows up > > I think this bug report by Rainer should have had severity critical and > have blocked kwalletmanager from entering stretch. I disagree, see below. > At this point I do not know how to recover the passwords from kwallet. > Looks like 100% data loss at this point. Kwalletmanager from Plasma 5 does not delete the original KDE SC 4 KWallet files. So I think it is safe to say the *.kwl files in ~/.kde/share/apps/ kwallet are still there. For some reason the migration failed on your system, but AFAIK you can repeat the attempt to migrate as many times as you like. I think it is sufficient to remove the first two lines from the config file of the kwalletmanager from Plasma 5. ~/.config> head -2 kwalletrc [Migration] alreadyMigrated=true and restart kwalletmanager. There was a blog post from KWallet Manager but, I cannot access it currently.[0] But really, this is user support, so please ask in debian-kde mailing list for help on how to successfully migrate it. If you then find a solution, then feel free to add it to the bug report. Again, I am nearly 100% sure that there is no data loss. So a severity of critical is not justified¹. I totally get that you are frustrated, but please first check whether your old kwalletmanager from KDE SC 4 *.kwl files are still there before setting the bug severity based on assumptions. Please note that this is also an upstream issue, so you can help by researching in the upstream bug tracker² for a bug about it. If you find one, please add information about it to this bug report. Well I searched there for "kwalletmanager migration", but found no obvious fit for your bug description³. But please look for yourself and probably try out different search terms. I am not even sure whether the file format changed. Maybe its even sufficient to copy the kwl files over to the new location, but that might not be enough. I had issues with migration for one of my users, but I fixed them long ago and do not remember exactly what I did. The new location is: ~/.local/share/ kwalletd [0] https://barlog.rusu.info/valentin/blog/?p=300 [1] https://www.debian.org/Bugs/Developer#severities [2] https://bugs.kde.org [3] https://bugs.kde.org/buglist.cgi?quicksearch=kwallet%20migration Thank you, -- Martin
Bug#804272: fails to synchronize caldav to OpenXChange without notice
Control: tags -1 upstream
Control: severity -1 important
kthxbye
Hello Thomas, hello Enrico, hello Petter.
I am sorry that you received no response to this bug report earlier.
I am downgrading the bug to important as its not a policy violation and also
the package is not unsuitable for everyone.
Of course some time has passed and current Debian Stable aka Stretch has the
updated Akonadi version 16.04.3. Could you reproduce this issue with this
version or a newer one?
If so, I kindly ask you to report the bug upstream if not already done. We
greatly appreciate your help.
Please report it via Help -> Report bug... menu item of the respective
application or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).
Whenever you open a bug report or find an existing one on the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)
[ copy this ]
forwarded {debbug} KDE-BUG-URL
thanks
[ copy this ]
Thanks,
--
Martin
Re: Fwd: KMyMoney 5.0 string freeze
Martin Steigerwald - 13.01.18, 19:49: > Just a notice that another KF5/Qt5 port is about to be released quite soon – > I know you want to get rid of Qt 4 :) : Sorry for noise, I later recognized that Luigi is involved and knows about it already. Thanks, -- Martin
Fwd: KMyMoney 5.0 string freeze
Hello. Just a notice that another KF5/Qt5 port is about to be released quite soon – I know you want to get rid of Qt 4 :) : -- Weitergeleitete Nachricht -- Betreff: KMyMoney 5.0 string freeze Datum: Samstag, 13. Januar 2018, 14:24:31 CET Von: Thomas Baumgart An: kmymoney-de...@kde.org, kde-i18n-...@kde.org Hi all, now that the feature list has been updated as the last string change, I herewith announce the string freeze for KMyMoney's 5.0 branch (which was actually planned for yesterday). Further details about the release plan can be found here: https://kmymoney.org/news.php#itemKMyMoney50releaseplan @devs: please don't modify any string without prior coordination with development team. @i18n-teams: the application is frozen, the documentation still needs to be updated. In case you need any of the meta-data about repos or so updated, please let me/us know. -- Regards Thomas Baumgart […] - -- Martin
Bug#886107: kdepim: depends on a lot of developer packages
Dear Pino. Pino Toscano - 02.01.18, 12:32: > reassign 886107 kdepim-runtime > forcemerge 885111 886107 > thanks > > On martedì 2 gennaio 2018 10:43:56 CET Martin Steigerwald wrote: > > Package: kdepim > > Version: 4:16.04.3+5.95 > > Severity: normal […] > > Today I tried again to upgrade to KF 5.41 from experimental and aptitude > > stumbled over updating some -dev packages I had still installed. > > > > I removed them and was surprised that apt removed kdepim + kmail as well. > > > > Afterwards I reinstalled kdepim and saw that apt wants to draw in a lot > > of *-dev packages. > > This is most probably #885111, hence reassigning and merging. Thanks. Sorry, I missed this one while browsing reportbug bug list for possible duplicates. These dependencies are what appears to prevent the upgrade of KF 5.41 from experimental. merkaba:~#130> LANG=C apt install -t experimental plasma-framework kinit […] The following packages will be REMOVED: kde-full kde-standard kdepim kdepim-runtime kdoctools-dev kgendesignerplugin kinit-dev kio-dev kmail knotes konsolekalendar kontact korganizer kross-dev libkf5akonadi-dev libkf5akonadinotes-dev libkf5archive-dev libkf5auth-dev libkf5bookmarks-dev libkf5calendarcore-dev libkf5calendarutils-dev libkf5completion-dev libkf5config-dev libkf5configwidgets-dev libkf5contacts-dev libkf5coreaddons-dev libkf5crash-dev libkf5doctools-dev libkf5emoticons-dev libkf5guiaddons-dev libkf5i18n-dev libkf5iconthemes-dev libkf5jobwidgets-dev libkf5kcmutils-dev libkf5kdelibs4support-dev libkf5khtml-dev libkf5kio-dev libkf5mediaplayer-dev libkf5newstuff-dev libkf5notifications-dev libkf5notifyconfig-dev libkf5parts-dev libkf5pty-dev libkf5service-dev libkf5style-dev libkf5su-dev libkf5textwidgets-dev libkf5unitconversion-dev libkf5wallet-dev libkf5webkit-dev libkf5widgetsaddons-dev libkf5windowsystem-dev libkf5xmlgui-dev libkolab-dev […] Thanks, -- Martin
Bug#886107: kdepim: depends on a lot of developer packages
Package: kdepim Version: 4:16.04.3+5.95 Severity: normal Dear Sandro, dear Maxy, dear Pino, dear maintainers, A happy, peaceful and successful new year to you! Today I tried again to upgrade to KF 5.41 from experimental and aptitude stumbled over updating some -dev packages I had still installed. I removed them and was surprised that apt removed kdepim + kmail as well. Afterwards I reinstalled kdepim and saw that apt wants to draw in a lot of *-dev packages. # Actual results merkaba:~> LANG=C apt install --no-install-recommends kdepim Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: kdepim-runtime kinit-dev kio-dev kio-ldap kio-sieve kio-smtp kmail knotes konsolekalendar kontact korganizer kross-dev libboost-thread-dev libical2-dev libkf5akonadi-dev libkf5akonadinotes-dev libkf5auth-dev libkf5bookmarks-dev libkf5calendarcore-dev libkf5calendarutils-dev libkf5configwidgets-dev libkf5contacts-dev libkf5coreaddons-dev libkf5crash-dev libkf5emoticons-dev libkf5guiaddons-dev libkf5iconthemes-dev libkf5jobwidgets-dev libkf5kcmutils-dev libkf5kdelibs4support-dev libkf5khtml-dev libkf5kio-dev libkf5mediaplayer-dev libkf5mime-dev libkf5newstuff-dev libkf5notifications-dev libkf5notifyconfig-dev libkf5parts-dev libkf5pty-dev libkf5service-dev libkf5style-dev libkf5su-dev libkf5textwidgets-dev libkf5webkit-dev libkf5xmlgui-dev libkolab-dev libkolabxml-dev libkpimgapicalendar5 libkpimgapicontacts5 libkpimgapicore5 libkpimgapitasks5 libkpimkdav5 libqt5quicktest5 libqt5webengine5 libqt5webkit5-dev libssl1.0-dev libxerces-c-dev qtdeclarative5-dev Suggested packages: clamav procmail gnokii libxerces-c-doc Recommended packages: kdepim-doc mbox-importer pim-data-exporter pim-sieve-editor libkf5auth-doc libkf5bookmarks-doc libkf5configwidgets-doc libkf5coreaddons-doc libkf5crash-doc libkf5emoticons-doc libkf5guiaddons-doc libkf5iconthemes-doc libkf5jobwidgets-doc libkf5kcmutils-doc libkf5kio-doc libkf5newstuff-doc libkf5notifications-doc libkf5notifyconfig-doc libkf5parts-doc libkf5pty-doc libkf5service-doc libkf5su-doc libkf5textwidgets-doc libkf5xmlgui-doc The following NEW packages will be installed: kdepim kdepim-runtime kinit-dev kio-dev kio-ldap kio-sieve kio-smtp kmail knotes konsolekalendar kontact korganizer kross-dev libboost-thread-dev libical2-dev libkf5akonadi-dev libkf5akonadinotes-dev libkf5auth-dev libkf5bookmarks-dev libkf5calendarcore-dev libkf5calendarutils-dev libkf5configwidgets-dev libkf5contacts-dev libkf5coreaddons-dev libkf5crash-dev libkf5emoticons-dev libkf5guiaddons-dev libkf5iconthemes-dev libkf5jobwidgets-dev libkf5kcmutils-dev libkf5kdelibs4support-dev libkf5khtml-dev libkf5kio-dev libkf5mediaplayer-dev libkf5mime-dev libkf5newstuff-dev libkf5notifications-dev libkf5notifyconfig-dev libkf5parts-dev libkf5pty-dev libkf5service-dev libkf5style-dev libkf5su-dev libkf5textwidgets-dev libkf5webkit-dev libkf5xmlgui-dev libkolab-dev libkolabxml-dev libkpimgapicalendar5 libkpimgapicontacts5 libkpimgapicore5 libkpimgapitasks5 libkpimkdav5 libqt5quicktest5 libqt5webengine5 libqt5webkit5-dev libssl1.0-dev libxerces-c-dev qtdeclarative5-dev 0 upgraded, 59 newly installed, 0 to remove and 0 not upgraded. Need to get 16.5 MB/17.4 MB of archives. After this operation, 95.1 MB of additional disk space will be used. Also the version number of the KDEPIM meta package suggests that is still for 16.04 instead of 17.08 of KDEPIM. # Expected results As kdepim is about the pre-compiled, binary version of KDEPIM I´d expect to depend on no *-dev packages. I´d expect these to be installed as build dependencies in case I want to build KDEPIM myself. Of course it may be that it is not kdepim package itself drawing in these development packages, but some package it depends on does this. Also I´d expect the version number of the meta package reflect which version of KDEPIM is going to be installed. Thank you, Martin -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-rc5-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT) 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) Versions of packages kdepim depends on: ii accountwizard4:17.08.3-1 ii akonadiconsole 4:17.08.3-1 ii akregator4:17.08.3-1 ii blogilo 4:17.08.3-1 ii kaddressbook 4:17.08.3-1 ii kalarm 4:17.08.3-1 ii kdepim-runtime 4:17.08.3-1 ii kleopatra4:17.08.3-1 ii kmail4:17.08.3-1 ii knotes 4:17.08.3-1 ii konsolekalendar 4:17.08.3-1 ii kontact 4:17.08.3-1 ii korganizer 4:17.08.3-1 Versions of packages kdepim recommends: ii kdepim-addo
Bug#881748: akregator: crash on startup (solved)
Hello Antonio. Antonio - 16.11.17, 08:16: > Thanks for reply. > > I installed from experimental repository these packages: > - akregator > - blogilo > - accountwizard > - kontact > but I have same problem. > > After investigation found the problem: I did not have a crash yet, but on researching for a bug why something context menu does not contain "Open link …" and "Back" / "Forward" entries I found: Bug 377129 - Akregator crashes immediatelly after being launched https://bugs.kde.org/show_bug.cgi?id=377129 And several others. Fixed in KDE Applications 17.08.3 which Debian Qt/KDE team currently uploads. Thanks, -- Martin
Bug#879095: sddm flickering on login screen (white + repaint)
Hello. I can confirm this behavior on an IBM ThinkPad T42 with Radeon graphics. martin@shambhala:~> lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ ATI] RV350/M10 / RV360/M11 [Mobility Radeon 9600 (PRO) / 9700] [1002:4e50] For me it appears to be related to Flickering ATI X1300 r300 Mesa 17.2 https://github.com/sddm/sddm/issues/898 However disabling vsync for r300 driver did not help. I tried it via .drirc in /root and in /var/lib/sddm like this: I also tried "dri2" as driver name. Thanks, -- Martin
Bug#866174: dolphin: Reload results in extending selection of files when ordered by tag
tag -1 upstream thanks Hola Leoš. Leoš Pohl - 27.06.17, 18:38: > Package: dolphin > Version: 4:16.08.3-3 > Severity: normal > > Dear Maintainer, > > If one sorts files in Dolphin by tags, then selects several files in > immediate sequence, however, not starting at the top of the list (e.g. > select files 4th - 6th) and then press F5 or select Cotnrol -> Reload, the > selection is extended to include all the files above the bottom most > selected. This sounds like an upstream bug that it out of the scope to fix it directly in Debian. Please choose one of the following options to proceed: 1. Try with a more recent Plasma / Dolphin version, for example by booting KDE Neon live system from an USB stick or DVD. If the issue is still there, please report it upstream at bugs.kde.org 2. Wait till a newer version of Dolphin appears in Debian and report an upstream bug report if the issue is still there then. Of course you can also report an upstream bug right away, but upstream may ask you to test with a newer version. If you report upstream, please send the URL to the bug report to this Debian bug report as well. By reporting a bug upstream you help Debian Qt/KDE team to focus on packaging work. Gracias. -- Martin signature.asc Description: This is a digitally signed message part.
Bug#856321: Fwd: KDE Project Security Advisory: ktnef: Directory Traversal
Attached is original security advisory. I choose attachment in order to preserve the mail headers. Thanks, -- Martin--- Begin Message --- KDE Project Security Advisory = Title: ktnef: Directory Traversal Risk Rating:Medium CVE:TBC Versions: ktnef <= 5.4.2 (KDE Applications 16.12.2) Date: 27 February 2017 Overview A directory traversal issue was found in ktnef which can be exploited by tricking a user into opening a malicious winmail.dat file. The issue allows to write files with the permission of the user opening the winmail.dat file during extraction. Solution Update to ktnef >= 5.4.3 (KDE Applications 16.12.3) (when released) Or apply the following patch: https://commits.kde.org/ktnef/4ff38aa15487d69021aacad4b078500f77fb4ae8 Credits === Thanks to X41 D-Sec GmbH for finding the issue and providing us with files to reproduce it --- End Message ---
Bug#856321: ktnef security issue: Directory Traversal
Package: ktnef Version: 4:16.04.3-3 Severity: important Tags: patch Dear Maintainer, from the KDE project security advisory: > A directory traversal issue was found in ktnef which can > be exploited by tricking a user into opening a malicious winmail.dat file. > The issue allows to write files with the permission of the user opening > the winmail.dat file during extraction. I forward the KDE project security advisory to the bug as soon as I got back bug number. Patch is at: https://commits.kde.org/ktnef/4ff38aa15487d69021aacad4b078500f77fb4ae8 Thank you, Martin -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.16-tp520+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages ktnef depends on: ii kio 5.28.0-1 ii libc6 2.24-9 ii libkf5configcore5 5.28.0-1 ii libkf5configwidgets5 5.28.0-1 ii libkf5coreaddons5 5.28.0-1 ii libkf5dbusaddons5 5.28.0-1 ii libkf5i18n5 5.28.0-1 ii libkf5kiowidgets5 5.28.0-1 ii libkf5service-bin 5.28.0-1 ii libkf5service55.28.0-1 ii libkf5tnef5 16.04.2-1 ii libkf5widgetsaddons5 5.28.0-1 ii libkf5xmlgui5 5.28.0-1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5widgets55.7.1+dfsg-3+b1 ii libstdc++67-20170221-1 ktnef recommends no packages. ktnef suggests no packages. -- no debconf information
Re: Bug#853241: kf5-messagelib: CVE-2016-7967 CVE-2016-7968
Am Montag, 30. Januar 2017, 19:55:16 CET schrieb Thorsten Alteholz: > Package: kf5-messagelib > Severity: important > Tags: security […] > the following vulnerabilities were published for kf5-messagelib. > > CVE-2016-7967[0]: > | KMail since version 5.3.0 used a QWebEngine based viewer that had > | JavaScript enabled. Since the generated html is executed in the local > | file security context by default access to remote and local URLs was > | enabled. > > CVE-2016-7968[1]: > | KMail since version 5.3.0 used a QWebEngine based viewer that had > | JavaScript enabled. HTML Mail contents were not sanitized for > | JavaScript and included code was executed. Unstable has KMail 5.2.3 from KDEPIM 16.04 which AFAIK doesn´t use webengine yet. I am not sure whether the older KMail + messagelib stuff has similar issues. Ciao, -- Martin
Bug#849978: nothing depends on or recommends qml-module-org-kde-kaccounts
Package: qml-module-org-kde-kaccounts Version: 16.08.3-1 Severity: normal Dear Maintainer, nothing depends on or recommends qml-module-org-kde-kaccounts. This probably hints to a missing dependency or recommendation. merkaba:~> apt-cache rdepends qml-module-org-kde-kaccounts qml-module-org-kde-kaccounts Reverse Depends: Thanks, Martin -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.15-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages qml-module-org-kde-kaccounts depends on: ii libaccounts-qt5-1 1.13+20150813-1 ii libc6 2.24-8 ii libgcc11:6.3.0-2 ii libkaccounts1 16.08.3-1 ii libkf5coreaddons5 5.28.0-1 ii libkf5i18n55.28.0-1 ii libqt5core5a 5.7.1+dfsg-2 ii libqt5gui5 5.7.1+dfsg-2 ii libqt5qml5 5.7.1-1 ii libsignon-qt5-18.59-1 ii libstdc++6 6.3.0-2 qml-module-org-kde-kaccounts recommends no packages. qml-module-org-kde-kaccounts suggests no packages. -- no debconf information
Bug#849976: qml-module-org-kde-people: has no reverse depends
Package: qml-module-org-kde-people Version: 5.28.0-1 Severity: normal Dear Maintainer, this qml module package has no reverse depends. This probably hints at a missing dependency. merkaba:~> apt-cache rdepends qml-module-org-kde-people qml-module-org-kde-people Reverse Depends: Thanks, Martin -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.15-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages qml-module-org-kde-people depends on: ii libc6 2.24-8 ii libkf5people5 5.28.0-1 ii libkf5peoplewidgets5 5.28.0-1 ii libqt5core5a 5.7.1+dfsg-2 ii libqt5gui55.7.1+dfsg-2 ii libqt5qml55.7.1-1 ii libqt5widgets55.7.1+dfsg-2 ii libstdc++66.3.0-2 qml-module-org-kde-people recommends no packages. qml-module-org-kde-people suggests no packages. -- no debconf information
Fwd: Re: Bug#834131: Video support still not working
Forwarding to Qt/KDE maintainers list as it may be read more closely. Also asking on #debian-qt-kde channel may yield quicker results. Ciao, Martin -- Weitergeleitete Nachricht -- Betreff: Re: Bug#834131: Video support still not working Datum: Sonntag, 18. Dezember 2016, 13:53:34 CET Von: Steve M. Robbins An: Simon Frei , pkg-kde-t...@lists.alioth.debian.org MartinKopie: Steigerwald On Sunday, December 18, 2016 2:49:42 PM CST Simon Frei wrote: > [...] upstream has dropped QTmultimedia for video handling and uses > QtAV (which in turn is based of ffmpeg). Unfortunately QtAV is not yet > in debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737016), > however upstream provides debian packaging already, which worked almost > fine for me (buildep without -nc flag resulted in an error). This will > take effect in the upcoming 5.4.0 release due at the end of this month. Thanks for the heads-up on the change to QtAV. Question for the KDE maintainers: the RFP for QtAV is fairly old, which makes me wonder if there is any issue (technical or legal) that stands in the way of packaging it. ?? Thanks, -Steve - -- Martin
Re: Bug#843416: libqt5widgets5: quasselclient segfaults with version 5.7.1~20161021+dfsg-5 of libqt5widgets5
Version: 5.8.2-1+b1 thanks Am Sonntag, 6. November 2016, 17:49:52 CET schrieb Dmitry Shachnev: > Hi Martin, > > On Sun, Nov 06, 2016 at 03:33:14PM +0100, Martin Steigerwald wrote: > > Dear Dmitry, dear Maintainer, > > > > with most recent libqt5widgets5 5.7.1~20161021+dfsg-5 quasselclient > > crashes > > on start. > > > > How to reproduce: > > - have that version of libqt5widgets5 > > - install quassel-client package > > - run quasselclient > > (Copying myself from IRC, for the record.) > > This will be fixed when plasma-integration is binNMUed, I have left > a message on #842574 about that. plasma-integration fixes the issue for me: 5.8.2-1+b1 Thanks, -- Martin
Bug#843416: libqt5widgets5: quasselclient segfaults with version 5.7.1~20161021+dfsg-5 of libqt5widgets5
Am Sonntag, 6. November 2016, 17:49:52 CET schrieb Dmitry Shachnev: > On Sun, Nov 06, 2016 at 03:33:14PM +0100, Martin Steigerwald wrote: > > Dear Dmitry, dear Maintainer, > > > > with most recent libqt5widgets5 5.7.1~20161021+dfsg-5 quasselclient > > crashes > > on start. […] > (Copying myself from IRC, for the record.) > > This will be fixed when plasma-integration is binNMUed, I have left > a message on #842574 about that. Wonderful! Thank you. -- Martin
Bug#843416: libqt5widgets5: quasselclient segfaults with version 5.7.1~20161021+dfsg-5 of libqt5widgets5
Package: libqt5widgets5
Version: 5.7.1~20161021+dfsg-5
Severity: normal
Dear Dmitry, dear Maintainer,
with most recent libqt5widgets5 5.7.1~20161021+dfsg-5 quasselclient crashes
on start.
How to reproduce:
- have that version of libqt5widgets5
- install quassel-client package
- run quasselclient
# gdb quasselclient
GNU gdb (Debian 7.11.1-2) 7.11.1
[…]
Reading symbols from quasselclient...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/quasselclient
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdfa50700 (LWP 9435)]
[New Thread 0x7fffddc3c700 (LWP 9436)]
[New Thread 0x7fffd5a10700 (LWP 9437)]
Thread 1 "quasselclient" received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt full
#0 0x in ()
#1 0x7377d30e in copyActionToPlatformItem(QAction const*,
QPlatformMenuItem*, QPlatformMenu*) (action=action@entry=
0x55ced3c0, item=item@entry=0x55f58ef0, itemsMenu=0x55f529e0)
at widgets/qmenu.cpp:3277
#2 0x7377cf11 in QMenuPrivate::syncPlatformMenu()
(this=0x55f57760) at widgets/qmenu.cpp:192
menuItem = 0x55f58ef0
action = 0x55ced3c0
it = {> = {}, current = {i =
0x55f57d80}}
end =
{> = {}, current = {i =
0x55f57d50}}
beforeItem = 0x0
actions =
{> = {}, {p = {static
shared_null = {ref = {atomic = {_q_value = {> = {static
_S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end =
0, array = {0x0}}, d = 0x55f57d40}, d = 0x55f57d40}}
#3 0x7377d027 in QMenu::setPlatformMenu(QPlatformMenu*)
(this=this@entry=0x55f50200, platformMenu=) at
widgets/qmenu.cpp:3482
#4 0x73966eb5 in QSystemTrayIconPrivate::addPlatformMenu(QMenu*) const
(this=0x55f56170, menu=0x55f50200) at util/qsystemtrayicon.cpp:767
it =
{c = {> = {}, {p =
{static shared_null = {ref = {atomic = {_q_value = {> =
{static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x55f57d40}, d = 0x55f57d40}}, i = {i =
0x55f57d80}}
platformMenu =
menu = 0x55f50200
this = 0x55f56170
#5 0x73966f92 in QSystemTrayIconPrivate::updateMenu_sys_qpa()
(this=0x55f56170) at util/qsystemtrayicon.cpp:716
#6 0x556df11c in StatusNotifierItem::init() ()
#7 0x556c1097 in MainWin::init() ()
#8 0x556c4fd4 in QtUi::init() ()
#9 0x5566d5d2 in ()
#10 0x5566abcc in main ()
(gdb)
Thanks,
Martin
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages libqt5widgets5 depends on:
ii libc62.24-5
ii libqt5core5a [qtbase-abi-5-7-1] 5.7.1~20161021+dfsg-5
ii libqt5gui5 5.7.1~20161021+dfsg-5
ii libstdc++6 6.2.0-11
libqt5widgets5 recommends no packages.
libqt5widgets5 suggests no packages.
-- no debconf information
Bug#843259: qml-module-org-kde-analitza: not co-installable with Qt 5.7.1
notfound 843259 4:16.08.1-1+b1 thanks Am Samstag, 5. November 2016, 16:42:42 CET schrieb Diederik de Haas: > On zaterdag 5 november 2016 16:22:45 CET Martin Steigerwald wrote: > > Package: qml-module-org-kde-analitza > > Version: 4:16.08.1-1 > > > Seems this may need a rebuilt: > Indeed: > # aptitude show qml-module-org-kde-analitza > Package: qml-module-org-kde-analitza > Version: 4:16.08.1-1+b1 > New: yes > State: not installed > Priority: optional > Section: libs > Maintainer: Debian/Kubuntu Qt/KDE Maintainers > Architecture: amd64 > Uncompressed Size: 131 k > Depends: analitza-common, libanalitza7 (>= 4:14.11.97), libanalitzagui7 (>= > 4:16.04.0), libanalitzaplot7 (>= 4:15.12.0), libc6 (>=2.14), libqt5core5a > (>=5.7.0), libqt5gui5 (>= 5.4), libqt5qml5 (>= 5.0.2), libqt5quick5 > (>=5.6.0~beta), libstdc++6 (>=4.1.1), qtdeclarative-abi-5-7-0 > > Notice the +b1 in _my_ version number, which probably appeared with the > 2016-11-05-1425.53.pdiff repo update ;-) Indeed, and it depends on new qtdeclarative-abi-5-7-0 so … closing this bug. Thanks, -- Martin
Bug#843259: qml-module-org-kde-analitza: not co-installable with Qt 5.7.1
Package: qml-module-org-kde-analitza
Version: 4:16.08.1-1
Severity: normal
Dear Maintainer,
Seems this may need a rebuilt and/or dependency update:
merkaba:~> LANG=C aptitude dist-upgrade
The following NEW packages will be installed:
libboost1.62-dev{ab} libqt5waylandcompositor5{a}
The following packages will be REMOVED:
libdouble-conversion1{u} libftdi1{u} libgeos-3.5.0{u} libicu55{u}
libicu55:i386{u} libopencv-legacy2.4v5{u}
The following packages will be upgraded:
akonadi-backend-mysql akonadi-server kde-style-qtcurve-qt5
kpackagelauncherqml kwin-common kwin-wayland kwin-wayland-backend-drm
kwin-wayland-backend-wayland
kwin-wayland-backend-x11 kwin-x11 libboost-dev libfm-qt3 libkf5akonadi-dev
libkf5akonadiagentbase5 libkf5akonadicore-bin libkf5akonadicore5
libkf5akonadiprivate5
libkf5akonadiserver-dev libkf5akonadiwidgets5 libkf5akonadixml5
libkf5calendarevents5 libkf5declarative5 libkf5quickaddons5
libkwin4-effect-builtins1 libkwineffects9
libkwinglutils9 libkwinxrenderutils9 libqt5clucene5 libqt5concurrent5
libqt5core5a libqt5dbus5 libqt5designer5 libqt5designercomponents5 libqt5gui5
libqt5help5
libqt5multimedia5 libqt5multimediaquick-p5 libqt5multimediawidgets5
libqt5network5 libqt5opengl5 libqt5opengl5-dev libqt5positioning5
libqt5printsupport5 libqt5qml5
libqt5quick5 libqt5quickparticles5 libqt5quicktest5 libqt5quickwidgets5
libqt5script5 libqt5scripttools5 libqt5serialport5 libqt5sql5 libqt5sql5-mysql
libqt5sql5-sqlite libqt5svg5 libqt5svg5-dev libqt5test5 libqt5waylandclient5
libqt5webkit5 libqt5webkit5-dev libqt5widgets5 libqt5x11extras5
libqt5x11extras5-dev
libqt5xdg2 libqt5xdgiconloader2 libqt5xml5 libqt5xmlpatterns5
libqt5xmlpatterns5-dev libvlc-bin libvlc-dev libvlc5 libvlccore-dev libvlccore8
mame mame-data
pcmanfm-qt pinentry-qt pinentry-qt4 python3-dbus.mainloop.pyqt5 python3-pyqt5
python3-pyqt5.qtopengl qdbus-qt5 qlipper qml-module-org-kde-draganddrop
qml-module-org-kde-kcoreaddons qml-module-org-kde-kio
qml-module-org-kde-kquickcontrols qml-module-org-kde-kquickcontrolsaddons
qml-module-org-kde-kwindowsystem
qml-module-qt-labs-folderlistmodel qml-module-qt-labs-settings
qml-module-qtgraphicaleffects qml-module-qtmultimedia qml-module-qtqml-models2
qml-module-qtquick-controls qml-module-qtquick-dialogs
qml-module-qtquick-layouts qml-module-qtquick-privatewidgets
qml-module-qtquick-window2 qml-module-qtquick2
qml-module-qtwebkit qmlscene qt5-image-formats-plugins qt5-qmake
qt5-qmltooling-plugins qtbase5-dev qtbase5-dev-tools qtdeclarative5-dev
qtscript5-dev qttools5-dev
qttools5-dev-tools qtwayland5 vlc vlc-bin vlc-data vlc-l10n vlc-plugin-base
vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba vlc-plugin-video-output
The following packages are RECOMMENDED but will NOT be installed:
libqt5multimedia5-plugins qt5-gtk-platformtheme vlc-plugin-skins2
vlc-plugin-video-splitter vlc-plugin-visualization
121 packages upgraded, 2 newly installed, 6 to remove and 0 not upgraded.
Need to get 113 MB of archives. After unpacking 54.9 MB will be used.
The following packages have unmet dependencies:
libboost1.62-dev : Conflicts: libboost1.61-dev but 1.61.0+dfsg-3+b1 is
installed
qml-module-org-kde-analitza : Depends: qtdeclarative-abi-5-6-0 which is a
virtual package, provided by:
- libqt5qml5 (5.6.1-11), but
5.7.1~20161021-4 is to be installed
The following actions will resolve these dependencies:
Remove the following packages:
1) kalgebra [4:16.08.0-1 (now, unstable)]
2) kalgebra-common [4:16.08.0-1 (now, unstable)]
3) kde-full [5:91 (now, unstable)]
4) kdeedu [4:15.08.0+5.91 (now, unstable)]
5) qml-module-org-kde-analitza [4:16.08.1-1 (now, unstable)]
Keep the following packages at their current version:
6) libboost-dev [1.61.0.2 (now)]
7) libboost1.62-dev [Not Installed]
Accept this solution? [Y/n/q/?]
Ciao,
Martin
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages qml-module-org-kde-analitza depends on:
ii analitza-common 4:16.08.1-1
ii libanalitza7 4:16.08.1-1
ii libanalitzagui7 4:16.08.1-1
ii libanalitzaplot7 4:16.08.1-1
ii libc6 2.24-5
ii libqt5core5a 5.6.1+dfsg-3+b1
ii libqt5gui55.6.1+dfsg-3+b1
ii libqt5qml5 [qtdeclarative-abi-5-6-0] 5.6.1-11
ii libqt5quick
Re: CVE-2016-7966 Informations got updated
Hi Sandro. Am Mittwoch, 2. November 2016, 14:02:37 CET schrieb Sandro Knauß: > Hey, > > nice roundtrip :) Actually this additional updates for CVE-2016-7966 were > introduced by me, when I was fixing the Debian packages. > > This means the packages in Debian have the additional patches backported > already. Thank you very much for already fixing it. Well that was when the information appeared in kde-announce. Anyway, in case you already follow KDEPIM security, I can stop forwarding announcements related to it. Thank you, Martin > Am Mittwoch, 2. November 2016, 10:14:06 CET schrieb Martin Steigerwald: > > Hello! > > > > For your information, it seems that a complete fix for the security > > vulnerability needs additional patches. > > > > Thank you, > > Martin > > > > -- Weitergeleitete Nachricht -- > > > > Betreff: Re: KDE Project Security Advisory: KMail: HTML injection in plain > > text viewer > > Datum: Dienstag, 1. November 2016, 23:42:54 CET > > Von: Albert Astals Cid > > An: KDE announce list > > > > Updated Information (1 November 2016) > > = > > > > The above mentioned patches are not enough to fix the vulnerability > > completely. This wasn't visible, because the patches for CVE-2016-7967 and > > CVE-2016-7968 made sure, > > that this vulnerability can't harm anymore. > > It only became visible, that this vulnerability isn't closed completely > > for > > systems, > > that are only affected by this CVE. > > > > For KCoreAddons you need: > > https://quickgit.kde.org/? > > > > p=kcoreaddons.git&a=commitdiff&h=96e562d9138c100498da38e4c5b4091a226dde12 > > > > for applying this patch you may also need to cherry-pick: > > https://quickgit.kde.org/? > > > > p=kcoreaddons.git&a=commitdiff&h=1be7272373d60e4234f1a5584e676b579302b053 > > (these two are released in KCoreAddons KDE Frameworks 5.27.0) > > > > additionally git commits, to close completely: > > https://quickgit.kde.org/? > > > > p=kcoreaddons.git&a=commitdiff&h=5e13d2439dbf540fdc840f0b0ab5b3ebf6642c6a > > not needed in the strong sense, but this will give you the additional > > > > automatic tests, to test if this CVE is closed: > > https://quickgit.kde.org/? > > > > p=kcoreaddons.git&a=commitdiff&h=a06cef31cc4c908bc9b76bd9d103fe9c60e0953f > > (will be part of KCoreAddons KDE Frameworks 5.28.0) > > > > For kdepimlibs 4.14: > > https://quickgit.kde.org/? > > > > p=kdepimlibs.git&a=commitdiff&h=176fee25ca79145ab5c8e2275d248f1a46a8d8cf > > > > https://quickgit.kde.org/? > > > > p=kdepimlibs.git&a=commitdiff&h=8bbe1bd3fdc55f609340edc667ff154b3d2aaab1 > > kdepimlibs is at end of life, so no further release is planned. > > > > > > El dijous, 6 d’octubre de 2016, a les 19:44:33 CET, Albert Astals Cid va > > > > escriure: > > > KDE Project Security Advisory > > > = > > > > > > Title: KMail: HTML injection in plain text viewer > > > Risk Rating:Important > > > CVE:CVE-2016-7966 > > > Platforms: All > > > Versions: kmail >= 4.4.0 > > > Author: Andre Heinecke > > > Date: 6 October 2016 > > > > > > Overview > > > > > > > > > Through a malicious URL that contained a quote character it > > > was possible to inject HTML code in KMail's plain text viewer. > > > Due to the parser used on the URL it was not possible to include > > > the equal sign (=) or a space into the injected HTML, which greatly > > > reduces the available HTML functionality. Although it is possible > > > to include an HTML comment indicator to hide content. > > > > > > Impact > > > == > > > > > > An unauthenticated attacker can send out mails with malicious content > > > that breaks KMail's plain text HTML escape logic. Due to the limitations > > > of the provided HTML in itself it might not be serious. But as a way > > > to break out of KMail's restricted Plain text mode this might open > > > the way to the exploitation of other vulnerabilities in the HTML viewer > > > code, which is disabled by default. > > > > > > Workaround > > > == > > > > > > None. > > > > > > Solution > > > > > > > > > For KDE Frameworks based releases of KMail apply the following patch to > > > kcoreaddons: > > > https://quickgit.kde.org/?p=kcoreaddons.git&a=commitdiff&h=96e562d9138c1 > > > 00 > > > 49 8da38e4c5b4091a226dde12 > > > > > > For kdelibs4 based releases apply the following patch: > > > https://quickgit.kde.org/?p=kdepimlibs.git&a=commitdiff&h=176fee25ca7914 > > > 5a > > > b5 c8e2275d248f1a46a8d8cf > > > > > > Credits > > > === > > > > > > Thanks to Roland Tapken for reporting this issue, Andre Heinecke from > > > Intevation GmbH for analysing the problems and Laurent Montel for > > > fixing this issue. > > > > - -- Martin
Fwd: Re: KDE Project Security Advisory: KMail: HTML injection in plain text viewer
Hello! For your information, it seems that a complete fix for the security vulnerability needs additional patches. Thank you, Martin -- Weitergeleitete Nachricht -- Betreff: Re: KDE Project Security Advisory: KMail: HTML injection in plain text viewer Datum: Dienstag, 1. November 2016, 23:42:54 CET Von: Albert Astals Cid An: KDE announce list Updated Information (1 November 2016) = The above mentioned patches are not enough to fix the vulnerability completely. This wasn't visible, because the patches for CVE-2016-7967 and CVE-2016-7968 made sure, that this vulnerability can't harm anymore. It only became visible, that this vulnerability isn't closed completely for systems, that are only affected by this CVE. For KCoreAddons you need: https://quickgit.kde.org/? p=kcoreaddons.git&a=commitdiff&h=96e562d9138c100498da38e4c5b4091a226dde12 for applying this patch you may also need to cherry-pick: https://quickgit.kde.org/? p=kcoreaddons.git&a=commitdiff&h=1be7272373d60e4234f1a5584e676b579302b053 (these two are released in KCoreAddons KDE Frameworks 5.27.0) additionally git commits, to close completely: https://quickgit.kde.org/? p=kcoreaddons.git&a=commitdiff&h=5e13d2439dbf540fdc840f0b0ab5b3ebf6642c6a not needed in the strong sense, but this will give you the additional automatic tests, to test if this CVE is closed: https://quickgit.kde.org/? p=kcoreaddons.git&a=commitdiff&h=a06cef31cc4c908bc9b76bd9d103fe9c60e0953f (will be part of KCoreAddons KDE Frameworks 5.28.0) For kdepimlibs 4.14: https://quickgit.kde.org/? p=kdepimlibs.git&a=commitdiff&h=176fee25ca79145ab5c8e2275d248f1a46a8d8cf https://quickgit.kde.org/? p=kdepimlibs.git&a=commitdiff&h=8bbe1bd3fdc55f609340edc667ff154b3d2aaab1 kdepimlibs is at end of life, so no further release is planned. El dijous, 6 d’octubre de 2016, a les 19:44:33 CET, Albert Astals Cid va escriure: > KDE Project Security Advisory > = > > Title: KMail: HTML injection in plain text viewer > Risk Rating:Important > CVE:CVE-2016-7966 > Platforms: All > Versions: kmail >= 4.4.0 > Author: Andre Heinecke > Date: 6 October 2016 > > Overview > > > Through a malicious URL that contained a quote character it > was possible to inject HTML code in KMail's plain text viewer. > Due to the parser used on the URL it was not possible to include > the equal sign (=) or a space into the injected HTML, which greatly > reduces the available HTML functionality. Although it is possible > to include an HTML comment indicator to hide content. > > Impact > == > > An unauthenticated attacker can send out mails with malicious content > that breaks KMail's plain text HTML escape logic. Due to the limitations > of the provided HTML in itself it might not be serious. But as a way > to break out of KMail's restricted Plain text mode this might open > the way to the exploitation of other vulnerabilities in the HTML viewer > code, which is disabled by default. > > Workaround > == > > None. > > Solution > > > For KDE Frameworks based releases of KMail apply the following patch to > kcoreaddons: > https://quickgit.kde.org/?p=kcoreaddons.git&a=commitdiff&h=96e562d9138c10049 > 8da38e4c5b4091a226dde12 > > For kdelibs4 based releases apply the following patch: > https://quickgit.kde.org/?p=kdepimlibs.git&a=commitdiff&h=176fee25ca79145ab5 > c8e2275d248f1a46a8d8cf > > Credits > === > > Thanks to Roland Tapken for reporting this issue, Andre Heinecke from > Intevation GmbH for analysing the problems and Laurent Montel for > fixing this issue. - -- Martin
Fwd: Re: Can Plasma 5.9 depend on Qt 5.7
Hello. Lisandro, I forwarded your information on Qt 5.7 to KDE distributions mailing list, in the new thread "Can Plasma 5.9 depend on Qt 5.7?". I am not surprised that Martin recommends staying with Qt 5.6, but well I bet you have your reasons why you may choose Qt 5.7 for uploading. And fixes could be forward-ported I bet. Ciao, Martin -- Weitergeleitete Nachricht -- Betreff: Re: Can Plasma 5.9 depend on Qt 5.7 Datum: Donnerstag, 27. Oktober 2016, 12:39:17 CEST Von: Martin Gräßlin An: Martin Steigerwald Kopie: distributi...@kde.org Am 2016-10-27 11:40, schrieb Martin Steigerwald: > Hi Martin. > > Am Dienstag, 25. Oktober 2016, 08:16:26 CEST schrieb Martin Graesslin: >> the Plasma team would like to depend on Qt 5.7 for the next Plasma >> release >> (5.9). Reasons are among others, that we would like to use: >> * appmenu support >> * QtVirtualKeyboard support >> * QtQuickControls 2 >> >> Which are all new in Qt 5.7. >> >> We would like to know whether that would cause a problem for any >> distribution. Please remember that Plasma 5.8 is an LTS and will stay >> on Qt >> 5.6. > > From Lisandro of the Debian Qt/KDE team I received the following > answer: > > "we are working to have 5.7.1 into unstable soon, but we are on a tight > schedule." > > So it *might* be that Debian 9 aka Stretch ships with Qt 5.7. I would recommend to Debian to keep to Qt 5.6 which is the LTS version. Qt 5.6 will be maintained over (most of?) the life time of Debian 9. Qt 5.7 will be out of support pretty soon. > > Anyway unstable currently has Plasma 5.8.2 and I am not aware of any > plans to > move to 5.9 in time of Debian 9. So it is my personal oppinion that it > won´t > matter for Debian whether you require Qt 5.7 for Plasma 5.9 or not. ok, thanks for the info. Cheers - -- Martin
Re: Fwd: KDE Frameworks & Plasma 5.8 LTS
Am Sonntag, 23. Oktober 2016, 12:36:01 CEST schrieb Martin Steigerwald: > Hello! > > I mentioned there that Debian Sid already has KF 5.27. Link to thread: https://mail.kde.org/pipermail/kde-frameworks-devel/2016-October/038859.html (my mail to it awaits moderator approval) > What are you plans regarding Qt? I mentioned the Sid currently ships 5.6.1 > but also mentioned that Qt 5.7 is in experimental. > > Thanks, > Martin > > -- Weitergeleitete Nachricht -- > > Betreff: KDE Frameworks & Plasma 5.8 LTS > Datum: Sonntag, 23. Oktober 2016, 12:14:51 CEST > Von: Dominik Haumann > An: KDE Frameworks > > Hi, > > at the Frameworks BoF, the idea was raised to provide updates for the > KDE Frameworks 5.26 release, since this is the one that also is > typically shipped with the KDE Plasma 5.8 LTS version (at least, that > was the argument). > > Do we follow up on this? > > Do we have any knowledge on whether distributions that ship Plasma 5.8 > LTS still provide updates to KDE Frameworks 5.27 etc? > > There are two issues in KTextEditor 5.26 release that are not so nice > - that's why I'm asking. > > For use, there are two solutions: > 1. We just write to kde-distro-packagers to cherry-pick certain git commits > 2. We provide KF 5.26.1 > > Both is fine for me ;) > > Greetings > Dominik > > - -- Martin
Fwd: KDE Frameworks & Plasma 5.8 LTS
Hello! I mentioned there that Debian Sid already has KF 5.27. What are you plans regarding Qt? I mentioned the Sid currently ships 5.6.1 but also mentioned that Qt 5.7 is in experimental. Thanks, Martin -- Weitergeleitete Nachricht -- Betreff: KDE Frameworks & Plasma 5.8 LTS Datum: Sonntag, 23. Oktober 2016, 12:14:51 CEST Von: Dominik Haumann An: KDE Frameworks Hi, at the Frameworks BoF, the idea was raised to provide updates for the KDE Frameworks 5.26 release, since this is the one that also is typically shipped with the KDE Plasma 5.8 LTS version (at least, that was the argument). Do we follow up on this? Do we have any knowledge on whether distributions that ship Plasma 5.8 LTS still provide updates to KDE Frameworks 5.27 etc? There are two issues in KTextEditor 5.26 release that are not so nice - that's why I'm asking. For use, there are two solutions: 1. We just write to kde-distro-packagers to cherry-pick certain git commits 2. We provide KF 5.26.1 Both is fine for me ;) Greetings Dominik - -- Martin
Release Schedule for LTS (was: Fwd: Plasma BOF Notes)
Hi! JFYI. Thanks, Martin -- Weitergeleitete Nachricht -- Betreff: Plasma BOF Notes Datum: Dienstag, 13. September 2016, 11:24:38 CEST Von: David Edmundson An: Plasma Release Schedule for LTS: - start off as normal (as in the wiki) - then release individual packages as needed on an ad-hoc basis. - new LTS every 18 months when the previous one ends LTS and frameworks: - Officially we encourage people to use latest frameworks, but: - 5.26 can get backports for security and major fixes for the duration. - Will be done by David F by cherry-picking from master and creating new tags. There will be no visible branch. Normal Plasma releases: - There was a proposal to change our 3 months schedule, to 6/1/4/whatever - Summary: There are valid merits to both longer and shorter, but neither wins. Lets just leave it. Speeding up packages: - We should start using the frameworks style keywords in commit logs so we can automate the release anouncements more. Especially the bug fix releases. KHotkeys: - to be binned for 5.9 - we need to fix kmenuedit - we need to move spectacle / other defaults to the new shortcuts KCM - custom shortcuts for custom scripts now involve the user creating a .desktop file by hand, we consider that fine. - kconf update script to move existing scripts to shortcuts KCM or kwin Martinscripts if it's on window activation. Marco and G are volunteering to that respectively Wayland: Martin - gave a summary of all the things - SDDM in wayland is an important thing to do - plan is to launch kwin_wayland round the greeter - will need security locked down in kwin - will need to be in a config as it's shared - detect if it fails and restart with X if needed - we will then know if wayland works before we launch the real session - Plan to make Neon support wayland when that SDDM thing is in Other people led some other more specific topics, can those people write them up please. Etherpad: https://notes.kde.org/p/akademy-2k16-plasma-bof-topics - -- Martin
Bug#831983: kde-telepathy-contact-list: ktp-contactlist no longer able to log in to gtalk, sip
Dear Juha, Am Mittwoch, 20. Juli 2016, 23:40:41 CEST schrieb Juha Jäykkä: > Package: kde-telepathy-contact-list > Version: 15.08.3-1 > Severity: important > > Dear Maintainer, > > After upgrading to 15.08.3-1, ktp-contactlist (or the plasma applets) no > longer can log into gtalk or sip. These are possibly separate bugs as sip > auth handler segfaults whereas gtalk simply does not become "available". It > gives no error messages, warnings or any other indication that it is even > trying to do anything. In case you feel adventurous I suggest you try out whether upgrading kde- telepathy to the version in experimental fixes your issue. I see you have experimental added to your sources list anyway. > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 […] I used the following command to do just that on my sid system: apt -t experimental install kde-telepathy kde-telepathy-approver kde- telepathy-auth-handler kde-telepathy-contact-list kde-telepathy-data kde- telepathy-desktop-applets kde-telepathy-filetransfer-handler kde-telepathy- integration-module kde-telepathy-kaccounts kde-telepathy-kpeople kde- telepathy-minimal kde-telepathy-send-file kde-telepathy-text-ui qml-module- org-kde-telepathy If you try this and it fixes the issue for you, please let us now. Thank you, -- Martin
Fwd: Re: Handling framework packages in distros
Hello, I got a comprehensive answer back from Martin regarding my question regarding versioned dependencies in KDE Frameworks. He suggests ordering after tiers. This all is related the discussion in the "kde 5.7" thread on debian-kde. Users bring up the breakage of testing regularily there. Thanks, Martin -- Weitergeleitete Nachricht -- Betreff: Re: Handling framework packages in distros Datum: Montag, 11. Juli 2016, 08:14:28 CEST Von: Martin Graesslin An: distributi...@kde.org Kopie: mar...@lichtvoll.de On Saturday, July 9, 2016 6:42:57 PM CEST Martin Steigerwald wrote: > Hello! > > In Debian we saw versioned dependencies in KDE framework packages > repeatedly. Like krunner not working with a partial mix of 5.23 and 5.22 > framework packages in Debian testing¹. > > Thus I want to clarify on upstream recommendations here: > > I bet you do not document and in some cases maybe don´t even know all cases > where a newer framework module requires another new framework module, but > rather expect distros to upgrade all KDE Framework packages in lockstep. > > Is that true? Kind of. Frameworks are considered as one product and a mix of framework versions is neither tested nor supported by upstream. Higher tier frameworks do specify the dependencies to lower tier frameworks by the same version number. That is every dependency is found by the exact version number. On the other hand updating a framework should not break existing software. I don't know what exactly went wrong in the mentioned bug as there is no (?) crash trace included and also don't really understand the bug report (too much noise). Maybe it's just a missing dependency somewhere? > > Since the order in which packages enter Debian Unstable and especially > Testing is not predictable this creates issues for users of these Debian > versions and also leads to bug reports that are interim breakages. > > Any recommendations, any ideas? A role out of all packages by tiers should work. E.g. first shipping all tier 1 packages. That should not break any existing package (ABI compatibility and things like that) and should be possible to do without an all or nothing. Afterwards you could role out tier 2 packages - those should also be possible to upgrade without an all or nothing. For tier 3 I'm not sure. If all dependencies are properly specified a role out should also be safe. If you don't know whether all dependencies are set correctly I would go for all as one. It's obvious that things break if a framework depends on new (runtime) functionality of another framework and that's not updated yet. But in the end that's just a missing dependency. If you see cases where dependencies are not properly specified upstream, please report to us. As a general note: I would recommend offline updates in distributions. Updates can do weird things to running application by e.g. loading newer plugins into applications started against the library of the older version. Such situations can easily happen with the highly plugin based applications in the KDE world. Cheers Martin - -- Martin
Bug#829614: plasma-workspace: krunner no longer launches application
Am Samstag, 9. Juli 2016, 16:41:13 CEST schrieb Diederik de Haas: > On zaterdag 9 juli 2016 16:29:27 CEST Gard Spreemann wrote: > > Do I mark it as fixed in 5.23.0, or do we instead consider this a > > non-bug I experienced because I had inadvertendly mixed Plasma > > versions? > > I'd say neither. > The issue seems (very much) to be caused by various framework packages not > being at the same versions. > It is still not known whether they all need to be at the same versions or > only a subset of those framework packages and which that would be. > > And as it causes real issues, it is a valid bug. It depends on the version of packages that end up in Stretch. I think upstream wise versioned dependencies for KDE framework modules to other KDE framework modules are not documented, probably not even always known, so I bet it is safest to provide *all* KF5 packages for Stretch in the exact same version. I tend to believe that this would also be upstream recommendation, but I ask on distributions mailing list. Ciao, -- Martin
Re: New Kmail and contact integration
Am Samstag, 9. Juli 2016, 01:02:23 CEST schrieb Yannick Roehlly: > Hi, Hello Yannick, Thank you for your feedback. > Since the recent KDEPIM update, I encounter these problems: Some of this are user support issues pointing to upstream problems, I suggest you use debian-kde mailing list for checking whether other users have the same issues and also check with upstream bug tracker. There you usually receive quicker feedback whether other users have similar issues, whether an issue may be a temporary breakage due to inconsistent package versions and so on. > - The contact avatar (from the address-book) is no more displayed in the > mail header. > > - The completion of To/Cc/... field does not take the contact addresses from > the address-book. For me it does, but there is currently an issue with it: You need to type some chars, then delete to the beginning of the input field and then type some chars again. This is an upstream issue. See at least: [kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook https://bugs.kde.org/show_bug.cgi?id=354400 But I think there is another one. > - It's no more possible to search for contact in Krunner. > > I remarks that the Krunner configuration did not propose the search in > contacts. Comparing with Archlinux, I found that I need to install > libkf5akonadisearch-plugins to make the option appear (shouldn't this > package be a dependence somewhere). But after installing it, none of the > problem above is solved. > > Did I miss something or is this a bug to report? I think this is worth a bug report. You can help by filing one. I wonder what package should depend on it or at least recommend it, but you can just choose one like kdepim meta package and let the Qt/KDE Debian/Kubuntu packaging team sort this out. Thanks, -- Martin
Bug#829614: plasma-workspace: Desktop search is also broken
Am Freitag, 8. Juli 2016, 15:46:24 CEST schrieben Sie: > In data giovedì 7 luglio 2016 20:26:42, Martin Steigerwald ha scritto: > > No error? Just no output? > > For some reason the Debian bug-tracking system is not showing my full > message, it curiously cut the interesting part! Please don´t use HTML mails. > In you click on "Message part 2" at the end of my message you'll be taken to > the link > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=829614;msg=30 where > you can see my full message, including terminal output Please review "Krunner stopped finding and running anything in Debian testing" thread on debian-kde mailinglist in case you use Debian Testing. Especially make sure libkf5plasma5 is at 5.23. Also to Gard: Please try this. Your issue bay also be fixed by this. Please use debian-kde mailinglist for further communication until its clear if there is really a bug or if its just a package version issue in testing currently. In case it would be beneficial to have a versioned dependency, you can still add that to the bug report later one. Thank you, Martin -- Martin
Fwd: Review of special packager access
Hello! In case no one of Qt/KDE team is subscribed on distro-packers, here is a mail about special packager access accounts. Martin -- Weitergeleitete Nachricht -- Betreff: Review of special packager access Datum: Freitag, 8. Juli 2016, 23:39:41 CEST Von: Ben Cooksley An: kde-distro-packag...@kde.org, kde-core-devel , kde-devel , informing about and discussing non-technical community topics , KDE release coordination Hi all, My apologies if you're not a packager or someone associated with a distribution - you can ignore this email. Packagers, please read on as this contains important details. First: If you're a packager, please ensure you are subscribed to kde-distro-packag...@kde.org, which is our usual list for communicating with packagers. It would seem a number of you are missing from there :) Prompted by a recent email I took a look at the list of accounts (one per distribution) which are provided in order to facilitate early access to packages - however for many i've no idea who would be the relevant point of contact. I'd therefore like for someone from each distribution to please confirm that their distro is still active and who can serve as a general point of contact for that distribution. It would also be appreciated if folks could check over their ~/.ssh/authorized keys file and remove any outdated keys. If your distribution has completely lost access, please have someone with an email address belonging to that distribution's domain email sysad...@kde.org to sort that out. KDE servers normally use a format something like this to clearly label whose key(s) are whose, for those that might find it helpful.: ## Name ssh-rsa ## Next Name The list of accounts, which should approximately correspond to distributions, is as follows: - Active - Aix - Aosc - Archlinux - Arklinux - Asplinux - Bluewhite64 - Chakra - Conectiva - Crux - Darwin - Debian - Exherbo - Fedora - FreeBSD - Gentoo - Kaos - Mageia - Magic - Mandriva - Meego - NetBSD - OpenBSD - PCLinuxOS - PLD - Redhat - Rpath - Siduction - Slackware - Slamd64 - SUSE - Tld - Tru64 - Tukaani - Turbo - Ubuntu - Uludag - Uoirix - Uomandriva - Uosolaris - Vine - Yellow - Yoper In two weeks time we'll go ahead and disable ones we don't get a response from. Thanks, Ben Cooksley KDE Sysadmin - -- Martin
Bug#829614: plasma-workspace: Desktop search is also broken
Am Donnerstag, 7. Juli 2016, 15:08:27 CEST schrieb Massimiliano Leoni: > In data giovedì 7 luglio 2016 14:53:37, Martin Steigerwald ha scritto: > > What does > > > > balooctl status > > > > say? > > > > And what > > > > dpkg -l | grep baloo | cut -c1-72 > > > > ? > > Here is the output of the commands above: > > ~$ balooctl status No error? Just no output? > ~$ dpkg -l | grep baloo | cut -c1-72 Well no wonder desktop search doesn´t work on your system as packages that are required for it are missing. On my system: martin@merkaba:~> LANG=C balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 192927 / 192927 files Current size of index is 1.32 GiB martin@merkaba:~> dpkg -l | grep baloo | cut -c1-72 ii baloo-dev 4:4.14.2-2 ii baloo-kf5 5.23.0-1 ii libbaloocore4 4:4.14.2-2 ii libbaloofiles44:4.14.2-2 ii libbaloopim4 4:4.14.2-2 ii libbalooqueryparser4 4:4.14.2-2 ii libbalooxapian4 4:4.14.2-2 ii libkf5baloo5 5.23.0-1 ii libkf5balooengine55.23.0-1 ii libkf5baloowidgets-bin16.04.0-1 ii libkf5baloowidgets5:amd64 16.04.0-1 I think I´d do apt install baloo-kf5 maybe you also need to install libkf5baloowidgets5 separately. > > I am on Debian Sid and desktop search and krunner work just fine. > > > > Another reason may be a corrupted desktop search database. > > How do I check this? It worked fine until the other day, and works fine > after downgrading. Well for me krunner crashed repeatedly as the database was broken with mdb.c in the backtrace. But on your system baloo does not seem to be installed, which is a user support issue, so please follow up on debian-kde mailinglist to keep this bug report to the real issue of the original reporter, that was with krunner. Its important to stay focussed on the original topic of a bug report and open new bug reports for other issues. The original bug sounds more general than just desktop search not working. Thank you, -- Martin
Bug#829614: plasma-workspace: Desktop search is also broken
Am Donnerstag, 7. Juli 2016, 12:03:48 CEST schrieb Massimiliano Leoni: > Package: plasma-workspace > Followup-For: Bug #829614 Dear Massimiliano, hello Gard > In addition to the info provided in Bug #829614, which I am also > experiencing, Iwould like to add that desktop search is broken as well > after upgrading to latest version 4:5.6.5-1. > In fact, typing the partial name of an application or file does not > yield the list of search results. What does balooctl status say? And what dpkg -l | grep baloo | cut -c1-72 ? The original reporter has testing aka stretch. In case you use testing it may be that not all important packages from Sid have entered testing yet. I am on Debian Sid and desktop search and krunner work just fine. Another reason may be a corrupted desktop search database. Thanks, -- Martin
Fwd: Long term support release for Plasma?
I didn´t receive this back from the list and I also do not see it on: https://lists.debian.org/debian-qt-kde/2016/06/threads.html So I send it again, even tough it seems Lisandro has seen the mail. Hello! here is a chance to speak up for having a Plasma LTS release? Its a post from the KDE distributions mailing list. In case you want to reply it makes sense to reply there. I can also reply, but I would like to know your preferences on this. Thank you. Here is what I would answer: > Here is an example (I mean it!) for how this could look like: > * 5.8 first LTS release based on Qt 5.6 (which is also an LTS) for X11 > * every fourth release will be another LTS release, so with the 3 month > cycle > there is one LTS per year - 5.8, 5.12, 5.16 > * Support is for five release cycles, so with 5.13 the 5.8 LTS goes EOL, > with > 5.17 the 5.12 release goes EOL > * bug fix release continue in the Fibonacci schedule till the EOL release > > We would like to know from you: > * is that something which is useful to you? Yes, it is. But 5.8 as first LTS release may be too late for Debian Stretch > * how often should we do an LTS release? Once a year sounds okay. The Debian release schedule is about every 2-3 years. > * how often should we do bug fix releases for an LTS? Depends on severy of issue. Its good to receive timely security fixes. > * how long should a LTS be supported? Ideally about 2-3 years at least. > Related to that: > * what to do with frameworks? Also provide an LTS release for the frameworks version that works best with a certain Plasma LTS. > * Would you freeze the frameworks version or continue to backport newer > framework versions to your distribution? Freeze. > * Would you want an LTS branch for frameworks as well? Yes. > * What would you expect that to look like? An LTS for the Frameworks version an specific Plasma LTS is initially used with it. Would that be in line with what you think? Thank you, Martin -- Weitergeleitete Nachricht -- Betreff: Long term support release for Plasma? Datum: Montag, 27. Juni 2016, 14:28:42 CEST MartinVon: Graesslin An: distributi...@kde.org Kopie: plasma-de...@kde.org Hi distributions, in Plasma we are considering to add a long term support release. For this idea we want to get some feedback from your side to know how we should set this up. Here is an example (I mean it!) for how this could look like: * 5.8 first LTS release based on Qt 5.6 (which is also an LTS) for X11 * every fourth release will be another LTS release, so with the 3 month cycle there is one LTS per year - 5.8, 5.12, 5.16 * Support is for five release cycles, so with 5.13 the 5.8 LTS goes EOL, with 5.17 the 5.12 release goes EOL * bug fix release continue in the Fibonacci schedule till the EOL release We would like to know from you: * is that something which is useful to you? * how often should we do an LTS release? * how often should we do bug fix releases for an LTS? * how long should a LTS be supported? Related to that: * what to do with frameworks? * Would you freeze the frameworks version or continue to backport newer framework versions to your distribution? * Would you want an LTS branch for frameworks as well? * What would you expect that to look like? Looking forward to your input on this rather important topic. Cheers Martin - -- Martin
Fwd: Long term support release for Plasma?
Hello! here is a chance to speak up for having a Plasma LTS release? Its a post from the KDE distributions mailing list. In case you want to reply it makes sense to reply there. I can also reply, but I would like to know your preferences on this. Thank you. Here is what I would answer: > Here is an example (I mean it!) for how this could look like: > * 5.8 first LTS release based on Qt 5.6 (which is also an LTS) for X11 > * every fourth release will be another LTS release, so with the 3 month > cycle > there is one LTS per year - 5.8, 5.12, 5.16 > * Support is for five release cycles, so with 5.13 the 5.8 LTS goes EOL, > with > 5.17 the 5.12 release goes EOL > * bug fix release continue in the Fibonacci schedule till the EOL release > > We would like to know from you: > * is that something which is useful to you? Yes, it is. But 5.8 as first LTS release may be too late for Debian Stretch > * how often should we do an LTS release? Once a year sounds okay. The Debian release schedule is about every 2-3 years. > * how often should we do bug fix releases for an LTS? Depends on severy of issue. Its good to receive timely security fixes. > * how long should a LTS be supported? Ideally about 2-3 years at least. > Related to that: > * what to do with frameworks? Also provide an LTS release for the frameworks version that works best with a certain Plasma LTS. > * Would you freeze the frameworks version or continue to backport newer > framework versions to your distribution? Freeze. > * Would you want an LTS branch for frameworks as well? Yes. > * What would you expect that to look like? An LTS for the Frameworks version an specific Plasma LTS is initially used with it. Would that be in line with what you think? Thank you, Martin -- Weitergeleitete Nachricht -- Betreff: Long term support release for Plasma? Datum: Montag, 27. Juni 2016, 14:28:42 CEST Von: Martin Graesslin An: distributi...@kde.org Kopie: plasma-de...@kde.org Hi distributions, in Plasma we are considering to add a long term support release. For this idea we want to get some feedback from your side to know how we should set this up. Here is an example (I mean it!) for how this could look like: * 5.8 first LTS release based on Qt 5.6 (which is also an LTS) for X11 * every fourth release will be another LTS release, so with the 3 month cycle there is one LTS per year - 5.8, 5.12, 5.16 * Support is for five release cycles, so with 5.13 the 5.8 LTS goes EOL, with 5.17 the 5.12 release goes EOL * bug fix release continue in the Fibonacci schedule till the EOL release We would like to know from you: * is that something which is useful to you? * how often should we do an LTS release? * how often should we do bug fix releases for an LTS? * how long should a LTS be supported? Related to that: * what to do with frameworks? * Would you freeze the frameworks version or continue to backport newer framework versions to your distribution? * Would you want an LTS branch for frameworks as well? * What would you expect that to look like? Looking forward to your input on this rather important topic. Cheers Martin - -- Martin
Bug#767905: kde-runtime is important
Hi! /usr/bin/kwalletd is the KDE SC 4 kwalletd, so kde-runtime may not be installed and you´d still have a working kwalletd5 system. So for migration it needs to be made sure that kde-runtime is installed as well. Thanks, -- Martin
